Managing Sterling Connect:Direct Secure Plus nodes

Using the Configuration tab, you can configure Sterling Connect:Direct® Secure Plus node entries in your Sterling Connect:Direct server configuration.

Note: To configure Sterling Connect:Direct Secure Plus objects on a Sterling Connect:Direct server, you should first secure the connection between the server and the IBM® Sterling Control Center. You can configure Sterling Connect:Direct Secure Plus over a non-secure connection, but this practice is discouraged due to the possible security ramifications.

The Sterling Connect:Direct® Secure Plus parameters file contains information that determines the protocol and encryption method used during security-enabled Sterling Connect:Direct operations. To configure Sterling Connect:Direct Secure Plus, each site must have a parameters file with one local node record and at least one remote node record. The local node record defines the most commonly used security and protocol settings for the node at the site.

Each remote node record defines the specific security and protocol that are used by a trading partner. You must create a remote node record in the Sterling Connect:Direct Secure Plus parameters file for each Sterling Connect:Direct node with which you communicate.

To use a different certificate to authenticate a trading partner, you must add that information to the remote node record. Likewise, to use a different trusted root file to validate the trusted source that issues certificates, you must add that information to the remote node record.

You can conduct multiple actions on this configuration object. To know more, refer Actions on configuration objects.