via the browser
(read the fine gettingstarted page on the wiki)
Thanks for the reply.
My jbpm server is running as part of another app (which itself is a standalone java app). How do I access it then? what port number should I use? Can this be specified somewhere in any configuration file?
Another qs : The console web application connects to the jbpm server, right? So, this means that it will be up only when the server is up? Is there any way it can directly connect to the database?
JBoss jBPM provides a sample web app that has console functions. If you have deployed this app with jBPM, then you can access it like any other web deployment from the application server. This also means that if the application server is not running, the web app will not run. If you have embedded jBPM into another application and do not want to run the sample web app, then you will need to create your own web app for administration of jBPM. (This is also how you would have a console that could access the DB without jBPM running).
How do you deploy this app standalone? I am not deploying the jbpm server, as provided in the starters kit. I did look at the starters-kit. Is it
If so, then how do you start it?
no it is not, it is jbpm.war
But what does it startup?
Could you please provide some more details into starting up just the console. As I had mentioned earlier, I am running jbpm in my own standalone java app, which does not have a web container. Given this, what are the steps I need to take to start the console app, so that I can monitor the process instances?
Any help is greatly appreciated.
IT IS A WEBAPP. if you do not know how to access (startup) that, well........
The problem here is that many people get the impression that the sample webapp is the console. They think it is the way to do it, and it is responsible for managing jBPM.
It's a SAMPLE webapp, giving EXAMPLES on how to monitor/etc. I think something needs to be done (no clue what) about people getting the wrong impression. Many just think it is jBPM itself, and that's how you use it.
Crack the webapp code open, look at what it is doing, and copy/modify/paste into your non-web application.
Learning the jBPM API allows you to do anything without relying on the example webapp. Write your own monitoring tool how you want, and you'll be set.
Right, I made a mention of this in another thread. Many people have the misconception that the webapp is either the only way to interact with jBPM or that the webapp is inextricably (sp?) tied to jBPM. Like you say, it is just an example really...like a reference implementation. At my company, we've completely developed our own entire web application to interact with jBPM processes, as I'm sure many others have done. I suggested in that other thread that something be written up in a Wiki or added to a sticky thread on this forum. A sticky thread dispelling some misconceptions would be nice.
Yes, I second the sticky thread, something like "About the jBPM Sample Webapp" or something similar. :)
OK good suggestion. I'll try to add something to the faq (could someone make a jira issue for this so I do not forget, or do it themselves ;-)) A sticky thread with 'read the faq) would be enough then.
Besides that David, could you start a thread in the design forum about the (missing?) functionality in the webapp, what you developed yourself, why (e.g. jsf vs. struts).. the webapp has to grow to a real console, but also a UI for executing processes, at least during RAD, resulting in jsf components that can be used in other pages etc...etc...etc...
hmmm.. not the 'about jbpm sample webapp' it is to specific. There are more questions like these. I'd propose the FAQ wiki page
A full detailed wiki page please....
Also, how goes the DEV work on the console web app, it was mentioned that it is going to useing faces. Is that working now?
We believe we will be using the webapp, and then adding a bit more on top of it to support our users in a nice simple UI.
A full detailed wiki page takes a lot of time. So if someone wants to contribute, fine, otherise it will start with a small faq entry and maybe afterwards a more complete page.
And yes, the 3.2 webapp is using faces