Bookshelf Home | Contents | Index | PDF |
Siebel Installation Guide for UNIX > Configuring Siebel Business Applications Server Modules > About Configuring Siebel Business ApplicationsAfter 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:
In most cases, you perform the configuration in a two-step process for each entity that you are configuring:
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, you might want to configure the Siebel system services to start automatically. For more information, see Configuring the Siebel Gateway for Automatic Start and Configuring the Siebel Server for Automatic Start. 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 TasksThe configuration tasks for Siebel Business Applications are described in the following locations, as shown in Table 4.
Configuration Requirements for Migration InstallationsIn 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:
Related Topics |
Siebel Installation Guide for UNIX | Copyright © 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |