Naming your agent

The agent name that you designate is displayed in the Tivoli Enterprise Portal when you are ready to run the agent.

Use the following steps to name your agent:

1. After starting the wizard by any of the methods, click Next in the Welcome window (Figure 14) to display the New IBM Tivoli Monitoring Agent Project page (Figure 15), where 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.
   Notes:

   1. The Location field affords an opportunity to navigate to a directory that is not the default directory for storing the project contents. If you want to put or use the project contents in another directory, clear the check box next to the Use default field and click Browse to navigate 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 for more information.
   Figure 15. Project page

   
2. After you type the project name, click Next to see the General Information page (Figure 16).
   Figure 16. 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 17). 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 once, the Agent Builder remembers your copyright statement and displays it in the copyright area each time that you start the wizard to create a new 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 your enterprise legal department.
4. Select the operating systems for which you want your agent to be built.
   Note:

   An agent can be deployed on a 64-bit operating system as a 32-bit process if the 32-bit version of that operating system is selected and the 64-bit version of that operating system is not selected.
5. Click Next to display the Agent Information page (Figure 17).
   Figure 17. Agent Information page

   
6. If you want 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 created on Windows and 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, you must 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 3-letter product code, you will be 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 developing the agent ("IBM®" is reserved.). A good candidate for this field can come from your company's URL. 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 being developed (for example, DISKMON might be the string for an agent that monitors disk usage). You can use the product code for the agent identifier.
   Note:

   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 3-digit number that identifies the agent version in the format VRR, where:
    • V = Version
    • R = Release
    • R = Release
    The VRR entered is converted to an IBM Tivoli Monitoring VVRRMMFF format in the following way: 0V.RR.00.00.

    In the agent editor, a patch level field is available when you need to release a fix for an agent, but you do not want to update 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 so that the IBM Tivoli Monitoring user knows 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 at the same time. Each of these remote systems can be represented separately in IBM Tivoli Monitoring and each can have different configuration values for communication. To do this, select the Support multiple instances of this agent check box, which 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. Table 4 provides the reasons to use each level.

    Table 4. 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 IBM Tivoli Monitoring version of 6.2.1 to run successfully, and you cannot install on a version earlier than 6.2.1 Figure 17. If you select 6.2.1, you can "Allow any configuration property to be overridden in any subnode", (See Allow any configuration property to be overridden in any subnode in Advanced subnode configuration.) This version has 64-bit numeric attribute support. This version includes support for different default configuration values for Windows and for UNIX and Linux. See Default Value for more information. The default minimum IBM Tivoli Monitoring version is 6.2.1.
    V6.2	By selecting 6.2, the resulting agent will run on IBM Tivoli Monitoring, version 6.2 or later, but other features listed above including 64-bit numeric attribute support will not be available to the agent, and Subnode Configuration Overrides must be defined when the agent is built (See Configuring a subnode).