IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Install IBM Tivoli Monitoring > Specify the browser used for online help

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Web Start: Specifying the browser location

Java Web Start deployed applications are described in jnlp deployment files. For IBM Tivoli Monitoring, there is one deployment file that describes the core Tivoli Enterprise Portal framework component and associated JAR files, and one deployment file for each and every Tivoli Enterprise Portal-based monitoring solution that is installed.

The core Tivoli Enterprise Portal Server deployment file is named tep.jnlp. The application deployment file is typically called kxx_resources.jnlp or kxx.jnlp, where xx is the application identifier (a product code, such as nt, ux, or lz).

The deployment file instances are generated whenever the Tivoli Enterprise Portal Server is installed or reconfigured (for example, when adding a new monitoring solution to the environment). The contents of these files are based upon two template deployment files (.jnlpt). The core Tivoli Enterprise Portal template deployment file is called tep.jnlpt. The application template deployment file is named component.jnlpt.

  1. To add or modify JVM arguments (such as maximum heap size) or other Tivoli Enterprise Portal-based properties (such as RAS1 trace options), you must edit either the tep.jnlp deployment file or the tep.jnlpt deployment template file. The deployment file is nothing more than XML syntax that describes the Web Start application being deployed. The <resources> element is used to define the JVM arguments, the Tivoli Enterprise Portal properties, JAR files, and references to component deployment files.

    • Modify the tep.jnlp file if the change will be temporary (for example, setting a trace option for gathering further diagnostics).

    • Modify the tep.jnlpt template file if the change will be long-term (for example, increasing the maximum heap size to accommodate a larger monitored environment or increased event load).

      If you modify the deployment template file, make sure you then reconfigure the Tivoli Enterprise Portal Server in order to regenerate the instance-level .jnlp deployment files with your changes.

      Changes to tep.jnlpt are not preserved when you migrate to a new release. A backup of the tep.jnlpt file will be made during migration; you must manually compare this backup to the new version installed during migration to determine what changes need to be manually incorporated into the new tep.jnlpt.

  2. To specify the location of the browser to use to display the online help, add the following property to the <resources> section of the appropriate file: 

      <property name="kjr.browser.default" value="fully-qualified path of browser executable>"

    Windows example: 

      <resources os="Windows">
    <jar href="classes/browser-winnt.jar"/>
    <jar href="classes/browser-core-winnt.jar"/>
    <property name="kjr.browser.default" value="C:\Program Files\Internet Explorer\iexplore.exe"/>
</resources>

    Linux example: 

      <resources os="Linux">
    <jar href="classes/browser-li.jar"/>
    <jar href="classes/browser-core-li.jar"/>
    <property name="kjr.browser.default" value="/usr/bin/firefox"/>
</resources>

    For the online help to display on a Linux or Unix computer, the kjr.browser.default value must specify Firefox as the default browser.

    kjr.browser.default is not the only property you can specify using the <property> keyword. You can include any client parameters that are specific to your operating system.


Parent topic:

Specify the browser used for online help

+

Search Tips   |   Advanced Search