Siebel Installation Guide for Microsoft Windows > Additional Postinstallation and Configuration Tasks > Preparing to Run Siebel Server Components >

Enabling and Disabling Server Component Groups

When you initially configured your Siebel Server, you specified which server component groups to enable. Before you deploy your Siebel Server, verify that the server component groups that you require are enabled. It is also recommended that you disable any server component groups that you do not require. Because you explicitly enabled server component groups when you configured the Siebel Server, you might or might not have to disable component groups after installation and configuration.

As is common for a new release, for the current release, Siebel Innovation Pack 2017, some new server components are provided. Also, some components have been removed or are no longer used.

For example, in Siebel Innovation Pack 2017, additional customer applications for Siebel Open UI are provided that were previously desupported in Siebel Innovation Pack 2016, but were available for standard interactivity in prior releases. As of Siebel Innovation Pack 2016, the Application Object Managers that in previous release were used for Siebel eSales, Siebel eCustomer, and Siebel eMarketing are now used for new customer applications built for Siebel Open UI.

Customers migrating from earlier releases also must consider which product changes are new to them because they were made in intervening releases. For example, in Siebel Innovation Pack 2014, some components moved from existing component groups into a new component group, Disconnected Mobile Synchronization (alias MobileSync). Consequently, if your deployment uses Siebel Mobile disconnected applications or uses Siebel Remote or Siebel Replication Manager, then you must enable the MobileSync component group, if you have not already done so, along with the HandheldSync or HandheldSyncSIS component group.

Product changes of these types introduce changed requirements for enabling server components and for deploying applications. The specific requirements that apply to your deployment depend on the products that you are using. Some requirements apply only for migration installations, and vary based on the Siebel CRM version that you are migrating from or the Siebel CRM version in effect when you first configured the software.

For example, for a new installation, you can enable any component groups using the Siebel Management Console. For a migration installation, if you do not reconfigure the Siebel Server and you have to enable any additional component groups, then you can do so manually after installation. In some cases, however, you might have to run certain scripts on the Siebel Server to make new products available.

Before performing a migration installation, also review parameter settings for server components affected by product changes, in case you need to reapply custom settings to components that moved, for example, or in case you must reconfigure the Siebel Server.

Several requirements apply to all migrations to Siebel Innovation Pack 2017, as Additional Tasks for Migration Installations. For example, you must create the Siebel Application Interface profile and apply it to the installed instance of Siebel Application Interface.

For information about the requirements for particular Siebel CRM products, see product documentation on Siebel Bookshelf or elsewhere.

This topic is part of Preparing to Run Siebel Server Components.

Related Topics

Additional Tasks for Migration Installations

Enabling and Disabling Language-Specific Application Object Managers and Adding Languages

Related Books

Siebel System Administration Guide

Siebel Mobile Guide: Disconnected

Siebel Remote and Replication Manager Administration Guide

Siebel Database Upgrade Guide