$('a[name]').remove(); $('#ic-homepage__footer').before('
'); $("#tabs").tabs({ selected: 1 }); $("#ic-homepage__ic-tips").append( quickTipHTML() ); unhideOneProductTip(); $("#ic-homepage__product-tips").wrapInner('
'); $("#ic-homepage__feed-tips").wrapInner('
'); });
IBM Tivoli Monitoring > Version 6.3 > User's Guides > Agent Builder User's Guide > Test and debugging your agent IBM Tivoli Monitoring, Version 6.3
Agent post-generation and installation results
Results to expect after creation and installation of an agent with Agent Builder.
Changes that you see after you generate and install the new agent that is created with the Tivoli Monitoring Agent Builder:
New files on your system
After you generate and install the agent that you created with the Tivoli Monitoring Agent Builder, you can see the following new files on your agent system:
xx denotes the two character product code.
- Windows systems:
- TMAITM6\kxxagent.exe
- Agent binary
- TMAITM6\KxxENV
- Environment variable settings
- TMAITM6\Kxx.ref
- Agent provider configuration
- TMAITM6\SQLLIB\kxx.his
- SQL description of agent attribute information
- TMAITM6\SQLLIB\kxx.atr
- Agent attribute information
- TMAITM6\xx_dd_062000000.xml
- Product description
- TMAITM6\xx_dd.properties
- Product name
- TMAITM6\kxxcma.ini
- Agent service definition file
- TMAITM6\your files
- Supplemental Files included from the Java API or Socket data sources with a file type of executable or library. Scripts included from the Script or Command return code data sources.
- UNIX/Linux systems:
- registry/xxarchitecture.ver
- Internal versions and prerequisites file
- architecture/xx/bin/xx_dd_061000000.xml
- Product description
- architecture/xx/bin/kxxagent
- Agent binary
- architecture/xx/bin/xx_dd.properties
- Product name
- architecture/xx/work/kxx.ref
- Agent provider configuration
- architecture/xx/tables/ATTRLIB/kxx.atr
- Agent attribute information
- architecture/xx/hist/kxx.his
- SQL description of agent attribute information
- architecture/xx/bin/your files
- Supplemental Files included from the Java API or Socket data sources with a file type of executable. Scripts included from the Script or Command return code data sources.
- architecture/xx/lib/your files
- Supplemental Files included from the Java API or Socket data sources with a file type of Library.
- config/.xx.rc
- Internal setup file
- config/xx.config
- Environment settings
- config/xx_dd_062000000.xml
- Product description
- config/xx_dd.properties
- Product name
- config/.ConfigData/kxxenv
- Environment variable settings
- config/xx.ini
- Environment settings
Run the following command to find out the architecture of the system:
cinfo -pxxwhere xx is the two-character product code. For example, for a Solaris 8 64-bit system that is running an agent with product code 19, here is the output:
# /opt/IBM/ITM/bin/cinfo -p 19 *********** Fri Aug 17 11:23:58 EDT 2007 ****************** User : root Group: other Host name : guadalajara Installer Lvl:06.20.00.00 CandleHome: /opt/IBM/ITM *********************************************************** Platform codes: sol286 : Current machine sol286 : Product (19) tmaitm6/sol286 : CT Framework (ax)The line in bold is the relevant one. The string before the colon, sol286 indicates the architecture in use for this agent. This string is different for different combinations of operating system and computer hardware type. The agent must already be installed in order for this feature to work.
The following are the files for the Java based data sources. These files are only created if the agent contains JMX, JDBC, HTTP, or SOAP data sources:
- cpci.jar
- jlog.jar
- common/jatlib-1.0.jar
The following are the files for JMX runtime support. These files are only created if the agent contains JMX data sources:
- common/jmx-1.0.jar
- common/connectors/jboss/connJboss-1.0.jar
- common/connectors/jsr160/connJSR160-1.0.jar
- common/connectors/was/connWas-1.0.jar
- common/connectors/weblogic/connWeblogic-1.0.jar
The following are the files for JDBC runtime support. These files are only created if the agent contains JDBC data sources:
- common/jdbc-1.0.jar
The following are the files for HTTP or SOAP runtime support. These files are only created if the agent contains HTTP or SOAP data sources:
- http-1.0.jar
The following are the files for the Java API runtime support. These files are only created if the agent contains a Java API data source:
- cpci.jar
- custom/your JAR file The name of this JAR file is specified in the Global settings of a Java API data source.
- custom/your JAR file Supplemental Files with a file type of Java resource
The same files exist on both Windows and on UNIX/Linux systems for Java based data sources, but they are in different directories:
- Windows path: TMAITM6\kxx\jars
- UNIX/Linux path: architecture/xx/jars
The following are the files for log file Monitoring runtime support. These files are only created if the agent contains log file data sources:
- On Windows systems: TMAITM6\kxxudp.dll
- On Solaris/Linux systems: architecture/xx/lib/libkxxudp.so
- On HP-UX systems: architecture/xx/lib/libkxxudp.sl
- On AIX systems: architecture/xx/lib/libkxxudp.a
The following are the files for SSH Script Monitoring runtime support. These files are only created if the agent contains a script data source that is enabled for SSH collection:
- On Windows systems: TMAITM6\kxxssh.dll
- On Solaris/Linux systems: architecture/xx/lib/libkxxssh.so
- On HP-UX systems: architecture/xx/lib/libkxxssh.sl
- On AIX systems: architecture/xx/lib/libkxxssh.a
Changes in the Manage Tivoli Enterprise Monitoring Services window
After you generate and install the agent that you created with the Tivoli Monitoring Agent Builder, you can see an entry for the agent in the Manage Tivoli Enterprise Monitoring Services window. The entry is named Monitoring Agent for agent_name.
On Windows systems, this entry contains a Task/Subsystem column that identifies whether your agent supports multiple instances:
- A single instance agent displays a new application in the Manage Tivoli Enterprise Monitoring Services window named Monitoring Agent for agent_name. A service is created for the agent (Figure 1). The Task/Subsystem column contains the value Primary.
- A multiple instance agent displays a new application template in the Manage Tivoli Enterprise Monitoring Services window named Monitoring Agent for agent_name. A service is not created for the agent until you create an instance of the agent from this template. The Task/Subsystem column contains the value Template to indicate that this entry is a template that is used to create instances of the agent.
On UNIX systems, the entry for the agent is the same whether your agent supports multiple instances or not.
The following screens are taken from a Windows system. UNIX systems have similar screens.
Figure 1. Manage Tivoli Enterprise Monitoring Services window
Changes in the Tivoli Enterprise Portal
After you generate, install, and start the agent, and click the green Refresh icon. The new agent that you created with the Tivoli Monitoring Agent Builder can be viewed in the Tivoli Enterprise Portal. You can see the following changes in the portal:
- A new subnode for the agent in the Tivoli Enterprise Portal physical view
- Nodes for every navigator group and top-level data source that you defined using the Agent Builder (Figure 2).
For each navigator item, you must define a default query.
Figure 2. Nodes for attribute groups you defined
- If your agent contains subnodes, an expandable node is present for each subnode that is defined in your agent. The following nodes are shown under the expandable node:
- xxx performance object status, where xxx is the three-letter subnode type
- Nodes for every Navigator group and data source that you defined in the subnode
- xxx event log node if you have event logs
- xxx JMX monitors node if you have JMX and you included JMX monitors
- The following automatic nodes:
- An availability node if your agent contains an availability data source (Figure 3)
This node behaves differently depending on the contents of the agent. If the agent monitors only availability, the availability node represents the availability data source. If the agent monitors availability and performance, the availability node becomes the Navigator item that represents the availability, and performance object status data sources.
Figure 3. Availability node
- Performance Object Status (if you specified that you want the agent to do performance monitoring and not availability) (Figure 4)
Figure 4. Performance Object Status node
- Event log (if you specified that filter for your agent) (Figure 5)
Figure 5. Event log node
See Attributes reference for descriptions of the attribute groups and attributes for Agent Builder.
Parent topic:
Test and debugging your agent