Incoming Concurrent EAI Requests and Session Management

When an external application sends a SOAP request to the Siebel EAI Object Manager and it uses a Session Token, the Siebel application uses the information in that token to find the EAI Server Task that created that Session Token if the Application Interface Profile parameter, No Session Preference in EAI-SOAP is set to FALSE.

Note: No Session Preference in EAI-SOAP is set to FALSE by default and can be found in the Application Interface Profile in the Siebel Management Console (SMC).

Note: When the No Session Preference in EAI-SOAP is set to TRUE, incoming requests are not tied to a specific EAI Server Task and will use any that are available. If no Server Task is available, a new one will be created and used. Having this parameter set to TRUE will not use session management.

A Session Token will route the incoming request to a specific EAI Server Task. If that Server Task is unavailable for any reason the Siebel Server returns an error response.

"Token might have been expired or logged out by the user. (SBL-UIF-00880)."

If an external server spawns multiple, simultaneous requests that use the same Siebel Session Token and they all reach the Siebel Server at the same time, one will be processed, and the others will receive the previous error because the EAI Server Task is unavailable as it is processing a request.

You cannot expect to have all the requests using the same Session Token to process simultaneously. One will process, the others will fail.

Note: You can also set the Maximum Retry for Processing EAI-SOAP Request parameter to a number greater than zero to get the server to retry and process the request again. If the EAI Server Task completes processing the request that caused it to be unavailable to the other requests, this parameter may get the request processed when the EAI Server Task becomes available for retry. This parameter is co-located with the No Session Preference in EAI-SOAP parameter in the Application Interface Profile.