OpenLink Multi-tier Server Side Components (Windows) for Ingres

Aims and Intentions

This guide is intended to enable competent system administrators to install and configure OpenLink Multi-tier client side components on Windows 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 Command Prompt window (for preferred testing purposes).
  • There MUST be installation of either Ingres (full) or Ingres Net present on the machine and you will MUST know where this installation resides.
  • If you are only utilising Ingres Net to establish a remote connection then you MUST have a preconfigured Ingres vNode.
    This should have neen configured and connectivity tested using the "Ingres Networking Utility".
  • You MUST ensure that both the Ingres Name server and Ingres Net server are started.

Installation

  1. Copy all relevant installation components to a suitable starting directory such as your Desktop.

    As a bare minimum, these will include; the OpenLink Request Broker, an OpenLink Database Agent for Ingres and finally an OpenLink license file (oplrqb.lic).
  2. Install the OpenLink Request Broker which will prompt for the license file

  3. Install the OpenLink Database Agent for Ingres
  4. All installers should finish without error.

Licensing

OpenLink Multi-tier licensing is handled on the server side so you should have provided the location of the license file (oplrqb.lic) during the installation of the Request Broker component.

If you chose to skip that part then you should now copy the license file to c:\Program Files\OpenLinkSoftware\UDA\bin

Configuration

Ingres requires a small amount of additional environmental configuration in the OpenLink Request Broker session rule book (c:\Program Files\OpenLink Software\UDA\bin\oplrqb.ini)--
  1. Edit the file c:\Program Files\OpenLink Software\UDA\bin\oplrqb.ini with a suitable text editor such as Wordpad.


  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 Ingres II-- 


     [Environment INGRES_II]
 II_DATE_FORMAT     = US
 II_SYSTEM          = C:\Program Files\Ingres
 ING_SET            = set lockmode session where readlock=nolock
 CURSOR_SENSITIVITY = LOW        ; Set to HIGH after loading oplrvc.sql
 Path               = C:\Program Files\Ingres\IngresII\ingres\bin;C:\WINNT\SYSTEM32  ; 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--

    In order to do this you must stop the "OpenLink Request Broker" service.

    Now, open a "Command Prompt" window and -- 


     #cd c:\Program Files\OpenLink Software\UDA\bin
 #oplrqb -fd
 OpenLink Request Broker
 Version 2.47 as of Wed Mar 05 2008 (Release 6.2 cvsid 00089)
 Compiled for Win32 (x86)
 Copyright (C) OpenLink Software  

 Registered to OpenLink US Lab - INTERNAL USE ONLY
 with product serial number OPL-US-INTERNAL
 This is a 500 concurrent users license
 restricted to 500 concurrent connections
 Issued by OpenLink Software
 This license will expire on Thu May 22 01:52:13 2008 GMT

 using rulebook c:\Program Files\OpenLink Software\UDA\bin\oplrqb.ini
 bound TCP protocol to 0.0.0.0.5000
 created job for controlling agents
 request broker started by garry
 spawning "C:\Program Files\OpenLink Software\UDA\bin\www_sv.exe" +debug +internal 2472
 started persistent www_sv (pid=3356)

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

  2. Starting Normally

    To start the OpenLink Request Broker normally, simply restart the "OpenLink Request Broker" service.

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 and have the OpenLink Request Broker running in (f)oreground (d)ebug mode as detailed above.

Additional Information

  1. Any changes made to c:\Program Files\OpenLink Software\UDA\bin\oplrqb.ini whilst the Request Broker is running will require the Request Broker to be re-initialised --

    Open a "Command Prompt" window and - 


     #cd c:\Program Files\OpenLink Software\UDA\bin
 #oplshut +reinit

Referenced by...