4.3.1 Determining important ports

Note the JNDI port number for your application server (JBoss, WebLogic, or WebSphere) and listener port for your database instance, which you plan to use for upgrading to LiveCycle ES4.

If you are not sure which ports the database uses, contact your database administrator.

4.3.1.1 JBoss:

  1. Navigate to the correct directory:

    • When upgrading to LiveCycle ES4 for JBoss, navigate to the right folder:

      • If using JBoss Turnkey, navigate to the [appserver root]/server/lc_turnkey/conf directory

      • If using Adobe pre-configured JBoss, navigate to the [appserver root]/server/lc_<database type>/conf directory

      • If using JBoss downloaded from internet, navigate to the [appserver root]/server/standard/conf directory

  2. Open the jboss-service.xml file.

  3. Find the <mbean code="org.jboss.naming.NamingService"> element. The JNDI server port is the value of the <attribute name="Port"> element.

4.3.1.2 WebSphere

  1. Log in to the WebSphere Administrative Console.

  2. In the navigation tree, click Servers > Server Types > WebSphere application servers.

  3. On the right pane, click the server name.

  4. Under Communications, click Ports , and find the value of BOOTSTRAP_ADDRESS.

4.3.1.3 WebLogic

For WebLogic, the JNDI server port is usually the same as the http port for the server that is created to host LiveCycle ES4. If a Managed Server is configured for deployment of LiveCycle ES4, the JNDI port should be same as the http port used by the Managed Server.

// Ethnio survey code removed