Workspace link to managing server visualization engine

With the appropriate configuration and permissions, you can access the managing server visualization engine from specific workspaces in the WebSphere® Tivoli® Enterprise Portal. Instead of opening another browser and clicking the relevant link, you can access the managing server visualization engine from Tivoli Enterprise Portal using a link called Diagnostic Server Activity Display. Some of the workspaces have additional links you can use to access the managing server visualization engine. All these links begin with the word Diagnostic. When you log in to the Welcome to the Application Monitor page, the information displayed is specific to the content in the Tivoli Enterprise Portal workspace you selected. You also can manually create your own links to the managing server visualization engine using the Link Wizard, which is available on all workspaces.

Important: To use this functionality, you need ITCAM for Application Diagnostics Managing Server.

You can access the managing server visualization engine from the following workspaces.

  • WebSphere Agent
  • Request Analysis
  • Garbage Collection Analysis
  • Datasources
  • JMS Summary
  • Web Applications
  • EJB Containers
  • DB Connection Pools
  • J2C Connection Pools
  • Thread Pools
Here is a list of the managing server visualization engine links available from the workspaces:
  • Diagnostic Server Activity display. Use this link to diagnose application problems, for example, slow transactions or high response times. This link is available from all workspaces except Request Analysis and Garbage Collection Analysis.
  • Diagnostic In-Flight Request Search. Use this link to identify any hanging transactions. This feature is only available from the WebSphere Agent and Request Analysis workspaces.
  • Diagnostic Recent Completed Requests. The Recent Requests tab displays data regarding recently completed server requests. This feature is only available from the Request Analysis workspace.
  • Diagnostic SMF Data. This feature is only available you are using a z/OS® data collector and in the Request Analysis workspace. The SMF Overview displays summary information for all the resources on the selected application server.
  • Diagnostic JVM Thread Display Use this link to diagnose application problems, for example, slow transactions by examining threads running in JVM. This link is available from the Thread Pools workspace.
  • Diagnostic Memory Leak Use this link to diagnose memory leak problems. This link is available from the Garbage Collection Analysis workspace.

For information about accessing workspaces, see Accessing the managing server visualization engine from Tivoli Enterprise Portal workspaces.

Prerequisites for access

The following conditions must be met to gain access to the managing server visualization engine through the Tivoli Enterprise Portal.
  • ITCAM for Application Diagnostics managing server and ITCAM Data Collector for WebSphere must be installed in your environment.
  • Tivoli Enterprise Portal users must be members of the Diagnostic Users Group within the Tivoli Enterprise Portal. For more information, see Granting users access to managing server visualization engine from Tivoli Enterprise Portal.
  • During the installation of the managing server, kernel properties in the managing server must be set up accordingly with the correct host name and port number. This action is completed by the user installing the managing server.
You can also create your own links to the managing server visualization engine using the Link Wizard.

For more information, see Creating links to the managing server visualization engine using the Link Wizard

Kernel Settings to access the managing server visualization engine through the Tivoli Enterprise Portal

If users access the managing server visualization engine through the Tivoli Enterprise Portal, the kernel properties in the managing server must be set up accordingly with the correct host name and port number.

The following properties must be added to kl1.properties and kl2.properties (By default, the managing server installer replaces @{HOST_VE} and @{PORT_VE_HTTP} at managing server installation time) :
  • ve.host=@{HOST_VE}
  • ve.port=@{PORT_VE_HTTP}
At kernel startup time, the kernel must read these two properties and set them as part of properties in PROBE_CONFIG.PROPS. If a user changes the VE host name or port number, then the kernel needs to be restarted. Use the following steps to start and stop the kernel In $MS_HOME/bin:
  1. To start kernel, issue:./amctl.sh wd<kernel count> start
  2. To stop kernel, issue: ./amctl.sh wd<kernel count> stop
where <kernel count> is 1 by default.