11 Setting Up File Viewing

You need to set up file viewing in Oracle Clinical so that users can:

• View report outputs and log files

• View log files from Parameterized Submission (PSUB) batch jobs

• View HTML previews of DCI Forms Layout definitions

This section contains the following topics:

• File Viewing Setup Overview

• Editing formsweb.cfg to Change File Viewing Protocol

• Setting Directory Mappings

• Setting Up Image Viewing for DCI and DCM Form Layouts HTML Preview Feature

File Viewing Setup Overview

To set up file viewing:

1. Install the Oracle RDBMS and specify the file viewing protocol you want to use: FTP, HTTP, HTTPS, or UNC; instructions are in the Oracle Clinical Installation Guide.

   • If your system uses a UNIX Database Server, we recommend that you choose FTP file viewing protocol. However, if your administration policies do not permit FTP use in your system, we recommend you choose HTTP.

   • If your system uses a Windows Database Server, we recommend that you choose the UNC file viewing protocol.

2. Complete the server setup required for the protocol you use:

   • For UNC, set up a shared directory on the database server that is accessible from your WAN.

   • For FTP, set up an FTP server on your database server.

   • For HTTP, setup an HTTP server on the database server.

3. Install the Oracle Clinical Reports Server and create a Reports Server root directory; instructions are in the Oracle Clinical Installation Guide.

4. Create one or more log directories for report outputs; see "Setting Up a Report Server Log Directory".

5. Create one or more log directories for batch job (PSUB) outputs; see "Creating a PSUB Log Directory".

   For the UNC or HTTP file viewing protocol, setup the correct permissions. Refer to "Creating a PSUB Log Directory".

6. Specify directory mappings in the "Setting Directory Mappings" section .

7. If you use a different file viewing protocol than the default for the operating system, modify the formsweb.cfg file to match the type of file viewing protocol you use. See "Editing formsweb.cfg to Change File Viewing Protocol" for information.

Editing formsweb.cfg to Change File Viewing Protocol

If you use a different file viewing protocol than the default for the operating system, modify the formsweb.cfg file to match the type of file viewing protocol you use.

This file is located in the ORACLE_AS10GR2MT_HOME\forms\server\ directory.

For example, to change configure the application server for a change from FTP to HTTP file viewing protocol, modify the opa_file_viewing parameter in formsweb.cfg from:

opa_file_viewing=PSUBMAP=FTP RSMAP=UNC

to:

opa_file_viewing=PSUBMAP=HTTP RSMAP=UNC

Note:

The RSMAP setting does not affect file viewing.

Setting Directory Mappings

Use this form to map the PSUB log directory specified for each user to a format that can be used to enable the user to view PSUB output files on the database server. This tasks is required only if you are using HTTP or HTTPS. It is not necessary if you are using UNC or FTP.

To map file viewing specifications:

1. Navigate to Admin, then Directory Mappings, then Directory Mappings. The system opens the Maintain Directory Mappings window.

2. Execute Query (F8), to see all records.

3. In the Mapping Code field select the file viewing protocol you are using on the database server.

   (You can add or remove values for this list of values in the MAPPING_TYPE installation reference codelist.)

4. In the Original Directory field, enter the root directory portion of the log directory for PSUB or the Reports Server, using the appropriate syntax for the operating system. See Table 11-1, "UNIX Directory Mapping Example" and Table 11-2, "Windows Directory Mapping Example".

5. In the Mapped Directory field, enter the UNC or the URL for the PSUB root directory. See Table 11-1, "UNIX Directory Mapping Example" and Table 11-2, "Windows Directory Mapping Example"

   Table 11-1 UNIX Directory Mapping Example

   Mapping Code	Original Directory	Mapped Directory	Where...
   HTTP	user01/home/logs	http://www.pharma.com/oc_output	shared directory named oc_output

   
   

   Table 11-2 Windows Directory Mapping Example

   Mapping Code	Original Directory	Mapped Directory	Where...
   HTTP	E:\opa\users	http://www.pharma.com/oc_output	shared directory name oc_output

   
   

Setting Up Image Viewing for DCI and DCM Form Layouts HTML Preview Feature

If your CRFs contain a company logo or other images and you want to be able to view the images using the HTML Preview feature of the Oracle Clinical DCI Forms Layout Editor, configure the J2EE application used in file viewing as follows:

1. Open the Windows Explorer on middle tier and navigate to ORACLE_AS10GR2MT_HOME\j2ee\opa\application-deployments\ocrdcclassic\ ocrdcclassic

2. Take a backup of the file orion-web.xml.

3. Open the original version in WordPad or a text editor.

4. Insert the following lines.

   <virtual-directory virtual-path="/crfimages" real-path="/Drive:/<image folder path>" /> 
   

   For example, if your images folder is at C:\opapps46\html\rdc\dcif_images, the file would look like:

   <?xml version="1.0"?>
   <!DOCTYPE orion-web-app PUBLIC "-//ORACLE//DTD OC4J Web Application 9.04//EN" "http://xmlns.oracle.com/ias/dtds/orion-web-9_04.dtd">
    
   <orion-web-app deployment-version="10.1.2.3.0"
                              jsp-cache-directory="./persistence"
                              jsp-cache-tlds="on"
                              temporary-directory="./temp">
           <!-- Uncomment this element to control web application class loader behavior.
               <web-app-class-loader search-local-classes-first="true"  include-war-manifest-class-path="true" />
           -->
               <virtual-directory virtual-path="/crfimages" real-path="/C:\opapps46\html\rdc\dcif_images"/>
               <web-app></web-app>
   </orion-web-app>
   

   Note:

   real-path can be a network location. If it is, make sure that the Oracle Process Manager Service on the middle tier is started up as a user with access to the specified network location; see "Setting Up a Network User to Run the Oracle Process Manager Service".

   If you have configured your Oracle Clinical and RDC installations to user a single repository for all images (see "Setting Up a Central Image Repository"), make sure that the path is to that location.

5. Save and close the file.

6. Log in as the network account you set up to start the Oracle Process Manager Service.

7. Restart the RDC OC4J instance.