The Comm. Bridge TCP/IP implementation makes use of stream sockets. A stream socket provides a full-duplex, sequenced, reliable transmission mechanism, over which a cooperative flow request can be transmitted. The socket provides the TCP communications endpoint used to gain access to the IP network.
A target server environment that is connected to the IP network listens for inbound connections and data transmissions using a socket that is located on the system hosting the target server.
Used by the Comm. Bridge, a socket consists of two parts, each defining application endpoints in the TCP communications. One of the application endpoints is the local application (that is, the Comm. Bridge). The other endpoint is the remote application. That is, the TCP front-end process of the target server environment. Examples include the Transaction Enabler AEFUF, Tuxedo Proxy Client, z/OS CICS Socket Listener or z/OS IMS Direct Connect, EJB Converter Service. These application endpoints are also referred to as the source and destination, respectively.
Each connection that a client TCP application establishes on a workstation is identified by its unique TCP port address. When a connection to a target server is requested, the source port address is selected by TCP from those port numbers not already in use by other TCP connections. The destination port address is the target server environment's well-known port address. The IP address of the target machines, along with its port address, is used by the Comm. Bridge in the construction of the destination portion of the TCP socket.
The Comm Bridge uses a system level socket support API to obtain all available IP addresses for the target server host machine. The Comm Bridge server connection subsystem will then iterate through all available IP addresses until a valid connection is made. The ordering of the reported IP addresses is determined by the Comm Bridge's host operating system configuration.
The Comm Bridge makes no attempt to prefer IPv4 connections over IPv6 or vice versa. The IP addresses are iterated through in the order received from the underlying operating system.
No special user interaction is required at the Comm Bridge to enable this support.
To configure a Comm. Bridge to communicate with a TCP/IP server environment you need:
The network address associated with the machine name of the target server environment can be resolved using either the workstation hosts file or by way of a Domain Name Services (DNS).
To modify the hosts' file or the DNS configuration on the client workstation, see the appropriate vendor documentation for instructions on using hosts file or DNS setup.
|
Copyright © 2013 CA.
All rights reserved.
|
|