-
1. Re: jbpm-console can only see Evaluation process
thomas.setiabudi Jun 4, 2013 3:24 AM (in response to neilmc)Do you change the default setting of guvnor? like the guvnor port and host?
check the "default.jbpm.console.properties" file at "jbpm-gwt-console-server.war\WEB-INF\classes\default.jbpm.console.properties"
You should find the file content to be something like this:
jbpm.console.server.host=localhost
jbpm.console.server.port=8080
jbpm.console.task.service.strategy=HornetQ
jbpm.console.task.service.host=127.0.0.1
jbpm.console.task.service.port=5153
jbpm.console.directory=
guvnor.protocol=http
guvnor.host=localhost:8080
guvnor.subdomain=drools-guvnor
guvnor.usr=admin
guvnor.pwd=admin
guvnor.packages=
guvnor.connect.timeout=10000
guvnor.read.timeout=10000
guvnor.snapshot.name=LATEST
Just make sure that the guvnor setting points to your guvnor.
Regards,
Thomas Setiabudi
-
2. Re: jbpm-console can only see Evaluation process
neilmc Jun 4, 2013 2:08 PM (in response to thomas.setiabudi)Hi Thomas,
Thanks for the quick reply.
I didn't change any of the console.properties files, and the guvnor settings look fine.
It seems to be finding the sample Evaluation project only, which I don't even see in guvnor.
Some log value to look for? Some debug to turn on?
Regards,
Neil
-
3. Re: jbpm-console can only see Evaluation process
neilmc Jun 4, 2013 2:46 PM (in response to neilmc)Annnnd, it's now working.
Had restarted jboss AS, and it wasn't there.
Restarted again today, and it's there.
Sorry for wasting your time.
-
4. Re: jbpm-console can only see Evaluation process
atan20 Jun 4, 2013 7:35 PM (in response to neilmc)This is a problem with JBPM5.2 where the process list is only retrieved once in JBPM console. I have been re-deploying JBPM console after I add a new process to drools guvnor by running the following linux command in my deploy directory to see an updated list of processes:
touch jbpm-gwt-console*
-
5. Re: jbpm-console can only see Evaluation process
ashpcs Jun 6, 2013 7:25 AM (in response to atan20)I think the issue is still in JBPM 5.4 as well.
Redeploying the application does not look like an elegant solution but solution nonetheless.