Shared Session Limits

Edit online

The Shared Session Limits (SHSL) feature manages all session activity within a group of Sterling Connect:Direct® Server Adapters.

Before SHSL, session activity was maintained privately within each Connect:Direct Server Adapter. Without a single, central bookkeeping authority, session accounting accuracy was almost impossible to achieve for a group.

With SHSL, session bookkeeping is centrally managed and shared between Connect:Direct Server Adapters participating within the same group. This feature enables accurate session accounting because all group participants use a single set of session counters.

Guidelines

Follow these guidelines to take full advantage of SHSL:

  • SHSL is enabled by default in Sterling B2B Integrator. You do not have configure SHSL.
  • Since each Connect:Direct Server Adapter is configured independently, care must be taken to ensure that every Connect:Direct Server Adapter participating in the group is configured with identical session limits. For example, each Connect:Direct Server Adapter must define the same pnode session limit and the same snode session limit.

    If the configuration is inconsistent, the group’s limits are defined by the configuration of the final member of the group to start. For example, if two Connect:Direct Server Adapters belong to a group and one Connect:Direct Server Adapter defines the pnode session limit to be 10 and the other Connect:Direct Server Adapter defines it to be 5, if the second adapter is the final adapter in the group to start, the group’s pnode session limit is 5.

    It is also good practice to configure each Connect:Direct Server Adapter participating in a group with the same Netmap. This practice ensures that each Connect:Direct Server Adapter in the group uses the same session limits that are defined in the remote node's configuration.

    Attention: As with all configuration changes to a Connect:Direct Server Adapter Netmap (for example, remote Node definitions or additions and deletions from a Netmap), all Connect:Direct Server Adapters that reference the Netmap must have their configuration refreshed. For example, you can refresh a configuration by one of the following actions:
    • From v5.2.6 and later versions, configuration is automatically refreshed throughout the GROUP of CDSAs and their shared Netmap by saving the configuration while editing a CDSA, Node, Netmap or Netmap-XREF.
    • Prior to v5.2.6, all configuration must be manually refreshed. For example, if a Node configuration is changed, the REFRESH operational steps (EDIT/SAVE/FINISH) must be performed on all CDSAs that share the Netmap that contains the Node. This also applies to changes made to add or remove Nodes from a Netmap.

Recovery from system failure

If a system failure occurs, you can manually reset the session system activity records with the following procedure:

  1. If Sterling B2B Integrator is not running, restart all of its nodes.
  2. Disable all of the Connect:Direct Server Adapters.
  3. After all of the Connect:Direct Server Adapters are disabled, re-enable them.