Server Reference Guide : Loadnrun : Before You Use Loadnrun
 
Share this page          
Before You Use Loadnrun
Pre-requisites for using Loadnrun are:
Installing the Loadnrun Client runtime on the target machine.
The Loadnrun client requires administrative rights but is packaged as a standard Microsoft Installer Package (MSI) installer. You may use Active Directory to push this runtime onto the target machine.
Connecting to an OpenROAD Server running the Loadnrun Server component.
Access to the OpenROAD Server can be provided over HTTP or SSL through a standard URL.
After meeting these requirements, any user can access OpenROAD eClient applications that are hosted on a Loadnrun Server through a Windows shortcut or simple command.
These versions of OpenROAD support the following versions of Loadnrun:
OpenROAD Version
Loadnrun Version
OpenROAD 11.1 (or higher)
Loadnrun 11.1
The Loadnrun Server is installed in the OpenROAD Server runtime. The Loadnrun Server may host Loadnrun eClient applications for any version of Loadnrun supported (11.1, or 6.2). The Loadnrun Server application image must be compatible with the version of OpenROAD that the OpenROAD Server uses.
The optional Ingres Net Client can be installed and configured when the Loadnrun Client runtime is installed. Loadnrun 11.1 install an Ingres 11.1-based Net Client. The Ingres installation code is fixed and is associated with the Loadnrun Client version:
Loadnrun Client
Ingres Net Client Installation Code
Loadnrun 11.1
XR
Loadnrun is distributed with its own installer, separate from the OpenROAD installer. You can obtain the Loadnrun installers from ESD. The Loadnrun installer is primarily used to install the Loadnrun Client runtime. The Loadnrun installer can optionally be used to install the Loadnrun Server. The OpenROAD installer has a Loadnrun feature. When the Loadnrun feature is selected during the OpenROAD installation process, the Loadnrun Server is installed.
The Loadnrun installer uses the following naming convention:
loadnrun-11.1.buildnum-win-x86-patchnum-a.zip
where buildnum corresponds to the current OpenROAD build number for that release.
OpenROAD versions 11.1 and 6.2 can be installed on the same machine concurrently. Only one OpenROAD Server can be configured per physical system. OpenROAD 11.1, and OpenROAD 6.2 Servers are capable of hosting all versions of the Loadnrun Server runtimes and can be used to deploy Loadnrun 11.1 and Loadnrun 6.2 applications.
If those using the client system desire to use multiple versions of Loadnrun applications, the corresponding Loadnrun Client runtime must be installed. This technique can be used as a migration mechanism to a new release. The existing versions of customer applications and the OpenROAD runtime do not have to be changed to implement a new version of OpenROAD or new versions of customer applications.