-
1. Re: Second login Screen on remote access
tomathome Aug 29, 2011 8:29 AM (in response to hamsterdancer)Hi,
we have also used the jbpm 5.1 ant installer to install the jbpm console on the remote server (not localhost) and have unfortunately the same problem like described obove. I cannot believe that nobody here use jbpm.console installed on the remote server ;-)
Best regards
Tom
-
2. Re: Second login Screen on remote access
melc Aug 29, 2011 9:09 AM (in response to tomathome)1 of 1 people found this helpfulHello,
There is a number of steps you have to take in order to make the installation work on an address other than localhost and a port other than 8080.
Please take a look here,
-
3. Re: Second login Screen on remote access
hamsterdancer Sep 1, 2011 6:18 AM (in response to melc)Ah, thanks a lot. but this did not help.
I've changed the build.xml, ONE changeset.xml (I didn't find more of them), a lot of js files and even the jbpm.console.properties and jbpm-gwt-corexxxx.jar in the jbpm-gwt-console-server.war.
I did not find anywhere a drools.xml and if there are more than one changeset.xml I even did not find them:(
-
4. Re: Second login Screen on remote access
melc Sep 1, 2011 7:38 AM (in response to hamsterdancer)Hello,
You are right since jbpm5.1 drools.xml has been renamed to jbpm.xml and it is located in designer.war\profiles.
As for the changeset.xml indeed there is only one.
Finally you'll have to also fix the address and port in the two classes (org.drools.guvnor.server.contenthandler.BPMN2ProcessHandler,org.drools.guvnor.server.GuvnorAPIServlet) of guvnor, as metnioned in that thread.