1. Installation Guide
  2. Installation-Related Changes for Siebel CRM

Installation-Related Changes for Siebel CRM

Siebel Installation Guide describes Siebel CRM product changes and requirements that affect your installation tasks and the overall flow of these tasks.

Documentation Improvements for Siebel CRM

This guide describes using the Siebel CRM installer for releases at or above this release version unless a newer bookshelf has been made available.

This guide will be updated again if the deployment requirements change for later Siebel CRM releases.

The following improvements in Siebel CRM business agility, application deployment and test automation it possible to move to a new release model. The new model provides the ability to deliver new features and innovation faster to our customers. Customers that are on our current release can now embrace frequent innovation updates without the need for major upgrades.

Here are the key benefits:

  • All future features and fixes to be delivered in “Updates”.
  • The updates can contain features as identified from the latest Statement of Direction. For example, updates containing features, coming in 2025 will relate to the "Siebel CRM 2025 Statement of Direction".
  • We are rationalizing the naming process to be more logical and related to the date of release, so an update in April 2025 will simply be called 25.4 applying an update, is not an upgrade (no IRM process or repository changes). Certain updates in the future that contain particular types of features may require IRM to be used. Updates are cumulative.
  • This new model means customers on 25.x and above will never run out of updates for their release.
  • This greatly simplifies the application update process, reducing maintenance costs over the old application upgrade approach.
  • There are no major changes for customers on Siebel CRM 25 and above, other than the fact that customers can look forward to a more continuous delivery in the future.
  • Alignment with agile development and deliver cumulative releases.

Updates and Changes

Release updates for Siebel CRM new features and bug fixes are released as 'Updates'.

We recommend that customers stay current with updates. By doing this they minimize the chance of encountering known bugs and security vulnerabilities. Staying current with Updates reduces the likelihood of requiring separate interim one-off patch fixes which lead to increased maintenance.

Lifetime Support Policy for Siebel CRM

To review the support life of Siebel CRM releases, please refer to the Lifetime Support Policy document.

Release Version Numbering Changes

The current notation for the Siebel CRM software updates is Year. Update is used, such as 25.2. This allows clear indication of the year and month of the update.

Installation Cases

Note the characteristics of the installation cases supported by this installer. More information is provided later in this topic. For new or migration installation cases, you no longer need to install or migrate a base release of a previous version. Existing requirements still apply for installing or upgrading the Siebel database, running Siebel Management Console, and so on. Roadmap topics are provided to guide your actions in each of the installation cases.

In release media or software contexts showing the Siebel version number, the version is often represented as version 25.x, such as version 25.2 for Siebel CRM 25.2. When you install a subsequent Siebel CRM release, the version number of the installed software increments to version 25.3, 25.4, and so on, according to the release installed.

Siebel Database Updates for Update Installations

When you install Siebel CRM to update an existing installation of Siebel CRM that includes Database Configuration Utilities, after installation, the installer runs the Post Installation Database Update (PostInstallDBSetup) utility on the Siebel database. PostInstallDBSetup runs several processes to ensure that the customer database schema, manifest, and seed data are up to date for the current monthly update release. (Database Configuration Utilities is no longer a selectable option for a new installation, but is always installed with Siebel Enterprise Components.) Where applicable, you can also optionally run the RepositoryUpgrade utility to support new features.

See also the information later in this topic about the new database repository and ancestor database repository support files. For more information about the Siebel database, see the following:

  • About Database Updates for Siebel CRM and other relevant content in this guide.

  • Siebel CRM Update Guide and Release Notes on My Oracle Support for the latest Siebel CRM release.

  • For supported Siebel database upgrade paths and instructions, see Siebel Database Upgrade Guide.

Product Media

Media packaging has been optimized and reorganized. You obtain the Siebel CRM product media as ZIP files that require no special utility to prepare for use. Siebel Image Creator utility is no longer provided. For more information, see Creating the Siebel Installation Image on the Network.

Media are reorganized relative to previous releases and include modules not previously part of Siebel CRM media or installation. For example:

  • For all installation cases, only Siebel CRM media of the version installed are required.

  • Media are consolidated for server and client modules (for Microsoft Windows).

  • No separate language media are provided, apart from the ZIP files for installing non-ENU safeboot files.

  • Media for new database repository and ancestor database repository support files are provided for inclusion in Siebel CRM server installations, where required for your deployment.

  • Media for Oracle Database SE2 are provided for inclusion in Siebel Web Client installations (for Siebel Mobile Web Client).

  • Media for Oracle Database Client is automatically installed for both server and client. Starting with Siebel CRM 25.2. The database client is updated via Siebel updates only.

Installation Characteristics

Note the following installation characteristics for Siebel CRM:

  • Each installation of Siebel CRM contains a complete set of binary files. Installations of Siebel CRM no longer require first creating or migrating a base installation using the installer for Siebel CRM 17.0.

  • The installations that you perform are faster and in many cases can be performed in a single installation session.

  • Installations require significantly less disk space. Duplication of language-related files and binary files across multiple components has been reduced or eliminated. For example:

    • (Windows) SIEBEL_ROOT\gtwysrvr\bin, SIEBEL_ROOT\dbsrvr\bin, and SIEBEL_ROOT\eaiconn\bin are now symbolic links to SIEBEL_ROOT\siebsrvr\bin.

    • (LINUX) SIEBEL_ROOT/gtwysrvr/lib, SIEBEL_ROOT/dbsrvr/lib, and SIEBEL_ROOT/eaiconn/lib are now symbolic links to SIEBEL_ROOT/siebsrvr/lib.

  • For all server installations (new, update, or migration installation cases), binaries for all Siebel Enterprise components are included. Individual selections for Siebel Server, Siebel Gateway, Siebel Application Interface, EAI Connector, Database Configuration Utilities, and other components have been removed, because these modules or their equivalents are always installed for Siebel Enterprise Components. Siebel Management Console configuration tasks are not affected by these installation changes. Newly added components are available to be configured if you choose. You must keep track of the modules you are configuring and deploying. Guidelines for nonproduction and production environments are provided here.

    Some components could not be collocated in prior releases, but such limitations no longer apply and the components are now installed together. Note, however, that if you collocate modules (that is, install and deploy them together), you must consider various issues described in Siebel Deployment Planning Guide, including those related to the application container, which is shared when Siebel Server and Siebel Gateway are collocated. Siebel Application Interface uses its own application container even where it is collocated with Siebel Server or Siebel Gateway. Customers must consider such factors, among others, when planning their Siebel CRM deployment topology and before installing and deploying Siebel CRM server modules.

  • Make installation selections that are consistent with your expected topologies or deployment environments, based in part on your security requirements. See also the information about client installation later in this topic. For example:

    • Development or test environments (nonproduction). You can install Siebel Enterprise Components and other modules, optionally including Siebel Web Client or Siebel Tools, or install only a subset of the components selectable in the installer. Some selections are dependent on other selections.

    • Production environments. Install Siebel Enterprise Components behind a firewall. You can also install Siebel Web Client, separately from the server components.

      Note: In a production environment, you install only components meant for user environments. Different security requirements might apply for production versus nonproduction environments. Your security requirements might also vary based on your intended deployment choices (for example, Siebel Application Interface requirements might differ from those for Siebel Server).

  • All modules that you install together in a new installation are collocated and use files and directories that exist in the same file structure or are shared with other modules. If you want to keep new installations separate for different modules, then you must install them into different locations.

  • You can add components or languages to an existing installation of the same version, as follows:

    • To add components to an existing installation of the same version, you start the Siebel CRM installer, select the existing installation, proceed without selecting any languages, select one or more components to add, and then complete this installation task.

    • To add languages to an existing installation of the same version, you start the Siebel CRM installer, select the existing installation, select any additional languages, and then complete this installation task.

  • You can install multiple side-by-side instances of Siebel CRM software on the same computer or operating system instance in separate installation directories. Where multiple instances are installed, when migrating, updating, modifying, or uninstalling an installed instance, you must select the installation directory of the instance to be migrated, updated, modified, or uninstalled.

    Note: As in prior releases, you can configure and use only one Siebel Gateway on each computer or operating system instance, as noted in General Requirements for Installing and Configuring Siebel Enterprise Components.

  • The applicationcontainer directory has been replaced by two directories, as follows:

    • applicationcontainer_external (for Siebel Application Interface)

    • applicationcontainer_internal (for all other Siebel Enterprise components)

    Correspondingly, multiple Apache Tomcat services (for Windows) or processes (LINUX) are created on the same installation, as needed. These changes are made automatically for updates from prior releases.

  • In the Siebel Application Interface installation, Web artifacts for application configurations, which were formerly located in applicationcontainer\webapps\siebel, now map to applicationcontainer_external\siebelwebroot. The siebelwebroot directory contains subdirectories such as lang (for each installed language, such as ENU for U.S. English, FRA for French, and so on), files, fonts, htmltemplates, images, migration, scripts, and smc.

  • You can optionally install new database repository and ancestor database repository support files, as follows:

    • New Database Repository. For installations in a nonproduction environment (such as a development environment), include the applicable media in the Siebel image, then install New Database Repository with Siebel Enterprise Components. Unless an updated version is provided later, it will not be necessary to include this media in subsequent Siebel CRM installations of later releases.

    • Ancestor Database Repository. For installations in a nonproduction environment (such as a development environment), include the applicable media in the Siebel image, then install Ancestor Database Repository with Siebel Enterprise Components. Install this option if you will perform upgrade operations on the Siebel database. After upgrading, it will not be necessary to include this media in subsequent Siebel CRM installations of later releases.

  • Oracle Database Client is provided as part of the Siebel CRM product media. You must include the applicable media in the Siebel installation image to be able to install it.

    • Oracle Database Client is included as a required component when you install Siebel Mobile Web Client, to support Oracle Database SE2.

    • You can also install Oracle Database Client manually to use on Siebel Developer Web Client or Siebel Server, to support connections to Oracle Database or LDAP authentication systems, where applicable.

    Note: Siebel installs and uses only a single instance of Oracle Database Client on a given operating system instance. The same can be used for all configuration.

Client Installation

Note the following client installation characteristics for Siebel CRM:

  • A single installer is now used for both server and client modules. Client modules (Siebel Web Client and Siebel Tools) require the Windows-based installer for installation on Microsoft Windows.

  • For a nonproduction environment, you can install Siebel Web Client or Siebel Tools (on Microsoft Windows) separately or collocated with Siebel Enterprise Components. All modules installed together are collocated in the same installation. For a production environment, install Siebel Web Client or Siebel Tools separately from Siebel Enterprise Components.

    Note: If you install Siebel Web Client or Siebel Tools with Siebel Enterprise Components in a nonproduction environment, then the files and directories for the client modules are created in the installation directory alongside of those for the server modules, which are listed in Verifying Installation for Siebel CRM. If you want to keep new installations separate for different modules, then you must install them into different locations.

  • You can install and configure the Siebel Web Client for use as a Mobile Web Client. Oracle Database SE2 and Oracle Database Client are installed automatically for a previous release.

    You must include the Oracle Database SE2 to be able to install and use the Mobile Web Client. Unless updated versions are provided later, it will not be necessary to include the media in subsequent Siebel CRM update installations of later releases.

    Note: If you uninstall Mobile Web Client, then you can also uninstall Oracle Database SE2. Performing a full uninstallation of Siebel Mobile Web Client or restoring a prior release does not uninstall Oracle Database SE2. If you uninstall Siebel Mobile Web Client and also want to uninstall Oracle Database SE2, see the documentation for this product on Oracle Help Center. See also Siebel Remote and Replication Manager Administration Guide.

  • You can install and configure the Siebel Web Client for use as a Developer Web Client.

Language Installation

Note the following language installation characteristics for Siebel CRM:

  • Language installation is more flexible than in previous releases. For Siebel Enterprise Components and Siebel Web Client, you can optionally install other languages, in a new installation or later in an add-language operation. Installing any non-ENU language requires that you have obtained the safeboot ZIP file that includes that language. See also Creating the Siebel Installation Image on the Network.

  • You can add languages to an existing installation of the same version. For more information, see the installation characteristics described earlier in this topic.

  • For Siebel Tools, only U.S. English (ENU) is installed and configured, regardless of your language selections that might apply to other installed components.

Configuration

Note the following configuration characteristics for Siebel CRM installation and deployment tasks:

  • You can choose whether to provide initial configuration input during Siebel CRM installation, such as to specify application container ports for server modules. If you defer such configuration steps, you can run the Siebel CRM installer again and do them later for the installed software. These tasks must be done within the installer before you can proceed with using Siebel Management Console to complete configuration and deployment tasks.

  • As in previous releases, you can choose which installed components to configure and deploy in your topology. It is not necessary to configure and use every component in every installation.

    You might require deploying multiple instances of certain components (such as Siebel Gateway, Siebel Server, or Siebel Application Interface) to support clustering or load balancing. You must keep track of all the components you configure and deploy for your deployment, and their configured settings.

    Note: Use a worksheet, such as what is provided in Siebel Deployment Planning Worksheet, to capture installation and configuration settings.

  • The TLS port is no longer specified within the installer when you install the Siebel Gateway in a new installation. The Siebel Management Console task for configuring the Gateway profile now includes the TLS Listener Port field.

Uninstallation

Full uninstallation now uses the uninstaller.bat batch file (Windows) or uninstaller script (LINUX), which uninstalls the Siebel CRM software and removes all of the Apache Tomcat services or processes. You can optionally uninstall the current release and restore the installation and configuration of a prior release. For more information, see Uninstalling Siebel CRM.

Limitations

The following are some of the applicable limitations for Siebel CRM installation and deployment:

  • By definition, migration or update installations are only from lower-versioned software releases. For example, you can update Siebel CRM 21.1 or Siebel CRM 22.1 to any Siebel CRM 22.x release.

  • For each Siebel CRM deployment, all installations must be at the same release level (version number).

  • Although each server installation now includes all Siebel Enterprise Components, the Siebel CRM installer does not currently support merging existing separate installations of the same or prior versions into a single installation.

Related Topics

Installing Siebel CRM using the User Interface

About Database Updates for Siebel CRM

Configuring the Siebel Deployment

Planning the Siebel Application Interface Topology

Related Books

Siebel CRM Update Guide and Release Notes on My Oracle Support