{"id":73117,"date":"2016-04-15T10:35:11","date_gmt":"2016-04-15T10:35:11","guid":{"rendered":"https:\/\/www.red-gate.com\/simple-talk\/uncategorized\/siebel-crm-part-9-upgrading-the-application-servers-for-8-1-1-x-deployments\/"},"modified":"2021-07-14T13:07:08","modified_gmt":"2021-07-14T13:07:08","slug":"siebel-crm-part-9-upgrading-the-application-servers-for-8-1-1-x-deployments","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/databases\/oracle-databases\/siebel-crm-part-9-upgrading-the-application-servers-for-8-1-1-x-deployments\/","title":{"rendered":"Siebel CRM Part 9: Upgrading the Application Servers for 8.1.1.X Deployments"},"content":{"rendered":"

In the first article in the series<\/a> we talked about having multiple paths for a Siebel upgrade. In a nutshell:<\/p>\n

    \n
  1. For Siebel versions 8.0.X and early 8.1 customers the best possible route is to re-implement Siebel rather than upgrade. For this purpose we had suggested that a sandbox environment be set up so that the existing business processes can be mapped to vanilla Siebel business processes and the deployment could be completed with minimal configuration \/customizations.<\/li>\n
  2. For Siebel 8.1.1.X customers an in-place upgrade was more suitable than a re-implementation as it was much quicker.<\/li>\n<\/ol>\n

    The first eight articles in this series were dedicated to building up a sandbox environment. The same steps can be used to build a new Siebel instance as well. Starting with this article, we will start detailing the upgrade process for in-place upgrades. Please bear in mind that this article is suitable only for clients who are already on a supported platform e.g. Windows 2008 R2 or higher. <\/strong>The Siebel certifications available on the Oracle support website must be checked prior to upgrading the servers. The upgrade process is split into four distinct steps:<\/p>\n

      \n
    1. Upgrade the Application Servers, which means upgrading the Siebel Gateway Name Server, Siebel Application Servers, Siebel Database configuration utilities and the Siebel Web Server extensions.<\/li>\n
    2. Upgrade the Siebel Database.<\/li>\n
    3. Run the incremental repository merge.<\/li>\n
    4. Upgrade the production database.<\/li>\n<\/ol>\n

      This article discusses the first part in the upgrade process which is upgrading the application servers.<\/p>\n

      <\/a>Pre-Upgrade Tasks<\/h2>\n

      Before starting the Siebel upgrade the following activities must be completed:<\/p>\n

        \n
      1. Log on to all the servers running the Siebel Application.<\/li>\n
      2. Copy the installation files across to all the servers.<\/li>\n
      3. Ensure that the Logarchive folders (<Siebel_Root>\\Siebsrvr\\LOGARCHIVE\\*<\/code>) are deleted. The reason this needs to be done is because post update the servers copy the whole folder as a backup.<\/strong><\/li>\n
      4. Backup the configuration files (*.cfg) from the <Siebel_Root>\\Siebsrvr\\Bin\\<LANG><\/code> folders. This is required since the upgrade process will overwrite any existing configuration files and any custom entries in the same will be lost.<\/a><\/li>\n<\/ol>\n

        Upgrade Siebel Application and Web Servers<\/h2>\n

        Before starting the upgrade, we need to make sure that the entire enterprise is shut down and all the services are disabled.<\/p>\n

          \n
        1. Shut down all Siebel Server services.<\/li>\n
        2. Disable the Siebel Services (this is done because the installer restarts these services after the upgrade, which we do not want to happen).<\/li>\n
        3. Shut down the Siebel Gateway Server Service.<\/li>\n
        4. Disable the Gateway Server Service.<\/li>\n
        5. Shutdown the World Wide Web Publishing service and the IIS Admin services on the webservers.<\/li>\n
        6. These services must not<\/em> be started until all of the activities are completed<\/strong>.<\/li>\n<\/ol>\n

          Siebel Application Servers – Gateway Name Server, Siebel Application Servers and the Database Configuration Utilities<\/h2>\n

          Navigate to the installation software folders. In our sandbox environment example, this would be: “D:\\Software\\Siebel_Install_Image\\15.0.0.0\\Windows\\Server\\Siebel_Enterprise_Server\\Disk1\\install<\/code>“<\/p>\n

          \"\"<\/p>\n

          Execute setup.bat.<\/p>\n

          \"\"<\/p>\n

          Click Next <\/strong>on the Welcome Screen.<\/p>\n

          \"\"<\/p>\n

          Enter the details for Oracle support if required. This step can be ignored if you like. Click on Next <\/strong>once done.<\/p>\n

          \"\"<\/p>\n

          Since we are performing an in-place upgrade, choose “Migrate Installation” and click on Next<\/strong>.<\/p>\n

          \"\"<\/p>\n

          The installer should automatically detect the previous installation. Please ensure that the home location is correctly chosen. The installer uses the Oracle Home to identify what components are installed on the server. Click Next<\/strong>.<\/p>\n

          Please note that in certain cases it is possible that the home location may not be detected. In these cases, we need to cancel the installation and apply fixes. The fixes are detailed towards the end of this article<\/a>.<\/strong><\/p>\n

          \"\"<\/p>\n

          Accept the defaults and Click Next<\/strong>.<\/p>\n

          \"\"<\/p>\n

          Ensure that the summary is correct and click on Install.<\/strong><\/p>\n

          \"\"<\/p>\n

          Once the installation is complete, click Next<\/strong>.<\/p>\n

          \"\"<\/p>\n

          Click Close<\/strong>.<\/p>\n

          This completes the upgrade of the Siebel Application servers. Please bear in mind that the same steps must be repeated for every Windows server which has Siebel installed.<\/strong><\/p>\n

          Upgrading the Siebel Web Servers<\/h2>\n

          Navigate to the installation software folders. In our sandbox environment example it would be: “D:\\Software\\Siebel_Install_Image\\15.0.0.0\\Windows\\Server\\Siebel_Web_Server_Extension\\Disk1\\install<\/code>“.<\/p>\n

          \"\"<\/p>\n

          Execute setup.bat<\/strong>.<\/p>\n

          \"\"<\/p>\n

          Click on Next.<\/strong><\/p>\n

          \"\"<\/p>\n

          As in the last installation, fill up the details if required and click on Next.<\/strong><\/p>\n

          \"\"<\/p>\n

          Choose Migrate Installation and click Next<\/strong>.<\/p>\n

          \"\"<\/p>\n

          The installer should automatically detect the previous installation. Please ensure that the home location is correct, as the installer uses the Oracle Home to identify what components are installed on the server. Click Next<\/strong>.<\/p>\n

          Please note that in certain cases it is possible that the home location may not be detected. In these cases, we need to cancel the installation and apply fixes. The fixes are detailed towards the end of this article<\/a>.<\/strong><\/p>\n

          \"\"<\/p>\n

          The SWSE cryptographic seed key is mandatory. Type a value in the field and store it. If there are multiple web servers deployed ensure that the same key is used in all the servers. <\/strong>Click on next<\/strong> once done.<\/p>\n

          \"\"<\/p>\n

          Accept the defaults and click Next<\/strong>.<\/p>\n

          \"\"<\/p>\n

          Review the information and click Install<\/strong>.<\/p>\n

          \"\"<\/p>\n

          \"\"<\/p>\n

          Click Next<\/strong> once the migration is complete.<\/p>\n

          \"\"<\/p>\n

          Click Close<\/strong>.<\/p>\n

          This completes the upgrade of the Siebel Web servers. Please note that if there are multiple webservers deployed, these steps must be performed on every web server.<\/strong><\/p>\n

          Troubleshooting When the Installation Folder is not Detected<\/h2>\n

          This issue typically happens when the installer cannot find anything in the registry pointing to the previous installation. The primary reason for this is that the installer was changed in the later versions of Siebel 8.1.1.X, which started using the Oracle home values. To fix this the following steps need to be performed.<\/p>\n

            \n
          1. Run Regedit on the server.<\/li>\n
          2. Locate HKEY_LOCAL_MACHINE\\Software\\Wow6432Node\\ORACLE<\/code> as shown in the image below:<\/li>\n<\/ol>\n

            \"\"<\/p>\n

              \n
            1. Make sure there is a key called “KEY_SBA_81” or “KEY_OH******”\u00a0<\/li>\n
            2. Within the key ensure that the following values are populated as shown in the image below:\n
                \n
              1. ORACLE_GROUP_NAME<\/li>\n
              2. ORACLE_HOME<\/li>\n
              3. ORACLE_HOME_NAME.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

                \"\"<\/p>\n

                  \n
                1. In the case that these values do not exist, please create them to match the image above. Example:\n
                    \n
                  1. KEY_OH0000000\u00a0<\/li>\n
                  2. ORACLE_GROUP_NAME Oracle – OH0000000\u00a0<\/li>\n
                  3. ORACLE_HOME: This is the path to the installation. For example, the Siebel Application servers in previous installations were typically installed in D:\\SBA81<\/code> while the web servers were installed in D:\\SBA81\\Sweapp<\/code>.<\/li>\n
                  4. ORACLE_HOME_NAME: OH0000000\u00a0<\/li>\n<\/ol>\n<\/li>\n
                  5. Once this is created reboot the server. The installation should now be detected.<\/li>\n<\/ol>\n

                    This concludes this article. The next article in the series details the database upgrade process for non-production instances.<\/p>\n","protected":false},"excerpt":{"rendered":"

                    In the first article in the series we talked about having multiple paths for a Siebel upgrade. In a nutshell: For Siebel versions 8.0.X and early 8.1 customers the best possible route is to re-implement Siebel rather than upgrade. For this purpose we had suggested that a sandbox environment be set up so that the existing business processes can b…<\/p>\n","protected":false},"author":105470,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[143533],"tags":[48498],"coauthors":[],"class_list":["post-73117","post","type-post","status-publish","format-standard","hentry","category-oracle-databases","tag-siebel-crm"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/73117","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/users\/105470"}],"replies":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/comments?post=73117"}],"version-history":[{"count":1,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/73117\/revisions"}],"predecessor-version":[{"id":91614,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/73117\/revisions\/91614"}],"wp:attachment":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/media?parent=73117"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/categories?post=73117"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/tags?post=73117"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/coauthors?post=73117"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}