Creating Sterling Connect:Direct Nodes

Create a Sterling Connect:Direct® node definition for each remote Sterling Connect:Direct node that communicates with the Sterling Connect:Direct Server Adapter. This is only required for nodes you plan to connect to and for nodes that connect to the Sterling Connect:Direct Server Adapter when you have netmap checking enabled.

Use the following procedure to create a new Sterling Connect:Direct node:

  1. From the Administration menu, select Deployment > Adapter Utilities > C:D Netmaps > C:D Nodes.
  2. In the Create Nodes pane, click Go!. The Create Nodes page appears.
    Field Value to Enter Description
    Connect:Direct Server Node Name Type the node name for the Sterling Connect:Direct server. Name that will be used to identify the Sterling Connect:Direct server. Required.
    Connect:Direct Server Host Type the host name or IP address for the Sterling Connect:Direct server. host name—Host name associated with the IP address. For example:

    host01 (where host01 is a machine on the local domain)

    host01.proddomain.com (fully-qualified host name)

    nnn.nnn.nnn.nnn or

    nnnn:nnnn:nnnn:nnnn:nnnn:nnnn:nnnn:nnnn—IP

    address of a machine running Sterling Connect:Direct.

    IPV6 is supported for Sterling Connect:Direct for UNIX 4.0 and Sterling Connect:Direct for Microsoft Windows 4.4 or later.

    Required.
    Connect:Direct Port Type the host port number for the Sterling Connect:Direct server. TCP/IP port number that Sterling Connect:Direct monitors for requests from remote nodes. Required.
    Note: If Sterling B2B Integrator is installed on a UNIX operating system, do not select ports in the range 1-1024. These are normally reserved by the operating system.
    Max locally initiated (pnode) sessions allowed During testing, set this value to 100 so that you do not run out of sessions.

    After testing, enter the estimated number of sessions you require. Otherwise, accept the default value of 5.

    		 Maximum number of sessions initiated locally by the Sterling Connect:Direct Server Adapter that may be active at any time. Optional. If omitted, the value defined by the Sterling Connect:Direct Server Adapter is used.

    This setting overrides the Max locally initiated (pnode) sessions allowed setting in the Sterling Connect:Direct Server Adapter configuration.

    Valid value: Any number up to 9999. Minimum value is 1. Default is 5.

    For more information on session limits, see How Sessions for Business Processes Are Established.
    Max remotely initiated (snode) sessions allowed During testing, set this value to 100 so that you do not run out of sessions.

    After testing, enter the estimated number of sessions you require. Otherwise, accept the default value of 5.

    		 Maximum number of sessions initiated by the remote node that may be active at any point of time. If omitted, the value defined by the Sterling Connect:Direct Server Adapter is used.

    This setting overrides the Max remotely initiated (snode) sessions allowed setting in the Sterling Connect:Direct Server Adapter configuration.

    Valid value: Any number up to 9999. Minimum value is 1. Default is 5.
    Alternate Comm Info Leave this blank unless the inbound Sterling Connect:Direct node has more than one outgoing IP address.

    If the inbound Sterling Connect:Direct node has more than one outgoing IP address, specify the IP addresses or host names in a comma-delimited list as shown in the Description.

    		 Provides support for establishing netmap-checked sessions with high-availability (especially load balancing) systems with multiple IP addresses, such as Sterling Connect:Direct/Plex for z/OS. Use this parameter to list all IP addresses or host names that are part of the multiple IP address environment.

    For Sterling Connect:Direct/Plex, this list should include the address of each Sterling Connect:Direct/Server with a different IP address from the Sterling Connect:Direct/Plex Manager.

    If a remote node has more than one outgoing IP address (as in a load balancing environment), specify all of the remote node's possible outgoing addresses in the Alternate Comm Info field so that those outgoing IP addresses are contained in the local node's netmap entry for that remote node. This configuration allows netmap checking to succeed when the remote node connects to the local node using any of the possible outgoing IP addresses specified.

    Valid format: hostname1/IP address, hostname2/IP address, hostname3/IP address (maximum length is 2048 characters)

    host name—Host name associated with the IP address. For example:

    host01 (where host01 is a machine on the local domain)

    host01.proddomain.com (fully-qualified host name)

    nnn.nnn.nnn.nnn or

    nnnn:nnnn:nnnn:nnnn:nnnn:nnnn:nnnn:nnnn—IP

    address of a machine running Sterling Connect:Direct

    IPV6 is supported for Sterling Connect:Direct for UNIX 4.0 and Sterling Connect:Direct for Microsoft Windows 4.4 or later.
    Secure+ Option Accept the default setting (Disabled) until you start using Sterling Connect:Direct Secure Plus.

    Files are not encrypted during copy operations.

    		 Valid if Netmap Override=Yes at the Connect:Direct Server Adapter. Indicate if you want to disable or enable encryption. Required.

    Valid values are:

    • Disabled (default)
    • Enabled
  3. Click Next. The Confirm page appears.
  4. Review your configuration settings and click Finish.