Solution ID: prim84076
How to change default ports for Jboss 5.0.1.GA
Status: Reviewed
Version(s): 7.0

Problem: How to change default ports for Jboss 5.0.1.GA.
Problem: How to run P6 v7 Progress Reporter and Web application on Jboss 5.1.0.GA.
Problem: Port conflicts when running  P6 v7 Standalone / Progress Reporter / P6 Web Access application on same machine with Jboss 5.1.0.GA.
Cause:

New installations for P6v7 Standalone use Oracle XE which has an administration page that uses port 8080.
Applications deployed on JBOSS use a default configuration of HTTP port 8080, as well as other port configurations listed below.


Running a combination of any 2  or more of the following causes a port conflict if the default port configurations are not changed for the JBOSS deployed application:


  • P6v7 Standalone on Oracle XE

  • Progress Reporter deployed on JBOSS

  • P6 Web Access deployed on JBOSS
Fix:

Both web servers have port configuration information stored within files called bindings.xml and server.xml.


  1. Stop both the Progress Reporter and the P6 v7 Web Application Services.


  2. Locate the bindings.xml file to be changed.

    NOTE:
      Changing either server is acceptable.

    Default file location for Progress Reporter:
    <Install Drive>\jboss-5.0.1.GA\server\pr\conf\bootstrap\bindings.xml
    Default file location for P6 v7 Web Access: <Install Drive>\jboss-5.0.1.GA\server\primaveraweb\conf\bootstrap\bindings.xml


  3. Ensure the file is not read-only, open with Notepad.


  4. Change the port numbers for the following eight areas:


    Remote classloading service


    Change port 8083 to an available port.

    For Example:

    <!– Remote classloading service –>
    <bean class=”org.jboss.services.binding.ServiceBindingMetadata”>
       <property name=”serviceName”>jboss:service=WebService</property>
       <property name=”port”>8084</property>
    </bean>


    RMI/JRMP invoker


    Change port 4444 to an available port.

    For Example:

    <!– RMI/JRMP invoker –>
    <bean class=”org.jboss.services.binding.ServiceBindingMetadata”>
       <property name=”serviceName”>jboss:service=invoker,type=jrmp</property>
       <property name=”port”>4454</property>
    </bean>


    Pooled invoker


    Change port 4445 to an available port.

    For Example:

    <!– Pooled invoker –>
    <bean class=”org.jboss.services.binding.ServiceBindingMetadata”>
       <property name=”serviceName”>jboss:service=invoker,type=pooled</property>
       <property name=”port”>4455</property>
    </bean>


    Naming Service


    Change ports 1098 and 1099 to available ports.

    For Example:

    <!– Naming Service –>
    <bean class=”org.jboss.services.binding.ServiceBindingMetadata”>
       <property name=”serviceName”>jboss:service=Naming</property>
       <property name=”bindingName”>Port</property>
       <property name=”port”>10990</property>
    </bean>

    <bean class=”org.jboss.services.binding.ServiceBindingMetadata”>
       <property name=”serviceName”>jboss:service=Naming</property>
       <property name=”bindingName”>RmiPort</property>
       <property name=”port”>10980</property>
    </bean>


    deploy/jmx-remoting.sar 

    Change port 1090 to an available port.

    For Example:

    <!– ********************* deploy/jmx-remoting.sar **************** –>

    <bean class=”org.jboss.services.binding.ServiceBindingMetadata”>
       <property name=”serviceName”>jboss.remoting:service=JMXConnectorServer,protocol=rmi</property>
       <property name=”port”>10900</property>
    </bean>
     


    Standard JBM bisocket connector

    Change port 4457 to an available port.

    For Example:
        

    <!– Standard JBM bisocket connector –>
    <bean class=”org.jboss.services.binding.ServiceBindingMetadata”>
       <property name=”serviceName”>jboss.messaging:service=Connector,transport=bisocket</property>
       <property name=”port”>4458</property>
    </bean>


    JBossTS Recovery Manager
     

    Change port 4712 to an available port.

    For Example:
        

    <!– JBossTS Recovery Manager –>
    <bean class=”org.jboss.services.binding.ServiceBindingMetadata”>
       <property name=”serviceName”>TransactionManager</property>
       <property name=”bindingName”>recoveryManager</property>
       <property name=”port”>4715</property>
    </bean>


    JBossTS Transaction Status Manager

    Change port 4713 to an available port.

    For Example:
        

    <!– JBossTS Transaction Status Manager –>
    <bean class=”org.jboss.services.binding.ServiceBindingMetadata”>
       <property name=”serviceName”>TransactionManager</property>
       <property name=”bindingName”>transactionStatusManager</property>
       <property name=”port”>4714</property>
    </bean>
     
     
  5. Save all changes and close the bindings.xml file.


  6. Locate the server.xml file to be changed.  

    NOTE:
      Changing either server is acceptable.

    Default file location for Progress Reporter:
    <Install Drive>\jboss-5.0.1.GA\server\pr\deploy\jbossweb.sar\server.xml
    Default file location for P6 v7 Web Access: <Install Drive>\jboss-5.0.1.GA\server\primaveraweb\deploy\jbossweb.sar\server.xml


  7. Change the port number in the following location:
    NOTE:  If P6 v7 standalone installation is present on the machine port 8080 will need to be changed so as not to conflict with the Oracle XE admin console url.
    A HTTP/1.1 Connector on port 8080

    Change port 8080 to an available port.

    Example:

    <!– A HTTP/1.1 Connector on port 8080 –>
          <Connector protocol=”HTTP/1.1″ port=”8181” address=”${jboss.bind.address}”
                   connectionTimeout=”20000″ redirectPort=”8443″ />


    A AJP 1.3 Connector on port 8009

    Change port 8009 to an available port.

    Example:

    <!– A AJP 1.3 Connector on port 8019 –>
    <Connector protocol=”AJP/1.3″ port=”8019” address=”${jboss.bind.address}”
       redirectPort=”8443″ />
     

  8. Save the change and close the server.xml file, close Notepad.


  9. Restart both the Progress Reporter and the P6 Web Services.

    NOTE:
      The order in which the services are started are irrelevant.