General Overview of the Conversion Process

While OpenInsight 10 is backward-compatible with earlier versions of OpenInsight, components of these earlier versions will not be able to take advantage of many of the new features and functionality of OpenInsight 10.0, unless they are recompiled. Rather than forcing the developer or user to recompile every component of an application, this Conversion Utility does most of this work for you.

In general, the flow is this:

• A new application is created in OpenInsight 10.0 with the same name as the application in the prior version of OpenInsight.

• The new Application is opened.

• The user launches the Conversion Utility from TCL.

• The user is prompted for the location of the original application.

• The user chooses the specific application to be converted.

• The system offers up a list of data volumes being used by that application.

• The user decides what to do with the data at those locations.

o (Data is either moved or copied to new locations, or left where it is)

• The Users and environment settings are replicated in the new Application.

• All repository items in the old application are copied into the new Application.

• Entity-specific changes are made.

• Result reports are generated on how the conversion went.

The conversion process does NOT copy any non-repository-based records that are stored in any system tables into the new OpenInsight 10 system. If there are records stored in system tables (such as SYSENV, SYSLISTS, etc.) that you wish to bring into the new system, you must either:

a) create APPROW entities for the record(s) that you wish to include; or

b) manually copy the records from your original system into your new OpenInsight 10 system after the automated upgrade has completed

Again, any records stored in system tables that do not have repository entries will NOT be copied during the conversion process.

In the following pages we will instruct the user or developer on how to run this process.