CEUServerAdapterInstanceName and SessionId

Edit online

The configuration name of the Sterling Connect:Enterprise® UNIX Server Adapter (CEUServerAdapterInstanceName) and SessionId are at the top level of the process data for visibility and use by the services in the business process, as in the following example:

<?xml version="1.0" encoding="UTF-8"?>
<ProcessData>
  <CEUServerAdapterInstanceName>BP</CEUServerAdapterInstanceName>
  <CEUServerAdapterInstanceName>BP</CEUServerAdapterInstanceName>
  <SessionId>2057</SessionId
  <ACD_INFO>
      .
      .
      .

These parameters are important because they indicate which Sterling Connect:Enterprise UNIX Server Adapter configuration started the business process and what session the services will be acting on behalf of. Because you can have multiple configurations of the adapter, each Sterling Connect:Enterprise UNIX Server service used in the business process needs to determine which adapter configuration to communicate with so that the business process activity is passed through the correct (requesting) adapter.

Note: Because the SessionId is put into process data during a schedule notification, it serves as an implied Begin Session; therefore, you do not need to use a Begin Session service in a business processes initiated from a schedule notification. However, you must still use an End Session service to bracket all activities within the same SessionId.

The CEUServerAdapterInstanceName in process data overrides whatever adapter the services are configured to use. Therefore, if you configure a new Sterling Connect:Enterprise UNIX Server Adapter you do not need to create a new suite of service configurations to point to the new adapter. The original Sterling Connect:Enterprise UNIX Server Adapter service configurations are reusable.