About Configuring Siebel CRM

After performing a new installation of Siebel Enterprise Server modules or Siebel Application Interface, you must configure the appropriate modules by using the Siebel Management Console, as described in this chapter.

The Siebel Management Console, a Web-based application that you run on the Siebel Application Interface, supports configuration tasks for the following:

Security
Siebel Gateway
Siebel Gateway Cluster
Siebel Enterprise
Siebel Server
Siebel Application Interface
Siebel Migration application

Siebel Management Console also provides the ability to configure and manage deployed server entities, similar to the functionality in the Administration - Server Configuration and Administration - Server Management screens in the Siebel application.

In most cases, you perform the configuration in a two-step process for each entity that you are configuring:

Creating a profile for the type of entity you are configuring
Deploying the profile into your Siebel deployment

A profile is a collection of configuration settings. You can create as many profiles as you require, and deploy these profiles according to your requirements, as appropriate for your physical installed Siebel software and your authentication methods. You can deploy profiles to multiple installed instances of Siebel Server or Siebel Application Interface, for example. When you create a profile, you must use a unique name in order to successfully create the profile.

Most of the configurable entities correspond to physical installed modules (Siebel Gateway, Siebel Server, or Siebel Application Interface). Some entities are provided with other modules. For example, security adapters are provided with the Siebel Server, and the Siebel Migration application is provided with the Siebel Application Interface installation. The Siebel Enterprise is a logical entity that you must deploy for each Siebel deployment. The Siebel Gateway Cluster is also a logical entity that you can optionally configure for multiple installed Siebel Gateway nodes.

You must configure and deploy at least the Siebel Gateway, Siebel Enterprise, Siebel Server, and Siebel Application Interface in every Siebel deployment.

After you configure the Siebel Gateway, you can create profiles in any sequence. Restrictions apply to the sequence in which you deploy these profiles in your Siebel deployment. In general, the configuration sequence for a new deployment corresponds to the sequence of the configuration topics in this chapter.

Note: For a migration installation case, you must install Siebel Application Interface first and specify information such as application container port numbers. You then provide some of this data as input for the migration installation of Siebel Gateway, which allows the configurations to be migrated. After the migration installations, you do not configure the Siebel Gateway, Siebel Enterprise, or Siebel Server using the Siebel Management Console. However, you must then configure the Siebel Application Interface. Additional configuration requirements apply for migration installations, as described in Configuration Requirements for Migration Installations.

The Siebel Management Console uses the Siebel Gateway registry to store configuration data. Consequently, the first configuration task that you must perform when you run the Siebel Management Console is configuring the Siebel Gateway itself, and its registry. After doing this, you can create and deploy profiles for all other applicable modules in your Siebel deployment.

Note: It is strongly recommended to back up the Siebel Gateway registry periodically for safety reasons, so that you will be able to restore the Siebel Gateway registry from a backup if something goes wrong. For more information, see Siebel System Administration Guide.

(Windows) After configuration, the Siebel system services start automatically. You can use the Windows Control Panel to change whether a Siebel system service starts automatically or manually, or to change the user name or password under which the system service runs.

(UNIX) After configuration, you might want to configure the Siebel system services to start automatically.

Note: You cannot operate any Siebel CRM modules for your deployment until you have configured and deployed them. You must be running the Siebel Gateway in order to configure and deploy any other entities.

Other Siebel Management Console Activities

You can also use the Siebel Management Console to remove configuration data for deployed entities, which is a necessary part of uninstalling the Siebel CRM software. Restrictions apply to the sequence in which you can remove configuration data for deployed modules. For more information, see Process of Removing Configuration Data.

To modify some configuration settings for an existing Siebel Enterprise or Siebel Server, or a Siebel Server component, you can optionally use the functionality in the Configuration screen in Siebel Management Console, as described in Configuring the Siebel Deployment. Alternatively, you can use the Administration - Server Configuration screen in the Siebel application or use Siebel Server Manager, as described in Siebel System Administration Guide. Depending on the specific configuration updates that you make, you might have to restart the Siebel Server before the changes take effect. The Siebel Management Console allows you to refresh the configuration data displayed so that it reflects the latest updates for the deployed Siebel Enterprise or Siebel Server.

In addition, you can manage server modules in the Siebel CRM deployment by using the Management screen in the Siebel Management Console, as described in Managing the Siebel Deployment. Alternatively, you can use the Administration - Server Management screen in the Siebel application or use Siebel Server Manager, as described in Siebel System Administration Guide.

This topic includes the following information: