3 Installing the Oracle Clinical Database Server on Windows

This chapter describes how to install Oracle Database and the Oracle Clinical database server on a Windows computer.

Note:

Installing Oracle Clinical with Oracle Real Application Clusters (RAC) is not supported on Windows.

Section 3.1, "Set Up the opapps User Account and the oclsascr User Group"
Section 3.2, "Set Up Local Policy Security Options"
Section 3.3, "Install Oracle Database"
Section 3.4, "Install the Oracle Clinical Database Server"
Section 3.5, "Perform Post-installation Tasks"

If you are upgrading Oracle Clinical, see Chapter 11.

For database tier system requirements, see the Oracle Database 12c Release 1 (12.1.0.1) Oracle Database Installation Guide for Windows at http://docs.oracle.com/cd/E16655_01/nav/portal_11.htm.

Note:

If you install the Oracle Clinical database on Windows and use SAS, you must also install SAS on Windows; see Chapter 9, " Setting Up SAS".

Critical Patch Updates See Section 1.9, "Applying Oracle Critical Patch Updates."

Oracle Database 12.1.0.1 includes many new features including multitenancy, which allows you to create one or more pluggable databases (PDBs) contained in a single root or container database (CDB). You can install Oracle Clinical on either a pluggable database or a non-CDB database (as in 11g). For more information on multitenancy, see http://docs.oracle.com/database/121/CNCPT/cdbovrvw.htm.

Oracle recommends learning about these new features in Oracle White Paper Plug into the Cloud with Oracle Database 12c at http://www.oracle.com/technetwork/database/plug-into-cloud-wp-12c-1896100.pdf and, for more details, the Oracle® Database New Features Guide 12c Release 1 (12.1) at http://docs.oracle.com/database/121/NEWFT/toc.htm.

3.1 Set Up the opapps User Account and the oclsascr User Group

Before you install Oracle Clinical database server, create the following user group and account:

oclsascr — The group that controls access to the files Oracle Clinical generates for SAS. This user group is required if you use SAS integrated with Oracle Clinical.
opapps — The operating system account that owns Oracle Clinical and that runs the Parameterized Submission (PSUB) process. This account is required.

3.1.1 Create the oclsascr and oinstall User Groups

The oclsascr user group controls access to the files Oracle Clinical generates on the database server for SAS, including data extract files, which contain patient data.

Use Windows Administrative Tools to create a new Global Group in your Domain named oclsascr.

See the Oracle Database 12.1.0.1 Installation Guide for Windows chapter "Configuring Users, Groups and Environments for Oracle Database" at http://docs.oracle.com/database/121/NTDBI/user_grps.htm#CIHCAABC.

3.1.2 Create the opapps Account and Add It to Groups

You must create the operating system account that owns Oracle Clinical. This account also has the privileges to run the parameterized submission (PSUB) service RXCPSDPS and the PSUB Launcher (PSLAUNCH).

The user name for the account is opapps, with a home directory named opapps. For example:

Drive:\opapps

The Oracle Clinical documentation uses the variable OPA_HOME to refer to this location on an Oracle Clinical database server.

Using Windows administrative tools, assign opapps to the following user groups:

ORA_DBA
ORA_ASMDBA
OCLSASCR

Note:
Beginning in Oracle Clinical 5.0, no other accounts need to be added to the oclsascr user group.

3.2 Set Up Local Policy Security Options

In the Start menu, navigate to Administrative Tools.
Open Administrative Tools, and then Local Security Policy.
Expand the Local Policies folder and then select Security Options.
Set the following values:

Set Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers to Allow All.

Set Network security: Restrict NTLM: Incoming NTLM traffic to Allow All.

Set Network Security:Allow Local System to use Computer identity for NTLM to Enabled.

Set Network Security:Allow Local System NULL session fallback to Enabled.
Enforce the policy by opening a command prompt and entering: gpupdate/force

3.3 Install Oracle Database

This section describes the following tasks:

Section 3.3.1, "Install Oracle Database 12.1.0.1 Enterprise Edition"
Section 3.3.2, "Install Oracle Database 12.1.0.1 Examples"

3.3.1 Install Oracle Database 12.1.0.1 Enterprise Edition

To install Oracle Database 12.1.0.1:

Locate the Oracle Database software in the staging area on the database server where you downloaded it; see Section 1.5, "Downloading and Extracting the Software."
Install Oracle Database 12.1.0.1. For instructions see the readme file and the 12.1.0.1 Oracle Database Installation Guide at http://docs.oracle.com/database/121/NXDQI/toc.htm#NXDQI120.
Choose to install the Enterprise Edition.

3.3.2 Install Oracle Database 12.1.0.1 Examples

Oracle Database Examples includes the following items:

Oracle JDBC Development Drivers (required)
Oracle Database Examples (required)
Oracle Product Demonstrations (optional)

Note:

You do not need to install any of the sample schemas. They are not required for either Oracle Clinical or Oracle Thesaurus Management System. You can add them later if you change your mind.

To install Oracle Database Examples:

Extract the zip file containing Oracle Database Examples in the examples directory.
Run the following file as an administrator:

examples\setup.exe
Accept all the default values during the installation.

For more information about installing software and various Oracle product demonstrations from the Oracle Database Examples media, see the Oracle Database Examples Installation Guide at http://docs.oracle.com/database/121/EXMPL/toc.htm.

3.4 Install the Oracle Clinical Database Server

This section describes how to install and set up the Oracle Clinical database server.

The Oracle Universal Installer performs the following operations:

Creates the Oracle Clinical directory structure (see Section 3.4.4 for details)
Installs the Oracle Clinical database server
Sets permissions on the directories
Creates the environment setup files
Modifies the environment setup files
Creates the Oracle Wallet to store credentials for OCPSUB and RXC_DISC_REP
Creates the directory for storing the SAS files

3.4.1 Gather Required Information

You must have the following information ready to enter in the Installer screens:

Home Details: The ORACLE_HOME location, which is where you installed Oracle Database 12.1.0.1; for example:

drive:\app\oracle\product\12.1.0.1\dbhome
OPA Home: The directory where Oracle Clinical will be installed; Oracle recommends:

drive:\opapps
SAS View: The directory where Oracle Clinical will generate SAS views; Oracle recommends:

drive:\opapps\sas_view
Oracle Wallet location and password. The Installer uses these to create the database Wallet in the location you specify. The database Wallet stores the password for two accounts:
- The OCPSUB proxy account, which is used for database access for parameterized submission (PSUB) jobs. If your installation includes multiple databases using either replication or RAC, each database needs an OCPSUB account and its credentials are created in this Wallet on the database server during Oracle Clinical database installation.
- The RXC_DISC_REP account. If you use disconnected replication you must insert credentials for this account manually. See Section 4.4.3, "Set Up Disconnected Replication (Optional)."
  
  Note:
  If you have already created a Wallet through a previous installation of Oracle Clinical 5.0 or higher, you can continue using it instead of creating a new one by entering the location and password for the existing Wallet.

3.4.2 Install the Oracle Clinical 5.1 Database Server for Windows

Log in to the server computer using the opapps account.
In the staging area, locate the directory where you downloaded and extracted Oracle Clinical (see Section 1.5, "Downloading and Extracting the Software").
Run the following file as an administrator:

Disk1\install\setup.exe

The Installer opens to the Welcome screen.

Note:
See "Using the Silent Installer" for instructions for running the Installer as a file with pre-entered parameter values.

Note:
Although there is a button for deinstalling products on the Welcome screen, Oracle does not support using the Installer to deinstall Oracle Clinical or Oracle Clinical Remote Data Capture (RDC) Onsite.
In the Select a Product to Install page, select OC Server for Windows 5.1.0.0.x.
Follow the instructions on the installation screens, providing the information you assembled in Section 3.4.1, "Gather Required Information".

3.4.3 Review the Log Files

The log files are located at:

\Oracle\Inventory\logs

For example:

C:\Program Files\Oracle\Inventory\logs

3.4.4 Oracle Clinical Database Server Directory Structure for Windows

The Installer creates the following directory structure:

OPA_HOME
      \bin
      \xmltemp
      \oc
         \51
            \bin      (Executables)
            \dcd      (Data Collection Definition)
            \des      (Design)
            \dm       (Data Management)
            \dx       (Data Extract)
            \glib     (Global Library)
            \install  (Install and upgrade scripts)
            \log      (PSUB log files)
            \lr       (Lab Ranges)
            \patch    (Patches to Oracle Clinical)
            \pd       (Procedure Definition)
            \psub     (Parameterized Submission process)
            \release  (Server code release marker)
            \tools    (Miscellaneous tools)

Note that OPA_HOME refers to the root installation directory of the Oracle Health Sciences products, which were formerly known as Oracle Pharmaceutical Applications (OPA). You specify the root installation directory when you install the Oracle Clinical database server. Typically, you specify the path to the opapps login directory, for example, drive:\opapps.

3.5 Perform Post-installation Tasks

This section describes the tasks you perform to complete the installation of Oracle Clinical database server on a Windows computer.

3.5.1 Limit Permissions on the XMLTEMP Folder

By default, a Windows installation grants read and write privileges to the XMLTEMP database folder to everyone. To reduce security risks, you should limit permissions on the XMLTEMP folder for all Windows database server installations.

To limit permissions on the XMLTEMP folder:

Use Windows Explorer to locate the XMLTEMP folder in the OPA_HOME directory.
Right-click on the XMLTEMP folder, and then select Properties from the menu.
Click the Sharing tab, then click Advanced Sharing.
Select the Share this folder check box to enable sharing with other users on your network.
Click Permissions.
Give Read and Write (Change) permissions to user oracle.
Click OK to save your changes and close the Permissions dialog box.
Click OK to save your changes and close the Advanced Sharing dialog box.
Click Close to close the Properties dialog box.

3.5.2 Review the opa_settings.bat File

On Windows systems, configurations are defined in the opa_settings.bat file. This file contains the commands to set environment variables at startup and execution of the PSUB service.

During installation of the server code, the Installer creates the opa_settings.bat file in the following directory:

Drive:opapps\bin

See Section 1.8, "Choosing a Character Set" for important information, and see the Oracle Clinical Administrator's Guide for a list of the settings and for information about changing, adding, and verifying values.

Review the opa_settings.bat file and adjust the default values, if necessary. Note:

The db_env_setting records in opa_settings.bat define a default value for particular environment variables that are set when the application calls opa_setup. You can override the default values for all databases or for a particular database.
See Section 1.8, "Choosing a Character Set" for important information.
NLS_DATE_FORMAT must be set to DD-MON-RRRR. It is possible to override this setting for display in RDC Onsite, the Patient Data Report, and Oracle Clinical data entry, but the value in opa_settings must be DD-MON-RRRR.