1. Initiation

Initiation is the data- or fact-gathering stage. It is concerned with investigating and documenting the current installation, which includes identifying all existing instances of OpenROAD, and gathering and documenting the requirements for the new environments.

Record any settings relevant to the existing OpenROAD installation. The upgrade test area should correspond as closely as possible to the live deployment environment, as should the development area setup to recompile and image OpenROAD in a 6.2 environment. The following checklist may be helpful in creating a proper test environment. These elements—or their absence—will impact the speed and success of your upgrade.

– ingres\files area (especially config.dat and appedtt.ff, apped.ctb, and any variants)

– Any other files and file areas that applications reference (including 3GL library files, registered where necessary), with appropriate permissions

• A test database with test data that closely tracks production data, configured to match the live database (including any II_EMBED_SET or ING_SET settings). If you are copying the data using copydb, ensure that any contents of II_STORED_STRINGS and II_STORED_BITMAPS are copied as well.

• Startup and other batch files (amended to reference the relevant databases, file systems, and so on, redirected as appropriate)

• User accounts, passwords, and permissions necessary to run the applications successfully

• Operating system, drivers, and settings (monitor, regional, and language settings in particular)

• Any referenced non-Ingres software, where its absence may prevent navigating to or displaying parts of the OpenROAD application

Ensure that you can access this test environment through an account with sufficient permissions to issue commands such as ingsetenv.

Determine and establish the roles and necessary skills required for the upgrade and ascertain the availability of the necessary people on the upgrade team.

Team members should establish and agree upon any expectations or mandatory requirements for the upgrade. For example, your business may have set certain performance targets or expectations as to when the upgrade should be in place. Incorporate these into your plan.

After this initiation process, the scope of the upgrade should be clear. Add all these elements to the plan as outlined in 6. Plan Creation.

For a safe and orderly upgrade, at least four OpenROAD installations are needed:

• New version of the development installation for preparing and testing applications

If possible, keep the installations away from the production machine. You may temporarily need additional hardware to accommodate the required installations during the upgrade.

A four-machine setup can be used, with each installation on its own machine. More commonly, however, the two development installations will share a machine. Because there is usually some traffic between these two installations during preparation, sharing a machine is convenient.

The OpenROAD 5.1 and OpenROAD 6.2 Development and Runtime features can reside on the same machine when installed into separate Ingres instances.

It is possible to deploy an OpenROAD 5.1 and OpenROAD 6.2 eClient runtime on the same machine. Configure each eClient application to select which version of the eClient runtime to use.

The OpenROAD Server for OpenROAD 5.1 and OpenROAD 6.2 needs environment variables that are set at the Windows system level. This means that you may install only one instance of the OpenROAD Server per machine.

Note: There is no remote installation procedure for OpenROAD. The machine must have local media support; otherwise, you will need to copy the distribution files from wherever they were installed.