Skip Headers
Oracle® Clinical Administrator's Guide
Release 4.6.2

E18818-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

12 Enabling Image Viewing

This section includes the following topics:

To enable image viewing on CRFs during RDC data entry, you can choose either to set up a central repository or to copy images to all RDC Onsite installations.

Setting Up a Central Image Repository

You can configure your OC and RDC installations to use a single repository for all images. After the initial setup, this approach is more efficient because edited and added images do not need to be copied to all installations.

There are also disadvantages:

To set up a single repository:

  1. Create a shared directory on a computer that is accessible from all Oracle Clinical and RDC Onsite installations, and put the image files in the shared directory.

  2. To use the central image repository in Oracle Clinical, add a line to orion-web.xml at each Oracle Clinical installation for virtual folder mapping to the central repository. See "Setting Up Image Viewing for DCI and DCM Form Layouts HTML Preview".

  3. To use the central image repository in RDC Onsite during data entry, add a line to orion-web.xml at each RDC Onsite installation for virtual folder mapping to the central repository. See "Setting Up Image Viewing During Data Entry".

  4. Repeat Step 2 on every Oracle Clinical installation and repeat Step 3 on every RDC Onsite installation.

Setting Up a Network User to Run the Oracle Process Manager Service

On each Oracle Clinical and RDC installation, the Oracle Process Manager Service must be started up as a network user to allow access to shared image files on a network location.

  1. Open Windows Service Manager.

  2. Select Oracle AS Process Manager.

  3. Right-click and select Properties.

  4. Go to the Log On tab.

  5. Select This Account.

  6. Enter username/password of the network account and click OK.

  7. Reboot the computer.

Setting Up Image Viewing During Data Entry

If your CRFs contain a company logo or other images that you want users to be able to see during data entry in RDC, you must configure the J2EE application used in file viewing.

To configure the J2EE application used in file viewing:

  1. Navigate to the following directory:

    ORACLE_AS10gR3_HOME\j2ee\rdc\application-deployments\olsardc\rdconsite\

  2. Back up the orion-web.xml file.

  3. Open the original orion-web.xml file with a text editor.

  4. Insert the following lines:

    <virtual-directory virtual-path="/de/crfimages" real-path="<shared folder path>"/> 
    

    For example, if your images folder is at \\sharemachine\images, the file would look like:

    <orion-web-app deployment-version="10.1.2.3.0"
                               jsp-cache-directory="./persistence"
                               jsp-cache-tlds="on"
                               temporary-directory="./temp">
            <virtual-directory virtual-path="/de/crfimages" real-path="\\sharemachine\images" />
            <!-- 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" />
            -->
            <web-app></web-app>
    </orion-web-app>
    
  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.

Copying Image Files to All Installations

You can create an images directory at every RDC installation and copy all image files to each installation. If the images are updated or if new ones are added, you must copy them to all installations.

Create an images directory at the following location at each installation:

ORACLE_AS10gR3_HOME\j2ee\rdc\applications\olsardc\rdconsite\de\crfimages

Note:

If you choose to copy files to all RDC installations, do not edit RDC Onsite's orion-web.xml file.