| Oracle® Life Sciences Data Hub Installation Guide Release 2.1.4 Part Number E18152-05 |
|
|
View PDF |
| Oracle® Life Sciences Data Hub Installation Guide Release 2.1.4 Part Number E18152-05 |
|
|
View PDF |
This section contains the following topics:
See also Appendix A, "Architecture Overview."
Note:
If you install Oracle Life Sciences Data Hub (Oracle LSH) for the first time or upgrade to a new version after December 31, 2010 and are using Oracle Enterprise Manager (OEM) 10.2.0.4 or 10.2.0.5 with Oracle LSH, apply OEM patch 8350262.For further information see My Oracle Support article number 1217493.1.
This section includes some general requirements for your Oracle Life Sciences Data Hub (Oracle LSH) installation. Additional details are available in the documentation for each product you must install.
To get the most current information on the Oracle LSH technology stack, including optional systems integrated with Oracle LSH, see My Oracle Support document 180430.1, Oracle Life Sciences Applications Supported Technology Stacks.
Note:
Oracle LSH supports HP-UX Itanium and Linux x86-64 only on the database tier.Read My Oracle Support document 316806.1, Oracle Applications Installation Update Notes, Release 11i (11.5.10.2), to make sure that your environment meets all hardware- and platform-specific requirements.
Not all technology stack components and integrated external systems are supported on the same operating systems so you may need multiple computers on the same network; see My Oracle Support document 180430.1, Oracle Life Sciences Applications Supported Technology Stacks and Chapter 8, "Integrating Other Systems." for further information.
Oracle recommends installing all the middle tier services, including the Concurrent Manager, on the same computer as the application server but on a different computer from the database server.
In addition, you need one computer running on Windows for use in installing TMS. You will not need this computer after installing TMS except to install any TMS patches that may be required in the future. See Chapter 6, "Installing Oracle Thesaurus Management System." You need at least one Windows computer if you plan to use Oracle Business Intelligence Enterprise Edition (OBIEE) to define Business Areas and create data visualizations (OBIEE Answers); see Integrating Oracle Business Intelligence with the Oracle Life Sciences Data Hub. You can use the same Windows computer for OBIEE and TMS.
In a typical installation, application- and database-tier computers are connected by a local area network (LAN), while application-tier computers are connected to clients in a wide area network (WAN).
Using Real Application Clusters (RAC) to install the database over several nodes is optional; see Appendix C, "Installing Real Application Clusters (RAC)" for further information.
Oracle LSH uses Oracle XML Publisher (which is bundled with Oracle Applications) to generate PDF-format Report Sets. If you plan to use this feature and if your Report Sets are very large, you may want to dedicate one node to Oracle XML Publisher processing.
For system hardware requirements see the documentation for each component; see Assemble the Documentation.
In addition:
The TCP/IP network connection between the server should be at least at 1 GB.
Be sure to allow for growth in database storage capacity.
Oracle recommends installing a test environment as similar as possible to the production environment, including all OS and other patches and updates.
To get the most current information on the Oracle LSH technology stack, see My Oracle Support document 180430.1. At the time of publication of this document, the required technology stack for Oracle LSH consists of the following products:
Oracle Applications 11.5.10.2 and required patches, including ATG RUP7. See Install Oracle Applications 11.5.10.2.
Note:
Oracle LSH Release 2.1.4 has been tested ONLY on Release 11.5.10.2 of Oracle Applications. Do NOT install more recent releases unless explicitly instructed to do so by an Oracle LSH-specific note or alert on My Oracle Support.XML Publisher 5.6.3, which is bundled with ATG RUP7 (6241631).
Note:
Do not apply any higher version of Oracle XML Publisher that may become available, unless explicitly instructed to do so by an Oracle LSH-specific note or alert on My Oracle Support. Oracle LSH Release 2.1.4 has been tested only with XML Publisher Release 5.6.3.Oracle Workflow FND.H is shipped and installed with Oracle Applications 11.5.10.2.
JDK The Java Developer Kit is shipped and installed with Oracle Applications 11.5.10.2.
Oracle Database 11.2.0.1. You must upgrade the database that is shipped and installed with Oracle Applications 11.5.10 to 11.2.0.1.
XML DB, which is included with the 11.2.0.1 database, is required for Oracle LSH.
Oracle Warehouse Builder 10.2.0.1 and 11.2.0.1 OWB 11.2.0.1 with required patches is required for Oracle LSH 2.1.4's execution system. In addition, if you use Oracle Discoverer for data visualizations you must install OWB 10.2.0.1.
Oracle Thesaurus Management System 4.6.1 is used internally for Oracle LSH's classification system.
Oracle Reports 6.0.8.28 is included with Oracle Developer 6i patch set 19, which is a prerequisite for Oracle Database 11gR2. It is required for Oracle LSH Programs of type Oracle Reports.
A Zip utility is required on the Oracle LSH Distributed Processing Server.
For IDE launch (client), Winzip —Winzip Pro 11.2 SR-1, Winzip 8.1, or any other Winzip version that includes the WZUNZIP.exe—is required. It is separately licensed and not included on the media pack.
Oracle LSH includes adapters to support integration with the following external systems.
Oracle Clinical 4.5.1 (Optional and licensed separately) with Oracle Clinical patch 4.5.1.14 or its successor, 4.5.1.75.
Oracle Clinical 4.6 (Optional and licensed separately.)
Oracle Discoverer 10.1.2.3 Optional. Do not use the version shipped and installed with Oracle Applications 11.5.10. Instead, use the standalone version in the Oracle LSH media pack.
SAS 8.2, SAS 9.1.3, SAS 9.2 Optional and licensed separately.
Informatica PowerCenter 8.6.1 with Hotfix 11 Optional and licensed separately.
Oracle Business Intelligence Enterprise Edition (OBIEE) 10.1.3.4.1 with patch 7642637. Optional and licensed separately but included in the media pack.
Oracle BI Publisher 10.1.3.4.1 (Included with OBIEE). Optional and licensed separately but included in the media pack.
The data loaded into Oracle Life Sciences Data Hub (LSH) may originate in many systems, and these systems may use different encodings for special characters, including characters used in languages other than English. Special characters encoded in a coding system other than the one used by Oracle LSH may not be stored or displayed correctly in Oracle LSH.
If your data includes special characters, follow the steps in the sections listed here to adjust the many settings that determine the encoding used by various processes.
Make changes only after carefully analyzing the potential impact on your own data.
Set the database character set when installing Oracle Applications; see Oracle LSH UTF8 Requirements.
Leave NLS_LENGTH_SEMANTICS set to its default value, which is BYTE. To use character semantics, which is required, see the next point.
Set the LHS profile Use Character Semantics for Workarea Installation to Yes. See the chapter on setting profile values in the Oracle Life Sciences Data Hub System Administrator's Guide for information.
Set environment variables on each computer where you install the Oracle LSH Distributed Processing (DP) Server; see Set NLS_LANG to UTF8.
Add a JVM argument to the DP Server Start script; see Edit the DP Server Start Script.
If you are running SAS programs from Oracle LSH, see Start SAS in UTF8 Mode.
Definers who have a SAS or Oracle client such as SQL Developer or SQL*Plus installed as a development environment on their PC should follow instructions in Set the NLS_LANG Environment Variable to UTF8.
|
 Copyright © 2006, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
