Inbound Web Services of SAI from Fix Pack 8.1.1.7+ seems the right way to provide "pooled" session
Dear Users of the Inbound Web Services of Siebel CRM,
who are challanged to implement a session management approach outlined in the famos Note 1266239.1
I believe we have good knews to you: since Fix Pack 8.1.1.7, the Siebel Application Architecture - SAI seems allows greatly reduce efforts on the WS client side to keep use session pool to gain performance to the Siebel WS calls.
Essentially, with the Inbound WS, hosted by SAI:
- one can keep use the already established approach of Stateless or Statefull SOAP exchange based on Siebel Session Management hgeaders
- one can reduce the session management logic on the WS client, by using
who are challanged to implement a session management approach outlined in the famos Note 1266239.1
I believe we have good knews to you: since Fix Pack 8.1.1.7, the Siebel Application Architecture - SAI seems allows greatly reduce efforts on the WS client side to keep use session pool to gain performance to the Siebel WS calls.
Essentially, with the Inbound WS, hosted by SAI:
- one can keep use the already established approach of Stateless or Statefull SOAP exchange based on Siebel Session Management hgeaders
- one can reduce the session management logic on the WS client, by using
2