Sterling Connect:Direct Requester Adapter
The Sterling Connect:Direct® Requester adapter configures communication between Sterling B2B Integrator and a remote Sterling Connect:Direct server. It acts as a Sterling Connect:Direct client.
This is an overview of the Sterling Connect:Direct Requester adapter:
| System Name | Sterling Connect:Direct Requester Adapter |
|---|---|
| Graphical Process Modeler (GPM) categories | Cannot be configured in the GPM. |
| Description | Configures communication between Sterling B2B Integrator and a remote Sterling Connect:Direct server. It acts as a Sterling Connect:Direct client. |
| Business usage | Use this adapter to request that a remote Sterling Connect:Direct node perform specific operations. For example, to view work that is active in the Sterling Connect:Direct server (for example, SELECT PROCESS) or view events that have already occurred on the Sterling Connect:Direct server (for example, SELECT STATISTICS). |
| Usage example | The Sterling Connect:Direct Requester adapter is used to submit a process that initiates a sequence of steps on a remote Sterling Connect:Direct server. |
| Preconfigured? | Yes |
| Requires third party files? | The following third-party files are required:
|
| Platform availability | All supported platforms |
| Related services | Tightly integrated with the Sterling Connect:Direct Submit Process service, Sterling Connect:Direct Requester Select Process service, and Sterling Connect:Direct Requester Select Statistics service. |
| Application requirements | Must be used with a perimeter server. Configure it before setting up this adapter. |
| Initiates business processes? | No |
| Invocation | Runs as part of a business process. |
| Business process context considerations | None |
| Returned status values | None |
| Restrictions | None |
| Persistence level | None |
| Testing considerations | Restart Sterling B2B Integrator after configuring and enabling the adapter to confirm that it can successfully connect to the remote Sterling Connect:Direct server using a supported Sterling Connect:Direct service. |
Implementing the Sterling Connect:Direct Requester Adapter
To implement the Sterling Connect:Direct Requester Adapter:
- Create a Sterling Connect:Direct Requester adapter configuration. For information, see Managing Services and Adapters.
- Configure the Sterling Connect:Direct Requester adapter.
- Use the Sterling Connect:Direct Requester adapter in a business process.
Sterling Connect:Direct Requester Adapter and SSL
The Sterling Connect:Direct Requester Adapter might have issues establishing Secure+ sessions for CBC-based cipher suites when running with CBC protection turned on.
Configure Sterling B2B Integrator to turn off CBC protection when using the Sterling Connect:Direct Requester Adapter and CBC-based cipher suites. This affects all TLS communications within the application. See "SSL not working with a CBC-based cipher suite" in the Troubleshoot SSL topic for information on how to turn off CBC protection.
Sterling Connect:Direct Requester Adapter Settings
To configure the Sterling Connect:Direct Requester adapter, specify the following settings in Sterling B2B Integrator:
| Field | Description |
|---|---|
| Name | Unique and meaningful name for the adapter configuration. Required. |
| Description | Meaningful description for the adapter configuration, for reference purposes. Required. |
| Select a Group | Group of services or adapters of the same type
that can act as peers. A Service Group name is used in BPML in place
of the Service Configuration name. Service Groups show up in the GPM
as if they were Service Configurations. Select a Service Group to
associate with this adapter. Valid values are:
For more information about service groups see Managing Services and Adapters. |
| Remote Sterling Connect:Direct Server Address | The IP address that the remote Sterling Connect:Direct server connects to. Required. Valid values are 0.0.0.0 to 255.255.255.254 (default is 127.0.0.1). |
| Remote Sterling Connect:Direct Server Port | The port number that the remote Sterling Connect:Direct server listens on for API connections. Required. Valid are any numeric values (default is 1363). |
| Remote Sterling Connect:Direct User ID | The user ID used to log on to the Sterling Connect:Direct server. Required. |
| Remote Sterling Connect:Direct User Password | The password used to log on to the Sterling Connect:Direct server. Required. |
| Sterling Connect:Direct Perimeter Services Option | The Perimeter server to use. Required. Default value is Local Node1. |
| Encryption using Secure+ | Whether Sterling Connect:Direct Secure Plus should be active. Required. Valid values are Enabled and Disabled (default). |
| Security Protocol | Indicates security protocol version enabled with Secure+. Only displayed if
“Encryption using Secure+" is enabled. Required if “Encryption using Secure+” is enabled. Valid
values are:
|
| CA Certificates | List of Sterling Connect:Direct Secure Plus CA certificates. Only displayed if “Encryption using Secure+" is enabled. Required if “Encryption using Secure+" is enabled. |
| Certificate Common Name | Value to be compared with the Common Name (CN) field from the remote node's
certificate during TLS/SSL handshake in order to enhance certificate authentication. Only displayed
if "Encryption using Secure+" is enabled. May be overridden at the node level. Note: To see the
actual CNs being compared during the handshake, set the Perimeter Services logging level to
ALL.
|
| Cipher Suites | List of Sterling Connect:Direct Secure Plus Cipher suites. Only displayed if “Encryption using Secure+" is enabled. Required if “Encryption using Secure+" is enabled. |
| Require Client Authentication | Indicates whether authentication occurs at the client level. Valid values
are: Yes (Default) No |