2Overview of Installing Siebel CRM

Overview of Installing Siebel CRM

This chapter provides an overview of installing Siebel CRM. It includes the following topics:

• Installation-Related Changes for Siebel CRM 20.x Update

• Installation-Related Changes for Siebel CRM 17.0

• Before You Install Siebel CRM

• Overview of Siebel CRM Server Architecture

• Roadmap for Installing Siebel CRM for a New Deployment

• Roadmap for Installing Siebel CRM 20.x Update for an Existing Installation of Siebel CRM 17.x or Later

• Roadmap for Installing Siebel CRM in a Migration Installation Case (Existing Installation of Siebel CRM 16.x or Earlier)

• Roadmap for Installing Siebel CRM in an Upgrade Case (Existing Database)

Installation-Related Changes for Siebel CRM 20.x Update

The Siebel Installation Guide for the operating system you are using, for Siebel CRM 20.x Update, describes product changes and requirements that affect your installation tasks and the overall flow of these tasks. See also all of the relevant references in What’s New in Siebel Installation Guide for UNIX, Siebel CRM 20.9 Update and similar topics for prior releases.

• Documentation is for Siebel CRM 20.9 Update. The Siebel Installation Guide for the operating system you are using is for installing the Siebel CRM software for Siebel CRM 20.9 Update.

  For Siebel CRM 18.4 Update through Siebel CRM 20.9 Update, you install the release on top of an existing installation of a prior release of Siebel CRM 17.x or later. For instructions for installing and uninstalling Siebel CRM 20.x Update, see Installing and Uninstalling Siebel CRM 20.x Update.

  Note: For the general purposes of this documentation, the current release is Siebel CRM 20.9 Update. Similar installation characteristics and requirements apply to multiple Siebel CRM 20.x, 19.x, and 18.x Update releases. Installers behave similarly to those for prior Siebel CRM 20.x, 19.x, and 18.x Update releases and Siebel CRM 17.x patchset releases. Siebel CRM 20.9 Update includes all of the functionality from these prior Siebel CRM releases. This guide will be updated again as the installation and configuration requirements evolve for later Siebel CRM 20.x Update releases and other future Siebel CRM releases. For information about the Siebel CRM continuous update deployment strategy, see 2378034.1 (Article ID) on My Oracle Support.

• Evolving installation scenarios. Note the following characteristics of the different installation scenarios, which continue to evolve. More information is provided later in this topic.

  • New installation. For a new installation, you first install Siebel CRM 17.0 as a new installation and then install the current release of Siebel CRM 20.x Update. Documented requirements for Siebel CRM 17.x and later apply, such as for installing the software, installing the Siebel database, running Siebel Management Console, and so on. See Roadmap for Installing Siebel CRM for a New Deployment.

  • Existing installation of Siebel CRM 17.x or later. If you have an existing installation of Siebel CRM 17.x or later, then you install the current release of Siebel CRM 20.x Update on top of your existing installation. See Roadmap for Installing Siebel CRM 20.x Update for an Existing Installation of Siebel CRM 17.x or Later.

    • All Siebel CRM 20.x Update releases contain bug fixes and binary enhancements.

    • The Siebel CRM 20.x Update installer runs various utilities on the Siebel database. See also the information that follows about the Post Install DB Setup (PostInstallDBSetup) utility.

    • Siebel CRM 20.x Update requires that you manually run various utilities on the Siebel database, where applicable.

    • Siebel CRM 20.x Update also provides optional Siebel Repository updates for Siebel CRM applications.

  • Existing installation of Siebel CRM 16.x or earlier (migration installation, with IRM). If you have an existing installation of a release prior to Siebel CRM 17.0, then you first install Siebel CRM 17.0 as a migration installation, and then install the current release of Siebel CRM 20.x Update. Documented requirements for Siebel CRM 17.x and later apply, such as for installing the software, running Incremental Repository Merge, running Siebel Management Console, and so on. See Roadmap for Installing Siebel CRM in a Migration Installation Case (Existing Installation of Siebel CRM 16.x or Earlier).

    For more information, see About Database Updates for Siebel CRM 20.x Update. See also Siebel CRM Update Guide and Release Notes on My Oracle Support for the latest Siebel CRM 20.x Update release. For supported Siebel database upgrade paths and instructions for running Incremental Repository Merge, see Siebel Database Upgrade Guide.

  • Existing installation of a release prior to Siebel CRM 8.1.1 or 8.2.2 (full database upgrade). For an upgrade-type migration from some older Siebel CRM releases, you first install Siebel CRM 17.0 as a new installation and then install the current release of Siebel CRM 20.x Update. Documented requirements for Siebel CRM 17.x and Siebel CRM 20.x Update apply, such as for installing the software, upgrading the Siebel database, running Siebel Management Console, and so on. See Roadmap for Installing Siebel CRM in an Upgrade Case (Existing Database). For supported Siebel database upgrade paths and upgrade instructions, see Siebel Database Upgrade Guide.

  In release media or software contexts showing the Siebel version number, the version is represented as version 20.x, such as version 20.9 for Siebel CRM 20.9 Update. When you install a subsequent Siebel CRM release, the version number of the installed software increments to version 20.10, 20.11, and so on, according to the release installed.

• Installer now runs Post Install DB Setup (PostInstallDBSetup) utility. As of Siebel CRM 20.3 Update, when you install Siebel CRM 20.x Update for an existing installation of Siebel CRM 17.x or later of Siebel Server and Database Configuration Utilities, after installation, the installer runs the Post Install DB Setup (PostInstallDBSetup) utility on the Siebel database. PostInstallDBSetup runs several processes to ensure that the customer database schema, manifest, and seed data is up to date for the current monthly update release.

  Where applicable, you can also optionally run the optional RepositoryUpgrade utility to support new features since Siebel CRM 17.0. For more information, see About Database Updates for Siebel CRM 20.x Update. See also Siebel CRM Update Guide and Release Notes on My Oracle Support and Siebel Database Upgrade Guide.

• You can now configure installed nodes of Siebel Gateway to work together as a cluster. As of Siebel CRM 18.5 Update, Siebel Gateway supports clustering to provide high availability benefits to Siebel CRM customers. The clustering feature supports both the Siebel Gateway service (application container) and the Siebel Gateway registry (Apache ZooKeeper). Siebel Gateway clustering is optional. You might choose to use Siebel Gateway clustering only for your production environment, for example.

  The tasks associated with installing an individual instance of Siebel Gateway are unchanged in the current release, as is the Siebel Management Console task for configuring the primary Siebel Gateway (the first one installed and configured). Siebel Management Console supports a new profile type, the Siebel Gateway cluster profile, and a new step to deploy the cluster profile.

  As of Siebel CRM 20.4 Update, you can change the primary service node and primary registry node in a Siebel Gateway cluster. For more information, see Configuring the Siebel Gateway Cluster.

• You can now configure load balancing for Siebel Application Interface application containers. As of Siebel CRM version 17.5, application containers for Siebel Application Interface instances on multiple nodes can be load balanced using products such as Apache HTTP Server (httpd) with the mod_jk module. The products you use must provide reverse proxy services and support load balancing based on jsessionid cookies. All instances of Siebel Application Interface must be protected by a reverse proxy. For more information, see Planning the Siebel Application Interface Topology.

• Siebel Management Console now includes a Configuration screen. As of Siebel CRM 18.7 Update, system administrators can configure server elements in the Siebel deployment by using the Configuration screen in the Siebel Management Console. Administrators can perform tasks that are equivalent to those that are traditionally performed in the Administration - Server Configuration screen in the Siebel application or in the Server Manager command-line utility, as described in Siebel System Administration Guide. This functionality is provided as an alternative to the traditional methods. For more information, see Configuring the Siebel Deployment.

• Siebel Management Console now includes a Management screen. As of Siebel CRM 18.12 Update, system administrators can manage server elements in the Siebel deployment by using the Management screen in the Siebel Management Console. Administrators can perform tasks that are equivalent to those that are traditionally performed in the Administration - Server Management screen in the Siebel application or in the Server Manager command-line utility, as described in Siebel System Administration Guide. This functionality is provided as an alternative to the traditional methods. For more information, see Managing the Siebel Deployment.

• Siebel Management Console now supports accessibility. As of Siebel CRM 18.7 Update, Siebel Management Console supports enhanced accessibility. For more information, see Accessibility for Siebel Management Console.

• Siebel Management Console now supports safe mode. As of Siebel CRM 19.11 Update, you can configure a safe mode user for Siebel Management Console. For more information, see Using Safe Mode for Siebel Management Console.

• Siebel Migration configuration in Siebel Management Console now includes a Migration Package Location setting. As of Siebel CRM 18.8 Update, you can optionally specify the path representing the location of the migration package. You can use the Migration Package Location setting to specify a single shared location that supports both export and import operations for synchronous and asynchronous migrations. For more information, see Configuring the Siebel Migration Application.

• Siebel Enterprise Cache configuration in Siebel Management Console now supports cache persistence. As of Siebel CRM 19.9 Update, Siebel CRM supports persistence for the caches managed by Siebel Enterprise Cache. For more information, see About Persistence for Siebel Enterprise Cache.

• Siebel Constraint Engine now supports load balancing. As of Siebel CRM 19.2 Update, you can deploy multiple instances of Siebel Constraint Engine in your Siebel deployment, to support load balancing. See also Configuring the Siebel Constraint Engine.

• Siebel Remote now supports TLS (Transport Layer Security). As of Siebel CRM 19.6 Update, Siebel Remote supports TLS encryption and no longer supports RSA encryption. For more information about configuring TLS for Siebel Remote, see Siebel Remote and Replication Manager Administration Guide and Siebel Security Guide.

• Enhanced autostart capability for application containers (Apache Tomcat). As of Siebel CRM 18.8 Update, you can configure application containers (Apache Tomcat) for installations of Siebel Gateway, Siebel Server, and Siebel Application Interface to start automatically on UNIX operating systems. For more information, see Stopping and Starting the Siebel Application Container and Configuring Siebel Application Containers for Automatic Start.

• Ability to customize application container for Siebel Application Interface. As of Siebel CRM 19.5 Update, you can customize URLs for Siebel CRM applications. You can also modify the HTTPS redirect port or HTTP port. These customizations involve modifying the application container (Apache Tomcat) for Siebel Application Interface. For more information, see Customizing URLs for Siebel CRM Applications and Modifying the HTTPS Redirect Port or HTTP Port for Siebel Application Interface.

• Workflow inactivation utility is provided. As of Siebel CRM 20.7 Update, you can run the InactivateWFs.exe utility in development environments to inactivate workflow processes that are no longer required. For more information, see Inactivating Workflow Processes.

• Siebel Tools no longer supports the local or sample database. As of Siebel CRM 17.0, Siebel Tools no longer supports the local or sample database. The local or sample database is only for use with Siebel Mobile Web Client. Developers now use Siebel Web Tools or Siebel Tools with workspaces in the enterprise Siebel database.

• Oracle Database SE2 has replaced Oracle Database XE for the local database. As of Siebel CRM 20.8 Update, Oracle Database SE2 has replaced Oracle Database XE for the local database. The sample database is no longer supported and can no longer be used at this release level or later.

  Unless you already installed Siebel CRM 20.8 Update, before you install the current release, all users of Siebel Remote clients (Mobile Web Clients with local database) must synchronize the local database. Oracle Database SE2 must be downloaded from Oracle and installed with the current release on each remote client. After installations are complete, the local database must be reextracted and initialized for each remote client. For more information, see Installing and Using Oracle Database SE2 for the Local Database.

  Tip: To continue using the sample database for prior versions of Siebel CRM 20.x Update, see About the Sample Database for Prior Versions of Siebel Mobile Web Client.

Related Topics

Installation-Related Changes for Siebel CRM 17.0

Installing and Uninstalling Siebel CRM 20.x Update

About Database Updates for Siebel CRM 20.x Update

Configuring the Siebel Deployment

Planning the Siebel Application Interface Topology

Related Books

Siebel CRM Update Guide and Release Notes on My Oracle Support

Installation-Related Changes for Siebel CRM 17.0

Note: This topic provides information that applies specifically to Siebel CRM 17.x and now also applies to environments in which you are now installing Siebel CRM 20.x Update. This information is provided for your reference and has not been updated for Siebel CRM 20.x Update releases. See also Installation-Related Changes for Siebel CRM 20.x Update.

The Siebel Installation Guide for the operating system you are using describes several product changes and requirements that affect your installation tasks and the overall flow of these tasks. See also all of the relevant references in What’s New in Siebel Installation Guide for UNIX, Siebel CRM 20.9 Update and topics for prior releases.

• Documentation is for Siebel CRM 17.0. The Siebel Installation Guide for the operating system you are using is for installing Siebel CRM 17.0. With some differences, installation for this release is similar to that for previous releases. You can install Siebel CRM 17.0 as a new installation or as a migration installation.

  Siebel CRM 17.0 includes new functionality and applicable functionality from previous releases.

  Customers who had previously installed a Siebel CRM release prior to Siebel CRM 17.0 can install Siebel CRM 17.0 as a migration installation. When you migrate from the prior release, you must also run Incremental Repository Merge, as described in Siebel Database Upgrade Guide.

  Previous versions of the Siebel Bookshelf are still available. The Siebel Installation Guides for prior releases are available on My Oracle Support, at 1461732.1 (Article ID). For detailed information about the installation features of prior releases, see these earlier guides.

• Enhanced support for deployment in a variety of computing environments. In Siebel CRM 17.0, several changes have been made to the Siebel CRM installation and deployment process and to the Siebel CRM architecture. Many of these changes, described in the rest of this topic and elsewhere, make it easier to deploy Siebel CRM 17.0 in a variety of computing environments: on-premise, on the cloud, or some combination of these. The Siebel CRM environment now uses embedded application container functionality and RESTful services. The new framework eliminates dependency on third-party Web servers and reduces dependency on other operating system-specific modules. Installations of Siebel Enterprise Server and Siebel Application Interface modules now include deployment of WAR files into the application container and configuration of application container ports.

  Note: For detailed information about the configuration and administration of an application container outside of the Siebel configuration framework, see Apache Tomcat documentation.

• New Siebel Gateway replaces Siebel Gateway Name Server. As of Siebel CRM 17.0, the functions previously provided by Siebel Gateway Name Server are now performed by a new module called Siebel Gateway. This module is installed with the updated version of the Siebel Enterprise Server installer.

  Siebel Gateway uses embedded application container functionality to manage communications with other modules. Configuration data for the Siebel environment is stored internally to Siebel Gateway. The siebns.dat file is no longer used. The Siebel Server installation also includes embedded application container functionality as part of communication with the Siebel Gateway. The authentication framework for accessing Siebel Gateway has changed. For more information, see Installing Siebel CRM Server Modules.

• New Siebel Application Interface replaces Siebel Web Server Extension. As of Siebel CRM 17.0, the functions previously provided by Siebel Web Server Extension (SWSE) are now performed by a new module called Siebel Application Interface. This module is installed with the updated version of the Siebel Enterprise Server installer.

  Install Siebel Application Interface in the secured application intranet zone, in a different location on the same computer as the other Siebel CRM modules, or on a different computer.

  Siebel Application Interface uses an internal Web application server, including application container functionality, to manage Siebel CRM Web requests that were formerly handled by SWSE installed on a third-party Web server.

  Siebel Application Interface plays a new role in supporting Siebel native load balancing for Siebel Servers in Siebel CRM 17.0. When a user requests a new application connection, Siebel Application Interface sends a request to Siebel Gateway, which returns a connect string for the least-loaded Application Object Manager from among the Siebel Servers supporting that server component. The user session will use this Application Object Manager.

  All instances of Siebel Application Interface must be protected by a reverse proxy. For more information about deployment options for Siebel Application Interface with Web servers for the current release, see Planning the Siebel Application Interface Topology.

  The application configurations formerly defined in the eapps.cfg file and associated with virtual directories on the Web server are now managed by the Siebel Management Console and stored in the Siebel Gateway registry. The new_virdirs script for adding newly available applications to a previously configured SWSE is not applicable for this release. Where virtual directories formerly mapped to the public directory on the SWSE, application configurations now map to applicationcontainer/webapps/siebel in the Siebel Application Interface installation.

  The URL format for Siebel CRM has been updated and standardized for Siebel applications, Siebel EAI (inbound SOAP, inbound HTTP), REST, CalDAV, CardDAV, and other programs or technologies. For more information, see Installing Siebel CRM Server Modules.

• New Siebel Management Console replaces Siebel Configuration Wizards. As of Siebel CRM 17.0, most of the initial configuration of the Siebel CRM environment is done through the Siebel Management Console, a new Web-based application provided with the Siebel Application Interface installation. Most of the Siebel Configuration Wizards are no longer provided. (Database Configuration Wizard and related utilities still use the old Siebel Configuration Wizard framework.) Several new modules can now be configured using the Siebel Management Console. The sequence in which you perform configuration tasks has also changed. For more information, see Configuring Siebel CRM Server Modules.

• New Siebel Migration application installed with Siebel Application Interface. The new Siebel Migration application, a Web-based tool for migrating Siebel Repositories and seed data and performing related tasks, is provided with the Siebel Application Interface installation. The Siebel Management Console includes tasks for configuring the Siebel Migration application. For more information, see Installing Siebel CRM Server Modules and Configuring Siebel CRM Server Modules. See also About Installing in Upgrade Environments and Siebel Database Upgrade Guide.

• Enhanced support for Siebel Enterprise Cache. The Siebel Enterprise Server installer now provides the option of installing the Siebel Enterprise Cache (formerly called Siebel Cache Server), and the Siebel Management Console includes tasks for configuring and managing the Enterprise Cache Server and the Enterprise Cache Client. The Siebel Enterprise Cache, which is based on Oracle Coherence, is used by the Siebel Constraint Engine (which is available as a developer preview). For more information, see Installing Siebel CRM Server Modules and Configuring Siebel CRM Server Modules.

• Enhanced support for Siebel Constraint Engine used by Siebel Product Configurator. The Siebel Product Configurator integration with Oracle Advanced Constraint Technology is available as a developer preview. The Siebel Constraint Engine is part of this integration, which also requires the Siebel Enterprise Cache. The Siebel Enterprise Server installer now provides options for installing both the Siebel Enterprise Cache and the Siebel Constraint Engine, and the Siebel Management Console includes tasks for configuring and managing these modules. For more information, see Installing Siebel CRM Server Modules and Configuring Siebel CRM Server Modules. See also Siebel Product Administration Guide.

• Siebel runtime repository replaces Siebel Repository Files. In Siebel CRM 17.0, Siebel Composer is now generally available. Siebel Repository Files (SRF) are no longer used, and Siebel applications use the Siebel runtime repository instead. Siebel Tools and Siebel Web Tools always use the Siebel runtime repository configuration provided by Oracle and cannot use a customer-modified Siebel runtime repository. (For troubleshooting purposes, Siebel applications using the Siebel Web Client or Mobile Web Client can also be configured to use the Siebel runtime repository provided by Oracle.) The objects directory (former SRF location) has been removed for all applicable Siebel CRM modules. For more information, see Using Siebel Tools. See also Siebel System Administration Guide.

• Custom Siebel Web template files migrate to Siebel database. In Siebel CRM 17.0, custom Siebel Web template files migrate into the Siebel database when you run Incremental Repository Merge, as described in Siebel Database Upgrade Guide. For more information, see Additional Tasks for Migration Installations.

• Existing customers must perform additional migration tasks. In Siebel CRM 17.0, existing configuration settings for SWSE are not automatically migrated to Siebel Application Interface. You must remove the existing configuration for SWSE. Before installing, you must run an additional command to attach the Oracle home from the prior release. You must perform the Siebel Application Interface migration installation first, before that for all other modules. After completing the migration installation for all server modules, you must configure Siebel Application Interface using the Siebel Management Console. Other requirements apply for all migration installations. For more information, see Additional Tasks for Migration Installations.

• Migration customers might need to upgrade the database client. In a migration installation case, you might need to upgrade the database client software to a supported version for Siebel CRM 17.0, as noted in the Certifications tab on My Oracle Support. Also update the path to the database client installation in the environment variables. Do this after performing the migration installations. For more information, see About Configuring Siebel CRM. See also Additional Tasks for Migration Installations.

• Additional customer applications are available. In Siebel CRM 17.0, additional customer applications for Siebel Open UI are provided that were previously desupported in Siebel CRM 16.0, but were available for standard interactivity in prior releases. The additional applications are available for new deployments or, through the upgrade process, for existing deployments. For more information, see Siebel Database Upgrade Guide and relevant application-related guides.

• 32-bit versions of the local database and sample database are no longer provided. In Siebel CRM 17.0, the local database and sample database are provided in the 64-bit versions only. The 32-bit versions are no longer provided as JAR files or as selections in Siebel Image Creator. For more information about Siebel Image Creator, see Creating the Siebel Installation Image on the Network.

• Enhanced support for CalDAV and CardDAV. In Siebel CRM 17.0, support for CalDAV and CardDAV is enhanced. For information about enabling this functionality, see Configuring Support for CalDAV or CardDAV Publishing.

• Enhanced support for Desktop Integration Siebel Agent (DISA) and Outlook to Siebel Drag and Drop. In Siebel CRM 17.0, support for Desktop Integration Siebel Agent (DISA) and Outlook to Siebel Drag and Drop has been enhanced. For more information, see Installing Desktop Integration Siebel Agent on Client Computers and Installing Outlook to Siebel Drag and Drop on Client Computers. For more information, see Desktop Integration Siebel Agent Guide.

• Siebel Test Execution is now available. In Siebel CRM 17.0, Siebel Test Execution can now be installed alongside of Siebel CRM. This module, which facilitates automated testing of Siebel CRM, is available through separate packaging than the media for Siebel CRM 17.0. For more information, see Testing Siebel Business Applications.

• Siebel Approval Manager is now available. In Siebel CRM 17.0, the Siebel Approval Manager can now be installed alongside of Siebel CRM. This module, which facilitates tracking of approvals for development work related to Siebel CRM, is available through separate packaging than the media for Siebel CRM 17.0. For more information, see Siebel Approval Manager Guide.

• Oracle LDAP Client is no longer provided. In Siebel CRM 17.0, the Oracle LDAP Client is no longer provided as part of Siebel CRM product media. Obtain it separately from Oracle Software Delivery Cloud.

• Oracle Configuration Manager is no longer installed. In Siebel CRM 17.0, the Oracle Configuration Manager is no longer installed with Siebel CRM. As a result, Siebel installer steps are simplified.

Related Topics

Installation-Related Changes for Siebel CRM 20.x Update

Before You Install Siebel CRM

Before you install Siebel CRM, you must perform the preinstallation tasks. Some of these tasks are described in Siebel Deployment Planning Guide.

1. Review all documented hardware and software requirements.

   For more information, see the installation guidelines in this topic and the information referenced there.

2. Review the worksheet in Siebel Deployment Planning Worksheet or create your own worksheet, and fill it in as you prepare for installing Siebel CRM.

3. Plan and prepare for your deployment.

4. Configure your RDBMS.

   Note: You can configure the RDBMS at any point before you run the Siebel Database Configuration Wizard. Most of the database tasks described in this guide do not apply if you have an existing Siebel database, such as in an upgrade environment.

   This task applies only for Roadmap for Installing Siebel CRM for a New Deployment. For more information, see Planning RDBMS Installation and Configuration and Configuring the RDBMS.

5. Obtain the Siebel media and create a Siebel installation image on the network, from which you will perform installations.

   • Obtain the media for Siebel CRM 17.0.

   • Obtain the media for Siebel CRM 20.9 Update.

   For more information, see Creating the Siebel Installation Image on the Network.

6. Create directories for Siebel CRM software and directories for the Siebel File System.

   For more information, see File and Directory Naming Conventions and Creating the Siebel File System.

7. Create the required Siebel accounts.

   For more information, see Creating the Siebel Service Owner Account.

8. Review all security requirements and take the necessary preparatory steps for either a new installation or a migration installation.

9. Perform any manual migration tasks that might be required prior to performing migration installations for an existing deployment, as described in Additional Tasks for Migration Installations.

   This step applies only for Roadmap for Installing Siebel CRM in a Migration Installation Case (Existing Installation of Siebel CRM 16.x or Earlier).

General Guidelines for Installing Siebel CRM

Follow these general guidelines for your installations:

• Before installing any Siebel CRM module, review all documented requirements, including those found in About Installation Tasks for Siebel CRM and in Requirements for Installing and Configuring Siebel CRM. Also review the information in Siebel Deployment Planning Guide, Siebel Security Guide, other relevant guides on Siebel Bookshelf, and the Certifications tab on My Oracle Support.

• You must plan for the installation and management of the Siebel CRM server modules that you are installing. Review the installation instructions and the installer screens to help you understand the information that is requested by the installers. Such information includes installation locations, languages, application container port numbers, other port numbers, and authentication settings.

• When you install Siebel CRM, as described in Installing Siebel CRM, the installer prompts you to specify valid keystore and truststore files, which are Java files containing certificates.

  The keystore and truststore files are necessary for the application container to use secure two-way communications when connecting with other Siebel CRM modules, as occurs during Siebel Management Console configuration and in normal operation. These files must contain the server certificate chain and an imported CA certificate. Generate your files so that the keystore file references both the private key and the public key, while the truststore file references the public key only. Specify the password that was previously configured to open the certificate files. If you do not configure these files correctly, then you will not be able to configure Siebel CRM, as described in Configuring Siebel CRM Server Modules. See also Siebel Security Guide.

• Various restrictions and guidelines apply regarding which server modules must be installed separately or are recommended to be installed separately from other modules. The installer prevents installation combinations that are not allowed, and warns for installation combinations that are not recommended for production or other end-user environments. For more information, see About Installation Tasks for Siebel CRM.

• You install Siebel Gateway for each Siebel Enterprise. You can install it with Siebel Server or install it separately, depending on your requirements. You can optionally install it on multiple nodes in order to support Siebel Gateway clustering. For more information, see About Installation Tasks for Siebel CRM. See also Configuring the Siebel Gateway Cluster.

• You install Siebel Database Configuration Utilities once, together with the first Siebel Server installed. You must install it with a Siebel Server.

• You install all of the Siebel CRM server modules that you will require to get started, and then you configure them.

  Various requirements apply to the sequence in which you must perform configuration tasks. Security requirements such as for authentication affect many phases of your installation and configuration process, including the overall task sequence. For example, depending on your authentication method, you might need to install the Siebel database for a new deployment before you configure the Siebel CRM server modules using the Siebel Management Console.

• The migration installation and database upgrade cases differ in their requirements for installation sequence, Siebel database tasks, configuration of the Siebel environment, and other post-installation tasks.

  For example, for migration installations, you must perform the migration installation of the Siebel Application Interface first (for your existing installation of SWSE). Then perform the migration installation of the Siebel Gateway and Siebel Server.

• You can install additional instances of Siebel Server and Siebel Application Interface, as needed, for medium-sized or larger deployments.

• After you install Siebel CRM 17.0 for each applicable Siebel CRM module, you install Siebel CRM 20.9 Update.

• You must activate license keys for Siebel CRM, using the License Key Activation utility, after you install a new database, run Incremental Repository Merge (for migration installations), or complete a full database upgrade.

Related Topics

About Installation Tasks for Siebel CRM

Installing and Uninstalling Siebel CRM 20.x Update

Requirements for Installing and Configuring Siebel CRM

About Siebel CRM Releases

Related Books

Siebel Deployment Planning Guide

Siebel Security Guide

Deploying Siebel Open UI

Siebel Performance Tuning Guide

Siebel System Administration Guide

Certifications tab on My Oracle Support

Install & Configure Advisor: Siebel Innovation Pack 2017 (17.0), 2277538.2 (Article ID) on My Oracle Support

Siebel CRM Update Guide and Release Notes on My Oracle Support

Overview of Siebel CRM Server Architecture

The following illustrates a simplified architecture for the server elements in your Siebel deployment, after you have initially installed and configured the software. For a more detailed illustration, see Siebel Deployment Planning Guide.

The Siebel CRM installation and configuration process requires multiple tasks that you perform in a general sequence that depends on your installation case. For more information, see:

• Roadmap for Installing Siebel CRM for a New Deployment

• Roadmap for Installing Siebel CRM 20.x Update for an Existing Installation of Siebel CRM 17.x or Later

• Roadmap for Installing Siebel CRM in a Migration Installation Case (Existing Installation of Siebel CRM 16.x or Earlier)

• Roadmap for Installing Siebel CRM in an Upgrade Case (Existing Database)

Related Topics

Before You Install Siebel CRM

Requirements for Installing and Configuring Siebel CRM

Related Books

Siebel Deployment Planning Guide

Siebel Security Guide

Siebel System Administration Guide

Certifications tab on My Oracle Support

Roadmap for Installing Siebel CRM for a New Deployment

Use this roadmap to guide you in performing the installation and configuration tasks for deploying Siebel CRM, where there is no existing Siebel CRM installation and no existing Siebel database.

The following figure presents a simplified view of the installation and configuration tasks for Siebel CRM server modules for a new deployment.

Note: This illustration does not mention installation or configuration tasks for Siebel Enterprise Cache, Siebel Constraint Engine, or the Siebel Migration application. However, those tasks, where applicable, are implicitly part of this roadmap. The Siebel Constraint Engine is available as a developer preview.

Unless you use another authentication method, a Siebel database must exist before you can configure the Siebel CRM modules, in order to provide an authentication framework for the configuration tasks. You install Database Configuration Utilities with the first Siebel Server.

Note: For each applicable Siebel CRM module, you install Siebel CRM 20.9 Update after you install Siebel CRM 17.0 and before you install the Siebel database or configure the Siebel CRM products. For more information, see Installation-Related Changes for Siebel CRM 20.x Update.

The installation process for Siebel CRM for a new deployment requires multiple tasks that you perform in the following general sequence:

1. Before performing installation and configuration tasks, review all documented requirements.

   See Before You Install Siebel CRM.

2. Create the network images for all applicable releases of Siebel CRM:

   • Create a network image for Siebel CRM 17.0.

   • Create a network image for Siebel CRM 20.9 Update.

   See Creating the Siebel Installation Image on the Network.

3. For the Siebel Enterprise Server, install Siebel CRM 17.0. Then install Siebel CRM 20.9 Update. You can install the following Siebel CRM modules:

   • Siebel Application Interface

   • Siebel Gateway

   • Siebel Server

   • Database Configuration Utilities (install with the first Siebel Server)

   • EAI Connector (optional)

   • Siebel Enterprise Cache (optional)

   • Siebel Constraint Engine (optional, available as a developer preview)

   Note: Some restrictions apply to installing Siebel CRM modules together. For more information, see About Installation Tasks for Siebel CRM.

   As part of installation, you also specify authentication information and port numbers that will be used by your Siebel CRM deployment. The port numbers must be unique on each installation computer or operating system instance.

   See Installing Siebel CRM Server Modules.

4. (Optional) Install Siebel Gateway on additional nodes, if you will use clustering.

   See Configuring the Siebel Gateway Cluster.

5. Verify the installation of Siebel CRM modules.

   See Verifying and Troubleshooting Your Installation.

6. Configure the RDBMS.

   See Configuring the RDBMS.

7. Install the Siebel database.

   This task installs a Siebel database for Siebel CRM. This database contains schema changes, Siebel Repositories, and seed data for Siebel CRM functionality through the current release.

   See Installing the Siebel Database on the RDBMS.

8. Activate the license keys.

   See Activating License Keys.

9. Run the Siebel Management Console and configure your Siebel deployment:

   1. Configure a security profile.

   2. Configure the Siebel Gateway. (Configure the primary Siebel Gateway, for a cluster environment.)

   3. (Optional) Configure the Siebel Gateway cluster.

   4. Configure the Siebel Enterprise.

   5. Configure the Siebel Server.

   6. Configure the Siebel Application Interface.

   7. Perform any other configuration tasks that you require for your deployment.

   See Configuring Siebel CRM Server Modules.

10. Perform additional postinstallation tasks for the Siebel Server.

    See Additional Postinstallation and Configuration Tasks.

11. For Siebel Tools, install Siebel CRM 17.0. Then install Siebel CRM 20.9 Update.

    See Installing Siebel Web Clients and Siebel Tools.

12. For Siebel Mobile Web Clients (or Developer Web Clients), install Siebel CRM 17.0. Then install Siebel CRM 20.9 Update.

    Note: When you install Siebel CRM 20.8 Update or later, Oracle Database SE2 is installed for use with the local database, for Siebel Mobile Web Client.

    See Installing Siebel Web Clients and Siebel Tools.

13. Verify the installation of Siebel Tools and Siebel Mobile Web Clients.

    See Verifying and Troubleshooting Your Installation.

14. (Optional) Install additional Siebel CRM modules. For example:

    • Desktop Integration Siebel Agent (DISA)

    • Siebel Search software

    • Siebel Test Execution

    • Siebel Approval Manager

15. (Optional) Install and configure additional instances of Siebel Gateway, Siebel Server, or Siebel Application Interface if they are required for your deployment, then verify each installation.

16. Perform any remaining postinstallation tasks. For example, install any required third-party products.

    See the Certifications tab on My Oracle Support.

    See Additional Postinstallation and Configuration Tasks.

Related Topics

Roadmap for Installing Siebel CRM 20.x Update for an Existing Installation of Siebel CRM 17.x or Later

Roadmap for Installing Siebel CRM in a Migration Installation Case (Existing Installation of Siebel CRM 16.x or Earlier)

Roadmap for Installing Siebel CRM in an Upgrade Case (Existing Database)

Related Books

Siebel CRM Update Guide and Release Notes on My Oracle Support

Roadmap for Installing Siebel CRM 20.x Update for an Existing Installation of Siebel CRM 17.x or Later

Use this roadmap to guide you in performing the installation tasks for installing Siebel CRM 20.9 Update or the latest Siebel CRM 20.x Update release, where there is an existing installation of Siebel CRM 17.x or later.

Note: For each applicable installed Siebel CRM module of a qualified version, you install only Siebel CRM 20.9 Update. For more information, see Installation-Related Changes for Siebel CRM 20.x Update.

The installation process for Siebel CRM for a new deployment requires multiple tasks that you perform in the following general sequence:

1. Before performing installation and configuration tasks, review all documented requirements.

   See Before You Install Siebel CRM.

   Note: It is recommended to back up the Siebel database before installing Siebel CRM 20.9 Update.

2. Create the network images for all applicable releases of Siebel CRM:

   • Create a network image for Siebel CRM 20.9 Update.

   See Creating the Siebel Installation Image on the Network.

3. For each installed Siebel Enterprise Server module, install Siebel CRM 20.9 Update.

   See Installing Siebel CRM Server Modules.

   Note: As of Siebel CRM 20.3 Update, the installer also runs the PostInstallDBSetup utility. Along with other functions, this utility supports new features using the seamless repository framework. You can also run the optional RepositoryUpgrade utility to support new features since Siebel CRM 17.0 that require repository updates but do not use nonextensible objects. Some other postinstallation tasks for the Siebel database might also apply. For more information, see About Database Updates for Siebel CRM 20.x Update.

4. Verify the installation of Siebel CRM modules.

   See Verifying and Troubleshooting Your Installation.

5. For each installed instance of Siebel Tools and Siebel Mobile Web Client (or Developer Web Client), install Siebel CRM 20.9 Update.

   Note: When you install Siebel CRM 20.8 Update or later, Oracle Database SE2 is installed for use with the local database, for Siebel Mobile Web Client.

   See Installing Siebel Web Clients and Siebel Tools.

6. Verify the installation of Siebel Tools and Siebel Mobile Web Clients.

   See Verifying and Troubleshooting Your Installation.

Related Topics

Roadmap for Installing Siebel CRM for a New Deployment

Roadmap for Installing Siebel CRM in a Migration Installation Case (Existing Installation of Siebel CRM 16.x or Earlier)

Roadmap for Installing Siebel CRM in an Upgrade Case (Existing Database)

About Database Updates for Siebel CRM 20.x Update

Related Books

Siebel CRM Update Guide and Release Notes on My Oracle Support

Roadmap for Installing Siebel CRM in a Migration Installation Case (Existing Installation of Siebel CRM 16.x or Earlier)

Use this roadmap to guide you in performing the installation tasks for deploying Siebel CRM, where there is an existing installation of a prior version. This is the migration installation case.

You use this roadmap when you have an existing Siebel CRM installation of a prior release of Siebel CRM (prior to Siebel CRM 17.0). You must perform the migration installation tasks for your existing installed Siebel CRM software.

Tip: For the upgrade case, where you are upgrading from a Siebel CRM release prior to version 8.1.1 or version 8.2.2, see Roadmap for Installing Siebel CRM in an Upgrade Case (Existing Database) instead. In an upgrade case, you also perform a full database upgrade instead of running Incremental Repository Merge (IRM). In general, this book uses the term migration to refer to a migration installation and uses the term upgrade to refer to a full database upgrade.

The following figure presents a simplified view of the installation and configuration tasks for Siebel CRM server modules for a migration deployment.

Note: This illustration does not mention installation or configuration tasks for security, Siebel Enterprise Cache, Siebel Constraint Engine, or the Siebel Migration application. However, those tasks, where applicable, are implicitly part of this roadmap. The Siebel Constraint Engine is available as a developer preview.

Note: For each applicable installed Siebel CRM module of a qualified version, you install Siebel CRM 20.9 Update after you install Siebel CRM 17.0 as a migration installation and before you run Incremental Repository Merge or configure the Siebel CRM products. For more information, see Installation-Related Changes for Siebel CRM 20.x Update.

This roadmap only summarizes the migration installation process and does not include details about required tasks. For example, you must do the following tasks after performing the migration installation tasks. See also Additional Tasks for Migration Installations.

• Upgrade the database client. You might need to upgrade the database client software to a supported version for Siebel CRM, as noted in the Certifications tab on My Oracle Support. Also update the database client installation path in the defined environment variables. See About Configuring Siebel CRM.

• Run Incremental Repository Merge (IRM). Customers must run Incremental Repository Merge. Before doing this, you must have installed at least one Siebel Server with Database Configuration Utilities and installed Siebel Tools. For more information about Incremental Repository Merge, see Siebel Database Upgrade Guide.

• Reset passwords in Siebel Gateway and on the Siebel Server. Customers must reset any passwords on the Siebel Gateway that were previously encrypted using encryption other than AES. Such passwords are now encrypted using AES. For more information about reencrypting these passwords, see Siebel Security Guide. See also Additional Tasks for Migration Installations.

The installation process for Siebel CRM in a migration installation case requires multiple tasks that you perform in the following general sequence:

1. Before performing installation tasks, review all documented requirements and perform any necessary premigration tasks.

   See Before You Install Siebel CRM and Additional Tasks for Migration Installations.

2. Create the network images for all applicable releases of Siebel CRM:

   • Create a network image for Siebel CRM 17.0.

   • Create a network image for Siebel CRM 20.9 Update.

   See Creating the Siebel Installation Image on the Network.

3. Remove the existing configuration on the Web server computer where you previously installed Siebel Web Server Extension (SWSE).

   Caution: You must perform this task before you perform the migration installation of Siebel Application Interface for the existing installation of SWSE.

   See Additional Tasks for Migration Installations and About Configuring Siebel CRM.

4. For the Siebel Application Interface, install Siebel CRM 17.0 as a migration installation for each existing installation of Siebel Web Server Extension (SWSE). Then install Siebel CRM 20.9 Update.

   As part of installation, also specify authentication information and port numbers that will be used by your Siebel CRM deployment. The port numbers must be unique on each installation computer or operating system instance.

   See Installing Siebel CRM Server Modules.

5. For the remaining Siebel Enterprise Server modules, install Siebel CRM 17.0 as a migration installation for each existing installation. Then install Siebel CRM 20.9 Update. Also perform any necessary postmigration tasks.

   As part of installation, also specify authentication information and port numbers that will be used by your Siebel CRM deployment. The port numbers must be unique on each installation computer or operating system instance.

   Note: When you migrate the Siebel Gateway, you also must provide information to allow your existing configurations to migrate. This includes the port number of the existing Siebel Gateway Name Server as well as some Siebel Application Interface settings that you specified in Roadmap for Installing Siebel CRM in a Migration Installation Case (Existing Installation of Siebel CRM 16.x or Earlier). (If you installed multiple instances of Siebel Application Interface, then specify the settings that apply to the instance of Siebel Application Interface from which you will run Siebel Management Console.)

   See Installing Siebel CRM Server Modules. See also Additional Tasks for Migration Installations.

6. (Optional) Install Siebel Gateway on additional nodes, if you will use clustering.

   See Configuring the Siebel Gateway Cluster.

7. Verify the installation of Siebel CRM modules.

   See Verifying and Troubleshooting Your Installation.

8. For Siebel Tools, install Siebel CRM 17.0 as a migration installation for each existing installation. Then install Siebel CRM 20.9 Update. Also perform any necessary postmigration tasks.

   See Installing Siebel Web Clients and Siebel Tools. See also Additional Tasks for Migration Installations.

9. For Siebel Mobile Web Clients (or Developer Web Clients), install Siebel CRM 17.0 as a migration installation for each existing installation. Then install Siebel CRM 20.9 Update. Also perform any necessary postmigration tasks.

   Note: When you install Siebel CRM 20.8 Update or later, Oracle Database SE2 is installed for use with the local database, for Siebel Mobile Web Client.

   See Installing Siebel Web Clients and Siebel Tools. See also Additional Tasks for Migration Installations.

10. Verify the installation of Siebel Tools and Siebel Mobile Web Clients.

    See Verifying and Troubleshooting Your Installation.

11. Run Incremental Repository Merge on the Siebel database.

    See Siebel Database Upgrade Guide.

12. Run the Siebel Management Console and configure your Siebel deployment:

    1. (Optional) Configure the Siebel Gateway cluster.

    2. Configure the Siebel Application Interface.

    3. Perform any other configuration tasks that you require for your deployment.

    See Configuring Siebel CRM Server Modules.

13. Perform additional postinstallation tasks for the Siebel Server.

    See Additional Postinstallation and Configuration Tasks.

14. (Optional) Install additional Siebel CRM modules. For example:

    • Desktop Integration Siebel Agent (DISA)

    • Install Siebel Search software

    • Siebel Test Execution

    • Siebel Approval Manager

15. (Optional) Install and configure additional instances of Siebel Gateway, Siebel Server, or Siebel Application Interface if they are required for your deployment, then verify each installation.

16. Perform any remaining postinstallation tasks. For example, install or upgrade any required third-party products.

    See the Certifications tab on My Oracle Support.

    See Additional Postinstallation and Configuration Tasks.

Related Topics

Roadmap for Installing Siebel CRM for a New Deployment

Roadmap for Installing Siebel CRM 20.x Update for an Existing Installation of Siebel CRM 17.x or Later

Roadmap for Installing Siebel CRM in an Upgrade Case (Existing Database)

Related Books

Siebel Database Upgrade Guide

Siebel CRM Update Guide and Release Notes on My Oracle Support

Roadmap for Installing Siebel CRM in an Upgrade Case (Existing Database)

Use this roadmap to guide you in performing the installation and configuration tasks for deploying Siebel CRM, where there is an existing Siebel database and you are upgrading from a Siebel CRM release prior to Siebel CRM 8.1.1 or 8.2.2.

Tip: For the migration installation case, where you are upgrading from an existing installation of a prior release of Siebel CRM, see Roadmap for Installing Siebel CRM in a Migration Installation Case (Existing Installation of Siebel CRM 16.x or Earlier) instead. In a migration installation, you also run Incremental Repository Merge instead of performing a full database upgrade. In general, this book uses the term migration to refer to a migration installation and uses the term upgrade to refer to a full database upgrade.

The following figure presents a simplified view of the installation and configuration tasks for Siebel CRM server modules for an upgrade installation case. You install Database Configuration Utilities with the first installed Siebel Server.

Note: This illustration does not mention installation or configuration tasks for Siebel Enterprise Cache, Siebel Constraint Engine, or the Siebel Migration application. However, those tasks, where applicable, are implicitly part of this roadmap. The Siebel Constraint Engine is available as a developer preview.

Note: For each applicable Siebel CRM module, you install Siebel CRM 20.9 Update after you install Siebel CRM 17.0 as a new installation and before you upgrade the Siebel database or configure the Siebel CRM products. For more information, see Installation-Related Changes for Siebel CRM 20.x Update.

This roadmap only briefly mentions the Siebel database upgrade tasks. Before you upgrade the database, you must have installed at least one Siebel Server with Database Configuration Utilities and installed Siebel Tools. For more information about upgrading, see About Installing in Upgrade Environments and see Siebel Database Upgrade Guide.

The installation process for Siebel CRM in an upgrade installation case requires multiple tasks that you perform in the following general sequence:

1. Before performing installation and configuration tasks, review all documented requirements.

   See Before You Install Siebel CRM.

2. Create the network images for all applicable releases of Siebel CRM:

   • Create a network image for Siebel CRM 17.0.

   • Create a network image for Siebel CRM 20.9 Update.

   See Creating the Siebel Installation Image on the Network.

3. For the Siebel Enterprise Server, install Siebel CRM 17.0. Then install Siebel CRM 20.9 Update. You can install the following Siebel CRM modules:

   • Siebel Application Interface

   • Siebel Gateway

   • Siebel Server

   • Database Configuration Utilities (install with the first Siebel Server)

   • EAI Connector (optional)

   • Siebel Enterprise Cache (optional)

   • Siebel Constraint Engine (optional, available as a developer preview)

   Note: Some restrictions apply to installing Siebel CRM modules together. For more information, see About Installation Tasks for Siebel CRM.

   As part of installation, also specify authentication information and port numbers that will be used by your Siebel CRM deployment. The port numbers must be unique on each installation computer or operating system instance.

   See Installing Siebel CRM Server Modules.

4. (Optional) Install Siebel Gateway on additional nodes, if you will use Siebel Gateway clustering.

   See Configuring the Siebel Gateway Cluster.

5. Verify the installation of Siebel CRM modules.

   See Verifying and Troubleshooting Your Installation.

6. Upgrade the Siebel database.

   See About Installing in Upgrade Environments and see Siebel Database Upgrade Guide.

7. Activate the license keys.

   See Activating License Keys.

8. Run the Siebel Management Console and configure your Siebel deployment:

   1. Configure a security profile.

   2. Configure the Siebel Gateway. (Configure the primary Siebel Gateway, for a cluster environment.)

   3. (Optional) Configure the Siebel Gateway cluster.

   4. Configure the Siebel Enterprise.

   5. Configure the Siebel Server.

   6. Configure the Siebel Application Interface.

   7. Perform any other configuration tasks that you require for your deployment.

      See Configuring Siebel CRM Server Modules.

9. Perform additional postinstallation tasks for the Siebel Server.

   See Additional Postinstallation and Configuration Tasks.

10. For Siebel Tools, install Siebel CRM 17.0. Then install Siebel CRM 20.9 Update.

    See Installing Siebel Web Clients and Siebel Tools.

11. For Siebel Mobile Web Clients (or Developer Web Clients), install Siebel CRM 17.0. Then install Siebel CRM 20.9 Update.

    Note: When you install Siebel CRM 20.8 Update or later, Oracle Database SE2 is installed for use with the local database, for Siebel Mobile Web Client.

    See Installing Siebel Web Clients and Siebel Tools.

12. Verify the installation of Siebel Tools and Siebel Mobile Web Clients.

    See Verifying and Troubleshooting Your Installation.

13. (Optional) Install additional Siebel CRM modules. For example:

    • Desktop Integration Siebel Agent (DISA)

    • Siebel Search software

    • Siebel Test Execution

    • Siebel Approval Manager

14. (Optional) Install and configure additional instances of Siebel Gateway, Siebel Server, or Siebel Application Interface if they are required for your deployment, then verify each installation.

15. Perform any remaining postinstallation tasks. For example, install or upgrade any required third-party products.

    See the Certifications tab on My Oracle Support.

    See Additional Postinstallation and Configuration Tasks.

Related Topics

Roadmap for Installing Siebel CRM for a New Deployment

Roadmap for Installing Siebel CRM 20.x Update for an Existing Installation of Siebel CRM 17.x or Later

Roadmap for Installing Siebel CRM in a Migration Installation Case (Existing Installation of Siebel CRM 16.x or Earlier)

Related Books

Siebel Database Upgrade Guide

Siebel CRM Update Guide and Release Notes on My Oracle Support