15.5. Appendix E: Changing the JBoss HTTP Port

This section provides instructions for changing the JBoss HTTP port. This content applies to single-node EKM servers that do not use a front-end webserver. In this configuration, clients connect directly to the HTTP port of JBoss to access EKM.

For instructions on changing the HTTP port of a front-end web server, refer to Installing a Front-End Web Server.

By default, JBoss listens on port 8080/TCP for incoming HTTP connections. However, it is sometimes necessary or desired to change this to another port, such as 80/TCP. To change the HTTP port, follow the instructions in this section.


Note:  On Linux systems, ports below 1024 are called “privileged ports.” Root privileges are required for a program to open these ports. Windows does not enforce this restriction.

Some firewalls and security products may process or alter traffic whose destination port is port 80 (HTTP) in ways that may cause EKM to function incorrectly. If you decide to configure the EKM server, or a front-end web server connected to the EKM server, to listen on port 80 and experience difficulties using the EKM server, it may be necessary to configure the EKM server or front-end web server to use another port, such as 8080.


To change the HTTP port under JBoss, follow these steps:

  1. On each EKM cluster node, stop the EKM server.

  2. Edit the JBoss domain configuration (see JBoss Domain Mode and Configuration).

  3. Find the socket-binding-groups configuration element:

    <socket-binding-groups>
    
  4. Find the socket-binding-group element whose name is ha-sockets:

    <socket-binding-group name="ha-sockets" default-interface="public">
  5. Find the socket-binding child element whose name is http:

    <socket-binding name="http" port="${jboss.http.port:8080}"/>
  6. Modify the port number (8080), shown above in bold, to change the value to the desired port number.


    Note:  The HTTP port number set here is adjusted by the port offset as described in Appendix D: Resolving Network Port Conflicts.


  7. Edit EKM_HOME/conf/ekm.xml and update the value of ekmUrl (shown in bold) to the new URL for EKM:

     <ekmUrl>http://ekm.mycompany.com:8080/ekm</ekmUrl>

    Old URL: http://ekm.mycompany.com:8080/ekm

    New URL: http://ekm.mycompany.com:NNNN/ekm

    where NNNN is the new EKM server HTTP port.

  8. On each EKM cluster node, start the EKM server.

  9. Refer to Appendix I: Updating EKM Server Objects and update any server objects in EKM workspaces on remote EKM servers that refer to this EKM server.


Release 18.2 - © ANSYS, Inc. All rights reserved.