Installing Siebel CRM in a New Installation

Review Before You Install Siebel CRM and Installation Tasks for Siebel CRM and observe the requirements and recommendations.

For example, if you are installing Siebel Enterprise components that will communicate with an existing configured installation of Siebel Gateway on another computer or operating system instance, then make sure that the Siebel Gateway is running.

You can stop any Siebel Server or Siebel Gateway services running on the same computer where you are installing Siebel CRM. If you do not stop them, the installer will stop them for you.

Log on to the server computer:

(Windows) Log on to the server computer, using an account with administrative privileges, such as the Siebel service owner account that you recorded in the copy that you made earlier of the worksheet in Siebel Deployment Planning Worksheet. The account that you use must belong to the Windows domain of your Siebel CRM deployment and must have full write permissions to the Siebel File System.
(LINUX) Log on to the server computer, using the Siebel service owner account that you recorded in the copy that you made earlier of the worksheet in Siebel Deployment Planning Worksheet.

(Windows) Shut down all of the open programs that are running on the server.

Open a new window or shell. Navigate to the Siebel image location for your Siebel CRM 22.x release. For more information, see Creating the Siebel Installation Image on the Network.

(Windows) In Windows Explorer, navigate to the directory where the installer is located. Navigate to Siebel_Image\Disk1\install. In this path, Siebel_Image is the directory for your version-specific Siebel network image, such as C:\Siebel_Install_Image\25.2.
(LINUX) In the shell you opened, navigate to the directory where the installer is located. For example, for Linux, navigate to Siebel_Image/Disk1/install. In this path, Siebel_Image is the directory for your version-specific Siebel network image, such as /Siebel_Install_Image/25.2.

Verify the permissions to the directory into which you will install Siebel CRM. You must have write and execute permission.

(Windows) Before you run the Siebel CRM installer to perform the migration installation of a Siebel CRM module from a release prior to Siebel CRM 17.0, run the following command:

module.exe -debug -silent -attachhome ORACLE_HOME_NAME=Oracle_Home_Name ORACLE_HOME=Oracle_Home

For example, you might enter a command like this, depending on the Oracle home name for the module you are installing and on the original installation directory:

module.exe -debug -silent -attachhome ORACLE_HOME_NAME=SES_HOME ORACLE_HOME=c:\Siebel\ses

Start the Siebel CRM installer for the current release:

(Windows) To start the installer, double-click setup.bat.
(UNIX) To start the installer, enter the following command:
```
./runInstaller.sh -invPtrLoc inventory_location
```

In this command, inventory_location is the full path of the oraInst.loc file (for example,/export/home/oraInst.loc), which points to the OUI inventory location. Use the -invPtrLoc option if you want to specify an inventory pointer file other than the default.

Note: Optionally, for a silent (unattended) installation, you can append the flags described in the information about installing Siebel CRM in silent mode that is described in Installing Siebel CRM Using Silent Mode.

The Siebel Installation Location screen appears.

Specify the directory in which to install the software, and click Next.

(Windows) You might specify an installation path for a new installation like C:\Siebel, C:\Siebel_SES, C:\Siebel_AI, C:\Siebel_Client, C:\Siebel_Tools, or a similar value.
(LINUX) You might specify an installation path for a new installation like /Siebel, /Siebel_SES, /Siebel_AI, C:\Siebel_Client, C:\Siebel_Tools, or a similar value. Siebel Web Client and Siebel Tools can be installed only on Microsoft Windows.

Accept the default path or specify a different fully qualified path by typing it directly or by clicking Browse. If you have an existing installation, then you must specify a new path for the new installation. For more information about installation path requirements, see File and Directory Naming Conventions.

If you are adding languages or components to an existing installation of the same version, select the directory of the existing installation for which you want to add languages or components.

The Language Selection screen appears.

Select the languages that you want to install, and click Next.

All of the supported languages are available for selection for a new installation. You must select at least one language in order to proceed. To select a language, you click the name of the language in the Available box and then use the arrow controls to move it into the Selected box. Use Ctrl+click to select multiple languages.

Note: You specify the languages to install in order to run Siebel applications using these languages. The files that are specific to the languages chosen in this step will be copied to your installation. Language installation characteristics vary for different modules. For more information about language installation, see also Installation-Related Changes in Siebel CRM.

If you are adding languages to an existing installation of the same version, select the languages you want to add and proceed to complete the installation.

Note: When you configure the Siebel Server or the Siebel Application Interface in Siebel Management Console, you can specify which installed languages to deploy and which installed language is the primary language. Deploy the superset of all of the languages required by the Application Object Manager components you require in your Siebel deployment.

If you are adding components to an existing installation of the same version, proceed to the next step without selecting any languages.

The Component Selection screen appears.

For an installation into a production environment, do the following. For more information, see Installation-Related Changes in Siebel CRM. For a nonproduction environment, skip to Step 11.

Specify which components to install. Select one of the following:
- Siebel Enterprise Components. Includes Siebel Gateway, Siebel Server, Siebel Application Interface, and EAI Connector.
- Siebel Web Client. You can install and configure Siebel Web Client for use as either a Mobile Web Client or a Developer Web Client.
  
  For Siebel Mobile Web Client, Oracle Database SE2 must have been included when you prepared the product media in Creating the Siebel Installation Image on the Network, and are installed with Siebel Web Client. It may be automatically updated with later Siebel updates.
If you are adding components to an existing installation of the same version, select the components to add and proceed to complete the installation.
Specify which configuration tasks to perform later in the installation session. Select one or more of the following (available selections are based on the modules you are installing):
- Enterprise Container Configuration. See Step 12 through Step 14.
- Application Interface Container Configuration. See Step 12 through Step 14.
- Siebel Web Client Configuration. See Step 15.
Go to Step 12.

For an installation into a nonproduction (development or test) environment, do the following. For more information, see Installation-Related Changes in Siebel CRM.

Specify which components to install. Select one or more of the following:
- Siebel Enterprise Components. Includes Siebel Gateway, Siebel Server, Siebel Application Interface, and EAI Connector.
- New Database Repository. Available to select if you included this item when you prepared the media in Creating the Siebel Installation Image on the Network and if you chose Siebel Enterprise Components. You install the New Database Repository option once, together with the first Siebel Server installed. You must install it with a Siebel Server.
- Ancestor Database Repository. Available to select if you included this item when you prepared the media in Creating the Siebel Installation Image on the Network and if you chose Siebel Enterprise Components and New Database Repository.
- Siebel Web Client. You can install and configure Siebel Web Client for use as either a Mobile Web Client or a Developer Web Client.
  
  For Siebel Mobile Web Client, Oracle Database SE2 must have been included when you prepared the product media in Creating the Siebel Installation Image on the Network, and is installed with Siebel Web Client. Oracle Database client is automatically installed and updated as part of Siebel install. It will not be installed again for subsequent updates you install.
- Siebel Tools. Installs the Siebel Tools client.
If you are adding components to an existing installation of the same version, select the components to add and proceed to complete the installation.
Specify which configuration tasks to perform later in the installation session. Select one or more of the following (available selections are based on the modules you are installing):
- Enterprise Container Configuration. See Step 12 through Step 14.
- Application Interface Container Configuration. See Step 12 through Step 14.
- Siebel Web Client Configuration. See Step 15.
- Siebel Tools Configuration. See Step 16.
Click Next.

If you selected Enterprise Container Configuration or Application Interface Container Configuration, then the Application Container Ports screen appears.

Specify port numbers for this installation, and click Next.

Siebel Application Interface Port Details:

HTTPS Redirect Port. (Default: 443)
HTTP Connection Port. (Default: 80)
Shutdown Port. (Default: 8005)

Siebel Enterprise Components Port Details:

HTTPS Redirect Port. Used for secure HTTPS connections to the application container, which can include connections redirected from the HTTP port. (Default: 444)
HTTP Connection Port. Incoming connections on the HTTP port are redirected to the secure HTTPS port. (Default: 8081)
Shutdown Port. Used for management purposes by Siebel CRM, for local use only. (Default: 8006)

Note: Specifying these port numbers allows the application containers and other parts of the configuration framework to work together during and after the configuration and deployment tasks you perform using Siebel Management Console. The port numbers must be unique on each installation computer or operating system instance. See also Configuring Siebel CRM Server Modules.

If you selected Application Interface Container Configuration in a previous step, then the Application Interface Authentication screen appears.

Specify the appropriate authentication credentials for access to Siebel Management Console, and click Next.

User Name. Specify the user name to use when you log in to Siebel Management Console, as described in Starting the Siebel Management Console.
Password. Specify the password for this user name.
Confirm Password.
Application Context Name. Specify the name of the application context as defined in Siebel Application Interface. This name appears in all of the URLs for this installation. The default value is siebel. You can also change this value for an existing installation. For more information, see Customizing URLs for Siebel CRM Applications.

Note: You use the credentials specified here when you first log in to Siebel Management Console, after installing the first Siebel Application Interface node. These credentials, which are stored in the applicationinterface.properties file, are valid only before you have configured the security profile. After configuring security, you must log in to Siebel Management Console again with valid credentials for the authentication method specified in the security profile. Then, when you install any subsequent instance of Siebel Application Interface, you would also specify those same valid credentials (that are used by the first Siebel Application Interface node) for the specified authentication method, for example, user name sadmin and password mypwd.

If you selected Enterprise Container Configuration or Application Interface Container Configuration in a previous step, then the Client Authentication screen appears.

Specify information that supports secure communications for the installed software, and click Next. The installer does not require that separate files are specified. Use files that meet your security requirements.

Siebel Enterprise Components Authentication:

Keystore Name. Specify a file (such as a JKS file) you have generated that will serve as the keystore.
Truststore Name. Specify a file (such as a JKS file) you have generated that will serve as the truststore.
Password. Specify the password for the specified keystore and truststore files.
Confirm Password.

Siebel Application Interface Authentication:

Keystore Name.
Truststore Name.
Password.
Confirm Password.

Note: The keystore and truststore files are Java files containing certificates. They are necessary for the application container to use secure two-way communications when connecting with other Siebel CRM modules, as occurs during Siebel Management Console configuration and in normal operation. These files must contain the server certificate chain and an imported CA certificate. Generate your files so that the keystore file references both the private key and the public key, while the truststore file references the public key only. Specify the password that was previously configured to open the certificate files. Use the same password for the keystore and truststore files. Use fully qualified domain names rather than IP addresses. If you do not configure these files correctly, then you will not be able to configure Siebel CRM, as described in General Guidelines for Installing Siebel CRM. See also Siebel Security Guide.

(Windows) If you are installing and configuring Siebel Web Client, then the Siebel Web Client Configuration details screen appears.

(Windows) Specify the Siebel Web Client Configuration details, and click Next.

Client Type. Select either Mobile Web Client or Developer Web Client.
(Mobile Web Client only) Siebel Remote Server Hostname. Specify the name of the Siebel Server on which you are running the Siebel Remote server components. The Siebel Remote server components are required for initializing and synchronizing the local database on the Siebel Mobile Web Client computer.
Select Required Applications. Specify the Siebel applications your Siebel Web Client users require. Click to select one application. Ctrl+click to select additional applications.
Developer Web Client options:
- Database Server. Select the type of database server that you are using for Siebel CRM. Choose one of the following:
  - Oracle Database Server
  - IBM DB2 UDB for Windows and UNIX
  - Microsoft SQL Server
  - IBM DB2 UDB for z/OS
- Database details. Specify database information according to your database type. Enter the data that you previously specified in the worksheet in Siebel Deployment Planning Worksheet.
  - For Oracle Database, specify the Database Alias and Table Owner.
  - For IBM DB2, specify the Database Alias, Table Owner, and DB2 Instance Home Directory.
  - For Microsoft SQL Server, specify the Database Server Host Name and Database Instance Name.
  - For IBM DB2 for z/OS, specify the Database Alias, Schema Qualifier (Table Owner), Current SQLID, and DB2 Instance Home Directory.
- Directory Path for Siebel File System. Specify the directory path for a network-based Siebel File System.
  
  Note: For the Siebel File System path, you can use a UNC share name (for example, \\SRV1\siebfile) or a mapped drive (for example, K:\siebelFS). For more information, see File and Directory Naming Conventions. See also Creating the Siebel File System.
- Gateway Server Address. Specify the network name or the IP address of the computer on which the Siebel Gateway is installed. To enter a specific port number, append the Gateway Server Address string with a colon and the desired port number.
- Enterprise Server Name. Specify the name of the Siebel Enterprise to which this Siebel Developer Web Client will connect for administration purposes. The Enterprise Server name is the name of the Siebel Enterprise under which the Siebel Servers that support the server database operate.
- Request Server Name. Specify the name of the Siebel Server on which the Server Request Broker component is operating. This component is used for dynamic assignment and other interactive operations.
- Search Server Name. Specify the host name of the server computer where the search server operates.
- Search Server Port Number. Specify the port number of the search server. The default value is 2048.
- HTTP Connection Port. Incoming connections on the HTTP port are redirected to the secure HTTPS port. (Default: 9001)
- Shutdown Port. Used for management purposes, for local use only. (Default: 9005)

(Windows) If you are installing and configuring Siebel Tools, then the Siebel Tools Configuration details screen appears.

(Windows) Specify the Siebel Tools Configuration details, and click Next.

Database Server. Select the type of database server that you are using for Siebel CRM. Choose one of the following:
- Oracle Database Server
- IBM DB2 UDB for Windows and UNIX
- Microsoft SQL Server
- IBM DB2 UDB for z/OS
Note: Depending on your selection, the Siebel CRM installer validates that the correct database connectivity software has been installed. If it has not been installed, then you must exit the installer, install the required software, and then restart the installer.
Database details. Enter the following information for your database server. Enter the same data that you put in your Siebel Deployment Planning Worksheet.
- For Oracle Database, specify the Database Alias and Table Owner.
- For IBM DB2, specify the Database Alias and Table Owner.
- For Microsoft SQL Server, specify the Database Server Host Name and Database Instance Name.
- For IBM DB2 for z/OS, specify the Database Alias (as defined in DB2 Connect) and Table Owner or Schema Qualifier.
Directory path for Siebel File System. Specify the directory path for a network-based Siebel File System by typing it directly or by clicking Browse.

Note: You can use a UNC share name (for example, \\SRV1\siebfile) or a mapped drive (for example, K:\siebelFS). For more information, see File and Directory Naming Conventions and Creating the Siebel File System.

The Summary screen appears.

In the Summary screen, review the information presented.

This screen displays the location where Siebel CRM will be installed. Before you proceed, confirm that you have met all of the installation requirements, such as for disk space. Then do one of the following:

To begin installing Siebel CRM, click Install. You can also click Install after saving a response file.
To save a response file to use for a silent installation later, click Save Response File, and then save the file from the dialog box that appears. If you are not also installing at this time, then click Cancel after you save the response file. For information about performing silent installations, see Installing Siebel CRM Using Silent Mode.

The Installation Progress screen appears. Siebel CRM is installed into the directory that you specified in Step 8.

When the Next button becomes available, the installation is complete. Click Next.

The Finish Installation screen appears. This screen indicates whether the installation was successful and shows the location of the installer log file. You can access this file to review the installation results.

To close the installer, click Close.

This new installation of Siebel CRM is now finished.

If you installed New Database Repository for a new installation of Siebel Enterprise Components, then the shortcut for the Database Configuration Wizard is created in the program folder, using a generated name.

As required for your installation, you must configure your deployment using the Siebel Management Console, as described in Configuring Siebel CRM Server Modules. (If you did not complete Enterprise Container Configuration or Application Interface Container Configuration, then you must run the Siebel CRM installer again and do so before you run Siebel Management Console.)

To install Siebel CRM modules in a new installation