$('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:

where 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:

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:

The following are the files for JMX runtime support. These files are only created if the agent contains JMX data sources:

The following are the files for JDBC runtime support. These files are only created if the agent contains JDBC data sources:

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:

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:

The same files exist on both Windows and on UNIX/Linux systems for Java based data sources, but they are in different directories:

The following are the files for log file Monitoring runtime support. These files are only created if the agent contains log file data sources:

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:


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:

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:

See Attributes reference for descriptions of the attribute groups and attributes for Agent Builder.


Parent topic:

Test and debugging your agent

+

Search Tips   |   Advanced Search