Configuring the No Session Preference in EAI-SOAP Parameter

During an Inbound SOAP call, a Siebel Session Token passed in the header of the SOAP request is used to start a EAI Server Task to handle the request. The Server Task is tied to the Session Token by default so that once that Server Task completes or is stopped in any way, any subsequent inbound SOAP request that uses the same Session Token will fail because the Session Token has affinity to the completed Server Task. It cannot be re-used for other Server Tasks.

The error returned to the requesting process will be:

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

To break the tie between the Session Token and the EAI Server Task, use the No Session Preference in EAI-SOAP parameter in the Basic Information section of the EAI application in Application Interface Profile in SMC. Selecting the check box breaks the tie.

The No Session Preference in EAI-SOAP option behaves as follows:

• When No Session Preference in EAI-SOAP = FALSE (deselected, which is the default setting), there is affinity between the Session Token and the EAI task.

  • When an EAI Server Task is still available, incoming requests with the original Session Token will get executed by the original EAI Server Task.
  • When an EAI Server Task is no longer available, incoming requests with the original Session Token will get routed to original EAI Server Task, but since that task is no longer available, it generates the error:

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

• When No Session Preference in EAI-SOAP = TRUE (selected), there is no affinity between the Session Token and the EAI Server Task.

  • When an EAI task is still available, incoming requests with the original Session Token will not have any affinity with the original EAI Server Task and can be executed by any available EAI Server Task.
  • If the original EAI Server Task is not available, a new EAI Server Task is created for the request. The token expired error does not occur.

Use these steps to set this parameter:

1. Log into the Siebel Management Console.
2. Find the Application Interface Profile that you wish to update.
3. Edit the Application Interface Profile.
4. Go to the Applications section of the Profile.
5. Expand the EAI application section of the Profile
6. Expand the Basic section of EAI application.
7. If the Configure EAI HTTP Inbound Transport check box is not selected, select it.

   This will cause the No Session Preference in EAI-SOAP check box to appear.

8. Do one of the following:
   • If you wish to break the one-to-one correspondence between the Session Token and the EAI Server Task, select the check box.
   • If you wish to leave the correspondence intact, do not select the check box.
9. Click Submit.

Note: Selecting/deselecting (changing the value) for the No Session Preference in EAI-SOAP check box does not require a restart of the Application Interface, the EAI Component, or the Siebel Server. It takes effect when the next Session Token is generated.

Note: Anonymous Pool Connections are not affected by the No Session Preference in EAI-SOAP check box. Only requests using Session Management respond to this parameter.