How To Use HTTP Session Mode for Stateful Inbound Web Service Integration (with Example in VB.Net)
(Doc ID 477749.1)
Last updated on NOVEMBER 22, 2019
Applies to:Siebel CRM - Version 188.8.131.52 [IP2013] and later
Information in this document applies to any platform.
As it is documented in the Siebel Bookshelf version 7.5.3 > Integration Platform Technologies: Siebel eBusiness Application Integration Volume II > Web Services > Examples of Invoking Web Services, the HTTP sessionless exchange is typically used to perform a Simple Object Access Protocol (SOAP) into the Siebel application.
This means the following for every inbound Web Service call (used to run a business service of a workflow process):
A new Siebel EAI Object Manager session is instantiated (an Object Manager task is started).
The Siebel user authentication (with credentials provided in the URL string of the HTTP POST request) takes place.
The established Siebel session is used to execute a targeted business service or workflow process.
Upon completion, the Siebel session is closed (Object Manager task terminates).
However, in some cases, it is useful to perform subsequent Inbound Web Service calls of various Web Services and their methods within the same Siebel session context by using HTTP stateful communication. This approach can be helpful to:
Avoid repeated Siebel user credential exchange and Siebel user authentication
Reduce the number of allocated Siebel Object Manager tasks (for all calls)
Preserve the Siebel application context between Web Service calls (global variables, profile attributes, etc)
This document describes how to achieve Siebel session stateful exchange with Siebel application over HTTP/SOAP link. The example is based on the standard session mode functionality of the Siebel HTTP Inbound Transport as described in the Siebel Bookshelf version > Transports and Interfaces: Siebel eBusiness Application Integration Volume III > EAI HTTP Transport.
The session mode is established via the Siebel Session Cookie ('_sn'), which is provided in every incoming HTTP POST/GET request to identify the currently opened Siebel Application Object Manager Session.
The Siebel Session Cookie can be provided either in the HTTP request header or in the URL-argument of the HTTP request query string.
This document is informational and intended for any user.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!