IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Install IBM Tivoli Monitoring > Configure clients, browsers, and JREs
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Java Web Start clients
No post-installation configuration of the JRE is required if the Java Web Start is used to deploy the Tivoli Enterprise Portal client.
The Tivoli Enterprise Portal client is typically deployed via Java Web Start by entering the following address in the browser’s location field:
http://teps_host:15200/tep.jnlpUnder Windows, the last JRE installed on the machine usually controls which Java Web Start loader is associated with the Java Web Start deployment files, which have the extension .jnlp. If the Oracle JRE was the last JRE installed, the Oracle Java Web Start loader and associated JRE will be used for the Tivoli Enterprise Portal client. If both IBM and Oracle Java are installed on the same machine and the IBM JRE was installed last, it may be necessary to manually re-associate the .jnlp extension with the Oracle JRE.
The method that you use to re-associate a file extension to a program that can support that file type will vary depending on which version of Windows you have installed.
Under Linux, when you invoke Java Web Start using the Firefox browser using the URL above, you might be presented with a dialog window asking what Firefox should do with the associated .jnlp file (see Figure 1).
Figure 1. Launching Java Web Start client
If this happens, complete the following steps:
- Select Open with and choose the Java Web Start loader program named javaws. This file is normally located in the ../bin directory where you installed the JRE.
- To ensure that this program is always used in the future for this file type, select Do this automatically for files like this from now on.
For more information on using and configuring Java Web Start client and setting up its environment, see Use Web Start to download and run the desktop client.
Parent topic:
Configure clients, browsers, and JREs