Session Establishment and Process Recovery
Sterling B2B Integrator provides several parameters that allow you to customize features that govern how many sessions it establishes for a Connect:Direct Server Adapter node and remote Sterling Connect:Direct® nodes and how it performs retry processing in the case of a failed or interrupted file transfer.
How Sessions for Business Processes Are Established Sterling Connect:Direct servers and the Sterling Connect:Direct Server Adapter, you configure those components in Sterling B2B Integrator so that it knows who it will be communicating with. One of the required parameters you define for both Sterling Connect:Direct nodes and the Connect:Direct Server Adapter is the maximum number of locally initiated sessions the Connect:Direct Server Adapter may have active at any point in time. This parameter, Max locally initiated (pnode) sessions allowed, determines the maximum number of sessions available for establishing and re-establishing sessions, and plays a key role when business processes are suspended and resumed. If this value is also specified at the remote node-level, the effective session limit is the smaller of two values: the limit for the adapter and the session limit for the remote node.How Checkpoint Restart and Retry Processing Works Purging Checkpoint Data Sterling B2B Integrator stores checkpoint information for 30 days, after which it is automatically purged. If your database has been corrupted, you must purge this checkpoint information by performing a cold restart. To purge all checkpoint data, each Connect:Direct Server Adapter must be cold started.How File Allocation Retry Processing Works Sterling Connect:Direct for z/OS® system. FAR processing only affects locally initiated (PNODE) sessions that use the Connect:Direct Server CopyTo service or CopyFrom service.Enabling File Allocation Retry Processing Shared Session Limits Sterling Connect:Direct Server Adapters.