The following information helps you diagnose and resolve problems.
- After installation, the Store and Forward agent fails to register
with the management server on AIX, Version 5.1 with maintenance level 5100-02.
- After installing the Store and Forward agent on an AIX, Version 5.1
operating system with maintenance level 5100-02, the Store and Forward
agent will be unable to register with the management server because the ibmproxy
service dies shortly after starting. To resolve this behavior, install an
AIX operating system with maintenance level 5100-03.
- Port 50000 is required for a management server with an embedded
DB2 installation. However, port 50000 is also used by the SuSE SLES 8.0 operating
system.
-
Note:
This item and the associated workaround apply only to
installations of IBM Tivoli Monitoring for Transaction Performance 5.2. The
fix pack does not provide a new management server installation.
A port conflict can occur if a management server with an embedded DB2
installation is performed on a computer that has a fresh installation of the
SuSE SLES 8.0 operating system. The SuSE SLES 8.0 operating system claims
port 50000 in /etc/services, but that port is also used by the DB2 instance.
As a result, the DB2 installation stops. If this occurs, the following error
is displayed in the /tmp/db2setup.his file:
ERROR:DBI1702E The specified service name or port number conflicts with
existing values in the TCP/IP services file.
To resolve this error, edit the /etc/services file by commenting
out the following lines before performing a management server installation
with an embedded DB2 installation:
mrt 50000/tcp # telnet interface of mrt programs
mrt 50000/udp # telnet interface of mrt programs
- The topology report cannot be viewed and navigated in the IBM
Home Page reader
- The topology is an applet, and applets are not supported by Home Page
Reader. However, all of the topology data is also available in a tabular format.
The ability to view the data in tables makes the topology accessible by sight-impaired
users, in accordance with guidelines set forth by IBM accessibility checklists.
Tables can be viewed in the IBM Home Page reader.
- Installation of IBM Tivoli Monitoring for Transaction Performance
5.2 fails on a management server running the Intel-based SLES 8.0 operating
system.
-
Note:
This item and the associated workarounds apply only
to the installation of IBM Tivoli Monitoring for Transaction Performance 5.2.
The fix pack does not include a new management server installation.
When you install the IBM Tivoli Monitoring for Transaction Performance
5.2 management system, the installation utilities look for a file named <WAS_BASEDIR>/properties/version/was50_fp1_linux390.ptf.
On Intel-based installations, this file does not exist.
Use either of the
following two workarounds to install a management server on the Intel-based
SLES 8.0 operating system:
- Depot installation (see the IBM Tivoli Monitoring for Transaction Performance 5.2 Installation Guide for
more information). Before starting the installation process, edit the MsPrereq.xml
file and remove 390 from the line containing the file
name <WAS_BASEDIR>/properties/version/was50_fp1_linux390.ptf.
Continue with the installation.
- Zero-size file named <WAS_BASEDIR>/properties/version/was50_fp1_linux390.ptf. When you create a size
0 file having this name, the installation process sees that the file exists
and proceeds correctly. This workaround is useful when you must install from
a CD.
- The management server GUI sometimes fails to load after you
install the Windows Internet Explorer KB832864 security patch.
- If you have installed the KB832864 security patch for Internet Explorer
on a Windows operating system and can no longer launch the management server
GUI, perform the following steps:
- Launch Internet Explorer.
- Click Tools -> Internet Options, and click the Advanced tab.
- Clear the Use HTTP 1.1 check box under HTTP 1.1 settings.
- Click OK, and close the browser.
- Open a new Internet Explorer browser, and log in to the management server.
Clearing the Use HTTP 1.1 check box sometimes
breaks other Web applications you are using. If this occurs, perform the following
steps to enable all browsers that have the patch to log in to the management
server, regardless of the Use HTTP 1.1 setting:
- Browse to the URL http://<MS_HOSTNAME>:9090/admin
to open the WebSphere Administrator Console for the management server.
- In the navigation tree, select Servers -> Application
Servers to open the Application Servers window.
- Select server1 to open the Web Container window.
- Click HTTP Transports to open the HTTP Transports
window.
- Click the underlined asterisk (*) in the 9445 row to open the 9445 window.
- Scroll down the page, and click Custom Properties to
open the Custom Properties window.
- Click New to open a New window.
- Type MaxKeepAliveConnections in the Name field.
- Type 0 in the Value field,
and click OK.
- Click Save in the Message box.
- Click Save in the Save to Master
Configuration box to save the new setting.
- Restart the management server.
- The Windows 2003 Internet Explorer browser does not load the
management server GUI if the site is not trusted.
- If you are unable to launch the management server GUI on a Windows 2003
operating system, perform the following steps: Click File -> Add this site to -> Trusted Sites Zone. The login window is displayed.
- Applications added to an existing XML file are not displayed
in the Component Management window.
- If you enable an ARM application that has an XML file, and add new applications
to that XML file, the applications are displayed in listening policy-related
windows, but not in the Component Management window.
To enable new applications
to be displayed in the Component Management window, create an additional XML
file for your new application instead of editing the existing XML file.
- Uninstalling the fix pack from the Control Panel fails to completely
remove the directory structure.
- To completely remove the directory structure, uninstall the fix pack
only from the Work with Agent Updates window. You must uninstall the fix pack
before uninstalling IBM Tivoli Monitoring for Transaction Performance 5.2.
- Registration with a management server is restricted to 500
management agents.
- This fix pack enforces a maximum limit of 500 management agents that
can register with a management server. If a management agent installation
is attempted after the 500 management agent limit is reached, the management
agent is unable to register with the management server. The management agent
installation log contains the following message: <![CDATA[500 agents
installed. Max licenses exceeded.]]>
- The J2EE monitoring component deployment code sometimes fails
to instrument the start script.
- When the J2EE monitoring component is deployed to a WebLogic application
server that is started by a script, the instrumentation code is automatically
inserted in the start script immediately before the Java command. The Java command invokes the Java virtual
machine (JVM).
In most WebLogic 7 start scripts, instrumentation code is
added with a call to the startWLS script in the WL_HOME/bin
directory. When the start script invokes the startWLS script,
the J2EE monitoring component inserts instrumentation code just before the
call to startWLS. If the application server start script
does not invoke startWLS, but invokes the JVM directly,
the J2EE monitoring component code fails to instrument the start script
To prevent this problem, insert one of the following comments into the application
start script, just before the call to start the application server JVM:
- (For a Windows CMD program) "@rem Insert
TMTP Instrumentation"
-- OR --
- (For a Unix shell script) "# Insert TMTP
Instrumentation"
- In certain circumstances, Generic Windows is unable to play
back a 3270 emulation recording.
- Generic Windows is sometimes unable to play back a 3270 emulation recording.
This occurs most frequently when the recording is in Japanese. Most users
are able to successfully play back emulation recordings. There is, however,
no formal support for terminal emulation playbacks.
- The database transaction log fills up when enabled applications
have large numbers of transactions.
- If your environment has many enabled applications (such as 20 applications)
with XML files containing large numbers of transactions (such as 8000 transactions),
the database transaction log might become full. If this occurs, an error message
displays stating that an application with that name already exists on that
management agent. The trace log displays an error that the transaction log
is full in the database. To resolve this error, increase the database transaction
log file size and restart. For instructions on how to increase the transaction
log file size for your database, consult the database documentation.