About Supporting Multiple Siebel Modules

Depending on the specific Siebel CRM applications that you are using and how you deploy them, these applications have different requirements and characteristics.

• Employee applications, such as Siebel Call Center.

• Customer applications, such as Siebel Self Service or Siebel eSales.

All Siebel CRM applications use Siebel Open UI. All Siebel applications have many architectural elements in common. Multiple applications can use the same Siebel runtime repository. Each application uses its own Siebel Application Object Manager component. You might need to define, configure, and test multiple instances of each application to verify that your requirements are met in each usage scenario.

The performance of your Siebel applications will vary according to how you have configured the applications using Siebel Tools, custom browser scripts, or other methods. See Following Configuration Guidelines.

Client performance will also vary according to which Siebel modules that you deploy. The performance of the Siebel client is highly dependent on feature functionality. Therefore, performance characteristics of Siebel modules will differ.

Some modules add special processing requirements. For example, Siebel CTI uses the Communications Session Manager (CommSessionMgr) component, and supports the communications toolbar and displaying screen pops in the client. Server and local resources support this functionality.

Supporting users who are dispersed in offices around the country or around the world introduces special deployment factors that can affect performance.