Before you begin
Before configuring TCP/IP stack affinity for WebSphere Application Server for z/OS on a system with multiple stacks, you must:Why and when to perform this task
Setting up TCP/IP stack affinity can provide network isolation for one or more of your applications. For example, if you have multiple OSA Features, each one might connect your system to a different network. You can use the common INET physical file system (C_INET PFS) to assign a TCP/IP stack to each OSA Feature. This physical file system allows you to configure multiple physical file systems (network sockets) and make them active concurrently. To set up the common INET physical file system, specify common INET through the NETWORK DOMAINNAME parameter of SYS1.PARMLIB(BPXPRMxx).
If you plan to configure WebSphere Application Server for z/OS to use a non-default TCP/IP stack, consult z/OS UNIX System Services Planning, and z/OS Communications Server: IP Configuration Reference, for details.
Note:
To configure TCP/IP stack affinity for WebSphere Application Server for z/OS on a system with multiple TCP/IP stacks
Steps for this task
In the administrative console, click Environment > Manage WebSphere Variables > New.
Note: If you are setting this variable for the Daemon, you probably want to set it at the cell level to give all the Daemons in that cell the same setting. Unless one of the Daemons is serving multiple nodes, if for some reason you need to specify different settings for different Daemons in a cell, , you can set this variable at the node level.
Note: If you are setting this variable for the Daemon, you probably want to set it at the cell level to give all the Daemons in that cell the same setting. Unless one of the Daemons is serving multiple nodes, if for some reason you need to specify different settings for different Daemons in a cell, , you can set this variable at the node level.