Preparing the Original Application for Conversion

Many OpenInsight-based applications have grown organically over their lifespans. New windows could have been created, old ones saved and modified, new reports started but never finished, etc.

Since the conversion process will move over every entity from the original application to OpenInsight 10, so before the conversion process is run, it is a good time to examine the existing application and clean it up as much as possible.

We recommend that you, or your system’s developer, clean the system that is to be converted by using the SCAN_REP window.

NOTE: The Scan Repository window has been updated for OpenInsight 10.2.3 and newer. Please review the instructions for the new Scan Repository tool here.

The Scan Repository Wizard, an automated form that prompts the user for a few key pieces of information and then executes on its own, examines system-defined types and classes and creates any new ones, if needed. It also prompts the user to select a basic scan (or perform a custom one), or to automatically scan the whole repository.

After scanning the repository, the Scan Repository produces a report for all invalid/orphaned entities it found and prompts the user to delete or retain them. The report also indicates the reason Scan Repository flagged these faults.

The wizard also suggests whether the system indexes should be rebuilt and—if they do—provides the steps to do so. This tool is especially helpful when used just before the OpenInsight 10 Conversion process since invalid repository entities may prevent a successful conversion.

The wizard can be executed in two different ways: through the Application Manager or through the System Monitor. To execute Scan Repository through the application manager, go to OpenInsight executables, and choose OpenInsight Form Executables, then scroll down to the form; “SCAN_REP”. SHIFT+DOUBLE-CLICK the

SCAN_REP form. This will execute the form. Or, from the System Monitor, type in the following command: EXEC SCAN_REP and press return. This will also launch the form.

Before launching the form, please ensure that all other users are logged out of the application.

When the form first launches, the first screen will confirm that Repository Mirroring is turned off, and that all other users are logged out. It does them automatically. It also requires that the user check the box indicating that a recent backup is available. Ensure that there is a recent backup, and check the box, as seen below. Once you have checked the box, the Next button becomes enabled. Click on it.

Once the Next button has been clicked, the second panel of the wizard appears, asking if the user would like to create types and classes that may be missing. Choose the default of ‘Create known repository types and classes’, and press the Next button.

Pressing on the Next button will cause the system to create any missing types or classes. The Options panel appears next.

The next screen the user the option to customize the search according to his needs. If the user wants everything be scanned for errors, he should leave all the defaults “as is” and click the button marked “NEXT”. If the user wishes to create a custom scan, he can check or deselect the appropriate boxes.

The default selections are recommended for all scans. The only benefit from changing the defaults is to scale down the comprehensiveness of the tests, reducing the length of time involved in the scan. Users unfamiliar with what the checkboxes refer to should leave the first and last checkbox unselected, and the rest checked (the default).

Clicking on the Next button causes the Repository Scan to begin. The final screen lists all the entities and classes the wizard found to be invalid and recommended for deletion. Reasons for deletion can be found in the column marked “REASONS”.

The user can either manually select specific objects for deletion, or select all objects to be deleted. It is recommended that experienced developer decide which entities should be deleted. Once complete, the Conversion process should be run.

Note: Please remove or rename any REVPARAM files from the target OpenInsight v9 application before launching the Conversion Program.

Note: Relational indexes and custom MFS may need to be removed if migrating via LH Copy.