Set Up the Reports Server for Access and File Viewing

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.

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.

Parent topic: Set Up the Reports Server for Access and File Viewing

Share and Grant Access to Each 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:

Use Windows Explorer to select the Reports Server root directory.
Right-click on the folder and select Properties.
Click the Sharing tab.
Select Shared This Folder, and then enter a value in the Share Name field.
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.

Parent topic: Set Up the Reports Server for Access and File Viewing

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:

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/opa52/rdc/temp
```
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

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>

Map a drive to the RDC share on the application server.
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/opa52/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

Parent topic: Set Up the Reports Server for Access and File Viewing

Configure the Reports Server to Send Output to a Printer

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

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 6.0\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".

Parent topic: Set Up the Reports Server for Access and File Viewing