Bookshelf Home | Contents | Index | Search | PDF

Siebel Interactive Selling Applications Upgrade Guide > Upgrading OnLink Browser-Based Applications to Siebel 7 > Overview of Upgrading OnLink Browser-Based Applications to Siebel 7 >

The Upgrade Process

---

You begin the process outlined in this guide once you have Siebel 7 installed. For information on setting up your implementation of Siebel 7, see the Siebel Server Installation Guide for the operating system you are using, and Siebel Tools Reference.

The upgrade tools you will use are embedded into the Siebel Interactive Designer authoring environment within the screens used to create new eAdvisor and eConfigurator applications. This approach allows the upgraded applications to be edited within the same environment.

You will complete the upgrade process by taking these steps:

Preparing for the migration by verifying that you have a working project.
Generating the HTML files and export each pageset.
Migrating version 4.x projects to Siebel 7 projects.
Publishing and validate the migration.
Performing a quality review of your application.
Deploying the migrated application to your site.

NOTE:  This upgrade process was designed to migrate the files and data normally associated with a standard version 4.x application. This process is not capable of automatically upgrading customized code or other special files you may have associated or embedded into your application. Special consideration must be given to upgrade any customized aspects of the applications.

Figure 14 shows how a 4.x project is migrated.

Figure 14. Migration of 4.x Project Files

The Migrate function copies the application data into the database and the project files into the file system. During this update, the CSV files are interpreted into pageset, feature, and configuration table data within the S_ONL_* database tables.

Limitations

Upgrading to eAdvisor version 7 has the following limitations:

The Contents List display names (listed in the Contents List Table Manager) from the 4.x project will not be preserved. See Backing Up Your 4.x Project.
The upgrade process does not validate the Composer 4.x data model. See Backing Up Your 4.x Project.
You cannot overwrite an existing Siebel project. To remigrate, you must delete the existing Siebel project first, or create a new Siebel project with a different name.
The version 4.x display pages or other application HTML will not be converted to SWE Web template format.
Since the code set will be upgraded, any custom code changes made to the 4.x run-time code set files will not be preserved in the migration. Any custom code changes to files other than code set files are not guaranteed to be preserved. See Backing Up Your 4.x Project.

Bookshelf Home | Contents | Index | Search | PDF