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

About Installation Tasks for Siebel Business Applications


Use the Siebel Enterprise Server installer to install the server modules for Siebel Business Applications, including Siebel Gateway, Siebel Server, Database Configuration Utilities, and Siebel Application Interface. Siebel Application Interface replaces the Siebel Web Server Extension (SWSE) from prior releases. Optionally, you can also install EAI Connector, Siebel Enterprise Cache, and Siebel Constraint Engine (which is available as a developer preview). This chapter describes both new installations and migration installations.

Before installing Siebel Business Applications server modules, review the following and perform any necessary preinstallation tasks:

Use the instructions in this chapter to install the following modules:

  • Siebel Application Interface
  • Siebel Gateway
  • Siebel Server
  • EAI Connector (optional)
  • Database Configuration Utilities (install with the first Siebel Server)
  • Siebel Enterprise Cache (optional)
  • Siebel Constraint Engine (optional, available as a developer preview; see also Siebel Product Administration Guide and Article ID 2112562.1 on My Oracle Support)

Various restrictions and guidelines apply regarding which server modules must be installed separately or are recommended to be installed separately from other modules. Note the following restrictions and guidelines for installing these modules:

  • Siebel Application Interface must be installed in a separate installation location or on a different computer or operating system instance from all other modules.
  • Siebel Gateway cannot be installed with either of the following components:
    • Siebel Enterprise Cache
    • Siebel Constraint Engine
  • You cannot install Database Configuration Utilities without also installing a Siebel Server.
  • If you are installing and deploying Siebel Constraint Engine (available as a developer preview), then you must also install and deploy Siebel Enterprise Cache somewhere in your Siebel deployment.
  • Some installation combinations are strongly recommended against. 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 modules that are new in the current release, you must perform a new installation, as the migration installation option is not available.
  • You cannot install another module into an existing installation of the current version, even where such a combination might otherwise be allowed. You must perform a new installation into a different location.

For more information about different ways of deploying Siebel Business Applications server modules, see Installation and Configuration Methods by Deployment Type.

After a new installation, you install the Siebel database and then you configure server modules using the Siebel Management Console. You perform the configuration tasks after installing the current release (Siebel CRM version 17.0) and installing the latest Siebel Patchset release, where available.

Migration installation is analogous to patch installation for an existing installation. You perform migration installations using the same installer that you use for new installations. A migration installation replaces your existing installation with a new installation. However, the installation location, installation languages, server configuration data, and other settings from the existing installation are used for the new installation, where feasible. Before the new installation is performed, the existing installation is moved to a backup location and can no longer be used.

NOTE:  In a migration installation case, you must install Siebel Application Interface before you install any other modules. In the current release, a migration installation of Siebel Application Interface does not copy customer configurations or files from your existing installation of SWSE to the new installation. After completing all of the migration installations, you must configure the Siebel Application Interface.

You must perform any necessary manual migration tasks prior to performing migration installations, as described in Additional Tasks for Migration Installations. For example, you must remove the existing configuration for the SWSE before you install Siebel Application Interface as a migration installation. If you are using data encryption, then you must back up the key file.

For client installation, see Installing Siebel Web Clients and Siebel Tools.

Related Topics

Installation-Related Changes for Siebel Innovation Pack 2017

Installing Siebel Business Applications

Installing Siebel Business Applications in Unattended Mode

Additional Tasks for Migration Installations

Configuring Siebel Business Applications Server Modules

Installing Siebel Web Clients and Siebel Tools

Requirements for Installing and Configuring Siebel Business Applications

About Installing Siebel Business Applications

Siebel Installation Guide for Microsoft Windows Copyright © 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices.