Installing Siebel CRM in a Migration Installation

Use the following procedure to install Siebel CRM in a migration installation. This task is part of Installing Siebel CRM using the User Interface.

Note: Use this procedure only where a prior release of Siebel CRM 16.x or earlier is already installed. For a new installation, see Installing Siebel CRM in a New Installation. Where a prior release of Siebel CRM 17.x or later is already installed, you perform an update installation instead, as described in Installing Siebel CRM in an Update Installation.

This task is a step in:

For more information about migration installations, see Installation Tasks for Siebel CRM.

Note: If you need to add any modules that were not present in your original installation, including, for example, new modules or additional instances of Siebel Server or Siebel Application Interface, then you must install them as a new installation, as described in Installing Siebel CRM in a New Installation.

Caution: You must perform the migration installation for Siebel Application Interface before you perform the migration installations for any other Siebel CRM server modules. When you do the migration installations for other Siebel Enterprise Server modules, the installer prompts you to provide the host name and installation location for the migrated installation of Siebel Application Interface. Without this information, the migration installations of Siebel Gateway, Siebel Server, or other modules cannot complete successfully.

To install Siebel CRM in a migration installation

Review Before You Install Siebel CRM and Installation Tasks for Siebel CRM and observe the requirements and recommendations.
Perform any premigration tasks that might be necessary, as noted in Additional Tasks for Migration Installations.

Caution: For example, you must remove the existing configuration for the SWSE before you install Siebel Application Interface as a migration installation. If you are using data encryption, then you must back up the original key file.

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.
(Windows) For a migration installation of Siebel Web Client from a release prior to Siebel CRM 16.0, exit Siebel QuickStart for Mobile Web Client.

Note: Siebel QuickStart is no longer supported as of Siebel CRM 16.0. For a Siebel Mobile Web Client using the Siebel QuickStart feature, you must exit the QuickStart agent if it is running before you perform the migration installation. To do this, right-click the QuickStart icon in the system tray, and then choose Exit.
(Optional) Shut down all of the open programs associated with the Siebel CRM modules to be updated on this computer.

For example, stop any services (for the existing installed instance of a prior version) for the Siebel Gateway Name Server, Siebel Server, Siebel Management Agent, or Oracle Configuration Manager. Also shut down any running instances of the Siebel Server Manager (srvrmgr). If you do not shut down these services, then the installer shuts them down. (Siebel Management Agent and Oracle Configuration Manager are not installed or supported in the current Siebel CRM release.)
(Windows) For a migration installation of Siebel Application Interface for the existing installation of SWSE, stop the Microsoft IIS services by doing the following:
- Stop the IIS Administration service.
- Stop the World Wide Web Publishing service.
(UNIX) For a migration installation of Siebel Application Interface for the existing installation of SWSE, stop the Web server by running one of the following commands:
- ompmnctl stopall – for Oracle HTTP Server (on supported Linux operating systems)
- stopapa – for other Apache-based Web servers (on supported operating systems)
- stop – for Oracle iPlanet Web Server (on Oracle Solaris)
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.
  
  For Siebel Web Client, log onto the client computer as a user with administrative privileges.
- (UNIX) 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.
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\22.7.
- (UNIX) 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/22.7.
(Windows) Before you run the Siebel CRM installer to perform the migration installation of a Siebel CRM module, 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.
- (LINUX) 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.
Select the location of your existing installation from the dropdown list, and click Next.

The Application Container Port Configuration 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.

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.
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.

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.

The screens in Step 15 through Step 18 contain settings that are required in order to migrate your existing configurations and allow you to use Siebel Management Console for any additional configuration tasks.

The Security Profile Details screen appears.
Specify the Security Profile details, and click Next. Specify the following settings:
- Database User Account Name.
- Database User Account Password.
- Data Source Name.
- Database Host Name.
- Database Port Number.
- Database Service Name.
The Gateway Registry screen appears.
Specify the Siebel Gateway registry configuration, and click Next. Specify the following settings:
- Security Profile.
- Registry Port.
- Primary Language.
- Registry User Name.
- Registry User Password.
The Application Interface Home screen appears.
Specify the Application Interface Home Location, and click Next.

The Application Interface Details screen appears.
Specify the Application Interface details, and click Next. Specify the following settings:
- Application Interface Hostname.
- Application Interface HTTPS Port.
- Application Interface Username.
- Application Interface Password.
- Application Interface Truststore Name.
- Application Interface Truststore Password.
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 11.
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 migration installation of Siebel CRM is now finished.

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.