Pooled default database connections or Pooled specialized database connections for EAI performance
(Doc ID 823014.1)
Last updated on APRIL 30, 2018
Applies to:Siebel Call Center - Version 220.127.116.11 SIA  and later
Siebel CRM - Version 18.104.22.168  to 22.214.171.124  [Release V7]
Information in this document applies to any platform.
For best performance of inbound web service calls, the preferred choice is to use Siebel Authorization Stateless Session Management SOAP headers as discussed in documents :
- Use Siebel Authorization Stateless Session Management for HIGH load inbound web service integrations (Doc ID 795552.1)
- How To Set up web service session management and best practices (Doc ID 1266239.1)
- HowTo close a stateless EAI session when invoking inbound web services using SOAP Headers for Authentication and Session Management and Session token ? (Doc ID 512111.1)
In addition to using Siebel Authorization Stateless Session Management SOAP headers for web services, the EAI component can have its database connections tuned for better performance with the use of :
- Pooled default database connections
- or Pooled specialized database connections
This document explain the differences between them and how to set them up.
Please notice these options are available regardless of using or not Siebel Authorization Stateless Session Management SOAP headers for web services. That is, they could be used with username and password in the URL or WS-Security as well.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|1) Pooled default database connections|
|2) Pooled specialized database connections|
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|