Server Reference Guide : Loadnrun : Getting Started with Loadnrun : Set Up the Loadnrun Client
 
Share this page                  
Set Up the Loadnrun Client
Before you begin setup of the Loadnrun Client, ensure that you have URL access to the OpenROAD Server HTTP Gateway. For example:
http://hostname/openroad/
Entering this URL into a browser should display a web page containing the following text:
Java Servlet Gatekeeper:
The following URL is typically used:
http://hostname:8080/openroad
A page with the following message should be displayed if the Gatekeeper is working:
OpenROAD HTTP Gatekeeper Servlet here.
This connection is not secure. IP address:
  fe99:9:9:9:a9c9:b999:9999:fd9b%99
Authentication mechanism: null
The ASP.NET Gatekeeper URL is typically http://hostname/openroad/ and the Java Gatekeeper URL is typically http://hostname:8080/openroad/. Each Gatekeeper provides the same functionality and accesses the same OpenROAD Server.
The following examples use the ASP.NET URL. The Java Servlet URL could be substituted with no change in behavior.
To install the Loadnrun 6.2 Client runtime on a client machine
1. Obtain the Loadnrun 6.2 installer from http://esd.actian.com. Typically it is distributed as a Zip file with the following name:
openroad-6.20.buildnum-win-x86-loadnrun-a.zip
This file contains all necessary components.
2. Unzip this file into a directory.
3. Change to the directory created in the previous step.
4. Launch the setup.exe command. You can do this one of two ways:
• Windows Explorer: Double-click on the setup.exe file.
• Command Prompt: Enter the following command:
setup.exe
You can use the following command to launch the installer with traces turned on:
setup.exe -Tyes -LC:\temp\loadnrun_install.log -/appflags DEBUG=YES LOGFILE=YES
Launching setup.exe creates two files:
File Installed
Description
C:\temp\loadnrun_install.log
The setup.exe log file
%userprofile%\setup_orinstall.log
The MSIEXEC log file
The MSIEXEC log file typically is not used unless there is an installer error. These two files will be needed by Actian Support to diagnose any installer issues.
Launching setup.exe opens a frame where you specify parameters.
5. Specify parameters in the following four sections:
Section
Parameter
Description
Customization
Appname
Enter the name of a user-provided eClient application that Loadnrun will launch as the default application. This is typically a user-written OpenROAD eClient application that you can use to launch other Loadnrun eClient applications.
If you have no default application, simply enter the following string:
launcher
This will be used if a Default Appname Shortcut option is required.
 
Gateway URL
Enter the URL used to verify access to the OpenROAD Gatekeeper. For example:
http://hostname/openroad/
This URL will be used by the client to access the OpenROAD Server.
 
Server Suffix
Enter the value of a subdirectory used to host the eClient applications that will be accessed by Loadnrun to download to the local machine. The default for your OpenROAD version is one of the following:
• 62demo
• 60demo
• 51demo
Note:  This suffix value has nothing to do with the version of the Loadnrun Client running on the local system. The Loadnrun application hosted on the Loadnrun Server determines which Loadnrun Client runtime it will use. This is determined on an application-by-application basis and can be configured in the install4gl.txt file for the application on the Loadnrun Server.
Client Operations
eClient Runtime
Installs the Loadnrun eClient runtime. Specify Yes.
 
Launcher Shortcut
Installs the Loadnrun Simple Launcher shortcut. If specified, the Launcher Loadnrun eClient application will be downloaded and started. Specify Yes.
 
Default Appname Shortcut
Installs the Default Appname Shortcut. If specified, a user eClient application (specified in the Appname option) will have a shortcut created that uses Loadnrun to launch that application. Specify as No if no user application is being used.
 
Install Stand-Alone Net Client
Specifies that the Loadnrun Net Client should be installed and configured. This enables Loadnrun to support client/server OpenROAD deployments using a prepackaged Ingres Net client.
If the connect_example1, connect_example2, or qt (Query Tool) demo applications will be used, specify this as Yes.
 
Demo Shortcuts
The Simple Launcher application can be used to launch the demo applications provided as samples. If this option is selected, shortcuts will be created to launch these Loadnrun demo applications directly:
• Comtestclient
• connect_example1
• connect_example2
• httptest
• Intertask1
• Intertask2
• Jigfall
• Minesweeper
• qt
If this option is specified as Yes, the shortcuts will be created. If specified as No, no shortcuts to launch these demo applications will be created.
Server Options
Sample Demos
Used by the Loadnrun Server. Specify as Yes.
 
Demo Source
Used by the Loadnrun Server. Specify as Yes.
Common Options
Product Uninstall Shortcut
Creates a product uninstallation shortcut.
Specify as Yes.
After setting all of these options to their required values, click Next.
If you selected the Install S/A Net Client option, the Input Net Client Configuration Parameters frame is displayed. If you did not select the Install S/A Net Client option, this frame is not displayed.
6. (Optional) Specify S/A Net Client installation parameters:
Ingres Installation Code (II_INSTALLATION)
Indicates the Ingres installation code for the S/A Net Client. For Loadnrun 6.2, it has a value of XP. This cannot be modified.
Ingres Character Set (II_CHARSET)
Specifies the Ingres character set. It can be set to any valid Ingres character set value such as UTF8 or ISO88591.
Default: WIN1252
Ingres Terminal (TERM_INGRES)
Specifies the TERM_INGRES environment variable, which is used primarily to control the behavior of tools such as NETUTIL.
Date Format (II_DATE_FORMAT)
Set this to any valid Ingres date format value.
Money Format (II_MONEY FORMAT)
Set this to any valid money format value.
Decimal Character (II_DECIMAL)
Set this to any valid decimal character value.
After setting all of these options to their required values, click Next. This launches the MSI installer. The MSI installer will complete the installation of the Loadnrun Client.
You must set up the Loadnrun Server before the Loadnrun Client can be used. See Set Up the Loadnrun Server.
For information about testing the Loadnrun Client, see Test the Loadnrun Client or Server.