Scenario 3 – External Nodes Communicate with Both IBM Connect:Direct Servers

This configuration uses the IBM® Connect:Direct®/Plex workload balancing capability. In this environment, both external nodes can communicate with either IBM Connect:Direct Server.

In this configuration, the network map of each Connect:Direct for UNIX node is changed to point to both IBM Connect:Direct Servers. However, because the IBM Connect:Direct/Plex normally is displayed as a single node to external systems, you must first create a unique node name for SERVER2. To create a unique node name, specify:

  • CDPLEX.SERVER.NODE = ZOS.CD2 in the SERVER2 local initialization parameters (callout 1)

    You do not need to specify the CDPLEX.SERVER.NODE initialization parameter for SERVER1 because it uses the local node (ZOS.CD).

  • USE.SERVER.NODE=YES in the IBM Connect:Direct/Plex network map adjacent node definitions (callout 2)

The ZOS.CD2 node name is then added to the external nodes' network maps (callouts 3 and 4).

The advantage of this configuration is that you can perform workload balancing on outgoing Processes from the IBM Connect:Direct/Plex. However, you cannot perform automatic workload balancing on Processes received from the external nodes; you must manually balance them by changing the SNODE.