6 Installing Reports Servers

This chapter describes how to install and connect Reports Servers. The Oracle Clinical 4.6 Reports Server runs on Oracle AS10gR2.

The Reports Server runs most batch reports, schedules all jobs, including PSUB jobs, and runs job sets. In addition, it creates PDF output for RDC Patient Data Reports, RDC Blank Casebook Reports, and Oracle Clinical Audit Reports.

There are two Reports Server installation types:

• Combined: a Reports Server on the same computer as a computer with a Forms Server installation.

• Standalone: a Reports Server on a computer without an installed Forms Server. You can add standalone Reports Servers to balance the workload between running Oracle Clinical and running reports jobs.

Tasks for Installing a Standalone Reports Server

The application-tier software components that support a Reports Server are the same as the Forms Server. To set up a standalone Reports Server, first perform these Forms Server installation tasks:

1. Section 5.1, "Setting Up the OPAREPS Account"

2. Section 5.2, "Installing and Patching Oracle AS10gR2 Forms and Reports Services"

3. Section 5.2.3, "Apply Oracle AS10gR2 Patch Set 3 (10.1.2.3)"

4. Section 5.2.4, "Apply Application Server Patch 7384879"

5. Section 5.2.6, "Set Resource Limits to Zero in Enterprise Manager"

6. Section 5.3, "Applying a CPU Security Update Patch"

7. Section 5.4, "Setting Up the SQL*Net Connections for Existing Databases"

   Next, continue with the tasks in this chapter:

8. Section 6.1, "Installing the Oracle Clinical 4.6 Reports Server"

9. Section 6.2, "Setting Up the Reports Server for Access and File Viewing"

10. Section 6.3, "Testing the Reports Server Installation"

11. Section 6.4, "Troubleshooting Reports Server Problems"

Tasks for Installing a Combined Forms and Reports Server

If you are installing a Reports Server on the same computer as the Forms Server, set up the Forms Server first, as described in Chapter 5. Next, continue with the tasks in this chapter:

1. Section 6.1, "Installing the Oracle Clinical 4.6 Reports Server"

2. Section 6.2, "Setting Up the Reports Server for Access and File Viewing"

3. Section 6.3, "Testing the Reports Server Installation"

4. Section 6.4, "Troubleshooting Reports Server Problems"

6.1 Installing the Oracle Clinical 4.6 Reports Server

Perform these instructions to deploy the Oracle Clinical Reports application onto the Oracle AS10gR2 installation.

Note:

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

To install the Oracle Clinical 4.6 Reports Server:

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

2. Insert Disk V17174-01 of the Oracle Clinical 4.6 and Oracle Thesaurus Management System 4.6.1 Media Pack.

3. Locate and execute the following file:

   oc\middle_tier\install\setup.exe

   The Installer opens to the Welcome screen.

4. Follow the instructions on the installation screens. For additional information on each screen, see Section 6.1.1, "Attend to the Oracle Clinical Reports Server Installation Screens."

6.1.1 Attend to the Oracle Clinical Reports Server Installation Screens

The Installer acts in two phases. In the first phase, the Installer collects information about your system. During this phase, you can move backward and forward through the screens, revising your entries. During the second phase, the Installer runs the scripts to set up the Oracle Clinical 4.6 software according to the information you provided in the first phase.

The following sections describe each Installer screen and the required action.

Welcome

Click Next.

Specify File Locations

Source  Check that the displayed default path is the location of the jar file that contains Oracle Clinical Report Server component.

Destination Enter values for the Oracle Home you created when you installed Oracle AS10gR2 Forms and Reports Services on:

• a combined Forms and Reports server

• a separate Reports Server

Click Next.

Select a Product to Install

Select OC Report Server 4.6.0.0.XX (where XX is the build number). Click Next.

OC Report Server Choose OPA home directory

Specify the directory that is the root of installations of Oracle Health Sciences products. This value must end with opapps46. Click Next.

OC Report Server Enter Report Server Name

The default value is the repcomputer_name. You can update this value. This document refers to the value you enter here as the report_server_name. If the name includes an underscore, remove it. Do not put underscores in the new value if you change it. Click Next.

OC Report Server Acrobat Reader

If installed, the Installer detects the location of the computer's Acrobat Reader installation. The Acrobat Reader is necessary for generating Patient Data Reports.

Click Next.

OC Report Server Do you want to store DCIF images locally

The Installer displays this screen only if you are installing a standalone Reports Server. The default value is Yes. Select No if you want to store DCIF images remotely. One of the following screens appears depending on your selection.

Click Next.

OC Report Server Choose the local DCIF Images Directory

If you selected Yes for the option of storing DCIF images locally, enter or browse to the path of the local directory where you want to save the DCIF images.

Click Next.

OC Report Server Enter the shared location of DCIF images

If you selected No for the option of storing DCIF images locally, enter the path of the remote directory where you want to store the DCIF images. This location is typically:

\\forms_server_name\rdc\dcif_images

Click Next.

Summary

This screen displays a navigation diagram of the target directories. (The Installer only displays oracle_home in the Destination field. It may differ from your actual directory path.) This concludes the information gathering phase of the installation process.

Click Install.

Install

The Installer copies the files onto the server and generates a log file of this installation.

End of Installation

This screen informs you whether the installation was successful.

Click Exit.

Restart the Computer

Restart the computer before continuing.

6.2 Setting Up the Reports Server for Access and File Viewing

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

6.2.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 all Reports Servers.

6.2.2 Grant OPAREPS Read and Write Access to the Reports Server Root Directory

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

To share the Reports Server root directory on Windows with the OPAREPS 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 Universal Naming Convention (UNC) for any Report 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 being 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. If you want to have longer names for user, then shorten the share name.

   
   

6.2.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 "Reports Server Tasks" in the Oracle Clinical Administrator's Guide.

6.2.4 Specify Directory Mappings for PSUB in Each Database

To set up file viewing by mapping directories in each database, see "Grant Access to Data" in the Oracle Clinical Administrator's Guide for information.

6.2.5 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.)

6.3 Testing 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. If not, review the instructions in Section 5.1.3, "Add Printers to the OPAREPS Account."

   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.

6.4 Troubleshooting Reports Server Problems

This section lists solutions to a few Reports Server problems that can arise under certain conditions. In addition, see the Reports Server Troubleshooting Guide on My Oracle Support.

Preview for Form layout editor or DCI Form Generation Fails on Standalone Reports Servers

This problem can arise if you add separate Reports Servers to an installation with no Forms Servers configured to support them. For separate Reports Servers to work, you must set up registry settings on each separate Reports Server and a Forms Server, and share directories on the Forms Server. See Section 5.6.3, "Share the RDC Directory and Set Image Browsing" for more information.

Unable to stop a Reports job

Check if this is a scheduled job. If it is, use the Oracle AS10gR2 Enterprise Manager to stop it. Navigate to Action, Report Queue Manager from any screen, or Admin, PSUB/Report Jobs, Enterprise Manager. The Report Queue Manager window opens. The instructions vary by manager version, so follow the instructions in the window to stop the job.