IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

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 have the option to manually create your own links to the Managing Server Visualization Engine using the Link Wizard which is available on all workspaces.

You can access the Managing Server Visualization Engine from the following workspaces.

This is a list of the Managing Server Visualization Engine links available from the workspaces:

For information about accessing workspaces, see Access 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.

You can also create your own links to the Managing Server Visualization Engine using the Link Wizard.

For more information see Create 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 are to 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 need to 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) :

At kernel startup time, the kernel needs to 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. T 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.


See


Parent topic:

Workspaces for ITCAM Agent for WebSphere Applications