Create a 6.2 Test Environment
The test area should correspond as closely as possible to the live deployment environment (and 3.5 test 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.
• OpenROAD installation (local or file-served). This includes:
– Ingres and operating system environment variables
– ingres\files area (especially config.dat and appedtt.ff, apped.ctb, and any variants)
– ingres\w4glapps area (all referenced application images)
– Any globals redefinition files
– Any other files and file areas the applications reference (including 3GL library files, registered where necessary), with appropriate permissions
• The same test data that the 3.5 environment is working with, in a test database 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.
• Ingres Net nodes (redirected to up-to-date test or training databases)
• Startup and other batch files (amended to reference the relevant databases, file systems, and so on, redirected as appropriate)
• Shortcuts (as these may contain explicit parameters or settings)
• User accounts, passwords, and permissions necessary to run the applications successfully
• Network connectivity (where it affects OpenROAD application use)
• Operating system, drivers, and settings (monitor, regional, and language settings in particular)
• Citrix and MainWin settings, where applicable
• Any referenced non-Ingres software, where its absence may prevent navigating to or displaying parts of the OpenROAD application
• A display monitor set to client specifications
Ensure that you can access this test environment through an account with sufficient rights to issue commands such as ingsetenv.