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 Lite 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 the Oracle Node Manager service and start it.
From the Windows Start menu, go to All Programs, then Oracle Classic_asinst_1, then:
Under Forms Services, make sure that WLS_FORMS is running.
Under Reports Services, make sure that WLS_REPORTS is running.
Stop the OPADomain Server. NOTE: This is required if you are installing the TMS Front End after the Oracle Clinical Front End is already installed. 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: Enter the following:
Name: OPA_HOME
Path: C:\opapps52
Java home is located in version JDK 1.8.0_111 or higher.
Your Oracle Fusion Middleware home directory; for example:
C:\Oracle\Middleware\Oracle_Home
Your OPA home directory; by default:
C:\opapps52
WebLogic username: The account created when you installed the WebLogic Server.
WebLogic Server Password: Enter a new password or use the password you created when installing WebLogic Server.
Administration Server configuration details:
Listen address
Listen port number
SSL listen port number
WebLogic username
Node Manager configuration details:
Listen address
Listen port number
WebLogic username
WebLogic Server password
Managed Server configuration details:
Number of Managed Servers
Listen port start index
Database details:
Server.Domain; for example:
servername.your_company.com
Port number
Database service name
Oracle Fusion Middleware Repository Creation Utility (RCU) configuration details:
Schema prefix
Database administrator username and password
RCU schema password
Oracle HTTP Server (OHS) port information:
Oracle HTTP Server SSL Listen Port number
Oracle HTTP Server Non-SSL Listen Port number
To get the port numbers, check the httpd.conf and ssl.conf files located at ORACLE_HOME\user_projects\domains\FRDomain\config\fmwconfig\components\OHS\instances\ohs1.
To check, go to the URL https://host:port with each port.
TMS Proxy Password (tmsproxy)—the password you created when installing Oracle Thesaurus Management System database objects.
Wallet location: for the Wallet you created in Section 3.11, "Enable SSL Between a Browser and Oracle HTTP Server". (You can browse for it on screen.)
Online help URL: If you have customized the online help, the URL where the customized online help is located.
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.6, "Download the Software").
Run the following file as an administrator:
Disk1\install\setup.exe
The Installer opens to the Welcome screen.
Note:
See Section 1.7, "Use the Silent Installer (Optional)" 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.
Select a Product to install: Oracle Thesaurus Management System Front End 5.2.1.0.x.
Home Details: There are two drop-downs, Oracle Home Name and Directory. Use the Directory drop-down to select the OPA Home that corresponds to the Oracle Forms and Reports home, similar to C:\opapps52.
When you select the directory, the Home value changes automatically.
Choose Install Type: Select Yes to install a Oracle Thesaurus Management Front End.
Available Product Components: Select Oracle Thesaurus Management System Front End 5.2.1.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.Follow the instructions on the installation screens, providing the information you assembled in Section 5.2.1, "Gather Required Information.".
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.
Install: The Installer copies the files onto the server, completes the setup and configuration tasks, and generates a log file of this installation.
In addition, the Install screen displays the location of the log file that records the results of the installation activities for this session. Make a note of this information so you can view the log file after the installation.
End of Installation: The End of Installation screen reports whether the installation was successful. In addition, this screen lists the URLs that you use to access the Oracle Clinical, RDC Onsite, and RDC Administration applications.
The Installer saves the URL information in the following file:
\opapps52\log\setup.txt
When you have finished reviewing the installation information, click Exit.
During the installation of an Oracle Health Sciences component, the Oracle Universal Installer generates the following log file:
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
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.6.6, "Download 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.
This section describes installing and configuring a Reports Server. The TMS Reports Server runs on Oracle Forms and Reports 12c (12.2.1.2). 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.
The WebLogic FRDomain Admin Server must be running when you install the Reports Server.
At the DOS command prompt, do one of the following:
Go to ORACLE_HOME\user_projects\domains\FRDomain\bin and run the startWebLogic.cmd.
Go to C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Oracle FMW 12c Domain-FRDomain - 12.2.1.2.0 and run startWeblogicAdminServer.cmd.
Go to ORACLE_HOME\user_projects\domains\FRDomain\bin and run startNodeManager.cmd.
Have the following information ready to enter in the Installer screens:
Home Details: Enter the following:
Name: OPA_HOME
Path: c:\opapps52
Your Oracle Fusion Middleware home directory; for example:
C:\Oracle\Middleware\Oracle_Home
Your OPA home directory; for example:
C:\opapps52
WebLogic username and password
Report Server name
Report Server output directory
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.6, "Download the Software").
Run the following file as an administrator:
Disk1\install\setup.exe
The Installer opens to the Welcome screen.
Note:
See Section 1.7, "Use the Silent Installer (Optional)" 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.2.1.0.x.
The Oracle Universal Installer guides you through the installation and configuration of the TMS Reports Server.
See Section 5.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.
Review the generated installation log file, installActions
timestamp
.log
, for errors.
This is the name of the most current log file. Earlier files have a timestamp appended to the name.
Location: \Oracle\Inventory\logs
For example:
C:\Program Files\Oracle\Inventory\logs
Work with Oracle Support, if necessary, to resolve any errors.
Download the patch from My Oracle Support.
To apply the patch, follow instructions in the patch release notes.
Verify that these URLs work and you can log into the application:
Forms-based TMS—https://host/opa52/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 3.4, "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 5.7.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 5.7.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 5.7.2, "Correct Values".
To correct any of the above problems:
Navigate to middleware_home
\Oracle_Home_FR\oracle_common\common\bin
.
Back up commEnv.cmd.
Open commEnv.cmd in a text editor.
The first set
command in the file, before any other set
command, must identify the JAVA_HOME value. For example:
set JAVA_HOME=c:\app\java\jdk
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 5.7.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.
To start servers manually, see Section 5.9, "How to Start Servers Manually".
Check if the boot.properties file exists in Oracle_Home\user_projects\domains\FRDomain\servers\AdminServer\security.
If not, create it as a plain text file with the following contents:
username = weblogic_user_name password = weblogic_user_password
By default, the WebLogic user name is weblogic
. This user name and password will get encrypted after all services are started.
For OPADomain and FRDomain to start successfully, depending on the performance in your environment, you may want to increase the delay by which OPADomain and FRDomain start to allow time for Node Manager to start first.
Go to OPA_HOME\config\opa_setup_scripts\ directory.
Open the autostartfrdomain.cmd and autostartopadomain.cmd files.
In each file, find the line PING 127.0.0.1 -n 30
, and change the value from 30 to 60.
Save and close the files.
Set up the Task Scheduler to start the FRDomain and OPADomain at startup:
From Start, then Control Panel, then Administrative Tools, open Task Scheduler.
Select Create Basic Task on the right side of the Task Scheduler.
Enter the following values:
Name: Oracle FRDomainNM Autostart
Trigger: When the computer starts
Action: Start a program
Select: opa_home
\config\opa_setup_scripts\autostartfrdomainNM.cmd
Click Next and then Finish to complete creation of the scheduled task.
Find the task Oracle Domain Autostart under the Task Scheduler Library list. Right-click on the task you just created and select Properties.
On the General tab, select Run whether user is logged on or not.
Click OK.
When prompted, enter the user name and password.
Repeat the above steps for OPADomain Node Manager, OPADomain, and FRDomain, except for step 3 enter:
For OPADomain Node Manager:
Name: Oracle OPADomainNM Autostart
Select: opa_home
\config\opa_setup_scripts\autostartopadomainNM.cmd
For OPADomain:
Name: Oracle OPADomainMS Autostart
Select: opa_home
\config\opa_setup_scripts\autostartOPADomain.cmd
For FRDomain:
Name: Oracle FRDomainMS Autostart
Select: opa_home
\config\opa_setup_scripts\autostartfrdomain.cmd
From a DOS window, enter command:
opa_home2\config\opa_setup_scripts\autostart
nnnn
.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/opa52/launch.htm
TMS Lite Browser: https://server.domain/tmsadf/faces/Login?setUpDone=Y
To test:
Restart the computer.
Allow some time for the services to start.
Verify that these URLs work and you can log into application:
Oracle Clinical: https://server.domain/opa52/launch.htm
RDC: https://server.domain/rdcadfsrnd/faces/Login
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, see Section 1.2, "Architecture" and Section 1.3, "Network Topology".
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.
At the DOS command prompt, do one of the following:
Go to ORACLE_HOME\user_projects\domains\FRDomain\bin and run the startWebLogic.cmd.
Go to C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Oracle FMW 12c Domain-FRDomain - 12.2.1.2.0 and run Start Weblogic Admin Server.
Note:
You cannot start it from the Admin Console because if the server is not running, the FRDomain Admin Console is not available.Go to ORACLE_HOME\user_projects\domains\FRDomain\bin and run startNodeManager.cmd.
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:
Go to C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Oracle FMW 12c Domain - FRDomain - 12.2.1.2.0\Oracle Forms Services - WLS_FORMS and run Start Weblogic Server - WLS_Forms.
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.
Start the Reports Server in the Admin Console at http://host:7001/console.
Note:
The Admin Console is available only if the Admin Server is running.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 Managed Server of OPADomain.
To start the OPADomain Admin Server:
Go to ORACLE_HOME\user_projects\domains\OpaDomain\bin and run startWebLogic.cmd.
Note:
You cannot start from the Admin Console because if the server is not running, the OPADomain Admin Console is not available.Go to ORACLE_HOME\user_projects\domains\OpaDomain\bin and run startNodeManager.cmd.
The Managed Server of OPADomain is located on the WebLogic Server domain named OPADomain, which must use port number 7101. The Managed Server of OPADomain runs on Oracle ADF and supports RDC Onsite, the TMS Browser, and TMS reports. It also contains the database connections.
You must start the OPADomain Admin Server before the Managed Server of OPADomain.
To start the Managed Server of OPADomain, 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/opa52/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:
Stop WLS_FORMS by running ORACLE_HOME\user_projects\domains\FRDomain\bin>stopManagedWebLogic.cmd WLS_FORMS from a command prompt started as an administrator.
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:
Stop WLS_REPORTS by running ORACLE_HOME\user_projects\domains\FRDomain\bin>stopManagedWebLogic.cmd WLS_REPORTS from a command prompt started as an administrator.
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:
Stop AdminServer by running ORACLE_HOME\user_projects\domains\FRDomain\bin>stopManagedWebLogic.cmd AdminServer from a command prompt started as an administrator.
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:
Stop AdminServer by running ORACLE_HOME\user_projects\domains\OPADomain\bin>stopManagedWebLogic.cmd AdminServer from a command prompt started as an administrator.
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.