IBM E027SLL-H - Tivoli Monitoring - PC, Troubleshooting Manual

Page: 139 / 310

Enterprise Portal Server. Set the IBM JVM (JavaVirtual Machine) as a trusted
program to allow the portal client to connect to the Tivoli Enterprise Monitoring
Server. You might need to include the IBM Java program in the programs section
of your firewall software and include the IP addresses of other IBM Tivoli
Monitoring components in the access control for the firewall.
Portal server is initializing and is not ready for communications
If you attempt to log in to the Tivoli Enterprise Portal Server, soon after it has
started, it is possible the portal server is not ready for requests until initialization is
complete.
The portal server is not ready for requests from the portal client until its process,
kfwservices.exe
is fully started. Keep the Logon window open and click OK after
waiting a moment or two.
Portal server is unavailable during a portal client work session
When a message in the Tivoli Enterprise Portal indicates that the Tivoli Enterprise
Portal Server is unavailable, suspend further interactions until a message indicates
the server is available unless you decide to end the current work session.
When the Tivoli Enterprise Portal Server is available again, your client session is
automatically reconnected and you can resume normal interactions. If you are
running the portal client in browser mode and the portal server is available but the
client has not reconnected after three to five minutes, exit the browser, restart the
browser, and restart a client session.
Portal server does not start after installation
If the Tivoli Enterprise Portal Server does not start after installation or upgrade,
review the log files for the cause.
Check the following log files for messages that indicate why the Tivoli Enterprise
Portal Server did not start:
Table 14. The Tivoli Enterprise Portal Server does not start after installation
Log file For messages that indicate . . .
kfwras1.log
A failure during upgrade.
The Tivoli Enterprise Monitoring Server hub did not connect.
install_dir\cnps\sqllib\migrate.log
Any error.
Portal server is not connecting with the hub monitoring server
If the Tivoli Enterprise Portal Server is not connecting to the hub Tivoli Enterprise
Monitoring Server or it was connected and has lost the connection, review the
possible causes and solutions for the symptoms you experience.
Tivoli Enterprise Portal Server lost contact with the Tivoli Enterprise Monitoring
Server and is attempting to reconnect
This message displays when the portal server has lost its connection to the
hub monitoring server, usually because the monitoring server stopped or is
recycling. See also KFW_CMW_RECYCLE_DELAY.
Chapter 6. Connectivity troubleshooting
121