Migration Issues and Solutions for Siebel CRM 17.0 and Later

Many product and support changes for Siebel CRM 17.0 and later releases make it necessary for you to perform certain migration-related tasks. Issues and possible solutions are provided for some items. Review all items before proceeding. This list is not comprehensive. Many of the tasks are interrelated and are not necessarily presented in the order in which you would perform them. Various dependencies apply that might not be fully explained. Some of these issues apply only to migrations from releases prior to Siebel CRM 16.0.

This topic is part of Additional Tasks for Migration Installations.

• Synchronize local databases before migrating or doing other premigration tasks. Siebel Mobile Web Client users might need to synchronize their local database changes with the server, through Siebel Remote, as described in Siebel Remote and Replication Manager Administration Guide. Or, Siebel Tools developer users might need to check in any changes made to objects in the existing local database, as described in Using Siebel Tools for earlier releases of Siebel Tools.

• Remove the Siebel Web Server Extension (SWSE) configuration before migrating, and then configure Siebel Application Interface after migrating. In Siebel CRM 16.0, the virtual directories, which formerly mapped to public\lang_code (such as ENU), were mapped directly to public. Virtual directories no longer apply and are replaced by application configurations. In the current release, these configurations map to applicationcontainer_external\siebelwebroot in the Siebel Application Interface installation. When you install the Siebel Application Interface as a migration installation, the existing virtual directories on the Web server that were configured for SWSE in a prior release are not migrated. After all of the migration installations are complete, you must configure the Siebel Application Interface to create the application configurations. For more information, see About Installation Tasks for Siebel CRM and About Configuring Siebel CRM.

  Caution: You must remove the configuration for the SWSE before you install Siebel CRM 17.0 as a migration installation, as described in Process of Removing Configuration Data.

• When data encryption is enabled, you must back up the original key file (keyfile.bin) before performing a migration installation for Siebel Enterprise Server, and then copy it back after migrating. For more information, see General Requirements for Installing and Configuring Siebel Enterprise Components.

  Caution: If data migration is enabled, then the migration installation overwrites your existing key file. If you have not backed up your existing key file and copied it back after the migration, then the encrypted columns will be inaccessible after the migration.

• Preserve premigration installation. You might want to preserve your premigration installations, in case you need to restore your prior version after having done the migration installations and made the manual migration changes described here. It is recommended that you manage your migration tasks to make sure that you have not permanently deleted, moved, or renamed files or directories in these installations. Also keep track of changed requirements, so that you can restore the overall environment for your prior release. For more information, see Uninstalling Siebel CRM.

• Move files and directories or delete unnecessary files. Depending on the release you are migrating from and on your requirements, you might need to copy some files or directories from your existing installation into your new migrated installation, or you might need to delete some unnecessary files and directories from your new migrated installation. For example:

  • The webtempl directory on Siebel Server. As of Siebel CRM 17.0, the SIEBSRVR_ROOT\webtempl directory is not part of the Siebel Server installation and is not migrated. The Siebel Web templates are now located in the Siebel database. Custom Siebel Web templates for Siebel Open UI migrate into the database when you run Incremental Repository Merge, as described in Siebel Database Upgrade Guide.

    In order for this migration to succeed, you must copy all of the applicable custom Siebel Web template files into a directory. Then, when you run Incremental Repository Merge and the Database Configuration Wizard prompts for the Web Templates Directory, specify this new directory location.

    • If you are migrating from Siebel CRM 16.x, then the applicable Siebel Web template files to copy are those located in the SIEBSRVR_ROOT\webtempl\custom subdirectory in your prior installation.

    • If you are migrating from a release prior to Siebel CRM 16.0, then the applicable Siebel Web template files to copy are those located in the SIEBSRVR_ROOT\webtempl\ouiwebtempl\custom subdirectory in your prior installation.

      For Siebel Web Client and Siebel Tools installations, the webtempl directory has also been removed and Siebel Web templates are now provided in the Siebel database. A newly extracted local database for Siebel Mobile Web Client also includes your custom Siebel Web templates.

  • The webmaster directory on Siebel Server. As of Siebel CRM 16.0, the SIEBSRVR_ROOT\webmaster directory on the Siebel Server has been removed. If you are migrating from a release prior to Siebel CRM 16.0, then you can delete this directory from your migrated Siebel Server installation.

  • The public directory on Siebel Web Server Extension. As of Siebel CRM 17.0, the SWSE_ROOT\public directory is not part of the Siebel Application Interface installation. In the current release, the equivalent location is SIEBEL_AI_ROOT\applicationcontainer_external\siebelwebroot. Files and directories are not automatically migrated for Siebel Application Interface. If you require any of the files from the public directory in your prior installation of SWSE, then you can copy them manually after completing installation and configuration tasks.

    Before you copy files, you must take into account the following changes that occurred in the structure of the public directory in Siebel CRM 16.0:

    • public\lang_code\build_number, where lang_code is an installed Siebel language (such as ENU) and build_number is one of the build numbers for the installed Siebel software. The applet subdirectory was removed. The scripts subdirectory moved under public. And the build_number directory was removed.

    • public\lang_code\files. This directory moved under public.

    • public\lang_code\fonts. This directory moved under public.

    • public\lang_code\htmltemplates. This directory moved under public.

    • public\lang_code\images. This directory moved under public.

    • public\lang_code\webeditor. This directory was removed.

    • public\lang_code\default.htm. This file moved under public.

    • public\lang_code\blank.htm. This file moved under public.

    • public\lang_code\wait.htm. This file was removed.

    • public\lang_code\*.pcd. These files were removed.

    • public\lang_code\*.manifest. The variable string %BuildNumber% was removed from the .tmanifest files, from which the .manifest files are generated.

    Note: The Siebel application virtual directories, which formerly mapped to the public\lang_code directory on SWSE, are obsolete as of Siebel CRM 17.0. In the current release, the application configurations for Siebel Application Interface map to SIEBEL_AI_ROOT\applicationcontainer_external\siebelwebroot.

• Move files and directories: Files and directories on Siebel Web Client and Siebel Tools have changed relative to equivalent locations for releases prior to Siebel CRM 16.0. Similar changes apply for migration installations of Siebel Web Client and Siebel Tools, as described above for migration installations of Siebel Application Interface. However, the files are copied into the new migration installations of Siebel Tools. Note also that Siebel Web Client still uses the public directory, as in Siebel CRM 16.0.

  Issue (for migrations from release prior to Siebel CRM 16.0). After a migration installation of Siebel Web Client or Siebel Tools (from a release prior to Siebel CRM 16.0), duplicate directories will exist, because some of the directories will be in new locations relative to those seen for the files and directories that migrated from the prior release. Your custom files will be in the wrong locations and cannot be used until you have moved them to the new locations.

  Solution. Reorganize the files and directories in SIEBEL_CLIENT_ROOT\public and SIEBEL_TOOLS_ROOT\public on the migrated installations to incorporate the migrated custom files that you require and to conform to the changes described earlier in this topic for Siebel Application Interface. Finally, remove all extraneous files and directories in SIEBEL_CLIENT_ROOT\public and SIEBEL_TOOLS_ROOT\public.

• Upgrade the database client. In a migration installation case, after migrating, you must make sure that a supported version of the database client software is installed for use with the current release of Siebel CRM, as noted in the Certifications tab on My Oracle Support. You might also need to update the database client installation path in the defined environment variables. You can install Oracle Database Client with Siebel Enterprise Components. For more information, see About Configuring Siebel CRM.

  Installing Siebel Web Client also installs Oracle Database SE2 and Oracle Database Client, as noted in Installing and Using Oracle Database SE2 for the Local Database and other topics.

• Edit configuration files for Siebel Web Client. After doing a migration installation for Siebel Web Client from Siebel CRM 16.x or earlier, you might need to edit all applicable migrated configuration files, such as uagent.cfg for Siebel Call Center. For example:

  For a migration from Siebel CRM 16.x or earlier, in the [Siebel] section of each applicable configuration file, the existing WebClientSiteDir parameter value will include a language element, which is no longer needed. For example, for a value like C:\Siebel\Client\public\enu, update the parameter value to C:\Siebel\Client\public.

• Remove obsolete parameters. Several parameters for server components or in configuration files are obsolete as of Siebel CRM 17.0. To reduce confusion after migration installations, you might choose to delete some of the parameters that no longer apply, such as HighInteractivity and EnableOpenUI (which are obsolete as of Siebel CRM 16.0). For more information about obsolete parameters, see Siebel System Administration Guide.

• Reset passwords on the Siebel Gateway and on the Siebel Server. After doing a migration installation from Siebel CRM 16.x or earlier, you must reset any passwords on the Siebel Gateway that were previously encrypted using encryption other than AES. Such passwords are now encrypted using AES. For more information about reencrypting these passwords, see Siebel Security Guide. Furthermore, the Siebel Server system service and server components do not work after a migration installation until you have updated them to use AES password encryption. Make these changes in coordination, as described in Updating the Siebel Server System Service and Server Components to Use AES Password Encryption.