| Oracle® Clinical Installation Guide Release 4.6.2 E18817-04 |
|
|
PDF · Mobi · ePub |
| Oracle® Clinical Installation Guide Release 4.6.2 E18817-04 |
|
|
PDF · Mobi · ePub |
A client is the Web browser interface to the application server. It displays data and transmits user actions to and from the application server. This chapter describes how to set up each client in your Oracle Clinical installation.
This chapter includes the following topics:
Section 10.1, "About an Oracle Clinical Client Installation"
Section 10.3, "Setting Internet Options for Microsoft Internet Explorer"
Section 10.5, "Downloading Required Applications for Clients"
Section 10.7, "Enabling Report Generation from the Command Line"
Oracle Clinical has two layout systems supporting data entry:
Character-based layouts support Oracle Clinical data entry and RDC Classic data entry.
Graphic-based layouts support RDC Onsite (HTML) data entry. In addition, graphic-based layouts support annotated CRFs and Patient Data Reports.
If you are annotating CRFs or generating Patient Data Reports, see the Oracle Clinical Administrator's Guide for more information.
Oracle Clinical supports the following Microsoft operating systems for the client:
Windows XP; Service Pack 1, 2, or 3; 32-bit architecture (US English)
Windows Vista; Service Pack 1; 32-bit architecture (US English)
Windows 7; Service Pack 1; 32-bit or 64-bit architecture (US English)
Windows Server 2008; Release 2; Service Pack 1; 64-bit architecture (US English)
To access Oracle Clinical, RDC Onsite, RDC Classic, and RDC Administration, clients must have the following applications installed:
Microsoft Windows Internet Explorer
For Windows XP: Internet Explorer 7 or 8
For Windows Vista: Internet Explorer 7 or 8
For Windows 7: Internet Explorer 8 or 9
For Windows Server 2008: Internet Explorer 8
Java Runtime Environment (JRE)
Oracle Clinical, RDC Classic, and RDC Administration require Java SE 6 Update 24 (Standard Edition, Version 1.6.0.24) or later.
RDC Onsite does not require the JRE.
Adobe Reader and Adobe Acrobat.
In addition, clients must have an intranet or internet connection.
If the client computer has a personal firewall, you must either disable it or configure it for RDC to function correctly. See your firewall documentation or ask your system administrator for assistance.
This section describes how to configure Internet Explorer on a client computer so you can run the Oracle Clinical, RDC Onsite, RDC Classic, and RDC Administration applications.
You must configure your client proxy settings if one of the following conditions is true for your installation:
You connect to the application tier with its fully qualified name (server_name.domain_name).
You use proxies.
To configure your client proxy settings:
Start Internet Explorer.
Open the Tools menu, and then select Internet Options.
Click the Connections tab.
Click LAN settings to open the Local Area Network (LAN) Settings dialog box.
Select Use a proxy server for your LAN, and then click Advanced.
Define the Exceptions at the bottom of the panel.
In the Do not use proxy server for addresses beginning with field, use the following format to enter the fully qualified name of each application server:
server_name.domain_name
For example, if the server name is sys63 and the domain name is mycompany.com, then you enter:
sys63.mycompany.com
If you are connecting to more than one application server, enter the fully qualified name of each server. Use the semicolon (;) to separate your entries.
Clients use Microsoft Windows Internet Explorer (Release 7, 8, or 9) to access the Oracle Clinical and RDC applications. The supported version of Internet Explorer depends on the version of Microsoft Windows you are using. For details, see Section 10.1.2, "Application Requirements for Oracle Clinical and RDC Clients."
If you are using Internet Explorer 8 or 9, check the Browser Mode and Document Mode settings. Table 10-1 lists the possible settings for each mode.
Oracle Clinical and RDC work properly with the default settings configured when Internet Explorer is installed. However, a user can change the Document Mode setting such that RDC Onsite does not work properly. For information about this known issue, see Section 10.3.3, "Using Internet Explorer 8 or 9 with RDC Onsite."
Table 10-1 Browser Mode and Document Mode Settings
| Internet Explorer | Settings |
|---|---|
|
Release 8 |
Browser Mode
Document Mode
|
|
Release 9 |
Browser Mode
Document Mode
|
Internet Explorer 8 and Internet Explorer 9 include a set of tools that enable Web site developers to prototype and test Web sites they develop. The Document Mode setting is one of those tools.
Although RDC Onsite supports Internet Explorer 8 and 9, a user can change the Document Mode setting such that RDC Onsite does not work properly. It is not anticipated that RDC Onsite users will change the Document Mode setting, as it is targeted at Web developers.
If you plan to use Internet Explorer 8 or 9 for RDC Onsite, ensure the Document Mode for the browser is set to Quirks Mode (Page Default).
To verify or configure the Document Mode setting:
Launch Internet Explorer 8 or 9.
Open the Tools menu, and then select Developer Tools.
Set the Document Mode to Quirks Mode (Page Default).
To start and log in to the Oracle Clinical:
Start Internet Explorer.
Enter the following URL:
https://computer_name.domain:port/opa46/launch.htm
where:
computer_name is the network name for the application server
domain is the network domain name for your organization
Click Login.
Enter your user name, your password, and the database name.
Click Connect to start the Oracle Clinical session.
Note:
If the JRE is not present on this client, Oracle Clinical automatically starts to download the JRE when you click Login. Follow the on-screen instructions to download and install the JRE to the default location.Table 10-2 lists the URLs you enter in Internet Explorer to start the Oracle Clinical, RDC Onsite, RDC Classic, and RDC Administration applications.
When entering a URL, replace the variables as follows:
computer_name is the network name for the application server
domain is the network domain name for your organization
Table 10-2 URLs to Start Oracle Clinical and RDC Applications
| Application | URL |
|---|---|
|
Oracle Clinical |
|
|
RDC Onsite |
|
|
RDC Classic |
|
|
RDC Classic (in Test Mode) |
|
|
RDC Administration |
|
|
RDC Administration (in Test Mode) |
|
This section describes how to download and install the following applications:
Java Runtime Environment (JRE)
Oracle Clinical PDF plug-in
Adobe Reader
Oracle Clinical, RDC Classic, and RDC Administration require the Java Runtime Environment (JRE).
Before you download the JRE, uninstall any old versions of the JRE, if present. By uninstalling old versions, you avoid receiving the following message when starting an Oracle Health Sciences application:
The Application requires an earlier version of JRE. Do you want to continue?
To download and install the JRE onto a client:
Open Internet Explorer and enter the URL to open the Launch page for the Oracle Clinical application. For example:
https://computer_name.domain:port/opa46/launch.htm
Click the Downloads link on the Launch page. The Oracle Health Sciences Downloads page opens.
Follow the on-screen instructions to download and install the JRE.
During the installation, you must accept all prompts to accept signed jar files.
The system downloads the JRE from your Forms Server. When you set up the Forms Server, you installed the latest version of the JRE. See Section 6.2, "Making the Java Runtime Environment Available for Download" for more information.
If you want to be able to generate annotated layouts in Oracle Clinical, you must install the PDF plug-in onto the client.
Note:
The PDF plug-in is not required for RDC data entry.To download and install the Oracle Clinical PDF plug-in onto the client:
Open Internet Explorer and enter the URL to open the Launch page for the Oracle Clinical application. For example:
https://computer_name.domain:port/opa46/launch.htm
Click the Downloads link on the right of the Launch page. The Oracle Health Sciences Downloads page opens.
Follow the on-screen instructions to download and install the PDF plug-in.
The system downloads the plug-in from your Forms Server. When you set up the Forms Server, you installed the latest version of the PDF plug-in. See Section 6.3, "Downloading the Oracle Clinical PDF Plug-in" for more information.
Oracle Clinical and RDC support Adobe Reader 7.x or later, English versions. However, this requirement may change during the life of this document. Check My Oracle Support for the latest requirements.
To download the free Adobe Reader:
Go to the Adobe Corporation Web site:
Follow the on-screen instructions to download the latest version of the Adobe Reader.
If you intend to use this client to design graphic CRFs, you can enable an image browsing feature to simplify inserting graphic images in your layouts. Instead of entering the exact path and file name into the Insert Image field, you can use the standard Windows Browse button.
You must first set up the Forms Server where you store your images. See Section 6.5, "Sharing the RDC Directory and Setting Image Browsing" for details.
To enable image browsing, you must permanently map the Forms Server's drive to this client:
Open My Computer.
Open the Tools menu, and then select Map Network Drive.
Enter the drive letter that you want to assign to this connection.
Enter the path of the folder you want to be able to access. Alternatively, you can click Browse to select the folder location.
Click Finish.
In the RDC Onsite application, you can generate Patient Data Reports (PDRs) and Blank Casebook Reports from the Reports page if you have the necessary privileges.
In addition, you can configure your desktop to generate these reports from the MS-DOS command line. Generating reports from the command line can be useful when producing electronic submissions for new drug applications (NDAs). Adding the commands to a batch file lets you generate many Patient Data Reports at once.
For information about how to configure the Desktop PDR to generate reports from the command line, see the Oracle Clinical Remote Data Capture Onsite Administrator's Guide.
|
 Copyright © 1996, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
