Siebel Installation Guide for Microsoft Windows > Configuring Siebel Business Applications Server Modules >

About Configuring Siebel Business Applications

After performing a new installation of Siebel Enterprise Server components 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 supports configuration tasks for the following entities:

• Security
• Siebel Gateway
• Siebel Enterprise
• Siebel Server
• Siebel Application Interface
• Siebel Enterprise Cache Server
• Siebel Enterprise Cache Client
• Siebel Constraint Engine (available as a developer preview)
• Siebel Migration 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.

Most of the configurable entities correspond to physical installed modules (Siebel Gateway, Siebel Server, Siebel Application Interface, Siebel Enterprise Cache, or Siebel Constraint Engine). Some entities are available after installing particular modules (security adapters, for example, and the Siebel Migration application, which is provided with the Siebel Application Interface installation). The Siebel Enterprise is a logical entity that you must deploy for each Siebel deployment.

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

If you will be using the Siebel Product Configurator integration with Oracle Advanced Constraint Technology (available as a developer preview), then you must also install, configure, and deploy the Siebel Enterprise Cache and the Siebel Constraint Engine. For more information, see Siebel Product Administration Guide.

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 later in this topic.

You can also use the Siebel Management Console to remove configuration data for deployed entities, which is a necessary part of uninstalling the Siebel Business Applications 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.

The Siebel Management Console uses the Siebel Gateway registry to store all of the 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 of the applicable modules in your Siebel deployment.

Alternatively, to modify some configuration settings for an existing Siebel Enterprise or Siebel Server, or a Siebel Server component, you can use Siebel Server Manager, as described in Siebel System Administration Guide. Depending on the specific updates made, 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.

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.

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

Where to Find Configuration Tasks

The configuration tasks for Siebel Business Applications are described in the following locations, as shown in Table 4.

Configuration Requirements for Migration Installations

In the current release, the migration installation case has particular requirements that relate to configurations. For your installed Siebel CRM software for a prior release, do the following, in the order shown:

1. Review all relevant documentation. See Before You Install Siebel Business Applications and About Installation Tasks for Siebel Business Applications.
2. Perform any necessary premigration tasks, as noted in Additional Tasks for Migration Installations.

   CAUTION:  In particular, you must remove the existing Siebel Web Server Extension (SWSE) configuration on the Web server computer where you installed SWSE for the prior release. Do this before you perform the migration installation of Siebel Application Interface for the current release. Otherwise, the virtual directories cannot be cleaned up adequately. For more information, see Removing the Siebel Application Interface Configuration.

3. Install Siebel Application Interface as a migration installation for your existing installation of SWSE, as described in Installing Siebel Business Applications in a Migration Installation.
4. Install Siebel Enterprise Server as a migration installation, as described in Installing Siebel Business Applications in a Migration Installation.

   NOTE:  For the Siebel Enterprise Server that includes the Siebel Gateway, when you perform the migration installation, you provide input that configures the Siebel Gateway and allows the existing configurations for the Siebel Enterprise and Siebel Servers to migrate to the new Siebel Gateway.

5. (Optional) Install Siebel Enterprise Server as a new installation, selecting only components that are new in the current release and that you require, as described in Installing Siebel Business Applications in a New Installation. For example:
   • Siebel Enterprise Cache
   • Siebel Constraint Engine (available as a developer preview)
6. Perform any necessary postinstallation tasks, as noted in Additional Tasks for Migration Installations. For example, do the following:
   • Where necessary, upgrade the database client to a supported version for Siebel Innovation Pack 2017. Also update the database client installation path in the defined environment variables.
   • Update files and directories on Siebel Enterprise Server and Siebel Application Interface (where necessary).
7. Run Incremental Repository Merge, as described in Siebel Database Upgrade Guide.
8. Run the Siebel Management Console, as described in Starting the Siebel Management Console. See also About Configuring Siebel Business Applications.
   • Create a profile for Siebel Application Interface, and then deploy this profile to the installed Siebel Application Interface. For more information, see Configuring the Siebel Application Interface.
   • Configure any new components that you installed, including those noted in Step 5, or the Siebel Migration application.

Related Topics

Installation-Related Changes for Siebel Innovation Pack 2017

Installing Siebel Business Applications Server Modules

About Installation Tasks for Siebel Business Applications

Additional Tasks for Migration Installations

Running the Siebel Management Console

Installing the Siebel Database on the RDBMS

Additional Postinstallation and Configuration Tasks

Requirements for Installing and Configuring Siebel Business Applications

Process of Removing Configuration Data