![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page ]
This section describes the following additions and modifications to components and real-time reports:
The AutoUpdate feature enables you to perform the following tasks:
When an installed update affects both the agent and one or more monitoring components, the agent is updated first, followed by the components. Uninstallations proceed in reverse order, with update code uninstalled from the components first, and then from the agent. The specified update starts at the next polling interval. The polling interval is the regularly scheduled time (by default, every 15 minutes) when new information is sent to the management agents.
A table in the Work with Agent Updates window informs you whether an update is available for a particular agent and provides update status. The table also shows the monitoring components that are running on each agent and displays the update status of each component.
To begin using AutoUpdate, select System Administration -> Work with Agent Updates in the main menu. The online helps provide detailed step-by-step information about using the feature.
The fix pack includes two events that inform you whether AutoUpdate uninstallations have succeeded or failed.
The following event indicates a successful uninstallation:
<message
id="0x002C"
tms_id="ITPMS0094I"
tms_prefix="no"
event_family="ManagementServer"
symbol="ROLLBACK_COMPLETE"
alt_symbol="Rollback-Complete">
<text>An endpoint rollback process has completed successfully. {0}</text>
The following event indicates a failed uninstallation:
<message
id="0x002D"
tms_id="ITPMS0095I"
tms_prefix="no"
event_family="ManagementServer"
symbol="ROLLBACK_FAILED"
alt_symbol="Rollback-Failed">
<text>An endpoint rollback process has failed due to an error. {0}</text>
IBM Tivoli Monitoring for Transaction Performance 5.2 enables you to set thresholds on an overall Generic Windows transaction, but not on subtransactions. The fix pack introduces the ability to set thresholds on Generic Windows subtransactions.
During the process of creating a new Generic Windows policy, you can create thresholds only on the overall transaction. To create a subtransaction threshold, you first run the policy and then consult the topology view, where subtransactions are displayed as nodes. From the topology, you can right-click a subtransaction node and specify Thresholds View to create a threshold.
The online helps provide more information about the use of Generic Windows subtransaction thresholds.
The fix pack offers the following updated functionality for reports. See the online helps for more thorough discussions.
When you right-click on a base node in the topology report, the menu includes the Subtransaction Performance View item, which you can select to inspect subtransaction performance.
The fix pack provides the updateprops command that you use in preparation for uninstalling the J2EE monitoring component. You might want to uninstall a J2EE component when changes exist that affect access to the J2EE-instrumented application server. A J2EE component installation depends on a user name, password, or port for the instrumented application server, and some or all of that information might have changed since the installation was completed.
If your authentication information has changed on the J2EE application server since the J2EE component was installed, you run the updateprops command before removing the J2EE component. The command takes two parameters, serverName and serverHome, as illustrated in the following example:
updateprops.sh -serverName server1 -serverHome /opt/WebSphere/AppServer
The command prompts you for a user name, password, and port number. If you do not want to change any of these fields, press the Enter key. The appropriate properties file is updated with the new value. Passwords are encrypted and written to the properties file, and you can now remove the J2EE component.
[ Top of Page | Previous Page | Next Page ]