IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Agent-based services > Agent Service Interface
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Start the Agent Service Interface
Start the Agent Service Interface from your browser to get a menu of choices for reporting agent information, getting situation status, displaying short-term history, and for making service requests in XML.
You must have an administrator user ID for the operating system where the monitoring agent is installed to access the Agent Service Interface and its functions.
Follow these steps to start the IBM Tivoli Monitoring Service Index utility and then log onto the Agent Service Interface for the agent that you want to get information about.
Procedure
- Start the IBM Tivoli Monitoring Service Index by entering http://<host name>:1920 or https//<host name>:3661, where host name is the fully qualified name or IP address of the computer where the agent is installed. A list of the started services is displayed.
- Click the IBM Tivoli <PC> Agent Service Interface (where pc is the two-character component code) link for the application to work with.
- As prompted, enter the administrator-level user name and password for the operating system.
Results
After you have been authenticated, the Agent Service Interface Navigator page is displayed with links to Agent Information, Situations, History, Queries, and Service Interface Request. The Navigator page is the navigator.htm file that is installed at this location by default:
- install_dir\localconfig\html
- install_dir/localconfig/HTML
Monitoring agents that use subnodes, such as Agentless Monitors, VMware VI Agent, and subnodes created with Agent Builder, have some reporting limitations in the Agent Service Interface:
- Queries link is unavailable
- Situations listing shows all the situations for an agent, including the subnodes; filtering by subnode is not available
- Private history shows all the collected historical data for the selected attribute on the agent, including any subnodes; filtering by subnode is not available.
Parent topic:
Agent Service Interface