1. Deployment Planning Guide
  2. Determining Server Platform Requirements

Determining Server Platform Requirements

This topic is part of Mapping Siebel CRM Deployment Elements to Platforms.

Perform the following steps to determine your server platform requirements, for topology planning:

To determine server platform requirements

  1. Determine the amount of hardware required for Siebel Server components. Consider both average and peak workloads. Also consider background processing workloads.

    On two- or four-CPU platforms, customers typically deploy one Application Object Manager on each Siebel Server. Deploying Application Object Managers in this manner is a common practice, but not a requirement. Depending on the number of concurrent users, the amount and complexity of customization and the components used, the distribution of components can vary.

    For information about calculating the settings for MaxTasks, MaxMTServers, and MinMTServers, see Siebel Performance Tuning Guide.

    For additional help with sizing Siebel Servers, contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle’s Application Expert Services.

  2. Identify which Siebel Server components you can collocate. Distribute these across platforms in a way that evenly distributes workload.

    Recommendations for collocating server components are provided later in this topic.

  3. Determine how many additional hardware platforms are needed to comply with high availability policies.

    For clustered servers, define a failover strategy for components (active-active, active-passive).

    Note: In active-active clustering, a process is only active on one node of the cluster and is not active on the other node; that is, two physical servers are running a different clustered process. For information about high availability options, see Defining High Availability Policies.

  4. Identify additional hardware required to comply with security policies. For example, do you have to install additional firewalls or a proxy server? Do you have to install LDAP servers?

  5. Use average and peak workload information to determine how many instances of Siebel Application Interface are needed.

  6. Create a diagram of the Siebel CRM deployment that shows all of the platforms and the distribution of Siebel Servers. Use the diagram to do the following:

    1. Verify that all of the needed server components are enabled and correctly set up on each platform.

    2. Run component and platform failure scenarios. Verify that there are no single points of failure that can cause unacceptable impacts.

    For example, assume that you have one Siebel Application Interface. All of your inbound customer orders must go through it and then to one HTTP inbound adapter. If the Siebel Application Interface or the inbound adapter fails, then customers cannot place orders.

  7. Use server naming conventions to identify groups of servers that provide similar functions.

    For example, in an enterprise, Application Object Managers run on one group of computers, workflows on a second group of computers, and remote user synchronization on a third group. Give the Application Object Manager servers names starting with APP, the workflow servers names starting with WF, and the Siebel Remote servers names starting with REM.

    The servers in each group are displayed together in Server Manager, which simplifies server administration.

    Note: Additional considerations for server naming are provided in Siebel Installation Guide.