Install OpenROAD into an Existing Ingres Installation
The installer can install the MainWin System Core (MSC) subsystem during the installation process, or you can follow the instructions to install the MSC subsystem manually later.
How to Prepare for Installation
Before you install OpenROAD into an existing Ingres installation, you must perform the following steps.
To prepare for installation
1. Shut down your existing Ingres installation (ingstop).
2. Shut down the OpenROAD Server, if running (orspostop).
3. Perform a backup of your Ingres installation.
4. Decide which OpenROAD package you want to install:
• ordev for OpenROAD Runtime and Development
• orrun for OpenROAD Runtime only
Note: The ordev and orrun packages do not include the Ingres Net components. The installer does not allow an Ingres Net upgrade because you are installing into an existing Ingres installation. To upgrade your Ingres Net in this situation, you must first acquire and install a new version of Ingres.
5. Decide whether you want the installer to prompt for license acceptance.
Installation Command Syntax
The installation command uses the following syntax:
./or62install.sh -f filename.tar
–l prompt|accept
-mtmp path
-no_xml_lib
-r N|Y
-t ordev|orrun | tee or62install.log
-f filename.tar
Specifies the OpenROAD installation tar file name
-l prompt|accept
Specifies how to handle the license prompt:
prompt
Specifies that the user will be prompted to accept the Actian license
accept
Specifies that the license will be accepted automatically without prompting the user
Default: prompt
-mtmp path
Specifies the path for temporary MainWin files
Default: /tmp
-no_xml_lib
Specifies that the platform-specific XML library not be registered.
Important! XML system classes, XML import/export functionality, and passing XML to the OpenROAD server will not work if this option is used.
-r N|Y
Specifies whether the OpenROAD Server components should be registered.
For 32-bit only: Registration requires that the -m Y flag be specified or that MCS be running already.
Default: N
-t orpkg
Specifies one of the following installation types:
ordev
Specifies OpenROAD Development (includes Runtime)
orrun
Specifies OpenROAD Runtime only
Example—installation command:
The following command starts the installation, specifies that OpenROAD Development be installed and that that the license file be accepted automatically, specifies a path for temporary MainWin files, does not register the OpenROAD Server components, and creates the installation log or62install.log.
./or62install.sh -t ordev -f or62.tar –l accept -mtmp path -r N | tee or62install.log
Start the Installation
You install OpenROAD using or62install.sh.
To start the installation
1. Log in as the owner of the existing Ingres installation and set Ingres environment (II_SYSTEM, etc.)
2. Copy or62.tar into the $II_SYSTEM directory.
3. Change the current directory to $II_SYSTEM.
4. Untar the tar file into the installation script:
tar xf or62.tar or62install.sh
During installation, the installer prompts for a root password if you decided to install the MainWin System Core (also known as the MSC subsystem).
Start Ingres and Workbench on Linux Systems
1. Start Ingres and create a database (if one has not already been created) to act as the Workbench repository:
cd ~ingres
ingstart
createdb myrepo
2. Start the OpenROAD Workbench in your display console:
source .orXXsh
export DISPLAY=:0.0
w4gldev runimage workbnch.img -Tall
Replace XX with your installation identifier, for example II.
How You Perform Post-installation Customization
After installing OpenROAD, you can customize the runtime environment by following these steps.
1. The MSC subsystem is set up to run as a system service, S99mwcore_services, as a daemon process at system boot time.
If you have previously set up a daemon process S99orspo to start the OpenROAD Server at system boot, ensure that the daemon runs after the MSC subsystem daemon process.
2. Use the environment setup script created by the installer, replacing XX with your installation identifier:
For C shell (csh):
% source $HOME/.orXXcsh
For Bourne (sh), Korn (ksh), or bash shell:
$ . $HOME/.orXXsh
How You Update Your Registry on UNIX
The registry file created prior to OpenROAD 4.1 SP3 is incompatible with this release. After you have completed installing or upgrading OpenROAD, do one of the following:
• Convert an existing registry file to the new format (see Update an Existing Registry File)
Note: We recommend that you create a new registry file for this release. For instructions, see Update an Existing Registry File.
Create a New Registry File
There is no special setup procedure to create a new registry file. When you launch an OpenROAD application, the MainWin runtime creates a new registry file automatically, if needed. If you need to view or modify the registry information, use the MainWin supplied utility, regedit.
Note:
• Before creating a new registry file, you should remove the existing registry files and ensure that the MWREGISTRY environment variable does not exist.
• The mwregedit -new command used in previous releases is obsolete. If your registry file gets corrupted, or you need to recreate a new registry, delete the old registry file and then start the OpenROAD Workbench, or use w4glrun to run any OpenROAD application; a new registry file with system keys is recreated automatically. However, if you are using the OpenROAD Server, you must re-register it—instructions follow.
To re-register the OpenROAD Server
If you create a new registry, you must re-register the OpenROAD Server. Use the following commands: