TMS Lite Browser Administration

This section describes the following administrative topics:

Granting User Privileges for Using the TMS Lite Browser

Users require the rxclin_read privilege to browse dictionary data. See Security for information about creating TMS users and granting them roles appropriate to their work.

Creating a Launch Page, Button, or Link for the TMS Lite Browser

You can customize the shipped TMS Launch page to add a link to the TMS Lite Browser, create a new Launch page, or create a button or link to the TMS Lite Browser from an existing website such as your users' Home page. Oracle provides scripts that help prevent problems that may arise in the TMS Lite Browser.

In addition, you may want to customize the TMS Lite Browser URL:

  • If you have multiple databases, you can specify a database other than the default one set up during installation.

  • You can enable automatic login, so that the system automatically logs in any user as tmsproxy.

    Note:

    By default, automatic login is disabled.

See Customizing the TMS Lite Browser URL to Support Additional Databases or Automatic Login.

For more information, see:

Creating or Customizing a Launch Page to Use Provided Scripts

Oracle recommends using the scripts provided here to control when and how the TMS Lite Browser Login page opens, to prevent users from having problems in the TMS Lite Browser application resulting from:

To use these scripts in your launch page:

  1. Place the script from Sample Java Script for Launching in a New Window without Tool or Menu Bar in a file called Launch.js.
  2. Place the script from Sample JavaScript for Checking if Compatibility View Is On in a file called IeCompatCheck.js.
  3. Place the scripts at the same location as the Launch page or in a folder (called JS in the example code below) in the same location as Launch page. The shipped TMS Launch page, launch.htm, is located in opa_home/html.
  4. Create an HTML page that contains a button or link to the TMS Lite Browser that invokes the functions in the JavaScript files or add code to the shipped Launch page or an existing website to do the same.

    Put the code referencing the scripts near the top of the HTML page; for example:

     <title> Launch RDC Onsite </title>
      <script type="text/javascript" src="JS/IeCompatCheck.js"></script>
      <script type="text/javascript" src="JS/LaunchJS.js"></script>
     
     </head>
    <body>
    

    Add button code or link code as follows, and see Customizing the TMS Lite Browser URL to Support Additional Databases or Automatic Login.

    <script language="JavaScript">
    document.write('<FORM>');
    document.write('<input type="button" value="TMS Browser" onclick="return launch(event,\'../tmsadf/faces/Login\',\'TMSLite\')" class="loginButton"/>');
    document.write("</FORM>");
    </script>  
    
    <noscript>
    <a onclick="return launch(event,'../tmsadf/faces/Login',\'TMSLite\')" href="#">Launch TMS Browser</a>
    </noscript>

Sample Java Script for Launching in a New Window without Tool or Menu Bar

function launch(event,url,windowname){
            if(detectIECompatibility(event)){
                cancelEvent(event);
                return false;
            }
            if(!!!windowname){
                windowname="_blank";
            }
            window.open(url,windowname,'location=0,resizable=1,toolbar=0,titlebar=1,status=1,scrollbars=1,menubar=0','true');
} 

Sample JavaScript for Checking if Compatibility View Is On

The following script checks if Compatibility View is on and if so, displays a message asking the user to turn it off.

function IECompatDetect(){       
        this.isCompatOn = function(){
                    var ua = navigator.userAgent;
                    var on = false;
                    for(var index=0; index< this.ieUAProps.length; index++){
                        var ieProp = this.ieUAProps[index];
                        if(ua.search(ieProp.layoutEngine) == -1){
                            continue;
                        }
                        if(ua.search(ieProp.browser) == -1){
                            on = true;
                            break;
                        }                   
                    }
                    return (on);
                };       
        this.ieUAProps= [
                        {
                            browser: 'MSIE 10',
                            layoutEngine: 'Trident/6'
                        },
                        {
                            browser: 'MSIE 9',
                            layoutEngine: 'Trident/5'
                        },
                        {
                            browser: 'MSIE 8',
                            layoutEngine: 'Trident/4'
                        }
                    ]
 
    }
function cancelEvent(e){
    var event = e || window.event;
    if(event == null){
        return;
    }
    if(event.preventDefault){
        event.preventDefault();
    }else{
        event.returnValue=false;
        event.cancelBubble=true;
    }
}
 
function compatCheck(event,isCompatRequiredToBeOn){
    var compatOn=(new IECompatDetect()).isCompatOn();
    if(compatOn && !isCompatRequiredToBeOn){
        cancelEvent(event);
        alert("Please turn off IE's Compatibility View. Go to Tools->Compatibility View/Compatibility View Settings to do so.");   
    }
    if(!compatOn && isCompatRequiredToBeOn){
        cancelEvent(event);       
        alert("Please turn on IE's Compatibility View. Go to Tools->Compatibility View/Compatibility View Settings to do so.");   
    }
    return compatOn;
}
function detectIECompatibility(e){   
    return compatCheck(event,false);   
}
 
//Call on load
(function(){
    compatCheck(null,false);
})();

Customizing the TMS Lite Browser URL to Support Additional Databases or Automatic Login

The format of the TMS Lite Browser URL is:

https://server.domain/tmsadf/faces/Login?setUpDone=Y &parameter1=value1&parameter2=value2

This URL, without any parameters, goes to the default database set up during installation and requires the user to log in. You can use one or more parameters to change this behavior:

Table 3-1 Parameters Used to Customize the URL

Parameter Parameter Value Description

db

database_name

Links to a database that is not the default one; see Adding and Configuring WebLogic Server Data Sources. The database name must be the JNDI name defined in the data source.

event

doAutoLogin

Helps enable automatic login; seeEnabling and Disabling Automatic Login.

For example, when both parameters are used:

https://server.domain/tmsadf/faces/Login?setUpDone=Y & db=database& event=doAutoLogin

Enabling and Disabling Automatic Login

If automatic login is enabled, any user can click a link for the TMS Lite Browser and the application opens immediately, bypassing the Login page. The system passes the credentials for the tmsproxy user, using the password entered in the TMS Installer. Users who log in with automatic login cannot perform searches on patient data.

By default, automatic login is disabled and when users click the link the Login page opens and they must enter their own credentials.

For more information, see:

Enabling Automatic Login

To enable automatic login:

  1. Open the tmsconfig.properties, which is located at <OPA_HOME>\config.
  2. Search for the parameter tms_auto_login. If it is not present, add it.
  3. Set it to Y:

    tms_auto_login=Y

  4. Save.

    Note:

    You must also add the string event=doAutoLogin to the TMS Lite Browser URL; see Customizing the TMS Lite Browser URL to Support Additional Databases or Automatic Login..

Disabling Automatic Login

Automatic login is disabled by default.

The setting of the parameter tms_auto_login in the tmsconfig.properties file overrides the URL event setting. If it is set to any value other than Y, or if it is not present in the tmsconfig.properties file, even if the TMS Lite Browser URL includes event=doAutoLogin, the link goes to the Login page instead of automatically logging in the user as tmsproxy.

To disable automatic login:

  1. Open the tmsconfig.properties, which is located at <OPA_HOME>\config.
  2. Search for the parameter tms_auto_login.
  3. If it is set it to Y, change its setting to N.
  4. Save.

Enabling TMS Lite Browser Logs

Do the following to enable exception log files for the TMS Lite Browser. A file named OpaServer-tms_1.log will be created in Middlware_HOME\user_projects\domains\OPADomain\ servers\OpaServer1\logs.

  1. Open the logging config file logging.xml that is located at:

    Middlware_HOME\userprojects\domains\OPADomain\config\fmwconfig\ servers\<server_name>_OPA_1

  2. Add the following entry:
    <?xml version='1.0' encoding='UTF-8'?> 
    <logging_configuration> 
    <log_handlers> 
    .. 
    .. 
     <log_handler name='tmshandler'   
    class='oracle.core.ojdl.logging.ODLHandlerFactory'   
    filter='oracle.dfw.incident.IncidentDetectionLogFilter'> 
       <property name='path'   
    value='${domain.home}/servers/${weblogic.Name}/logs/${weblogic.Name}-tms_1.log 
      
    '/> 
       <property name='maxFileSize' value='10485760'/> 
       <property name='maxLogSize' value='104857600'/> 
       <property name='encoding' value='UTF-8'/> 
       <property name='useThreadName' value='true'/> 
       <property name='supplementalAttributes'   
    value='J2EE_MODULE.name,composite_name,component_name'/> 
      </log_handler> 
    .. 
    .. 
    </log_handlers> 
    <loggers> 
    .. 
    .. 
      <logger name='oracle.pharma.tms.logging' level='ALL'   
    useParentHandlers='false'>   
       <handler name='tmshandler'/> 
      </logger> 
    .. 
    .. 
    </loggers> 
    </logging_configuration> 
      
  3. Add the following to the URL to get all debug information:
    ?setUpDone=Y&debug=all

Using the About Window

The About window shows information about the TMS and other Oracle Health Sciences releases that have been applied to this database. Choose either TMS or OPA from the Installed Product list to browse:

  • Which releases have been applied to the middle and database tiers.

  • The dates in which these releases were installed.