Set Up the Reports Server for Access and File Viewing

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

Create the Reports Server Root Directory

If your Oracle Clinical environment includes any standalone Reports Servers and/or File Servers, select the single computer where you will locate your Reports Server root directory. The directory can reside on the Forms Server, on any of the Reports Serves, or any other computer. Otherwise, you will locate the Reports Server root directory on the single computer comprising your entire Oracle Clinical installation.

  1. Create the Reports Server Root directory, making sure it is accessible by the user that started up the auto process; see Set Up Automatic Startup.

Share and Grant Access to Each Reports Server Root Directory

If your Oracle Clinical environment includes multiple servers, you must make your Report Server root directory shareable on every server (Forms Server and Reports Server). Otherwise, all of your Oracle Clinical components and your Report Server root directory reside on a single computer, and you can skip the following steps.

  1. Share the Reports Server root directory:
    1. Log on to Windows with an administrator account.
    2. Use Windows Explorer to select the Reports Server root directory.
    3. Right-click on the folder, and select Properties.
    4. Click the Sharing tab.
    5. Select Shared This Folder, and then enter a value in the Share Name field.
    6. Click OK to save your changes.
  2. On each Forms and Reports Server, map a drive to the shared directory.
    1. You must use the same drive letter in each server's mapping, for example 't'. This allows for a unified specification of the output directory in Oracle Clinical.
    2. Even if the root directory is local to the Report Server, you must map a drive to allow for unified specification.

If you have already completed the Oracle Clinical Report Server installation and did not specify the correct Report Server root directory path, you can correct this by editing the rwserver.conf file, directly, as follows:

<folderAccess><read>%OPA_HOME%\oc;%OPA_HOME%\*;%REPORTS_LOG_DIR%\*</read><write>%OPA_HOME%\oc;%OPA_HOME%\*;%REPORTS_LOG_DIR%\*</write></folderAccess>

Configure the Reports Server and Forms Server for DCI Form Generation

Both the Reports Server and the Oracle Clinical application server must have read/write access to the directory (\rdc\temp) on the application server used to write temporary files during the DCI form generation process.

If you have any standalone Reports Servers, they must also have access to this directory.

On the Oracle Clinical (Forms) Server:

  1. Confirm that the OUI has the specified values for the registry settings OPA_XMLTEMP_UNC and OPA_XMLTEMP_HTTP. During the installation, if you correctly indicated that there is a standalone report server, the value of the key(s) is set to:
    • OPA_XMLTEMP_UNC:
      C:\opapps52\html\rdc\temp
      
    • OPA_XMLTEMP_HTTP:
      https://<serverName>:port/opa54/rdc/temp
      
  2. To provide access to the remote Report Server, share the directory with the share name "RDC", providing read/write privileges to the domain/account on the report server.

On the Reports Server used in DCI Form Generation

  1. By default, OUI will have updated RWSERVER.conf, specifying a value of %OPA_HOME%\oc;%OPA_HOME%\*;%REPORTS_LOG_DIR%\* under folder access.

    For example:

    <folderAccess>
    <read>%OPA_HOME%\oc;%OPA_HOME%\*;%REPORTS_LOG_DIR%\*</read>
    <write>%OPA_HOME%\oc;%OPA_HOME%\*;%REPORTS_LOG_DIR%\*</write>
    </folderAccess>
    
  2. Map a drive to the RDC share on the application server.
  3. Update the registry values. For example:
    • OPA_XMLTEMP_UNC:
      z:\rdc\temp
      

      The Z drive is mapped to \\SharedAPPSERVERNAME\OPA_HOME\html.

    • OPA_XMLTEMP_HTTP:
      https://servername(same as Z drive):port/opa54/rdc/temp
      

If the only report server that you use to generate DCI forms co-exists on the same computer with the application server, there is no need to share the xmltemp directory and the path specification can be a simple local directory name, such as,

C:\opa_home\html\rdc\temp

Configure the Reports Server to Send Output to a Printer

If you run the PDR, and you send the output directly to a printer:

  1. Set value for the RDC_PDF_PRINT_TOOL key.

    The value assigned to the RDC_PDF_PRINT_TOOL key determines the location of the Adobe Acrobat or Reader executable, which allows users to run PDF patient data reports with "PRINTER" specified as the output type. This value must be in the form:

    "<acrobat-reader_path>" /t
    

    Note that the double-quotation marks around the path and the "/t" switch are required. A typical example of a value is:

    "C:\Program Files\Adobe\Acrobat <version>\Acrobat\Acrobat.exe" /t
    

In addition to setting this key correctly, ensure that the Adobe Acrobat or Reader application is running on the Reports Server prior to users initiating this type of report job, that is, a job that specifies the output type as "PRINTER".