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. However, the following differences between the two protocols exist:
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
You complete this action in a different panel, but this is the time to think about it. Most end points are managed at a single location, which is why they do not appear 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 end points. 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:
For an application server, click Servers > Application Servers > server_name. Under Additional Properties, click End Points. The End Points panel is displayed for the specified server.
For an application server, click Servers > Application Servers > server_name > End Points.
For a node agent, go to System Administration > Node Agents > node_name. Under Additional Properties, click End Points. The end points 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 End Points.
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 end point 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 (LSD) resides on the node agent and piggybacks onto the ORB listener port, which results in the need to have 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:
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.
Results
The inbound transport configuration is complete.Example
What to do next
When you finish configuring security, perform the following steps to save, synchronize, and restart the servers: