Bookshelf Home | Contents | Index | PDF     

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

Additional Tasks for Migration Installations

Certain product changes have been made in Siebel Innovation Pack 2016 that can affect migration installations for existing customers. All customers performing migration installations must review the information in this topic before installing, to make sure that they can successfully migrate all custom files and settings to the current release and to avoid any of the issues described here.

These product changes affect some of the files and directories of installations of Siebel Server, Siebel Web Server Extension (SWSE), Siebel Web Client, and Siebel Tools. Also affected are some of the configuration settings for these modules. Many of the product changes described in this topic were made as part of consolidating support for Siebel Open UI and desupporting high interactivity and standard interactivity.

This topic describes specific product changes, describes how these changes might affect migration installations, and provides steps you can take to avoid any issues and complete the migration successfully. Some of the tasks you perform before installation, but most of them you would perform after installation. Additional migration considerations are also provided.

Migration Issues and Solutions in Siebel Innovation Pack 2016

Many product and support changes for Siebel Innovation Pack 2016 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 explained.

  • 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.
  • Remove the Siebel Web Server Extension (SWSE) configuration before migrating, and then reconfigure SWSE after migrating. In Siebel Innovation Pack 2016, the virtual directories, which formerly mapped to public/lang_code (such as ENU), now map directly to public. However, the existing virtual directories on the Web server that were configured for a prior release are not updated automatically when you migrate the SWSE. In order to correct this problem after the migration installation, you must reconfigure the SWSE. For more information, see About Configuring Siebel Business Applications.

    CAUTION:  You must remove the configuration for the SWSE before you install the current release as a migration installation.

  • 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 Server 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 roll back to your prior version after doing the migration installations and making 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 if you roll back. Additional requirements apply for rollbacks. For more information, see Uninstalling Siebel Business Applications.
  • Move files and directories: The webmaster directory has been removed. On the Siebel Server, the SIEBSRVR_ROOT/webmaster directory has been removed. The files it contained are now located in the SWSE_ROOT/public directory on the SWSE, although several subdirectories have been reorganized. This change involves certain types of files that customers often create or modify, and so it changes where you would access and update such files.

    The Siebel Enterprise Security Token, formerly used to update files from SIEBSRVR_ROOT/webmaster on the Siebel Server to SWSE_ROOT/public on the SWSE, is no longer applicable.

    Issue. Custom files located in SIEBSRVR_ROOT/webmaster directory cannot automatically migrate from the Siebel Server to the SWSE during migration installation. Where custom files exist, the SIEBSRVR_ROOT/webmaster directory and applicable subdirectories automatically migrate instead to the new installation of Siebel Server, where they are not used.

    Solution. Customers can migrate their custom files manually from the Siebel Server to the SWSE using one of two overall approaches.

    • Before doing the migration installations, manually update the SWSE from the Siebel Server, using the Siebel Enterprise Security Token, as documented for prior releases, and perform any other premigration tasks. Reorganize the files and directories in SWSE_ROOT/public on the migrated SWSE to incorporate your custom files and to conform to the changes described in this topic. Then perform the migration installations. Finally, remove all extraneous files and directories in SWSE_ROOT/public on the migrated SWSE and remove SIEBSRVR_ROOT/webmaster on the migrated Siebel Server. Details of reorganizing files and folders are provided after this item.
    • Alternatively, perform any premigration tasks, perform the migration installations, and then manually copy the relevant files and directories from SIEBSRVR_ROOT/webmaster to the migrated SWSE. Details of reorganizing files and folders are provided after this item.
  • Move files and directories: Files and directories have changed in the public directory on SWSE. On the SWSE, in the SWSE_ROOT/public directory, changes affect subdirectories and files as follows. Note that the virtual directories, which formerly mapped to public/lang_code (such as ENU), map directly to public for Siebel Innovation Pack 2016. Because of this change, you must also reconfigure the SWSE, as noted earlier in this topic.
    • 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 has been removed. The scripts subdirectory has moved to SWSE_ROOT/public. And the build_number directory has been removed.
    • lang_code/files. This directory has moved to SWSE_ROOT/public.
    • lang_code/fonts. This directory has moved to SWSE_ROOT/public.
    • lang_code/htmltemplates. This directory has moved to SWSE_ROOT/public.
    • lang_code/images. This directory has moved to SWSE_ROOT/public.
    • lang_code/webeditor. This directory has been removed.
    • lang_code/default.htm. This file has moved to SWSE_ROOT/public.
    • lang_code/blank.htm. This file has moved to SWSE_ROOT/public.
    • lang_code/wait.htm. This file has been removed.
    • lang_code/*.pcd. These files have been removed.
    • lang_code/*.manifest. The variable string %BuildNumber% has been removed from the .tmanifest files, from which the .manifest files are generated.

      Issue. After a migration installation of SWSE, duplicate directories will exist, because some of the directories provided in Siebel Innovation Pack 2016 will be in new locations relative to those seen for the files and directories that migrated from the prior release. As described earlier, if you did not manually update the files from the Siebel Server to SWSE_ROOT/public before doing the migration installation, then the migrated custom files might not represent the latest files. Your custom files will be in the wrong locations and cannot be used until you have moved them to the new locations.

      Solution. Whichever method you use, you must reorganize the files and directories in SWSE_ROOT/public on the migrated SWSE installation to incorporate your custom files and to conform to the changes described in this topic. Finally, remove all extraneous files and directories in SWSE_ROOT/public on the migrated SWSE and remove SIEBSRVR_ROOT/webmaster on the migrated Siebel Server, as noted.

  • Move files and directories: Files and directories have changed in the public directory on Siebel Web Client and Siebel Tools. On Siebel Web Client and Siebel Tools installations, in the SIEBEL_CLIENT_ROOT/public directory and the SIEBEL_TOOLS_ROOT/public directory, similar changes have been made as those on the SWSE, for applicable directories and files.

    Issue. After a migration installation of Siebel Web Client or Siebel Tools, duplicate directories will exist, because some of the directories provided in Siebel Innovation Pack 2016 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 your migrated custom files and to conform to the changes described in this topic for SWSE. Finally, remove all extraneous files and directories in SIEBEL_CLIENT_ROOT/public and SIEBEL_TOOLS_ROOT/public.

  • Move files and directories: Files and directories have changed in the webtempl directory on Siebel Server, Siebel Web Client, and Siebel Tools. On Siebel Server, Siebel Web Client, and Siebel Tools installations, in the webtempl directory, the ouiwebtempl and ouiwebtempl/custom directories are no longer used. Only Web templates for Siebel Open UI are valid. Only the webtempl and webtempl/custom directories are needed in Siebel Innovation Pack 2016, and contain standard Web templates and custom Web templates, respectively.

    Issue. After a migration installation of Siebel Server, Siebel Web Client, or Siebel Tools, your custom Web template files for Siebel Open UI will be in the wrong locations and cannot be used until you have moved them to the new locations.

    Solution. In SIEBSRVR_ROOT, SIEBEL_CLIENT_ROOT, and SIEBEL_TOOLS_ROOT, move the migrated files from webtempl/ouiwebtempl/custom into webtempl/custom. Then remove the directories webtempl/ouiwebtempl/custom and webtempl/ouiwebtempl.

  • (Oracle Database only) Upgrade the Oracle Database Client. For deployments on Oracle Database in a migration installation case, after migrating, you must upgrade the Oracle Database Client to a supported version for Siebel Innovation Pack 2016, as noted in the Certifications tab on My Oracle Support. You must also update the Oracle Database Client path in the defined environment variables. For more information, see About Configuring Siebel Business Applications.

    Using Oracle Database XE for Siebel Mobile Web Client or Siebel Tools also requires a valid Oracle Database Client, as noted in Installing and Using Oracle Database XE for the Local or Sample Database.

  • Edit configuration files for Siebel Web Client. After doing a migration installation for Siebel Web Client for Siebel Innovation Pack 2016, you must edit all applicable migrated configuration files, such as uagent.cfg for Siebel Call Center. In the [Siebel] section of each applicable configuration file, update the value of the WebClientSiteDir parameter to remove the language element. 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 now obsolete in Siebel Innovation Pack 2016. To reduce confusion after migration installations, you might choose to delete some of the parameters that no longer apply, such as HighInteractivity and EnableOpenUI. For more information about obsolete parameters, see Siebel System Administration Guide.
  • Reset passwords in siebns.dat and on the Siebel Server. After doing a migration installation of Siebel Innovation Pack 2016, you must reset any passwords in the siebns.dat file on the Siebel Gateway Name Server that were previously encrypted using RC4 encryption. In the current release, such passwords are encrypted using AES instead of RC4. 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.

Updating the Siebel Server System Service and Server Components to Use AES Password Encryption

The Siebel Server system service and server components do not work after a migration installation until you have performed steps to update them to use AES password encryption, as described in the following procedure. The examples in the procedure are for UNIX operating systems, but the same issue applies on Microsoft Windows.

To update the Siebel Server system service and server components to use AES password encryption

  1. Unset any SIEBEL* environment variables.
  2. Source the siebenv script from the Siebel Gateway Name Server installation directory, as follows:

    . ./siebenv.sh

  3. Start the Siebel Gateway Name Server and make sure that it is running.
  4. Write down the old encrypted password from the current siebns.dat file. For example:

    [/enterprises/esia81/parameters/Password]
    Persistence=full
    Type=string
    Value="9ntkUOUf"
    Length=16

  5. Run a command like the following, using the old encrypted password value:

    ../ses/siebsrvr/lib/spu 9ntkUOUf

    This command obtains a reencrypted value for the password, such as in the following output:

    ENPVR6S/HKgBncoAAA==

  6. Delete the current svc* and osdf* files from the SIEBSRVR_ROOT/sys directory.
  7. Source the siebenv script from the SIEBSRVR_ROOT directory.
  8. Change directory to the SIEBSRVR_ROOT/bin directory and then run a command like the following:

    siebctl -S siebsrvr -i esia81:srvr1 -a -g "-g localhost:2320 -e esia81 -s srvr1 -u SADMIN -ep ENPVR6S/HKgBncoAAA=="

    Note that the new encrypted string from Step 5 is used.

  9. Run the following command using the old encrypted password value, like the following:

    ../ses/siebsrvr/lib/gpu -g localhost:2320 -e esia81 -u SADMIN -p 9ntkUOUf

  10. Customers who have overridden the user name or password at the component definition level must change the passwords again through srvrmgr in order to use the new encrypted password value. For example:

    change param password=<pwd_value> for compdef <comp_name>

    change param password=<pwd_value> for comp <comp_name> server <server_name>

  11. Update old encrypted passwords in the current siebns.dat file on the Siebel Gateway Name Server to use AES encryption.

    For more information, see Siebel Security Guide.

  12. Restart both the Siebel Gateway Name Server and the Siebel Server.
Related Topics

About Installing Siebel Business Applications

About Configuring Siebel Business Applications

About Installing the Siebel Web Client or Siebel Tools

Installing and Using Oracle Database XE for the Local or Sample Database

Uninstalling Siebel Business Applications

      
Siebel Installation Guide for UNIX Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices.