7/29/2019 Sie Bins TwinSie Bins Twin
1/335
Siebel Installation Guidefor Microsoft Windows
Version 8.1, Rev. A
January 2010
7/29/2019 Sie Bins TwinSie Bins Twin
2/335
Copyright 2005, 2010 Oracle and/or its affiliates. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information;
they are provided under a license agreement containing restrictions on use and disclosure and are alsoprotected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering,disassembly, or decompilation of the Programs, except to the extent required to obtain interoperabilitywith other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problemsin the documentation, please report them to us in writing. This document is not warranted to be error-
free. Except as may be expressly permitted in your license agreement for these Programs, no part ofthese Programs may be reproduced or transmitted in any form or by any means, electronic ormechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programson behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS
Programs, software, databases, and related documentation and technical data delivered to U.S.Government customers are "commercial computer software" or "commercial technical data" pursuant to
the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such,use, duplication, disclosure, modification, and adaptation of the Programs, including documentation andtechnical data, shall be subject to the licensing restrictions set forth in the applicable Oracle licenseagreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, CommercialComputer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City,CA 94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup,redundancy and other measures to ensure the safe use of such applications if the Programs are used forsuch purposes, and we disclaim liability for any damages caused by such use of the Programs.
The Programs may provide links to Web sites and access to content, products, and services from third
parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites.You bear all risks associated with the use of such content. If you choose to purchase any products orservices from a third party, the relationship is directly between you and the third party. Oracle is not
responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms ofthe agreement with the third party, including delivery of products or services and warranty obligationsrelated to purchased products or services. Oracle is not responsible for any loss or damage of any sortthat you may incur from dealing with any third party.
Oracle, JD Edwards, and PeopleSoft are registered trademarks of Oracle Corporation and/or its affiliates.Other names may be trademarks of their respective owners.
7/29/2019 Sie Bins TwinSie Bins Twin
3/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A 3
Contents
Siebel Installation Guide for Microsoft Windows 1
Chapter 1: Whats New in This Release
Chapter 2: Preparing to Install Siebel BusinessApplications
About the Deployment Planning Worksheet 17
About Installing Siebel Releases 17
About Installing in Upgrade Environments 20About the Windows and UNIX Versions of This Guide 21
Overview of Installing Siebel Business Applications 22
General Considerations in Planning Your Siebel Deployment 23
Planning Topologies 24
Preparing the Hardware 25
Planning Siebel Server Load Balancing 26
Planning Disk Space Requirements 26
Planning RDBMS Installation and Configuration 26
Managing Siebel Image Directories and Media Files 28
Managing Temporary Disk Space Required by Siebel Installers and Wizards 28The Language in Which Siebel Installers and Wizards Run 29
Installing Multiple Instances of Siebel Business Applications 30
Specifying the Locale for Siebel Business Applications 32
Restrictions on Host Names for Siebel Gateway Name Server and Siebel Server 32
Restrictions on Names for Siebel Enterprise Server and Siebel Server 33
File and Directory Naming Conventions 34
Creating the Siebel File System 35
Creating the Siebel Service Owner Account 39
Chapter 3: Configuring the RDBMS
Overview of Database Configuration 41
Configuring an Oracle Database for Siebel Business Applications 43
Guidelines for Selecting a Language for Oracle Database 44
Guidelines for Configuring Settings in the init.ora File 45
Guidelines for Sizing Redo Logs for an Oracle Database 46
Guidelines for Creating Oracle Table Spaces 47
7/29/2019 Sie Bins TwinSie Bins Twin
4/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A
Contents
4
Guidelines for Sizing the Oracle Database 48
Guidelines for Creating Temporary Oracle Table Spaces 48
Guidelines for Overriding Oracle Default Table Spaces for Database Objects 48Guidelines for Creating Oracle Database Objects 49
Guidelines for Ongoing Oracle Database Administration 50
Guidelines for Using Real Application Clusters for an Oracle Database 51
Configuring an IBM DB2 Database for Siebel Business Applications 51
Guidelines for Setting IBM DB2 Database Manager Configuration Parameters 52
Guidelines for Selecting a Language for IBM DB2 54
Guidelines for Creating the IBM DB2 Database 55
Guidelines for Setting IBM DB2 Configuration Parameters 56
Guidelines for Setting Up IBM DB2 Bufferpools 58
Guidelines for Creating IBM DB2 Table Spaces 59
Guidelines for Overriding IBM DB2 Default Table Spaces for Database Objects 60Guidelines for Preventing IBM DB2 from Running Out of ODBC Statement Handles 62
Guidelines for Determining IBM DB2 Log Space 62
Guidelines for Archiving IBM DB2 Log Files 63
Guidelines for Creating IBM DB2 Database Objects 63
Guidelines for Managing IBM DB2 Fragmentation 63
Configuring a Microsoft SQL Server Database for Siebel Business Applications 64
Guidelines for Configuring Microsoft SQL Server Parameters 65
Guidelines for Selecting a Language for Microsoft SQL Server 66
Guidelines for Creating the Microsoft SQL Server Database 67
Guidelines for Allocating Microsoft SQL Server Database Log Space 67
Guidelines for Overriding Microsoft SQL Server Default Table Spaces for Database Objects67
Guidelines for Creating Microsoft SQL Server Database Objects 68
Guidelines for Ongoing Microsoft SQL Server Administration 69
Chapter 4: Creating the Siebel Installation Image on theNetwork
Obtaining Siebel Installation Media Files 71
Siebel Installation Media Contents 72
Preparing to Create a Siebel Installation Image 75Determine Location for Siebel Media Files and Siebel Images 75
Requirements for Siebel Image Directories 76
Cross-Platform Issues When Creating Siebel Image Directories 77
Requirements for Running Image Creator Utility 78
Creating a Siebel Installation Image 79
Running Siebel Image Creator in GUI Mode 79
7/29/2019 Sie Bins TwinSie Bins Twin
5/335
Contents
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A 5
Running Siebel Image Creator in Console Mode 82
Troubleshooting Siebel Image Creation 83
Chapter 5: Installing Siebel Enterprise Server and RelatedComponents
Overview of Installing and Configuring Servers in a Siebel Deployment 85
Process of Installing and Configuring Servers in a Siebel Deployment 88
Installation and Configuration Methods by Deployment Type 89
Small to Medium-Sized Deployments 89
Medium-Sized Deployments 90
Large Deployments 91
Requirements for Siebel Enterprise Server Installation and Configuration 92
General Requirements for Siebel Enterprise Server Installation and Configuration 93
Requirements for Siebel Gateway Name Server Installation and Configuration 97
Requirements for Siebel Server Installation and Configuration 98
Requirements for Siebel EAI Connector Installation 100
About Installing and Deploying Siebel Business Applications with Multiple Languages100
Scenarios for Installing and Deploying Multiple Languages 103
Installing and Deploying All Required Languages Once 103
Installing All Required Languages but Deploying Some Languages Later 104
Installing and Deploying Additional Languages 106
Configuring Connectivity to the Siebel Database 107
Verifying Network Connectivity for the Siebel Server Computer 108
Installing Siebel Enterprise Server Components 110
Reviewing the Siebel Enterprise Server Installation 117
Reviewing the Installation for Siebel Gateway Name Server 118
Reviewing the Installation for Siebel Server 118
Reviewing the Installation for the Database Configuration Utilities 120
Installing Using the Siebel FastTrack Wizard 121
Installing Siebel Management Agent and Siebel Management Server 123
About Siebel Management Agent and Siebel Management Server 124
Requirements for Installing Siebel Management Agent and Siebel Management Server124
Installing Siebel Management Agent 126
Installing Siebel Management Server 128
Command-Line Options for Siebel Installers and Wizards 130
7/29/2019 Sie Bins TwinSie Bins Twin
6/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A
Contents
6
Chapter 6: Configuring Siebel Enterprise Server andRelated Components
About Configuring Siebel Enterprise Server and Related Components 133Configuration Wizard Changes in Release 8.0 and Later 134
Configuration Wizards Associated with Installable Components 137
Configuration Wizards and Associated Model Files 140
Launching the Siebel Configuration Wizard 141
Procedures for Launching Configuration Wizards 143
Configuration Wizard Syntax Elements 144
Commands for Launching Configuration Wizards 146
Performing Configuration Tasks 147
Performing Tasks for Configuring Siebel Gateway Name Server, Siebel Enterprise, and
SWSE Logical Profile 148Settings for Configuring the Siebel Gateway Name Server 150
Settings for Configuring the Siebel Enterprise 151
Performing Tasks for Configuring the Siebel Server 158
Settings for Configuring the Siebel Server 159
Performing Tasks for Configuring the Siebel Database 163
Performing Tasks for Configuring the SWSE 163
Verifying the Siebel Gateway Name Server Has Started 164
Postinstallation Tasks for Siebel Server 165
Starting the Siebel Server Services 165
Verifying the ODBC Data Source 166
Verifying the ODBC Data Source for Oracle Database 166
Verifying the ODBC Data Source for IBM DB2 167
Verifying the ODBC Data Source for MS SQL Server 168
Establishing Network Connectivity for Mobile Users 169
Preparing to Run Siebel Server Components After Installation and Configuration170
Enabling and Disabling Server Component Groups 170
Enabling and Disabling Language-Specific AOMs and Adding Languages 170
Synchronizing Batch Components 171
Saving Component Job Definitions in an Upgrade Scenario 171Migrating Siebel Enterprise Server and Siebel Server Parameter Settings 172
Configuring Load Balancing for Siebel Business Applications 172
Generating the Load Balancing Configuration File (lbconfig.txt) 172
Setting Up a Third-Party HTTP Load Balancer 174
Setting the Load Balancer Connection Time-Out 176
7/29/2019 Sie Bins TwinSie Bins Twin
7/335
Contents
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A 7
Monitoring Servers with Siebel Native Load Balancer or Third-Party HTTP Load Balancers176
Installing Additional Siebel Servers for an Existing Siebel Enterprise Server 177Troubleshooting Siebel Enterprise Server Installation and Configuration 178
Troubleshooting Siebel Gateway Name Server Installation and Configuration 178
Troubleshooting Siebel Server Installation and Configuration 179
Troubleshooting the ODBC Data Source Connection 179
Configuring Siebel Management Agent and Siebel Management Server 180
About Configuring Siebel Management Agents and Siebel Management Server 181
Process of Configuring Siebel Management Agents and Management Server 183
Creating the Siebel User for Siebel Diagnostic Tool 183
Configuring Siebel Management Agent 185
Configuring Siebel Management Server 188Using Perl Scripts to Register Additional Siebel Management Agents or to Configure SiebelADM 192
Restarting Siebel Management Server After Installation and Configuration 196
Chapter 7: Configuring the Siebel Database
About the Siebel Database and the Database Configuration Utilities 197
Process of Configuring the Siebel Database 198
Requirements for Configuring the Siebel Database 200
Setting Up Your Environment to Support Global Time Zone 202
Creating Table Owner and Administrator Accounts 202
Installing the Stored Procedures and User-Defined Functions on IBM DB2 205
Configuring the Siebel Database on the RDBMS 206
Installing the Siebel Database Components 206
Reviewing the Log Files for Siebel Database Installation 211
Verifying System Preferences and Other Settings for Database Code Page 213
Populating the Siebel File System 214
Importing a Siebel Repository into the Siebel Database 215
Importing a Siebel Repository 215
Reviewing the Log Files for Repository Import for the Siebel Database 218
Chapter 8: Installing and Configuring the Siebel WebServer Extension
About Siebel Web Server Extension (SWSE) 221
Process of Installing and Configuring the SWSE 222
7/29/2019 Sie Bins TwinSie Bins Twin
8/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A
Contents
8
Requirements for SWSE Installation and Configuration 223
Installing the Web Server 227
Installing the SWSE 227
Configuring the SWSE 230
Creating the SWSE Logical Profile 231
Settings for Creating the SWSE Logical Profile 232
Applying the SWSE Logical Profile 236
Settings for Applying the SWSE Logical Profile 236
Postinstallation Tasks for the SWSE and the Web Server 238
Reviewing the Installation for the SWSE 238
Reviewing the Log Files for the SWSE 239
Verifying Virtual Directories on the Web Server 239
Creating Custom Virtual Directories 240
Supporting ASP Pages and Siebel Business Applications on the Same Web Server 240
Setting SWSE and Virtual Directory Permissions 240
Enabling HTTP Compression for Siebel Business Applications 241
Editing the SWSE Configuration File (eapps.cfg) 242
Configuring the Default HTTP and HTTPS Ports for the Web Server 243
Updating Web Server Static Files on SWSE Using the Siebel Enterprise Security Token244
Troubleshooting SWSE Installation 245
Chapter 9: Installing Siebel Mobile Web ClientsAbout Installing the Siebel Client 247
Process of Installing the Siebel Client 249
Preinstallation Tasks for the Siebel Client 249
Installing the Siebel Mobile Web Client and Developer Web Client 251
Installing the Siebel Sample Database 255
Importing Non-ENU Repository and Seed Data into the Siebel Sample Database 258
Postinstallation Tasks for the Siebel Client 259
Configuring the Siebel Client When Siebel VB or Siebel eScript Is Not Licensed 260
Verifying the Siebel Client Directory Structure 260
Logging in to Your Siebel Application 261
Siebel Client Shortcuts and Startup Options 263
Siebel Client Shortcuts 264
Siebel Client Startup Options 265
Creating Custom Siebel Application Shortcuts 267
7/29/2019 Sie Bins TwinSie Bins Twin
9/335
Contents
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A 9
Using Siebel QuickStart with the Siebel Mobile Web Client 268
Chapter 10: Installing Siebel ToolsAbout Installing Siebel Tools 273
Process of Installing Siebel Tools 274
Requirements for Siebel Tools Installation 274
Installing the Siebel Tools Client 276
Postinstallation Tasks for Siebel Tools 278
Verifying Successful Installation of Siebel Tools 279
Verifying the Siebel Tools Directory Structure 279
Verify Read and Write Access to Siebel Tools Directories 281
Verify Siebel Tools ODBC Data Sources 281
Chapter 11: Installing Siebel Charts
Process of Installing Siebel Charts 283
Installing Siebel Charts 283
Configuring Siebel Charts 285
Changing the Siebel Charts Server Used by Web Clients 285
Chapter 12: Installing and Configuring in Unattended andConsole Modes
About Unattended or Console Mode Installation and Configuration 287
Descriptions of Unattended or Console Mode Installation 287
Siebel Modules for Unattended or Console Mode Installation 288
Combinations of Installation and Configuration Modes 289
About Installation and Configuration Response Files 293
Installing and Configuring in Unattended Mode 294
Generating Installation and Configuration Response Files 295
Editing siebel.ini Files for Unattended Installation and Configuration 295
Running Unattended Installation from the Command Line 299
Installing and Configuring in Console Mode 300
Editing siebel.ini Files for Console Mode Installation 300
Running Console Installation from the Command Line 301
Chapter 13: Verifying Your Server Environment
About the Environment Verification Tool 303
About the EVT Configuration File 304
7/29/2019 Sie Bins TwinSie Bins Twin
10/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A
Contents
10
Launching the EVT Utility 306
Running EVT in Query Mode 306
Optional EVT Command-Line Flags 307
Available EVT Output Formats 309
Changing EVT Output Text 309
Chapter 14: Uninstalling Siebel Business Applications
About Uninstalling Siebel Business Applications 311
Uninstalling Earlier Versions of Siebel Business Applications 314
Uninstalling Siebel Enterprise Server Software 314
Uninstalling Siebel Web Server Extension 317Uninstalling Siebel Management Server 318
Uninstalling Siebel Management Agent 318
Uninstalling Siebel Strong Encryption Pack 318
Uninstalling Siebel Clients and Siebel Tools 319
Uninstalling Siebel Charts 320
Troubleshooting Uninstallation 320
Appendix A: Deployment Planning Worksheet
Team Lead Summary 323
Enterprise Server Names and Installation Directories 324
Siebel Accounts, Host Names, and Static IP Addresses 325
Cluster Deployment Data 326
Ports and RDBMS Details Data 326
Index
7/29/2019 Sie Bins TwinSie Bins Twin
11/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A 11
1 Whats New in This Release
Siebel Installation Guide for Microsoft Windows covers the installation and initial configuration of
Oracles Siebel Business Applications. The installation and configuration tasks are covered for Siebel
Enterprise Server software, Siebel Web Server Extension, Siebel Mobile Web Clients, Siebel Tools,
and other installable Siebel modules.
NOTE: For more information about third-party products, such as supported operating systems or
RDBMS platforms, Web servers, Visual Mining NetCharts, and so on, see also Siebel System
Requirements and Supported Platforms on Oracle Technology Network.
Whats New in Siebel Installation Guide for Microsoft Windows,Version 8.1, Rev. ATable 1 lists some of the changes in this version of the documentation to support release 8.1 of the
software.
Table 1. Whats New in Siebel Installation Guide for Microsoft Windows, Version 8.1, Rev. A
Topic Description
Obtaining Siebel Installation Media
Files on page 71
Modified topic. Clarified the content about Siebel media files
in relation to Siebel Image Creator.
For the version 8.1.1 base release, separate Siebel media
files are available for the Siebel Industry Applications andSiebel Cross-Industry Applications application types.
For version 8.1.1.x maintenance releases, the same
media files support either application type, which you
select in Image Creator.
About Configuring Siebel
Management Agents and Siebel
Management Server on page 181
Modified topic. Added information about specifying the Siebel
Enterprise and Gateway Name Server during configuration of
Siebel Management Server. Also updated information about
specifying the Siebel ADM package directory.
Using Perl Scripts to Register
Additional Siebel Management
Agents or to Configure Siebel ADMon page 192
Modified topic. Clarified requirements and procedures for
executing the Perl scripts as part of configuring Siebel
Management Server and Management Agent, or Siebel ADM.
Siebel Modules for Unattended or
Console Mode Installation on
page 288
Modified topic. It describes installation and configuration
options for several Siebel modules, now including Siebel
Management Server and Management Agent.
7/29/2019 Sie Bins TwinSie Bins Twin
12/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A
Whats New in This Release
12
Whats New in Siebel Installation Guide for Microsoft Windows,Version 8.1Table 2 lists some of the changes in this version of the documentation to support release 8.1 of the
software.
Table 2. Whats New in Siebel Installation Guide for Microsoft Windows, Version 8.1
Topic Description
About Installing Siebel Releases
on page 17
Updated topic.
Overview of Installing Siebel
Business Applications on page 22
If you are deploying Siebel Self-Service Applications, first
install and configure Siebel Business Applications software as
described in this guide.
For more information about Self-Service Applications
requirements, see Siebel Self-Service Application
Deployment Guide and related guides.
Overview of Installing Siebel
Business Applications on page 22
General Requirements for Siebel
Enterprise Server Installation and
Configuration on page 93
Performing Tasks for Configuring
Siebel Gateway Name Server, Siebel
Enterprise, and SWSE Logical
Profile on page 148
Many other topics in this guide
Authentication for the Siebel Gateway Name Server is now
provided. As a result, the overall installation and
configuration process has changed.
If you do not have an existing Siebel Database, you now
install the Siebel Database before you configure the Siebel
Server.
The Language in Which Siebel
Installers and Wizards Run on
page 29
This version of Siebel Business Applications now supports
installing Siebel Language Packs for Polish, Russian, and
Turkish, in addition to previously available languages.
Many limitations apply for the languages supported for the
user interface text of Siebel installers and wizards. The
installers for Siebel Mobile Web Client and Siebel Tools can
display the user interface only in the languages supported by
the Oracle Universal Installer framework.
For more information about languages, see Siebel GlobalDeployment Guide and Siebel System Requirements and
Supported Platforms on Oracle Technology Network.
7/29/2019 Sie Bins TwinSie Bins Twin
13/335
Whats New in This Release
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A 13
Configuring an Oracle Database for
Siebel Business Applications on
page 43
Configuring an IBM DB2 Database
for Siebel Business Applications on
page 51
Siebel System Requirements and
Supported Platforms on Oracle
Technology Network
Supported versions of some RDBMS platforms have changed.
Some database configuration parameters or settings have
changed for the affected platforms:
Oracle Database 11g is now supported (in addition to
Oracle Database 10g).
IBM DB2 v9 is now supported (instead of v8). IBM DB2 for
z/OS (v8) is still supported. (These database products are
sometimes identified with names that include UDB, for
Universal Database.)
Obtaining Siebel Installation Media
Files on page 71
Preparing to Create a Siebel
Installation Image on page 75
Creating a Siebel Installation
Image on page 79
Siebel media DVDs now contain ZIP files instead of JAR files.
For version 8.1.1, the Siebel Image Creator utility no longerpresents a choice between Siebel Industry Applications and
Siebel Business Applications (Siebel Cross-Industry
Applications). When you use Image Creator, the correct
application type for the specific release is enforced.
Installing and Deploying Additional
Languages on page 106
Performing Tasks for Configuring
the Siebel Server on page 158
Performing Tasks for Configuring
the SWSE on page 163
The Configuration Wizards for Siebel Server and Siebel Web
Server Extension now allow you to add deployed languages.
Use this option for languages that were previously installed
but not deployed, or for languages that were newly installed
using an add language installation task.
Installing Using the Siebel
FastTrack Wizard on page 121
The Siebel FastTrack Wizard now supports Oracle Database as
well as Microsoft SQL Server.
About Siebel Management Agent
and Siebel Management Server on
page 124
Added a comment about the support for Java Management
Extension (JMX) interfaces for Siebel Management Agent. For
more information, see Siebel System Monitoring and
Diagnostics Guide.
Configuration Wizard Changes in
Release 8.0 and Later on page 134
Added information about configuration-related changes in
version 8.1 for Siebel Enterprise Server and Siebel Web
Server Extension (SWSE).
Table 2. Whats New in Siebel Installation Guide for Microsoft Windows, Version 8.1
Topic Description
7/29/2019 Sie Bins TwinSie Bins Twin
14/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A
Whats New in This Release
14
Performing Tasks for Configuring
Siebel Gateway Name Server, Siebel
Enterprise, and SWSE Logical
Profile on page 148
Added a table listing the settings in the Configuration Wizard
tasks for configuring the Siebel Gateway Name Server and
Siebel Enterprise.
The settings for configuring the SWSE logical profile and the
SWSE were already documented in version 8.0.
The Siebel Enterprise configuration task now configures
authentication for subsequent access to the Gateway Name
Server using Configuration Wizards or Server Manager.
The Siebel Enterprise configuration task for configuring
security authentication no longer enables the configured
security adapter for the Enterprise, as it did for version 8.0.
The Siebel Enterprise configuration task now includes
settings to support using the password salt feature. For more
information, see Siebel Security Guide.
Performing Tasks for Configuring
the Siebel Server on page 158
Added a table listing the settings in the Configuration Wizard
tasks for configuring the Siebel Server.
The Siebel Server configuration task now uses Gateway Name
Server authentication.
The Siebel Server Configuration Wizard now includes a task
for deploying newly installed languages on an existing Siebel
Server that you previously configured.
Performing Tasks for Configuring
the SWSE on page 163
Configuring the SWSE on
page 230
The SWSE Configuration Wizard now includes a task for
deploying newly installed languages on an existing SWSE that
you previously configured.
Configuring Siebel Management
Agent and Siebel Management
Server on page 180
Options related to Secure Socket Layers (SSL) have been
updated in the Management Agent and Management Server
Configuration Wizard tasks.
Setting Up Your Environment to
Support Global Time Zone on
page 202
Time zone configuration for daylight savings time has been
enhanced. For more information, see Siebel Global
Deployment Guide.
Requirements for SWSEInstallation and Configuration on
page 223
Support for heterogeneous SWSE configuration has beenenhanced. A workaround formerly applicable in one
heterogeneous scenario is no longer necessary.
Table 2. Whats New in Siebel Installation Guide for Microsoft Windows, Version 8.1
Topic Description
7/29/2019 Sie Bins TwinSie Bins Twin
15/335
Whats New in This Release
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A 15
Additional Changes Find the Siebel Bookshelfand Siebel System Requirements and Supported Platforms on Oracle
Technology Network.
NOTE: The Siebel Bookshelfis available on Oracle Technology Network (OTN) and Oracle
E-Delivery. It might also be installed locally on your intranet or on a network location.
Find Siebel Maintenance Release Guide on My Oracle Support (pending availability of patch
releases).
Find Oracle Global Customer Support documents (formerly published as Siebel Alerts, Technical
Notes, and FAQs) on My Oracle Support.
About Installing the Siebel Client
on page 247
Installing the Siebel Mobile Web
Client and Developer Web Client on
page 251
The installer for the Siebel Mobile and Developer Web Clients
is now based on the Oracle Universal Installer framework,
rather than InstallShield installer technology.
About Installing Siebel Tools on
page 273
Installing the Siebel Tools Client
on page 276
The installer for the Siebel Tools Client and Siebel Business
Rules Developer is now based on the Oracle Universal
Installer framework, rather than InstallShield installer
technology.
Installing Siebel Reports Server Removed chapter. The Actuate products formerly provided as
Siebel Reports Server are no longer shipped with orsupported by Siebel CRM version 8.1 or later.
Reporting functionality is now available using Oracle Business
Intelligence Publisher. For more information, see Siebel
Reports Guide.
Installing on Multiple Servers
Using Siebel Update Server
Removed chapter. Siebel Update Server and Siebel Update
Client are no longer shipped with or supported by Siebel CRM
version 8.1 or later.
Chapter 14, Uninstalling Siebel
Business Applications
Removed information about uninstalling Siebel Reports
Server (Actuate). For information about uninstalling a
previous version of Siebel Reports Server, refer to that earlier
version of the Siebel Installation Guide for the operatingsystem you are using.
Uninstallation for the Siebel client, Siebel Tools, and Siebel
Business Rules Developer has changed in various ways as
part of moving the installers for these modules to Oracle
Universal Installer.
Table 2. Whats New in Siebel Installation Guide for Microsoft Windows, Version 8.1
Topic Description
7/29/2019 Sie Bins TwinSie Bins Twin
16/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A
Whats New in This Release
16
7/29/2019 Sie Bins TwinSie Bins Twin
17/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A 17
2 Preparing to Install SiebelBusiness Applications
This chapter provides information to help you prepare for installing Siebel Business Applications
software. This chapter includes the following topics:
About the Deployment Planning Worksheet on page 17
About Installing Siebel Releases on page 17
About Installing in Upgrade Environments on page 20
About the Windows and UNIX Versions of This Guide on page 21
Overview of Installing Siebel Business Applications on page 22
General Considerations in Planning Your Siebel Deployment on page 23
About the Deployment PlanningWorksheetThe Deployment Planning Worksheet is an integral part of the installation process.
Before proceeding, go to Appendix A, Deployment Planning Worksheet,and make a copy of the
worksheet. Using the copy, the deployment team fills out the first section. Members of the team fill
out the information in the sections for which they are responsible. As you work through the
preparation steps in this chapter, you are prompted to record information you will need while
installing and configuring Siebel Business Applications.In subsequent chapters, you will be prompted to refer to the Deployment Planning Worksheet for
specific information about your site and deployment. You will also use it to record other important
information for future installations, upgrades, reconfiguration, and expansion of your deployment.
About Installing Siebel ReleasesEach Siebel Business Applications software release from Oracle has a specific version or release level.
A full installation can be performed for the base release applicable to this guide. This document
assumes the base release to be version 8.1.1. The procedures in this guide are for performing full
installations of the base release. An installation of Siebel Business Applications software at the base
release version is a base installation.
7/29/2019 Sie Bins TwinSie Bins Twin
18/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A
Preparing to Install Siebel Business Applications About Installing Siebel Releases
18
About Maintenance ReleasesAdditional releases are typically provided subsequent to a base release that can be installed on top
of your existing base installation. Such releases are collectively known as maintenance releases, and
are sometimes calledpatch releases. Patch releases include Fix Pack releases and Quick Fix releases.
Fix Pack releases that can be installed on top of a version 8.1.1 base installation are four-digit
releases versioned 8.1.1.x. Subsequently, a later Fix Pack release can also be installed.
NOTE: References in this guide to Siebel version numbers later than version 8.1.1 are for example
or illustrative purposes only. You must verify the availability, characteristics, and requirements of any
future releases, including version 8.1.1.x patch releases, that may also be covered by this guide (or
updated versions of it) or by other documentation. Installation tasks and requirements for all future
releases are subject to change.
About the Siebel Network Image
For each Siebel Business Applications release representing the products you have purchased, yourun the Image Creator utility to create a Siebel network image. All installations of Siebel Business
Applications must be performed from a network image.
About Documented RequirementsBefore installing any Siebel release, observe all documented requirements and review documented
installation tasks. Refer to this guide or any updated version of it, the Siebel Maintenance Release
Guide on My Oracle Support, and any other relevant documents on Oracle Technology Network or My
Oracle Support. Documentation for each Quick Fix release is provided with the release.
As an example of an installation requirement, before installing a patch release for Siebel Enterprise
Server, you must shut down services for Siebel Server or Siebel Gateway Name Server, and shut
down any running instances of srvrmgr. Before installing a patch release for Siebel Web ServerExtension, you must stop the Web server.
In general, if you reinstall a maintenance release for any reason, existing files previously delivered
for this maintenance release are not overwritten. Any missing files will, however, be redelivered. (If
you are aware of any corrupt file for which an updated file should be delivered as part of a
maintenance release, remove the corrupt file before reinstalling.)
All Siebel modules used within a given Siebel Enterprise must share the same release level (version
number), such as 8.1.1 or 8.1.1.1.
After any Siebel release is installed, including a base release or a maintenance release, the browser
health check (if enabled) will run when a user logs in for the first time.
About Configuration TasksAfter installation, you configure server modules using the Siebel Configuration Wizards.
Configuration is done after installing the base release, or after installing the base release and
available patch releases. For more information about configuration tasks for different installation
scenarios, seeOverview of Installing and Configuring Servers in a Siebel Deployment on page 85.
7/29/2019 Sie Bins TwinSie Bins Twin
19/335
Preparing to Install Siebel Business Applications About Installing Siebel Releases
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A 19
Typically, no configuration tasks of this type are associated with installing a patch release: you would
not run the Siebel Configuration Wizard to configure a module that was already configured. However,
requirements may vary for a given patch release, or for using particular supported languages or
features.
About Language InstallationIf you have added any languages to your deployment since you initially installed any maintenance
release, all applicable maintenance releases must be reinstalled in order to bring the new languages
up to the same release level as the rest of the installed software. Additional steps would be required
to deploy newly installed languages.
If you are installing or deploying a language for the first time in an existing installation, it is
recommended to install the latest maintenance release before you add the language to the Siebel
Database using the Database Configuration Wizard. SeeAbout Installing and Deploying Siebel
Business Applications with Multiple Languages on page 100. See also Chapter 7, Configuring the
Siebel Database.
About Slipstream Patch InstallationDepending on the installation requirements for particular releases, you may be able to set up your
installations so that a Fix Pack or Quick Fix release will be automatically installed immediately
following a full installation of the base release, in a chained fashion. This type of installation is
sometimes referred to as slipstream patch installation. For example, if the base release is version
8.1.1 and Fix Pack release 8.1.1.1 is available and installable as a patch release, you may be able to
install these releases together, in sequence.
Slipstream patch installation is supported for server modules such as the Siebel Enterprise Server or
Siebel Web Server Extension installers. Slipstream patch installation is not supported for the Siebel
Mobile Web Client or Siebel Tools installers, which use Oracle Universal Installer technology.
NOTE: Before you install the base release, note whether maintenance releases are also available,
review installation requirements, and determine whether to install your releases together using
slipstream patch installation.
Related InformationFor related information, see the following:
For information about obtaining Siebel media files and about creating the Siebel network image,
seeObtaining Siebel Installation Media Files on page 71 and subsequent topics.
Installation of Siebel modules is described in later chapters in this guide, such as Chapter 5,Installing Siebel Enterprise Server and Related Components.
Uninstallation of Siebel modules is described in Chapter 14, Uninstalling Siebel Business
Applications.
For details on browser configuration and related requirements, see Siebel System Administration
Guide. See also Siebel System Requirements and Supported Platforms on Oracle Technology
Network.
7/29/2019 Sie Bins TwinSie Bins Twin
20/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A
Preparing to Install Siebel Business Applications About Installing in Upgrade
Environments
20
For detailed information about installing maintenance releases (including slipstream patch
installation), about uninstalling maintenance releases (where applicable), about the features or
other changes provided in all applicable maintenance releases for your Siebel Business
Applications, and about configuration requirements for such features, see Siebel MaintenanceRelease Guide on My Oracle Support.
About Installing in UpgradeEnvironmentsWhen you install Siebel Business Applications, you may be creating a new deployment or you may
be installing updated software to be used in a deployment that is being upgraded from a previous
release of Siebel Business Applications, such as an upgrade from version 8.0 to version 8.1.1. Such
a deployment is sometimes called an upgrade environment.
You install your new Siebel Business Applications software before upgrading the Siebel Database.
NOTE: Some upgrade scenarios may also include migration to use the Siebel Industry Applications
repository. For more information, see 549362.1 (Doc ID) and related articles on My Oracle Support.
See alsoAbout Installing Siebel Releases on page 17.
For detailed information about upgrading the Siebel Database, and about tasks you perform before
installing or upgrading, see Siebel Database Upgrade Guide or Siebel Database Upgrade Guide for
DB2 for z/OS. See also any relevant documents on Oracle Technology Network or My Oracle Support.
Review all applicable documentation before you install or upgrade.
CAUTION: As part of installing Siebel Business Applications 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 installthe component called Database Configuration Utilities on a Siebel Server, as
described in Chapter 5, Installing Siebel Enterprise Server and Related Components.
You do not create the database instance on the RDBMS, as described in Chapter 3, Configuring
the RDBMS.(After the upgrade is complete, you may need to modify database parameters for
your RDBMS platform to match settings described in that chapter.)
You do not perform the tasks described in Chapter 7, Configuring the Siebel Database.
Certain installation and configuration requirements associated with Siebel Gateway Name Server
authentication that apply for new deployments do not apply in this case. For details, seeGeneral
Requirements for Siebel Enterprise Server Installation and Configuration on page 93.
After installing and upgrading, additional tasks may apply. For example, some tasks that may apply
are described in Siebel Application Deployment Manager Guide and Going Live with Siebel Business
Applications. See alsoPreparing to Run Siebel Server Components After Installation and Configuration
on page 170.
When you install Siebel Business Applications in some upgrade scenarios, you may in some cases be
able to install different versions of a Siebel module on the same computer, if this scenario is valid for
particular modules and may be helpful to you. For more information, seeInstalling Multiple Instances
of Siebel Business Applications on page 30.
7/29/2019 Sie Bins TwinSie Bins Twin
21/335
Preparing to Install Siebel Business Applications About the Windows and UNIX
Versions of This Guide
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A 21
After installing the base release (such as version 8.1.1), you can install any applicable patch releases
(such as Fix Pack or Quick Fix releases). In general, you install such patch releases before you initiate
the upgrade process. After upgrading, you can install additional patch releases when they become
available.
CAUTION: After you have started upgrading, do not install any patch releases until the upgrade is
complete.
For information about installing patch releases for version 8.1, seeAbout Installing Siebel Releases
on page 17 and see Siebel Maintenance Release Guide on My Oracle Support.
Instructions in this guide apply both for new installations and upgrades, except where noted.
About the Windows and UNIX Versions
of This GuideThis book, the Siebel Installation Guide for the operating system you are using is provided inseparate versions for Microsoft Windows or UNIX operating systems:
Siebel Installation Guide for Microsoft Windows
Siebel Installation Guide for UNIX
Supported UNIX operating systems include IBM AIX, HP-UX, Linux, and Sun Solaris.
Information about supported Linux operating systems is provided in Siebel Installation Guide for
UNIX. Linux is treated in this guide as a UNIX operating system. Specific supported Linux operating
systems are listed in Siebel System Requirements and Supported Platforms on Oracle Technology
Network. In Siebel Installation Guide for UNIX, supported Linux operating systems are usually
discussed in generic terms and are not differentiated. However, some information in this guide may
apply only to particular Linux operating systems.
NOTE: For all operating system support details, including supported versions and product support
exceptions, see Siebel System Requirements and Supported Platforms on Oracle Technology
Network.
Both the Windows and UNIX versions of this guide contain information about installing client-based
modules, such as Siebel Tools or the Siebel Mobile Web Client, on Microsoft Windows.
In general, Siebel Installation Guide for UNIXdoes not contain detailed information about installing
server-based modules on Windows, particularly Siebel Enterprise Server and Siebel Web Server
Extension (SWSE).
NOTE: Siebel Management Server is a server module that is available only on Windows, but is
documented in both versions of this guide. Siebel Collaboration Service is also covered, to a lesserextent. Some information relevant to configuring these modules is provided only in Siebel
Installation Guide for Microsoft Windows.
Siebel Installation Guide for UNIXdoes not contain information about either Microsoft SQL Server or
Microsoft Internet Information Services (the Web server also referred to as Microsoft IIS).
Siebel Installation Guide for Microsoft Windows does not contain information about UNIX-based Web
servers.
7/29/2019 Sie Bins TwinSie Bins Twin
22/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A
Preparing to Install Siebel Business Applications Overview of Installing Siebel
Business Applications
22
In this guide, the term Windows refers to all Microsoft Windows operating system versions listed as
supported for server or client platforms (for applicable Siebel modules) for this release in Siebel
System Requirements and Supported Platforms on Oracle Technology Network.
References in this guide (primarily in Siebel Installation Guide for UNIX) to UNIX operating systems
are sometimes in placeholder form, such as UNIX_OS. Such references, which are explained in
context, may refer to an operating system name (for example, HP-UX) or to a directory or file name
element that corresponds to an operating system (for example, HPUX or hp).
Overview of Installing Siebel BusinessApplicationsThe server installation process requires multiple tasks that you perform in the following general
sequence. For an illustration of part of this task flow, see Overview of Installing and Configuring
Servers in a Siebel Deployment on page 85.
1 Planning your deployment. See Siebel Deployment Planning Guide.
For example, you might install and configure server clustering software.
2 Determining your load-balancing strategy. See Siebel Deployment Planning Guide and seeConfiguring Load Balancing for Siebel Business Applications on page 172.
3 Creating your database instance. See Chapter 3, Configuring the RDBMS.
NOTE: You can create the database instance at any point before you run the Database
Configuration Wizard and perform the tasks noted in Step 9 on page 23. Most database tasks do
not apply if you have an existing Siebel Database, such as in an upgrade environment.
4 Obtaining Siebel media and creating a Siebel installation image on the network, from whichinstalls will be performed. See Chapter 4, Creating the Siebel Installation Image on the Network.
5 Installing required third-party products. See Siebel System Requirements and SupportedPlatforms on Oracle Technology Network. See also the Siebel Business Applications Third-Party
Bookshelfin the product media pack on Oracle E-Delivery.
6 Creating directories for Siebel Business Applications software and the Siebel File System. SeeGeneral Considerations in Planning Your Siebel Deployment on page 23.
7 Creating the required Siebel accounts. SeeCreating the Siebel Service Owner Account onpage 39.
8 Installing and configuring the Siebel Enterprise Server components.
You install Siebel Gateway Name Server, Siebel Server, and Database Configuration Utilities.
Then you run the Siebel Configuration Wizard to configure the Siebel Gateway Name Server,
Siebel Enterprise, and Siebel Web Server Extension (SWSE) logical profile.
NOTE: If you have no existing Siebel Database, you configure the Siebel Server after you install
the Siebel Database (see Step 9 on page 23). For more information, see the Gateway Name
Server authentication content inGeneral Requirements for Siebel Enterprise Server Installation
and Configuration on page 93.
7/29/2019 Sie Bins TwinSie Bins Twin
23/335
Preparing to Install Siebel Business Applications General Considerations in Planning
Your Siebel Deployment
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A 23
For more information about installation and configuration tasks, see:
Chapter 5, Installing Siebel Enterprise Server and Related Components
Chapter 6, Configuring Siebel Enterprise Server and Related Components
Configuring the SWSE on page 230 (task for configuring SWSE logical profile)
9 Running the Database Configuration Wizard on the Siebel Server computer where you installedDatabase Configuration Utilities. You run the task to install the Siebel Database, which creates
the schema on the RDBMS and adds seed data and Siebel repository data (for the primary
language only). Additional steps apply for each additional language. See Chapter 7, Configuring
the Siebel Database.
NOTE: Most database tasks do not apply if you have an existing Siebel Database, such as in an
upgrade environment.
10 Configuring the Siebel Server. See Chapter 6, Configuring Siebel Enterprise Server and Related
Components.11 Installing your Web server, and installing and configuring the SWSE (applying the SWSE logical
profile). See Chapter 8, Installing and Configuring the Siebel Web Server Extension.
12 (Optional) Installing Siebel Search software.
NOTE: For specific guidelines and requirements about installing search software, see Siebel
Search Administration Guide.
13 (Optional) Installing Siebel Mobile Web Clients or Developer Web Clients. See Chapter 9,Installing Siebel Mobile Web Clients.
14 Installing Siebel Tools for developers. See Chapter 10, Installing Siebel Tools.
15 (Optional) Installing additional Siebel modules, such as Siebel Charts. See Chapter 11, Installing
Siebel Charts.
16 Verifying your environment using the Environment Verification Tool (EVT). See Chapter 13,Verifying Your Server Environment.
17 (Optional) Installing and configuring additional Siebel Server instances, or additional Web serverand SWSE instances, if required for your deployment.
18 (Optional) If you are deploying Siebel Self-Service Applications, follow the instructions in SiebelSelf-Service Application Deployment Guide.
General Considerations in Planning Your
Siebel DeploymentYou must plan where to install the various Siebel components on your servers. This topic contains
several subtopics about issues you must consider.
Planning Topologies on page 24
Preparing the Hardware on page 25
Planning Siebel Server Load Balancing on page 26
7/29/2019 Sie Bins TwinSie Bins Twin
24/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A
Preparing to Install Siebel Business Applications General Considerations in Planning
Your Siebel Deployment
24
Planning Disk Space Requirements on page 26
Planning RDBMS Installation and Configuration on page 26
Managing Siebel Image Directories and Media Files on page 28
Managing Temporary Disk Space Required by Siebel Installers and Wizards on page 28
The Language in Which Siebel Installers and Wizards Run on page 29
Installing Multiple Instances of Siebel Business Applications on page 30
Specifying the Locale for Siebel Business Applications on page 32
Restrictions on Host Names for Siebel Gateway Name Server and Siebel Server on page 32
Restrictions on Names for Siebel Enterprise Server and Siebel Server on page 33
File and Directory Naming Conventions on page 34
Creating the Siebel File System on page 35
Creating the Siebel Service Owner Account on page 39
Planning Topologies
This topic is part ofGeneral Considerations in Planning Your Siebel Deployment on page 23.
Consider running specialized components on dedicated computers. Whether you do so depends on
considerations that include available resources, overall load, and performance.
NOTE: All Siebel modules used within a given Siebel Enterprise must share the same release level.
For additional information about Siebel releases, seeAbout Installing Siebel Releases on page 17.
Third-party products must use supported release levels as documented in Siebel SystemRequirements and Supported Platforms on Oracle Technology Network.
See also the following topics later in this chapter:
Installing Multiple Instances of Siebel Business Applications on page 30
Restrictions on Host Names for Siebel Gateway Name Server and Siebel Server on page 32
Restrictions on Names for Siebel Enterprise Server and Siebel Server on page 33
File and Directory Naming Conventions on page 34
Creating the Siebel File System on page 35
Record the computer names and installation directory names you decide on in your copy of the
worksheet in Appendix A, Deployment Planning Worksheet.
For more information about planning your topologies, see Siebel Deployment Planning Guide. See
also Siebel Performance Tuning Guide.
7/29/2019 Sie Bins TwinSie Bins Twin
25/335
Preparing to Install Siebel Business Applications General Considerations in Planning
Your Siebel Deployment
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A 25
Planning the Web Server TopologyBefore you install the Siebel Web Server Extension (SWSE), as described in Chapter 8, Installing and
Configuring the Siebel Web Server Extension,you must decide how you will distribute the Web servers
and other components.
Single-node. Installation of Siebel Enterprise Server components and your Web server and
SWSE on a single computer or node. (If you do this, use separate installation directories to avoid
file permission problems at installation time.)
Distributed.Distribution of the preceding components, where multiple Web servers connect tomultiple Siebel Servers in the Siebel Enterprise. These Web servers can be dynamically balanced
across Application Object Manager components on different Siebel Server computers.
Each deployment choice involves 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 Web server and the Siebel Server (with Application
Object Manager) on different computers eliminates contention for CPU and other serverresources. 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 impact of failure on any one computer.
Greater flexibility with firewalls. Putting the Web components of the Siebel Business
Applications on a different computer from the Siebel Server with Application Object Managers
lets you deploy your Web server in the DMZ while keeping the Enterprise Server behind a secure
firewall.
High availability. A multinode configuration is required for deployments that support large
numbers of concurrent users or where high availability is an operating requirement.
For more information, see Siebel Deployment Planning Guide. See also Siebel Security Guide.
Preparing the Hardware
This topic is part ofGeneral Considerations in Planning Your Siebel Deployment on page 23.
Verify that the hardware you have chosen meets all requirements for running your Siebel Business
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 Name Server,
Siebel Server, and other Siebel modules. Also plan to support Siebel Tools developer workstations
and Siebel Mobile Web Clients, where applicable. For more information, see subsequent chapters for
installing these modules. See also Siebel Deployment Planning Guide.
For size limitations and information on required third-party software, see Siebel System
Requirements and Supported Platforms on Oracle Technology Network.
7/29/2019 Sie Bins TwinSie Bins Twin
26/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A
Preparing to Install Siebel Business Applications General Considerations in Planning
Your Siebel Deployment
26
Planning Siebel Server Load Balancing
This topic is part ofGeneral Considerations in Planning Your Siebel Deployment on page 23.
Before you install your Siebel Enterprise Server components, determine your load balancing strategy
for Siebel Servers. For more information, seeConfiguring Load Balancing for Siebel Business
Applications on page 172. See also Siebel Deployment Planning Guide and Siebel System
Administration Guide.
Planning Disk Space Requirements
This topic is part ofGeneral Considerations in Planning Your Siebel Deployment on page 23.
Before you install, you must anticipate your disk space requirements for each installable Siebel
module. Each Siebel installer displays the required disk space for the installed software before files
are copied.
You must also anticipate the disk space required for Siebel image directories. For more information,
seeManaging Siebel Image Directories and Media Files on page 28 and Chapter 4, Creating the Siebel
Installation Image on the Network.
Siebel installers also have temporary disk space requirements, as described inManaging Temporary
Disk Space Required by Siebel Installers and Wizards on page 28.
Planning RDBMS Installation and Configuration
This topic is part ofGeneral Considerations in Planning Your Siebel Deployment on page 23.
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 Chapter 3, Configuring the RDBMS.For
more information about configuring the Siebel Database after installing Siebel Enterprise Server, see
Chapter 7, Configuring the Siebel Database.
Make sure that this release of Siebel Business Applications supports the exact version of your
chosen RDBMS, as specified in Siebel System Requirements and Supported Platforms on Oracle
Technology Network, and that the RDBMS has been installed on its designated server. This server
will hold the database tables containing your business data, such as sales (personnel, territories,
opportunities, and activities), marketing, and customer service information.
Verify that the network name of the server that will support the Siebel Database is properly
recorded in your copy of the worksheet in Appendix A, Deployment Planning Worksheet.
The Siebel Enterprise Server installer creates the ODBC data source name during installation,
using the name EnterpriseName_DSN. For example, if your Siebel Enterprise Server name is
SBA_81, the ODBC data source name will be SBA_81_DSN. Using this pattern, determine what
your ODBC data source name will be and record it in your copy of the worksheet in Appendix A,
Deployment Planning Worksheet.
7/29/2019 Sie Bins TwinSie Bins Twin
27/335
Preparing to Install Siebel Business Applications General Considerations in Planning
Your Siebel Deployment
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A 27
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 scripts in the repository during import or export processes. See also topics
for verifying the ODBC data source for your RDBMS platform, such as those inVerifying the ODBCData Source on page 166.
Siebel client installers also create ODBC data source names during installation. The naming
convention is different than ODBC data source names created by the Siebel Enterprise Server
installer. For more information, see Chapter 9, Installing Siebel Mobile Web Clients,and
Chapter 10, Installing Siebel Tools.
About Database Code Pages and Locale SupportIn a database environment that is enabled for Unicode, you can install any of the available Siebel
Language Packs.
However, in a database environment that is not enabled for Unicode, you must consider thecorrelation of the Language Packs 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.
For a list of supported code pages and encoding strategies, see Siebel System Requirements and
Supported Platforms on Oracle Technology Network. See also Siebel Global Deployment Guide.
See alsoSpecifying the Locale for Siebel Business Applications on page 32.
See also the topics that apply to your RDBMS platform in Chapter 3, Configuring the RDBMS.
Planning Database ConnectivityUse the ODBC driver versions listed in Siebel System Requirements and Supported Platforms on
Oracle Technology Network for your chosen RDBMS for Siebel Servers, Siebel Tools clients, and
Siebel Developer Web Clients (if applicable). Make sure that ODBC connectivity uses TCP/IP as the
transport layer protocol for your Siebel Servers, Siebel Tools clients, and Siebel Developer Web
Clients.
How to Use This Guide If Your Database Is IBM DB2 for z/OSThis guide describes installation of Siebel 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.)
NOTE: The Siebel Bookshelfis available on Oracle Technology Network (OTN) and Oracle E-Delivery.
It might also be installed locally on your intranet or on a network location.
7/29/2019 Sie Bins TwinSie Bins Twin
28/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A
Preparing to Install Siebel Business Applications General Considerations in Planning
Your Siebel Deployment
28
Customers for IBM DB2 for z/OS will require this guide (Siebel Installation Guide for the operating
system you are using) and will require Implementing Siebel Business Applications on DB2 for z/OS.
Both of these guides are available on the Siebel Bookshelf.
NOTE: In this guide, Chapter 3, Configuring the RDBMS,and Chapter 7, Configuring the Siebel
Database,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,
see also Siebel Database Upgrade Guide for DB2 for z/OS. For information about relevant
requirements related to authentication for the Siebel Gateway Name Server, seeGeneral
Requirements for Siebel Enterprise Server Installation and Configuration on page 93.
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 Business Applications, and specific procedures for moving data
from development to production. Also consult all other applicable Siebel Bookshelfdocumentation,
such as Siebel Security Guide.
Managing Siebel Image Directories and Media Files
This topic is part ofGeneral Considerations in Planning Your Siebel Deployment on page 23.
All Siebel Business Applications modules are installed from a Siebel image you create on the network
using the Siebel Image Creator utility. Each Siebel release has its own version-specific network
image, whether it is a base release or a patch release.
You will need to allocate space on the network for Siebel images that are to be used as the source
location for Siebel installations. Retain all network images until they no longer apply.
Also retain all Siebel media files, including any ZIP files you obtain and the JAR files you use to create
the Siebel image on the network.
For complete information about obtaining Siebel media and using Siebel Image Creator, see
Chapter 4, Creating the Siebel Installation Image on the Network.
Managing Temporary Disk Space Required by SiebelInstallers and Wizards
This topic is part ofGeneral Considerations in Planning Your Siebel Deployment on page 23.
Siebel installer programs, the Siebel Image Creator utility, and Siebel Configuration Wizards 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 to periodically clear out the temporary directory you are using. You may need 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.
7/29/2019 Sie Bins TwinSie Bins Twin
29/335
Preparing to Install Siebel Business Applications General Considerations in Planning
Your Siebel Deployment
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A 29
CAUTION: A nondefault temporary directory name you specify must not include spaces, in order to
avoid problems associated with how Microsoft Windows handles long path names. Installers or
wizards may fail if this problem is encountered.
When you run a Siebel installer or wizard, you can optionally specify the temporary directory the
program will use in place of the directory specified by TEMP and TMP. For example, when installing
Siebel Enterprise Server on Windows, you can use a command like the following:
setup.exe -is:tempdir temp_directory_location
For more information about command-line options for Siebel installers, seeCommand-Line Options
for Siebel Installers and Wizards on page 130.
The user running the installer or wizard must have privileges that include write permission for the
temporary directory.
Table 3 on page 29 shows the minimum disk space required by Siebel installers and wizards (by
operating system), along with the default temporary directory locations.
To verify the name of your temporary d ir ector y
From a DOS command prompt, enter the commands set temp and set tmp.
The Language in Which Siebel Installers and WizardsRun
This topic is part ofGeneral Considerations in Planning Your Siebel Deployment on page 23.
When you launch Siebel installer programs, the Siebel Image Creator utility, or Siebel Configuration
Wizards, the user interface text is in one of the languages supported for Siebel Business Applications.
For Siebel installers and the Siebel Image Creator utility, the language in which the program launches
is determined by the language for the locale of your operating system, where this language and
locale are supported for the current version of Siebel Business Applications and supported for the
installers.
Installers for Siebel server modules, Siebel Configuration Wizards, and Siebel Image Creator can run
in all languages corresponding to the available Siebel Language Packs, with the exceptions of Arabic,
Hebrew, Polish, Russian, Thai, and Turkish. You must use a different user interface language, such
as U.S. English.
Table 3. 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:)
7/29/2019 Sie Bins TwinSie Bins Twin
30/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A
Preparing to Install Siebel Business Applications General Considerations in Planning
Your Siebel Deployment
30
Installers for Siebel Mobile or Developer Web Client and Siebel Tools, which are based on Oracle
Universal Installer, run in the current language corresponding to the regional and language options
settings on the client computer, if the current language is one of the following: U.S. English, French,
German, Italian, Japanese, Korean, Brazilian Portuguese, Spanish, Chinese Simplified, or ChineseTraditional. For any other current language setting, the client installer runs in U.S. English.
For all Siebel installers or Siebel Image Creator, in order to change the user interface language, you
must change the current operating system language and locale. Make sure the language setting
under the regional option of your operating system is set to the desired choice of your language. The
language you select must one of those supported for Siebel installers.
For installers for Siebel server modules, if the current language is not supported and another
language is not specified (where applicable), then, when you launch the program, you are prompted
for the language in which to run the program.
For Siebel Configuration Wizards, the language in which the program launches is determined by the
following factors, in order of priority:
The setting of the LANG argument for the wizard, if specified. When the Configuration Wizard is
launched by the installer, the installer launches the wizard with the LANG argument set to the
language the installer ran in. For details, seeConfiguration Wizard Syntax Elements on page 144.
The setting of the SIEBEL_LANGUAGE environment variable, if defined.
The language for the locale of your operating system, if this language and locale are supported
for the current version of Siebel Business Applications.
For information about installing Language Packs for Siebel Business Applications, see About
Installing and Deploying Siebel Business Applications with Multiple Languages on page 100 and other
relevant topics.
Installing Multiple Instances of Siebel BusinessApplications
This topic is part ofGeneral Considerations in Planning Your Siebel Deployment on page 23.
This topic describes issues in installing multiple instances of similar or dissimilar versions of Siebel
Business Applications on the same computer.
Installing Multiple Instances of Similar Versions of Siebel BusinessApplications
By default, the Siebel installers automatically install Siebel Business Applications software in uniquedirectory names that will not conflict with other Siebel modules that you install on the same
computer. To install another instance of the same version of a module on a single computer (where
applicable), specify a custom installation path.
However, installing multiple instances of some modules may cause problems. For example:
You cannot install multiple instances of the same version of Siebel Gateway Name Server on the
same computer. The reason for this is that installing and configuring the Siebel Gateway Name
Server creates a service which cannot coexist in multiple instances for different installations.
7/29/2019 Sie Bins TwinSie Bins Twin
31/335
Preparing to Install Siebel Business Applications General Considerations in Planning
Your Siebel Deployment
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A 31
Restrictions apply for installing multiple instances of SWSE. For details, seeRequirements for
SWSE Installation and Configuration on page 223.
Restrictions apply for installing multiple instances of Siebel Tools, where Siebel Business RulesDeveloper is also installed. For details, seeRequirements for Siebel Tools Installation on
page 274.
For important related considerations, see alsoAbout Installing Siebel Releases on page 17 and
Planning Topologies on page 24.
NOTE: In this context, same version refers to all releases sharing the same first two digits, such as
8.1.1, 8.1.1.1, 8.1.1.2, 8.1.2 (if available), and so on.
Components of the same Siebel Enterprise Server that you install on the same computer mustbe
installed into the same root directory (such as C:\sba81 on Microsoft Windows or /siebel on UNIX).
These components include Siebel Gateway Name Server, Siebel Server, Database Configuration
Utilities, and EAI Connector. See alsoFile and Directory Naming Conventions on page 34.
NOTE: You cannot install additional Siebel Enterprise Server components into the root directory for
the installation after installing a patch release. In this case, you must uninstall the patch, install
additional Siebel modules as desired, and then reinstall the patch to all modules. For uninstalling a
patch, see Siebel Maintenance Release Guide on My Oracle Support. You can install additional
languages into a root directory after applying a patch, but you must reinstall the patch afterwards.
Installing Multiple Instances of Dissimilar Versions of Siebel BusinessApplicationsMultiple versions of some Siebel components can be installed on the same computer. Sometimes you
may need to do this as part of some upgrade scenarios. For more information about upgrading, see
Siebel Database Upgrade Guide.
Use naming conventions for your installation directories that reflect the component and the version
being installed, such as 81 for the current version. The default installation directories already
reference version 8.1 in this way.
Each Siebel Gateway Name Server must be installed on a separate computer, regardless of the
version.
For installation instructions, see Chapter 5, Installing Siebel Enterprise Server and Related
Components.
If you install multiple versions of the Siebel Server on the same computer, you must install them
in different directories (default installation directories are already different between versions).
For installation instructions, see Chapter 5, Installing Siebel Enterprise Server and Related
Components.
Restrictions apply for installing multiple instances of SWSE. For details, seeRequirements for
SWSE Installation and Configuration on page 223.
7/29/2019 Sie Bins TwinSie Bins Twin
32/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A
Preparing to Install Siebel Business Applications General Considerations in Planning
Your Siebel Deployment
32
Specifying the Locale for Siebel Business Applications
This topic is part ofGeneral Considerations in Planning Your Siebel Deployment on page 23.
When a Siebel application component (Siebel Server, Siebel Tools client, 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 may be defined elsewhere.
Do not explicitly set the NLS_LANG (Oracle-specific) or SIEBEL_CODEPAGE environment variables for
Siebel Business Applications. Windows Registry settings for these variables may be defined, but
these settings are not used for the database connection. These Registry settings affect any software
that runs on that computer (except for the Siebel Business Applications themselves).
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 notset automatically for Siebel
Business Applications using an Oracle Database connection. Therefore, settings you make for
NLS_SORT will affect any software that runs in the Siebel environment (including the Siebel Business
Applications).
CAUTION: For development environments, Siebel Business Applications support 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 orderand collation sequence are used interchangeably,
even though these terms may 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 for the Siebel Server. For more information about
creating or configuring this type of locale, see Siebel Applications Administration Guide and Siebel
Global Deployment Guide.
For more information, see:
Planning RDBMS Installation and Configuration on page 26
The topics that apply to your RDBMS platform in Chapter 3, Configuring the RDBMS
Restrictions on Host Names for Siebel Gateway NameServer and Siebel Server
This topic is part ofGeneral Considerations in Planning Your Siebel Deployment on page 23.
See alsoRestrictions on Names for Siebel Enterprise Server and Siebel Server on page 33, 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 Name Server or Siebel Server.
7/29/2019 Sie Bins TwinSie Bins Twin
33/335
Preparing to Install Siebel Business Applications General Considerations in Planning
Your Siebel Deployment
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A 33
The Siebel Gateway Name Server name is defined automatically based on the host name of the
server computer. However, problems may arise during configuration of Siebel modules unless the
following requirements are observed:
Host names for Siebel Gateway Name Server or Siebel Server must not include dashes
(hyphens). It is recommended to use an underscore if a separator character is required. For
example, host_sba81 is acceptable, but host-sba81 is not.
NOTE: A dash may not cause problems in every scenario, but problems have been observed in
many specific scenarios, as noted in 477993.1 (Doc 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 inRestrictions on Names
for Siebel Enterprise Server and Siebel Server on page 33.
The host name for Siebel Gateway Name Server must be no longer than 15 characters.
The Siebel Configuration Wizard task for configuring the Siebel Gateway Name Server cannotexecute successfully if the host name is longer than 15 characters.
(Configuration Wizard tasks for configuring the Siebel Enterprise and the Siebel Server also
validate that the name of the Siebel Gateway Name Server, 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 Name Server
computer to include domain information, as may be common in some UNIX environments. The
entire host name is subject to the 15-character limit mentioned above.
Restrictions on Names for Siebel Enterprise Server and
Siebel ServerThis topic is part ofGeneral Considerations in Planning Your Siebel Deployment on page 23.
This topic describes restrictions to observe when planning names you will give the Siebel Enterprise
Server and Siebel Server instances during configuration of Siebel Business Applications software.
See alsoRestrictions on Host Names for Siebel Gateway Name Server and Siebel Server on page 32.
Siebel Configuration Wizard tasks that specify or refer to the Siebel Enterprise name or the Siebel
Server name validate for some of the requirements below, such as the 12-character limit. More
validations are performed in live mode than in offline mode. Observe all documented restrictions
regardless of validation behavior.
Siebel Enterprise Server Naming RestrictionsThe following restrictions apply to naming Siebel Enterprise Servers:
Names must be no longer than 12 characters.
Names cannot be serveror enterprise. (Names such as enterprise1 are acceptable.)
7/29/2019 Sie Bins TwinSie Bins Twin
34/335
Siebel Installation Guide for Microsoft Windows Version 8.1, Rev. A
Preparing to Install Siebel Business Applications General Considerations in Planning
Your Siebel Deployment
34
Siebel Server Naming RestrictionsWhen 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 serveror enterprise. (Names such as server1 are acceptable.)
File and Directory Naming Conventions
This topic is part ofGeneral Considerations in Planning Your Siebel Deployment on page 23.
Use lowercase for all file names, directory names, path names, parameters, flags, and command-
line commands, unless you are instructed otherwise.
Directory names or file names may not contain special characters, including periods, apostrophes,
accents, number (pound or hash) signs, or ampersands. Underscores are acceptable. Spaces are not
allowed for server installs on Windows (though the operating system may otherwise allow it). Spaces
are acceptable for client installs on Windows.
How This Guide Refers to Your Installation DirectoriesThis 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.
SI EBEL_ ROOT. Generally, this refers to the main directory in which software for each Siebel
Enterprise Server component has been installed. The installers for the Enterprise Server components
install into the top-level directory C:\sba81 by default. Generally, this directory is what
SIEBEL_ROOTrepresents in this guide.
SI EBEL_ HOME. The installation or root directory for Siebel Business Applications software in
general, or of a specific module such as the Siebel Gateway Name Server or the Siebel Server,
depending on the context. Many scripts contain variables with this name; its meaning is most often
derived from the context.
SI EBSRVR_ ROOT. The installation or root directory for Siebel Server. By default, it is installed in
C:\sba81\siebsrvr.
SI EBEL_GATEWAY_ROOT. The installation or root directory for Siebel Gateway Name Server. By
default, it is installed in C:\sba81\gtwysrvr.
DBSRVR_ROOT . The directory into which you install the Siebel Database Configuration Utilities
(formerly referred to as the Siebel Database Server). By default, these utilities are installed in
C:\sba81\dbsrvr (on a Siebel Server computer).
7/29/2019 Sie Bins TwinSie Bins Twin
35/335
Preparing to Install Siebel Business Applications General Considerations in Planning
Yo