JBoss/Tomcat HTTP Port Change and LiveCycle Content Services ES2

Many system administrators change the port on which JBoss/Tomcat listens for HTTP requests from 8080 to 80. This makes LiveCycle URLs simpler because if the server listens on port 80, you don’t have to specify that to the browser.

However, a manual change has to be made for Content Services ES. Otherwise, you will get the following error messages in the server log:

ERROR [WSClient] ALC-CSV-001-000-Checking Server status at http://10.20.50.40:8080/contentspace/faces/jsp/login.jsp
INFO [HttpMethodDirector] I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect
INFO [HttpMethodDirector] Retrying request

1) Login to the LiveCycle AdminUI, and navigate to Services->Applications and Services->Service Management
2) Filter on the ‘Content Services’ category
3) Click on Document Management Service
4) In the Configuration tab, change HTTP Port to 80 (or whatever port JBoss/Tomcat is configured to listen on) and save.
5) Re-start JBoss
6) After re-start, login to the LiveCycle AdminUI and navigate to Services->LiveCycle ContentServices ES2 and make sure that the page loads. In the server log, you should see entries such as these:

ERROR [WSClient] ALC-CSV-001-000-Checking Server status at http://10.20.50.40:80/contentspace/faces/jsp/login.jsp
ERROR [WSClient] ALC-CSV-001-000-Query server at http://10.20.50.40:80/contentspace/faces/jsp/login.jsp is successful

Please ignore the ‘ERROR’ designation – it is a known problem which is being fixed.