9Application Object Manager Administration

Application Object Manager Administration

This chapter explains how to configure, deploy, and administer Application Object Managers to support Siebel Web Clients. This chapter also explains Application Object Manager concepts to provide useful background information. It includes the following topics:

• About the Siebel Application Object Manager

• Configuring the Application Object Manager Environment

• About Application Object Manager Parameters

• Administering the Application Object Manager

About the Siebel Application Object Manager

Siebel Application Object Manager (Application Object Manager) components host the Business Objects layer and Data Objects layer of the Siebel architecture. The Siebel Web Clients host the Siebel application user interface layer. The Application Object Manager supports Siebel Web Client connections and handles multiple users simultaneously by making requests to the Siebel Server on behalf of the clients.

Application Object Managers are hosted as components in the installed Siebel Server and run on the Siebel Server computer (sometimes called the application server computer). The Siebel Server provides the infrastructure for an Application Object Manager to serve multiple Siebel Web Client users. Multiple Application Object Manager components can run on a single Siebel Server installation. Application Object Manager components can be configured to run as multithreaded processes in the Siebel Server. Like other Siebel Server components, you can administer Application Object Manager components using the Siebel Server Manager.

Application Object Managers communicate with clients using the TCP/IP protocol through the Siebel Application Interface. Communication between the Siebel Application Interface and the Application Object Manager can be compressed and encrypted. An independent session is established to serve incoming connect requests from each client. Subsequent requests from clients are directed to the same Application Object Manager tasks until the sessions are terminated.

After startup, Application Object Managers do not achieve their full run-time environments until after the first connect, therefore, leading to possible delays during the first connection. For more information about how the Siebel Web Clients and Application Object Managers communicate, see Siebel Performance Tuning Guide.

The Siebel runtime repository is installed as part of each Siebel database installation. User preferences set and saved by Siebel Web Client users are saved on the Siebel Server.

Note: If you are running the Siebel Server in a UNIX environment, then Application Object Managers support Siebel eScript, but not Siebel Visual Basic.

About Application Object Manager Memory Allocation

The Application Object Manager caches information in two different ways. Some information is cached and used by every connection and other information is stored for each user connection.

Memory allocation for the Application Object Manager can be broken into three areas:

• User memory. The user area maintains specific information about each user's session. Typically, each user uses 3 MB to 4 MB of memory, although the memory required depends on the Siebel application in use. This memory is released when the task is completed.

• Shared memory between users. Shared memory is for common structures used by every user and is the largest segment of Application Object Manager memory. It contains definitions for business objects, business components, controls, and other metadata items from the Siebel repository. This memory is loaded as needed and remains loaded for the life of the process. Application Object Manager processes commonly use more than 150 MB.

• Administrative memory. The administrative area of memory used by Application Object Manager manages the component itself. This memory is relatively small and is used to manage communication between the Application Object Manager and other Siebel Server components. It runs the listener and coordinates threads and tasks.

Configuring the Application Object Manager Environment

This topic describes how to configure the environment for your Application Object Manager components.

To configure the Application Object Manager environment

1. Make sure that Application Object Managers are included as part of the Siebel Server installations you plan to use.

   Configuring a Siebel Server defines the Application Object Manager components for this Siebel Server. For information about installing and initially configuring the Siebel Server, see the Siebel Installation Guide for the operating system you are using.

2. Verify that the customized Siebel runtime repository is included in the Siebel database that serves the modified application.

   It is strongly recommended that no other user besides the application developer customize the Siebel runtime repository.

3. Configure the Application Object Manager components by setting the parameters that control:

   • Application name to run (configuration file)

   • Language code

   • Compression setting

   • Encryption setting

   • Number of processes for each component

   • Number of threads or tasks for each process

   • Session Manager parameters

   For more information about this subject, see About Application Object Manager Parameters.

4. Restart the Siebel Server system service to automatically register the Application Object Manager services that you configured in the previous step.

About Application Object Manager Parameters

At startup, Application Object Manager components accept several parameters that determine their behavior.

This section includes the following information:

• Application Object Manager Parameters in Server Manager

• Application Object Manager Named Subsystem Parameters

Parameters that affect the operation of Application Object Managers can be modified as follows:

• Component parameters for the Application Object Manager using the Siebel Server Manager. For more information about this task, see Configuring Siebel Server Component Parameters.

• Named subsystem parameters using Siebel Server Manager. For more information about this task, see Configuring Siebel Enterprise Server Named Subsystem Parameters.

Application Object Manager Parameters in Server Manager

This topic provides a partial list of component-specific and generic parameters that you set for the Application Object Manager. You configure Application Object Manager parameters in the same manner as those for any server component.

To configure Application Object Manager parameters using the Server Manager GUI, see Configuring Siebel Server Component Parameters. To configure Application Object Manager parameters using the Server Manager command-line interface, see Parameter Management Commands.

See the following parameters:

• Compression Type (alias Compress)

• Encryption Type (alias Crypt)

• Error Flags (alias ErrorFlags)

• Language Code (alias Lang)

• Log Print Timestamp (alias LogTimestamp)

• Maximum MT Servers (alias MaxMTServers)

• Maximum Tasks (alias MaxTasks)

• Minimum MT Servers (alias MinMTServers)

• Multi-Threaded (alias Threaded)

• Number of lines after which to flush the log file (alias LogFlushFreq)

• Password (alias Password)

• Trace Flags (alias TraceFlags)

• User Name (alias Username)

• Use Shared Log File (alias LogUseSharedFile)

For a description of each parameter, see Siebel Enterprise, Server, and Component Parameters.

For information about locale-specific Application Object Manager parameters, including information about regional standards for currency, time, date, and so on, see Siebel Global Deployment Guide.

Application Object Manager Named Subsystem Parameters

The Application Object Manager can maintain several different values for a particular parameter by using named subsystems.

For more information about named subsystems and named subsystem parameters, see About Named Subsystem Parameters. For information about configuring Application Object Manager named subsystem parameters, see Configuring Siebel Enterprise Server Named Subsystem Parameters.

To configure named subsystems using the Siebel Server Manager command-line interface, see Named Subsystem Management Commands.

Named Subsystems Used by Application Object Managers

The following table provides a partial list of named subsystems used by Application Object Managers.

Table Named Subsystems Used by Application Object Managers

Named Subsystem	Alias	Type	Description
DataMart Datasource	DataMart	InfraDatasources	Datamart data source used by Application Object Manager components
Gateway Datasource	GatewayDataSrc	InfraDatasources	Gateway data source used by Application Object Manager components
Object Manager Cache	ObjMgrCache	InfraObjMgrCache	Cache parameters for Application Object Manager components
Server Datasource	ServerDataSrc	InfraDatasources	Server data source used by Application Object Manager components
LDAP Security Adapter	LDAPSecAdpt	InfraSecAdpt_LDAP	LDAP security adapter used for Application Object Manager authentication with directory servers

Named Subsystem Parameters

The following table provides a partial list of named subsystem parameters.

Table Named Subsystem Parameters

Parameter Alias	Named Subsystem	Data Type	Description
DSConnectString	GatewayDataSrc	String	Specifies the host name of the Siebel Gateway. The value $(GatewayAddress) for the parameter ConnectString of the GatewayDataSrc section of the Application Object Manager's configuration file is replaced at run time with the value for the named subsystem parameter DSConnectString. An incorrect setting for DSConnectString results in server administration being inaccessible from the Siebel Web Client.
DSConnectString	ServerDataSrc	String	Specifies the database connection information. On Oracle Database (native), this information is the TNS alias from tnsnames.ora. On Microsoft SQL Server and IBM DB2, this information is the ODBC Datasource Name.
DSDockedFlg	ServerDataSrc	Boolean	When you create a new named subsystem for an Application Object Manager, you must set this parameter to True.
DSFileSystem	ServerDataSrc	String	Set this parameter to *FSM* to allow the use of the File System Manager server component for standard Siebel Web Clients.
DSMaxCursorSize	ServerDataSrc, GatewayDataSr, or DataMart	Integer	Sets the total number of rows that can be returned in a result set. The parameter MaxCursorSize is set for the Application Object Manager component by using the named subsystem parameter DSMaxCursorSize. (The applicable subsystem corresponds to the component parameter OM - Data Source.) This parameter is valid only with IBM DB2 for OS/390 and z/OS. For more information, see the description of the MaxCursorSize parameter in Parameters for Individual Data Source Sections.
DSPreFetchSize	ServerDataSrc, GatewayDataSr, or DataMart	Integer	Sets the number of rows that the Siebel application reads initially as part of a query execution. The parameter PreFetchSize is set for the Application Object Manager component by using the named subsystem parameter DSPreFetchSize. (The applicable subsystem corresponds to the component parameter OM - Data Source.) This parameter is valid only with IBM DB2 for OS/390 and z/OS. For more information, see the description of the PreFetchSize parameter in Parameters for Individual Data Source Sections.
DSEnterpriseServer	ServerDataSrc, GatewayDataSr	String	Specifies the name of the Siebel Enterprise Server used by various named subsystems. The value in the Application Object Manager is replaced at run time with the value set for the named subsystem.
DSRequestServer	ServerDataSrc	String	Specifies where asynchronous calls are redirected, for example when using Interactive Assignment. Set this value to the logical name of the Siebel Server, not the computer name. The default value is null.
DSTableOwner	All named subsystems of type InfraDatasources	String	Specifies the table owner for this data source. Application Object Manager server components, such as Call Center Object Manager, read the value of this parameter. Siebel Server infrastructure and system management components, such as Server Request Broker (SRBroker), read the value of the TableOwner enterprise parameter.
DSDisableExecuteRetry	ServerDataSrc	Boolean	When set to True, this parameter prevents the Application Object Manager from resending a query to the database layer if an error occurs such as a network error or session kill.

Administering the Application Object Manager

You can monitor Application Object Managers at the following levels:

• The server level using Siebel Server

• The component level using Application Object Manager components

• The task level using Application Object Manager tasks

At each of these levels, you can do the following:

• Use the server administration views to monitor the following:

  • State values

  • Statistics

  • Log files

• Use the Siebel Server Component Parameters view to set the component-specific parameters for the Application Object Manager.

• Start, stop, pause, or resume any Application Object Manager tasks.

At the component event level, you can enable SQL tracing to view the SQL that is generated for the specified Application Object Manager. You can enable SQL spooling on the Application Object Manager task by setting the Object Manager SQL Log event parameter to 4 at the component event level. For more information about event logging, see Event Logging Commands.

For more information about Application Object Manager state values, statistics, and log files, about monitoring an Application Object Manager server component, and about event logging, see Siebel System Monitoring and Diagnostics Guide.