4.3.1 Determining important ports

1. Navigate to the correct directory:

   • If you are using JBoss 4.2.1 when upgrading to LiveCycle ES3, 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/all/conf directory

   • If you are using JBoss 5.1 when upgrading to LiveCycle ES3, 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.

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.

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