IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Configure the monitoring agent using command line - J2EE agent

Before terminating, the installer prompts you to invoke the itmcmd command with the config operand to configure this agent:

You may now configure any locally installed IBM Tivoli Monitoring product
via the "[ITM home]/bin/itmcmd config" command.

Change to the ITM directory's bin subdirectory, and invoke itmcmd:

./itmcmd config -A yj

...where yj is the 2-character product code for the ITCAM Agent for J2EE Monitoring Agent.

For summary information about the invocation sequence for the configuration tool, enter itmcmd without parameters.

The configuration tool begins collecting configuration information specific to the ITCAM Agent for J2EE Monitoring Agent:

Edit 'Basic' settings? (default is: Yes):

Press Enter to update the monitoring agent's basic data-collection parameters. Specify these parameters with reference to Configuration parameters for ITCAM Agent for J2EE Monitoring Agent.

Request Data Monitoring         Type number of item from the below list
        1. Disable
        2. Level1
        3. Level2
         (default is: LEVEL1): 2
Request Data Monitoring Method
        Type number of item from the below list
        1. Fixed Interval
        2. On Demand
         (default is: FIXEDINTERVAL): 2
Resource Data Monitoring         Type number of item from the below list
        1. Disable
        2. Enable
         (default is: ENABLE):
Resource Data Monitoring Method
        Type number of item from the below list
        1. Fixed Interval
        2. On Demand
         (default is: ONDEMAND):
Garbage Collection Monitoring         Type number of item from the below list
        1. Enable
        2. Disable
         (default is: ENABLE):

Once you have defined the Basic monitoring agent parameters, you are prompted for whether you want to edit the agent parameters:

Edit 'Agent (Advanced)' settings? (default is: Yes):

If you press Enter (or reply YES), you are prompted for the agent parameter values. Specify these parameters with reference to Configuration parameters for ITCAM Agent for J2EE Monitoring Agent.

If you install more than one copy of the Monitoring Agent on a single host, set the Alternative Node ID parameter to different values for each of the copies. Otherwise, the multiple copies of the monitoring agent will not work correctly with Tivoli Monitoring.

Alternative Node ID for identifying this Agent (default is: ):
ITCAM for J2EE Agent Listening Port (default is: 63335):
Maximum Number of Agent Log Events (default is: 100):
Cascading Listening Port (default is: 3006):
Using Cascading
          Type number of item from the below list
         1. Disable
         2. Enable
          (default is: DISABLE):

After you have defined the agent parameters, you are prompted for whether you want to edit the Collection parameters:

Edit 'Collection (Advanced)' settings? (default is: Yes):

If you press Enter (or reply YES), you are prompted for the Collection parameter values. Specify these parameters with reference to Configuration parameters for ITCAM Agent for J2EE Monitoring Agent.

Request Data On Demand Maximum Sample Age (sec) (default is: 30):
Request Data Fixed Interval between Collections (sec) (default is: 60):
Request Data Sampling Rate (%) (default is: 2):
Resource Data On Demand Maximum Sample Age (sec) (default is: 30):
Resource Data Fixed Interval between Collections (sec) (default is: 60):
Garbage Collection Polling Interval (sec) (default is: 60):
Log Scan Polling Interval (sec) (default is: 60):

After you have defined the Collection parameters, you are prompted for whether you want to edit the Application Dashboard (Basic) parameters:

Edit 'Application Dashboard (Basic)' settings? (default is: Yes):

If you press Enter (or reply YES), you are prompted for the Application Dashboard (Basic) parameter values. Specify these parameters with reference to Configuration parameters for ITCAM Agent for J2EE Monitoring Agent.

Application Fair Completion Rate Threshold (%) (default is: 99):
Application Bad Completion Rate Threshold (%) (default is: 95):
Application Fair Resource Usage Threshold (%) (default is: 40):
Application Bad Resource Usage Threshold (%) (default is: 80):
Application Resource Usage Monitoring Cutoff Threshold (%) (default is: 25):

After you have defined the Application Dashboard (Basic) parameters, you are prompted for whether you want to edit the Application Dashboard (Auto Threshold) parameters:

Edit 'Application Dashboard (Auto Threshold)' settings? (default is: Yes):

If you press Enter (or reply YES), you are prompted for the Application Dashboard (Auto Threshold) parameter values. Specify these parameters with reference to Configuration parameters for ITCAM Agent for J2EE Monitoring Agent.

Response Time Selection (%) (default is: 50):
Response Time Deviation (%) (default is: 200):
Fair Response Time Projection (%) (default is: 150):
Bad Response Time Projection (%) (default is: 300):

The configuration tool next begins to configure the Tivoli Enterprise Monitoring Agent:

Will this agent connect to a TEMS? [YES or NO] (Default is: YES):

Accept the default (YES). The agent prompts for the location of the monitoring server this agent is to communicate with:

TEMS Host Name (Default is: localhost):

If the monitoring server resides on this node, press Enter to accept the default; otherwise supply the host name.

You are asked for the network protocol used for your ITM environment:

Network Protocol [ip, sna, ip.pipe or ip.spipe] (Default is: ip.pipe):

Specify the primary communications protocol for communication with the monitoring server that will communicate with this agent: IP.UDP, IP.PIPE, IP.SPIPE, or SNA.

You are prompted for your secondary network protocol. You can specify up to three communication methods; this enables backup communication methods so that, if protocol 1 fails, protocol 2 is used and then protocol 3.

Now choose the next protocol from one of these:
     - ip
     - sna
     - ip.spipe
     - none
Network Protocol 2 (Default is: none):
IP.PIPE Port Number (Default is: 1918):

You are prompted for whether to change the name of the KDC_PARTITION.

Enter name of KDC_PARTITION (Default is: null):

Press Enter; do not specify a name for this partition. Finally, you are asked if you need to configure this agent for connection to a secondary (hot standby) monitoring server:

Configure connection for a secondary TEMS? [YES or NO] (Default is: NO):
Enter Optional Primary Network Name or "none" (Default is: none):

Press Enter for both prompts.

After you have completed all questions, the following text is displayed:

Agent configuration completed...

When you have configured the monitoring agent, run the following commands to reconfigure the monitoring server, portal server, and portal client:

  1. On the portal server, run the following command: itmcmd config -A cq
  2. On all portal client systems, run the following command: itmcmd config -A cj
  3. On the monitoring server, run the following command:itmcmd config -S -t <tems_name>


Parent topic:

Configure the Tivoli Enterprise Monitoring Agent on UNIX and Linux

+

Search Tips   |   Advanced Search