What’s New in This Release

This chapter tracks the changes in the documentation. It includes the following topics:

What’s New in Siebel Database Upgrade Guide, Siebel CRM 24.11 Update

The following table lists the changes in this revision of the documentation to support this release of the software.

Topic

Description

Siebel CRM Upgrade Factory

Siebel CRM Upgrade Factory On Premises

Modified chapters. Upgrade Factory 2.0 extends the capabilities of the original release of the Upgrade Factory, providing an easier experience for you to leverage Upgrade Factory for their Siebel Upgrades.

What’s New in Siebel Database Upgrade Guide, Siebel CRM 24.1 Update

The following table lists the changes in this revision of the documentation to support this release of the software.

Topic

Description

Using REST API to Execute Schema Imports

New topic. You can manually run schema imports using the Migration Schema Service Import Business Service from inbound REST requests.

What’s New in Siebel Database Upgrade Guide, Siebel CRM 23.10 Update

The following table lists the changes in this revision of the documentation to support this release of the software.

Topic

Description

Component Parameter to Auto-detect Updated Configuration in the Runtime Repository

New topic. Component parameter feature is introduced to allow migrated configuration to be immediately available without a user login.

What’s New in Siebel Database Upgrade Guide, Siebel CRM 23.9 Update

The following table lists the changes in this revision of the documentation to support this release of the software.

Topic

Description

Siebel CRM Upgrade Factory On Premises

New topic. Upgrade Factory On Premises enables a simpler, faster, more predictable upgrade process.

Executing a Siebel Full Migration Plan

New Topic. Executing a full migration plan using Siebel Migration.

What’s New in Siebel Database Upgrade Guide, Siebel CRM 23.8 Update

The following table lists the changes in this revision of the documentation to support this release of the software.

Topic

Description

Monthly Updates 20.8 – 22.6 to 22.7+ - Workflow Process Consideration

New Topics. Workflow Process Consideration

What’s New in Siebel Database Upgrade Guide, Siebel CRM 23.7 Update

The following table lists the changes in this revision of the documentation to support this release of the software.

Topic

Description

Executing a Siebel Migration Plan

Executing a Migration Plan

Modified Topics. Additional information added as notes.

What’s New in Siebel Database Upgrade Guide, Siebel CRM 23.6 Update

The following table lists the changes in this revision of the documentation to support this release of the software.

Topic

Description

Siebel CRM Upgrade Factory

New topic. Siebel CRM Upgrade Factory delivers an automated development upgrade that includes the quick setup of a development environment and the efficient transition from Siebel CRM 8.0 and above to the latest Siebel CRM Release Update. The upgrade factory approach simplifies the application upgrade process, allowing customers to upload their customized, pre-IP2017 repository to run an upgrade and IRM process on Oracle Cloud Infrastructure (OCI).

What’s New in Siebel Database Upgrade Guide, Siebel CRM 23.1 Update

The following table lists the changes in this revision of the documentation to support this release of the software.

Topic

Description

Migrated Configuration Data Is Available to the Runtime Repository Without User Re-Login

New topic. It describes how the new configuration data migrated to Runtime Repository is available to users without user re-login.

What’s New in Siebel Database Upgrade Guide, Siebel CRM 22.7 Update

The following table lists the changes in this revision of the documentation to support this release of the software.

Topic

Description

Supported Upgrade Paths for Siebel CRM

Modified topics. Updated the version numbers for supported upgrade paths.

Test Environment

Modified topic. There is a third task involved in upgrading a test environment.

Production Environment

Modified topic. There is a fourth task involved in upgrading a production environment.

Logging and Diagnostics

Modified topic. Information about the TaskUpgrade utility has been added to this topic.

Running RepositoryUpgrade Utility

Modified topic. The -9 parameter no longer defaults to "MAIN". Best practice is to specify an Integration Workspace reflecting a planned future release (you will receive an error if you specify "MAIN").

Full Runtime Repository Migration Without Using Siebel Migration

Modified topic. The last note in this topic (step 12) is new.

Managing Cross Version Migration

Modified topic. Describes how workflows and task flows are handled during cross version migration. Describes also the CleanUpTaskDR utility.

What’s New in Siebel Database Upgrade Guide, Siebel CRM 22.5 Update

The following table lists the changes in this revision of the documentation to support this release of the software.

Topic

Description

Creating a New ODBC Data Source Before Upgrading Siebel Database

New topic. Describes how to manually create a new ODBC datasource.

Analyzing IBM DB2 Custom Tablespace Requirements for a Siebel Upgrade

Modified topic. The command line in Step 2 of this procedure has been updated to include the following switches: /Z UCS2_DATABASE and /A DEBUGMODE.

Post Installation Database Update

RepositoryUpgrade Utility

Modified topics. The PostInstallDBSetup.zip file contains the payload for PostInstallDBSetup and the RepositoryUpgrade.zip file contains the payload for RepositoryUpgrade. Both files are located in the Siebel Server "bin" folder.

Roadmap for Planning a Migration with Siebel Migration

Modified topic. The following note has been added to step 2a in this roadmap:

Note: The process running the Siebel Object Manager must have read-write access to the network file share path for the Migration Package Location.

Configure User Access to Siebel Migration Application

New topic. To access the Siebel Migration Application, users must be assigned the appropriate responsibility (for example, "Migration Users" responsibility).

Scenario for Using a Watermark

New topic. Describes a situation when a watermark is required.

Types of Watermarks

New topic. A generated watermark file can contain several types of watermarks.

Executing a Siebel Migration Plan

Modified topic. Steps 1 and 5 have been updated.

Renaming Repositories After Full Migration

Modified topic. You must provide the full path to the siebel.cfg file (for example: $SIEBEL_HOME\siebsrvr\bin\enu\<siebel.cfg>) .

Aborting a Running Migration Plan

New topic. Describes how to abort a running migration plan.

Viewing Migration Log Files

New topic. Describes how to view the log files for a migration plan.

Viewing Migration History

New topic. Describes how to view the history details for a migration plan execution.

Query Migration History

New topic. Describes how to query migration history data and filter the data shown in the History screen.

Cleanup Migration History

New topic. Describes how to cleanup migration history data by deleting history records in the History screen.

Full Runtime Repository Migration Without Using Siebel Migration

Modified topic. The last step in this procedure (re activating Task-based UI tasks in the target environment) is obsolete and has been removed.

Troubleshooting Data Migration Using Siebel Migration

New topic. This topic highlights some important issues to note when using Siebel Migration to migrate data.

Creating a New Migration Plan

Modified topic. The sample code in this topic has been updated.

About Inheriting Upgrade Behavior in a Siebel Upgrade

About the Siebel Postmerge Utilities

CSSGridRepPatch

CSSUINavUpgradeReposPrep

CSSMVGUpgradePatch77

Upgrade Planning for Siebel Workflow Designer

Running the Siebel Postmerge Utilities

Reviewing Siebel Grid-Based Applets

Review the User Interface

Modified topics. These topics have been updated to remove ICL content since Siebel Incorporate Custom Layout is no longer supported.

Siebel Incorporate Custom Layout Upgrade Option (chapter)

CSSWebTemplatePatch

Migrating Siebel Repository Objects to the Standard User Interface

Using Lag Time to Identify Postupgrade Customizations

How Repository Objects are Changed

How Logging is Done

Specifying a Lag Time

Migrating to the Standard User Interface

Eliminating Obsolete Siebel UI Fields

Reviewing Siebel UI Objects Affected by Incorporate Custom Layout

Reviewing Required Fields in the Siebel User Interface

Obsolete topics. These topics has been removed from the guide since Siebel Incorporate Custom Layout (ICL) is no longer supported.

About Siebel Rules Expression Designer

Creating Migration Rules

Activating Tasks

Activating Tasks with the Migration Incremental Runtime Repository Data Service

Obsolete topics. These topics have been removed from the guide.

What’s New in Siebel Database Upgrade Guide, Siebel CRM 22.3 Update

The following table lists the changes in this revision of the documentation to support this release of the software.

Topic

Description

Marking Conflict Resolution as Complete Using Siebel Tools

Modified topic. Step 1 in this procedure has changed. $SIEBEL_HOME is the directory where Siebel Tools is installed (a typical location would be C:\Siebel\Tools).

Renaming Repositories After Full Migration

New topic. Describes how to rename repositories after a full migration using the siebdevcli utility.

Full Runtime Repository Migration Without Using Siebel Migration

Modified topic. Steps 12 and 13 in this procedure have changed (step 14 is obsolete).

RepositoryUpgrade Utility

New topic. Describes the purpose of the RepositoryUpgrade utility and the typical order of events when planning to run the utility.

Managing Cross Version Migration

New topic. Describes how to manage some types of changes during cross version migration and the purpose of setting the FullMigCompatibilityMode system preference.

Executing a Migration Plan

Modified topic. Shows the HTTP POST request details to execute a migration plan.

What’s New in Siebel Database Upgrade Guide, Siebel CRM 21.10 Update

The following table lists the changes in this revision of the documentation to support this release of the software.

Topic

Description

Post Installation Database Update

Modified topic. The REP_VER_NUM column is automatically added to the S_WS_VERSION table during Post Installation Database Update. The purpose of the REP_VER_NUM column is to capture Siebel Repository version information when the RepositoryUpgrade utility is run – so that repository version and Workspace version are linked together.

Post Installation Database Update Exit Codes

New topic. Describes all PostInstallDBSetup utility exit codes.

Siebel Repository and Workspace Version Tracking

New topic. Describes how Siebel Repository and Workspace version tracking works.

Full Runtime Repository Migration Without Using Siebel Migration

Modified topic. Step12 in this procedure has changed.

What’s New in Siebel Database Upgrade Guide, Siebel CRM 21.8 Update

The following table lists the changes in this revision of the documentation to support this release of the software.

Topic

Description

Verifying or Editing an ODBC Definition on Windows

Modified topic. Because Siebel application uses a 32-bit ODBC data source, the registry entry for ODBC data source is as follows: HKEY_LOCAL_MACHINE\Software\Wow6432Node\ODBC\ODBC.INI\ODBC_Name.

Preparing Siebel Workflow Processes for Upgrade

About Workflow Processes in Siebel Repository

Obsolete topics. These topics have been removed from the guide.

Values Required by Post Installation Database Update

New topic. This topic replaces Siebel Enterprise Server Installer Changes.

Running RepositoryUpgrade Utility

Independently Apply RepositoryUpgrade Schema Changes

Modified topics. The RepositoryUpgrade utility should always be run from the Siebel Server home directory ($SIEBEL_HOME).

What’s New in Siebel Database Upgrade Guide, Siebel CRM 21.5 Update

The following table lists the changes in this revision of the documentation to support this release of the software.

Topic

Description

About Migrating with Siebel Migration

The Siebel service owner account must have read-write access to Siebel File System and the Migration Package Location.

Data Migration Using Siebel Migration

Modified topic. Siebel Migration does not support migration of repository or Workspace data from RR environments to other RR environments.

Setting the Seed Migration Priority System Preference

New topic. Describes the Seed Migration Priority system preference and when to set it.

Post Installation Database Update

Modified topic. You can select whether to execute, defer, or skip running the PostInstallDBSetup utility during the update installation.

Postpone Running Post Installation Database Update

New topic. If you do not want to implement the physical database schema changes during a monthly update release but apply them later by running the PostInstallDBSetup utility, then complete the steps in this procedure.

Skip Post Installation Database Update

New topic. If you do not want the installer to run the PostInstallDBSetup utility, then complete the steps in this procedure.

Independently Apply RepositoryUpgrade Schema Changes

New topic. Describes how to apply RepositoryUpgrade schema changes external to Siebel CRM utilities.

Refreshing a Connection

Refreshing a Migration Plan

New topics. You can refresh a connection and a migration plan for your migration by sending an HTTP POST request to the Siebel Migration Application.

What’s New in Siebel Database Upgrade Guide, Siebel CRM 21.3 Update

The following table lists the changes in this revision of the documentation to support this release of the software.

Topic

Description

Upgrade Planning for Siebel AES Encryption

Modifying siebel.cfg Before Upgrading Siebel Database

Modified topics. The siebel.cfg file must be updated correctly before running the Key Database Manager utility. For more information on the parameters to set (or update) in siebel.cfg before running the Key Database Manager utility, see Siebel Security Guide.

Importing with the Migration Schema Service

Modified topic. The Request Parameters (filename and password) and Request Body (filename and password) have been updated.

Importing with the Migration Application Data Service

Modified topic. The Request Parameters (filename) and Request Body (filename) have been updated.

Importing with the Migration Application Data Service With Transformation

Modified topic. The Request Parameters (filename) and Request Body (filename) have been updated.

Importing with the Migration Incremental Runtime Repository Data Service

Modified topic. The Request Parameters (filename) and Request Body (filename) have been updated.

Importing with the Migration Runtime Repository Data Service

Modified topic. The Request Parameters (filename) and Request Body (filename) have been updated.

Importing with the Migration Incremental Application Workspace Data Service

Modified topic. The Request Parameters (filename) and Request Body (filename) have been updated.

Getting a Seed Copy Import with the Migration Application Workspace Data Service

Modified topic. The Request Parameters (filename) and Request Body (filename) have been updated.

Getting the Full Seed Import with the Migration Application Workspace Data Service

Modified topic. The Request Parameters (filename) and Request Body (filename) have been updated.

Running RepositoryUpgrade Utility

New topic. Describes how to run the RepositoryUpgrade utility.

Multiple topics

In Siebel CRM 21.2 Update, the applicationcontainer directory has been replaced by two directories, as follows:

  • applicationcontainer_external (for Siebel Application Interface)

  • applicationcontainer_internal (for all other Siebel Enterprise components)

In the Siebel Application Interface Installation, Web artifacts for application configurations, which were formerly located in applicationcontainer\webapps\siebel, now map to applicationcontainer_external\siebelwebroot. The siebelwebroot directory contains subdirectories such as files, fonts, htmltemplates, images, migration, scripts, and smc.