Let's go straight to your answers
1) Basically you can build your own services using the jBPM runtime as you build your applications or you can use the jBPM Console Server, which is provided by the installer. This Server exposes a jBPM runtime via REST. You can also use the Drools Server to expose knowledge sessions via REST and SOAP but that option will require more configurations from your side, or as mentioned before you can build your own custom service that exposes and works as you need for your application.
2) The jBPM Console Server is a web applicaiton, that means that it can be deployed in any servlet container, not matter if it's JBoss or another app server.
3) Once again, as you mention " you imagine an architecture", what you imagine is just one possible way of doing things. jBPM is flexible enough to allow you to do what you imagine, but you will need to set up or build your own components if the ones provided with the project doesn't fulfill your requirements. If you are planning to build an architecture on top of an Application Server, you can deploy the jBPM Console Server, it's not a big deal and you can use that to host your processes, if not you can build your own component to do that.
And thank you for the quick answers.
In fact, I didn't get the point that the console was split in 2 parts:
- the console
- the console server
And if I have a look to the file jbpm-5.2.0.Final-gwt-console.zip from jbpm-installer, I can see inside 2 war files, one for console and the other for console-server.
If you say that console-server embeds its own jbpm engine, ok I now understand. I just need to deploy this console-server (without the console) and to use the REST API.
Then I will have a distant access to my jbpm runtime running in only one place.
If this REST API is not enough, then I have to do my own developments.
Thank you very much for these clarifications.
That's the idea, I'm sure that the console server will be improved to support more use cases in the future, so in the case that it doesn't work for you, you can write us back with the reason why it doesn't work for you and we can work and update the server to fulfill your needs in the future. This is how community projects works