Siebel Composer Developer Preview Guide > Setting up Siebel Composer >

About the Web Template Migration Process

A Web template migration process is automatically completed when:

• You install the current release in a new deployment.
• You run Incremental Repository Merge after you install the current release as a migration installation for an existing Siebel installation of an earlier version.

  The time needed for Incremental Repository Merge is longer than the time in earlier releases because of the Web template migration process.

• You upgrade the Siebel database from a release earlier than the Siebel 8.1.1/8.2.2 release.

In this process, a script is run to convert file-based content for Siebel Web templates into the table-based content for Siebel Web templates. This table-based content appears in fields in Siebel Composer. For more information about the newly added fields in Siebel Composer, see Added Fields in Siebel Composer.

The semantics of the logical Web template are retained in this conversion process. Table 6 shows how the information in Siebel Web template files is mapped to the fields in Siebel Composer.

New Web templates are created for the Siebel Web template files that are included in another Siebel Web template file.

All Siebel Web template files in the appropriate directories are included in the migration process. For more information about the appropriate directories, see Prerequisite for Web Template Migration Process.

The migration script is supported in all environments and database platforms. For more information about installing a new Siebel database, see Siebel Installation Guide for the operating system you are using. For more information about upgrading the Siebel database and about using Incremental Repository Merge, see Siebel Database Upgrade Guide.