Install OpenROAD into an Existing Ingres Installation
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.
Install libx11 and libxext
OpenROAD needs X11 to be installed. For example, under RedHat Linux, issue the following command:
yum install libX11 libXext
Installation Command Syntax
The installation command uses the following syntax:
./or11install.sh -f filename.tar
–l prompt | accept
-mtmp path
-no_xml_lib
-r N | Y
-t ordev | orrun
-licdir path
-mailhost name_mail_server
-mailport mail_port_number
-email list_of_emails1[,list_of_emails2...]
-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
-licdir
Path where the license.xml file resides
Default: The value will be read from config.dat. If it does not exist in config.dat, you will be prompted for the value.
-mailhost
Mail Server Host to receive emails about license expiration.
Default: The value will be read from config.dat. If it does not exist in config.dat, you will be prompted for the value.
-mailport
Port of the Mail Server to receive emails about license expiration.
Default: The value will be read from config.dat. If it does not exist in config.dat, you will be prompted for the value.
-email
Email addresses to receive emails about license expiration.
Default: The value will be gotten from config.dat. If it does not exist in config.dat, you will be prompted for the value.
Example—installation command:
The following command starts the installation, specifies that OpenROAD Development be installed and that the license file be accepted automatically, specifies a path for temporary MainWin files, does not register the OpenROAD Server components.
./or11install.sh -t ordev -f or11.tar -l accept -mtmp path -r N
Note: If the Actian License MAILHOST, MAILPORT, and EMAIL configurations are not set during installation, then you may learn how to configure them post-installation from
Licensing.
Start the Installation
You install OpenROAD using or11install.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 or11.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 or11.tar or11install.sh
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:
For C shell:
%setenv USERNAME host_login
%setenv COMPUTERNAME host_name
%w4glrun asreg.img
For Bourne shell:
$USERNAME=host_login
$COMPUTERNAME=host_name
$export USERNAME
$export COMPUTERNAME
$w4glrun asreg.img
host_login
Specifies a valid host login, such as “ingres”
host_name
Specifies the name of your UNIX or Linux machine
If the registry did not previously exist, these commands create a new registry file in $HOME/.mw/hkcu.bin and populate it with system keys and the appropriate OpenROAD Server keys.
Upgrade an Existing Registry File from OpenROAD 4.1 or 4.1 Service Pack 1
If you are upgrading from OpenROAD 4.1 or 4.1 SP1, you must upgrade the registry file to complete the installation. You must run the following two upgrade utilities:
mwregconv
Converts your existing registry file to a new format
ru41sp2.img
Updates existing OpenROAD Server keys
Note: Before running the upgrade utilities, ensure that your OpenROAD runtime environment is set up correctly.
To update the default registry file
Run the following upgrade procedures:
mwregconv $HOME/windows/registry.bin
w4glrun ru41sp2.img
To upgrade a user-defined registry file
Run the following upgrade procedures:
mwregconv /full_path/existing_registry_file_name
w4glrun ru41sp2.img
full_path
Specifies the full path to the existing registry file
existing_registry_file_name
Specifies the name of the existing registry file
Note: Do not set the MWREGISTRY environment variable to the old registry file name because it is passed to mwregconv as a command line parameter.
Upgrade an Existing Registry File from OpenROAD 4.1 Service Pack 2
If you are upgrading from OpenROAD 4.1 SP2, you must upgrade the registry file to complete the installation using the upgrade utility, orregconv.
The orregconv utility is a shell script that exports the OpenROAD Server root keys from an existing registry file and imports them into the new registry file. If necessary, you can modify this script to export and import other registry keys. Orregconv is located in the $II_SYSTEM/ingres/bin directory.
Note: Before running the upgrade utility, ensure that your OpenROAD runtime environment is set up correctly.
To upgrade the default registry file
Run the following upgrade procedure:
orregconv $HOME/windows/hklm_$MWOS.bin:$HOME/windows/hkcu.bin
To upgrade a user-defined registry file
Run the following upgrade procedure:
orregconv /full_path/existing_registry_name:$HOME/windows/hkcu.bin
full_path
Specifies the full path to the existing registry file
existing_registry_file_name
Specifies the name of the existing registry file
Note: Do not set the MWREGISTRY environment variable to the old registry file name because it is passed to orregconv as a command line parameter.