Set Up Client Computers

There are two types of client setups depending on the role of the Oracle LSH user:

For information on supported operating systems and browsers for the client, see My Oracle Support article 180430.1, Oracle Life Sciences Applications Supported Technology Stacks.

Consumers and Administrators

Oracle LSH Consumers, who retrieve information in the form of reports and visualizations, and Oracle LSH Administrators, who perform administrative tasks within Oracle LSH, require the following on their personal computers:

  • A Web browser (one of those supported by Oracle Applications)

  • Java Virtual Machine (JVM)

Consumers require JVM if they are using Oracle Discoverer Plus to create data visualizations.

Administrators require either JInitiator or JVM to use any of the Oracle Forms screens related to security, to run the post-installation jobs or to set up user accounts or functional roles.

The first time a user opens one of the Oracle Forms screens, the user is prompted to download and install JVM if it is not already installed.

Note:

If you are currently using JInitiator, you can continue to do so.

Application Developers

An Oracle LSH Application Developer (also called a Definer) writes source code on his or her personal computer in an integrated development environment (IDE) and then uploads the source code file to Oracle LSH.

An Oracle LSH Definer client requires:

  • A Web browser (one of those supported by Oracle Applications)

  • Java Virtual Machine (JVM)

  • A Zip utility: 7-Zip or WinZip Pro 11.2 SR-1, WinZip 8.1, or any other WinZip version that includes the WZUNZIP.exe

This section contains the following topics:

Install the Client Plug-In

Oracle LSH files contained in CdrClientInstall.zip handle the integration of the IDEs with Oracle LSH.

System Administrator Tasks

To prepare these files for installation by developers, do the following:

  1. Download CdrClientInstall.zip from $CDR_TOP/plugin/sas.

  2. Unzip CdrClientInstall.zip. One of the files unzipped is cdrconfig.xml.

  3. (Optional) Edit cdrconfig.xml to add a directory path for each IDE developers may use, including the IDEs mentioned in Integrating Other Systems. and any other IDEs that your company is using with Oracle LSH, either by buying a third party adapter or developing your own adapter.

    If you are using 7-Zip instead of WinZip, follow instructions in Section 5.17.2.1.3, "Enabling Using 7-Zip".

  4. Write the unzipped contents of CdrClientInstall.zip to a CD-ROM.

  5. Give the CD-ROM to each Oracle LSH Definer who will use an IDE, with instructions for where to install the IDE software so that the directory paths you entered in cdrconfig.xml are correct.

    Note:

    Alternatively, do not edit cdrconfig.xml before writing it to the CD-ROM and tell each Definer to edit his or her own copy.

Definer Task

On each Definer's personal computer, load the CD-ROM that contains the unzipped files. InstallShield automatically runs setup.exe, which loads cdrconfig.xml and cdrclient.exe to a location the Definer specifies on his or her local computer. The default location is ProgramFilesDir\oracle\cdr where ProgramFilesDir is the registry entry for the value name ProgramFilesDir. If the specified location does not exist, the InstallShield creates it.

In addition, it sets the location for the CDR Work directory. By default this location is %USERPROFILE%/Application Data/CDR. Oracle recommends using this setting if you are installing the client IDE on a server for access by multiple users. It creates a separate work space for each user so they do not overwrite each other's files.

Enabling Using 7-Zip

If you want to use 7-Zip instead of WinZip, do one of the following:

Edit cdrconfig.xml to Use 7-Zip If WinZip Is Not Installed

Add the following code:

REM ------------------------------------------- 
REM wzunzip 
REM ------------------------------------------- 
if  exist "%ProgramFiles%\WinZip\wzunzip.exe"   
"%ProgramFiles%\WinZip\wzunzip.exe" -yo %1 %2 %3 
if  not exist "%ProgramFiles%\WinZip\wzunzip.exe"  goto 7zip 
goto end 
 
:7zip 
REM ------------------------------------------- 
REM 7-zip 
REM ------------------------------------------- 
if  exist "%ProgramFiles%\7-Zip\7z.exe"  "%ProgramFiles%\7-Zip\7z.exe" x -y 
%3 
if  not exist "%ProgramFiles%\7-Zip\7z.exe" goto errormsg 
goto end 
  
:errormsg 
msg "%username%" Either wzunzip nor 7z could be found. No Launch possible. 
  
goto end 
 
:end 

Create a .bat File and Edit cdrconfig.xml

  1. Create a file called wzunzip.bat with the following contents:

    "C:\Program Files\7-Zip\7z" x %3

  2. Add the path to the wzunzip.bat to the CDRCONFIG.xml file.

Edit cdrconfig.xml When 7-Zip is the Only Option

Change this line in CDRCONFIG file:

<USER_DEFINE NAME="WINZIPEXE" VALUE="&quot;C:\Program Files\ WinZip\wzunzip.exe&quot;"/>

to:

<USER_DEFINE NAME="WINZIPEXE" VALUE="&quot;C:\Program Files\ 7-Zip\7z.exe&quot;"/>

Set NLS_LANG to UTF8

Check and set your NLS_LANG environment variable:

  1. Right-click the My Computer icon on your desktop, then click Properties.

  2. Click the Advanced tab, then click Environment Variables.

  3. In User Variables and System Variables, check if there is a variable named NLS_LANG.

  4. If there is an NLS_LANG variable, highlight it and click Edit.

  5. Set the variable value to UTF8; for example: AMERICAN_AMERICA.UTF8

If you do not have the NLS_LANG environment variable, change your registry settings:

  1. Click Start, then Run.
  2. In the Run window, enter regedit and click OK.
  3. Locate one of the following registry key entries:
    • HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE

    • HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEx

      where x is the unique number identifying the Oracle home

  4. Add a new key named NLS_LANG with a value including UTF8; for example:
    NLS_LANG=AMERICAN_AMERICA.UTF8

Set Up Development Environments

Oracle LSH supports several integrated development environments (IDEs). For information on configuring these for use with Oracle LSH, see:

For information on setting up the Oracle BI Administration Tool, see the Oracle Life Sciences Data Hub System Administrator's Guide.