Performance Tuning Guide > Tuning the Siebel Application Object Manager for Performance >

AOM Infrastructure

An AOM component is implemented as a multithreaded process on the Siebel Server. At runtime, a parent process starts one or more multithreaded processes, according to the AOM configuration.

Each process can host multiple user sessions (as tasks), which in turn are implemented as threads within the process. These threads may be dedicated to particular user sessions, or they may serve as a pool that can be shared by multiple user sessions. (For each process, a few threads also start that are dedicated to performing core functions for the process.)

As more users log into the system, additional processes may be instantiated to host these users.

  • In this chapter, the term thread is often used interchangeably with task, except when you are using thread pooling. For details, see Using Thread Pooling for AOM.
  • The terms multithreaded server or MT server are alternative terms for multithreaded process (a process that supports multiple threads). For example, the names of the AOM parameters MaxMTServers and MinMTServers refer to multithreaded processes.

AOM components, which run in interactive mode, handle processing for Siebel Web Client sessions, in which the application user interface (UI) resides. The AOM task manages Siebel business objects and data objects and performs business logic for the client session.

Generally, each AOM task starts in response to a request from a Siebel Web Client running in a Web browser, and ends when the client disconnects.

AOM Communications with Other Modules

Each AOM task uses Siebel Server infrastructure capabilities to communicate with the Siebel Database, the Web server (through the SWSE), and other Siebel Enterprise Server components.

  • 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 details on configuring database connection pooling, see Configuring Database Connection Pooling for AOMs.

  • Communication with Siebel Connection Broker (SCBroker) uses mechanisms internal to the operating system. SCBroker receives each SISNAPI connection request from the SWSE and forwards the connection request to the AOM multithreaded process with the fewest running tasks. Once the connection has been forwarded, requests flow directly from SWSE to AOM.

    For more information about tuning SCBroker, see the load balancing sections in Siebel Installation Guide for the operating system you are using and the Siebel System Administration Guide.

  • Communication with the Siebel Web Server Extension uses SISNAPI (Siebel Internet Session API), a messaging format that runs on top of the TCP/IP protocol. SISNAPI connections can be configured to use encryption and authentication based on Secure Sockets Layer (SSL).

    For details on tuning SISNAPI communications, see Configuring SISNAPI Connection Pooling for AOM.

  • Communication with other Siebel Enterprise Server components (including other Siebel Servers) also uses SISNAPI, going through Server Request Broker (SRBroker).

    For more information about tuning SRBroker, see Tuning Server Request Broker (SRBroker).

About Tuning the AOM

Tuning activities directly or indirectly applicable to AOM components may involve any or all of the following:

  • Configuring parts of your system using the Siebel Enterprise Server configuration utility.
  • Using the Siebel Server Manager to tune parameters for the Enterprise Server, the Siebel Server, or the AOM component. These parameters are stored in the siebns.dat file in a directory on the Siebel Gateway Name Server.
  • Selectively enabling component groups and components on each Siebel Server. Only enable the component groups and components you need.
  • Tuning parameters in the eapps.cfg file on the Siebel Web Server Extension. This file is located in the bin subdirectory of the Siebel Web Server Extension installation directory, on the Web server machine.
  • Tuning parameters in the application configuration file, such as uagent.cfg for Siebel Call Center. This file is located in the bin/language subdirectory of the Siebel Server installation directory. Parameters in certain sections of this file, such as [SWE], are read by the relevant AOM, such as SCCObjMgr_enu for Siebel Call Center in a U.S. English environment.

Some other chapters in this book discuss AOM tuning that relates to using other modules, such as Siebel Communications Server or Siebel Configurator.

Performance Tuning Guide