$('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 > Create a basic agent > Create and defining the agent IBM Tivoli Monitoring, Version 6.3

Naming your agent

Use the Project page to name your Agent.

Start the new agent wizard. See starting the wizard.


When you are ready to run the agent, the agent name that you designate is displayed in the (Tivoli Enterprise Portal).

Use the following steps to name your agent:


Procedure

  1. After you start the new agent wizard, click Next in the Welcome window. Clicking Next displays the New IBM Tivoli Monitoring Agent Project page (Figure 1). On that page you can type a project name for the folder that is created in the Eclipse workspace to hold the necessary files for generating the agent.

    1. Use the Location field to select a directory that is not the default directory for storing the project contents. To put or use the project contents in another directory, clear the check box next to the Use default field. Then, click Browse to browse to your preferred directory.

    2. The Working Set function is an optional Eclipse feature that you can use to add resources to working sets. You can change how the Eclipse Navigator View displays resources by adding them to various working sets. See the Eclipse help.

    Figure 1. Project page

  2. After you type the project name, click Next to see the General Information page.

    Figure 2. General Information page

    The project name is displayed in the Display name field. This name is displayed in the Tivoli Enterprise Portal.

  3. Type the copyright statement that you want to use for your new agents in the Copyright field (Figure 3). This statement must meet your legal requirements for copyrights. This copyright statement is inserted into all of the files that are generated for the agent and can be edited when needed. After you supply the statement for the first time, the Agent Builder remembers your copyright statement. Agent Builder displays your copyright statement in the copyright area each time that you start the wizard to create an agent. For example, you might use the following format and contents: Copyright ABC Corp 2009. All rights reserved. If you are unsure what information you want to supply about the copyright, contact the enterprise legal department.

  4. Select the operating systems for which you want your agent to be built.

    If the 32-bit version of an operating system is selected, the agent can be deployed on a 64-bit operating system as a 32-bit process. However, in that case the 64-bit version of the operating system must not then be selected.

  5. Click Next to display the Agent Information page.

    Figure 3. Agent Information page

  6. To change the name of the agent, type a new name in the Service name field. The service name is the name of the service that is created on Windows. The service name is also the name of the service that is displayed in the Manage Tivoli Monitoring Services window. The name of the service is Monitoring Agent for Name, where Name is any name you choose consisting of letters, numbers, spaces, and underscores.

  7. In the Product code field, type the registered product code for your new agent. A range of product codes is reserved for use with the Agent Builder. The allowed values are K00-K99,K{0-2}{A-Z}, and K{4-9}{A-Z}. These values are for internal use only and are not intended for agents that are to be shared or sold. If you are creating an agent to be shared with others, send a note to toolkit@us.ibm.com to reserve a product code. The request for a product code must include a description of the agent to be built. A product code is then assigned, registered, and returned to you. When you receive the three-letter product code, you are told how to enable the Agent Builder to use the assigned product code.

  8. In the Company identifier field, type an alphabetic string that uniquely identifies the organization that develops the agent (IBM is reserved). A good candidate for this field can come from the URL of your company. For example, from a mycompany.com URL, use the text mycompany.

  9. In the Agent identifier field, type an alphabetic string that uniquely identifies the agent For example, DISKMON might be the string for an agent that monitors disk usage. You can use the product code for the agent identifier.

    The combined length of the Agent identifier field and the Company identifier field cannot exceed 11 characters.

    By default, Agent Builder sets the Agent identifier to be the same as the Product code.

  10. In the Version field, type a three-digit number that identifies the agent version in the format VRR, where:

    • V = Version

    • R = Release

    • R = Release

    The VRR entered is converted to a Tivoli Monitoring VVRRMMFF format in the following way: 0V.RR.00.00.

    In the agent editor, a patch level field is available. The patch level field can be used when you release a fix for an agent, without updating the version.

  11. If you want your agent to support multiple instances, select the Support multiple instances of this agent check box.

    Some applications can be configured to run multiple instances of the application on a system at the same time. When building agents for these types of applications, it is often desirable to separate the management of each of the application instances. The separation means that the Tivoli Monitoring user can more determine when there are problems with one of the application instances. A similar condition happens if you are building an agent that uses a data provider from the Data from a server monitoring category. Because these data monitors can be used to monitor remote systems, it is possible to install the agent on one system and monitor several other systems. Each of these remote systems can be represented separately in Tivoli Monitoring and each can have different configuration values for communication. To have different configuration values, select Support multiple instances of this agent. This selection causes the Agent Builder to create a "template" agent. After the agent is installed, you can create and configure an instance of the agent for each instance of the monitored application.

  12. In the Minimum ITM Version field, select the minimum version of IBM Tivoli Monitoring that the agent requires. See Table 1 which provides the reasons to use each level.


    Minimum version of IBM Tivoli Monitoring required by the agent

    IBM Tivoli Monitoring level Reason to use this level
    V6.2.1

    • The generated agent requires a minimum Tivoli Monitoring version of 6.2.1 to run successfully, and you cannot install on a version earlier than 6.2.1 (Figure 3). If you select 6.2.1, you can Allow any configuration property to be overridden in any subnode. See (Advanced subnode configuration.)

    • This version supports 64-bit numeric attributes.

    • This version includes support for different default configuration values for Windows and for UNIX and Linux. See Default Value.

    The default minimum Tivoli Monitoring version is 6.2.1.

    V6.2 By selecting 6.2, the resulting agent runs on Tivoli Monitoring, version 6.2 or later. However, other features that are listed earlier including 64-bit numeric attribute support are not available to the agent. Also, Subnode Configuration Overrides must be defined when the agent is built, see (Configure a subnode).


What to do next

Click Next to define an initial data source for your agent. See Define initial data source


Parent topic:

Create and defining the agent

+

Search Tips   |   Advanced Search