| Oracle® Clinical Installation Guide Release 4.6 Part Number A83779-08 |
|
|
View PDF |
| Oracle® Clinical Installation Guide Release 4.6 Part Number A83779-08 |
|
|
View PDF |
The Oracle Clinical Forms Server performs the form processing, communicates the display changes to the client, and calls forms to query, update, select, and delete data from the Database Server.
An Oracle database does not have to be installed for you to install an Oracle Clinical Forms Server. However, you need a supported Oracle database to verify the Forms Server installation.
To install the Oracle Clinical Forms Server, you complete the following tasks:
Section 5.2, "Installing and Patching Oracle AS10gR2 Forms and Reports Services"
Section 5.4, "Setting Up the SQL*Net Connections for Existing Databases"
Section 5.5, "Installing the Oracle Clinical 4.6 Forms Server"
Note:
Installing the Oracle Clinical Forms Server also installs Oracle Clinical RDC Onsite on the same server.Oracle Clinical uses the OPAREPS user account when starting the Oracle Reports Server, the Oracle HTTP Server, and the Oracle Clinical application.
You use the OPAREPS account on the Reports Server to perform the following tasks:
Generate Reports Server output and log files for individual users
Review PSUB and report output for the HTTP Server
Delete temporary PSUB and report output for the HTTP Server
Run report jobs and print reports for the Report Server
OPAREPS is also used by the HTTP Server to view or delete report or PSUB output, and to print report output.
This section describes how to create the OPAREPS account for the first server in a network domain. You should make OPAREPS part of a network domain for the following reasons:
You do not have to create a new account for each Web or Reports Server installation.
You can direct the report output to other computers.
Use the Windows Administrative Tools to create the OPAREPS account.
If an OPAREPS account is already created in the domain, be sure that the tasks in Section 5.1.2 and Section 5.1.3 are also complete.
Use the Windows Administrative Tools to add the OPAREPS account to the Administrators group for this computer.
Once you have created the OPAREPS account, you need to modify the account and specify every printer that you plan to use for printing Oracle Clinical reports.
To add a printer for the OPAREPS account:
Log in to Windows as the OPAREPS user.
Click Start, Settings, and then Printers. The Windows Printer dialog box opens.
Double-click the Add Printer icon. The Add Printer Wizard opens.
Click Next. The wizard prompts for the type of printer — local or network — that you want to add.
Select the Network Printer option, and then click Next.
Specify the name or address of the printer. If you do not know the name or address, you can browse for a printer. Click Next to continue.
Specify whether you want to use this printer as the default printer for Windows-based programs. Click Next to continue.
Click Finish. The system adds this printer to this computer.
Enter a printer specification in the Printer field or select a printer from the list of shared printers, and then click OK next to your selection.
To install Oracle AS10gR2 Forms and Reports Services:
Close all running applications on the computer.
Log in to the application server using an account with system administrator privileges.
Insert Disk B24458-01 from the Oracle Clinical 4.6 and Oracle Thesaurus Management System 4.6.1 Media Pack.
Use Windows Explorer or the command line to execute the setup.exe file:
install\setup.exe
The system briefly displays a DOS window while it checks your computer's compatibility, and then opens the Welcome screen.
Follow the instructions on the installation screens. For additional information on each screen, see Section 5.2.1, "Attend to the Oracle AS10gR2 Installation Screens."
For more information on AS10gR2, see the Oracle AS10gR2 Forms and Reports Services documentation.
Click Next to continue the installation. Alternatively, you can click Installed Products to review a list of installed Oracle products.
On this screen, you set up the Oracle AS10gR2 home:
Source Path: Accept the default Source location path.
Destination Name: Enter the home name of the application tier (middle tier). For example, AS10gR2mt.
Path: Append your specified home name to the path. You can change the path to another location, or you can keep the default path. For example: D:\oracle\AS10gR2mt.
Click Next.
Language Selection Oracle Application Server Forms and Reports Services 10g 10.1.2.0.2
Select a language for the Oracle Application Server Forms and Reports Services.
Specify Port Configuration Options
Select Automatic, and then click Next.
Provide Outgoing Mail Server Information
To enable and use the outgoing mail feature, enter the necessary mail server information. The mail server is optional. It is not needed to run Oracle Clinical 4.6.
Click Next.
Specify Instance Name and ias_admin Password
Each instance of Oracle AS10gR2 requires its own name and password combination, regardless of who installs the instance on the host computer. The name of the Oracle AS10gR2 instance cannot be the same as the infrastructure instance. The suggested name for this instance is AS10gR2mt.
Enter and confirm a valid password, and then click Next.
Review the installation details to verify that they are correct. To revisit earlier installation screens and make changes, click Back.
When you are ready to continue, click Install. The Installer configures this instance of Oracle AS10gR2. The configuration process can take several minutes. Do not interrupt the automated configuration.
Scroll through and review the information in the End of Installation section of the window. The Universal Installer saves all of this information in the following file:
setupinfo.txt
The Installer displays the location of this file near the top of the End of Installation section. Make note of this location in case you want to reference the file in the future.
When you have finished reviewing the installation information, click Exit. At the confirmation prompt, click Yes to exit from the Universal Installer.
To ensure that all configuration changes for Oracle AS10gR2 are initialized, you must restart the computer.
When the computer restarts, log in as a user with system administrator privileges. You are now ready to apply several patches for Oracle AS10gR2 Forms and Reports Services and the Application Server.
To apply Patch Set 3 (10.1.2.3) to Oracle AS10gR2 Forms and Reports Services:
Insert Disk V17174-01 of the Oracle Clinical 4.6 and Oracle Thesaurus Management System 4.6.1 Media Pack.
Locate p5983622_10123_WINNT.zip, which is Oracle AS10gR2 Forms and Reports Services Patch Set 3 (10.1.2.3).
Extract the patch zip file to a location that is accessible to the Forms Server.
Follow the instructions in the ReadMe file to apply the patch set. The ReadMe file is located at the top level of the patch set extraction location.
To apply Patch 7384879 to the Application Server:
Insert Disk V17174-01 of the Oracle Clinical 4.6 and Oracle Thesaurus Management System 4.6.1 Media Pack.
Locate p7384879_10123_GENERIC.zip.
Extract the patch zip file to a location that is accessible to the Forms Server.
Follow the instructions in the ReadMe file to apply the patch. The ReadMe file is located at the top level of the patch extraction location.
To tune the application server for better performance, download the following white paper from My Oracle Support:
Title: Configuring Oracle Clinical Remote Data Capture Onsite 4.6 for Performance and Scalability
Article ID: 873743.1
If you set up multiple Forms Servers:
Log in to Oracle AS10gR2 Enterprise Manager.
Select this Application Server. The utility displays a System Component list.
Click Web Cache.
Click the Administration tab.
Set the Keep Alive Timeout (Seconds) value in the Timeouts section to 0 (zero).
Click OK.
Click Restart Web Cache.
Oracle publishes a CPU Security Update patch quarterly. Apply the latest CPU Security Update patch approved for the Oracle Health Sciences applications to this computer. Check My Oracle Support to determine the latest version.
You must stop the HTTP Server before you apply the patch.
Establish that SQL*Net connections can be created to connect the Forms Server and the Reports Server to all databases.
To do this, modify 10g_oracle_home\network\admin\tnsnames.ora. Ensure that it contains an entry for each database.
Consider maintaining a central copy of tnsnames.ora with all the system's tnsnames entries for the databases. Copy the file to all clients, Forms Servers, and Reports Servers.
Beginning with Release 4.6, Oracle Clinical no longer uses a tns entry for the Reports Server. The only entry needed on the Forms Server and the Reports Server is the entry for databases.
If the system returns a connection error, you must resolve this problem before continuing. Possible causes of errors include:
The computer is not physically connected to the network.
One of the databases does not exist.
The network protocol software is not loaded on the computer (try a remote log-in to check).
The SQL*Net software is not loaded on the computer.
The database or SQL*Net listener process is not started on the server.
An incorrect connect string, user ID, or password was entered.
The tnsnames.ora file is not present in the correct directory or does not contain the correct entries.
To install the Oracle Clinical 4.6 Forms Server:
Log in as a user with system administrator privileges.
Insert Disk V17174-01 of the Oracle Clinical 4.6 and Oracle Thesaurus Management System 4.6.1 Media Pack.
Locate and execute the following file:
oc\middle_tier\install\setup.exe
The Installer opens to the Welcome screen.
Follow the instructions on the installation screens. For additional information on each screen, see Section 5.5.1, "Attend to the Oracle Clinical Forms Server Installation Screens."
The following sections describe each Installer screen and the required action.
Click Next.
In the Source section, specify the location where you extracted the Oracle Clinical 4.6 patch.
In the Destination section, accept the default values.
Click Next.
Select OC Front End 4.6, and then click Next. The Installer installs both the Oracle Clinical Forms Server and the Remote Data Capture option. Click Next.
OC Front End Choose OPA Home Directory
Specify the application tier installation directory. This is the directory that is the root of installations of Health Sciences products. Typically, you should respond with the path to the opapps46 directory.
The recommended installation directory for Release 4.6 is:
drive:\opapps46
where drive is the disk's letter designation, and opapps46 is the directory name.
References to the OPA_HOME variable in all the application tier (middle tier) instructions in this guide take the value you enter here.
Click Next.
OC Front End Select the PSUB File Access Mode
Select either FTP or UNC as the protocol for viewing files generated by PSUB. For more information, see "File Viewing" in the Oracle Clinical Administrator's Guide.
Click Next.
OPA Front End Enter NLS Language
Select an NLS language setting that is appropriate for your database character set.
If you are only installing Oracle Clinical and RDC, Oracle recommends that you use the UTF8 character set. In addition, Oracle recommends UTF8 for new customers.
However, be sure to use the same character set on the database tier and the application tier. If your database is US7ASCII and you select UTF8 for the application tier, Oracle Clinical stores some special characters incorrectly in the database.
Click Next.
OPA Front End Enter NLS Date Format
If the NLS_DATE_FORMAT entry in the system registry is not configured with an appropriate value, the Installer prompts for a value. The correct format is DD-MON-RRRR. Adjust the date format, if necessary, and click Next.
OPA Front End Enter Report Queue Manager Machine
By default, the Installer displays the IP address or the name of the computer. Accept the default value. Click Next.
OPA Front End Enter URL for the Report Queue Manager
Accept the default value. Click Next.
OPA Xhelp Choose the URL location of your custom documentation.
If you have a directory for custom help, enter the location in this form. Otherwise, accept the default value. Click Next.
The Installer displays a diagram of the target directories. (The Installer only displays oracle_home in the Destination field. It may differ from your actual directory path.)
This concludes the information gathering phase of the installation process. To change any of the information, click Previous to revisit earlier screens. When you are satisfied with the information on this screen, click Install.
The Installer copies the files onto the server and generates a log file of this installation.
The Installer informs you whether the installation was successful and prompts you to quit or continue with the next product installation. Click Exit to pause here, or click Next Install to install another Health Sciences product.
The Installer creates log files at OPA_HOME\log.
Note:
Before you install a Reports Server, you should restart this computer.To change the login properties of the Oracle AS10gR2 Process Manager Service to use the OPAREPS account:
Log in as the OPAREPS user or as a user with system administrator privileges.
Open the Windows Control Panel.
Double-click Administrative Tools.
Double-click Services.
Select Oracle AS10gR2 Process Manager Service.
Open the Action menu, and then click Properties.
Click the Log On tab.
Set the account to OPAREPS.
Click OK to save your changes.
Close the Services dialog box.
For PDF generation to succeed in Oracle Clinical, the Database Server must be able to communicate with the Forms Server computer. Ensure that the Database Server can ping the Forms Server computer using its network name.
As part of the Forms Server setup, you need to:
Share the RDC directory so that it is available to both the Reports Server and the Oracle Clinical Graphic Layout Editor
Enable (or disable) image browsing by setting values in the Windows system registry
To share the RDC directory and to configure image browsing:
Log in to the Forms Server computer as a user with system administrator privileges.
Share the \opapps46\html\rdc\ directory. Give the directory the name RDC. Make it readable by any user account that uses the Graphic Layout Editor.
Open the Windows System Registry Editor.
Navigate to the following key:
\HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\10g_oracle_home
Set values for the following keys:
RDC_DCIF_IMAGES_BROWSE = Y
RDC_DCIF_IMAGES = \\forms_server_name\rdc\dcif_images
The forms_server_name is the network name of the computer. You must use the reference syntax for the value. Entering the exact path does not work.
RDC_DCIF_IMAGES_URL = http://web_server_name.domain_name/opa46/ rdc/dcif_images
The domain_name is the fully qualified domain name. For example, my.company.com.
RDC_DCIF_IMAGES_VALIDATE = Y (enables image browsing) or N (disables image browsing)
Note:
The value for RDC_DCIF_IMAGES and RDC_DCIF_IMAGES_URL must be the same location.The JSpell Spelling Checker application is a third-party product from The Solution Cafe (http://www.thesolutioncafe.com/). You can use it to check the spelling of text objects in graphic layouts.
The Graphic Layout Editor in Oracle Clinical supports the SDK 2004 Spell Checker version of JSpell. However, Oracle does not maintain the product itself. You must purchase the product separately.
To install the JSpell application on the Forms Server:
Extract the Jspell files on the Application Server.
Copy the jspell2k4s.jar and jspell2k4n.jar files into the following location:
ORACLE_HOME/forms/java
Create the jspell directory in the root of the Application Server. For example, if the Application Server is installed in c:/oracle then create the c:/jspell directory.
Copy the lex_enUS.jdx file into the jspell directory.
Log in to the Enterprise Manager Application Server Control (http://app_server:18100).
Select the Application Server instance:
Click the opa OC4J system component.
Click the Applications tab.
Click Deploy WAR File.
Enter the following values:
Web Application: Specify the location of the JSpellWAR file, jspell2k4.war, using the Browse feature.
Application Name: jspell2k4.
Map to URL: /jspell2k4.
Click Deploy.
Click OK.
To test the JSpell Servlet, open the following URL:
http://server_name/jspell2k4/servlet/JSpellServlet? operation=status
If the status page opens without error, JSpell is properly installed.
When you installed the JSpell application, the instructions recommended that you create the jspell directory in the same root (parent) directory as the Application Server. For example, if the Application Server is installed in c:/oracle, then you create the c:/jspell directory.
If the JSpell and Application Server directories are not at the same root directory, you must map JSpell's lexicons directory:
Navigate to the following directory:
oracle_as10gr2mt_home\j2ee\opa\applications\jspell2k4 \jspell2k4\WEB-INF
Open the web.xml file.
Find the following lines in the web.xml file:
<init-param> <param-name>indexDirectory</param-name> <param-value>/jspell/</param-value> </init-param>
Change the /jspell/ text string to the location of the lex_enUS.jdx file on the Application Server.
The Oracle Clinical and RDC launch pages test that the Java Runtime Environment, or JRE (also known as the Java Virtual Machine, or JVM) exists on the user's computer. If the JRE does not exist, the Oracle Clinical and RDC plug-in pages provide a link to install the software.
Oracle Clinical supports JRE Version 1.6, Update 15 or later.
To download the latest version of the JRE and position the software so your users can install it directly from the plug-in page:
Go to the Java Web site:
Download the latest Java Runtime Environment installer (for example, JavaSetup6u21-rv.exe) to the following location:
OPA_HOME\html
Rename the download file to sunjpi.exe.
If your organization implements the DCI Forms graphic layout system for annotated CRFs, you must download the Oracle Clinical PDF plug-in from My Oracle Support, and then set it up on each Forms Server computer.
To download the Oracle Clinical PDF plug-in:
Sign in to My Oracle Support at http://support.oracle.com.
Click the Patches & Updates tab. The Patches & Updates page opens and displays the Patch Search region.
In the Patch ID or Number is field, enter 8262425. The current plug-in patch number is 8262425. If this patch becomes obsolete, download its successor.
Click Search to execute your query. The Patch Search Results page opens.
Click the patch ID number. The system displays details about the patch. In addition, you can view the ReadMe file before downloading the patch.
Click Download. Follow the instructions on the screen to download and save the patch zip file to this computer.
Extract the file to a temporary directory.
Follow the instructions in the ReadMe file to install the PDF plug-in on this Forms Server.
If you modified any files or scripts in a previous Oracle Clinical installation, see Section 9.2.1, "Upgrade Forms Server Customizations."
|
 Copyright © 1996, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
