| Oracle® Thesaurus Management System Installation Guide Release 5.1 E53656-03 |
|
|
PDF · Mobi · ePub |
| Oracle® Thesaurus Management System Installation Guide Release 5.1 E53656-03 |
|
|
PDF · Mobi · ePub |
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:
Restart the computer and then stop all servers and services:
Restart the computer.
In the Windows Services control panel, find Oracle Node Manager service and stop it.
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.
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.
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:Open an MS DOS window.
Go to oracle_instance/bin.
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
To install the TMS Front End:
Log in as a user with system administrator privileges.
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").
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.The Oracle Universal Installer guides you through the installation and configuration of the TMS Front End.
Product to install: Oracle Thesaurus Management System Front End.
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.
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.
Follow the instructions on the installation screens, providing the information you assembled in Section 6.2.1, "Gather Required Information.".
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.
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.
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.
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.
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.
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.
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.
Copy the downloaded file from the staging area to OPA_HOME\html.
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".
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.
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.
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.
To install the TMS Report Server:
Log in as a user with system administrator privileges.
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").
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.In the Select a Product to Install page, select Oracle Thesaurus Management System Report Server 5.1.0.0.x.
The Oracle Universal Installer guides you through the installation and configuration of the TMS Reports Server.
See Section 6.2.1, "Gather Required Information." Some of the same information is required for the Report Server.
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.
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.
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
Check values and correct them if required.
To check variable values:
Open a DOS prompt window.
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.
Inspect the value of JAVA_HOME:
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."
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".
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".
To correct any of the above problems:
Navigate to middleware_home\wlsserver_10.3\common\bin
Back up commEnv.cmd.
Open commEnv.cmd in a text editor.
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
Find:
set JAVA_VM=-client
change it to:
set JAVA_VM=-server
Close the DOS window and open a new one, then repeat the steps in Section 6.6.1, "Check Values".
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.
Create a task and set up the Task Scheduler to run the job on bootup:
From Start, then Control Panel, then Administrative Tools, open Task Scheduler.
Select Create Basic Task on the right side of the Task Scheduler.
Enter following values:
Name: Oracle FRDomain Autostart
Trigger: When the computer starts
Action: Start a program
Select:opa_home\config\autostartFRDomain.cmd
Click Next and then Finish to complete creation of the scheduled task.
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.
On the General tab, select Run whether user is logged on or not.
Repeat these steps for OPADomain, with two differences. In Step 3, enter:
Name: Oracle OPADomain Autostart
Select:opa_home\config\autostartOPADomain.cmd
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.
From a different DOS window, enter command:
opa_home\config\autostartopadomain2.cmd
to start the OPADomain server.
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 ...
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
To test:
Restart the computer.
Allow some time for the services to start.
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
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.
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.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.
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.
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.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)
Verify that these URLs work and you can log into application:
https://host/opa51/launch.htm
https://host/tmsadf/faces/Login
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.
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.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.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.
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)
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.
|
 Copyright © 1999, 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|