Running multiple TCP/IP stacks on the same system
By assigning a TCP/IP stack to an integration node, you can run multiple TCP/IP stacks on the same system to provide network isolation for one or more integration nodes.
Before you begin
C_INET PFS. You can then use the file system to set up multiple TCP/IP stacks. The physical file system enables you to configure multiple physical file systems, or network sockets, and make them active concurrently.
About this task
You must establish the stack affinity between the integration node and the TCP/IP stack. Establishing stack affinity binds all socket communications to the stack and allocates correct host name resolution configuration data sets to IBM® Integration Bus. The data sets enable host name lookups to be resolved correctly.
Establish the stack affinity of the integration node to the required TCP/IP stack.
Set the following option in the component profile. The component profile is BIPBPROF for an integration node:
Submit BIPGEN to recreate the integration node
- Restart the integration node for the updates to take effect.
- Set the following option in the component profile. The component profile is BIPBPROF for an integration node:
You can configure the data set for the host name resolution of each integration node.
For more information about the
RESOLVER_CONFIGvariable in the component profile. The component profile is BIPBPROF for an integration node. The
RESOLVER_CONFIGvariable can specify an appropriate MVS™ data set or a z/OS® UNIX file, for example, /etc/resolv.conf
BIPGENto re-create the integration node
- Restart the integration node to enable the change to take effect.
RESOLVER_CONFIGoption, see the z/OS Communications Server IP Configuration Reference in the z/OS product documentation.
- Set the