Bookshelf Home | Contents | Index | PDF     

Siebel Installation Guide for UNIX > Installing Siebel CRM Server Modules > Installing Siebel CRM >

Installing Siebel CRM in a Migration Installation

Use the following procedure to install Siebel CRM server modules in a migration installation.

NOTE:  Use this procedure only when server modules for a prior release of Siebel CRM are already installed. Otherwise, you must follow the steps in Installing Siebel CRM in a New Installation instead.

During a migration installation, the original Siebel CRM installation directory is renamed from OriginalName to OriginalName_pre17.0. For example, if the original installation directory name was ses or sweapp, then this directory is renamed to ses_pre17.0 or sweapp_pre17.0. The new installation directory is named OriginalName, such as ses or sweapp. Retain the original installation directory, in case you choose to perform a rollback uninstallation later. For more information, see Rolling Back the Siebel CRM Server Modules.

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

NOTE:  If you need to add any modules that were not present in your original installation, including new modules, then you must install them as a new installation, as described in Installing Siebel CRM in a New Installation.

This topic is part of Installing Siebel CRM.

This task is a step in Roadmap for Installing Siebel CRM in a Migration Installation Case (Existing 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. Otherwise, the migrations will not complete successfully.

To install Siebel CRM in a migration installation

  1. Review Before You Install Siebel CRM and About Installation Tasks for Siebel CRM and observe the requirements and recommendations.
  2. 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 a Siebel Server 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.

  3. (Optional) Shut down 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.

    NOTE:  Siebel Management Agent and Oracle Configuration Manager are not installed or supported in the current Siebel CRM release.

  4. For a migration installation of Siebel Application Interface, stop the Web server for the existing installation of SWSE 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)
  5. (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

  6. (AIX only) Execute the following command:

    /usr/sbin/slibclean

  7. 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.
  8. Open a new shell, and navigate to the Siebel image location for Siebel CRM 17.0. 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/17.0.0.0.

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

    NOTE:  You must perform the migration installation of Siebel Application Interface before you migrate other modules, such as Siebel Gateway or Siebel Server.

  10. (AIX only, with IBM DB2 for z/OS) Create a directory DB2_JAR, which is parallel to the directory in which you are installing Siebel CRM (the existing installation directory). Then copy the file db2jcc_license_cisuz.jar from the DB2 or DB2 client installation into this directory. For more information, see

    http://www-01.ibm.com/support/docview.wss?uid=swg21191319

  11. To start the Siebel Enterprise Server installer (to install any of the modules listed at the start of Installing Siebel CRM), enter the following command:

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

    Optionally, for an unattended installation, you can append the flags described in Installing Siebel CRM in Unattended Mode.

    The Select Installation Task screen appears.

  12. To perform a migration installation of Siebel CRM where an existing prior installation is present, choose Migration Installation, and click Next.

    The Installation Migration Details screen appears.

  13. Confirm or select the name and location of your existing installation, and then click Next. Do 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 Application Container Port Configuration screen appears. This screen applies to all installable modules except EAI Connector and Database Configuration Utilities.

  14. Specify port numbers, and click Next. Specify the following:
    • HTTPS Redirect Port (default: 443, or example: 9011). Used for secure HTTPS connections to the application container, which can include connections redirected from the HTTP port.
    • HTTP Connection Port (default: 8080, or example: 9012). Incoming connections on the HTTP port are redirected to the secure HTTPS port.
    • Shutdown Port (default: 8005, or example: 9013). Used for management purposes by Siebel CRM, for local use only.

      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 Client Authentication screen appears. This screen appears if you are installing Siebel Gateway, Siebel Server, or Siebel Application Interface.

  15. Specify information that supports secure communications for the installed software. Specify the following:
    • 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

      NOTE:  The keystore and truststore files are Java files containing certificates. These files 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. If you do not configure these files correctly, then you will not be able to configure Siebel CRM, as described in Configuring Siebel CRM Server Modules. See also Siebel Security Guide.

      If you are migrating an installation of Siebel Gateway, then the Gateway Port Configuration screen appears.

  16. Specify the TLS port number for the existing installation of Siebel Gateway Name Server (default: 2320, or example: 9014).

    CAUTION:  The TLS port number for a migration installation must be the port number on which the Siebel Gateway Name Server was configured in the prior installation. Failing to enter the right port will result in failure of the migration installation.

    The Summary screen appears.

  17. In the Summary screen, review the information presented.

    This screen displays the location where the Siebel CRM software 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 an unattended 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 unattended installations, see Installing Siebel CRM in Unattended Mode.

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

  18. When the Next button becomes available, this 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. This screen also shows the new location of the original installation, which the installer moved before it performed the new installation.

  19. 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 applicable 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 migrated installation).

  20. To close the installer, click Close.

    This migration installation of Siebel CRM is now finished.

    After the migration process is complete, the installer starts applicable services, such as for the Siebel Gateway and Siebel Server. Note that the software that runs is part of the new installation you are migrating to, not part of the original installation.

  21. After installing Siebel CRM:
  22. Repeat this procedure, modifying selections as appropriate, on each computer or operating system instance with a Siebel CRM installation to be migrated.
      
Siebel Installation Guide for UNIX Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices.