Siebel Application Object Manager Communications with Other Modules
Each Siebel Application Object Manager task uses Siebel Server infrastructure capabilities to communicate with the Siebel database, the Siebel Application Interface, and other Siebel Enterprise Server components.
The following are the major types of communication that the Siebel Application Object Manager has with other modules:
Communication with the Siebel database uses database connections. Database connections can also be managed and tuned for optimal performance. You can optionally configure connection pooling for database connections.
For information about configuring database connection pooling, see Configuring Database Connection Pooling for Siebel Application Object Managers.
Communication between the Siebel Connection Broker (SCBroker) and the Siebel Application Object Manager processes on the same Siebel Server uses mechanisms internal to the operating system. SCBroker receives each SISNAPI (Siebel Internet Session Network Application Programming Interface) connection request from the Siebel Application Interface and forwards the connection request to a Siebel Application Object Manager multithreaded process. Once the request has been forwarded, subsequent requests for the same user session flow directly from Siebel Application Interface to this Siebel Application Object Manager process. The request is forwarded using either a least-loaded or a round-robin algorithm, according to the setting of the SCBroker parameter
ConnForwardAlgorithm
.For information about configuring SCBroker, see Siebel Deployment Planning Guide and Siebel System Administration Guide. See also Siebel Installation Guide.
Communication with the Siebel Application Interface uses SISNAPI, a messaging format that runs on top of the TCP/IP protocol. SISNAPI connections use encryption and authentication based on Transport Layer Security (TLS). For information about tuning SISNAPI communications, see Configuring SISNAPI Connection Pooling for Siebel Application Object Managers.
Communication with other Siebel Enterprise Server components (including other Siebel Servers) also uses SISNAPI, going through Server Request Broker (SRBroker). For information about tuning SRBroker, see Tuning Server Request Broker (SRBroker).