Tivoli Enterprise Portal Desktop Called Through Java Web Start Does Not Work Properly After Adding Agents Support For Tivoli Enterprise Portal Server; Receive A Loading Java Tm0 Applet Failed; Tacmd Createuser Output Indicates That The Path To The Java Home Directory Was Not Found - IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual

KFW_TOPOLOGY_CLUSTER_LIST forces the navigation display to use that
apparent host name instead of the TCP/IP host name.
Some agents require a different mechanism to change the apparent host name. In
the case of the MQ Agent for example (AFF_MVS_MQM), update the mq.cfg file
and add:
SET AGENT NAME(hostname)
Long host names can create confusion such as when a host name is fully qualified.
The default portal server processing only uses the first part of the fully qualified
name, so two names like abc.xyz.large.com and abc.def.large.com would both
appear at the node labeled abc. That can be controlled by adding the following to
the portal server environment file (KFWENV/cq.ini):
KFW_TOPOLOGY_KEEP_DOT_IN_NODE_NAMES=Y
Remember the managed system names are limited to 32 characters - so the
hostname:product can be truncated and cause accidental duplications. That would
be another case where you would need to set the CTIRA_HOSTNAME.
Tivoli Enterprise Portal Desktop called through Java Web Start does
not work properly after adding agents support for Tivoli Enterprise
Portal Server
Launch the Manage Tivoli Enterprise Monitoring Services utility on the system
where Tivoli Enterprise Portal Server is installed and execute the TEPS reconfigure
action. Restart the Tivoli Enterprise Portal Desktop through the Java Web Start.
Receive a Loading Java TM0 Applet Failed... error
There is a known problem with Firefox 3.5 (and possibily higher) that results in a
"Loading Java TM0 Applet Failed.." error when using the Java browser client.
There is a problem with way Firefox's JSObject is used to communicate between
Java and JavaScript.
tacmd createUser output indicates that the path to the Java home
directory was not found
About this task
This problem occurs when issuing tacmd createUser on Windows 2003 SP1. The
following error message is displayed:
KUICCU097E: The path to the Java home directory was not found.
Call IBM Software Support.
To resolve this problem launch the CandleGetJavaHome.bat script located in
InstallITM subdirectory of ITM home directory. Ensure that valid Java Home
directory is returned. (This directory should exist and contain an installation of
Java 1.5). If the message CScript Error: Loading your settings failed. (Access
is denied. ) is returned instead, ensure that the Windows Script Host (WHS)
works properly in your environment.
To verify that Windows Script Host is working on your system, execute the
following steps:
The directory name returned by the CandleGetJavaHome script was not found.
Chapter 7. Portal client troubleshooting
131