Configuring a Sterling Connect:Direct Server Adapter

The Sterling Connect:Direct® Server Adapter can function as either the PNODE, SNODE, or both, in the Sterling Connect:Direct network, initiating and responding to Sterling Connect:Direct transfer requests. Configuring a Connect:Direct Server Adapter is similar to configuring a Sterling Connect:Direct server.

1. From the Deployment menu, select Services > Configuration.
2. Click Go in the Create New Service pane.
3. In the Service Type box, type Connect:Direct Server Adapter and click Next.
4. Configure the following fields for this scenario. Accept default values for all other fields.
   Note: To enable session establishment retry processing, the value specified for either the number of long-term or short-term retry attempts must be greater than 0. Both of these adapter-level settings can be overridden by values specified for in the Connect:Direct Server Begin Session service for a particular business process.

   To enable copy restart processing, session establishment retry processing must be enabled. You must also configure the Checkpoint Interval in the Connect:Direct Server Adapter CopyTo or CopyFrom service in your business process. For additional information, see How Checkpoint Restart and Retry Processing Works.

   Note: When you configure how you want retry processing to work, note that the short-term retry interval is configured in seconds rather than in minutes used for the long-term retry interval. For additional information, see How Checkpoint Restart and Retry Processing Works.

   Field	Value to Enter	Description
   Name	Type a unique name for the Connect:Direct Server Adapter configuration.	Required. Note: Name is the adapter name, not the node name. However, in Sterling B2B Integrator business processes, Name is the CDLocalNodeName. To avoid confusion, use the same value for both Name and Connect:Direct Server Node Name in your Connect:Direct Server Adapter configuration.
   Description	Type a description for the Connect:Direct Server Adapter configuration.	Required
   Connect:Direct Server Node Name	Type the node name to use to identify this Connect:Direct Server Adapter. Best practice is to use the same value as the Name field.	Maximum 16 characters. This node name must match the Connect:Direct netmap entry for the Connect:Direct Server Adapter. Required.
   Connect:Direct Server Port	Type the listening port number for the Connect:Direct Server Adapter. Make sure you select a port number that is not in use by another application.	TCP/IP port number that Connect:Direct Server Adapter monitors for requests from remote nodes. Required. Note: If your application 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, you may want to set this value to a high number, such as 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. If you need to specify session limits for each node, set this value at the highest anticipated number of total, locally initiated sessions and then specify node limits in the netmap.	Maximum number of sessions initiated locally by the Connect:Direct Server Adapter that may be active at any point in time. Required. May be overridden at the node level. If a node-level value is configured, the effective session limit is the smaller of two values: the limit for the adapter and the session limit for the remote node. Valid value: Any number through 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, you may want to set this value to a high number, such as 100, so that you do not run out of sessions. After testing, enter the estimated number of sessions you required. Otherwise, accept the default value of 5. If you need to specify session limits for each node, set this value at the highest anticipated number of total, remotely initiated sessions and then specify node limits in the netmap.	Maximum number of sessions initiated by all remote nodes that may be active at any point in time. Required. May be overridden at the node level. If a node-level value is configured, the effective session limit is the smaller of two values: the limit for the adapter and the session limit for the remote node. Valid value: Any number through 9999. Minimum value is 1. Default is 5.
   NetMap Check	For testing purposes, you may find it convenient to select the default (No). After testing, select the value that best serves your network security requirements.	Whether the node netmap should be checked to authorize sessions. Required values are: Check both node name and IP address—Searches the Connect:Direct Server Adapter network map for an entry corresponding to the node name of the remote client. If one exists, the IP address is obtained and compared to the IP address of the remote node making the request. Check node name only—Searches the Connect:Direct Server Adapter network map for an entry corresponding to the node name of the remote client. No (default)—Disables netmap validation.
   Number of short-term session retry attempts	Valid value: Any number up through 9999. Default is 0. Required. Retry activity is logged (if logging enabled). For more information on retry processing, see Session Establishment and Process Recovery.	Specifies the maximum number of short-term attempts for creating a session with a Sterling Connect:Direct node or for re-establishing a session after a session failure during COPY processing (both CopyTo and CopyFrom). This setting can be overridden by the value specified for ShortTermMaxRetries in the Connect:Direct Server Begin Session service. Note: The counter for the number of short-term session retry attempts is reset to zero when a session is successfully reestablished.
   Interval between short-term session attempts (seconds)	Valid value: Any number through 99999999. Default is 5. Required.	Specifies the amount of time, in seconds, to wait between short-term session establishment and re-establishment attempts. This setting can be overridden by the value specified for ShortTermRetryInterval in the Connect Direct Server Begin Session service. This parameter performs successive retries within a shorter period of time than is available with the Interval between session establishment attempts (minutes) settings.
   Number of long-term session retry attempts	Valid value: Any number up to 9999. Default is 0. Required. Retry activity is logged (if logging enabled).	Specifies the maximum number of long-term attempts for creating a session with a Sterling Connect:Direct node or for re-establishing a session after a session failure during COPY processing (both CopyTo and CopyFrom). This setting can be overridden by the value specified for BeginSessionMaxRetries in the Connect:Direct Server Begin Session service. Note: The counter for the number of long-term session retry attempts is reset to zero when a session is successfully reestablished.
   Interval between long-term session attempts (minutes)	Any number through 99999999. Required. Default is 1.	Specifies the time, in minutes, to wait between long-term session establishment and re-establishment attempts. This setting can be overridden by the value specified for BeginSessionRetryInterval in the Connect Direct Server Begin Session service.
   Encryption using Secure+	Select the default setting (Disabled) until you start using Sterling Connect:Direct Secure Plus.	Whether Sterling Connect:Direct Secure Plus is enabled. Required. Valid values are Enabled and Disabled. Default is Disabled. Sterling Connect:Direct Secure Plus must be installed on your system. In addition, you must have the required certificates for implementing Sterling Connect:Direct Secure Plus. For information, see the Sterling Connect:Direct documentation for the platform you are using.
   C:D Netmap Name	Select the netmap name you created in Creating Sterling Connect:Direct Netmaps .

5. When you configure how you want retry processing to work, note that the short-term retry interval is configured in seconds rather than in minutes used for the long-term retry interval. For additional information, see How Checkpoint Restart and Retry Processing Works.
   This will complete the Connect:Direct Server Adapter configuration and start the adapter.