So yesterday I wrote about installing 2 versions of LiveCycle ES, but with the limitation that you can’t run them simultaneously. I didn’t really intend to try to run them simultaneously because I thought it would be a lot of work, but it did feel unfinished and that kept nagging. So a little over an hour ago I decided to give it a shot anyway. Not the way you are supposed to do it, but using a brute force approach. The first step was using “netstat -ano” to register all the ports in use by the JBoss and MySQL processes. After filtering that produced the following list:
Active Connections Proto Local Address Foreign Address State PID TCP 0.0.0.0:1098 0.0.0.0:0 LISTENING 1032 TCP 0.0.0.0:1099 0.0.0.0:0 LISTENING 1032 TCP 0.0.0.0:1100 0.0.0.0:0 LISTENING 1032 TCP 0.0.0.0:1101 0.0.0.0:0 LISTENING 1032 TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING 2392 TCP 0.0.0.0:3528 0.0.0.0:0 LISTENING 1032 TCP 0.0.0.0:4444 0.0.0.0:0 LISTENING 1032 TCP 0.0.0.0:4445 0.0.0.0:0 LISTENING 1032 TCP 0.0.0.0:4446 0.0.0.0:0 LISTENING 1032 TCP 0.0.0.0:4447 0.0.0.0:0 LISTENING 1032 TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING 1032 TCP 0.0.0.0:8083 0.0.0.0:0 LISTENING 1032 TCP 0.0.0.0:8093 0.0.0.0:0 LISTENING 1032 TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING 1032 UDP 0.0.0.0:1161 *:* 1032 UDP 0.0.0.0:1162 *:* 1032 UDP 192.168.0.121:1496 *:* 1032 UDP 192.168.0.121:1498 *:* 1032 UDP 192.168.0.121:1501 *:* 1032 |
The next step was a search of all the configuration files to find all occurences of these port numbers. All the configuration files means everything with the extensions .properties, .xml and .ini in all the subfolders of “c:\Adobe\LiveCycle8.3\jboss\” and “c:\Adobe\LiveCycle8.3\mysql\”. I did some fuzzy selection on which of these files were really relevant and changed the port numbers to a number exactly 1000 higher in the following files:
C:\Adobe\LiveCycle8.2\jboss\server\all\conf\jacorb.properties C:\Adobe\LiveCycle8.2\jboss\server\all\conf\jboss-minimal.xml C:\Adobe\LiveCycle8.2\jboss\server\all\conf\jboss-service.xml C:\Adobe\LiveCycle8.2\jboss\server\all\deploy\cluster-service.xml C:\Adobe\LiveCycle8.2\jboss\server\all\deploy\httpha-invoker.sar\META-INF\jboss-service.xml C:\Adobe\LiveCycle8.2\jboss\server\all\deploy\jboss-ws4ee.sar\META-INF\jboss-service.xml C:\Adobe\LiveCycle8.2\jboss\server\all\deploy\jbossweb-tomcat55.sar\server.xml C:\Adobe\LiveCycle8.2\jboss\server\all\deploy\jms\hajndi-jms-ds.xml C:\Adobe\LiveCycle8.2\jboss\server\all\deploy\juddi-service.sar\juddiws.war\WEB-INF\juddi.properties C:\Adobe\LiveCycle8.2\jboss\server\all\deploy\snmp-adaptor.sar\META-INF\jboss-service.xml C:\Adobe\LiveCycle8.2\jboss\server\all\deploy-hasingleton\jms\uil2-service.xml C:\Adobe\LiveCycle8.2\jboss\server\all\deploy\adobe-ds.xml C:\Adobe\LiveCycle8.2\jboss\server\all\deploy\mysql-ds.xml C:\Adobe\LiveCycle8.2\mysql\my.ini |
This appears to work (for some value of work). Anytime now I will get an alarm because the system overheated and imploded (it has only 2 GB of RAM), but the server started, the server.log is clean and I am logged on to both the LiveCycle 8 Admin on port 8080 and the LiveCycle 8.2 Admin on port 9080.So as long as you’re willing to bypass all the rules on how it should be done and just go for the brute force approach it appears to be pretty easy to run 2 versions of LiveCycle ES simultaneously.