Before you begin
Inbound transports refer to the types of listener ports and their attributes that are opened to receive requests for this server. Both Common Secure Interoperability Specification, Version 2 (CSIv2) and Secure Authentication Service (SAS) have the ability to configure the transport.
Why and when to perform this task
Complete the following steps to configure the Inbound transport panels in the administrative console:Steps for this task
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, which is generally not specified and selected dynamically during run time. 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.
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. |
Complete the following steps using the administrative console to specify the ORB_LISTENER_ADDRESS port or ports.
In the WebSphere Application Server Network Deployment environment, complete the following steps for the node agent and the deployment manager.
Result
The inbound transport configuration is complete. With this configuration, you can configure a different transport for inbound security versus outbound security. For example, if the application server is the first server that is used by users, the security configuration might be more secure. When requests go to back-end enterprise bean servers, you might lessen the security for performance reasons when you go outbound. With this flexibility you can design the right transport infrastructure to meet your needs.What to do next
When you finish configuring security, perform the following steps to save, synchronize, and restart the servers: