'); $("#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 IBM Tivoli Monitoring, Version 6.3
Import application support files
Custom situations, workspaces, Take Action commands, and queries can also be included in the installation package. To have a single installation image for situations, workspaces, and the agent, the situation, and workspace files must be in the same project as the agent. The Agent Builder provides a wizard to create the appropriate files in the agent project.
Definitions that are associated with an agent can also be included in the installation package. The content of these definitions is different for an agent that is used in an enterprise monitoring environment and in a system monitor environment. An enterprise monitoring agent image can include custom situations, workspaces, Take Action commands and queries. A system monitor agent image can include private situations, trap definitions, and agent configuration information.
To have a single installation package that includes the appropriate definitions and the agent itself, the files must be in the same project as the agent. The Agent Builder provides a wizard to create the appropriate files for an enterprise monitoring installation. The files for a system monitor agent environment are created using the process that is described in the Agent Autonomy chapter in the IBM Tivoli Monitoring Administrator's Guide. The resulting files are copied into the root of the Eclipse project for the agent.
Export and importing files for Tivoli Enterprise Monitoring Agents
After you create situations, workspaces, queries, and Take Action commands in the Tivoli Enterprise Portal, you can export and import them into another Tivoli Monitoring Version 6.2 environment. For more information about creating situations and workspaces, see (Create workspaces, Take Action commands, and situations). Use the following steps to extract the situations, workspaces, Take Action commands, and queries:
Procedure
- From the Project Explorer tab, right-click the agent project folder.
- Select IBM Tivoli > Import Application Support Files.
Figure 1. Importing application support files
- Enter the host name of the Tivoli Enterprise Portal Server.
- Enter the user name and password for the Tivoli Monitoring environment you are connecting to.
- If you defined situations for your agent, a dialog box is presented that lists the situations that are defined for the agent.
Figure 2. Importing situations
- Select the situations that you want to export from the list and click >> to add them to the selected situations table and click OK.
The import might take a few moments. When the task completes, you see the SQL files in the appropriate folders in the agent project.
Figure 3. Selecting situations
- If you defined Take Action commands for your agent, a dialog presents the Take Action commands defined. Choose the Take Action commands that you want to export from the list and click >> to add them to the Selected Take Actions table and click OK.
The import might take a few moments. When the task completes, you see the SQL files in the appropriate folders in the agent project.
Figure 4. Take Actions window
- If you defined custom queries for your agent, a dialog presents the Take Action commands defined. Select the queries that you want to export from the list and click >> to add them to the Selected Queries table and click OK.
Figure 5. Importing queries
The import might take a few moments. When the task completes, you see the SQL files in the appropriate folders in the agent project.
Workspaces are imported automatically.
Export and importing files for Tivoli System Monitor Agents
The system monitor agent definitions are contained in three types of files:
- Private situations are defined in a file named xx_situations.xml, where xx is the two-character product code
- Trap configuration information is defined in a file named xx_trapcnfg.xml, where xx is the two-character product code
- For agents that require configuration, the configuration is defined in one file for each instance of the agent. When the agent is a single instance agent, the file is named xx.cfg. When the agent is a multi-instance agent, there is a file is present for each instance. The file names are xx_instance name.cfg, where xx is the two-character product code and instance name is the name of the agent instance.
Procedure
Create the files using the process that is described in the Agent Autonomy chapter in the IBM Tivoli Monitoring Administrator's Guide. Copy the files into the root of the project directory manually, or use the Eclipse import function to select the files to be imported: File > Import > General > File System. These files are included in the agent image and installed by the installer.
When the agent is installed the installation:
- Copies the included files into the appropriate locations.
- Any private situations that are defined in the pc_situations.xml file that is run on the agent.
- The trap definitions that are defined in the pc_trapcnfg.xml are used to forward traps that are based on the situations.
- The agent is automatically configured and started if:
- The agent is a single instance agent with no configuration defined as part of the agent.
- The agent is a single instance agent with configuration defined as part of the agent and the image includes a pc.cfgfile.
- The agent is a multi-instance agent (all multi-instance agents require configuration): the installer starts one instance of the agent for each pc_inst.cfg file.