Consider fixing the listener ports that you configured. You
complete this action in a different panel, but think about this action now.
Most endpoints are managed at a single location, which is why they do not
display in the Inbound transport panels. Managing end points at a single location
helps you decrease the number of conflicts in your configuration when you
assign the endpoints. The location for SSL end points is at each server. The
following port names are defined in the End points panel and are used for
Object Request Broker (ORB) security:
- CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS
- CSIv2 Client Authentication SSL Port
- CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS
- CSIv2 SSL Port
- SAS_SSL_SERVERAUTH_LISTENER_ADDRESS
- SAS SSL Port
- ORB_LISTENER_PORT
- TCP/IP Port
For an application server, click Servers > Application servers
> server_name. Under Communications, click Ports. The Ports
panel is displayed for the specified server.
For
a node agent, go to System administration > Node agents > node_name.
Under Additional properties, click Ports. The Ports panel for the node
agent and deployment manager already are fixed, but you might consider reassigning
the ports. For the deployment manager, click System Administration > Deployment
manager. Under Additional properties, click Ports.
The
Object Request Broker (ORB) on WebSphere Application Server uses a listener
port for Remote Method Invocation over the Internet Inter-ORB Protocol (RMI/IIOP)
communications, and is statically specified using configuration dialogs or
during migration. If you are working
with a firewall, you must specify a static port for the ORB listener and open
that port on the firewall so that communication can pass through the specified
port. The endPoint property for setting the ORB listener port is: ORB_LISTENER_ADDRESS.
In the WebSphere Application Server
Network Deployment environment, the ORB_LISTENER_ADDRESS end point is specified
on the node agent. The location service daemon resides on the node agent and
piggybacks onto the ORB listener port, which results in needing the port fixed.
Also, you must add the ORB_LISTENER_ADDRESS to the other application servers
to set their ORB listener port. Each ORB has a distinct listener port. In
WebSphere Application Server Network Deployment, you must specify a different
listener port. For example, you might specify the following ports:
- Node agent: ORB_LISTENER_ADDRESS=9000
- Server1: ORB_LISTENER_ADDRESS=9811
- Server2: ORB_LISTENER_ADDRESS=9812
Federated servers can
run without the node agent running. When ORB_LISTENER_ADDRESS is set to a
value of zero (0) or greater, the server does not depend on the location service
daemon to redirect connections to the server. When you set ORB_LISTENER_ADDRESS,
all object references in the namespace specify the connection to the server,
not the location service daemon. When the server is running without the node
agent, all applications must be accessed through the name server that runs
on the application server. The client must change the Java Naming Directory
Interface (JNDI) reference to use the host and port of the application server.
Table 1.
ORB_LISTENER_ADDRESS |
|
value = 0 |
The server starts on
any available port and does not use the location service daemon. |
value > 0 |
The server starts on
the port that is specified by the value you enter. The location service daemon
is not used. |
Note: Work load management might not work without the node agent running.
Complete
the following steps using the administrative console to specify the ORB_LISTENER_ADDRESS
port or ports.
Complete the
following steps for the node agent and the deployment manager.
- Click Servers > Application Servers > server_name.
Under Communications, click Ports > New.
- Select ORB_LISTENER_ADDRESS from the Port name field
in the Configuration panel.
- Enter the IP address, the fully qualified Domain Name System
(DNS) host name, or the DNS host name by itself in the Host field.
For example, if the host name is myhost, the fully qualified
DNS name can be myhost.myco.com and the IP address can be 155.123.88.201.
- Enter the port number in the Port field. The
port number specifies the port for which the service is configured to accept
client requests. The port value is used with the host name. Using the previous
example, the port number might be 9000.