Requirements for Installing and Configuring Siebel CRM

This chapter documents requirements that apply to installing and configuring Siebel CRM software. It includes the following topics:

About Installing Siebel CRM

Each Siebel CRM software release from Oracle has a specific version level, such as Siebel CRM 20.9 Update. You can install Siebel Enterprise Server components, Siebel Application Interface, Siebel Web Client, or Siebel Tools at the current version. This topic contains the following information:

About Documented Requirements

This topic is part of About Installing Siebel CRM.

Before installing any Siebel release, observe all of the documented requirements and review documented installation tasks. See this guide or any updated version of it, the Certifications tab on My Oracle Support, and any other relevant documents on Oracle Help Center, Oracle Technology Network, or My Oracle Support. See also Siebel CRM Update Guide and Release Notes on My Oracle Support.

Note: All Siebel CRM modules used within a given Siebel Enterprise must share the same release level (version number), such as Siebel CRM 20.9 Update. Third-party products must use supported release levels as documented in the Certifications tab on My Oracle Support.

Examples of installation requirements follow:

Before installing Siebel CRM 17.0 for Siebel Enterprise Server (migration installation case), you must shut down services for Siebel Server or Siebel Gateway Name Server, and shut down any running instances of srvrmgr. For Siebel Installation Guides for prior releases, see My Oracle Support, at 1461732.1 (Article ID).
Before installing Siebel CRM 17.0 for Siebel Application Interface (migration installation case), you must stop the Web server used for the previously installed release. For Siebel Installation Guides for prior releases, see My Oracle Support, at 1461732.1 (Article ID).

About Siebel CRM Releases

This topic is part of About Installing Siebel CRM.

Siebel CRM software releases and their various installation methods have evolved significantly. Some previous types of releases no longer apply. The current release is Siebel CRM 20.9 Update. You install this release on top of Siebel CRM 17.x (Siebel Innovation Pack 2017) or later. This book describes the tasks and requirements that apply for the current release.

This guide, the Siebel Installation Guide for the operating system you are using, is for installing the current release. The Siebel Installation Guides describe how to perform both new installations and migration installations.

You install Siebel Gateway, Siebel Server, Database Configuration Utilities, Siebel Application Interface, Siebel Web Client, or Siebel Tools as a new installation of the software or as a migration installation. For more information, see Installation-Related Changes for Siebel CRM 20.x Update, Installation-Related Changes for Siebel CRM 17.0, and related topics.

Note: For an existing installation of a prior version (before Siebel CRM 17.0), running Incremental Repository Merge is required after performing a migration installation. For more information, see About Database Updates for Siebel CRM 20.x Update. Other requirements apply. See also Additional Tasks for Migration Installations.

The following table lists the major installable Siebel CRM modules for Siebel CRM 17.0 and shows which installation methods are supported in order to install the current release. Both new installations and migration installations of Siebel CRM 17.0 use the same installers.

Table Siebel CRM Installers and Applicable Versions

Siebel CRM Module	Installation Methods for Current Release (Siebel CRM 20.9 Update)
Siebel Gateway Siebel Server Database Configuration Utilities EAI Connector Siebel Application Interface	New installation of Siebel CRM 17.0, plus Siebel CRM 20.9 Update, as described in Installing Siebel CRM in a New Installation Migration installation of Siebel CRM 17.0, plus Siebel CRM 20.9 Update, as described in Installing Siebel CRM in a Migration Installation Installation of Siebel CRM 20.9 Update on top of an existing installation of Siebel CRM 17.x or later, as described in Installing Siebel CRM 20.x Update
Siebel Enterprise Cache Siebel Constraint Engine	New installation of Siebel CRM 17.0, plus Siebel CRM 20.9 Update, as described in Installing Siebel CRM in a New Installation Installation of Siebel CRM 20.9 Update on top of an existing installation of Siebel CRM 17.x or later, as described in Installing Siebel CRM 20.x Update
Siebel Web Client	New installation of Siebel CRM 17.0, plus Siebel CRM 20.9 Update, as described in Installing the Siebel Web Client as a New Installation Migration installation of Siebel CRM 17.0, plus Siebel CRM 20.9 Update, as described in Installing the Siebel Web Client as a Migration Installation Installation of Siebel CRM 20.9 Update on top of an existing installation of Siebel CRM 17.x or later, as described in Installing Siebel CRM 20.x Update
Siebel Tools	New installation of Siebel CRM 17.0, plus Siebel CRM 20.9 Update, as described in Installing Siebel Tools as a New Installation Migration installation of Siebel CRM 17.0, plus Siebel CRM 20.9 Update, as described in Installing Siebel Tools as a Migration Installation Installation of Siebel CRM 20.9 Update on top of an existing installation of Siebel CRM 17.x or later, as described in Installing Siebel CRM 20.x Update

Typically, no additional Siebel application configuration tasks are associated with a migration installation. You would not have to run the Siebel Management Console (successor to Siebel Configuration Wizards) to configure a module that was already configured. However, requirements vary for different release, or for using particular functionality. In some cases, for example, you might need to reconfigure a server module after doing a migration installation. In Siebel CRM 17.0, you must configure the Siebel Application Interface after performing migration installations.

Note: The installation tasks and requirements for all future releases are subject to change. You must verify the availability, characteristics, and requirements of any future releases, including any Siebel CRM 20.x Update releases, that might also be covered by this guide (or updated versions of it) or by other documentation.

Related Books

For Siebel Installation Guides for prior releases, see My Oracle Support, at 1461732.1 (Article ID).

For Siebel CRM 20.x, 19.x, or 18.x Update releases, see also Siebel CRM Update Guide and Release Notes on My Oracle Support.

For the readme documents for individual Siebel Patchset releases for Siebel CRM 17.x and earlier, see Siebel Patchset Installation Guide for Siebel CRM, 1614310.1 (Article ID) on My Oracle Support. For more information about Siebel Patchset releases, see 1600520.1 (Article ID) on My Oracle Support.

For versions of Siebel Maintenance Release Guide for prior releases, see 880452.1 (Article ID) on My Oracle Support for version 8.1.1.x or see 1441523.1 (Article ID) for version 8.2.2.x.

About Installing in Upgrade Environments

This topic is part of About Installing Siebel CRM.

When you install Siebel CRM, you might be creating a new deployment or you might be installing updated software to be used in a deployment that is being upgraded from a previous release of Siebel CRM, such as an upgrade from version 8.0 to the current version. A deployment that is being upgraded is sometimes called an upgrade environment. You install your new Siebel CRM software before upgrading the Siebel database.

In some cases, you can upgrade the Siebel database directly to the current release. For detailed information about upgrading the Siebel database, and about tasks that you perform before the installation or upgrade, see Siebel Database Upgrade Guide. See also any relevant documents on Oracle Technology Network or My Oracle Support.

Note: Review all of the applicable documentation before you install or upgrade.

For IBM DB2 for z/OS, see relevant parts of Planning RDBMS Installation and Configuration and see Siebel Database Upgrade Guide for DB2 for z/OS.

Caution: As part of installing Siebel CRM software in an upgrade environment, in general, you do not perform any database-related tasks described in this guide.

In an upgrade environment:

You do install the Siebel Enterprise Server module called Database Configuration Utilities on a Siebel Server, as described in Installing Siebel CRM Server Modules.
You do not create the database instance on the RDBMS, as described in Configuring the RDBMS. (After the upgrade is complete, you might have to modify database parameters for your RDBMS platform to match settings described in that chapter.)
You do not perform the tasks described in Installing the Siebel Database on the RDBMS.
Certain installation and configuration requirements associated with authentication for using Siebel Gateway and Siebel Management Console that apply for new deployments do not apply in this case. For details, see Requirements for Siebel Gateway Authentication.

For more information about how to use this guide in an upgrade installation case, see Roadmap for Installing Siebel CRM in an Upgrade Case (Existing Database).

After installing and upgrading, you might have to perform additional tasks. Some tasks that might apply are described in Siebel Application Deployment Manager Guide, Siebel System Administration Guide, or Siebel Database Upgrade Guide.

As of Siebel CRM 17.0, the 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. Siebel Database Upgrade Guide describes the Siebel Migration application. See also Preparing to Run Siebel Server Components.

When you install Siebel CRM in some upgrade scenarios, you might in some cases be able to install different versions of a Siebel CRM module on the same computer or operating system instance, if this scenario is valid for particular modules and might be helpful to you. For more information, see Planning to Install Multiple Instances of Siebel CRM.

After you install Siebel CRM 17.0, you install Siebel CRM 20.9 Update. Install Siebel CRM 20.9 Update before you initiate the upgrade process. After upgrading, you can install additional Siebel releases as they become available.

Caution: Do not install any additional Siebel release until the upgrade is complete.

For information about types of Siebel CRM releases, see About Siebel CRM Releases.

Instructions in this guide apply both for new installations and upgrades, except where noted.

About Language Installation

This topic is part of About Installing Siebel CRM.

It is strongly recommended that you install and deploy, or at least install, all of the languages that you expect to require. For more information about installing and deploying languages, see Installing and Deploying Siebel CRM with Multiple Languages.

Planning Your Siebel Deployment

You must plan where to install the various Siebel CRM modules on your servers. This topic contains the following information:

Preparing the Hardware and Planning Topologies

This topic is part of Planning Your Siebel Deployment.

Verify that the hardware that you have chosen meets all of the requirements for running your Siebel applications as well as the required third-party software. Verify also that the hardware is able to support the RDBMS and the Siebel database, the Siebel File System, Siebel Gateway, Siebel Server, Siebel Application Interface, and other Siebel CRM modules. Also plan to support Siebel Tools developer workstation computers and Siebel Mobile Web Client computers, where applicable, as well as mobile devices if you are deploying Siebel Mobile applications.

Consider running specialized components on dedicated computers. Whether you do so depends on considerations that include available resources, overall load, performance, security, and so on.

In general, it is assumed that, for security purposes, your computer resources are not shared between Siebel CRM and other applications or systems that are not related to supporting your Siebel CRM deployment.

Record the computer names and installation directory names that you decide on in your copy of the worksheet in Siebel Deployment Planning Worksheet.

Related Books

Siebel Deployment Planning Guide

Siebel Performance Tuning Guide

Siebel Security Guide

Certifications tab on My Oracle Support

Planning Disk Space and Configuration Requirements

This topic is part of Planning Your Siebel Deployment.

Before you install, you must anticipate your disk space requirements for each installable Siebel CRM module. Each Siebel installer displays the required disk space for the installed software before files are copied. Also anticipate the disk space required for Siebel image directories. For more information, see Creating the Siebel Installation Image on the Network.

Siebel installers also have temporary disk space requirements, as described in Managing Temporary Disk Space Required by Siebel Installers and Wizards.

The Siebel CRM architecture is designed to scale across multiple application server computers to meet the needs of large, complex deployments. For assistance in capacity planning and sizing hardware platforms for Siebel CRM server modules, contact your Oracle sales representative or Oracle Advanced Customer Services to request assistance from Oracle’s Application Expert Services.

The number of server computers, the CPU resources, and the memory resources required for operating Siebel CRM increases with the number and types of users and the deployed Siebel CRM modules.

In addition to the disk space required for installation, computers operating Siebel Remote components require 1 MB of usable disk space for each mobile user. Oracle recommends using high-performance and high-availability storage solutions, as appropriate, for Siebel CRM deployments, particularly for high-capacity deployments. Oracle also recommends using high-performance disks or fault-tolerant disk arrays for all server computers, Siebel File System servers, and database servers.

Hardware or software high-availability disk configurations are critical for Siebel Remote servers, Siebel File System servers, and database servers. It is recommended that you configure other Siebel Server computers, Siebel Application Interface computers, and other components to use hardware or software RAID level 1 or comparable configurations.

High-availability solutions, such as clustering, are also recommended on critical components and can be used in conjunction with applicable high-availability storage solutions. Clustering is critical for high availability of the Siebel Gateway, Siebel Remote servers, and the database server. Clustering is also recommended for any Siebel Server computer that is not load-balanced.

Customers are responsible for making sure that clustering is supported on each server component and that the Siebel Server hardware operates with the supported server operating systems and clustering solutions. For supported operating systems, see the Certifications tab on My Oracle Support. For more information, see 1492194.1 (Article ID) on My Oracle Support.

It is strongly recommended to configure Siebel Gateway clustering using Siebel Management Console, as described in Configuring the Siebel Gateway Cluster.

For more information about some of these recommendations, see Siebel Deployment Planning Guide. See also Siebel Performance Tuning Guide.

Planning RDBMS Installation and Configuration

This topic is part of Planning Your Siebel Deployment.

Note the following guidelines for installing and configuring the Relational Database Management System (RDBMS) on which you will create the Siebel database.

For more information about configuring the RDBMS, see Configuring the RDBMS. For more information about configuring the Siebel database after installing Siebel Enterprise Server, see Installing the Siebel Database on the RDBMS.

Make sure that this release of Siebel CRM supports the exact version of your chosen RDBMS, as specified in the Certifications tab on My Oracle Support, and that the RDBMS has been installed on its designated server. This database server will hold the database tables containing your business data, such as sales (personnel, territories, opportunities, and activities), marketing, and customer service information. It will also contain Siebel Repository tables, which are used both for developing and for operating Siebel applications.
Verify that the network name of the server that will support the Siebel database is properly recorded in your copy of the worksheet in Siebel Deployment Planning Worksheet.
Installing the Siebel database, as described in Installing the Siebel Database, creates a ODBC data source name, which might be needed to provide authentication for the Siebel Management Console configuration process, as described in Configuring Siebel CRM Server Modules.
When you configure the Siebel Enterprise, the Siebel Management Console creates the ODBC data source name, using the name SiebelEnterpriseName_DSN. For example, if your Siebel Enterprise name is sieb17, then the ODBC data source name will be sieb17_DSN. If a data source using this name exists, then it is overwritten. Using this pattern, determine what your ODBC data source name will be and record it in your copy of the worksheet in Siebel Deployment Planning Worksheet.

Note: In most cases, do not change any of the default ODBC settings or parameters. Otherwise, you will encounter problems using the ODBC. For example, setting OptimizeLongPerformance to enable corrupts all of the scripts in the Siebel Repository during import or export processes. For information about verifying the ODBC data source for your RDBMS platform, see Verifying the ODBC Data Source. See also Troubleshooting the ODBC Data Source Connection.
Siebel Web Client and Siebel Tools installers also create ODBC data source names during the installation. The naming convention is different than ODBC data source names created by the Siebel Management Console. For more information, see Installing Siebel Web Clients and Siebel Tools.

About Database Code Pages and Locale Support

In a database environment that is enabled for Unicode, you can install any of the available Siebel language packs.

In a database environment that is not enabled for Unicode, however, you must consider the correlation of the language packs that you want to install and the characters supported by your database code page. For example, in a Western European code page database, you can only install Western European language packs, such as U.S. English, French, Spanish, or German language packs. In a Japanese code page database, you can only install Japanese or U.S. English language packs. The installed languages and the code page of the operating system on which your Siebel Server runs must match those of your Siebel database instance.

Related Books

Siebel Global Deployment Guide

Certifications tab on My Oracle Support

For Siebel CRM language support, Unicode support, and legacy code page support, see 1513102.1 (Article ID) on My Oracle Support.

Planning Database Connectivity

Use the ODBC driver versions listed in the Certifications tab on My Oracle Support for your chosen RDBMS for Siebel Servers, Siebel Tools, and Siebel Developer Web Clients (if applicable). Make sure that ODBC connectivity uses TCP/IP as the transport layer protocol for Siebel Servers, Siebel Tools, and Siebel Developer Web Clients.

How to Use This Guide If Your Database Is IBM DB2 for z/OS

This guide describes installation of Siebel CRM modules for each supported RDBMS, with the exception of IBM DB2 for z/OS. (This database product was formerly referred to in some Siebel Bookshelf documentation as IBM DB2 UDB for z/OS and OS/390.) The Siebel Bookshelf is available on Oracle Technology Network (OTN) and Oracle Software Delivery Cloud. It might also be installed locally on your intranet or on a network location.

Customers for IBM DB2 for z/OS require this guide (Siebel Installation Guide for the operating system you are using) and Implementing Siebel Business Applications on DB2 for z/OS. Both of these guides are available on the Siebel Bookshelf.

Note: In this guide, Configuring the RDBMS and Installing the Siebel Database on the RDBMS do not apply to customers using DB2 for z/OS. Instead, see Implementing Siebel Business Applications on DB2 for z/OS for database-related content. If you are upgrading on this platform, then see also Siebel Database Upgrade Guide for DB2 for z/OS. For information about relevant requirements related to authentication for the Siebel Gateway, see Requirements for Siebel Gateway Authentication.

Implementing Siebel Business Applications on DB2 for z/OS includes, but is not limited to, topics such as special security issues for this RDBMS, installing the Siebel schema, performance guidelines for use of this RDBMS with Siebel CRM, and specific procedures for moving data from development to production. Also consult all of the other applicable Siebel Bookshelf documentation, such as Siebel Security Guide.

Managing Temporary Disk Space Required by Siebel Installers and Wizards

This topic is part of Planning Your Siebel Deployment.

Siebel installer programs, the Siebel Image Creator utility, and other programs all require the use of temporary disk space while operating. Disk space required varies by operating system. The location of temporary directories is specified using the TEMP and TMP environment variables. Set these variables the same: to a valid existing directory that contains adequate space.

It is recommended that you periodically clear out the temporary directory that you are using. You might have to do this as part of resolving installer or wizard problems.

On Microsoft Windows, the temporary directory used by default is C:\Documents and Settings\username\Local Settings\Temp.

The minimum disk space figures provided in this topic are general guidelines only. The specific amount of temporary disk space needed by a particular installation operation varies. If there is insufficient disk space, then the installer will notify you that more disk space is needed.

The user running the installer or wizard must have privileges that include write permission for the temporary directory.

Managing Temporary Disk Space Required by Siebel Installers and Wizards shows the minimum disk space required by Siebel installers and wizards (by operating system), along with the default temporary directory locations.

Table Temporary Disk Space Required by Siebel Installers and Wizards

Operating System	Minimum Required Space	Default Location
Windows	65 to 100 MB	System drive (usually `C:`)
AIX	200 MB	`/tmp`
HP-UX	240 MB	`/var/tmp`
Linux	200 MB	Home directory for user
Oracle Solaris	115 MB	`/var/tmp`

About The Language in Which Siebel Installers and Wizards Run

This topic is part of Planning Your Siebel Deployment.

When you start Siebel installer programs, the Siebel Image Creator utility, or the Siebel Database Configuration Wizard, the language in which the program runs (the user interface text) is determined by the language for the locale of your operating system, where this language and locale are supported for Siebel CRM and for the installer, utility, or wizard.

Installers for Siebel CRM server modules and client modules are based on Oracle Universal Installer and run in the current language corresponding to the regional and language options settings on the server or client computer, where the current language is one of the following: U.S. English, French, German, Italian, Brazilian Portuguese, Spanish, Japanese, Korean, Chinese Simplified, or Chinese Traditional. For any other current language setting, the installer runs in U.S. English.

Siebel Image Creator and the Siebel Database Configuration Wizard also use the current language corresponding to the regional and language options setting. The programs can run in all of the languages corresponding to the available Siebel language packs, except Arabic, Hebrew, Polish, Russian, Thai, or Turkish. If the current language is one of these or any language not supported for Siebel CRM, then the program runs in U.S. English.

For the Siebel installers, Database Configuration Wizard, and Siebel Image Creator, in order to change the user interface language, you must change the current operating system language and locale. .Make sure that the locale of your operating system is set to the desired choice of your language. The language that you select must be one of those supported for Siebel CRM, as described earlier.

Note: If a supported locale that you intend to use does not exist on the supported operating system, then use another existing supported locale, so that you can proceed with installation and initial configuration in a familiar language; for example, DE_DE.UTF-8 for German (on AIX), en_US.UTF-8 for U.S. English (on Oracle Solaris), and so on. For a list of supported locales for your UNIX operating system, see Specifying the Locale for Your UNIX Operating System.

For information about installing language packs for Siebel CRM, see the applicable installation task topic and see Installing and Deploying Siebel CRM with Multiple Languages.

Planning to Install Multiple Instances of Siebel CRM

This topic is part of Planning Your Siebel Deployment.

This topic describes issues in installing multiple instances of similar or dissimilar versions of Siebel CRM on the same computer or operating system instance.

Installing Multiple Instances of the Same Version of Siebel CRM

By default, the Siebel installers automatically install Siebel CRM software in directories with unique names that will not conflict with other Siebel CRM modules that you install on the same computer or operating system instance. To install another instance of the same version of a module on a single computer or operating system instance (where applicable), specify a custom installation path.

However, installing multiple instances of some modules might cause problems. For example:

You cannot install multiple instances of the same version of Siebel Gateway on the same computer or operating system instance.
You must take care to avoid conflicts in port number usage whenever you install or configure multiple Siebel CRM modules or multiple instances on the same computer or operating system instance. You specify multiple port numbers when you install and configure Siebel CRM modules.
Restrictions apply for installing multiple instances of Siebel Application Interface. You must install them in different locations and assign unique port numbers for the application containers. For details, see Requirements for Installing and Configuring the Siebel Application Interface.

For important related considerations, see also About Installing Siebel CRM and Preparing the Hardware and Planning Topologies.

Note: In this context, same version refers to multiple installations of a given release, such as Siebel CRM 20.9 Update.

All Siebel CRM server modules that you install together on the same computer or operating system instance are installed into the same root directory (such as C:\Siebel on Microsoft Windows or /Siebel on UNIX), except in the case described in the note that follows. These modules might include Siebel Gateway, Siebel Server, Database Configuration Utilities, EAI Connector, and Siebel Enterprise Cache. Restrictions and guidelines apply to collocating Siebel CRM modules, as noted in About Installing Siebel CRM. See also File and Directory Naming Conventions.

As an example of restrictions for collocating Siebel CRM modules, you must install Siebel Application Interface in a different directory than other Siebel CRM modules, or on a different computer or operating system instance.

If you have already installed Siebel CRM modules (Siebel Enterprise Server) for the current release, and you require additional Siebel CRM modules (for example, Siebel Gateway is already installed and you want to install a Siebel Server), then you can install a new instance of Siebel Enterprise Server software, with the modules you require. You must install the new instance in a different directory or on a different computer or operating system instance. Then install Siebel CRM 20.9 Update for each installed instance. For more information about options in this situation, see General Requirements for Installing and Configuring Siebel Enterprise Server Modules and other relevant topics.

Each installed instance of Siebel CRM software, whether on the same or on a different computer or operating system instance, must be configured in order to operate it in your Siebel deployment. Configuration requirements are different for new installations and migration installations. A new installation must be configured using Siebel Management Console, by configuring and applying profiles for each module. Depending on your existing deployment, in a migration installation case involving multiple instances of a Siebel CRM module, you might have a choice about whether to install and configure each additional instance of a new module as a new installation or as a migration installation. Specific requirements vary by Siebel CRM module and by installation case.

If you install additional instances of Siebel Application Interface (when the primary instance is operational, whether a new or migration installation), then some additional steps might be necessary to deploy these instances. These steps involve editing the applicationinterface.properties file, which is located in SIEBEL_AI_ROOT\applicationcontainer\webapps. Copy the following parameters and their values from applicationinterface.properties on the primary instance of Siebel Application Interface into the [Application Interface] section of the corresponding file on the new instance: Password, UserName, and CGHostURI. For each new Siebel Application Interface instance, after you save the updated file, restart the application container. Then you can apply a profile to deploy this instance.

Installing Multiple Instances of Different Versions of Siebel CRM

Multiple versions of Siebel CRM modules can be installed on the same computer or operating system instance. Sometimes you might have to do this as part of some upgrade scenarios.

If you install multiple versions of Siebel Gateway on the same computer or operating system instance, then you must install them in different directories and assign unique port numbers for the application containers.
If you install multiple versions of Siebel Server on the same computer or operating system instance, then you must install them in different directories and assign unique port numbers for the application containers.
Multiple instances of different or dissimilar versions of Siebel Application Interface do not apply in the current release, because it is the first release for this module.

Related Books

Siebel Database Upgrade Guide

Specifying the Locale for Siebel CRM

This topic is part of Planning Your Siebel Deployment.

When a Siebel application component (Siebel Server, Siebel Tools, or Siebel Developer Web Client) opens a connection to the Siebel database, the locale is automatically determined on a per-session basis for the connection. This setting overrides settings that might be defined elsewhere.

Do not explicitly set the NLS_LANG (Oracle-specific), LANG, or SIEBEL_CODEPAGE environment variables for Siebel CRM. Siebel environment setup files such as siebenv.csh (for C shell) or siebenv.sh (for Bourne or Korn shell) might set these variables, but these settings are not used for the database connection. The settings in the siebenv.csh or siebenv.sh files affect any software that runs in the Siebel environment controlled by those files (except for Siebel CRM).

For deployments using Oracle Database, the NLS_LANG variable determines default behaviors that can be overridden using other variables, such as NLS_SORT, that are not set automatically for Siebel CRM using an Oracle Database connection. Therefore, settings that you make for NLS_SORT will affect any software that runs in the Siebel environment (including Siebel CRM).

Caution: For development environments, Siebel CRM supports only binary sort order. Therefore, for Oracle Database, when you are setting the locale for your development environment, either do not set NLS_SORT at all, or set it to BINARY. In production environments, this restriction does not apply. (In this guide, sort order and collation sequence are used interchangeably, even though these terms might not always mean the same thing.)

You can explicitly set the locale to be used by a Siebel Server or Application Object Manager component by setting the Locale Code parameter.

Related Books

Siebel Applications Administration Guide

Siebel Global Deployment Guide

Specifying the Locale for Your UNIX Operating System

This topic is part of Planning Your Siebel Deployment.

To successfully run Siebel CRM on UNIX, you must configure the appropriate locales on your operating system for the language that you will run the applications in. In some cases, you might have to install additional content on your system in order to support the locale.

For LANG or LC_ALL settings on different UNIX operating systems for supported languages or locales, see Specifying the Locale for Your UNIX Operating System.

Note: The setting of the LANG environment variable does not affect database connections for Application Object Manager components for Siebel CRM. However, it does affect database connections used by other Siebel components.

Table Lang or LC_ALL Parameter Settings for Supported Languages or Locales

Language or Locale Siebel Language Code	LANG or LC_ALL Parameter Setting for Each Supported UNIX Operating System
	AIX	HP-UX or Linux	Oracle Solaris
Arabic (Saudi Arabia) ARA	AR_SA.UTF-8	ar_SA.utf8	ar_SA.UTF-8
Chinese (Simplified) CHS	ZH_CN.UTF-8	zh_CN.utf8	zh_CN.UTF-8
Chinese (Traditional) CHT	ZH_TW.UTF-8	zh_TW.utf8	zh_TW.UTF-8
Czech CSY	CS_CZ.UTF-8	cs_CZ.utf8	cs_CZ.UTF-8
Danish DAN	DA_DK.UTF-8	da_DK.utf8	da_DK.UTF-8
Dutch NLD	NL_NL.UTF-8	nl_NL.utf8	nl_NL.UTF-8
English (United States) ENU	EN_US.UTF-8	en_US.utf8	en_US.UTF-8
Finnish FIN	FI_FI.UTF-8	fi_FI.utf8	fi_FI.UTF-8
French (France) FRA	FR_FR.UTF-8	fr_FR.utf8	fr_FR.UTF-8
German (Germany) DEU	DE_DE.UTF-8	de_DE.utf8	de_DE.UTF-8
Hebrew HEB	IW_IL.UTF-8	iw_IL.utf8	iw_IL.UTF-8
Italian ITA	IT_IT.UTF-8	it_IT.utf8	it_IT.UTF-8
Japanese JPN	JA_JP.UTF-8	ja_JP.utf8	ja_JP.UTF-8
Korean KOR	KO_KR.UTF-8	ko_KR.utf8	ko_KR.UTF-8
Polish PLK	PL_PL.UTF-8	pl_PL.utf8	pl_PL.UTF-8
Portuguese (Brazil) PTB	PT_BR.UTF-8	pt_BR.utf8	pt_BR.UTF-8
Portuguese (Portugal) PTG	PT_PT.UTF-8	pt_PT.utf8	pt_PT.UTF-8
Russian RUS	RU_RU.UTF-8	ru_RU.utf8	ru_RU.UTF-8
Spanish (Modern) ESN	ES_ES.UTF-8	es_ES.utf8	es_ES.UTF-8
Swedish SVE	SV_SE.UTF-8	sv_SE.utf8	sv_SE.UTF-8
Thai THA	TH_TH.UTF-8	th_TH.utf8	th_TH.UTF-8
Turkish TRK	TR_TR.UTF-8	tr_TR.utf8	tr_TR.UTF-8

Setting Permissions and Ownership

This topic is part of Planning Your Siebel Deployment.

This topic provides information about permissions and ownership for user accounts that will perform installations.

To install server-based Siebel CRM modules, you must be a nonroot user. You cannot install these modules as the root user using Oracle Universal Installer software. This requirement applies to all new installations of Siebel Enterprise Server and Siebel Application Interface. It also applies to all migration installations and to all installations of Siebel CRM 20.7 Update.
For existing installations of Siebel CRM version 8.1.1.7 or earlier that were originally installed as the root user (using InstallShield installers), you can use the chown command to change the owner for all of the installation directories and files to a nonroot user in order to perform the migration installation.
After installing as a nonroot user, you can optionally change the installation owner back to the root user. Note that the same requirement will apply every time that you install a new release, including installations of Siebel CRM 20.x Update releases. In general, it is recommended not to change the owner back to the root user, unless your deployment requires it.
Before you install each server module discussed in this guide, set umask to 027 on the installation directory of that computer. Changing this setting eliminates other permissions, including group write permissions. This action also sets the default permissions, so that all of the files and directories that are created afterwards have rwxr-x--- permissions. The Siebel service owner account must have all permissions. However, the group must have read and execute (for directory access) permissions only. See also Creating the Siebel Service Owner Account.

Installing Siebel CRM from a Remote Server Computer

This topic is part of Planning Your Siebel Deployment.

If you are installing server-based Siebel modules in GUI mode from a remote server computer, then you must set the DISPLAY variable to display the Java installer user interface on your local computer. For example, depending on your shell:

export DISPLAY=mycomputer:0.0

or:

setenv DISPLAY mycomputer:0.0

In this command, mycomputer is the computer name or IP address of your local workstation computer.

You might be able to test that your display works correctly on your local computer by entering:

xclock

You can also verify the IP address by entering:

echo $DISPLAY

If the clock does not appear on your local computer, then issue the following command on your local computer:

xhost +

If you are using X-connectivity software to access the UNIX computer from a Windows computer, then the installer might fail or stop responding. If this is the case, then try using a later version of the X-connectivity software.

Note: For additional information, refer to vendor or other documentation for your UNIX operating system, or contact your system administrator for assistance.

Restrictions on Host Names for Siebel Gateway and Siebel Server

This topic is part of Planning Your Siebel Deployment.

See also Restrictions on Names for Siebel Enterprise and Siebel Server, which is about names for Siebel entities that you specify during configuration.

This topic describes restrictions for host names for server computers on which you will install Siebel Gateway or Siebel Server.

The Siebel Gateway name is defined automatically based on the host name of the server computer. However, problems might arise during configuration of Siebel CRM modules unless the following requirements are observed:

Host names for Siebel Gateway or Siebel Server must not include dashes (hyphens). It is recommended that you use an underscore if a separator character is required. For example, host_sba17 is acceptable, but host-sba17 is not.

Note: A dash might not cause problems in every scenario, but problems have been observed in many specific scenarios, as noted in 477993.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Alert 1067. (Workarounds described in the alert, involving substitute .scm files, do not apply to the current software version.) In any case, similar restrictions for naming a Siebel Enterprise or Siebel Server are noted in Restrictions on Names for Siebel Enterprise and Siebel Server.
The host name for Siebel Gateway must be no longer than 15 characters.
The Siebel Management Console task for configuring the Siebel Gateway displays an error if the host name you enter is longer than 15 characters.
(Siebel Management Console tasks for configuring the Siebel Enterprise and the Siebel Server also validate that the name of the Siebel Gateway, which would have been previously configured, is no longer than 15 characters.)
In general, it is recommended not to define the host name for the Siebel Gateway computer to include domain information, as might be common in some UNIX environments. The entire host name is subject to the 15-character limit mentioned previously.

Restrictions on Names for Siebel Enterprise and Siebel Server

This topic is part of Planning Your Siebel Deployment.

This topic describes restrictions to observe when planning the names that you will give the Siebel Enterprise and Siebel Server instances during configuration of Siebel CRM software.

Siebel Management Console tasks that specify or refer to the Siebel Enterprise name or the Siebel Server name validate for some of the following requirements, such as the 12-character limit. User input is validated in the Siebel Management Console. Observe all of the documented restrictions regardless of validation behavior.

Siebel Enterprise Naming Restrictions

The following restrictions apply to naming a Siebel Enterprise:

The name must be no longer than 12 characters.
The name cannot be server or enterprise. (A name such as enterprise1 is acceptable.)

Siebel Server Naming Restrictions

When planning the names of Siebel Server instances within a Siebel Enterprise, the following restrictions apply:

Names must contain only alphabetic characters, numerals, underscores, or a combination thereof. For example, do not use dashes (hyphens) in naming Siebel Server instances.
Names must lead with an alphabetic character.
Names must be unique within the Siebel Enterprise.
Names must be no longer than 12 characters.
Names cannot be server or enterprise. (A name such as server1 is acceptable.)

File and Directory Naming Conventions

This topic is part of Planning Your Siebel Deployment.

Use lowercase for all of the file names, directory names, path names, parameters, flags, and command-line commands, unless you are instructed otherwise.

Directory names or file names cannot contain special characters, including periods, apostrophes, accents, number (pound or hash) signs, ampersands, or spaces. Underscores are acceptable. Spaces are not allowed for server installs on Windows (though the operating system might otherwise allow it). Spaces are acceptable for Siebel Web Client or Siebel Tools installs (on Windows).

How This Guide Refers to Your Installation Directories

This guide uses the following conventions to refer to the installation directories either created by the installers or to which users navigate to access files and executable programs.

Note: The default installation directories shown in this guide for Siebel Enterprise Server modules, Siebel Application Interface, Siebel Web Clients, and Siebel Tools are those for new installations of the current release, Siebel CRM 17.0. Alternatively, your products might have been installed in different installation directories, such as if you had originally installed them for a prior release.

$SIEBEL_ROOT. Generally, this refers to the main directory in which software for each Siebel Enterprise Server module has been installed. The installers for the Siebel Enterprise Server modules install into the top-level directory, such as /Siebel, although the directory where you install might be different, such as /export/home/Siebel. Generally, this directory is what $SIEBEL_ROOT represents in this guide.

Note: $ SIEBEL_ROOT might also represent the value of the SIEBEL_ROOT environment variable, which usually corresponds to a module-specific installation directory, such as /Siebel/siebsrvr for Siebel Server.

$ORACLE_HOME. This refers to the same directory as represented by $SIEBEL_ROOT.

$SIEBEL_HOME. The installation or root directory for Siebel CRM software in general (such as /Siebel), or of a specific module such as Siebel Gateway or Siebel Server (such as /Siebel/siebsrvr for Siebel Server), depending on the context. Many scripts contain variables with this name; its meaning is most often derived from the context.

$SIEBSRVR_ROOT. The installation or root directory for Siebel Server, such as /Siebel/siebsrvr.

$SIEBEL_SERVER_ROOT. This term is sometimes used within executable programs, such as the siebel_server script, as a synonym for $SIEBEL_HOME.

$SIEBEL_GATEWAY_ROOT. The installation or root directory for Siebel Gateway, such as /Siebel/gtwysrvr.

DBSRVR_ROOT. The directory into which you install Siebel Database Configuration Utilities (also called the Siebel Database Server), such as /Siebel/dbsrvr (on a Siebel Server computer).

SIEBEL_AI_ROOT. The directory into which you install Siebel Application Interface, such as /Siebel_AI.

SIEBEL_CLIENT_ROOT. The directory into which you install Siebel Mobile Web Client or Siebel Developer Web Client, such as C:\Siebel\Client or a similar location.

SIEBEL_TOOLS_ROOT. The installation or root directory for Siebel Server, such as C:\Siebel\Tools or a similar location.

Creating the Siebel File System

This topic is part of Planning Your Siebel Deployment.

The Siebel File System is a shared directory, or set of directories, that is network-accessible to the Siebel Server and that can store files such as attachments for use by Siebel CRM. Siebel File System directories might optionally exist on multiple separate devices or partitions.

Each File System directory might be created on a server computer where you have installed a Siebel Server, or on another network server that can share the directory, so that it is available to the Siebel Server. Consult your third-party documentation for requirements for networked file systems.

Creating multiple Siebel File System directories in different locations can enable you to store larger volumes of data. As new file attachments are inserted, they are evenly distributed to these multiple File System directories. If you create multiple File System directories, then you must include all of the directory locations, delimited by commas, when you specify the Siebel File System location during configuration of your Siebel environment. Each File System directory location must be uniquely named within the network context where it will be accessed.

You can exclude certain types of files from being saved to the Siebel File System, as determined by their file extensions. For more information about setting system preferences to enable this feature and to specify the file extensions to be excluded, see Siebel Security Guide.

Siebel File System Requirements

The following are requirements for the Siebel File System. Additional requirements are noted later in this topic.

You specify the Siebel File System directory when you configure and deploy the Siebel Enterprise using Siebel Management Console. Siebel Management Console creates the Siebel File System directory if the directory specified for the File System does not exist. However, t is recommended that you create the primary Siebel File System directory with appropriate permission before you configure the Siebel Enterprise.
The user running the Siebel Management Console must have write permission in the Siebel File System directory.
It is strongly recommended that you disable short file-name generation on Windows server computers or operating system instances hosting the Siebel File System. Using this type of file-naming can cause severe performance issues when the file system grows to a large size.
The underlying physical file system must use file locking. Valid locks must be returned that are appropriate to the action being undertaken. For example, when a file is created or written to, an exclusive lock is needed. File locking must ensure the integrity of the files accessed. If a write lock is acquired for a file, then no other process must be able to access the file. For more information and recommendations, see 759070.1 (Article ID) on My Oracle Support.
For a UNIX deployment with an NFS file system, you must enable the NFS server’s lockd and statd daemons, and also the basic NFS daemons that implement mounting and accessing a share. These locking daemons must be tuned to the number of operating system threads. Otherwise, these daemons might not be able to manage the high volume of concurrent file system lock requests that a large scale Siebel CRM system can generate.
If the operating systems of the computers hosting the Siebel Server and a File System directory are different (for example, one Windows and one UNIX), then you might have to deploy a third-party cross-platform networking tool, such as Samba, to allow both computers to share the directory. See your third-party vendor documentation for details.
You must create a separate Siebel File System for each Siebel Enterprise. For example, if you have development and test databases, then you must have two separate Siebel Enterprises, and therefore two Siebel File Systems.
The ability to use multiple directories and devices for the Siebel File System does not apply to the Siebel Mobile Web Client, for which the Siebel File System must use a single directory on the client computer.
If you operate a File System directory as part of a cluster for failover purposes, then you must create the directory on a clustered disk drive with a clustered network share resource. For information about clustering your servers and about deployment options for the Siebel File System, see Siebel Deployment Planning Guide.

Siebel File System and Siebel Server Components

Each Siebel Server accesses the Siebel File System (for the Siebel Enterprise) by means of a dedicated server component, called File System Manager (alias FSMSrvr). Individual Siebel Web Clients require no direct knowledge of the locations of the Siebel File System directories, because they connect to FSMSrvr through the Application Object Manager component on the Siebel Server to request file uploads or downloads. The Application Object Manager passes such requests to FSMSrvr, which processes the requests through interaction with the File System directories.

Because the Siebel Server is the sole access mechanism to the Siebel File System, the user with administrative privileges for the Siebel Server, and no other user, must have access privileges to the File System directories. This precaution protects the File System from direct physical access by all other users.

Some Siebel Server components might access the Siebel File System directly, without using File System Manager.

Siebel File System Parameter

The Siebel File System parameter defines the particular directory or set of directories that you are using for the Siebel File System. Specify multiple File System directories delimited by commas.

The Siebel File System parameter can be defined at the Siebel Enterprise level, Siebel Server level, or server component level. When you configure the Siebel Enterprise, you specify a value for this parameter, as described in Creating a Siebel Enterprise Profile.

For a Siebel Server dedicated for use with Siebel EIM, for example, you might choose to use a Siebel File System location that is not in general use in the Siebel Enterprise. Use Siebel Server Manager to individually modify the parameter at the Siebel Server or component level, if the File System that is to be used by a particular Siebel Server or applicable component has different directory locations than are defined for the Siebel Enterprise.

The value of the Siebel File System parameter cannot exceed 2048 characters in length.

Note: Verify that the network names of servers that support the Siebel File System are properly recorded in your copy of the worksheet in Siebel Deployment Planning Worksheet. Use the computer names, not the IP addresses, for the Siebel File System names. IP addresses are not supported.

Deployments Using the Siebel Migration Application

Because the Siebel Migration application uses the Siebel File System, it is strongly recommended to use different file system locations for the source and target environments, to avoid any file conflicts. For this type of configuration, use Siebel Server Manager to set the following parameters in the source and target environments:

Set the parameter DSFileSystem for the server data source (ServerDataSrc) to *FSM*.
Set the parameter FileSystem for the enterprise to specify the file system locations applicable for that environment.

For more information, see the description of the Migration Package Location setting in Configuring the Siebel Migration Application. For more information about administering the Siebel File System and setting parameters, see Siebel System Administration Guide.

Siebel File System Utilities

The following utilities are available to help you manage your Siebel File System directories: sfscleanup and sfspartition.

Use sfscleanup to clean up orphan files in the Siebel File System.
Use sfspartition to configure an existing Siebel File System to use multiple partitions or multiple directories.

For information about using these utilities, see Siebel System Administration Guide.

Naming a Siebel File System Directory

Each Siebel File System directory name must be alphanumeric, must begin with an alphabetic character, and cannot contain special characters or spaces. Underscores are permitted. For example, you might name a directory something like this:

/server/siebel or /server/siebel/filesystem

Such a directory might be referred to using the following notation:

SiebelFS/siebel17

where:

SiebelFS is the host name of the computer (for example, where a dedicated computer is used for the Siebel File System).
siebel17 is the name of the shared directory.

You have to specify all of the applicable shared directories (delimited by commas) when configuring the Siebel Enterprise. These shared directories must be available to all of the Siebel Servers in the Siebel Enterprise. You might have to use a file-sharing tool to access the directories.

Note: When you create a Siebel File System shared directory, only the associated Siebel Servers must be allowed to create subdirectories in that location. Do not manually create subdirectories in that location.

As part of the Siebel Server installation, File System Manager automatically generates a set of subdirectories under each Siebel File System root directory. Some of these directories are described in Naming a Siebel File System Directory.

Table Siebel File System Subdirectories

Subdirectory	Purpose
att	Main subdirectory for file attachments
atttmp	Temporary directory for file attachments
CFGCache	Files used by Siebel Product Configurator
CFGDefs	Files used by Siebel Product Configurator
cms	Files used for outbound communication requests
eim	Siebel transaction files for Siebel EIM
ISS_OBrkCache	Files used by Siebel Product Configurator
Marketing	Main subdirectory for Siebel Marketing
Migration	Main subdirectory for the Siebel Migration application
red	Rule edit cache for Siebel Product Configurator
ssp	Session preferences
userpref	Siebel user preferences

For a migration installation case, Siebel File System subdirectories from previous releases are retained. Some of these directories might no longer apply in the current release, due to evolving feature support in Siebel CRM.

For more information about some of the Siebel File System subdirectories, see applicable documentation on Siebel Bookshelf, including Siebel System Administration Guide.

Setting Up the Siebel File System

Use the following procedures to set up the Siebel File System directories.

Note: In addition to using the following steps, you must install the third-party software required to view standard attachment types, such as Microsoft Word, Excel, or Lotus Notes, on client computers where users run Siebel CRM.

To set up the Siebel File System

Create each directory on the applicable server and record all of the directory locations in the copy that you made of the worksheet in Siebel Deployment Planning Worksheet.
Using the appropriate administrative tools for your UNIX operating system, set permissions for the Siebel administrator to access the directory and subdirectories to 700.

Note: Only the Siebel administrator for the Siebel Server, and no other user, must have access privileges to the Siebel File System directories.
Grant access to each Siebel Server for the appropriate group.
If an appropriate GUI-based administrative tool does not exist on your operating system, then you can use the chmod and chgrp utilities to set these parameters. Consult your UNIX operating system documentation for more information.

Related Books

Siebel Deployment Planning Guide

Siebel System Administration Guide

Siebel Security Guide

Creating the Siebel Service Owner Account

This topic is part of Planning Your Siebel Deployment.

The Siebel Enterprise Server requires that you create a standard UNIX system user account. This account must be available on each Siebel Server in your Siebel Enterprise under which Siebel processes and components operate.

Use the following guidelines to create the Siebel service owner account:

The Siebel service owner account must be defined or available on each applicable server computer: on the Siebel Gateway, on each Siebel Server in the Siebel Enterprise, and on any computer on which the Siebel File System exists.
Create the Siebel service owner account at the network level, using an appropriate administration tool for your UNIX operating system, so that the same account can be used for all of the UNIX server computers within the Siebel Enterprise Server. Make sure that the numeric values for uid and gid match across the various computers.
The Siebel service owner account password must not require a change on next logon and must be set not to expire.
The Siebel service owner account name or password cannot contain any spaces.
When you determine the Siebel service owner account name and password, record this information in your copy of the worksheet in Siebel Deployment Planning Worksheet. (For security reasons, you might prefer not to record the password in the worksheet.) See also Siebel Security Guide.

Installation and Configuration Methods by Deployment Type

You can use any of several different overall methods for installing and configuring Siebel CRM software. Use the following information to help you determine which overall method, or combination of methods, is most suitable for your deployment requirements.

For more information, see Overview of Installing Siebel CRM and other relevant topics.

Small to Medium-Sized Deployments

Do you require a small to medium-sized deployment? For smaller deployments, including some test or demonstration deployments, you might require all of the server-based Siebel CRM software to be installed on the same computer.

Verify that you have created the database instance (if you do not already have a Siebel database). The Siebel database might be located on the same computer as the Siebel Enterprise Server and the Siebel Application Interface, or on a different computer.

In this scenario, you install the Siebel Enterprise Server modules and you install the Siebel Application Interface on the same computer. Siebel Enterprise Server modules include Siebel Gateway, Siebel Server, Database Configuration Utilities, EAI Connector, and Siebel Enterprise Cache.

You use the Siebel Enterprise Server installer to install the Siebel Enterprise Server modules. Then you use the same installer to install the Siebel Application Interface in a different directory on the same computer.

If you do not have a Siebel database, then you start the Database Configuration Wizard and perform the task to install the Siebel database into the database instance.

After you install the Siebel database, you run Siebel Management Console to configure the Siebel CRM modules that you installed. You configure Siebel security, the Siebel Gateway, Siebel Enterprise, Siebel Server, Siebel Application Interface, and other modules.

Medium-Sized Deployments

Do you require a medium-sized deployment? Will you install all of the Siebel Enterprise Server modules on the same computer? Siebel Enterprise Server modules include Siebel Gateway, Siebel Server, Database Configuration Utilities, EAI Connector, and Siebel Enterprise Cache.

Verify that you have created the database instance (if you do not already have a Siebel database). The Siebel database is assumed to be located on a different computer than the computer with Siebel Enterprise Server software.

In this scenario, all of the Siebel Enterprise Server modules are to be installed on the same computer, but the Siebel Application Interface is to be installed on a different computer.

You use the Siebel Enterprise Server installer to install the Siebel Enterprise Server modules. Then you use the same installer to install the Siebel Application Interface on a different computer.

You can install in GUI mode or use unattended installation. For more information about unattended installation, see Large Deployments.

If you do not have a Siebel database, then you start the Database Configuration Wizard and perform the task to install the Siebel database into the database instance.

After you install the Siebel database, you run Siebel Management Console to configure the Siebel CRM modules that you installed. You configure Siebel security, the Siebel Gateway, Siebel Enterprise, Siebel Server, Siebel Application Interface, and other modules.

Large Deployments

Do you require a relatively large deployment? Will you use multiple servers to deploy Siebel CRM modules?

If you must support many users or multiple Siebel applications and have multiple servers available, then you will probably install the Siebel Gateway, Siebel Server, Siebel Application Interface, and the Siebel database on different computers.

A large deployment usually also requires multiple Siebel Servers running on different computers or operating system instances. Each Siebel Server might be configured to run a particular application or set of applications. Or, multiple Siebel Servers might be configured similarly for participation in load balancing. You might also require multiple instances of Siebel Application Interface running on different computers or operating system instances.

Follow the same steps as for a medium-sized deployment. Then install and configure each additional instance of Siebel Server and Siebel Application Interface.

Installation and Configuration Options

This topic is part of Installation and Configuration Methods by Deployment Type.

Options that can help you install and configure Siebel CRM software efficiently include:

Installation and configuration tasks are separate and are performed at different times, optionally by different users. After basic deployment decisions are made, installations can be done under the supervision of administrators who are most familiar with Siebel CRM. Such specialized administrators might perform all of the tasks in the Siebel Database Configuration Wizard and the Siebel Management Console.
You can perform unattended installation or configuration, which can save you time, provide greater flexibility, and reduce error, compared to installing and configuring each installed Siebel CRM module manually.
- For information about unattended installation, see Installing Siebel CRM in Unattended Mode.
- For information about unattended configuration, see Installing Siebel CRM Server Modules.

Requirements for Installing and Configuring Siebel Enterprise Server Modules

Review the requirements and guidelines in the following topics before installing and configuring the Siebel Enterprise Server modules:

For requirements specific to the Siebel database, see Requirements for Installing and Configuring the Siebel Database.

General Requirements for Installing and Configuring Siebel Enterprise Server Modules

This topic is part of Requirements for Installing and Configuring Siebel Enterprise Server Modules.

Review this topic before installing and configuring Siebel Enterprise Server modules. See also the topics about individual modules.

Before installing Siebel CRM software, you must review all of the relevant information in the Certifications tab on My Oracle Support. Also check for applicable alerts, bulletins, or other documents on My Oracle Support.
Review About Installing Siebel CRM and Planning Your Siebel Deployment.
All computers or operating system instances on which the Siebel Enterprise Server software is installed must meet the hardware and software requirements detailed in the Certifications tab on My Oracle Support or elsewhere. The Siebel Enterprise Server installer verifies that you have required software at the necessary version levels.
In general, you must have installed all of the third-party products that you will require for the Siebel Enterprise Server software that you are installing. Some products can be installed after Siebel CRM software. Such products are listed in the Certifications tab on My Oracle Support.
You must have created a Siebel CRM installation image that includes all of the modules and components that you require. Users who run Siebel installers or modify installer files must have the necessary permissions to the network directories where the Siebel image is located. For information about creating the Siebel installation image, see Creating the Siebel Installation Image on the Network.
If you install multiple Siebel Enterprise Server modules, such as Siebel Gateway and Siebel Server, on the same computer, then they are installed into a common root directory, such as /Siebel. The environment variable SIEBEL_ROOT might be set differently in different locations, to reflect the full path to the installation location of a specific component, such as Siebel Server. Installing Siebel CRM modules in certain combinations is not recommended. For more information, see About Installing Siebel CRM and About Installation Tasks for Siebel CRM.
Installation directories must meet the requirements described in File and Directory Naming Conventions.
If you will be clustering the Siebel Gateway or Siebel Server, then plan your use of clustering or redundant disk arrays (RAID) to configure against a single point of failure. For information about an optional native clustering feature for Siebel Gateway, see Configuring the Siebel Gateway Cluster. See also Siebel Deployment Planning Guide.
Each computer or operating system instance that supports Siebel Enterprise Server software must have TCP/IP network connectivity to other computers that are part of or that work with the Siebel Enterprise Server. For example, the Siebel Gateway computer requires connectivity to all of the Siebel Server computers. Verify connectivity between all such computers, using the ping utility. For more information, see Verifying Network Connectivity for the Siebel Server Computer.
Before running any of the Siebel Management Console tasks in which you will specify a server computer’s host name or IP address, validate the host name or IP address that you will enter during configuration. You can use the ping utility for this purpose. The host name and IP address data that you specify when you run the Siebel Management Console must be correct in order for the configuration process to proceed correctly.
Verify that the network names of the servers that will support the Siebel Gateway and all of the Siebel Servers are recorded in Siebel Deployment Planning Worksheet. You need this information when configuring the Siebel Servers.
It is strongly recommended to review all applicable security information before you configure Siebel CRM, which uses Transport Layer Security (TLS).
When data encryption is enabled, make a backup copy of the key file before you start a migration installation for Siebel Enterprise Server. Copy back this file after the migration.

Caution: When data encryption is enabled, a migration installation for Siebel Enterprise Server creates a new key file (keyfile.bin), overwriting your existing key file. If this happens, the encrypted columns will be inaccessible. To prevent this result, you must make a backup copy of the key file before starting the migration installation. After the migration installation, copy back the original key file. For more information about data encryption, see Siebel Security Guide.
Review the issues described in Managing Temporary Disk Space Required by Siebel Installers and Wizards. For example, make sure that you have adequate disk space, and make sure that the login ID running the installer has write permissions to this directory.
It is strongly recommended that you install and deploy, or at least install, all of the languages that you expect to require. For more information, see Installing and Deploying Siebel CRM with Multiple Languages.
For more information, see additional relevant topics, including:
- About Installing Siebel CRM
- Planning RDBMS Installation and Configuration
- Siebel Installation Media Contents
- About Configuring Siebel CRM and following topics
- Preparing to Run Siebel Server Components
You cannot install new Siebel Enterprise Server modules into an existing installation.
Note that the Siebel Enterprise Server installer user interface can run in the supported languages described in About the Language in Which Siebel Installers and Wizards Run.
Before you configure Siebel Enterprise Server modules, you must have created the Siebel File System. It must meet all of the criteria described in Creating the Siebel File System.
Before you install Siebel CRM, review documented information about the installation and configuration process and applicable requirements. Customers must manage the overall installation and configuration process carefully to ensure success.
For existing deployments, all Siebel Server component jobs must complete before:
- You perform any Siebel CRM installations in a migration installation case.
- You perform any upgrade tasks in a full database upgrade case.
  After you perform all installation and upgrade tasks, recreate any component job definitions that you require for your deployment.
Antivirus software, firewalls, and other security software can interfere with installation and operation of software if they are not properly configured. In some cases, you might need to disable antivirus software while installing Siebel CRM software. It is also recommended to exclude certain types of files from virus scanning. In addition, you might need to disable the Windows feature User Account Control while installing Siebel CRM software. Follow these guidelines for using antivirus software:
- Run virus scans on Siebel Enterprise Servers during maintenance windows, if possible, not when they are online. Scans can then be performed on all files at that time.
- You can run regular virus scans for the Siebel File System. It is recommended to perform these scans during off-peak hours.
For a migration installation case, you must perform the migration installation for Siebel Application Interface before you perform the migration installations for any other Siebel CRM server modules. When you do the migration installations for other Siebel Enterprise Server modules, the installer prompts you to provide the host name and installation location for the migrated installation of Siebel Application Interface. Without this information, the migration installations of Siebel Gateway, Siebel Server, or other modules cannot complete successfully.
Additional requirements apply for migration installations of the current release. For more information, see Additional Tasks for Migration Installations.

Related Books

Siebel Security Guide

Siebel Deployment Planning Guide

Requirements for Siebel Gateway Authentication

This topic is part of Requirements for Installing and Configuring Siebel Enterprise Server Modules.

Before you configure any Siebel Enterprise Server software, review the requirements associated with authentication for access to the Siebel Gateway. Authentication applies to access using Siebel Management Console or Siebel Server Manager.

Note the following requirements:

Supported Siebel Gateway authentication methods include database authentication, LDAP, and custom methods. Additional configuration is required. You can use the same authentication method as for your Siebel enterprise connections, or use different methods.
When you initially configure the Siebel Enterprise (after installing and configuring the Siebel Gateway), you propagate settings to the Siebel Gateway that specify authentication settings. Siebel Gateway authentication uses Siebel security adapters, which are discussed in detail in Siebel Security Guide.
The user account that you use for Siebel Gateway authentication must have the same privileges as the Siebel administrator account created during the Siebel installation process; these privileges are required to connect to the Siebel Gateway. You can choose to use the Siebel administrator account for Siebel Gateway authentication, or you can create a new database user account, ensuring that you assign it the same level of rights and privileges as the Siebel administrator account. For more information about requirements for this account, see Siebel Security Guide.
If you do not have an existing Siebel database, then, if you will use database authentication, you must install it before you can configure the Siebel CRM software using the Siebel Management Console.
After you configure the Siebel Gateway, users doing subsequent Siebel Management Console tasks that require Siebel Gateway authentication, or using Siebel Server Manager, must enter Siebel administrator user credentials that are valid for the authentication method in use.
All Siebel Management Console tasks are subject to Siebel Gateway authentication.
For more information about using Server Manager, see Siebel System Administration Guide.
If you want to use LDAP or a custom authentication method for the Siebel Gateway, then you can configure this method as part of the Siebel Management Console tasks for creating or modifying the Siebel Enterprise. The Siebel Management Console both configures and enables the security adapters (for the Siebel Enterprise or for the Siebel Gateway).
When you configure the Siebel Gateway using Siebel Management Console, the Authorization Roles setting defines the role that is required to access the Siebel Gateway. This setting includes the Siebel Administrator, which is provided by Oracle and cannot be modified. Optionally, you can add more comma-separated roles, specifying other roles that can access the Siebel Gateway.
If you want to configure a second Siebel Enterprise on the same Siebel Gateway, then do not check the option to propagate authentication settings to the Siebel Gateway when prompted. Otherwise, your settings will overwrite the existing settings.

Requirements Specific to UNIX or Linux Operating Systems

This topic is part of Requirements for Installing and Configuring Siebel Enterprise Server Modules.

Review the following requirements specific to UNIX or Linux operating systems:

Verify that the network adapter is correctly configured to support full duplex Ethernet by verifying the following parameters:
- RJ45 Port Link Status: up
- Media Speed Selected: 100 Mbps Full Duplex
- Media Speed Running: 100 Mbps Full Duplex
If the set-group-id flag is used, then make sure that the installer ID is a member of the group that owns the Siebel Enterprise Server root directory.
Installation must be performed as a nonroot user. This requirement stems from the Oracle Universal Installer software.
Future Siebel CRM releases must be installed as the same user who installed the base release.
For more information, see Setting Permissions and Ownership.
See also Configuring the Siebel Gateway for Automatic Start and Configuring the Siebel Server for Automatic Start.
When you install Siebel server modules into a mount point location, you must do so into a directory that is at least one level down from this location.
For example, given the mount points /export/home or /export/siebel, you must create a new directory under either of these directories, in which you will install the Siebel Enterprise Server or Siebel Application Interface. For example, you might create a directory named siebel and then install into /export/home/siebel or /export/siebel/siebel. Installing directly into the mount point location, such as /export/siebel, might create significant problems for your installation.
You must configure the environment before you run the Database Configuration Wizard. Run the script CreateDbSrvrEnvScript to generate the environment setup files dbenv.csh and dbenv.sh. Source one of these files before you run the Database Configuration Wizard. For more information, see Installing the Siebel Database. See also General Requirements for Installing and Configuring Siebel Enterprise Server Modules.

Requirements for AIX Only

The following requirements apply on AIX only:

Before installing, verify that the login ID performing the installation has permission to run slibclean by asking the administrator to change the permission as follows:
```
chmod 6555 /usr/sbin/slibclean
```
Before you install Siebel Enterprise Server software on AIX, you must install X11 filesets, if they were not included as part of the base AIX installation.
Where you are deploying Siebel Enterprise Cache, if either (but not both) of the following modules (Siebel Gateway and Siebel Constraint Engine) is installed on AIX, then the other module must also be installed on AIX.

Requirement for HP-UX Only

The following requirement applies on HP-UX only:

If the environment variable LANG is set to a directory name that is a symbolic link, then the installer for Siebel Server will fail. You must reset any existing LANG variable to the directory that the symbolic link represents.

Note: The LANG variable cannot be set to univ.utf8. Doing so causes the installer to fail.

Requirement for Oracle Solaris Only

The following requirement applies on Oracle Solaris only:

Set the TCP ndd variable tcp_co_min to the MTU of the network interface card.

Requirements for Installing and Configuring the Siebel Gateway

This topic is part of Requirements for Installing and Configuring Siebel Enterprise Server Modules.

Review this topic before installing and configuring the Siebel Gateway. See also General Requirements for Installing and Configuring Siebel Enterprise Server Modules.

Install the Siebel Gateway at least once for each Siebel Enterprise. If necessary, multiple Siebel Enterprises can be supported by a single Siebel Gateway. In general, installing multiple instances of the same version of Siebel Gateway on the same computer is not recommended.
For more information, see Planning to Install Multiple Instances of Siebel CRM. See also 477770.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 531.
Optionally install multiple instances of Siebel Gateway on different nodes in order to configure and deploy clustering. For more information, see Configuring the Siebel Gateway Cluster.
The default port number for Siebel Gateway is 2320. If necessary, you can select any port number (32767 or lower) that is free on the computer where the Siebel Gateway is running. Do not use port number 2321, which is the default port number for the SCBroker (Siebel Connection Broker) component, or any other port that is already in use on the server. To confirm that a port (such as 2320) is free, use a command like netstat -a | grep 2320.

Requirements for Installing and Configuring the Siebel Server

This topic is part of Requirements for Installing and Configuring Siebel Enterprise Server Modules.

Review this topic before installing and configuring the Siebel Server. See also General Requirements for Installing and Configuring Siebel Enterprise Server Modules.

To configure a Siebel Server, a Siebel Gateway must be installed and running, and the Siebel Enterprise must be configured.
After you install the Siebel Gateway, you run the Siebel Management Console to configure it, and then you configure the Siebel Enterprise. All Siebel Servers you install that are part of the same Siebel Enterprise, regardless of the operating system, must connect to the same Siebel database. For most deployments, all of the Siebel Servers connecting to this database will belong to the same Siebel Enterprise.
Additional Siebel Servers that you install and configure inherit parameters from the Siebel Enterprise. You configure each Siebel Server using the Siebel Management Console.
When you run the Siebel Management Console to configure each Siebel Server, all of the component groups are listed and you must enable the ones that you need for this server. If you do not enable component groups during Siebel Server configuration, then you can enable them manually after installation, using Siebel Server Manager. For more information about component groups and about using Server Manager, see Siebel System Administration Guide. See also Preparing to Run Siebel Server Components.
Depending on your business requirements, you might deploy one or more Siebel Enterprise Servers. For information about deploying multiple Siebel Enterprise Servers, see Siebel Deployment Planning Guide. See also 477770.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 531.

Note: In special cases, such as for some large deployments, a single Siebel database can support multiple Siebel Enterprises. Such a deployment must be planned carefully. For details, see 477829.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 544.

About Clustering the Siebel Gateway and Siebel Server

If you will operate certain servers as part of a cluster, then it is strongly recommended that you install and configure the Siebel Gateway and the Siebel Server on separate resource groups. For information about clustering, see Siebel Deployment Planning Guide.

For information about configuring Siebel Gateway clustering using Siebel Management Console, see Configuring the Siebel Gateway Cluster.

Language and Locale Requirements

Make sure that you have the appropriate locales installed on the computers on which you intend to deploy Siebel Server. Siebel log and configuration files use UTF-8 with Byte Order Mark as the default encoding. If these files contain any non-ASCII characters, then proper viewing and editing requires a UTF-8 locale.

For more information about supported locales, see the Certifications tab on My Oracle Support.

The locale can affect how dates and times are displayed. For more information, see Siebel Global Deployment Guide.

Note: Make sure that the locale that you are using matches the locale set at your operating system level. For details, see Specifying the Locale for Your UNIX Operating System.

Guidelines for Installing Multiple Language Packs on the Siebel Server

If you will install multiple language versions of Siebel applications on your Siebel Servers, then review the following configuration guidelines:

You can include multiple languages when you install and configure a Siebel Server.
For each installed language that you choose to deploy when you configure the Siebel Server, language-specific Application Object Manager components are created.
For more information about scenarios for multilingual deployments, see Installing and Deploying Siebel CRM with Multiple Languages and related topics. See also Siebel Global Deployment Guide.
If multiple languages are installed on a Siebel Gateway or Siebel Server, then you will be prompted for the primary (base) language. The primary (base) language is the language in which you want your server to run and in which you normally want to read messages. If you want to change the language in which you bring up your server, then you must change this setting.

Search Server

A Siebel Server computer can be configured to execute searching using a locally installed search server or can be pointed to a remote search server to handle search execution tasks.

Note: For search-related installation guidelines and requirements, see Siebel Search Administration Guide.

Database Requirements

Make sure that your database administrator has installed the RDBMS that your site will use and created the Siebel database instance and that you meet all of the database connectivity requirements. For more information, see Configuring the RDBMS, including Configuring Siebel Server Connectivity to the Siebel Database. See also Planning RDBMS Installation and Configuration.

The RDBMS that you are using must support the same languages and code pages that you install on the Siebel Servers. For Siebel CRM language support, Unicode support, and legacy code page support, see 1513102.1 (Article ID) on My Oracle Support.

Note: After performing a migration installation of the current release, then you must run Incremental Repository Manager. For more information, see About Database Updates for Siebel CRM 20.x Update.

Third-Party Software Requirements

Make sure that you have already installed the appropriate version of all of the third-party software products required. Otherwise, the Required Software Components prompt appears. For more information, see the Certifications tab on My Oracle Support.

Temporary Disk Space

Review the issues described in Managing Temporary Disk Space Required by Siebel Installers and Wizards. For example, make sure that you have adequate disk space, and make sure that the login ID running the installer has write permissions to this directory.

Requirements for Installing the Siebel EAI Connector

This topic is part of Requirements for Installing and Configuring Siebel Enterprise Server Modules.

You can install EAI Connector with other Siebel Enterprise Server modules or install it a separate location.

For a list of supported operating systems for EAI Connector, see the Certifications tab on My Oracle Support. See also General Requirements for Installing and Configuring Siebel Enterprise Server Modules.

Requirements for Installing and Configuring the Siebel Application Interface

Before installing and configuring the Siebel Application Interface, review the requirements described in the following information:

About the Siebel Application Interface

Siebel Application Interface enables communication between Siebel Web Clients and Siebel Servers. Siebel applications are a family of Web-based applications that users access through a standard Web browser. Several components work together to deliver the applications to end users:

Siebel Web Client. The Siebel CRM client that runs in the browser on the end user’s computer and connects to the Siebel Application Interface.
For information about other Siebel clients, see the applicable documentation. For example, for information about the Siebel Mobile applications, see Siebel Mobile Guide: Connected and Siebel Mobile Guide: Disconnected.
Siebel Application Interface. A program that communicates with the Siebel Web Engine (which is part of an Application Object Manager component, such as Call Center Object Manager) on the Siebel Server and with browsers run by users of Siebel CRM.
For Siebel Application Interface installation instructions, see Installing Siebel CRM. For configuration instructions, see Configuring the Siebel Application Interface. See also Planning the Siebel Application Interface Topology.
Siebel Web Engine (part of Application Object Manager on Siebel Server). The Siebel Web Engine is part of the Application Object Manager component on the Siebel Server, such as Call Center Object Manager. The Application Object Manager provides access to Siebel CRM data and logic.

For information about the hardware and operating systems supported for Siebel CRM, see the Certifications tab on My Oracle Support.

Planning the Siebel Application Interface Topology

Before you install the Siebel Application Interface for your Siebel deployment, as described in Installing Siebel CRM Server Modules, you must decide how you will distribute instances of Siebel Application Interface and other Siebel CRM modules. For the best performance and scalability, put the Siebel Application Interface on one or more dedicated computers.

This topic is part of Requirements for Installing and Configuring the Siebel Application Interface.

Two basic methods are as follows:

Single-node. Installing Siebel Enterprise Server modules and Siebel Application Interface on a single computer node, or operating system instance. 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. If you install all Siebel CRM modules on a single node, then you must use a separate installation directory for Siebel Application Interface.
You can use existing Web servers to host reverse proxy or authentication, where these products support jsessionid cookies and the mod_jk module. All instances of Siebel Application Interface must be protected by a reverse proxy.
Distributed. Distributing Siebel CRM modules, where instances of Siebel Application Interface on one or more dedicated computers or operating system instances connect to multiple Siebel Servers in the Siebel Enterprise. These Siebel Application Interface instances can be dynamically balanced for Application Object Manager components on different Siebel Server computers.
You can distribute incoming network traffic over multiple Siebel Application Interface instances by using third-party HTTP load balancers that support jsession-based load balancing in front of a reverse proxy Web server. You can use existing Web servers to host reverse proxy, authentication, or load balancing, where these products support jsessionid cookies and the mod_jk module. All instances of Siebel Application Interface must be protected by a reverse proxy.

Note: 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 about these or other products that meet these requirements, refer to vendor documentation. If you configure load balancing for application containers in this way, then, whenever an application container fails for a Siebel Application Interface node, the active sessions handled by that node transparently failover to another available healthy application container node.

Each deployment choice involves a trade-off. However, in enterprise-sized deployments, it is strongly recommended that you use a distributed node deployment for the following reasons:

Less resource contention. Distributing the Siebel Application Interfaces and the Siebel Servers (with Application Object Manager components) on different computers eliminates contention for CPU and other server resources. However, to take advantage of the performance improvement, you must have a high-speed network connection between the two computers.
Higher fault tolerance. Operating multiple instances of components on multiple computers reduces downtime and the effect of failure on any one computer.
High availability. A multinode configuration is required for deployments that support large numbers of concurrent users or where high availability is an operating requirement.

Related Books

Siebel Deployment Planning Guide

Siebel Security Guide

General Requirements for Installing and Configuring the Siebel Application Interface

This topic lists general requirements for installing and configuring the Siebel Application Interface.

This topic is part of Requirements for Installing and Configuring the Siebel Application Interface.

Before installing Siebel CRM software, you must review all of the relevant information in the Certifications tab on My Oracle Support. Also check for applicable alerts, bulletins, or other documents on My Oracle Support.
Review the issues described in Managing Temporary Disk Space Required by Siebel Installers and Wizards. For example, make sure that you have adequate disk space, and make sure that the login ID running the installer has write permissions to the temporary directory.
Make sure that the computers on which you install the Siebel Application Interface meet all of the hardware and software platform requirements documented in the Certifications tab on My Oracle Support.
You must have installed all of the key Siebel Enterprise Server modules, including the Siebel Gateway, at least one Siebel Server, and the Database Configuration Utilities.
Before you can configure Siebel Application Interface using Siebel Management Console, you must have configured the Siebel Gateway, the Siebel Enterprise, and the Siebel Server.
Application Object Manager components must be enabled for the Siebel CRM products that you purchased and intend to use. You enable components during initial Siebel Server configuration. For information about enabling server components using Siebel Server Manager, see Siebel System Administration Guide.

Note: Wait to install additional Siebel Servers until after you have completed installation of the Siebel Application Interface software and verified the connection from the Siebel Application Interface to the initial Siebel Server.
You must perform the migration installation for Siebel Application Interface before you perform the migration installations for any other Siebel CRM server modules. When you do the migration installations for other Siebel Enterprise Server modules, the installer prompts you to provide the host name and installation location for the migrated installation of Siebel Application Interface. Without this information, the migration installations of Siebel Gateway, Siebel Server, or other modules cannot complete successfully.
You can deploy multiple language packs on one Siebel Application Interface instance. The Siebel Server and the Siebel Application Interface do not have to be operated in the same language. However, the Siebel Server, the Siebel Application Interface, and all of the other server components must use the same character set. For more information, see Siebel Global Deployment Guide. See also Installing and Deploying Siebel CRM with Multiple Languages.
At least one Siebel Application Interface is required for each Siebel Enterprise.
Note that uninstalling a Siebel Application Interface instance that you have configured removes the associated Siebel application configuration. See also Uninstalling the Siebel Application Interface.
Note that the user interface of the Siebel Enterprise Server installer, which you use to install Siebel Application Interface, can run in the supported languages described in About the Language in Which Siebel Installers and Wizards Run.

Requirements for User Permissions for the Siebel Application Interface

This topic describes some requirements for permissions that affect installation or operation of the Siebel Application Interface and the Siebel application configurations that are associated with it.

This topic is part of Requirements for Installing and Configuring the Siebel Application Interface.

The user who will run the Siebel Application Interface must have read, write, and execute permissions on the SIEBEL_AI_ROOT/applicationcontainer/webapps/siebel directory and subdirectories (in this path, SIEBEL_AI_ROOT is the directory in which the Siebel Application Interface is installed). These permissions allow static public files to be cached on the Siebel Application Interface. These directories are created during Siebel Application Interface installation and configuration. In general, Siebel administrators require full access to SIEBEL_AI_ROOT and all of its subdirectories.

(AIX only) Before installing, verify that the login ID performing the installation has permission to run slibclean by asking the administrator to change the permission as follows:

chmod 6555 /usr/sbin/slibclean

Requirements for Configuring Anonymous Users for the Siebel Application Interface

As noted in Creating a Siebel Application Interface Profile, when you configure profiles for Siebel CRM using Siebel Management Console, you are prompted for user names and passwords of Siebel users who will serve as anonymous users for Siebel applications. Provide the anonymous user credentials, as appropriate for your deployment.

This topic is part of Requirements for Installing and Configuring the Siebel Application Interface.

The anonymous user has functions that include the following:

Starting the anonymous session that displays the login page to an end user for an application. This function applies to both employee applications and customer applications.
Allowing anonymous browsing and navigation within the application. In this case, usually applicable to customer applications only, the anonymous user must have access to any public view in the application.

You can define as many different anonymous users as you require for your deployment, each with the appropriate permissions, according to your needs. During Siebel software configuration, using Siebel Management Console, you can specify an anonymous user name and associated password when you:

Configure the Siebel Server profile, as described in Configuring the Siebel Server. You can specify the anonymous user to serve as a default for that Siebel Server.
Configure the Siebel Application Interface profile, as described in Configuring the Siebel Application Interface:
- An anonymous user that will serve as a global default for all applications, unless overridden by the corresponding Siebel Server profile setting or by the corresponding setting for an individual application.
- An anonymous user that will override the default for an individual application, unless overridden by the corresponding Siebel Server profile setting.
- An anonymous user that will be used for REST inbound authentication. The password for this anonymous user is used for REST requests that are sent without a user name and password.

If, after performing the initial configuration, you change the password for the database account that you are using for an anonymous user, or decide to specify a different anonymous user for a particular application, then you can modify the configuration to provide the updated password or to specify a different anonymous user for this application.

Record the credentials for each anonymous user in your deployment in the worksheet provided in Siebel Deployment Planning Worksheet.

Note the following guidelines and requirements:

For more information about configuring anonymous users, see Siebel Security Guide.
All anonymous users for your deployment must be defined in the Siebel database and must be defined as Siebel users. Strong passwords are highly recommended for anonymous user accounts. Anonymous users should have limited access rights, no more than is necessary for the usage context. The Siebel Management Console does not allow the Siebel administrator user, SADMIN, to be specified as an anonymous user.
You can create new database users that will serve as anonymous users through editing the grantusr.sql script. You review, modify, and execute this script before you install the Siebel database and configure the Siebel deployment. GUESTCST is an example of an anonymous user account that you would create in the grantusr.sql script. After you install the Siebel database and configure the Siebel deployment, then you still also add corresponding Siebel users. For more information, see Creating Table Owner and Administrator Accounts.
The anonymous user for employee applications must be defined as an employee and must be associated with an appropriate position and responsibility.
If your Siebel application does not use functionality that requires anonymous browsing, then you can disable access by the anonymous user by setting the AllowAnonUsers parameter for the Application Object Manager component to False. If anonymous browsing must be enabled, then you set AllowAnonUsers to True.
Anonymous users are used by applications that allow anonymous browsing by unregistered users, that display a Siebel login page, that support self-registration, or that support external authentication such as LDAP. The anonymous user and password are used for serving the login page.
To use nondefault or application-specific anonymous users, you must specify the anonymous user and passwords for each application, in the Siebel Application Interface profile. You can also specify the anonymous user in the Siebel Server profile.

Related Books

Siebel Security Guide

Siebel System Administration Guide

Deploying Siebel Open UI

Requirements for Installing and Configuring the Siebel Database

Before you install and configure the Siebel database, review the following information:

Review database information in the Certifications tab on My Oracle Support and elsewhere.
For Siebel CRM language support, Unicode support, and legacy code page support, see 1513102.1 (Article ID) on My Oracle Support.
For new installations, make sure that the Siebel database instance has been created and is properly configured, as documented in Configuring the RDBMS.
Review Installing the Siebel Database on the RDBMS, including About Installing the Siebel Database, and the topics that follow.
Obtain the services of a qualified database administrator (DBA) to assist you with your installation and, where applicable, upgrade.
Complete the appropriate RDBMS-specific information in your copy of the worksheet in Siebel Deployment Planning Worksheet, as follows.

General Requirement

Installing the Siebel database is subject to installation requirements for Siebel Database Configuration Utilities related to Siebel Gateway authentication, which are noted in General Requirements for Installing and Configuring Siebel Enterprise Server Modules.

Oracle Database

For Oracle Database, make sure that the following elements are defined for your Siebel database:

Oracle SQLNet alias connect string. Provide the name of the Oracle schema qualifier or table owner name and the SQLNet connect string for Oracle. You need this to connect to your Oracle Database.
Table owner account (schema) name and password. Using an Oracle Database requires that you assign a user name and password to any database tables that you create. The term table owner refers to the schema that owns the database objects, such as tables, indexes, views, and triggers.
Before installing the Siebel database components, you have to edit the grantusr.sql script, enter this and related information, and execute the script. See Creating Table Owner and Administrator Accounts.
Siebel data tablespace. The name of the tablespace on the Oracle Database server where the Siebel data tables are stored.
Siebel index tablespace. The name of the tablespace on the Oracle Database server where the Siebel indexes are stored.
Install the Oracle Database Client software onto the computer where you will install the Database Configuration Utilities. Make sure that you have set the ORACLE_HOME variable appropriately before installing Siebel CRM software.

Note: Make sure that the Oracle Database Client and Oracle Database versions are compatible, unless you are otherwise advised by Oracle Global Software Support or unless required for your particular deployment. For supported versions of Oracle Database products, see the Certifications tab on My Oracle Support.

IBM DB2

For IBM DB2, make sure that the following elements are defined for your Siebel database:

Database alias. The DB2 database alias that you created when you installed the DB2 software.
Table owner or database owner account user name and password. DB2 requires that you assign a user name and password to each database that you create.
Before you install the tablespaces and indexes, you are prompted to edit the grantusr.sql script, enter this and related information, and execute the script. See Creating Table Owner and Administrator Accounts.
Siebel index tablespace. The name of the tablespace on the DB2 server where the Siebel indexes are stored.
Siebel 4-KB tablespace. The name of the tablespace on the DB2 server where the 4 KB Siebel data tables are stored.
Siebel 16-KB tablespace. The name of the tablespace on the DB2 server where tables reside whose row length is equal to or greater than 4005 bytes, but less than 16384 bytes.
Siebel 32-KB tablespace. The name of the tablespace on the DB2 server where tables reside whose row length is 32768 bytes.
Statistics are generated automatically during table, index, and seed data installation, and during the Siebel Repository import process. However, it is recommended that statistics be kept up to date through standard database administration procedures.
Make sure that you have installed the required IBM fix pack on your database server computer. For more information, see the Certifications tab on My Oracle Support.
Make sure that IBM DB2 is properly configured and you have allocated disk space appropriate to your installation requirements.

Requirements for Installing Siebel Web Clients

Review the issues and tasks in this topic before installing the Siebel Web Client, as described in Installing the Siebel Web Client.

Administrative Rights for Installation

Administrative rights are required for installation or uninstallation of the Siebel Mobile Web Client or Developer Web Client.

For information about setting administration rights, consult the operating system manuals for the version of Microsoft Windows on which you are installing the Siebel Web Client software.

For information about uninstalling Siebel Web Client software, see Uninstalling Siebel Web Clients or Siebel Tools.

Directory Naming Conventions

By default, the Siebel Web Client installer assumes an installation directory of C:\Siebel\Client or a similar location. You can specify to install in a different location.

If you must change the installation location to use a nondefault path, then use installation directory names that describe the Siebel CRM module being installed. The directory name can use any characters appropriate for Windows-compatible long file names, except that spaces must not be used in your install directory.

In this guide, the directory into which you install the Siebel Web Client is often referred to as SIEBEL_CLIENT_ROOT.

Do not install other Siebel CRM modules, such as Siebel Tools, into the same directory where you have installed the Siebel Web Client, such as C:\Siebel\Client. Install each module into a separate directory. If you install the sample database, then do so in the same directory as the Siebel Mobile Web Client. (Alternatively, you can install the sample database into the Siebel Tools directory instead of the Siebel Mobile Web Client directory.) If you install multiple Siebel CRM modules on the same computer (that will access different data sources), then determine your directory-naming convention before you begin installing.

Requirements and Recommendations for Siebel Web Client

Before beginning Siebel Web Client installation, review the requirements and recommendations for hardware, system software, and third-party software described in the Certifications tab on My Oracle Support.

Restricted Support for Siebel Developer Web Client

The Siebel Developer Web Client is not supported for end-user deployment. This Siebel Web Client type is supported only for development, troubleshooting, and limited administration usage scenarios.

Database Connectivity Software for Siebel Developer Web Client

Siebel Developer Web Client computers connecting directly to the Siebel database must have the correct vendor-specific database connectivity software installed. See the Certifications tab on My Oracle Support.

Note: The correct version of database connectivity software must be installed before you install the Siebel Web Client.

For additional information, see Logging in to Your Siebel Application.

When you have installed your database connectivity software, configure it as follows:

For Oracle Database, you install and configure the Oracle client software to connect to the Siebel database. Record the connect string and table owner information on the worksheet in Siebel Deployment Planning Worksheet. Use the driver version specified in the Certifications tab on My Oracle Support.
For an Oracle client, use a binary sort order for development environment databases. This setting is required for adequate performance from the Siebel Developer Web Client.
For more information, see Specifying the Locale for Siebel CRM. See also Configuring an Oracle Database for Siebel CRM and Siebel Database Upgrade Guide.
For IBM DB2, you install and configure the DB2 Client software to connect to the Siebel database. Record the connect string and table owner information on the worksheet in Siebel Deployment Planning Worksheet. Use the ODBC driver version specified in the Certifications tab on My Oracle Support.
For IBM DB2 for z/OS, you use DB2 Connect to connect from the Siebel Developer Web Client to the Siebel database. For details, see Implementing Siebel Business Applications on DB2 for z/OS.

Requirements for Oracle Database SE2 and the Local Database

In the current release, Oracle Database SE2 is used for the local database, and the sample database is no longer supported. For information about the requirements for installing and using Oracle Database SE2 for Siebel Mobile Web Client, see Installing and Using Oracle Database SE2 for the Local Database.

Security-Related Software

Antivirus software, firewalls, and other security software can interfere with installation and operation of software if they are not properly configured. In some cases, you might need to disable antivirus software while installing Siebel CRM software, including Oracle Database SE2 for the local database for Siebel Mobile Web Client on Microsoft Windows. It is also recommended to exclude certain types of files from virus scanning. In addition, you might need to disable the Windows feature User Account Control while installing Siebel CRM software.

Other Oracle or Third-Party Software

Your Siebel application might require some other Oracle software products or third-party software products to be installed on the client computer, for full functionality. For more information about third-party software, see the Certifications tab on My Oracle Support.

Note: Remember to install on the client computers all of the software required to view any standard attachment types your Siebel CRM deployment might use.

For information about requirements for the Web browser environment for running Siebel Web Clients, see Deploying Siebel Open UI and see the Certifications tab on My Oracle Support. See also topics such as the following:

Chrome Browser Users

When using Siebel Mobile Web Client or Developer Web Client with Google Chrome as the default browser, make sure that no other instances of Chrome are running prior to starting the Siebel client.

Closing Browser Sessions

Before you install the Siebel Web Client software, it is strongly recommended that you close any browser sessions on the client computer.

For information about requirements for the Web browser environment for running Siebel Web Clients, see also Deploying Siebel Open UI.

Migration Installations

Additional requirements apply for migration installations of the current release. For more information, see Additional Tasks for Migration Installations.

Requirements for Installing Siebel Tools

Review the requirements in this topic before installing Siebel Tools, as described in Installing Siebel Tools.

Your Siebel Tools platform must meet the requirements defined in the Certifications tab on My Oracle Support.
You must have all of the third-party software required for your implementation installed, including the database connectivity software for your chosen RDBMS. See the Certifications tab on My Oracle Support.
You must have installed and configured the Siebel Enterprise Server software, as described in Configuring Siebel CRM Server Modules and Configuring Siebel CRM Server Modules.
You must have created the Siebel database and installed the Siebel schema and seed data, as described in Configuring the RDBMS and Installing the Siebel Database on the RDBMS. This database stores the Siebel Tools project repositories.
The sort order for the Siebel database for development environments must be set to binary. If it is set otherwise, then you cannot compile or merge repositories.
Antivirus software, firewalls, and other security software can interfere with installation and operation of software if they are not properly configured. In some cases, you might need to disable antivirus software while installing Siebel CRM software. It is also recommended to exclude certain types of files from virus scanning. In addition, you might need to disable the Windows feature User Account Control while installing Siebel CRM software.
Administrative rights are required for installation or uninstallation of Siebel Tools. For information about setting administration rights, consult the operating system manuals for the version of Microsoft Windows on which you are installing the Siebel Web Client software.
Before performing a migration installation of Siebel Tools in a deployment with multiple languages, you must make sure that the current language mode for Siebel Tools corresponds to the primary language of the Siebel database.

Caution: If the current language mode for Siebel Tools, before the migration installation, was not the same as the primary language, then failures will occur during the execution of Incremental Repository Merge after the migration installation. For more information about setting the language mode, see Using Siebel Tools. For more information about running Incremental Repository Merge, see Siebel Database Upgrade Guide.
Additional requirements apply for migration installations of the current release. For more information, see Additional Tasks for Migration Installations.