Hi, I've downloaded the jbpm-5.3.0.Final-installer-full.zip and have got it working fine on my localhost.
I'm now trying to deploy it on an Amazon EC2 Centos instance and having no end of problems. Amazon EC2 is a NAT'd server, so the actual IP on the server is different to the IP accessible from the Internet.
I'm trying to get the JBPM-console working correctly. I can see the console and launch processes, but tasks never arrive for the users. Keep getting stack traces which I can share if required.
So, the things I've tried on the Final installer are:
1) Modify build.xml so that the bind address is the NAT'd IP address on the server's primary interface.
2) In standalone.xml I've changed the management and public addresses from localhost to 0.0.0.0 (Listen on all interfaces)
3) Then 'ant install.demo' to push the changes
It is now accessible from the Internet and I can access drools-guvnor, jbpm-console etc.
Here are the listening ports:
[root@myinst2 data]# lsof -i -Pn|grep java|grep -i listen
java 29475 root 7r IPv4 1416067 0t0 TCP *:9092 (LISTEN)
java 29536 root 161u IPv4 1416083 0t0 TCP *:9999 (LISTEN)
java 29536 root 163u IPv4 1416084 0t0 TCP 10.240.217.46:8080 (LISTEN)
java 29536 root 166u IPv4 1416085 0t0 TCP *:9990 (LISTEN)
java 29536 root 170u IPv4 1416087 0t0 TCP *:1090 (LISTEN)
java 29536 root 171u IPv4 1416088 0t0 TCP *:1091 (LISTEN)
java 29536 root 799u IPv4 1416111 0t0 TCP 127.0.0.1:5445 (LISTEN)
So what is the subtle difference between having a working JBPM-console on localhost vs live on the Internet?
I tried modifying the war file for the jbpm-console as advised here: http://docs.jboss.org/jbpm/v5.3/userguide/ch.console.html#d0e4624 but then JBPM-console wouldn't even start. All I did was add the NAT'd IP address for bpm.console.server.host=<NAT IP address> in WEB-INF/classes/jbpm.console.properties.
Any advice on how to deploy JBPM 5.3 on a Cloud server (using NAT - like they all do) would be appreciated.
Geoff.