Oracle® Thesaurus Management System

Installation Guide

Release 5.1

E53656-03

July 2017

This guide describes how to install, configure, and upgrade Oracle Thesaurus Management System.

Oracle Thesaurus Management System Installation Guide, Release 5.1

E53656-03

Copyright © 1999, 2017, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Finding Information and Patches on My Oracle Support

- Finding Oracle Documentation

- Related Documents

- Conventions

1 Preparing to Install Oracle Thesaurus Management System

- 1.1 Installation and User Documentation

- 1.1.1 My Oracle Support Articles

- 1.1.2 User Documentation

- 1.2 Architecture

- 1.3 Technology Stack

- 1.3.1 Planning a TMS Database Installation

- 1.3.1.1 Character Set Requirements

- 1.3.1.2 Critical Patch Update

- 1.3.1.3 Database Tier Operating System Requirements

- 1.3.1.4 Database Tier System Requirements

- 1.3.1.5 Oracle Database Requirement: Oracle Text Option

- 1.3.2 Planning a TMS Application Tier Installation

- 1.3.2.1 Character Set Requirements

- 1.3.2.2 Critical Patch Update

- 1.3.2.3 Permanent IP Address

- 1.3.2.4 Installing TMS with Oracle Clinical

- 1.3.3 Planning a TMS Client Installation

- 1.4 Downloading and Extracting the Software

- 1.4.1 Creating Staging Areas

- 1.4.1.1 Database Server Staging Area

- 1.4.1.2 Application Server Staging Area

- 1.4.2 Downloading and Extracting the Oracle Clinical 5.1 and Oracle Thesaurus Management System 5.1 media pack

- 1.4.3 Downloading and Extracting Patches from My Oracle Support

- 1.4.4 Downloading Oracle Java Development Kit

- 1.4.5 Downloading the Java Runtime Environment

- 1.4.6 Downloading Adobe Reader

- 1.5 Using the Silent Installer

- 1.6 Reviewing the Installation Log Files

- 1.7 Choosing a Character Set

- 1.8 Applying Oracle Critical Patch Updates

- 1.9 Applying the Latest TMS Patch Set

2 Installing Oracle Database on UNIX

- 2.1 Performing Prerequisite Tasks for Installing Oracle Database

- 2.1.1 Create Owners, Groups, and Mount Points

- 2.1.2 Configure Kernel Resources and Adjust Operating System Environment

- 2.1.3 Install Latest Operating System Patches

- 2.2 Installing Oracle Database

- 2.2.1 Install Oracle Database 12.1.0.1 Enterprise Edition

- 2.2.2 Install Oracle Database Examples

3 Installing Oracle Database on Windows

- 3.1 Install Oracle Database 12.1.0.1 Enterprise Edition

- 3.2 Install Oracle Database Examples

4 Creating a TMS Database

- 4.1 Restart Computer and Stop All Servers and Services

- 4.2 Installing the TMS Database Server Code

- 4.2.1 Gather Required Information

- 4.2.2 Start the TMS Server Installer

- 4.2.3 Attend to the TMS Database Server Code Installation Screens

- 4.3 Review Database Requirements and Recommendations (All Databases)

- 4.3.1 Start with a New Database Instance

- 4.3.2 Accept Connections as a Service

- 4.3.3 Check Required Tablespaces

- 4.3.4 Use the Database Configuration Assistant

- 4.3.5 Select Required Components

- 4.3.6 Use Automatic Memory Management

- 4.3.7 Set Initialization Parameters

- 4.3.8 Modify the tnsnames.ora File on the Database Server

- 4.4 Install TMS Database Objects (All Databases)

- 4.4.1 Unlock Accounts Before Installing the TMS Database

- 4.4.2 Gather Required Information

- 4.4.3 Stop the PSUB Process (If Integrated with Oracle Clinical)

- 4.4.4 Start the Installer

- 4.4.5 Attend to the TMS Database Installer Screens

- 4.4.6 Check the Database Log File

- 4.5 Create a TMS Administrator User Account (All Databases)

- 4.6 Register Databases Integrated with Oracle Clinical

- 4.6.1 Gather Required Information

- 4.6.2 Start the Installer

- 4.6.3 Attend to the TMS Database Registration Screens

- 4.7 Load Dictionaries (Single or Master Database)

- 4.8 Complete Distributed Environment Setup

- 4.8.1 Export Data from the Master Database

- 4.8.2 Import Data to the Slave Database

- 4.8.3 Clean Up after Export and Import

- 4.8.4 Complete the Creation of the Slave Database

- 4.8.5 Configure DSI Import

- 4.8.6 Setting Up and Starting Symmetric Replication

- 4.8.6.1 Preliminary Steps to Start Replication

- 4.8.6.1.1 Check the initdbname.ora File

- 4.8.6.1.2 Run the opasrc01.sql Script

- 4.8.6.1.3 Run the opasrc02.sql Script

- 4.8.6.2 Start Replication on the Master Database

- 4.8.6.3 Start Replication on Each Slave Instance

- 4.8.7 Register Slave Databases Integrated with Oracle Clinical

5 Installing and Configuring the Application Tier

- 5.1 Before You Start

- 5.1.1 Identify a Single Account to Perform All Application Tier Installation Tasks

- 5.1.2 Get a CA Certificate for HTTPS

- 5.2 Install Adobe Reader

- 5.3 Install Oracle Java Development Kit

- 5.4 Install Oracle WebLogic Server 10.3.6

- 5.5 Install and Configure Oracle Application Server 11gR2

- 5.5.1 Install Oracle Application Server 11gR2 (11.1.2.1)

- 5.5.2 Stop Services

- 5.5.3 Apply Patch

- 5.5.4 Create ORACLE_INSTANCE Environment Variable

- 5.6 Enable SSL Between a Browser and Oracle HTTP Server

- 5.6.1 Enabling SSL Between a Browser and Oracle HTTP Server Using a Certificate Authority

- 5.6.1.1 Creating an Oracle Wallet and Generating a Certificate Request

- 5.6.1.2 Obtain Trusted Certificate and User Certificate from Certificate Authority

- 5.6.1.3 Import the User Certificate and Trusted Certificate to OWM

- 5.6.1.4 Edit the Oracle HTTP Server Configuration File

- 5.6.1.4.1 Add the New Wallet Location and Specify Port

- 5.6.1.4.2 Make OHS Compatible with Internet Explorer 9 and Above

- 5.6.1.4.3 Add Security Settings

- 5.6.2 Enabling SSL Between a Browser and Oracle HTTP Server With Self Signing

- 5.7 Install Oracle Application Developer FrameWork and Apply Patches

- 5.7.1 Install Oracle Application Developer Framework (ADF)

- 5.7.2 Upgrade ADF

- 5.7.3 Patch ADF to Support Internet Explorer 11

- 5.8 Modify the tnsnames.ora File on the Application Server

- 5.9 Test Connectivity to Databases for Forms and Reports Servers

- 5.9.1 Test the Connection from the Application Servers to the Database

- 5.9.2 Troubleshoot Network Connection Issues

- 5.10 Restart the Computer

6 Installing Oracle Thesaurus Management System Application Components

- 6.1 Restart Computer and Stop All Servers and Services

- 6.2 Installing the TMS Front End

- 6.2.1 Gather Required Information

- 6.2.2 Start the Installer

- 6.2.3 Attend to the TMS Front End Installer Screens

- 6.2.4 Review the Installation Log File

- 6.2.5 Restart the Computer

- 6.2.6 Add WebLogic Data Sources If Using Multiple Databases

- 6.3 Make the Java Runtime Environment Available for Download

- 6.4 Installing the TMS Reports Server

- 6.4.1 Start the WebLogic FRDomain Admin Server

- 6.4.2 Gather Required Information

- 6.4.3 Start the TMS Report Server Installer

- 6.4.4 Attend to the TMS Reports Server Installation Screens

- 6.5 Verifying the Application Tier Installation

- 6.6 Verify and Fix Environment Variables

- 6.6.1 Check Values

- 6.6.2 Correct Values

- 6.7 Set Up Automatic Startup

- 6.7.1 Set Up Script to Execute Automatically at Machine Startup

- 6.7.2 Verify Autostart Scripts

- 6.7.3 Test Autostart

- 6.8 Starting Servers Manually

- 6.8.1 Starting the FRDomain Admin Server

- 6.8.2 Starting the Forms Server

- 6.8.3 Starting the Reports Server

- 6.8.4 Starting the OPADomain Admin Server

- 6.8.5 Starting the OpaServer1 Server

- 6.9 Verify the Application Tier Installation

- 6.10 Stopping Servers

- 6.10.1 Stopping the Forms Server

- 6.10.2 Stopping the Reports Server

- 6.10.3 Stopping the FRDomain Admin Server

- 6.10.4 Stopping the OPADomain Admin Server

- 6.10.5 Stopping the OpaServer1 Server

7 Upgrading Oracle Thesaurus Management System to Release 5.1

- 7.1 Upgrade Oracle Clinical (If Integrated with Oracle Clinical)

- 7.2 Install Oracle Database

- 7.2.1 Installing the Oracle Database Server on UNIX

- 7.2.2 Installing the Oracle Database Server on Windows

- 7.3 Install the TMS Database Server Code

- 7.4 Upgrade a Single or Master TMS Database

- 7.4.1 Suspend Symmetric Replication (Distributed Environment Only)

- 7.4.2 Prevent Access to Oracle Thesaurus Management System Databases

- 7.4.3 Upgrade to Oracle Database 12.1.0.1

- 7.4.3.1 Upgrade in Place

- 7.4.3.2 Clone Your Database

- 7.4.4 Gather Required Information

- 7.4.5 Stop PSUB Process (If Integrated with Oracle Clinical)

- 7.4.6 Start the Installer

- 7.4.7 Attend to the TMS Database Upgrade Installer Screens

- 7.4.8 Set Initialization Parameters

- 7.4.9 Check Installation Log for Errors

- 7.4.10 Configure DSI Import

- 7.4.11 Load Dictionaries

- 7.4.12 Create an Export File (Distributed Environments Only)

- 7.5 Upgrade Slave TMS Databases (Distributed Environments Only)

- 7.6 Upgrade Cloned Databases

- 7.7 Run Scripts to Gather Schema Statistics for the 11g Optimizer

- 7.8 Install or Upgrade the Application Tier Technology Stack

- 7.8.1 Upgrading from a Release Earlier than 5.1

- 7.9 Install the TMS Front End and Reports Server

- 7.9.1 Install the Oracle Thesaurus Management System Front End and Reports Server

- 7.9.2 Set Remote Method Invocation (RMI) JDBC Security to Secure

- 7.10 Redefine the TMS Load User

8 Post-Installation Steps for the New Installation or Upgrade

- 8.1 Patch TMS

- 8.2 Test the TMS Forms Server

- 8.3 Configure WebLogic Server Data Sources

- 8.3.1 Confirm the OPA Data Source Value in WebLogic Server Admin Console

- 8.3.2 Set REPORT_CONFIG Reference Codelist Value

- 8.3.3 Add Data Source (Required Only If Using Multiple Databases)

- 8.4 Making the Java Runtime Environment Available for Download

- 8.5 Create a Link to TMS HTML Browser

- 8.6 Define and Load Dictionaries

- 8.7 Setting Up Client Computers

- 8.7.1 Configuring Personal Firewall

- 8.7.2 Using Safari on an iPad

- 8.7.3 Setting Internet Options for Microsoft Internet Explorer

- 8.7.3.1 Setting Document Mode to Quirks (the Default Setting)

- 8.7.3.2 Disabling Cookies

- 8.7.3.3 Allowing More Connections

- 8.7.3.4 Turning Off Compatibility View

- 8.7.3.5 Set Up for Proxy Usage on Fully Qualified Application Tier Names

- 8.7.4 Download the Java Virtual Machine to Client Computers

- 8.7.5 Logging In

Preface

This guide describes how to install Oracle Thesaurus Management System (TMS) Release both as an initial installation and as an upgrade from a previous release.

This preface includes:

- Audience

- Documentation Accessibility

- Finding Information and Patches on My Oracle Support

- Finding Oracle Documentation

- Related Documents

- Conventions

Audience

The audience for this installation guide is database administrators (DBAs) and system administrators. Installing TMS requires the skills listed below. If you want assistance with your installation, engage Oracle Consulting.

Database Administrators

Installing TMS requires a level of knowledge equivalent to having mastered the material in the Oracle Architecture and Administration course for DBAs. You must be able to read and edit SQL*Plus scripts, run SQL scripts, and review logs for Oracle errors. For ongoing administration, additional training as a DBA is essential.

System Administrators

Installing and maintaining a TMS network requires expertise in the following skill areas:

- UNIX operating systems

- Creating and managing user accounts and groups

- Installing Oracle database software and patches

- Identifying space on a file system for Oracle database tablespaces

- Setting and using environment variables

- Microsoft Windows operating systems

- Creating and managing user accounts and groups

- Installing Oracle software

- Managing settings through the Control Panel and Administrative Tools

- Managing network printers

- Creating services

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Finding Information and Patches on My Oracle Support

Your source for the latest information about Oracle Thesaurus Management System is Oracle Support's self-service Web site My Oracle Support (formerly MetaLink).

Before you install and use Oracle Thesaurus Management System, always visit the My Oracle Support Web site for the latest information, including alerts, White Papers, installation verification (smoke) tests, bulletins, and patches.

Creating a My Oracle Support Account

You must register at My Oracle Support to obtain a user name and password account before you can enter the Web site.

To register for My Oracle Support:

1. Open a Web browser to https://support.oracle.com.

2. Click the Register link to create a My Oracle Support account. The registration page opens.

3. Follow the instructions on the registration page.

Signing In to My Oracle Support

To sign in to My Oracle Support:

1. Open a Web browser to https://support.oracle.com.

2. Click Sign In.

3. Enter your user name and password.

4. Click Go to open the My Oracle Support home page.

Finding Information on My Oracle Support

There are many ways to find information on My Oracle Support.

Searching by Article ID

The fastest way to search for information, including alerts, White Papers, installation verification (smoke) tests, and bulletins is by the article ID number, if you know it.

To search by article ID:

1. Sign in to My Oracle Support at https://support.oracle.com.

2. Locate the Search box in the upper right corner of the My Oracle Support page.

3. Click the sources icon to the left of the search box, and then select Article ID from the list.

4. Enter the article ID number in the text box.

5. Click the magnifying glass icon to the right of the search box (or press the Enter key) to execute your search.
The Knowledge page displays the results of your search. If the article is found, click the link to view the abstract, text, attachments, and related products.

Searching by Product and Topic

You can use the following My Oracle Support tools to browse and search the knowledge base:

- Product Focus — On the Knowledge page under Select Product, type part of the product name and the system immediately filters the product list by the letters you have typed. (You do not need to type "Oracle.") Select the product you want from the filtered list and then use other search or browse tools to find the information you need.

- Advanced Search — You can specify one or more search criteria, such as source, exact phrase, and related product, to find information. This option is available from the Advanced link on almost all pages.

Finding Patches on My Oracle Support

Be sure to check My Oracle Support for the latest patches, if any, for your product. You can search for patches by patch ID or number, or by product or family.

To locate and download a patch:

1. Sign in to My Oracle Support at https://support.oracle.com.

2. Click the Patches & Updates tab. The Patches & Updates page opens and displays the Patch Search region. You have the following options:

- In the Patch ID or Number field, enter the number of the patch you want. (This number is the same as the primary bug number fixed by the patch.) This option is useful if you already know the patch number.

- To find a patch by product name, release, and platform, click the Product or Family link to enter one or more search criteria.

3. Click Search to execute your query. The Patch Search Results page opens.

4. Click the patch ID number. The system displays details about the patch. In addition, you can view the Read Me file before downloading the patch.

5. Click Download. Follow the instructions on the screen to download, save, and install the patch files.

Finding Oracle Documentation

The Oracle Web site contains links to all Oracle user and reference documentation. You can view or download a single document or an entire product library.

Finding Oracle Health Sciences Documentation

To get the latest user documentation for Oracle Health Sciences applications, including an HTML version of this guide, go to the Oracle Health Sciences documentation page at:

http://www.oracle.com/technetwork/documentation/hsgbu-clinical-407519.html

Note:
Always check the Oracle Health Sciences Documentation page to ensure you have the latest updates to the documentation.

Finding Other Oracle Documentation

To get user documentation for other Oracle products:

1. Go to the following Web page:
http://www.oracle.com/technology/documentation/index.html

Alternatively, you can go to http://www.oracle.com, point to the Support tab, and then click Documentation.

2. Scroll to the product you need and click the link.

3. Click the link for the documentation you need.

Related Documents

This section lists the documents in the Oracle Thesaurus Management System documentation set. The most recent version of each guide is posted on the Oracle Web site; see "Finding Oracle Health Sciences Documentation".

- Oracle Thesaurus Management System Installation Guide

- Oracle Thesaurus Management System User's Guide

In addition, Oracle Thesaurus Management System customers can request a copy of the Oracle Thesaurus Management System Technical Reference Manual from Oracle Support.

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Preparing to Install Oracle Thesaurus Management System

This chapter includes:

- Section 1.1, "Installation and User Documentation"

- Section 1.2, "Architecture"

- Section 1.3, "Technology Stack"

- Section 1.4, "Downloading and Extracting the Software"

- Section 1.5, "Using the Silent Installer"

- Section 1.6, "Reviewing the Installation Log Files"

- Section 1.7, "Choosing a Character Set"

- Section 1.8, "Applying Oracle Critical Patch Updates"

- Section 1.9, "Applying the Latest TMS Patch Set"

OPA and OLSA Internal Names

The Oracle Thesaurus Management System (TMS) product is now part of the Oracle Health Sciences Global Business Unit (HSGBU). TMS was formerly part of the Oracle Life Sciences Applications (OLSA) and the Oracle Pharmaceutical Applications (OPA) organizations. During the installation you will see references to OLSA and OPA in the software (such as in directory names, file names, and screen text) that have not been changed.

1.1 Installation and User Documentation

Be aware of these additional resources.

1.1.1 My Oracle Support Articles

Visit the My Oracle Support website for the most up-to-date installation information, including alerts, release notes, bulletins, White Papers, and patches; see "Finding Information and Patches on My Oracle Support".

The My Oracle Support website includes these important installation topics:

- Oracle Thesaurus Management System 5.1 Release Notes (Article ID 1931236.1)

- OLSA Known Installation and Configuration Issues (Article ID 1572864.1)

- Oracle Clinical, Oracle Clinical Remote Data Capture, and Oracle Thesaurus Management System Security Configuration Guide available with the user documentation.

- Oracle Health Sciences (Life Sciences/ Pharmaceutical/ Healthcare) Supported Technology Stacks (Article ID 180430.1)

- Oracle Thesaurus Management System Installation Verification Test (Article ID 398443.1)

- Oracle Thesaurus Management System Patches (Article ID 132626.1)

- TMS Product Information Center page (Article ID 1343408.1): Check here for new notes and White Papers, including the performance White Paper and the Installation Verification Test, which are not available at the time of publication of this document.

1.1.2 User Documentation

The most current TMS user documentation is located on oracle.com at:

http://www.oracle.com/technetwork/documentation/hsgbu-clinical-407519.html

TMS user documentation includes:

- Oracle Thesaurus Management System Installation Guide

- Oracle Thesaurus Management System User's Guide

- Oracle Clinical, Oracle Clinical Remote Data Capture, and Oracle Thesaurus Management System Security Configuration Guide

In addition, Oracle Thesaurus Management System customers can request a copy of the Oracle Thesaurus Management System Technical Reference Manual from Oracle Support.

1.2 Architecture

The architecture for TMS consists of three tiers: the database tier, the application tier, and the client tier.

Figure 1-1 illustrates the architecture and technology stack for TMS.

Figure 1-1 TMS Architecture and Technology Stack

The database tier in a TMS environment includes the Oracle Database 12c Release 1 (12.1.0.1) software and the TMS database(s). In past releases, the database tier was called the back end.

The application tier includes:

- TMS Forms Server — The Forms Server performs all forms processing, communicates the display changes to the client, and calls forms to query, update, select, and delete data from the database.

- TMS Server Code— The Server Code consists of scripts used to create TMS databases.

- TMS Reports Server — The Reports Server runs most batch reports, schedules all jobs, and creates PDF output for reports. Most TMS reports interface with the TMS Reports Server.

- TMS Browser — The TMS Browser runs in a browser and does not required a plug-in. It allows users to browse dictionary terms and, if fully integrated with a clinical data system like Oracle Clinical, source terms and associated external system information.

The client tier communicate users' keystrokes and mouse movements to the application tier. It requires a browser and Browser Native Oracle JVM.

Figure 1-2 Oracle Thesaurus Management System Network Topology

Figure 1-2 shows how the Oracle Thesaurus Management System components and technology stack are related and provides an example of how the product can be installed. The left side of the Application Tier—APPHOST1—is a standard installation, while the whole—with APPHOST2—shows a multi-node middle tier installation using Oracle Clusterware.

In the client tier, end users' browsers communicate via HTTPS with the Oracle HTTP Server (OHS), which is located inside a firewall. When users log in, OHS detects the product they logged in to and consults formsweb.cfg to connect them to the appropriate application tier service.

The application tier comprises Oracle Application Server and Oracle WebLogic Server. The integrated tier has two domains:

- FRDomain includes the Oracle Forms runtime service and Forms Server, and the Oracle Reports Server and engine, which run Oracle Thesaurus Management System forms and reports. It also includes the WebLogic Server Admin Server and Oracle Enterprise Manager.
The Oracle Application Server domain must be named FRDomain and must use port number 7001.

- OPADomain includes the WebLogic Server Administration Console, WebLogic Server Java, and OpaServer1, which are required to run the TMS HTML Browser and TMS reports. It also contains the database connections. Note that when you install the Oracle Enterprise Manager in the FRDomain, it serves for monitoring the OPADomain as well.
The TMS Installer automatically creates the OPADomain. OPADomain must use port number 7101.

You can distribute the application tier over multiple nodes in a network using Oracle Clusterware. The Admin Server is required only on the primary node.

The WebLogic Server Node Manager exists outside the domains on the host. The Oracle Thesaurus Management System Installer automatically stops the Node Manager before each Java deployment and starts the Node Manager afterward so you do not need to do that.

The database tier includes Oracle Database with Oracle Thesaurus Management System. The diagram shows a distributed installation integrated with Oracle Clinical using Oracle Real Application Clusters (RAC); this is one example of how it can be installed.

1.3 Technology Stack

The following tables list technology stack requirements for the database tier, the application tier, and the client tier:

- Table 1-1, "Oracle Thesaurus Management System Database Tier Technology Stack"

- Table 1-2, "Oracle Thesaurus Management System Application Tier Technology Stack"

- Table 1-3, "Oracle Thesaurus Management System Client Tier Technology Stack"

The sections following the tables provide additional information about requirements.

- Section 1.3.1, "Planning a TMS Database Installation"

- Section 1.3.2, "Planning a TMS Application Tier Installation"

- Section 1.3.3, "Planning a TMS Client Installation"

For updates to the technology stack, see Oracle Health Sciences (Life Sciences/ Pharmaceutical/ Healthcare) Supported Technology Stacks (Article ID 180430.1) on My Oracle Support; see "Finding Information on My Oracle Support.".

Table 1-1 Oracle Thesaurus Management System Database Tier Technology Stack

Component

Supported Version

Operating System

Oracle Linux 6.4 with Unbreakable Enterprise Kernel (UEK) 64 bit ; (US English)

Oracle Solaris SPARC 10 and 11; 64-bit architecture (US English)

HP Itanium 11.31; 64-bit architecture

Windows Server 2008 Release 2, Service Pack 1; 64-bit architecture (US English)

Oracle Database

12c Release 1 (12.1.0.1) Enterprise Edition 64-bit

Compiler

For Oracle Linux x86-64: GNU GCC-4.4.6

For Oracle Solaris SPARC 10 and 11: Sun Studio 12

For HP Itanium: HP C/aC++ for Integrity Servers B3910B A.06.27

Optional Software

Oracle Real Application Clusters (RAC) on Sun, HP, and Linux, including Exadata

Oracle Virtual Machine (OVM) 3.2

Table 1-2 Oracle Thesaurus Management System Application Tier Technology Stack

Component

Supported Version

Operating System

Microsoft Windows Server 2008 Release 2; Service Pack 1 or 2; 64-bit architecture

Oracle Application Server

Oracle Application Server 11g Release 2 (11.1.2.1.0); 64-bit architecture

Oracle WebLogic Server

Oracle WebLogic Server 11g R1 (10.3.6)

Oracle ADF

Oracle Application Developer's Framework 11g R2 (11.1.2.4)

Oracle Java Development Kit (JDK)

Oracle Java Development Kit 1.6.0_65, also known as JDK 6 Update 65.

Table 1-3 Oracle Thesaurus Management System Client Tier Technology Stack

Component

Supported Version

Operating Systems

Microsoft Windows 7; Service Pack 1; 32-bit or 64-bit architecture (US English)

Microsoft Windows Server 2008; Release 2; Service Pack 1; 64-bit architecture (US English)

Microsoft Windows 8/8.1; 64-bit architecture

Mobile Operating Systems

iOS 7.1.2—iPad and OS X 10.7.5—for TMS Browser only

Supported Browsers

Microsoft Internet Explorer versions depend on the operating system:

- Microsoft Windows 7 (32-bit): Internet Explorer 9

- Microsoft Windows 7 (64-bit): Internet Explorer 9, 10, or 11

- Microsoft Windows Server 2008: Internet Explorer 9, 10, or 11

- Microsoft Windows 8 (64-bit): Internet Explorer 10 or 11

Safari 7.0.3 on iOS 7.1.2, for TMS Browseronly

Adobe Reader

Releases 8x, 9.x, 10.x, 11.x (US English). Required for viewing PDF reports

Oracle Java Runtime Environment (JRE)

Java SE 7 Update 65 (Standard Edition, Version 1.7.0.65

1.3.1 Planning a TMS Database Installation

This section describes the hardware and software requirements for the TMS database tier.

Note:
It is possible to install more than one version of TMS on the same machine in UNIX. Each is installed in its own release-specific directory.

1.3.1.1 Character Set Requirements

For information about the guidelines and requirements for character sets, see Section 1.7, "Choosing a Character Set."

1.3.1.2 Critical Patch Update

You must obtain the latest Critical Patch Update (CPU) approved by Oracle Health Sciences from My Oracle Support and install it on each database and application tier server computer; see Section 1.8, "Applying Oracle Critical Patch Updates".

1.3.1.3 Database Tier Operating System Requirements

See Table 1-1, "Oracle Thesaurus Management System Database Tier Technology Stack" for basic information.

To verify that your system fits the requirements listed in Table 1-1, "Oracle Thesaurus Management System Database Tier Technology Stack" do the following in UNIX or Windows:

To verify the operating system details, enter the following command:

UNIX To verify UNIX operating system details, enter the following command:

uname -a

In addition, to verify the update version for Linux, enter the following command:

cat /etc/issue

Windows To verify Windows operating system details, navigate to the Control Panel, then System and Security, then System.

1.3.1.4 Database Tier System Requirements

For database tier system requirements, see the Oracle Database 12c Release 1 (12.1.0.1) Installation Guide for your respective operating system.

1.3.1.5 Oracle Database Requirement: Oracle Text Option

Choose to install the Oracle Database Text Option. It is required for TMS. Oracle Database includes the Oracle Text Option, but note that installing and using it requires purchasing a separate license.

1.3.2 Planning a TMS Application Tier Installation

See Table 1-2, "Oracle Thesaurus Management System Application Tier Technology Stack" for basic information.

The application tier includes the Forms Server and Reports Server components as well as WebLogic Server.

Note:
The default application tier installation uses HTTPS.

1.3.2.1 Character Set Requirements

For information about the guidelines and requirements for character sets, see Section 1.7, "Choosing a Character Set"

1.3.2.2 Critical Patch Update

You must obtain the latest Critical Patch Update (CPU) approved by Oracle Health Sciences from My Oracle Support and install it on each database and application tier server computer; see Section 1.8, "Applying Oracle Critical Patch Updates".

1.3.2.3 Permanent IP Address

Each server computer must have a permanent IP address.

1.3.2.4 Installing TMS with Oracle Clinical

You can install TMS and Oracle Clinical on the same application tier or on different application tiers. To integrate Oracle Clinical and TMS, both products must be installed on the same database.

Oracle recommends installing Oracle Clinical before TMS.

If you install both products on the same application server, you do not need to install the TMS Reports Server.

1.3.3 Planning a TMS Client Installation

In addition to the software noted in Table 1-3, "Oracle Thesaurus Management System Client Tier Technology Stack", a client requires an intranet or internet connection. In addition, see Section 8.7, "Setting Up Client Computers."

1.4 Downloading and Extracting the Software

- Section 1.4.1, "Creating Staging Areas"

- Section 1.4.2, "Downloading and Extracting the Oracle Clinical 5.1 and Oracle Thesaurus Management System 5.1 media pack"

- Section 1.4.3, "Downloading and Extracting Patches from My Oracle Support"

- Section 1.4.4, "Downloading Oracle Java Development Kit"

- Section 1.4.6, "Downloading Adobe Reader"

1.4.1 Creating Staging Areas

Oracle recommends creating one staging area on the database server and another on the application server. In each staging area, create one directory for each media pack disk, patch, or other software unit that needs to be downloaded to that server, as shown in Table 1-4, "Software to Download to Database Server Staging Area" and Table 1-5, "Software to Download to Application Server Staging Area".

Give each directory a logical name such as the media pack disk or patch name (not part or patch number) to make instructions later in this guide easier to follow.

1.4.1.1 Database Server Staging Area

Table 1-4, "Software to Download to Database Server Staging Area" shows which software to download to the database server staging area.

Table 1-4 Software to Download to Database Server Staging Area

Disk or Patch Name

Source

Oracle Thesaurus Management System 5.1.0.0.0 Documentation—The latest versions are posted at http://www.oracle.com/technetwork/documentation/hsgbu-clinical-407519.html.

Media pack or www.oracle.com

Oracle Thesaurus Management System 5.1.0.0.0

Media pack

Oracle Database 12c Release 1 (12.1.0.1) — Linux x86-64

Media pack

Oracle Database 12c Release 1 (12.1.0.1) — Solaris Sparc 64

Media pack

Oracle Database 12c Release 1 (12.1.0.1) — HP IA

Media pack

Oracle Database 12c Release 1 (12.1.0.1) — Windows x64

Media pack

1.4.1.2 Application Server Staging Area

Table 1-5, "Software to Download to Application Server Staging Area" shows which software to download to the application server staging area.

Table 1-5 Software to Download to Application Server Staging Area

Disk or Patch Name

Source

Oracle Thesaurus Management System 5.1.0.0.0 Documentation—The latest versions are posted at http://www.oracle.com/technetwork/documentation/hsgbu-clinical-407519.html.

Media pack or www.oracle.com

Oracle Thesaurus Management System 5.1.0.0.0

Media pack

Oracle WebLogic Server 11gR1 (10.3.6) Generic and Coherence

Media pack

Oracle Application Development Runtime 11g Patch Set 5 (11.1.1.6) (also known as Application Developer's Framework or ADF)

Media pack

ADF 11.1.2.4 patches 16546129 and 16546157

My Oracle Support

Internet Explorer 11 compatibility patch for ADF 11.1.2.4 (patch 18277436) or its successor; consult My Oracle Support document Supportability on Internet Explorer 11 (IE11) with Oracle ADF (ID 1599898.1).

My Oracle Support

Oracle Forms and Reports 11gR2 (11.1.2.1.0) for Microsoft Windows x64 (64-bit)

Media pack

Oracle Application Server (Forms and Reports) patch 12632886

My Oracle Support

Oracle Java Development Kit 1.6.0_65, also known as JDK 6 Update 65 (patch 17046855); see Section 1.4.4, "Downloading Oracle Java Development Kit."

My Oracle Support

Java Runtime Environment (JRE) 1.7.0.65; see Section 1.4.5, "Downloading the Java Runtime Environment."

www.oracle.com

Adobe Reader

http://www.adobe.com/

1.4.2 Downloading and Extracting the Oracle Clinical 5.1 and Oracle Thesaurus Management System 5.1 media pack

Note:
To receive a physical media pack with all the required DVDs, contact Oracle Support. To expedite your request you can either call Oracle Support directly or open a Service Request (SR) selecting problem category: Version Update Request.

To download the software:

1. Go to http://edelivery.oracle.com and log on.

2. From the Select a Product Pack drop-down list, select Health Sciences.

3. From the Platform drop-down list, select the appropriate operating system.

4. Click Go.

5. Select Oracle Clinical 5.1 and Oracle Thesaurus Management System 5.1 media pack for Your_Operating_System and click Continue.

6. Download each disk into the appropriate directory in the appropriate staging area as shown in Table 1-4, "Software to Download to Database Server Staging Area". Each download consists of a single file named part_number.zip.

7. Extract each part_number.zip file into a meaningfully named directory.

8. For the Oracle Thesaurus Management System software, extract application_server.zip.

1.4.3 Downloading and Extracting Patches from My Oracle Support

To download a patch from My Oracle Support:

1. Go to My Oracle Support at https://support.oracle.com and sign in.

2. Click the Patches & Updates tab, then enter the patch number in the Patch Name or Number is field and click Search.

3. Click the link for your operating system and download the patch file to the appropriate directory in the staging area.

4. Extract the .zip file.

1.4.4 Downloading Oracle Java Development Kit

To download and install JDK 1.6.0_65:

1. Go to My Oracle Support at https://support.oracle.com and sign in.

2. In the Search Knowledge Base field in the upper right, enter: 1439822.1
A page appears with a list of documents.

3. Click the link All Java SE Downloads on MOS [Article ID 1439822.1].

4. Scroll down to the list of JDK versions to Oracle JDK 6 Update 65 (Patch ID 17046855).

Note:
Check Oracle Health Sciences (Life Sciences/ Pharmaceutical/ Healthcare) Supported Technology Stacks (Article ID 180430.1) on My Oracle Support to see if a more recent versions are supported; see "Finding Information on My Oracle Support".

5. Click the patch number link.

6. Select Microsoft Windows x64 (64-bit) and click ReadMe to read the release notes and Download to download the patch.

Installation instructions are in Section 5.3, "Install Oracle Java Development Kit."

1.4.5 Downloading the Java Runtime Environment

Oracle Thesaurus Management System requires that Java Standard Edition (SE) Runtime Environment (JRE) 1.7.0.65—also known as JRE 7 Update 65—exist on the user's computer.

To download JRE:

1. On the application server, go to the following Oracle Web site:
http://www.oracle.com/technetwork/java/javase/downloads/index.html

2. Under Java SE 7u65, click the Download button for JRE.

3. Select the Windows x86 Offline version.

Note:
This is the version for 32-bit browsers (not operating systems). The default browser for Windows machines is 32-bit, but Windows machines also come with a 64-bit version. To support the 64-bit version, you must either customize your Launch page to point to sunjpi64.exe or instruct users with 64-bit browsers to download the 64-bit version of JRE from the link in Step 1.

4. Download it to the staging area in a recognizably named directory.

1.4.6 Downloading Adobe Reader

Adobe Reader is required on the Reports Server and on client computers to read PDF reports. Download it from http://www.adobe.com. At this time no particular version is required.

1.5 Using the Silent Installer

You can run any of the Oracle Universal Installers—including the Oracle Thesaurus Management System Installers—in silent mode. This may be useful to promote uniform installations in many sites or on many computers.

TMS ships with .rsp (response) files that include the parameter prompts and sample parameter values for each component. They are located on the media pack's Oracle Thesaurus Management System 5.1 disk in TMS\application_server.zip\Disk1\ stage\Response, and include:

- oracle.pharma.tms.db.install.Master.rsp

- oracle.pharma.tms.db.install.Slave.rsp

- oracle.pharma.tms.db.register.Custom.rsp

- oracle.pharma.tms.db.upgrade.Master.rsp

- oracle.pharma.tms.db.upgrade.Slave.rsp

- oracle.pharma.tms.frontend.Custom.rsp

- oracle.pharma.tms.reportserver.Complete.rsp

- oracle.pharma.tms.server.Complete.rsp

For information on the parameters, see the corresponding section of this guide.

1. Open the file in a text editor and enter values directly.

2. Run the file.
In UNIX:

./runInstaller -responseFile response_file_name

In Windows (as an administrator):

setup.exe -responseFile response_file_name

3. When you run the file at each location, edit the local parameters as required.

Alternatively, you can run the Installer once, entering values manually, and record the process to create a response file.

Run the file.

In UNIX:

./runInstaller -record -destinationFile response_file_name

In Windows (as an administrator):

setup.exe -record -destinationFile response_file_name

For more information see Oracle Universal Installer documentation at:

- http://docs.oracle.com/cd/E18790_01/doc/em.112/e12255/oui3_response_files.htm

- http://docs.oracle.com/cd/E11882_01/install.112/e24321/app_nonint.htm#CIHEGBII

1.6 Reviewing the Installation Log Files

During the installation of an Oracle Health Sciences component, the Oracle Universal Installer generates the following log file:

installActions.log

This log file records the actions of the Installer — such as loading information from the CD to the Application or Database Server — and is useful for diagnosing problems with the Installer. You should include the log file if you report any problems that occur when installing an Oracle Health Sciences component.

On a Windows installation, the log files are located at:

\Oracle\Inventory\logs

For example:

C:\Program Files\Oracle\Inventory\logs

On a UNIX installation, the log files are located at:

$ORACLE_BASE/oraInventory/logs

For example:

/u01/app/oraInventory/logs

The current log file is installActions.log. All previous log generations have a timestamp appended to the name. For example:

installActions2013-04-30_11-22-52AM.log

1.7 Choosing a Character Set

Oracle Health Sciences supports certain character sets for each product or each combination of integrated products. For TMS, Oracle strongly recommends that you use the AL32UTF8 character set. TMS also supports UTF8, US7ASCII, WE8ISO8859P1, or any single byte character set.

TMS uses the NLS_LANG environment variable to control the language, territory, and character set used for database connections. The NLS_LANG variable concatenates the three components as LANGUAGE_TERRITORY.CHARSET.

The TMS Installer sets the default value for the TMS application tier to AMERICAN_AMERICA.AL32UTF8. You set the value during database creation outside the Installer.

- You must set the CHARSET component of the NLS_LANG variable to match the character set of the database.

- You must use the same character set on the database tier and the application tier. If you select US7ASCII for the database tier and AL32UTF8 or UTF8 for the application tier, for example, Oracle Clinical stores some special characters incorrectly in the database.

1.8 Applying Oracle Critical Patch Updates

Every quarter, Oracle provides Critical Patch Updates (CPUs) to address security vulnerabilities. These patches are cumulative: each one contains all the fixes contained in the previous patch.

Check My Oracle Support article ID 121863.1, Oracle Health Sciences Supported Technology Stacks, for the latest CPU patch tested with Oracle Health Sciences applications, with a link to the separate article about each one. Install these patches on every computer with an Oracle Home.

1.9 Applying the Latest TMS Patch Set

Check Oracle Thesaurus Management System Patches (Article ID 132626.1) on My Oracle Support for the latest patch set and apply it. See the patch set release notes for more information.

2 Installing Oracle Database on UNIX

This chapter includes:

- Section 2.1, "Performing Prerequisite Tasks for Installing Oracle Database"

- Section 2.2, "Installing Oracle Database"

If you are upgrading to Release 5.1, see Chapter 7.

For database tier system requirements, see the Oracle Database Installation Guide for your operating system at http://docs.oracle.com/cd/E16655_01/nav/portal_11.htm.

Critical Patch Updates See Section 1.8, "Applying Oracle Critical Patch Updates."

Oracle Database 12.1.0.1  includes many new features including multitenancy, which allows you to create one or more pluggable databases (PDBs) contained in a single root or container database (CDB). You can install Oracle Thesaurus Management System on either a pluggable database or a non-CDB database (as in 11g). For more information on multitenancy, see http://docs.oracle.com/database/121/CNCPT/cdbovrvw.htm.

Oracle recommends learning about these new features in Oracle White Paper Plug into the Cloud with Oracle Database 12c at http://www.oracle.com/technetwork/database/plug-into-cloud-wp-12c-1896100.pdf and, for more details, the Oracle® Database New Features Guide 12c Release 1 (12.1) at http://docs.oracle.com/database/121/NEWFT/toc.htm.

2.1 Performing Prerequisite Tasks for Installing Oracle Database

To ensure that your platform meets the minimum requirements for installing Oracle Database, you must perform the following preparatory tasks:

- Create Owners, Groups, and Mount Points

- Configure Kernel Resources and Adjust Operating System Environment

- Install Latest Operating System Patches

2.1.1 Create Owners, Groups, and Mount Points

To create the software owner, required groups, and mount points:

1. Create the software owner and groups:

- Create a UNIX user to own the Oracle software. Typically, the user name is oracle.

- Create two groups: one is the Oracle Inventory group; the other is the operating system DBA group. Typically, the group names are oinstall and dba, respectively.

2. Create mount points owned by the oracle user:

- Create a software mount point of at least 10 GB.

- Create mount points to hold the database files, control files, and log files, respectively.

3. Test permissions. Ensure that the oracle user can write to the new mount points and all subdirectories.

4. Ensure that the oinstall group can write to the new mount points and all subdirectories.

2.1.2 Configure Kernel Resources and Adjust Operating System Environment

The performance of Oracle Database relies on proper tuning of operating system parameters. In addition, if you are creating several Oracle instances, you might have to increase the amount of shared memory and semaphores on the system by setting kernel parameters.

For details, see the section on configuring kernel parameters in the of the Oracle Database 12c Installation Guide for your operating system available here: http://docs.oracle.com/database/121/nav/portal_11.htm

2.1.3 Install Latest Operating System Patches

Download and install the latest operating system patches required for Oracle, if necessary. Review the latest platform-specific install bulletins for Oracle Database 12c Release 1 (12.1.0.1).

2.2 Installing Oracle Database

This section includes:

- Install Oracle Database 12.1.0.1 Enterprise Edition

- Install Oracle Database Examples

2.2.1 Install Oracle Database 12.1.0.1 Enterprise Edition

To install Oracle Database 12.1.0.1:

1. Locate the Oracle Database software in the staging area on the database server where you downloaded it; see Section 1.4, "Downloading and Extracting the Software."

2. Install Oracle Database 12c Release 1 (12.1.0.1). For instructions see the readme file and the section "Running Oracle Universal Installer" in the Oracle Database Installation Guide for your operating system at http://docs.oracle.com/cd/E16655_01/nav/portal_11.htm.

3. Choose to install the Enterprise Edition.

4. Choose the following database options that are required for Oracle Thesaurus Management System:

- Oracle XML DB

- Oracle JVM

- Oracle InterMedia

- Oracle Text

2.2.2 Install Oracle Database Examples

Oracle Database Examples includes the following items:

- Oracle JDBC Development Drivers (required)

- Oracle Database Examples (required)

- Oracle Product Demonstrations (optional)

Note:
You do not need to install any of the sample schemas. They are not required for either Oracle Clinical or Oracle Thesaurus Management System. You can add them later if you change your mind.

To install Oracle Database Examples:

1. Extract the zip file containing Oracle Database Examples in the examples directory.

2. Start Oracle Universal Installer from the examples directory.

./runInstaller

Or, if the database server has multiple Oracle Homes, then enter:

./runInstaller -invPtrLoc ORACLE_HOME/oraInst.loc

For example:

./runInstaller -invPtrLoc /u01/app/oracle/product/121010_qa/oraInst.loc

3. Accept all the default values during the installation.

For more information about installing software and various Oracle product demonstrations from the Oracle Database Examples media, see the Oracle Database Examples Installation Guide at http://docs.oracle.com/cd/E16655_01/nav/portal_11.htm.

3 Installing Oracle Database on Windows

This chapter describes how to set up a new Oracle Database Server on a Windows computer.

- Section 3.1, "Install Oracle Database 12.1.0.1 Enterprise Edition"

- Section 3.2, "Install Oracle Database Examples"

If you are upgrading to Release 5.1, see Chapter 7.

For database tier system requirements, see the Oracle Database Installation Guide for your operating system at http://docs.oracle.com/cd/E16655_01/nav/portal_11.htm.

Critical Patch Updates See Section 1.8, "Applying Oracle Critical Patch Updates."

Oracle Database 12.1.0.1  includes many new features including multitenancy, which allows you to create one or more pluggable databases (PDBs) contained in a single root or container database (CDB). You can install Oracle Thesaurus Management System on either a pluggable database or a non-CDB database (as in 11g). For more information on multitenancy, see http://docs.oracle.com/database/121/CNCPT/cdbovrvw.htm.

Oracle recommends learning about these new features in Oracle White Paper Plug into the Cloud with Oracle Database 12c at http://www.oracle.com/technetwork/database/plug-into-cloud-wp-12c-1896100.pdf and, for more details, the Oracle® Database New Features Guide 12c Release 1 (12.1) at http://docs.oracle.com/database/121/NEWFT/toc.htm.

3.1 Install Oracle Database 12.1.0.1 Enterprise Edition

To install Oracle Database 12.1.0.1:

1. Locate the Oracle Database software in the staging area on the database server where you downloaded it; see Section 1.4, "Downloading and Extracting the Software."

2. Install Oracle Database 12.1.0.1. For instructions see the patch readme file and see the 12.1.0.1 Oracle Database Installation Guide at http://docs.oracle.com/database/121/NXDQI/toc.htm#NXDQI120.

3. Choose to install the Enterprise Edition.

4. Choose the following database options that are required for Oracle Thesaurus Management System:

- Oracle XML DB

- Oracle JVM

- Oracle InterMedia

- Oracle Text

3.2 Install Oracle Database Examples

Oracle Database Examples includes the following items:

- Oracle JDBC Development Drivers (required)

- Oracle Database Examples (required)

- Oracle Product Demonstrations (optional)

Note:
You do not need to install any of the sample schemas. They are not required for either Oracle Clinical or Oracle Thesaurus Management System. You can add them later if you change your mind.

To install Oracle Database Examples:

1. Extract the zip file containing Oracle Database Examples in the examples directory.

2. Run the following file as an administrator:
examples\setup.exe

3. Accept all the default values during the installation.

For more information about installing software and various Oracle product demonstrations from the Oracle Database Examples media, see the Oracle Database Examples Installation Guide at http://docs.oracle.com/database/121/EXMPL/toc.htm.

4 Creating a TMS Database

Your Oracle Database and TMS Server installations must be complete before you install the TMS database.

Single TMS Database or Master Database in a Distributed Environment If you plan to use only one TMS database, or if you are using replication to distribute data among multiple databases, do the following on the single or master database:

- Section 4.1, "Restart Computer and Stop All Servers and Services"

- Section 4.2, "Installing the TMS Database Server Code"

- Section 4.3, "Review Database Requirements and Recommendations (All Databases)"

- Section 4.4, "Install TMS Database Objects (All Databases)"

- Section 4.5, "Create a TMS Administrator User Account (All Databases)"

- Section 4.6, "Register Databases Integrated with Oracle Clinical" (This step is required only if you are integrating TMS with Oracle Clinical.)

- Section 4.7, "Load Dictionaries (Single or Master Database)"

- Section 4.8, "Complete Distributed Environment Setup" (This step is required only in a distributed environment.)

Local (Slave) Databases If you are installing multiple databases in a distributed environment, perform the steps in the following sections on each local (slave) database:

- Section 4.1, "Restart Computer and Stop All Servers and Services"

- Section 4.3, "Review Database Requirements and Recommendations (All Databases)"

- Section 4.4, "Install TMS Database Objects (All Databases)"

- Section 4.5, "Create a TMS Administrator User Account (All Databases)"

- Section 4.8, "Complete Distributed Environment Setup" This section includes tasks to be done on both the master and slave databases.

4.1 Restart Computer and Stop All Servers and Services

Restart the computer and then stop all servers and services:

1. Restart the computer.

2. In the Windows Services control panel, find Oracle Node Manager service and stop it.

3. From the Windows Start menu, go to All Programs, then Oracle Classic_asinst_1, then:

- Forms Services, then Stop WLS_FORMS

- Reports Services, the Stop WLS_REPORTS

- Stop Admin Server: NOTE: This is required if you are installing the Front End and the Server (database server code), but if you are installing the Report Server the Admin Server must be running.

4.2 Installing the TMS Database Server Code

TMS database server code must be installed on Windows on the same computer as the TMS Front End. You must install the server first, then create one or more databases, and then install the Front End.

4.2.1 Gather Required Information

Make sure you have the information below, which is arranged in the order it is prompted for by the Installer during a fresh installation. The order for upgrades is somewhat different.

Note:
You must install the Oracle Thesaurus Management System database server before you install or upgrade the Oracle Thesaurus Management System database.

1. OPA Home: the directory where Oracle Thesaurus Management System will be installed; by default:
C:\opapps51

2. Home Details: Select the Oracle Home that corresponds to the Oracle Forms and Reports home, similar to C:\oracle\middleware\Oracle_FRHome1.

4.2.2 Start the TMS Server Installer

To install the TMS Server:

1. Log in as a user with system administrator privileges.

2. In the staging area, locate the directory where you downloaded and extracted Oracle Thesaurus Management System (see Section 1.4, "Downloading and Extracting the Software").

3. Run the following file as an administrator:
Disk1\install\setup.exe

The Installer opens to the Welcome screen.

Note:
See Section 1.5, "Using the Silent Installer" for instructions for running the Installer as a file with pre-entered parameter values.

Note:
Although there is a button for deinstalling products on the Welcome screen, Oracle does not support using the Installer to deinstall Oracle Thesaurus Management System.

4. In the Select a Product to Install page, select Oracle Thesaurus Management System Server 5.1.0.0.x.

4.2.3 Attend to the TMS Database Server Code Installation Screens

The Installer guides you through the installation and configuration of the TMS database server. Provide the information you assembled in "Gather Required Information."

4.3 Review Database Requirements and Recommendations (All Databases)

A TMS database can be installed on Windows or UNIX. You must install the TMS database server (always on Windows) before installing a TMS database.

Before you install the TMS database component, review the following requirements and recommendations — such as service names, tablespace sizes, memory management, and initialization parameters — for each TMS database you plan to install.

4.3.1 Start with a New Database Instance

Oracle recommends that you set up a new database instance so that neither TMS nor its installation process interferes with other applications. However, you can install TMS on an existing database instance.

4.3.2 Accept Connections as a Service

Choose to configure the database to accept connections as a service instead of a SID. Service name requirements for Oracle Thesaurus Management System include:

- The service name must be less than 15 characters long.

- It must not include the domain.

- It must be all lowercase.

Note:
If you are installing the Oracle Thesaurus Management System database on a pluggable Oracle 12.1.0.1 database (PDB), see My Oracle Support article ID 1910177.1, How To Configure TNS / SQLNET using the local_listener parameter for Pluggable Database In Oracle 12c, Allowing a SQLNET Connection to the PDB. See "Finding Information on My Oracle Support".

4.3.3 Check Required Tablespaces

Table 4-1 lists the tablespaces, along with their minimum size, required for TMS. Make sure the database contains these tablespaces. The best practice is to create them with the Autoextend On option, to avoid running out of space.

In addition, you may need to increase the minimum sizes for your installation.

Table 4-1 Required Tablespaces and Sizes

Tablespace

Minimum Size

SYSTEM

900 MB

TEMP

100 MB

UNDOTBS1

700 MB

USERS

500 MB

SYSAUX

600 MB

4.3.4 Use the Database Configuration Assistant

To create a new database, use the Oracle Database Configuration Assistant. For instructions about the Database Configuration Assistant, see the Oracle Database 12c Release 1 (12.1.0.1) documentation, including online help and the Oracle Database 12.1.0.1 Installation Guide for the appropriate operating system.

Note:

- Use the Custom Database installation option.

- The following parameters are not listed under All Initialization Parameters. Click Show Advanced Parameters to set the following parameters as described in Section 4.3.7, "Set Initialization Parameters":

- Db_cache_size

- Db_files

- Java_pool_size

- Job_queue_process

- Large_pool_size

- The Custom installation option allows access to the Database Storage screen, where you can expand the Tablespaces folder in the tree on the left side of the screen and edit the following tablespaces as required; see Section 4.3.3, "Check Required Tablespaces"

4.3.5 Select Required Components

When you create a TMS database, select the following mandatory components:

- Oracle Text

- Oracle JVM

- Oracle XML DB

4.3.6 Use Automatic Memory Management

Oracle recommends that you use Oracle Database 12c Release 1 (12.1.0.1)'s Automatic Memory Management feature for a new or an upgraded TMS database.

4.3.7 Set Initialization Parameters

Table 4-2 lists the required and recommended initialization parameters in the init.ora file for TMS. For those parameters that accept a value from within a range, the values in the table are minimum values.

Tip:
Table 4-2 arranges the parameters in alphabetical order. In the Database Configuration Assistant, you can select the Parameter column to sequence the parameters in the same order.

Note:
If you make any changes to the initialization parameters, be sure to stop and restart the database in order to acquire the new parameter settings.

Table 4-2 Required and Recommended Initialization Values in the init.ora File

Parameter

Value

Comments

COMPATIBLE

11.2.0.4

Specifies the release with which the Oracle server must maintain compatibility.

DB_BLOCK_SIZE

16384 bytes

You cannot change this value after you create the database.

DB_CACHE_SIZE

150 MB

Recommended value for 50 to 60 concurrent users. Adjust this value according to your organization's needs.

DB_DOMAIN

null

DO NOT set this value. In Release 5.1 onward, setting this value causes problems.

DB_FILES

200

Oracle adds needed space to the control files up to the number specified in the DB_FILES parameter.

EVENT

31151 trace name context forever, level 0x100

Required for HTML generation.

NOTE:

- This value is required only if you are integrating TMS with Oracle Clinical.

- Do not include the EVENT parameter when you create the database. Once the database is created, you can add the EVENT parameter to the init.ora file.

JAVA_POOL_SIZE

50 MB

Recommended value for 50 to 60 concurrent users. You can change the value of this parameter after installation.

JOB_QUEUE_PROCESSES

10

Developer-specific parameter. You can change the value of this parameter after installation.

LARGE_POOL_SIZE

50 MB

Recommended value for 50 to 60 concurrent users.

MEMORY_MAX_TARGET

1000 MB (minimum)

Adjust this value according to your organization's needs.

MEMORY_TARGET

1000 MB (minimum)

Adjust this value according to your organization's needs.

NLS_DATE_FORMAT

DD-MON-RRRR (default value)

Determines the format in which client applications running on the Windows server transfer date information to and from the database. The format must specify the year as RRRR.

NLS_LENGTH_SEMANTICS

BYTE

The CHAR value for this parameter is not supported.

OPEN_CURSORS

800 or greater

You can change the value of this parameter after installation.

OPTIMIZER_FEATURES_ENABLE

11.2.0.4

Acts as an umbrella for enabling a series of optimizer features based on an Oracle release number.

NOTE: Oracle Thesaurus Management System 5.1 is certified on Oracle Database 11g optimizer features; see Section 7.7, "Run Scripts to Gather Schema Statistics for the 11g Optimizer."

OPTIMIZER_MODE

CHOOSE

If you run TMS's statistics-gathering scripts, the CHOOSE value sets Oracle Optimizer to apply the execution plan that best minimizes response time. See Oracle Database documentation for more information. (CHOOSE is the default value when you specify 11.2.0.4 as the value of OPTIMIZER_FEATURES_ENABLE.)

PGA_AGGREGATE_TARGET

200 MB

Recommended value for 50 to 60 concurrent users. You can change the value of this parameter after installation.

REMOTE_LOGIN_PASSWORDFILE

EXCLUSIVE

The database must be set up to use password file authentication.

REMOTE_OS_AUTHENT

FALSE

NOTE: Do not include the REMOTE_OS_AUTHENT parameter when you create the database. After the database is created, you can add the REMOTE_OS_AUTHENT parameter to the init.ora file.

REMOTE_OS_AUTHENT is an obsolete parameter. When you start up a database that has this setting, TMS displays the following warning:

ORA-32004: obsolete and/or deprecated parameter(s) specified. ORACLE instance started.

You can safely ignore this warning.

SEC_CASE_SENSITIVE_LOGON

FALSE

Lets you enter passwords without case sensitivity.

SESSIONS

500 or greater

You can change the value of this parameter after installation.

SGA_MAX_SIZE

600 MB (minimum)

Recommended value for 50 to 60 concurrent users. Adjust this value according to your organization's needs.

SGA_TARGET

600 MB (minimum)

Recommended value for 50 to 60 concurrent users. Adjust this value according to your organization's needs.

SHARED_POOL_SIZE

150 MB (minimum)

Recommended value for 50 to 60 concurrent users. You can change the value of this parameter after installation.

UNDO_MANAGEMENT

AUTO

Specifies which undo space management mode the system uses. When set to AUTO, the instance starts in Automatic Undo Management (AUM) mode.

UTL_FILE_DIR

opa_home\ xmltemp

Specifies each directory you access.

If this environment is exclusively an Oracle Thesaurus Management System environment, you do not have to set this parameter.

However, if you share this environment with Oracle Clinical or Oracle Adverse Event Reporting System (AERS), you must specify entries to support Oracle Clinical PDF layout generation and Oracle AERS.

In a Windows environment, samples of the valid syntax are as follows:

UTL_FILE_DIR=c:\e2b\import

UTL_FILE_DIR=c:\opapps\xmltemp

In a UNIX environment, UTL_FILE_DIR requires an entry with two specified paths: one with and one without a trailing slash. Add these lines before any other UTL_FILE_DIR entries:

UTL_FILE_DIR=/usr/opapps/oc/xmltemp/

UTL_FILE_DIR=/usr/opapps/oc/xmltemp

4.3.8 Modify the tnsnames.ora File on the Database Server

The tnsnames.ora file must have an entry for each database that matches the database's Oracle SID. There is a tnsnames.ora file in at least two locations in the installation. Oracle recommends maintaining a master file and copying it to each location whenever you add a database. If the database server has multiple Oracle Homes, the tnsentries for all databases should be maintained in a central location; for example: /etc/tnsnames.ora.

The tnsnames.ora file is on each database server at: oracle_home/network/admin. See Section 5.8, "Modify the tnsnames.ora File on the Application Server" for the application server locations.

4.4 Install TMS Database Objects (All Databases)

This section describes how to add TMS database objects to each Oracle database that you will use for TMS.

4.4.1 Unlock Accounts Before Installing the TMS Database

The Installer prompts you for passwords to several system accounts. In Oracle Database, some accounts are locked. Before you run the Installer, check these accounts. Unlock them if necessary. You will need to set their passwords when you run the Installer.

Make sure the following accounts are unlocked: SYSTEM, CTXSYS, XDB, and SYS.

When you have finished installing the database, relock any accounts that were locked except for SYSTEM and SYS, which should not be locked.

4.4.2 Gather Required Information

Before you start the installer, be sure you have the information it prompts for; see Section 4.4.5, "Attend to the TMS Database Installer Screens".

1. Home Details: The full path to the Oracle Home location on your application server; by default:
C:\app\oracle\Middleware\Oracle_FRHome1

2. TMS Server Code Home Directory: The system detects the location and enters the value for you. By default, it is C:\opapps51\tms.

3. Database Connect String: Enter the database name. It must be a valid TNS entry in your tnsnames.ora file; see Section 4.3.8, "Modify the tnsnames.ora File on the Database Server".

4. NLS Settings: Enter the NLS settings for the database; see Section 1.7, "Choosing a Character Set". Oracle strongly recommends that you use UTF8. The default values are:

- American_America.UTF8

- DD-MON_RRRR

5. Directory for data tablespace data files: Enter the path to the directory on the database server where the data tablespace datafiles for the application should be created during the installation. The Installer does not validate the value and you must use the following syntax, including a trailing slash, depending on your operating system; for example:

- UNIX: /u01/oradata/dbname/

- Windows: drive:\oradata\dbname\

6. Directory for index tablespace data files: Enter the path to the directory on the database server where the index tablespace datafiles for the application should be created during the installation. The Installer does not validate the value and you must use the following syntax, including a trailing slash, depending on your operating system; for example:

- UNIX: /u01/oradata/dbname/

- Windows: drive:\oradata\dbname\

7. Enter and confirm passwords for the following accounts:

- SYS

- SYSTEM

- CTXSYS

- OPA

- RXC

- TMS

- TDX

- BC4J_INTERNAL

- OPS$TMSBROWSER

8. Ignore tablespace creation errors:

- Select Yes if the database already has the TMS tablespaces created.

- Select No if the TMS tablespaces do not exist.

9. The Installer gives you information that you should make a note of.

10. When you are ready, install.

4.4.3 Stop the PSUB Process (If Integrated with Oracle Clinical)

If your TMS installation is integrated with Oracle Clinical, you must stop the PSUB process before upgrading the database. See the Oracle Clinical Administrator's Guide for instructions.

4.4.4 Start the Installer

To install a TMS database:

1. Log in as a user with system administrator privileges in the application tier.

2. In the staging area, locate the directory where you downloaded and extracted Oracle Thesaurus Management System (see Section 1.4, "Downloading and Extracting the Software").

3. Run the file as an administrator:
Disk1\install\setup.exe

The Installer opens to the Welcome screen.

Note:
See Section 1.5, "Using the Silent Installer" for instructions for running the Installer as a file with pre-entered parameter values.

Note:
Although there is a button for deinstalling products on the Welcome screen, Oracle does not support using the Installer to deinstall Oracle Thesaurus Management System.

4. In the Select a Product to Install page, select TMS Database Install 5.1.0.0.x.

5. The Installer prompts for the type of installation you want.

- Select Master if you are planning to use only one database or if you have a distributed environment (using data replication) and this is the master database.

- Select Slave only if you have a distributed environment and this is a slave, or local, database.

4.4.5 Attend to the TMS Database Installer Screens

The Installer guides you through the installation and configuration of the TMS database server.

4.4.6 Check the Database Log File

For each database installation you perform, the Installer creates the following log file in the INSTALL directory:

tmsinst_database_name.log

Always check the log file for status, messages, and errors.

4.5 Create a TMS Administrator User Account (All Databases)

This section describes creating an administrator-level TMS user, which is defined as a user with the OPA_ADMIN role. Users with this role have access to the Define Users window in TMS, which enables them to create additional users in the database.

Note:
If the user already has an TMS OPS$ user account in the same database, you only need to grant the user the OPA_ADMIN role (see Step 4 only).

To create a new Oracle account for a user:

1. Connect to SQL*Plus as system and run the following script:
OPA_HOME\tms\51\install\tmsadduser.sql

2. Enter a user ID.

3. Enter a password for this user. Do not use the identified externally clause; explicitly assign a password.

4. Grant the user the OPA_ADMIN role:

grant OPA_ADMIN to user_id

4.6 Register Databases Integrated with Oracle Clinical

If you are installing TMS in the same database as Oracle Clinical, register the single or master database by running the TMS Installer.

Note:
Run TMS database registration on slave databases only after you have followed instructions in Section 4.8.6, "Setting Up and Starting Symmetric Replication" as directed in Section 4.8.7, "Register Slave Databases Integrated with Oracle Clinical."

4.6.1 Gather Required Information

Before you start the installer, be sure you have the information it prompts for; see Section 4.6.3, "Attend to the TMS Database Registration Screens".

4.6.2 Start the Installer

To register your TMS database for use with Oracle Clinical:

1. Log in to the application tier server as a user with system administrator privileges.

2. In the staging area, locate the directory where you downloaded and extracted Oracle Thesaurus Management System (see Section 1.4, "Downloading and Extracting the Software").

3. Run the following file as an administrator:
Disk1\install\setup.exe

The Installer opens to the Welcome screen.

Note:
See Section 1.5, "Using the Silent Installer" for instructions for running the Installer as a file with pre-entered parameter values.

Note:
Although there is a button for deinstalling products on the Welcome screen, Oracle does not support using the Installer to deinstall Oracle Thesaurus Management System.

4.6.3 Attend to the TMS Database Registration Screens

The Installer guides you through registering a TMS database.

1. Product to install: TMS Database Registration 5.1.0.0.x.

2. Home Details: The full path to the Oracle Home location on your application server; by default:
C:\app\oracle\Middleware\Oracle_FRHome1

3. TMS Server Code Home Directory: The system detects the location and enters the value for you. By default, it is C:\opapps51\tms\51.

4. Enter and confirm passwords for the following accounts:

- SYS

- TMS

- RXC

5. Global name: Enter the global name of the TMS database; for example:
service_name

To find out the global name, log in to SQL*Plus and enter:

select * from global_name

6. Enter the global name of the Oracle Thesaurus Management System database. A SQL*Net TNS alias mustexist with the same name.

7. The Installer gives you information that you should make a note of.

8. When you are ready, install.

4.7 Load Dictionaries (Single or Master Database)

See the Oracle Thesaurus Management System User's Guide for information about loading dictionaries.

If you are installing TMS with AERS in a distributed environment, you must load the AERS-TMS dictionaries onto the master database before creating an export file and importing it to the slave databases.

You can load dictionaries at any time. However, if you are installing TMS in a distributed environment, even without AERS, you may want to load dictionaries now so as to avoid doing another export/import later.

4.8 Complete Distributed Environment Setup

This section applies only if you are setting up a distributed environment. It includes:

- Section 4.8.1, "Export Data from the Master Database"

- Section 4.8.2, "Import Data to the Slave Database"

- Section 4.8.3, "Clean Up after Export and Import"

- Section 4.8.4, "Complete the Creation of the Slave Database"

- Section 4.8.6, "Setting Up and Starting Symmetric Replication"

- Section 4.8.7, "Register Slave Databases Integrated with Oracle Clinical"

4.8.1 Export Data from the Master Database

If you are installing a distributed environment, you must create an export file of the master database, which you then import into the slave database.

To export data from the master database:

1. Log in to the master database server.

2. Set up a physical directory as follows:

1. Create a new directory. For example: /u01/app/dmp.

2. Grant read and write permission to the Oracle database.

3. Verify that the tmsrepexp.dmp file does not exist in the directory. The Data Pump export will fail with an error if the tmsrepexp.dmp file already exists.

3. Create directory object on the master database:

1. Connect to the master database as the SYS user:
sqlplus sys/password as sysdba

2. Create a directory object called TMS_REP_DIR and then map it to the physical directory you created in the previous step.
CREATE OR REPLACE DIRECTORY TMS_REP_DIR AS 'PHYSICAL_DIR_ON_MASTER';

For example:

CREATE OR REPLACE DIRECTORY TMS_REP_DIR AS '/u01/app/dmp';

3. Grant directory privilege to TMS:
GRANT READ, WRITE ON DIRECTORY TMS_REP_DIR TO TMS;

4. Place tms.par in your working directory.

5. Point local variables to the database.

6. Invoke the Data Pump Export utility:
expdp tms/password PARFILE=tms.par

By default, the Data Pump Export utility creates a log file named export.log. Note that you can use the LOGFILE parameter to customize the name of the log file. For example:

expdp tms/password PARFILE=tms.par LOGFILE=my_export.log

7. Verify that the tmsrepexp.dmp file and an export log file are created in the physical directory you created in Step 2.

8. Open the export log file and verify that no errors occurred.

4.8.2 Import Data to the Slave Database

At every slave database, import the export file from the master database.

To import data to the slave database:

1. Log in to the slave database server.

2. Set up a physical directory as follows:

1. Create a new directory. For example: /u01/app/dmp.

2. Grant read and write permission to the Oracle database.

3. Transfer the tmsrepexp.dmp file from the master database server to this directory.

3. Create a directory object on the slave database:

1. Connect to the slave database as the SYS user:
sqlplus sys/password as sysdba

2. Create a directory object called TMS_REP_DIR and then map it to the physical directory you created in the previous step.
CREATE OR REPLACE DIRECTORY TMS_REP_DIR AS 'PHYSICAL_DIR_ON_MASTER';

For example:

CREATE OR REPLACE DIRECTORY TMS_REP_DIR AS '/u01/app/dmp';

3. Grant directory privileges to TMS:
GRANT READ, WRITE ON DIRECTORY TMS_REP_DIR TO TMS;

4. Point local variables to the database.

5. Invoke the Data Pump Import utility:
impdp tms/password CONTENT=ALL DIRECTORY=TMS_REP_DIR DUMPFILE=tmsrepexp.dmp TABLE_EXISTS_ACTION=SKIP

By default, the Data Pump Import utility creates a log file named import.log. Note that you can use the LOGFILE parameter to customize the name of the log file. For example:

impdp tms/password CONTENT=ALL DIRECTORY=TMS_REP_DIR DUMPFILE=tmsrepexp.dmp TABLE_EXISTS_ACTION=SKIP
LOGFILE=my_export.log

6. Open the import log file and verify that no errors occurred.

4.8.3 Clean Up after Export and Import

To clean database objects and log files after you export and import data:

1. Drop directory object as SYS user:
REVOKE READ, WRITE ON DIRECTORY TMS_REP_DIR FROM tms;
DROP DIRECTORY TMS_REP_DIR;

2. Delete the dump and log files from the physical directory.

3. Complete this procedure on each master database and each slave database.

For additional information about Oracle Data Pump, see the Oracle Database Utilities 11g Release 2 (11.2) documentation.

4.8.4 Complete the Creation of the Slave Database

On the TMS application server for each slave database, set the local variable and run the TMSUPGSLAVE.SQL script. This script generates a log file in the install directory called tmsupgslave_database_name.log.

Note:
Despite the "UPG" in its name, TMSUPGSLAVE.SQL is the correct script for initial TMS slave database installations.

To set the local variable and run TMSUPGSLAVE.SQL, enter:

set LOCAL=database_name

cd OPA_HOME\tms\install

sqlplus system/password

start tmsupgslave.sql

4.8.5 Configure DSI Import

If you plan to use disconnected system integration (DSI), enter following commands:

set LOCAL=databasename
sqlplus tms/password
exec tms_dsi_xml_schema.InstallSchemas;

4.8.6 Setting Up and Starting Symmetric Replication

This section describes how to set up symmetric replication for the first time (for new installations), and how to resume it (for upgrades). The steps required depend on your installation configuration.

- If you do not plan to use TMS in a distributed environment, skip this section.

- If you are creating a new installation, perform all the steps in this section.

- If you are upgrading, proceed to Section 4.8.6.2, "Start Replication on the Master Database."

If you choose to utilize symmetric replication, refer to the Oracle database manual that describes symmetric replication in detail. The instructions in this section provide the minimal list of the required tasks.

If you are establishing a distributed environment, you should enable symmetric replication for every TMS database.

Database Link and Privileges Changes

TMS users who use TMS for omission management and all users who perform replication must have a TMS database user account on either the master or local databases. In previous versions, TMS required that such users have accounts on both the master and local instances, but this is no longer necessary.

Integrated Installation

If you plan to integrate TMS with Oracle Clinical in a replicated environment, you must delete the Oracle Clinical RXA_READ public database link. Make sure you suspend Oracle Clinical replication, and then delete the RXA_READ link.

TMS creates its own public database link that does not contain connection information such as user ID and password. Oracle Clinical replication will use the TMS public link instead of RXA_READ.

4.8.6.1 Preliminary Steps to Start Replication

To start replication following an fresh installation of Oracle Thesaurus Management System (that is, you are not upgrading from a previous TMS release), complete the steps described in the following sections:

- Section 4.8.6.1.1, "Check the initdbname.ora File"

- Section 4.8.6.1.2, "Run the opasrc01.sql Script"

- Section 4.8.6.1.3, "Run the opasrc02.sql Script"

4.8.6.1.1 Check the initdbname.ora File

For every database in your TMS installation, check that the initdbname.ora file contains the following specifications:

- JOB_QUEUE_PROCESSES — At least 1

- GLOBAL_NAMES — TRUE

4.8.6.1.2 Run the opasrc01.sql Script

The opasrc01.sql script sets up common symmetric replication components for one database. You run this script once for each database in your installation.

To run the opasrc01.sql script:

1. Connect to the database as the SYSTEM user.

2. Run opasrc01.sql:
@OPA_HOME/tms/install/opasrc01

3. Respond to the prompts as follows:

1. Enter the name for local database: Enter the name of the database to which you are connected.

2. Enter the name for remote database: Press Enter. This script does not require the name of the remote instance.

4. Repeat these steps for every database in your TMS installation.

4.8.6.1.3 Run the opasrc02.sql Script

The opasrc02.sql script sets up common symmetric replication components. You run this script from each database location for each database location. For example, if you have three databases — A, B, and C — you must run the script six times: A for B, B for A, A for C, C for A, B for C, and C for B.

You do not have to run this replication script when you add a new database to a replicated TMS installation that is integrated with Oracle Clinical.

To run the opasrc02.sql script:

1. Connect to one of the databases as the SYSTEM user.

2. Run opasrc02.sql:
@OPA_HOME/tms/install/opasrc02

3. Respond to the prompts as follows:

1. Enter the name for local database: Enter the name of the database to which you are connected.

2. Enter the name for remote database: Enter the name of the remote database for which you want to create linkage.

3. Enter password: Enter the passwords for the SYSTEM and REPSYS schema on the local database, and the REPSYS schema on the remote database.

You may ignore errors indicating that database links already exist.

4. Repeat from each database location for each database location. Each time you run the script, enter the database to which you are connected at the "local database" prompt and the remote database at the "remote database" prompt.

4.8.6.2 Start Replication on the Master Database

This section describes how to start replication on the master instance in a distributed environment. Complete this procedure when you are starting replication for the first time after an initial installation and when you are starting symmetric replication after upgrading TMS.

To start replication on the master database:

1. Connect to the master site as the REPSYS user.

2. Create the master replication group, generate support, and resume symmetric replication activity on the master site:

start tmsmsrdefine
start tmsmsrgeneratesupport
start tmsmsrresumeactivity

3. Connect as the TMS user.

4. Create the materialized view logs on the master site:

start tmsmsrmvlog

4.8.6.3 Start Replication on Each Slave Instance

This section describes how to start replication on a slave instance in a distributed environment. Complete this procedure on each slave instance when you are starting replication for the first time after an initial installation and when you are starting replication after a TMS upgrade.

For setting up multiple slave instances, suspend the master replication group for setting up slave 2, and later resume the replication activity for both Oracle Clinical (if suspended) and TMS.

To start replication on a slave instance in a distributed environment:

1. On each Materialized View Site (slave site), connect to SQL*Plus as the REPSYS user and create the materialized view group:

start tmsssrdefine

When the system prompts for the master database, enter master_site.

2. On each slave site, connect as the TMS user and create the materialized views:

start tmsssrcmv

When the system prompts for the master database, enter master_site.

3. On each Materialized View Site (slave site), connect as the REPSYS user and add the materialized views to the Materialized View and Refresh Groups:

start tmsssrmvrep
start tmsssrmvref

4. On each Materialized View Site (slave site), connect as the SYSTEM user and compile all invalid:

start compile_all_invalid

5. On each Materialized View Site (slave site), connect as the REPSYS user and refresh the Materialized View Group:

exec dbms_refresh.refresh('TMS');

6. On each Materialized View Site (slave site), connect as the TMS user and run the following script to complete TMS processing:

start tmsscomplete

- If you are completing an initial installation, this script populates the TMS_DEF_INSTANCES table.

- If you are upgrading your installation, this script reports for which X_areas you need to run batch validation (or its equivalent). See Example 4-1, "Results of tmsscomplete Script" for more details.

Example 4-1 Results of tmsscomplete Script

For Oracle Clinical (System=OCL) Source Data, run batch validation for the following X_Areas. For non-Oracle Clinical source data, run the equivalent of Oracle Clinical's batch validation for the following X_areas:

SYSTEM

X_AREA

ES1

0

ES2

1

OCL

101

OCL

102

Based on these sample results, you need to run batch validation for the studies with a CLINICAL_STUDY_ID of 101 and 102, and the equivalent of batch validation for external systems ES1 and ES2.

4.8.7 Register Slave Databases Integrated with Oracle Clinical

This step is required only if you are integrating TMS with Oracle Clinical. Follow instructions in Section 4.6, "Register Databases Integrated with Oracle Clinical."

5 Installing and Configuring the Application Tier

This chapter describes how to install Oracle Application Server, which includes the Oracle Forms Server and the Oracle Reports Server, Oracle WebLogic Server, and Oracle Application Developer Framework.

This chapter includes:

- Section 5.1, "Before You Start"

- Section 5.2, "Install Adobe Reader"

- Section 5.3, "Install Oracle Java Development Kit"

- Section 5.4, "Install Oracle WebLogic Server 10.3.6"

- Section 5.5, "Install and Configure Oracle Application Server 11gR2"

- Section 5.6, "Enable SSL Between a Browser and Oracle HTTP Server"

- Section 5.7, "Install Oracle Application Developer FrameWork and Apply Patches"

- Section 5.8, "Modify the tnsnames.ora File on the Application Server"

- Section 5.9, "Test Connectivity to Databases for Forms and Reports Servers"

- Section 5.10, "Restart the Computer"

Critical Patch Updates See Section 1.8, "Applying Oracle Critical Patch Updates."

5.1 Before You Start

Do the following.

5.1.1 Identify a Single Account to Perform All Application Tier Installation Tasks

You must install all application tier components using the same user account. The account must have administrator privileges on the server computer.

5.1.2 Get a CA Certificate for HTTPS

To support HTTPS, you need to request a certificate from a Certificate Authority (CA) vendor such as Thawte, Entrust, or Verisign, and then import the certificate into the Oracle Wallet for the Oracle Application Server.

In the last step in Section 5.6.1.1, "Creating an Oracle Wallet and Generating a Certificate Request" you generate an encoded plain text certificate request file that you can email to the CA vendor. The vendor will sign the file and send you a Trusted Certificate and a User Certificate.

Allow some time for the certificates to be issued.

Note:
If your intention is to install an environment that will never be taken into production, you can skip this step and create a self-signed demo certificate for testing purposes; see Section 5.6.2, "Enabling SSL Between a Browser and Oracle HTTP Server With Self Signing."

5.2 Install Adobe Reader

Adobe Reader is required on the Reports Server and on client computers. If you have not already downloaded it, following instructions in Section 1.4.6, "Downloading Adobe Reader", do so now.

5.3 Install Oracle Java Development Kit

To install Oracle Java Development Kit (JDK):

1. If you have not already done so, follow instructions in Section 1.4.4, "Downloading Oracle Java Development Kit."

2. Follow instructions in the release notes to apply the patch.

Note:
Do not use the default download location. By default, the download directory is C:\Program Files\java\jdkversion. "Program Files" includes a space, which can cause problems. Oracle recommends specifying a directory with no spaces in the name.
In additon, the directory name must have no more than 8 characters; for example, C:\app\java\jdk16065.

3. Make a note of the directory in which you install JDK. You will need it when you install WebLogic Server.

5.4 Install Oracle WebLogic Server 10.3.6

Instructions in this section should be complete. However, additional information is in the WebLogic 10.3.6 following instructions in Oracle® Fusion Middleware Installation Guide for Oracle WebLogic Server 11g Release 1 (10.3.6), which you can find on the media pack or at http://docs.oracle.com/cd/E23943_01/doc.1111/e14142/overview.htm, or download the PDF from here: http://docs.oracle.com/cd/E23943_01/web.1111/e13708/toc.htm.

The complete documentation set for Oracle WebLogic Server 10.3.6 is available at: http://docs.oracle.com/cd/E23943_01/wls.htm.

1. In the staging area where you downloaded the media pack (see Section 1.4, "Downloading and Extracting the Software") locate the directory where you downloaded Oracle WebLogic Server 11gR1 (10.3.6) Generic and Coherence and extract the WebLogic Server .zip file if you have not already done so.

2. Log in as the user you selected in Section 5.1.1, "Identify a Single Account to Perform All Application Tier Installation Tasks".

3. Install Oracle WebLogic Server using a Generic Package installer—This type of installer is a .jar file; wls1036_generic.jar. Double-click on the .jar file to open the Installer.

You can accept most default values, with the exceptions noted below.

Note:
You can change the default value of the middleware_home directory, which is C:\Oracle\Middleware, if you wish but some code examples in this guide use that value to make it easier to copy and paste, so remember to change these if you change the value.
You must NOT change the names for any of the middleware home's subdirectories, including wlserver_10.3.

Security Updates

Specify whether you want to register the product installation with My Oracle Support. If you register, Oracle Support emails you immediately of any security updates that are specific to your installation. Follow instructions on screen to register or to reject the option.

Note:
Even if you accept this option you should check My Oracle Support for quarterly Oracle Critical Patch Update (CPU) security patches certified for use with Oracle Thesaurus Management System; see Section 1.8, "Applying Oracle Critical Patch Updates."

Choose the "Custom" Install Type

Select a "Custom" installation type rather than the default value, "Typical." This is required in order to create a Node Manager.

JDK Selection

Browse to the Oracle Java Development Kit (JDK) 1.6.0_65 (JDK 6) that you installed in the previous section.

Include the Node Manager

Be sure to install the Oracle WebLogic Node Manager in the Install Windows Service screen. The Node Manager is used to monitor, start, and stop server instances in a WebLogic domain.

Note:
Continue to click Next until you are finished. After the Installation Summary the processing may take a few minutes. You can safely ignore the Quick Start screen.

5.5 Install and Configure Oracle Application Server 11gR2

Install Oracle Applications Server as indicated below.

5.5.1 Install Oracle Application Server 11gR2 (11.1.2.1)

Oracle Application Server 11.1.2.1 provides Oracle Forms, Oracle Reports, and Oracle HTTP Server (OHS).

To install Oracle Application Server 11.1.2.1:

1. Restart the computer.

2. Log in as the user you selected in Section 5.1.1, "Identify a Single Account to Perform All Application Tier Installation Tasks".

3. Stop the WebLogic Node Manager:

1. Close the command shell in which the Node Manager is running, if any.

2. If any DOS windows are open that are running the node manager, close them.

3. Go to the Windows Control Panel, then Services, and stop the Oracle WebLogic Node Manager service.
For more information on the Node Manager, see the Oracle® Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server 11g Release 1 (10.3.6) at http://docs.oracle.com/cd/E23943_01/web.1111/e13740/toc.htm.

4. In the staging area where you downloaded the media pack—see Section 1.4, "Downloading and Extracting the Software"—locate the directory where you downloaded Oracle Forms and Reports 11g R2 (11.1.2.1.0) for Microsoft Windows x64 (64-bit) and extract the .zip file if you have not already done so.

5. Run the following file as an administrator:
Disk1\setup.exe

6. Follow the instructions on the installation screens as the Oracle Universal Installer guides you through the installation. You can accept most defaults except as noted below:

SKIP Software Updates

Select Skip Software Updates instead of the default value, Search My Oracle Support for Updates. Oracle Thesaurus Management System may not be certified with these updates.

Domain Name Must Be FRDomain

In the Select Domain window, the default name for the domain created by the Installer is ClassicDomain. You must rename it to FRDomain or TMS Browser installation will fail.

In the same screen, enter and confirm a password for WebLogic Server.

Oracle Instance Must Be asinst_1

When prompted for the Oracle Instance, accept the default value: middleware_home\asinst_1.

Specify Security Updates

Specify whether you want to register the product installation with My Oracle Support. By registering, Oracle Support emails you immediately of any security updates that are specific to your installation. Follow instructions on screen to register or to reject the option.

Note:
Even if you accept this option you should check My Oracle Support for quarterly Oracle Critical Patch Update (CPU) security patches certified for use with Oracle Thesaurus Management System; see Section 1.8, "Applying Oracle Critical Patch Updates."

Port

For greater security, you may want to customize the port. Auto Port Configuration is the default setting.

Proxy

For greater security, you may want to use a proxy. No proxy is the default setting.

Do NOT Use Application Identity Store

Uncheck the Use Application Identity Store check box at the top of the screen; Oracle Thesaurus Management System does not use OID (Oracle Identity).

5.5.2 Stop Services

Shut down the following services:

- WLS_FORMS under ORACLE_HOME

- WLS_REPORTS under ORACLE_HOME

- Oracle Process Manager

5.5.3 Apply Patch

Download patch 16837591from My Oracle Support and apply it following instructions in the patch readme file. It is required to support JRE7 Update 65.

Note:
The readme says "Ensure that the directory containing the OPatch script appears in your $PATH." The OPatch here is the one under ORACLE_FRHOME. For example:

set ORACLE_FRHOME= your_ORACLE_FRHome
set path=%oracle_frhome%\opatch;%path%

In addition, you can safely ignore the Prerequisites section in the readme.

5.5.4 Create ORACLE_INSTANCE Environment Variable

Create the ORACLE_INSTANCE environment variable and define it as the Oracle Application Server Home:

1. From the Control Panel, select System, then Advanced System Settings.

2. Create a system variable named ORACLE_INSTANCE and set its value to your Oracle Instance Home; for example C:\oracle\middleware\asinst_1.

5.6 Enable SSL Between a Browser and Oracle HTTP Server

Create the following SSL (HTTP Secure Socket Layer) configuration: from users' browsers, HTTPS to Oracle HTTP Server (Web proxy), then HTTP to Oracle WebLogic Server.

Follow instructions in one of the following sections:

- Section 5.6.1, "Enabling SSL Between a Browser and Oracle HTTP Server Using a Certificate Authority"

- Section 5.6.2, "Enabling SSL Between a Browser and Oracle HTTP Server With Self Signing"—This may be useful if you want to set up HTTPS with a demo certificate for internal testing purposes.

5.6.1 Enabling SSL Between a Browser and Oracle HTTP Server Using a Certificate Authority

The following basic steps are required:

- Creating an Oracle Wallet and Generating a Certificate Request

- Import the User Certificate and Trusted Certificate to OWM

- Edit the Oracle HTTP Server Configuration File

Oracle HTTP Server uses a utility called Oracle Wallet Manager (OWM) to manage certificates on the server. An Oracle Wallet is a container that stores your credentials, such as certificates, trusted certificates, certificate requests, and private keys.

The Oracle Thesaurus Management System Installer automatically enables traffic from Oracle HTTP Server to Oracle WebLogic Server.

Note:
Do all steps in this section with the same user account you have used in the previous steps in this chapter. You must have administrator privileges on the machine.

Note:
If you have not set the Oracle Instance variable as instructed in Section 5.5.4, do so now.

5.6.1.1 Creating an Oracle Wallet and Generating a Certificate Request

To create an Oracle Wallet:

1. Log in to Oracle HTTP Server as the user that installed Oracle Application Server.

2. Start Oracle Wallet Manager. From the Start menu, navigate to Oracle Classic 11g, then Integrated Management Tools, then Wallet Manager.

3. In Oracle Wallet Manager, from the Wallet menu, click New.
A dialog asks if you want to create a default directory.

4. Click No. Your account probably does not have privileges to do this. For Oracle Thesaurus Management System the Wallet will be in the directory where the Installer created the default certificate and Wallet.

5. Enter and confirm a password that conforms to the rules listed in the dialog. This password will be required every time you open the Wallet.
Leave the Wallet Type set to Standard and click OK.

6. A new dialog opens, asking if you want to create a certificate request. Click Yes.

7. In the Create Certificate Request dialog, enter values in the following fields:

- Common Name: Enter host.your_company_domain.

Note:
The Common Name must match the Server Name directory that is specified in the primary configuration file (httpd.conf), which is created during Oracle HTTP Server installation in C:\app\oracle\middleware\asinst_1\config\OHS\ohs1.
The rest of the fields do not affect SSL functionality.

- Organizational Unit: Your unit within your company.

- Organization: Your company.

- Locality or City, State or Province, and Country

- Key Size: 2048 (bits)

Note:
Most providers encourage 2048-bit keys on all certificates.

- DN: OHS generates this value from the values you entered.

Click OK. The system displays a confirmation that a certificate request has been created. Click OK.

8. Go to the directory where the Wallet has been created:

oracle_instance\config\OHS\ohs1\keystores\default

9. In the keystores directory, create a new directory with a meaningful name such as your organizational unit:

oracle_instance\config\OHS\ohs1\key_stores\your_unit

10. In the navigation tree on the left, select Certificate: [Requested] and then select Export Certificate Request from the Operations menu.

11. Navigate to the new directory you created and enter a name for a file to be created; for example, server_name.csr. Click Save.

12. Select Save As from the Wallet menu, navigate to the new directory, and click OK. The wallet file is always named ewallet.p12.
The system displays a confirmation message along the bottom of the screen that a certificate request has been exported successfully.

The new directory now contains the certificate request file as well as the wallet file.

5.6.1.2 Obtain Trusted Certificate and User Certificate from Certificate Authority

Obtain the certificates from the Certificate Authority as described in Section 5.1.2, "Get a CA Certificate for HTTPS". Depending on the Certificate Authority, you will need to send either the certificate request file generated in the previous section or you will need to copy and paste the text in that file.

5.6.1.3 Import the User Certificate and Trusted Certificate to OWM

After you have received the User Certificate and Trusted Certificate from a CA vendor:

1. Log in to Oracle HTTP Server as the admin user that owns OHS processes.

2. Start Oracle Wallet Manager. From the Start menu, navigate to Oracle Classic 11g, then Integrated Management Tools, then Wallet Manager.

3. In Oracle Wallet Manager, select Open from the Wallet menu.
A dialog asks if you want to create a default directory.

4. Click Yes.

5. Navigate to the directory where you saved the Wallet file and click OK.

6. Enter the Wallet password that you created.

7. From the Operations menu, select Import Trusted Certificate.

8. In the dialog, select the option Select a file that contains the certificate and click OK.

9. Navigate to the trusted certificate and click OK.
The system displays a confirmation message along the bottom of the screen that the trusted certificate has been imported successfully.

10. In the navigation tree on the left, select Certificate: [Requested] and then select Import User Certificate from the Operations menu.

11. Navigate to the signed certificate and click OK.
The system displays a confirmation message along the bottom of the screen that a certificate has been imported successfully.

12. In the Wallet menu, select Auto Login, then Exit.

5.6.1.4 Edit the Oracle HTTP Server Configuration File

Make the following two changes in the OHS configuration file, ssl.conf.

5.6.1.4.1 Add the New Wallet Location and Specify Port

WebLogic Server installation creates a default, unsigned SSL wallet file for OHS. Its location is specified in the configuration file (ssl.conf) loaded at startup from the oracle_instance\config\OHS\ohs1 directory.

1. Make a backup copy of ssl.conf, which is located at:

oracle_instance\config\OHS\ohs1

2. Open ssl.conf in a text editor.

3. Find the string #Path to the wallet and comment out the default location that follows it.

SSLWallet ${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/keystores/default

4. Replace the above string (in bold) with the path to the directory you created:

SSLWallet oracle_instance_home\config\OHS\ohs1\keystores\your_unit

5. By default, the port for SSL is 8890, which means all URLs need to include :8890. You can change the value to 443 in which case the URLs do not need to include any port. To change the port to 443, change the following lines:

Listen 8890
<VirtualHost *:8890>

to:

Listen 443
<VirtualHost *:443>

6. Stop and start Oracle HTTP Server using Oracle Process Manager Notification Server (OPMN) to load the configuration change:

oracle_instance\bin\opmnctl restartproc process-type=OHS

The OPMN opmnctl executable for the instance is located in oracle instance_home\bin directory.

7. Test that you can connect from a browser to your virtual host in HTTPS URL:
https://host.your_company_domain

5.6.1.4.2 Make OHS Compatible with Internet Explorer 9 and Above

While you have the ssl.conf file open, make the following additional change to make the application compatible with Internet Explorer 9 and 10.

OHS always returns HTTP 1.0 to Internet Explorer (IE) user-agents, which causes some problems in TMS Browser. It appears this configuration is outdated and should be commented out to work properly in IE 9 and 10.

Comment out or remove the following lines:

BrowserMatch ".*MSIE.*" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0

5.6.1.4.3 Add Security Settings

While you have the ssl.conf file open, make the following additional change to avoid weak ciphers and protocols for SSL (HTPS):

Add the following lines:

SSLProtocol -ALL +SSLv3 +TLSv1
SSLCipherSuite
ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:!NULL:RC4+RSA:+HIGH:+MEDIUM:!SSLv2:!EXPORT

5.6.2 Enabling SSL Between a Browser and Oracle HTTP Server With Self Signing

To set up HTTPS with a demo certificate for internal testing purposes:

1. Log in to Oracle HTTP Server as the user that installed Oracle Application Server.

2. Start Oracle Wallet Manager. From the Start menu, navigate to Oracle Classic 11g, then Integrated Management Tools, then Wallet Manager.

3. In Oracle Wallet Manager, from the Wallet menu, click New.
A dialog asks if you want to create a default directory.

4. Click No. Your account probably does not have privileges to do this. For Oracle Thesaurus Management System the Wallet will be in the directory where the Installer created the default certificate and Wallet.

5. Enter and confirm a password that conforms to the rules listed in the dialog. This password will be required every time you open the Wallet.
Leave the Wallet Type set to Standard and click OK.

6. A new dialog opens, asking if you want to create a certificate request. Click No.

7. Do Save As to save the empty password-protected Wallet to a meaningful location like your_unit. For example:
oracle_instance\config\OHS\ohs1\keystores\oc

8. Open a DOS window.

9. Navigate to: Middleware_Home\oracle_common\bin

10. Create and set the java_home environment variable; for example:
set java_home=c:\app\java\jdk16065

11. Run following orapki command for the Wallet created above:

c:\Oracle\Middleware\oracle_common\bin>orapki wallet add -wallet
full-path_to_the_location_of_the_Wallet_after_step_7 -dn
"CN=hostname.domain, OU=Department, O=Company, L=City, ST=State/Province, C=Country"
-keysize 2048 -self_signed -validity 2190 -pwd password

Note:
Double quotes where specified above are required.
Validity is hardcoded above to 2190 days, which is six years. You can change this value as required.

12. Start Oracle Wallet Manager. From the Start menu, navigate to Oracle Classic 11g, then Integrated Management Tools, then Wallet Manager.

13. Click Yes when prompted with "Your default wallet directory does not exist. Do you want to continue?"

14. In the Wallet Manager, open the Oracle Thesaurus Management System Wallet. The self-signed certificate should be displayed with a status of READY.

15. In the Wallet menu, select Auto Login.

16. Save and exit.

17. To complete the setup, follow these instructions:

1. Section 5.6.1.4, "Edit the Oracle HTTP Server Configuration File"

2. Section 5.6.1.4.2, "Make OHS Compatible with Internet Explorer 9 and Above"

3. Section 5.6.1.4.3, "Add Security Settings"

Note:
Since this is a demo certificate and is not from a recognized certificate authority, the browser will display a certificate warning. To prevent this, you can import the certificate into the browser and store it as a trusted publisher and trusted root CA, then restart the browser.

For more information, see How To Generate A Wallet Containing A Self Signed Certificate Using ORAPKI in Oracle Application Server and Fusion Middleware on My Oracle Support (Article ID 560982.1).

5.7 Install Oracle Application Developer FrameWork and Apply Patches

Install Oracle Application Developer Framework (ADF, also known as Oracle Application Developer) and apply required patches.

5.7.1 Install Oracle Application Developer Framework (ADF)

Install Oracle Application Developer 11g R1 (11.1.1.6.0), also known as ADF, which is included in the media pack.

Additional information is included in the Oracle® Fusion Middleware Installation Guide for Application Developer 11g Release 1 (11.1.1.6.0), which you can find on the media pack or at http://docs.oracle.com/cd/E23943_01/doc.1111/e14827/toc.htm.

1. In the staging area where you downloaded the media pack (see Section 1.4, "Downloading and Extracting the Software") locate the Oracle Application Development Runtime 11g Patch Set 5 (11.1.1.6.0) directory where you extracted the ADF .zip file.

2. If you have not done so already, log in as the user you selected in Section 5.1.1, "Identify a Single Account to Perform All Application Tier Installation Tasks".

3. In a DOS Command window, navigate to the above directory.

4. Execute the following command:
setup -jreLoc drive:\location_where_you_installed_jdk1.6.0_65

for example:

setup -jreLoc C:\app\Java\jdk16065

However, if you installed JDK in the default location, C:\Program Files\Java\jdk1.6.0_65, this command may not work because of the space between "Program" and "Files." The following command works for the same location:

setup -jreLoc C:\Progra~1\Java\jdk16065

Tip:
ADF's setup.exe file does not run if you double-click it. You must use the above command.

5. Follow instructions on the Installer screens.

Note:
If you see the message "WLS installation detected, WebLogic Server support available in this Middleware Home." Press Next to continue the installation.

5.7.2 Upgrade ADF

Upgrade ADF to the latest patch set that is certified with Oracle Thesaurus Management System. See Oracle Health Sciences (Life Sciences/ Pharmaceutical/ Healthcare) Supported Technology Stacks (Article ID 180430.1) on My Oracle Support for the latest information.

To upgrade ADF, apply two patches, a JDeveloper patch and a WebCenter Composer patch, and enter an upgrade command as detailed below. For ADF 11.1.2.4 the patch numbers are:

- 16546129—JDeveloper patch

- 16546157—WebCenter Composer patch

Note:
Oracle supports only English OS language settings for the application tier.

Additional information is in the patch readme files. However, because there are no WebCenter components explicitly installed, you cannot follow the patch readme instructions completely.

1. Restart the server.

2. Locate the patch files in the staging area where you downloaded them in Section 1.4, "Downloading and Extracting the Software."

3. Go to the Windows Control Panel, then Services, then stop all Oracle services (Oracle Process Manager, Oracle WebLogic Node Manager).

4. Open a DOS command window and set the oracle_home and path. For ADF (only) this should be:
set ORACLE_HOME=your_oracle_common_home

For example: set ORACLE_HOME=C:\Oracle\Middleware\Oracle_Common

set path=%oracle_home%\bin;%oracle_home%;%oracle_home%\opatch;%path%

Note:
The readme for the WebCenter patch directs you to set oracle_home to Oracle_WC1—the WebCenter install directory. However, if there are no WebCenter components explicitly installed, set oracle_home to oracle_common as above.

5. Navigate to one patch directory. For example, for ADF 11.1.2.4:
cd c:\downloads\p16546129_111160_Generic\16546129

6. Enter
opatch apply

7. Navigate to the other patch directory. For example, for ADF 11.1.2.4:
cd c:\downloads\p16546157_111160_Generic\16546157

8. Enter
opatch apply

9. If you have started any WebLogic services, including the Administration and Managed Servers, close them now:

- If any DOS windows are open that are running the node manager, close them.

- Go to the Windows Control Panel, then Services, and turn off the Oracle WebLogic Node Manager service.

10. From the DOS command line, navigate to middleware_home\oracle_common\common\bin and execute the following commands:

setWlstEnv.cmd
wlst.cmd

Then, in the WebLogic Server Scripting Tool shell, enter the following commands:

upgradeADF('middleware_home/user_projects/domains/frdomain')
exit()

Note:
Be sure to use forward slashes (/) in the path.
By default middleware_home is C:\oracle\middleware.

In the WLS Scripting Tool shell you can type help() to get information on available commands.

5.7.3 Patch ADF to Support Internet Explorer 11

Check My Oracle Support article ID 1599898.1 for information on what patches, if any, are required to make your version of ADF compatible with IE 11.

For ADF 11.1.2.4, Oracle JDeveloper patch 18277436 is required.

Download the patch from My Oracle Support and apply it, following instructions in the readme file.

5.8 Modify the tnsnames.ora File on the Application Server

The tnsnames.ora file must have an entry for each database that matches the database's service name. There is a tnsnames.ora file in at least two locations in the installation. Oracle recommends maintaining a master file and copying it to each location whenever you add a database. See Section 4.3.8, "Modify the tnsnames.ora File on the Database Server" for the database server location.

The tnsnames.ora locations on the application server include:

- middleware_home\asinst_1\config

- oracle_fr_home\network\admin. Oracle Thesaurus Management Systemrequires a copy here. Check this location and if no tnsnames.ora file is present, create it there.

5.9 Test Connectivity to Databases for Forms and Reports Servers

The Oracle Thesaurus Management System database must be able to communicate with the application servers. Establish that SQL*Net connections can be created to connect the application server to all databases.

5.9.1 Test the Connection from the Application Servers to the Database

To ensure that you can connect to the database from each application server:

1. Open a Microsoft DOS command window.

2. Use SQL*Plus to verify that you can connect to the database:
sqlplus system/password@dbname

5.9.2 Troubleshoot Network Connection Issues

If the system returns a connection error, you must resolve this problem before continuing with the installation of Oracle Thesaurus Management System.

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 login to check.

- The database or SQL*Net listener process is not started on the server.

- An incorrect connect string (service name), user ID, or password was entered.

- The tnsnames.ora file is not present in the correct directory or does not contain the correct entries.

5.10 Restart the Computer

To ensure that all configuration changes for the Oracle Application Server are initialized, restart the computer before you continue with the next task in the installation process.

6 Installing Oracle Thesaurus Management System Application Components

The Oracle Thesaurus Management System Front End includes:

- The Oracle Thesaurus Management System Forms Server, which is required for the primary Oracle Thesaurus Management System application

- The TMS Browser, the online help, and the OPA OC4J instance

You must install the TMS Server code and database objects before you install the Front End.

This section includes:

- Section 6.1, "Restart Computer and Stop All Servers and Services"

- Section 6.2, "Installing the TMS Front End"

- Section 6.4, "Installing the TMS Reports Server"

- Section 6.5, "Verifying the Application Tier Installation"

- Section 6.7, "Set Up Automatic Startup"

- Section 6.8, "Starting Servers Manually"

- Section 6.10, "Stopping Servers"

6.1 Restart Computer and Stop All Servers and Services

Restart the computer and then stop all servers and services:

1. Restart the computer.

2. In the Windows Services control panel, find Oracle Node Manager service and stop it.

3. From the Windows Start menu, go to All Programs, then Oracle Classic_asinst_1, then:

- Forms Services, then Stop WLS_FORMS

- Reports Services, the Stop WLS_REPORTS

- Stop Admin Server: NOTE: This is required if you are installing the Front End and the Server (database server code), but if you are installing the Report Server the Admin Server must be running.

6.2 Installing the TMS Front End

The TMS Report Server must be installed on the same machine as the TMS Front End and requires that the WebLogic FRDomain Admin Server be running during installation, whereas the TMS Front End and Server installation processes require that the Admin Server be stopped. So although the TMS Installer gives you the option to install all three at once you should not use that option.

6.2.1 Gather Required Information

Have the following information ready to enter in the Installer screens:

- Home Details: Select the Oracle Home that corresponds to the Oracle Forms and Reports home, similar to C:\oracle\middleware\Oracle_FRHome1.
On the Installer screen there are two drop downs, Name and Path. Use the Path drop-down to do the selection. When you select the directory, the Name value changes automatically.

- Your OPA Home directory; by default:
C:\opapps51

- Oracle HTTPS Server (OHS) SSL Listener Port number. You may have set this to 443 per the instructions in the previous chapter; see Section 5.6.1.4.1, "Add the New Wallet Location and Specify Port."

- Oracle HTTP Server (OHS) Non-SSL Listener Port number.

Tip:
To find these two port numbers:

1. Open an MS DOS window.

2. Go to oracle_instance/bin.

3. Enter opmnctl status -l
where the last character is a lowercase L.

To check, go to the URL https://host:port with each port.

- WebLogic username: The account created when you installed the WebLogic Server.

- Enter the passwords for:

- WebLogic Server (the password you created when installing WebLogic Server)

- OPA Proxy (bc4j_internal)

- TMS Proxy (ops$tmsbrowser)

- Database details:

- Database server:
server_name.your_company.com

- Database instance: database_name

- Port number

6.2.2 Start the Installer

To install the TMS Front End:

1. Log in as a user with system administrator privileges.

2. In the staging area, locate the directory where you downloaded and extracted Oracle Thesaurus Management System (see Section 1.4, "Downloading and Extracting the Software").

3. Run the following file as an administrator:
Disk1\install\setup.exe

The Installer opens to the Welcome screen.

Note:
See Section 1.5, "Using the Silent Installer" for instructions for running the Installer as a file with pre-entered parameter values.

Note:
Although there is a button for deinstalling products on the Welcome screen, Oracle does not support using the Installer to deinstall Oracle Thesaurus Management System.

6.2.3 Attend to the TMS Front End Installer Screens

The Oracle Universal Installer guides you through the installation and configuration of the TMS Front End.

1. Product to install: Oracle Thesaurus Management System Front End.

2. Home Details: There are two drop-downs, Oracle Home Name and Directory. Use the Directory drop-down to select the Oracle Home that corresponds to the Oracle Forms and Reports home, similar to C:\oracle\middleware\Oracle_FRHome1.
When you select the directory, the Home value changes automatically.

3. Available Product Components: Select Oracle Thesaurus Management System Front End 5.1.0.0.x.

Note:
Although the Installer gives you the option install the TMS Server (database server code) at the same time, do not select this option. You must install the TMS Server first, then the database objects, and then the Front End.
Do not choose to install the Report Server at the same time. Its installation process requires that the WebLogic FRDomain Admin Server be running, while the Front End and TMS Server installation processes require that the Admin Server be stopped.

4. Follow the instructions on the installation screens, providing the information you assembled in Section 6.2.1, "Gather Required Information.".

5. If the Installer detects that you have already installed 5.0 or above and created the OPADomain, the Installer asks if you want to overwrite OPADomain or not.

- Overwrite it if your previous installation failed or only partially completed; for example, the TMS Browser URL does not work.

- Do not overwrite if you have created it successfully, and especially if you have done customizations such as setting up clusters or multiple databases. Also if Oracle Clinical is installed in the same application server, do not overwrite OPADomain.

6. Summary: The Summary screen provides information about the global settings, languages, space requirements, and products for this installation.
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.

6.2.4 Review the Installation Log File

Review the generated installation log file for errors. See Section 1.6, "Reviewing the Installation Log Files" for details.

Work with Oracle Support, if necessary, to resolve any errors.

6.2.5 Restart the Computer

To ensure that all configuration changes are initialized, you must restart the computer before you continue with the next task in the installation process or before you install Oracle Thesaurus Management System Reports Server.

6.2.6 Add WebLogic Data Sources If Using Multiple Databases

When you run the Oracle Thesaurus Management System Installer, it sets up two data source connections, one for OPA and one for RDC Onsite, from the WebLogic Server (WLS) to the database you specify in the Installer screens.

If you plan to use more than one database, you must create a WLS data source for OPA and the TMS Browser for each additional database. The OPA connection is used for running TMS reports. If you also are using RDC on multiple databases, you need to create additional data sources for RDC.

Instructions are in the Oracle Thesaurus Management System User's Guide and the Oracle Clinical Remote Data Capture Onsite Administrator's Guide.

6.3 Make the Java Runtime Environment Available for Download

Oracle Thesaurus Management System requires that Java Standard Edition (SE) Runtime Environment (JRE) exist on the user's computer.

The Oracle Thesaurus Management System Launch page is configured to prompt users to install JRE if it does not exist on their computer. To make this work, you need to download JRE into the OPA_HOME\html directory and rename it.

1. If you have not already done so, download the software following instructions in Section 1.4.5, "Downloading the Java Runtime Environment."
See that section if you are using the 64-bit version.

2. Copy the downloaded file from the staging area to OPA_HOME\html.

3. Rename the file to sunjpi.exe.

If your users need to have both JRE 6 and 7 installed to support different versions of Oracle Thesaurus Management System, check My Oracle Support article 1570682.1 for guidance; see "Finding Information on My Oracle Support".

6.4 Installing the TMS Reports Server

This section describes installing and configuring a Reports Server. The TMS Reports Server runs on Oracle Application Server 11g Release 1 Forms and Reports Services. It schedules batch jobs such as synchronization.

You must install the TMS Front End before installing the TMS Report Server.

Note:
If you have already installed the Oracle Clinical Reports Server on this machine, you do not need to install the TMS Reports Server.
The Installer prevents you from installing two Reports Servers with the same name.

6.4.1 Start the WebLogic FRDomain Admin Server

Start the WebLogic FRDomain Admin Server is running. Do one of the following.

- Go to the Start menu, then All Programs, then Oracle Classic asinst_1, then Start Admin Server.

- Go to the Start menu, then All Programs, then Oracle Weblogic, then User Projects, then FRDomain, then Start Admin Server Weblogic Server Domain.

6.4.2 Gather Required Information

Before you start the Installer, be sure you have the information it prompts for; most of the information is the same as in Section 6.2.1, "Gather Required Information." In addition, you need to provide a name for the TMS Report Server that is unique across your installation.

6.4.3 Start the TMS Report Server Installer

To install the TMS Report Server:

1. Log in as a user with system administrator privileges.

2. In the staging area, locate the directory where you downloaded and extracted Oracle Thesaurus Management System (see Section 1.4, "Downloading and Extracting the Software").

3. Run the following file as an administrator:
Disk1\install\setup.exe

The Installer opens to the Welcome screen.

Note:
See Section 1.5, "Using the Silent Installer" for instructions for running the Installer as a file with pre-entered parameter values.

Note:
Although there is a button for deinstalling products on the Welcome screen, Oracle does not support using the Installer to deinstall Oracle Thesaurus Management System.

4. In the Select a Product to Install page, select Oracle Thesaurus Management System Report Server 5.1.0.0.x.

6.4.4 Attend to the TMS Reports Server Installation Screens

The Oracle Universal Installer guides you through the installation and configuration of the TMS Reports Server.

1. See Section 6.2.1, "Gather Required Information." Some of the same information is required for the Report Server.

2. Report Server name. Enter a unique name across your installation. If you try to create a second Reports Server with the same name as the first, the Installer detects it and prevents it.

3. Summary: The Summary screen provides information about the global settings, languages, space requirements, and products for this installation.
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.

6.5 Verifying the Application Tier Installation

Verify that these URLs work and you can log into the application:

- Forms-based TMS—https://host/opa51/launch.htm

- TMS HTML Browser—https://host/tmsadf/faces/Login

6.6 Verify and Fix Environment Variables

Check values and correct them if required.

6.6.1 Check Values

To check variable values:

1. Open a DOS prompt window.

2. Run:

middleware_home\domains\OPADomain\bin\setDomainEnv.cmd

For example:

c:\oracle\middleware\user_projects\domains\OPADomain\bin\setDomainEnv.cmd

The script should run with no errors.

3. Inspect the value of JAVA_HOME:

1. At the DOS command prompt, type: set JAVA_HOME. You should see the location where you installed JDK following instructions in Section 5.3, "Install Oracle Java Development Kit."

2. Enter: dir %java_home%. You should see the directory specified as your JAVA_HOME containing a file called src.zip and four subdirectories: jre, lib, bin, and include.
If you do not see these things, you will need to add them as directed in Section 6.6.2, "Correct Values".

If JAVA_HOME contains any spaces or if any of the directories in its path are greater than 8 characters, you will need to correct them as directed in Section 6.6.2, "Correct Values".

4. Inspect the value of JAVA_VM. At the command prompt, enter: set JAVA_VM. You should see something like JAVA_VM=-server. If not, correct as directed in Section 6.6.2, "Correct Values".

6.6.2 Correct Values

To correct any of the above problems:

1. Navigate to middleware_home\wlsserver_10.3\common\bin

2. Back up commEnv.cmd.

3. Open commEnv.cmd in a text editor.

4. The first line in commEnv.cmd identifies the JAVA_HOME value. If it does not exist or is not correct, add or edit it; for example:
set JAVA_HOME=c:\java\jdk1.6.0.45

5. Find:
set JAVA_VM=-client

change it to:

set JAVA_VM=-server

6. Close the DOS window and open a new one, then repeat the steps in Section 6.6.1, "Check Values".

6.7 Set Up Automatic Startup

It is possible to configure any Windows service to restart itself upon failure. These are standard options available when configuring a Windows service in the context of Windows Services Manager.

However, it is important to understand that Windows Services Manager only monitors the service's JVM process. If the JVM process fails (shuts down), then Windows Services Manager will attempt to restart it. But there are some scenarios where the WebLogic Admin Server or Managed Server may go into an unhealthy or failed state while the JVM is still running. The Windows Service Manager will not know to restart the process in these cases, whereas if the Admin Server and Managed Server had been started using the WebLogic Node Manager, Node Manager would recognize such a state and restart the process.

Oracle recommends starting the Admin and Managed Servers through the Node Manager using python scripts and then configuring the Windows server to execute the python scripts at startup.

6.7.1 Set Up Script to Execute Automatically at Machine Startup

Create a task and set up the Task Scheduler to run the job on bootup:

1. From Start, then Control Panel, then Administrative Tools, open Task Scheduler.

2. Select Create Basic Task on the right side of the Task Scheduler.

3. Enter following values:
Name: Oracle FRDomain Autostart

Trigger: When the computer starts

Action: Start a program

Select:opa_home\config\autostartFRDomain.cmd

4. Click Next and then Finish to complete creation of the scheduled task.

5. Find the task Oracle Domain Autostart under the Active Tasks list (center pane) and double-click to select it. Right-click on the task you just created and select Properties.

6. On the General tab, select Run whether user is logged on or not.

7. Repeat these steps for OPADomain, with two differences. In Step 3, enter:
Name: Oracle OPADomain Autostart

Select:opa_home\config\autostartOPADomain.cmd

6.7.2 Verify Autostart Scripts

1. From a DOS window, enter command:
opa_home\config\autostartfrdomain2.cmd

to start the FRDomain server. This command will print a lot of messages and will take some time. While this is executing, proceed to next step.

2. From a different DOS window, enter command:
opa_home\config\autostartopadomain2.cmd

to start the OPADomain server.

3. When both windows are complete, you will see messages like below, followed by the DOS prompt which will indicate script is complete:

Starting server WLS_FORMS ....................................
Server with name WLS_FORMS started successfully
Starting server WLS_REPORTS ............................
Server with name WLS_REPORTS started successfully

Successfully Connected to Node Manager.
Starting server AdminServer ...
Successfully started server AdminServer ...
Starting server OpaServer1 ...
Successfully started server OpaServer1 ...

4. Verify that these URLs work and you can log into application:

- TMS: https://server.domain/opa51/launch.htm

- TMS Browser: https://server.domain/tmsadf/faces/Login?setUpDone=Y

6.7.3 Test Autostart

To test:

1. Restart the computer.

2. Allow some time for the services to start.

3. Try the URLs in Section 6.7.2, "Verify Autostart Scripts."
If the URLs do not work after several minutes, check files in opa_home\log:

- autostartfrdomain2.log

- autostartfrdomain2.err

- autostartopadomain2.log

- autostartopadomain2.cmd

6.8 Starting Servers Manually

If you have not set up automatic startup, you can start the required servers manually using the instructions in this section.

For information about these servers and the server architecture, see the topology diagram.

6.8.1 Starting the FRDomain Admin Server

The Oracle FRDomain Admin Server is located on the WebLogic Server domain that must be named FRDomain and must use port number 7001. You must start the Admin Server before you can start either the Oracle Forms Server or the Oracle Reports Server.

To start the Admin Server, do one of the following:

- Go to the Start menu, then All Programs, then Oracle Classic asinst_1, then Start Admin Server.

- Go to the Start menu, then All Programs, then Oracle Weblogic, then User Projects, then FRDomain, then Start Admin Server Weblogic Server Domain.

Note:
You cannot start it from the Admin Console because if the server is not running, the FRDomain Admin Console is not available.

6.8.2 Starting the Forms Server

The Oracle Forms Server is located on the WebLogic Server domain that must be named FRDomain and must use port number 7001. You must start the FRDomain Admin Server before the Forms Server.

To start the Forms Server, do either:

- Start, then All Programs, then Oracle Classic asinst_1, then Forms, then Start WLS_FORMS.

- Use the Admin Console at http://host:7001/console.

6.8.3 Starting the Reports Server

The Oracle Reports Server is located on the WebLogic Server domain that must be named FRDomain and must use port number 7001. You must start the FRDomain Admin Server before the Reports Server.

To start the Reports Server, do either:

- Start, then All Programs, then Oracle Classic asinst_1, then Reports, then Start WLS_REPORTS.

- Use the Admin Console at http://host:7001/console.

6.8.4 Starting the OPADomain Admin Server

The Oracle OPADomain Admin Server is located on the WebLogic Server domain that the Installer names OPADomain, and which must use port number 7101. You must start the Admin Server before you can start the OpaServer1.

To start the OPADomain Admin Server, go to the Start menu, then All Programs, then Oracle WebLogic Server, then User Projects, then OPADomain, then Start Admin Server.

Note:
You cannot start from the Admin Console because if the server is not running, the OPADomain Admin Console is not available.

6.8.5 Starting the OpaServer1 Server

The OpaServer1 Server is located on the WebLogic Server domain named OPADomain, which must use port number 7101. The OpaServer1 Server runs on Oracle ADF and supports the TMS Browser and TMS reports. It also contains the database connections.

You must start the OPADomain Admin Server before the OpaServer1 Server.

To start the OpaServer1 Server, use the Admin Console at either:

- http://host:7101/console

- https://host/opaconsole (if configured)

6.9 Verify the Application Tier Installation

Verify that these URLs work and you can log into application:

- https://host/opa51/launch.htm

- https://host/tmsadf/faces/Login

6.10 Stopping Servers

You can stop each server either in the appropriate WLS Admin Console or from the Windows Start menu. These instructions are provided for your information; you do not need to do them now.

6.10.1 Stopping the Forms Server

The Oracle Forms Server is located on the WebLogic Server domain that must be named FRDomain and must use port number 7001.

To stop the Forms Server, do either:

- Start, then All Programs, then Oracle Classic asinst_1, then Forms, then Stop WLS_FORMS.

- Use the Admin Console at http://host:7001/console.

Note:
The Admin Console is available only if the Admin Server is running.

6.10.2 Stopping the Reports Server

The Oracle Reports Server is located on the WebLogic Server domain that must be named FRDomain and must use port number 7001.

To stop the Reports Server, do either:

- Start, then All Programs, then Oracle Classic asinst_1, then Reports, then Stop WLS_REPORTS.

- Use the Admin Console at https://host:7001/console.

Note:
The Admin Console is available only if the Admin Server is running.

6.10.3 Stopping the FRDomain Admin Server

The Oracle FRDomain Admin Server is located on the WebLogic Server domain that must be named FRDomain and must use port number 7001.

To stop the Admin Server, do either:

- Start, then All Programs, then Oracle Classic asinst_1, then Stop Admin Server.

- Use the Admin Console at https://host:7001/console.

6.10.4 Stopping the OPADomain Admin Server

The Oracle OPADomain Admin Server is located on the WebLogic Server domain that the Installer names OPADomain, and which must use port number 7101.

To stop the Admin Server, do either:

- Start, then All Programs, then Oracle WebLogic Server, then User Projects, then OPADomain, then Stop Admin Server.

- Use the OPADomain Admin Console at http://host/opaconsole or http://host:7101/opaconsole (if it's configured)

6.10.5 Stopping the OpaServer1 Server

The OpaServer1 Server is located on the WebLogic Server domain named OPADomain, which must use port number 7101.

To stop the OpaServer1 Server, use the Admin Console at either:

- http://host:7101/console

- https://host/opaconsole (if configured)

Note:
The Admin Console is available only if the Admin Server is running.

7 Upgrading Oracle Thesaurus Management System to Release 5.1

This chapter describes the recommended approach to upgrading an existing Oracle Thesaurus Management System installation to Release 5.1. Supported upgrade paths include:

- Release 4.6.1 or 4.6.2

- Patch Set 4.6.3, 4.6.4, 4.6.5, 4.6.6 or later

- Release 5.0

- Patch Set 5.0.1

Note:
If you are upgrading from Release 4.6 or earlier you must upgrade to Release 4.6.2 first. You must open a Service Request (SR) on My Oracle Support at https://support.oracle.com to download the Release 4.6.2 media.
A revised version of the TMS 4.6.2 Installation Guide is posted at http://www.oracle.com/technetwork/documentation/hsgbu-clinical-407519.html.

Be sure you are using the latest documentation:

- Check My Oracle Support Article ID 1572864.1 for any known installation issues; see "Finding Information on My Oracle Support".

- Check the Oracle Health Sciences Clinical documentation page at http://www.oracle.com/technetwork/documentation/hsgbu-clinical-407519.html to be sure you have the latest version of this guide.

- Check My Oracle Support Article ID 1931236.1 for the latest release of the Oracle Thesaurus Management System Release 5.1 Release Notes

Review Chapter 1, "Preparing to Install Oracle Thesaurus Management System" for system requirements and planning information.

This chapter includes:

- Section 7.1, "Upgrade Oracle Clinical (If Integrated with Oracle Clinical)"

- Section 7.2, "Install Oracle Database"

- Section 7.3, "Install the TMS Database Server Code"

- Section 7.4, "Upgrade a Single or Master TMS Database"

- Section 7.5, "Upgrade Slave TMS Databases (Distributed Environments Only)"

- Section 7.6, "Upgrade Cloned Databases"

- Section 7.7, "Run Scripts to Gather Schema Statistics for the 11g Optimizer"

- Section 7.8, "Install or Upgrade the Application Tier Technology Stack"

- Section 7.9, "Install the TMS Front End and Reports Server"

- Section 7.10, "Redefine the TMS Load User"

Critical Patch Updates See Section 1.8, "Applying Oracle Critical Patch Updates."

Oracle Database 12.1.0.1  includes many new features including multitenancy, which allows you to create one or more pluggable databases (PDBs) contained in a single root or container database (CDB). You can install Oracle Thesaurus Management System on either a pluggable database or a non-CDB database (as in 11g). For more information on multitenancy, see http://docs.oracle.com/database/121/CNCPT/cdbovrvw.htm.

For information about upgrading and migrating your existing database, see "Upgrading to Oracle Database 12c (12.1.0.2)" at http://www.oracle.com/technetwork/database/upgrade/upgrading-oracle-database-wp-12c-1896123.pdf.

For more information about new features see Oracle White Paper Plug into the Cloud with Oracle Database 12c at http://www.oracle.com/technetwork/database/plug-into-cloud-wp-12c-1896100.pdf and, for more details, the Oracle® Database New Features Guide 12c Release 1 (12.1) at http://docs.oracle.com/database/121/NEWFT/toc.htm.

7.1 Upgrade Oracle Clinical (If Integrated with Oracle Clinical)

If you are upgrading both Oracle Clinical and TMS in an integrated installation, upgrade Oracle Clinical first. See the Oracle Clinical Installation Guide.

7.2 Install Oracle Database

You must install Oracle Database 12c Release 1 (12.1.0.1). You cannot upgrade your existing Oracle Database installation.

Note:
If you are using TMS with DMW or LSH 2.4.x, do not install Oracle Database 12c. You must remain on Oracle Database 11g.

7.2.1 Installing the Oracle Database Server on UNIX

To install on UNIX, follow instructions in Chapter 2, "Installing Oracle Database on UNIX"

7.2.2 Installing the Oracle Database Server on Windows

To install on Windows, follow instructions in Chapter 3, "Installing Oracle Database on Windows".

7.3 Install the TMS Database Server Code

Follow instructions in Section 4.2, "Installing the TMS Database Server Code".

7.4 Upgrade a Single or Master TMS Database

Follow the instructions in this section when you are upgrading a single TMS database or, if you have a distributed environment, to upgrade the master TMS database. You must perform the tasks described in previous sections first.

Note:
Even if you have Oracle Clinical integrated with TMS, re-registering databases is not required during an upgrade.

- Section 7.4.1, "Suspend Symmetric Replication (Distributed Environment Only)"

- Section 7.4.2, "Prevent Access to Oracle Thesaurus Management System Databases"

- Section 7.4.3, "Upgrade to Oracle Database 12.1.0.1"

- Section 7.4.4, "Gather Required Information"

- Section 7.4.5, "Stop PSUB Process (If Integrated with Oracle Clinical)"

- Section 7.4.6, "Start the Installer"

- Section 7.4.7, "Attend to the TMS Database Upgrade Installer Screens"

- Section 7.4.9, "Check Installation Log for Errors"

- Section 7.4.10, "Configure DSI Import"

- Section 7.4.11, "Load Dictionaries"

- Section 7.4.12, "Create an Export File (Distributed Environments Only)"

7.4.1 Suspend Symmetric Replication (Distributed Environment Only)

If TMS is running in a distributed environment, suspend symmetric replication and drop the replication group before you patch Oracle Database 12.1.0.1 or the TMS databases by following the instructions in this section. Use the suspend scripts that are in your TMS server code area.

Table 7-1 Symmetric Replication Suspend Scripts and Instructions

Run Script

Where?

For Where?

Parameters

Purpose and Comments

tmsmupgsrsuspend.sql

Master instance

Master instance

None

Purpose: Suspends replication activity for all sites.

Comment: Wait until the dba_repgroup view has a status of QUIESCED on the master instance and all slave instances.

tmsmupgsrdrop.sql

Master instance

Master instance

None

Purpose: Drops replication group for all sites.

Comment: Wait until the dba_repcatlog view is empty on the master instance and on all slave instances.

To suspend replication:

1. Log in to the server using an account with system administrator privileges.

2. Open a MS-DOS command window.

3. Change to the OPA_HOME directory where the install scripts are located, for example:

cd c:\opapps51\tms\51\install

4. Set the local name for your master site:

set local=Master_Site

Note:
Ensure that you explicitly set the local name so that the system does not use the Oracle local registry variable by mistake. For this reason, it is best to run the upgrade scripts from the Command window, rather than from SQL*Plus.

5. Issue these commands:

sqlplus repsys/password

start tmsmupgsrsuspend

6. Unschedule the push operation from each slave site to the master site and from the master to each slave. Unschedule as many jobs as necessary to ensure that no scheduled push jobs remain.
Connect to each site as REPSYS and issue this command:

exec dbms_defer_sys.unschedule_push('remote_site');

7. Connect as REPSYS at each slave site and run the following script. On each updateable snapshot site (slave site), this script drops the TMS Snapshot Replication and Refresh Groups.

start tmsssrdrop

8. Connect as TMS at each slave site and run the following script. This step drops the TMS replicated tables on all sites.

start tmsssrdroptables

9. Connect as TMS at the master site and run the following script, which drops the TMS Snapshot Logs at the master site.

start tmsmsrdropmvlog

10. Connect as REPSYS on the master site and issue the following command, which drops the TMS Master Replication Group.

start tmsmupgsrdrop

Note:
You must follow steps in Section 7.4 to upgrade the master database before proceeding to the next step.

7.4.2 Prevent Access to Oracle Thesaurus Management System Databases

You must ensure that no data entry is performed, and no jobs that update data (such as batch validation) run during the upgrade process.

To prevent users from accessing the data, place the database in restricted mode. Provide restricted session access to the following accounts:

- SYSTEM

- SYS

- OPA

- RXC

- TMS

- CTXSYS

- BC4J_INTERNAL

- OPS$TMSBROWSER

- TDX

After you complete the upgrade, remove the restricted access from the databases and user accounts.

7.4.3 Upgrade to Oracle Database 12.1.0.1

Oracle recommends backing up your database(s) at this point.

Do one of the following:

- Upgrade in Place

- Clone Your Database

Note:
Choose to configure the database to accept connections as a service instead of a SID. Service name requirements for Oracle Thesaurus Management System include:

- The service name must be less than 15 characters long.

- It must not include the domain.

- It must be all lowercase.

The Oracle Thesaurus Management System Installer no longer works if you set up connections using the SID.

Note:
If you are installing the Oracle Thesaurus Management System database on a pluggable Oracle 12.1.0.1 database (PDB), see My Oracle Support article ID 1910177.1, How To Configure TNS / SQLNET using the local_listener parameter for Pluggable Database In Oracle 12c, Allowing a SQLNET Connection to the PDB. See "Finding Information on My Oracle Support".

7.4.3.1 Upgrade in Place

1. Install Oracle Database 12.1.0.1 binaries in the Oracle_Home. See Section 4.3, "Review Database Requirements and Recommendations (All Databases)."

2. To use one or more pluggable databases, create an Oracle Database Container Database (CDB). (If you are upgrading multiple databases, you still need only one CDB.)
Update the listener and tnsnames.ora either before or after the next step.

3. Upgrade your database to Oracle Database 12.1.0.1 using the Database Upgrade Assistant (DBUA) following Method 1 described in "Upgrading to Oracle Database 12c (12.1.0.2)" at http://www.oracle.com/technetwork/database/upgrade/upgrading-oracle-database-wp-12c-1896123.pdf.

7.4.3.2 Clone Your Database

1. Install Oracle Database 12.1.0.1 binaries in the Oracle_Home. See Section 4.3, "Review Database Requirements and Recommendations (All Databases)."

2. To use one or more pluggable databases, create an Oracle Database Container Database (CDB). (If you are upgrading multiple databases, you still need only one CDB.)
Update the listener and tnsnames.ora either before or after the next step.

3. Clone your database. See Oracle White Paper Cloning Oracle Clinical and TMS Databases, article ID 883213.1 on My Oracle Support. See "Finding Information on My Oracle Support".

7.4.4 Gather Required Information

Before you start the Installer, be sure you have the information it prompts for:

1. Home Details: The full path to the Oracle Home location on your application server; by default:
C:\app\oracle\Middleware\Oracle_FRHome1

2. TMS Server Code Home Directory: The system detects the location and enters the value for you. By default, it is C:\opapps51\tms.

3. Database Connect String: Enter the database name. It must be a valid TNS entry in your tnsnames.ora file.

4. NLS Settings: Enter the NLS settings for the database; see Section 1.7, "Choosing a Character Set". Oracle strongly recommends that you use UTF8. The default values are:

- American_America.UTF8

- DD-MON-RRRR

5. Directory for data tablespace data files: Enter the path to the directory on the database server where the data tablespace datafiles for the application should be created during the installation. The Installer does not validate the value and you must use the following syntax, including a trailing slash, depending on your operating system; for example:

- UNIX: /u01/oradata/dbname/

- Windows: drive:\oradata\dbname\

6. Enter and confirm passwords for the following accounts:

- SYS

- SYSTEM

- RXC

- OPA

- TMS

- CTXSYS

7.4.5 Stop PSUB Process (If Integrated with Oracle Clinical)

If your TMS installation is integrated with Oracle Clinical, you must stop the PSUB process before upgrading the database. See the Oracle Clinical Administrator's Guide for instructions.

7.4.6 Start the Installer

To upgrade a TMS database:

1. Log in to the application server as a user with system administrator privileges.

2. In the staging area, locate the directory where you downloaded and extracted Oracle Thesaurus Management System (see Section 1.4, "Downloading and Extracting the Software").

3. Run the following file as an administrator:
Disk1\install\setup.exe

The Installer opens to the Welcome screen.

Note:
See Section 1.5, "Using the Silent Installer" for instructions for running the Installer as a file with pre-entered parameter values.

Note:
Although there is a button for deinstalling products on the Welcome screen, Oracle does not support using the Installer to deinstall Oracle Thesaurus Management System.

4. In the Select a Product to Install page, select TMS Database Upgrade 5.1.0.0.x.

5. What type of installation do you want?

- Select Master if you are planning to use only one database or if you have a distributed environment (using data replication) and this is the master database.

- Select Slave only if you have a distributed environment and this is a slave, or local, database.

7.4.7 Attend to the TMS Database Upgrade Installer Screens

The Oracle Universal Installer guides you through the database upgrade. Provide the information you assembled in "Gather Required Information."

Ignore tablespace creation errors:

- Select Yes if the database already has the TMS tablespaces created.

- Select No if the TMS tablespaces do not exist.

The Installer gives you information that you should make a note of.

7.4.8 Set Initialization Parameters

After the upgrade completes, set the init.ora parameters according to the instructions in Section 4.3.7, "Set Initialization Parameters."

You must stop and then start the database to activate the changed init.ora parameters.

Notes:
Do NOT SET the DB_DOMAIN parameter. In Release 5.1 and above this causes problems.
If you set up the EVENT parameter in the init.ora file to trace unique key constraints before upgrading, you should set the event parameter back to its required value.

7.4.9 Check Installation Log for Errors

When you upgrade, the installation log file may report the following error:

".....
Connected.
BEGIN tms_dsi_xml_schema.InstallSchemas; END

*
ERROR at line 1:
ORA-02303: cannot drop or replace a type with type or table dependents
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 3
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 14
ORA-06512: at "TMS.TMS_DSI_XML_SCHEMA", line 35
ORA-06512: at line 1

finished TMSUPG
TMS will now attempt to validate any invalidate objects...
...."

This error occurs because the tmsupg.sql upgrade script executes tms_dsi_xml_schema.InstallSchemas before attempting to validate any invalid objects. Execution of tms_dsi_xml_schema.InstallSchemas fails if the database has invalid objects.

If this error occurs, you need to:

1. Run compile invalid until all database objects have been made valid.

2. Run tms_dsi_xml_schema.InstallSchemas manually. See Section 7.4.10, "Configure DSI Import" for details.

7.4.10 Configure DSI Import

If you plan to use disconnected system integration (DSI), enter following commands:

set LOCAL=databasename
sqlplus tms/password
exec tms_dsi_xml_schema.InstallSchemas;

7.4.11 Load Dictionaries

If you need to upgrade any dictionaries or load new dictionaries and are installing a distributed environment, this is a good time to do it since you have suspended replication and will next do an export/import. However, you can load dictionaries at any time.

If you are installing TMS with AERS in a distributed environment, you must load the AERS-TMS dictionaries onto the master database before creating an export file and importing it to the slave databases.

See the Oracle Thesaurus Management System User's Guide for information about loading dictionaries.

7.4.12 Create an Export File (Distributed Environments Only)

If you are upgrading a distributed environment, follow instructions in Section 4.8.1, "Export Data from the Master Database."

7.5 Upgrade Slave TMS Databases (Distributed Environments Only)

Follow the instructions in this section to upgrade existing slave databases in a distributed environment.

1. Follow these instructions:

1. Section 7.4.1, "Suspend Symmetric Replication (Distributed Environment Only)"

2. Section 7.4.3, "Upgrade to Oracle Database 12.1.0.1"

3. Section 7.4.4, "Gather Required Information"

4. Section 7.4.5, "Stop PSUB Process (If Integrated with Oracle Clinical)"

5. Section 7.4.6, "Start the Installer"

6. Section 7.4.7, "Attend to the TMS Database Upgrade Installer Screens"

7. Section 7.4.8, "Set Initialization Parameters"

8. Section 7.4.9, "Check Installation Log for Errors"

9. Section 7.4.10, "Configure DSI Import"

2. Import data from the master instance. Perform this task on the database server. At every slave database, import the export file you created in the previous task.
See Section 4.8.2, "Import Data to the Slave Database" for more information.

Note:
You must first create an export file of the master database; see Section 4.8.1, "Export Data from the Master Database."

3. On the TMS application server, set the LOCAL variable and run the tmsupgslave.sql script by entering the following commands in a MS-DOS window:

cd OPA_HOME\tms\51\install
sqlplus system/password
start tmsupgslave.sql

The script generates a log file in the install directory named tmsupgslave_database_name.log.

Note:
When upgrading a slave database to Release 5.1, the following types of errors occur in the tmsupg_database_name.sql log file:

Warning: Package created with compilation errors. (and appended PLSQL errors with line numbers)
Warning: Package Body created with compilation errors. (and appended PLSQL errors with line numbers) ORA-00942: table or view does not exist
ORA-01775: looping chain of synonyms
ORA-04063: view "TMS.view_name" has errors

As long as there are no errors in the log file, tmsupgslave_database_name.sql, and there are no invalid OPA/TMS objects in the database after the upgrade, the upgrade can be considered successful and these errors can be ignored.

4. Start symmetric replication, following instructions in Section 4.8.6.2, "Start Replication on the Master Database" and Section 4.8.6.3, "Start Replication on Each Slave Instance."

7.6 Upgrade Cloned Databases

If you have cloned a database, see Cloning Oracle Clinical and Oracle Thesaurus Management System Databases (Article ID 883213.1) on My Oracle Support:

Be sure to follow all the instructions in the document, including running the tmschown.sql script, the opachown.sql script, and, if you are using Oracle Clinical with TMS, the chown.sql script, before doing the upgrade.

7.7 Run Scripts to Gather Schema Statistics for the 11g Optimizer

After upgrading to Release 5.1 and setting initialization parameter optimizer_features_enable to 11.2.0.4 (see Section 4.3.7, "Set Initialization Parameters"), you must gather statistics required for the Oracle 11g Optimizer to be effective for accounts used internally by TMS.

Scripts opastats.sql and tmsstats.sql are available for this purpose. Failure to execute these scripts can negatively impact performance.

If your database contains large amounts of data, the scripts may take a long time to run. You may want to edit the scripts. For information the scripts' parameters see documentation of the Oracle DBMS_STATS package that they call: http://docs.oracle.com/cd/B19306_01/appdev.102/b14258/d_stats.htm#i1036456.

tmsstats.sql Since TMS already has a procedure, AnalyzeTables in tmspb_user_analyze.sql, that runs as part of every activation job, you may prefer to edit tmspb_user_analyze.sql if required and call it from tmsstats.sql to keep the two synchronized.

The tmsstats.sql script prompts for the password of the account it processes: TMS.

To change how TMS analyzes tables and ensure that tmsstats and AnalyzeTable remain in synch:

1. Modify the lAnalyzeTable procedure in tmspb_user_analyze.sql.

2. Edit tmsstats.sql to call tms_user_analyze.AnalyzeTable. Replace the section that analyzes tables with:
exec tms_user_analyze.AnalyzeTables

3. Run tmsstats.sql.

opastats.sql captures new statistics in the OPA application account used by TMS. It prompts for the OPA password. It is also used by Oracle Clinical and RDC Onsite.

7.8 Install or Upgrade the Application Tier Technology Stack

Whether you need to install or upgrade depends on what release you are upgrading from.

7.8.1 Upgrading from a Release Earlier than 5.1

If you are upgrading from a release prior to 5.1, you cannot upgrade the application tier. You must install it fresh because Release 5.1 and later use a different technology stack:

- Oracle Application Server 11gR2, which includes the Oracle Forms Server and the Oracle Reports Server. Both are required for Oracle Thesaurus Management System.

- WebLogic Server 11gR1 (10.3.6) and Oracle Application Developer Framework 11g R1. These are required for TMS Browser.

You can install all components on the same machine, or install on multiple machines, but you must install all components on all machines and then disable services on the machine(s) where they are not needed.

To ensure high availability of the Reports Server, you can set up and use more than one Reports Server on a subnet and they can access each other. For more information see the Oracle Clinical Administrator's Guide.

Follow all instructions in Chapter 5, "Installing and Configuring the Application Tier."

7.9 Install the TMS Front End and Reports Server

7.9.1 Install the Oracle Thesaurus Management System Front End and Reports Server

If you are upgrading from a release prior to 5.1, you cannot upgrade the application tier.

Follow instructions in Chapter 6, "Installing Oracle Thesaurus Management System Application Components."

Note:
If you have already installed the Oracle Clinical Reports Server on this machine, you do not need to install the TMS Reports Server.
The Installer prevents you from installing two Reports Servers with the same name.

7.9.2 Set Remote Method Invocation (RMI) JDBC Security to Secure

1. Log in to the WebLogic Server

2. Go to Summary of Servers, select OpaServer1, select General, and click Advanced.

3. Change the RMI JDBC Security setting to Secure.

4. Click Save.

5. Click Activate Changes.

7.10 Redefine the TMS Load User

During the upgrade process, the tables accessed by the TMS load user are dropped and recreated, so the load user loses the grants required to load dictionary data.

To re-grant the required privileges:

1. In TMS, navigate to Security, then Define Users.

2. Query for the load user your company created.

3. Uncheck LoadUser?.

4. Save.

5. Check Load User?.

6. Save.

8 Post-Installation Steps for the New Installation or Upgrade

This chapter includes:

- Section 8.1, "Patch TMS"

- Section 8.2, "Test the TMS Forms Server"

- Section 8.3, "Configure WebLogic Server Data Sources"

- Section 8.4, "Making the Java Runtime Environment Available for Download"

- Section 8.5, "Create a Link to TMS HTML Browser"

- Section 8.6, "Define and Load Dictionaries"

- Section 8.7, "Setting Up Client Computers"

8.1 Patch TMS

Check Oracle Thesaurus Management System Patches (Article ID 132626.1) on My Oracle Support for information about any patch sets and patches that have been released since Release 5.1. See "Finding Information on My Oracle Support".

8.2 Test the TMS Forms Server

Confirm that you can start TMS from this Forms Server before you set up each TMS client.

To test the deployment:

1. Open a browser.

2. Connect to the Oracle Health Sciences URL to start TMS.
The URL has the following syntax:

https://computer_name.domain/opa51/launch.htm

3. Click the Launch hyperlink, which initiates the download of the Java Virtual Machine (JVM).

8.3 Configure WebLogic Server Data Sources

When you run the TMS Installer, it sets up a connection, or data source, for OPA and another for the TMS Browser from the WebLogic Server to the database that you specify in the Installer screens.

Confirm that the OPA data source exists in the WebLogic Server Administration Console and then enter its JNDI name in the REPORT_CONFIG local reference codelist.

8.3.1 Confirm the OPA Data Source Value in WebLogic Server Admin Console

To check this:

1. Log in to the WebLogic Server Administration Console at:

http://host:7101/console

2. Navigate to Services under Domain Structure, then Data Sources.

3. Confirm that a data source with JNDI name: jdbc/opadatabase_nameDS exists.

8.3.2 Set REPORT_CONFIG Reference Codelist Value

Update local reference codelist REPORT_CONFIG with the data source JNDI name:

1. Log in to TMS.

https://computer_name.host/opa51/launch.htm

2. Navigate to Definition, then Local Reference Codelists.

3. Query for the REPORT_CONFIG codelist:

1. Press F7.

2. Enter REPORT_CONFIG in the Name field.

3. Press F8. The system displays the short value JDBC_DATA_SRC.

4. Enter the JNDI name value jdbc/opadatabase_nameDS as the long value.

5. Save.

8.3.3 Add Data Source (Required Only If Using Multiple Databases)

When you run the TMS Installer, it sets up a data source connection for OPA and the TMS HTML Browser from the WebLogic Server to the database you specify in the Installer screens.

If you plan to use more than one database, you must create an OPA and a TMS Browser data source for each additional database. The OPA data source is used to run TMS reports.

Complete instructions are in the Oracle Thesaurus Management System User's Guide chapter on Administration.

8.4 Making the Java Runtime Environment Available for Download

Oracle Thesaurus Management System requires that the Java Runtime Environment (JRE) exists on the user's computer.

The TMS Launch page is configured to prompt users to install JRE if it does not exist on their computer. To make this work, you need to download JRE into the OPA_HOME\html directory and rename it.

Note:
If you have already installed Oracle Clinical on the same machine, you do not need to do this again.

To download the latest version of the JRE and then position the software so your users can install it directly from the Downloads page:

1. If you have not already done so, download the software following instructions in Section 1.4.5, "Downloading the Java Runtime Environment."

2. Copy the downloaded file from the staging area to OPA_HOME\html.

3. Rename the file sunjpi.exe.

If your users need to have both JRE 6 and 7 installed to support different versions of Oracle Thesaurus Management System, check My Oracle Support article 1570682.1 for guidance; see "Finding Information on My Oracle Support".

8.5 Create a Link to TMS HTML Browser

You need to construct a link for users to access the TMS HTML Browser. You can add it to the TMS launch page or to your own users' home page. You can add links for more than one database if needed, and you can enable automatic login.

For instructions, see the administration chapter of the Oracle Thesaurus Management System User's Guide.

8.6 Define and Load Dictionaries

See the Oracle Thesaurus Management System User's Guide for information about defining TMS dictionaries in the user interface and loading dictionary data.

For sample load scripts, download the following document from My Oracle Support:

Title: Sample Maintenance Scripts for MedDRA, MedDRA Primary Path, MedDRA SMQ, WHO-Drug Formats B, B2, and C, and SNOMED

Article ID: 258975.1

Note:
If you are upgrading an existing TMS installation, you do not need to redefine and reload the dictionaries you are already using.

8.7 Setting Up Client Computers

This section includes:

- Section 8.7.1, "Configuring Personal Firewall"

- Section 8.7.2, "Using Safari on an iPad"

- Section 8.7.3, "Setting Internet Options for Microsoft Internet Explorer"

- Section 8.7.4, "Download the Java Virtual Machine to Client Computers"

- Section 8.7.5, "Logging In"

8.7.1 Configuring Personal Firewall

If the client computer has a personal firewall, you must either disable it or configure it for the TMS Browser to function correctly. See your firewall documentation or ask your system administrator for assistance.

8.7.2 Using Safari on an iPad

On an iPad, which is supported for the TMS Browser, some functionality available on a personal computer using a mouse is not available, including:

- Right-click and double-click options.

- Selecting multiple records using Ctrl+click

8.7.3 Setting Internet Options for Microsoft Internet Explorer

Users who use the TMS Browser or TMS reports should change their Internet Explorer settings as follows.

8.7.3.1 Setting Document Mode to Quirks (the Default Setting)

Internet Explorer 8 and above include a set of tools that enable Web site developers to prototype and test Web sites they develop, including the Document Mode setting.

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.

Ensure that the Document Mode is set to Quirks Mode (Page Default):

1. Launch Internet Explorer.

2. Open the Tools menu, and then select Developer Tools.

3. Set the Document Mode to Quirks Mode (Page Default).

8.7.3.2 Disabling Cookies

Before a user runs TMS reports, he or she must disable cookies on their computer:

1. In the IE Tools menu, go to Internet Options.

2. Click the Privacy tab, then Settings.

3. Move the slider to the top to block all cookies.

4. Click OK, then OK again.

8.7.3.3 Allowing More Connections

By default, Internet Explorer allows only two connections at a time to the same server. However, TMS Browser users may want to have more. If so, they can follow instructions from Microsoft at http://support.microsoft.com/kb/282402#fixit4me. The problem description is about being unable to download only two files at a time, but the fixes described work for this issue as well.

8.7.3.4 Turning Off Compatibility View

The TMS Browser does not support the Compatibility View available on Internet Explorer 8 and above. If the setting is enabled in in the browser, when a user tries to access the TMS Browser, he or she sees the following message: "The current compatibility setting is not supported." There are several places to turn off Compatibility View:

- In the IE Tools menu, toggle between turning Compatibility View on an off by clicking Compatibility View.

- The above setting is overridden by those found in the Tools menu under Compatibility View Settings. Uncheck both: Display intranet sites in Compatibility View and Display all websites in Compatibility View

- The Compatibility View icon:

appears in the address bar when it is turned on for the current website. Click the icon to turn it off.

8.7.3.5 Set Up for Proxy Usage on Fully Qualified Application Tier Names

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:

1. Start Internet Explorer.

2. Open the Tools menu, and then select Internet Options.

3. Click the Connections tab.

4. Click LAN settings to open the Local Area Network (LAN) Settings dialog box.

5. Select Use a proxy server for your LAN, and then click Advanced.

6. 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.

8.7.4 Download the Java Virtual Machine to Client Computers

To download the Java Virtual Machine (JVM) onto each client computer:

1. Open a browser.

2. Connect to the Oracle Health Sciences URL.
The URL includes the path variable you specified in Section 8.2, "Test the TMS Forms Server."

The first time you open TMS, the system prompts you to download JVM. This download is required. It is also available from a link on the Launch page.

8.7.5 Logging In

TMS To log in to Forms-based Oracle Thesaurus Management System, use the following URL:

https://computer_name.domain/opa51/launch.htm

TMS Browser To log in to the TMS Browser, use the following URL:

https://computer_name.domain/tmsadf/faces/Login?setUpDone=Y

Note:
See the chapter on administration in the Oracle Thesaurus Management System User's Guide for information about customizing the URL to support automatic login and multiple databases.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2017, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.