12/17

7 Installing the Oracle Clinical Reports Server

This chapter includes:

• Section 7.1, "Gather Required Information"

• Section 7.2, "Restart Computer and Stop Servers"

• Section 7.3, "Start the WebLogic FRDomain Admin Server"

• Section 7.4, "Install the Oracle Clinical Reports Server"

• Section 7.5, "Set Up the Reports Server for Access and File Viewing"

• Section 7.6, "Add the Reports Server to the Database Reference Codelist"

• Section 7.7, "Test the Reports Server Installation"

• Section 7.8, "Set Up Automatic Startup of Services"

You can install Forms Servers and Reports Servers to suit your needs. If you choose to have Reports Servers on computers that do not have a Forms Server installation, you must configure both computers to share a directory on the Forms Server computer.

Note:

To ensure high availability of the Reports Server, you can set up and use more than one Reports Server on a subnet and they can access each other. For more information see the Oracle Clinical Administrator's Guide.

The Oracle Application Server technology stack and Oracle Clinical Front End must be installed before you install the Oracle Clinical Reports Server. See Chapter 5, "Installing and Configuring the Application Tier" for installation instructions.

7.1 Gather Required Information

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

• A name for the Oracle Home location on your application server and its full path; for example:

  C:\oracle\Middleware\Oracle_FRHome1 (you can browse for this in the Installer screen)

• Your OPA Home directory; for example:

  C:\opapps51

• WebLogic username and password

• Report Server name

• Adobe Reader location; for example:

  C:\Program Files (x86)\Adobe\Reader 11.0\Reader\ AcroRd32.exe

7.2 Restart Computer and Stop Servers

If you are installing the Oracle Clinical Report Server immediately after the Oracle Clinical Front End and have already stopped the services and servers, you can skip this step.

1. Restart the computer.

2. In the Windows Services control panel, find Oracle Node Manager service and stop it.

3. Stop the Forms Server. From the Windows Start menu, go to All Programs, then Oracle Classic asinst_1, then Forms, then Stop WLS_FORMS.

4. Stop the Reports Server. From the Windows Start menu, go to All Programs, then Oracle Classic asinst_1, then Reports, then Stop WLS_REPORTS.

   Note:

   TheWebLogic FRDomain Admin Server must be running when you install the Reports Server. This is different from the Front End installation.

7.3 Start the WebLogic FRDomain Admin Server

Make sure that the WebLogic FRDomain Admin Server is running. Do one of the following.

• Go to the Start menu, then All Programs, then Oracle Classic asinst_1, then Start Admin Server.

• Go to the Start menu, then All Programs, then Oracle Weblogic, then User Projects, then FRDomain, then Start Admin Server Weblogic Server Domain.

7.4 Install the Oracle Clinical Reports Server

Follow these instructions to deploy the Oracle Clinical Reports Server onto the application tier installation.

Note:

If you run Patient Data Reports from a Reports Server, install Acrobat Reader before installing the Oracle Clinical Reports Server. The Installer detects the Reader's location and automatically configures the registry.

To install the Oracle Clinical Reports Server components:

1. Log in as a user with system administrator privileges.

2. Navigate to the location where you downloaded and extracted the software in Section 1.5, "Downloading and Extracting the Software".

3. 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.

4. Select a Product to Install: Select Oracle Clinical Report Server 5.1.0.0.x.

5. Follow the instructions on the installation screens.

6. Follow instructions on screen, entering the information you have gathered; see Section 7.1, "Gather Required Information".

7. Summary: The Summary screen provides information about the global settings, languages, space requirements, and products for this installation.

   Review the installation details to verify that they are correct. To revisit earlier installation screens and make changes, click Back.

   When you are ready to continue, click Install.

8. Install: The Installer copies the files onto the server, completes the setup and configuration tasks, and generates a log file of this installation.

   In addition, the Install screen displays the location of the log file that records the results of the installation activities for this session. Make a note of this information so you can view the log file after the installation.

9. End of Installation: The End of Installation screen reports whether the installation was successful. Please check the install logs if any errors are displayed.

   When you have finished reviewing the installation information, click Exit.

7.4.1 Restart the Computer

To ensure that all configuration changes are initialized, you must restart the computer before you continue with the next task in the installation process.

7.5 Set Up the Reports Server for Access and File Viewing

Perform these Reports Server file viewing tasks once for each Oracle Clinical location.

7.5.1 Create the Reports Server Root Directory

Create a directory on a computer for report and log files. The Reports Server root directory can reside on the Forms Server, on any of the Reports Servers, or any other computer. The directory must be accessible by the user that started up the auto process; see Section 6.9, "Setting Up Automatic Startup".

7.5.2 Share and Grant Access to the Reports Server Root Directory

This step is not required if you are installing the application tier on a single computer.

Make the Reports Server UNC sharable, and grant the administrator account read and write access to this directory.

To share the Reports Server root directory on Windows with the administrator account:

1. Use Windows Explorer to select the Reports Server root directory.

2. Right-click on the folder and select Properties.

3. Click the Sharing tab.

4. Select Shared This Folder, and then enter a value in the Share Name field.

5. Click OK to save your changes.

   
   

   Tip: The Microsoft Windows Universal Naming Convention (UNC) for any Reports Server log directory cannot exceed 35 characters. The UNC syntax is: \\computer\sharename\subdirectory For example, if the computer name is oclfsrv1, and the share name is opareportout, and the report log is stored in a subdirectory user under this shared directory, then the UNC is: \\oclfsrv1\opareportout\user This works as long as user does not exceed eight characters. To have longer names for user, shorten the share name.

   
   

7.5.3 Create Reports Server Log Directories for Each User

For each Oracle Clinical database account, create the Reports Server log directory for the user. See the Oracle Clinical Administrator's Guide for information.

7.5.4 Configure the Reports Server for DCI Forms and PDRs

If you are using DCI Forms or Patient Data Reports (PDRs) on this computer, there are more configuration tasks you must perform. See the Oracle Clinical Administrator's Guide for more information. (In particular, if you run the PDR, and you send the output directly to a printer, be sure to set RDC_PDF_PRINT_TOOL according to the instructions in Appendix A of the Oracle Clinical Administrator's Guide.)

7.6 Add the Reports Server to the Database Reference Codelist

For each Reports Server that you install, you must edit reference codelists in Oracle Clinical to specify the values for the Reports Server.

To set the Reports Server values:

1. Start Oracle Clinical.

2. Navigate to Admin, Reference Codelist, and then Local Codelist to open the Maintain Reference Codelists form.

3. Query for REPORT_SERVER in the Name field.

4. Complete the Short Value and Long Value fields as follows:

   • For each Short Value listed in Table 7-1, enter in the Long Value field the connection string of the Reports Server that you want to use as the default for the specified function.

   • For each additional, non-default Reports Servers, add a row to the reference codelist. Specify a unique name in the Short Value field and the connection string in the Long Value field.

     Table 7-1 REPORT_SERVER Local Reference Codelist Values

     Short Value	Enter in Long Value Field
     REPORT_SERVER	The connection string for the Reports Server you want to use as the default for Oracle Reports.
     JOB_SET_SERVER	The connection string for the Reports Server you want to use as the default for job sets.
     PSUB_SCHEDULER	The connection string for the Reports Server you want to use as the default for PSUB jobs.

     
     

5. Click Save.

7.7 Test the Reports Server Installation

To test that the Reports Server can create printouts and files:

1. Start Oracle Clinical.

2. Navigate to Admin, Admin Reports, and then Reference Codelist. The Report Reference Codelist submission screen opens.

3. Click the Reference Codelist Name field, and enter OCL_STATE.

4. Print the report:

   1. Click the Job Details button.

   2. Change the Output Type to PRINTER.

   3. Examine the printer's path to see if it is correct.

   4. Click Submit Job. You receive a status prompt. Close the prompt to return to the Submission screen.

   5. Click Job Status to check the progress of your print job. Look for the printout from your printer.

5. Print the report to file:

   1. Return to the Report Reference Codelist submission screen.

   2. Click the Reference Codelist Name field, and enter OCL_STATE.

   3. Click Job Details.

   4. Change the Output Type to FILE.

   5. Click Submit Job. The system displays a status prompt. Close the prompt to return to the Submission screen.

   6. Click Job Status.

   7. Check its status in the Execution Status field.

   8. Click View Output. The system displays a path location prompt.

   9. Click OK. The Report Server processes the file and converts it to the selected format. If successful, the file then opens in a separate window.

7.8 Set Up Automatic Startup of Services

Oracle recommends setting up the server so that the Node Manager automatically restarts services when necessary. If you are installing this on a machine with the Oracle Clinical Front End, you will have done this as part of executing Section 6.9, "Setting Up Automatic Startup".

• If this is a standalone reports server, follow the same instructions except, in script autostartfrdomainscript.py located in opa_home\config, comment out the following line:

  start ('WLS_FORMS')

• If you are not installing TMS, also comment out the following line in script autostartopadomainscript.py located in opa_home\config:

  domainName='OPADomain' domainDir='your_middleware_home/USER_P~1/domains/OPADomain' nmConnect(userConfigFile=configfile, userKeyFile=keyfile, nmPort=port, domainName=domainName,domainDir=domainDir,nmType='ssl') nmStart('Admin Server') connect(userConfigFile=configfile, userKeyFile=keyfile) nmStart('OpaServer1')