Siebel Installation Guide for UNIX > Installing Siebel Enterprise Server Components and the Siebel Web Server Extension > Installing Siebel Enterprise Server >

Installing Siebel Enterprise Server as a Migration Installation

Use the following procedure to install Siebel Enterprise Server as a migration installation for Siebel CRM version 8.1.1.11 or version 8.2.2.4 (for a patch installation case).

NOTE:  Use this procedure only when an earlier version of Siebel Enterprise Server is already installed. Otherwise, you must follow the steps in Installing Siebel Enterprise Server as a New Installation instead.

During a migration installation, the original Siebel Enterprise Server installation directory is renamed from OriginalName to OriginalName_pre8.1.1.11.0 or OriginalName_pre8.2.2.4.0. For example, if the original directory name was ses, then this directory is renamed to ses_pre8.1.1.11.0 or ses_pre8.2.2.4.0. The new Siebel Enterprise Server installation directory is named OriginalName, such as ses. Retain the original directory, in case you choose to perform a rollback uninstallation later. For more information, see Rolling Back the Siebel Enterprise Server.

This topic is part of Installing Siebel Enterprise Server.

This task is a step in Roadmap for Installing Siebel Business Applications in a Patch Installation Case (Existing Installation).

To install Siebel Enterprise Server as a migration installation

1. Review About Installing Siebel Business Applications.

   For example, if you are installing a Siebel Server that will communicate with an existing installation of Siebel Gateway Name Server on another computer, then make sure that the Siebel Gateway Name Server is running on that computer.

2. (Optional) Shut down the Siebel CRM modules to be updated on this computer.

   For example, stop the services for the Siebel Gateway Name Server, Siebel Server, Siebel Management Agent, and Oracle Configuration Manager. Also shut down any running instances of the Siebel Server Manager (srvrmgr). If you do not shut down the Siebel Gateway Name Server, Siebel Server, and Oracle Configuration Manager modules, then the installer shuts them down.

3. (AIX only) Verify that the login ID performing the installation has permission to run slibclean by asking the administrator to change the permission as follows:

   chmod 6555 /usr/sbin/slibclean

4. (AIX only) Execute the following command:

   /usr/sbin/slibclean

5. Log on to the server, using the Siebel service owner account that you recorded in the copy that you made earlier of the worksheet in Siebel Deployment Planning Worksheet.
6. Open a new shell, and navigate to the Siebel image location for the current release. Then navigate to the directory where the installer is located. For example, for Oracle Solaris, navigate to Siebel_Image/Solaris/Server/Siebel_Enterprise_Server/Disk1/install.

   In this path, Siebel_Image is the directory for your version-specific Siebel network image, such as /Siebel_Install_Image/8.1.1.11 or /Siebel_Install_Image/8.2.2.4.

7. Verify the permissions to the directory into which you will install the Siebel Enterprise Server. You must have write and execute permission.
8. To start the Siebel Enterprise Server installer, enter the following command:

   ./runInstaller -jreLoc jre_location -invPtrLoc inventory_location

   where:

   • jre_location is the full path of the installed Java Runtime Environment (JRE) software. On AIX, you must use the -jreLoc option. It is not required on other operating systems. For more information about the JRE requirements for AIX, see Requirements Specific to UNIX or Linux Operating Systems.
   • 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.

     Optionally, for an unattended installation, you can append the flags described in Installing Siebel Enterprise Server Components and Siebel Web Server Extension in Unattended Mode.

     The Siebel Enterprise Server installer displays the Welcome screen.

9. Click Next.

   The Oracle Configuration Manager screen appears, which prompts for email contact information.

10. Enter your My Oracle Support credentials and click Next.

    Oracle Configuration Manager software is installed on the target computer. For more information, see About Oracle Configuration Manager.

    The Select Installation Task screen appears. The New Installation task is selected by default.

11. To perform a migration installation of the Siebel Enterprise Server software where an existing prior installation of Siebel CRM version 8.1.1.x or version 8.2.2.x is present, choose Migration Installation, and click Next.

    The Installation Migration Details screen appears.

12. Confirm or select the name and location of your existing installation, and then click Next. Note the following:
    • Confirm the existing installation name, or select it from the drop-down list.
    • Confirm the existing installation location, or select it from the drop-down list.

      For more information about Oracle home and installation path requirements, see File and Directory Naming Conventions.

      The Summary screen appears. This screen displays the location into which it will install the Siebel Enterprise Server.

13. Review the information in the Summary screen. 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 save a response file to use for an unattended installation later, click Save Response File. After the response file is saved, if you are not also installing, then Click Cancel. For information about performing unattended installations, see Installing Siebel Enterprise Server Components and Siebel Web Server Extension in Unattended Mode.
    • To begin installing the Siebel Enterprise Server software, click Install. You can also click Install after saving a response file.

      The Installation Progress screen appears. The Siebel Enterprise Server software is installed into the directory that you specified in Step 12.

14. 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 main installer log file. You can access this file to review the installation results. This screen also shows the new location of the original installation, which the installer moved before it performed the new installation.

15. Review the report that is generated about any conflicts between your customized files and the files that are delivered by the Siebel Enterprise Server installer. As needed, copy any of your customized files from the original installation to the new migrated installation.

    Conflicts are identified in the file overwrittenfiles_timestamp.log, which is created in the ORACLE_HOME/cfgtoollogs/oui directory (in the new Siebel Enterprise Server installation).

16. To close the installer, click Close.

    The Siebel Enterprise Server installation is now finished.

    After the migration process is complete, then the installer starts the services for the Siebel Gateway Name Server, Siebel Server, and Oracle Configuration Manager. Note that the software that runs is part of the new installation you are migrating to, not part of the original installation.

17. Start the service for the Siebel Management Agent, if it is needed.
18. After installing the Siebel Enterprise Server software:
    • Verify the Siebel Enterprise Server installation, as described in Verifying Installation for the Siebel Enterprise Server.
    • Install the latest Siebel Patchset release. Then verify the installation again.
    • Perform any additional postinstallation steps, as described in Additional Postinstallation and Configuration Tasks.