Setting the connection to the WebSphere Application Server v6.x

You can use the SOAP connector (formerly known as Simple Object Access Protocol) or remote method invocation (RMI) to make JMX connections with the server. These ports are used for communication between the development environment and the server.

The RMI (ORB bootstrap) port is designed to improve performance and communication with the server.

The SOAP connector port is designed to be more firewall compatible. It is used by an HTTP transport for incoming SOAP requests.

Tip: If there is a firewall between the development environment and the server, use the SOAP connector port rather than the ORB bootstrap port.
To configure the server connection type and port number for WebSphere® Application Server v6.x:
  1. In the Servers view, double-click your WebSphere Application Server v6.x to open the server editor.
  2. Click the Overview tab.
  3. Expand the Server section.
  4. Under the Server connection type and admin port, use the radio button to select whether to use the RMI or SOAP connection as the communication channel between the development environment and the server. By default, the RMI radio button is enabled when working with a local server. If you are working with a remote server, the SOAP radio button is enabled by default.
  5. Specify the port number:
    1. For RMI connection, in the ORB bootstrap port field, type the port number. The default port number is 2809.
    2. For SOAP connection, in the SOAP connector port field, type the port number. The default port number is 8880.
    Tip: You can determine the port values of a configured profile by referencing its server configuration files. The port values are stored the in serverindex.xml file located in the following directory: x:\profiles\<profileName>\config\cells\<cellName>\nodes\<nodeName>, where x is the directory WebSphere Application Server is installed.
  6. Save and close the editor. When you save the modifications to the server editor, the server tools attempts to make a connection to the server using your latest saved changes.
Related reference
Problems publishing to a WebSphere Application Server Network Deployment v6.x
Related information
WebSphere Application Server maintenance releases

Feedback