| Oracle® Thesaurus Management System Installation Guide Release 4.6.2 Part Number E18826-03 |
|
|
View PDF |
| Oracle® Thesaurus Management System Installation Guide Release 4.6.2 Part Number E18826-03 |
|
|
View PDF |
This chapter includes the following topics:
Section 8.4, "Update HTML Browser and Web Search Engine Bookmarks"
Section 8.6, "Download the Java Virtual Machine to Client Computers"
Section 8.7, "Add a Link to the TMS Launch Page for the HTML Browser"
Check My Oracle Support Article ID 132626.1, Oracle Thesaurus Management System Patches, for information about patches. See "Finding Information and Patches on My Oracle Support".
The Users page in Oracle Enterprise Manager 10g Application Server Control provides the options that let you change user passwords, add users, and delete users for the OPAAdmin application.
To change the password for the opaconfig user:
Open a Web browser and enter your URL to the Oracle Application Server Forms and Reports Services Welcome page:
computer-name.company-name.com
Click the Log on to Oracle Enterprise Manager 10g Application Server Control link to open the Application Server Home page.
Log in as user ias_admin with the password you set when you installed the Application Server.
Select the appropriate instance.
Click the opa OC4J instance.
Click the Applications tab.
Click the opaadmin link.
Click the Administration tab.
Expand the Security administration task, and then select the Go to Task icon for Security Provider.
Click the Realms tab.
Locate the jazn.com realm, and then click the number in its Users column.
Click the opaconfig user name.
Enter the old password, enter the new password, and then confirm your new password.
Click Apply. Note that the user name remains opaconfig.
Restart the opa OC4J instance.
Use the OPAAdmin application to set up the necessary database connections to be used with the TMS HTML Browser. The information that you enter for each database via the OPAAdmin application is saved in the OpaConfig.xml file on the application server.
For each database:
Enter the OPAAdmin application by opening a browser to the following URL:
http://server.domain/opaadmin/opaConfig.do
Enter your database values for the following fields:
Database Name = Name of your database
Host = Host name of your database
Port = Port number of your database
Sid = Database SID
Determine the existing BC4J password for your environment and specify it here.
Determine the existing TMS Browser password for your environment and specify it here.
Specify Default = true to identify the default database used by RDC Onsite users.
Select Save.
This section is applicable only if you are upgrading from a previous release. If you are performing a new installation, skip this section.
If you have saved bookmarks for the HTML Browser (called the "Dictionary Browser" or "Light Browser" in earlier releases) or the Web Search Engine on any clients in your installation, you must update them to the TMS 4.5 locations by making the changes described in this section.
Update every bookmark on every client. Bookmarks are not replicated among clients.
Netscape Navigator is not supported as a client for this release. If you have any bookmarks you want to carry forward into the new release, export them from Netscape to Internet Explorer.
In TMS 4.0 and later, the Dictionary Browser URL was:
http://server.domain:port/DAD/tms_user_browser.Home
where:
server.domain is the TMS application server through which you connect
port is the port used for connections to the Dictionary Browser
DAD is the Database Access Descriptor for the database you want to browse
Update these URLs to the following format:
http://server.domain:port/tms/tmsLogin.uix
Direct Old Web Search Engine Bookmarks to the HTML Browser
The Web Search Engine became obsolete in TMS 4.5, and all of its functionality included in the Source Data and Document Repository searches in the updated HTML Browser.
The Web Search Engine URL was:
http://server.domain/DAD/tms_user_doc.home
where:
server.domain is the TMS application server
DAD is the Database Access Descriptor for the database to which you are connecting
Change the URL for Web Search Engine bookmark to the URL for the updated HTML Browser.
Confirm that you can start TMS from this Forms Server before you set up each TMS client.
To test the deployment:
Open a browser.
Connect to the Oracle Health Sciences URL to start TMS.
The URL has the following syntax:
http://computer_name.domain/opa46/launch.htm
Click the Launch hyperlink, which initiates the download of the Java Virtual Machine (JVM).
To download the Java Virtual Machine (JVM) onto each client computer:
Open a browser.
Connect to the Oracle Health Sciences URL.
The URL includes the path variable you specified in Section 8.5, "Test the TMS Forms Server." For example, for the default path variable opa46, the URL is:
http://computer_name.domain/opa46/launch.htm
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.
If you plan to use the HTML Browser from this TMS application server, add an HTML Browser link to the TMS Launch page.
You can create links for more than one database. The URLs you create here bypass the single machine/port/instance combination in the bc4j.xcfg file.
You can set up links for either autologin or the login page, where users are prompted for their user name and password.
The user and schema necessary for autologin (ops$tmsbrowser) is created automatically on each database during installation.
To set up a link to the TMS Login page, it is not necessary to have the same user name and password on each database. Users must log in using their own user names and passwords.
To add an HTML Browser link to the TMS Launch page:
Open the Launch Oracle Pharmaceutical Applications page in a text editor:
OPA_HOME/html/launch.htm
Search for the text "Oracle Health Sciences User Group."
Under the </tr> tag on the next line, add lines like those shown in Example 8-1, which shows links to two databases displayed on two separate lines. The information in the actual anchor tag must be as shown, with actual values substituted for the variables as described below. To set up an autologin link, use the anchor line in Example 8-2.
Save the Launch page. Verify the link connects to the HTML Browser login page.
Example 8-1 Sample HTML Lines for Adding an HTML Browser Link to the TMS Login Page
<tr> <td><center><b><font face="Arial,Helvetica"><font size=+1><a href= "http://server.domain/tms/tmsLogin.uix">HTML Browser db1</a></font></font></b></center></td> <td><font face="Arial,Helvetica">Launch HTML Browser</font></td> </tr> <tr> <td><center><b><font face="Arial,Helvetica"><font size=+1><a href= "http://server.domain:7881/tms/tmsLogin.uix?event=setDb&dbJDBCurl=machine:port:db2">HTML Browser db2</a></font></font></b></center></td> <td><font face="Arial,Helvetica">Launch HTML Browser</font></td> </tr>
These lines add a new row for the HTML Browser under the "Oracle Health Sciences User Group" link. The variables in these lines mean the following:
server is the TMS application server to which you are connected
domain is the domain for your TMS application server; for example, us.oracle.com.
machine is the name of the database server on which your TMS database resides; for example, opasolaris5.
port is the port you use to connect to that database. The default value for Oracle databases is 1521.
db is the name of the database to which you want to connect; for example, sun5x12.
Note:
The default port value that TMS uses to connect to the application server is 7881.Example 8-2 HTML Anchor Line for an Autologin HTML Browser Link
"http://server.domain:7881/tms/tmsLogin.uix?event=doAutoLogin&dbJDBCurl=machine:port:db1"
Substitute the line above for the anchor line in the sample code shown in Example 8-1.
The Document Repository enables TMS users to search and customize a set of documents and, if Oracle Clinical is installed, patient data as well.
If you plan to use the Document Repository in the HTML Browser, follow instructions in the Oracle Thesaurus Management System User's Guide chapter on the HTML Browser for the following tasks:
Creating the Document Index
Choosing a Proxy Server and Configuring its Settings
Setting Categories for Web Document Groups
Defining Document Server Refresh Rules
Defining Document Servers
Generating a List of Accessible Documents
Populating the Document Index
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, and SNOMED
Article ID: 258975.1
|
 Copyright © 2000, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
