OpenLink Multi-tier Server Side Components (Unix) for Ingres II

Aims and Intentions

This guide is intended to enable competent system administrators to install and configure OpenLink Multi-tier client side components on *nix style operating systems in a few steps as possible.

This guide does not explain any of the non-pertinent features encountered along the way. Such explanations may be found in the full documentation.

Prerequisites

• You MUST be proficient in using a Unix shell.
  
• You MUST be proficient in using a Unix editor such as vi.
  
• You MUST have installed, and available to the server components; a full installation of Ingres Net and the Name Server started.
  
• You MUST have configured an Ingres Net vNode (using netutil) if connectivity is to a remote database.

Installation

1. Log onto the machine and create a suitable OpenLink installation directory ($OPENLINK_INSTALL).
   
   
2. Copy all relevant components to $OPENLINK_INSTALL.
   
   As a bare minimum, these will include; the OpenLink Request Broker, an OpenLink Database Agent for your respective target database and finally an OpenLink license file (oplrqb.lic).
   
   
3. Install using the "install.sh" shell script --
   
   

   
    #sh install.sh
   
   

   
   
4. You should take care to enter correct information when prompted pertaining to ports, passwords, etc and ensure that you note these down for future use.
   
   
5. The installation should finish without error.
   

Licensing

OpenLink Multi-tier licensing is handled on the server side so you should place the OpenLink license file (oplrqb.lic) in the $OPENLINK_INSTALL/bin directory.

Configuration

Ingres requires a small amount of additional environmental configuration in the OpenLink Request Broker session rule book ($OPENLINK_INSTALL/bin/oplrqb.ini)--

1. Edit the file $OPENLINK_INSTALL/bin/oplrqb.ini with a suitable text editor such as vi.
   
   
   
2. Locate and edit the [Environment xxxxx] section where xxxxx matches your target database so as to ensure that any relevant environment variables pertaining you your system and target database are correct.
   NOTE: You may need to consult with your database administrator to verify these.
   
   The following example depicts an environment section for Ingress--
   
   

   
    [Environment INGRES_II]
    II_DATE_FORMAT     = US
    II_SYSTEM          = /dbs3/ingres
    ING_SET            = set lockmode session where readlock=nolock
    CURSOR_SENSITIVITY = LOW        ; Set to HIGH after loading oplrvc.sql
    LD_LIBRARY_PATH    = /dbs3/ingres/ingres/lib  ; Find shared libraries
    SHLIB_PATH         = /dbs3/ingres/ingres/lib  ; Find shared libraries
    LIBPATH            = /dbs3/ingres/ingres/lib  ; Find shared libraries
   
   

   
   
   

Start the OpenLink Request Broker

1. Starting in foreground debug mode
   It is often best to initially start the Request Broker in (f)oreground (d)ebug in order to diagnose problems--
   
   

   
    #cd $OPENLINK_INSTALL
    #. ./openlink.sh
    #oplrqb -fd
    OpenLink Request Broker
    Version 2.47 as of Tue Jan 08 2008 (Release 6.2 cvsid 00089).
    Compiled for Solaris 5.8 (sparc-sun-solaris2.8-32)
    Copyright (C) OpenLink Software.  
   
    Registered to OpenLink US Lab - INTERNAL USE ONLY
    with product serial number OPL-US-INTERNAL
    This is a 5 concurrent users license
    restricted to 5 concurrent connections
    Issued by OpenLink Software
    This license will expire on Thu May 22 01:52:13 2008 GMT
   
    oplrqb: using rulebook $OPENLINK_INSTALL/bin/oplrqb.ini
    oplrqb: bound TCP protocol to 0.0.0.0.5000
    oplrqb: request broker started by openlink
    oplrqb: spawning $OPENLINK_INSTALL/bin/w3config/www_sv www_sv +debug
    www_sv: started http://hostname:5000
    oplrqb: started persistent www_sv (pid=25896)
    oplrqb: ZeroConfig thread started
    oplrqb: ZeroConfig registration Ingres (oplussol4)
   
   

   
   The OpenLink Request Broker will continue to run, taking over the session, until <Ctrl-C> is entered which stops the Broker
   
   
2. Starting Normally
   
   

   
    #cd $OPENLINK_INSTALL
    #. ./openlink.sh
    #oplrqb
   
   

   
   
   

Testing

You are now ready to test the connection which now requires that you read the relevant quick start guide for client component on the chosen operating system.

Additional Information

1. Any changes made to $OPENLINK_INSTALL/bin/oplrqb.ini whilst the Request Broker is running will require the Request Broker to be re-initialised --
   
   

   
    #cd $OPENLINK_INSTALL
    #. ./openlink.sh
    #oplshut +reinit
   
   

   
   
2. To stop a Request Broker running normally --
   
   

   
    #cd $OPENLINK_INSTALL
    #. ./openlink.sh
    #oplshut +force