|
Siebel Installation Guide for Microsoft Windows > Installing Siebel Business Applications Server Modules >
Additional Tasks for Migration Installations
Certain product changes that were made in Siebel Innovation Pack 2017 (or in prior releases) 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. Some migration tasks previously documented for Siebel Innovation Pack 2016 might not need to be done again for customers migrating from that release. These product changes affect some of the files and directories of installations of Siebel Server, Siebel Application Interface, 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 2017
Many product and support changes for Siebel Innovation Pack 2017 (and other recent 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 Innovation Pack 2016.
- 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 configure Siebel Application Interface after migrating. In Siebel Innovation Pack 2016, the virtual directories, which formerly mapped to
public\lang_code (such as ENU), were mapped directly to public. In Siebel Innovation Pack 2017, virtual directories are replaced by application configurations, which now map to applicationcontainer\webapps\siebel 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 Business Applications and About Configuring Siebel Business Applications.
CAUTION: You must remove the configuration for the SWSE before you install the current release 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 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 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 Innovation Pack 2017, 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.
- The webmaster directory on Siebel Server. As of Siebel Innovation Pack 2016, the
SIEBSRVR_ROOT\webmaster directory on the Siebel Server has been removed. If you are migrating from a release prior to Siebel Innovation Pack 2016, then you can delete this directory from your migrated Siebel Server installation.
- The public directory on Siebel Web Server Extension. In Siebel Innovation Pack 2017, the
SWSE_ROOT\public directory is not part of the Siebel Application Interface installation. The equivalent location is SIEBEL_AI_ROOT\applicationcontainer\webapps\siebel. For the current release, 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 Innovation Pack 2016:
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 has been removed. The scripts subdirectory has moved under public. And the build_number directory has been removed.
public\lang_code\files. This directory has moved under public.
public\lang_code\fonts. This directory has moved under public.
public\lang_code\htmltemplates. This directory has moved under public.
public\lang_code\images. This directory has moved under public.
public\lang_code\webeditor. This directory has been removed.
public\lang_code\default.htm. This file has moved under public.
public\lang_code\blank.htm. This file has moved under public.
public\lang_code\wait.htm. This file has been removed.
public\lang_code\*.pcd. These files have been removed.
public\lang_code\*.manifest. The variable string %BuildNumber% has been removed from the .tmanifest files, from which the .manifest files are generated.
NOTE: In Siebel Innovation Pack 2017, the Siebel application virtual directories, which formerly mapped to the public\lang_code directory on SWSE, are obsolete. Instead, the application configurations for Siebel Application Interface map to SIEBEL_AI_ROOT\applicationcontainer\webapps\siebel (without the lang_code element).
- 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 Innovation Pack 2016. 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 Innovation Pack 2016.
Issue (for migrations from release prior to Siebel Innovation Pack 2016). After a migration installation of Siebel Web Client or Siebel Tools (from a release prior to Siebel Innovation Pack 2016), 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 Siebel Innovation Pack 2017, 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. For more information, see About Configuring Siebel Business Applications.
Using Oracle Database XE for Siebel Mobile Web Client or Siebel Tools requires a supported version of the 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 from Siebel Innovation Pack 2016 or from a release prior to Siebel Innovation Pack 2016, you might need to edit all applicable migrated configuration files, such as uagent.cfg for Siebel Call Center. For example:
For a migration from a release prior to Siebel Innovation Pack 2016, 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 now obsolete in Siebel Innovation Pack 2017. 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 Innovation Pack 2016). 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 of Siebel Innovation Pack 2017 (from a release prior to Siebel Innovation Pack 2016), you must reset any passwords on the Siebel Gateway that were previously encrypted using encryption other than AES. In the current release, such passwords are 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.
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. Most of the command 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
- Unset any SIEBEL* environment variables.
- Source the siebenv script from the Siebel Gateway installation directory, as follows:
./siebenv.sh
- Start the Siebel Gateway and make sure that it is running.
- 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
- Run a command like the following, using the old encrypted password value:
SIEBEL_ROOT/siebsrvr/lib/spu 9ntkUOUf
This command obtains a reencrypted value for the password, such as in the following output:
ENPVR6S/HKgBncoAAA==
- Delete the current svc* and osdf* files from the
SIEBSRVR_ROOT/sys directory.
- Source the siebenv script from the
SIEBSRVR_ROOT directory.
- 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.
- Run the following command using the old encrypted password value, like the following:
SIEBEL_ROOT/siebsrvr/lib/gpu -g localhost:2320 -e esia81 -u SADMIN -p 9ntkUOUf
- 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>
- Update old encrypted passwords on the Siebel Gateway to use AES encryption.
For more information, see Siebel Security Guide.
- Restart both the Siebel Gateway and the Siebel Server.
Related Topics
About Installation Tasks for 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
Process of Removing Configuration Data
|
