IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Configure monitoring agent settings and communication with the monitoring server using command line


If the IBM Tivoli Monitoring infrastructure is used, you must configure Monitoring Agent settings before configuring the data collector to monitor any application server instances. You also need to configure Monitoring Agent communication to the monitoring server. Do not perform this configuration in a deep dive diagnostics only installation, where IBM Tivoli Monitoring is not used.

You can change the port used for communication between the data collector and the monitoring agent (this communication is on the local host). The default port is 63335. You can set an alternate node name that determines how the agent is displayed in the Tivoli Enterprise Portal navigation tree.

While you can change these values at a later time, it is normally most convenient to set them when initially configuring the communication. In this case no changes to configuration files is required to change the port number, and no customization of the Tivoli Enterprise Portal view could have been performed by any user. So, if you need to make such changes, make them at installation time if possible.

Configure Monitoring Agent settings and communication with the monitoring server on UNIX or Linux systems...

  1. Run...

      cd ITM_home/bin
      ./itmcmd config -A yn

    The itmcmd utility prompts you to change the agent configuration:

      Agent configuration started...  
      
      Edit "ITCAM Agent for WebSphere Applications" settings? 
      [ 1=Yes, 2=No ] (default is: 1):
      
      Enter 1, or press Enter to accept the default.
      

  2. The utility prompts you to select the configuration type:
      Select Configuration Type : Choose the configuration type:
       
      Configuration type description:
      
          1. Configure the Tivoli Enterprise Monitoring Agent (TEMA) port number or Agent ID. 
      
             If you modify the Tivoli Monitoring Agent port, all Application Servers with data collectors must be restarted to 
             complete the reconfiguration.
      
          2. Configure the data collector to monitor application server instances. 
      
             You can also use this option to configure the data collector to connect to the Managing Server. The option requires 
             that either the Application Servers are running (WAS Base Edition) or the Node Agent and Deployment Manager are 
             running (WAS ND or XD). 
      
             The Servers must be restarted to complete the configuration.
      
          3. Unconfigure the data collector from Application Server instances. 
      
             This option will remove all data collector configuration and runtime files for these instances. 
      
             Requires that either the Application Servers are running (WAS Base Edition) or the Node Agent and Deployment 
             Manager are running (WAS ND or XD). The Server instances must be restarted to complete the configuration. 
             After the unconfiguration, your Application Server instances will no longer be monitored.
      
          4. Reconfigure your data collectors to use a different Managing Server, change Managing Server information, or disable 
             data collector communication to the Managing Server. 
      
             The data collector must be already configured to monitor at least one application server instance. 
      
             You will need to restart the application servers monitored by the data collector.
      
          5. Upgrade ITCAM for WebSphere 6.1.x data collector to ITCAM 7.1; also to upgrade ITCAM for WAS 7.0.x data collector to ITCAM 7.1. 
      
             Requires that either the Application Servers are running (WAS Base Edition) or the Node Agent and 
             Deployment Manager are running (WAS ND or XD). The Servers must be restarted to complete the configuration.
      
          6. Update data collectors with the new maintenance or reverting the update.Requires that either the Application Servers are 
             running (WAS Base Edition) or the Node Agent and Deployment Manager are running (WAS ND or XD). 
      
             The Servers must be restarted to complete the configuration.
      
          7. Remove unused data collectors maintenance levels.
             
      Choose the configuration type: 
      
         [1=Configure Tivoli Enterprise Monitoring Agent (TEMA), 
          2=Configure data collectors within Application Servers, 
          3=Unconfigure data collectors from Application Servers, 
          4=Enable/disable communication to Managing Server for deep-dive diagnostics, 
          5=Upgrade ITCAM for WebSphere 6.1.x or ITCAM for WebSphere 7.0.x data collector to ITCAM 7.1, 
          6=Change data collectors maintenance level, 
          7=Remove unused data collectors maintenance levels ] 
      
          (default is: 1):
         
      

    Type 1 and press Enter to start configuring the data collector communication to the monitoring agent.

  3. The configuration utility prompts you for an alternative Node ID for identifying the agent.

    This identifier determines how the agent is displayed in the Tivoli Enterprise Portal navigation tree. Default is "Primary", used with the host name of the computer where the agent is installed is used.

    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 the agent.
      This is a unique id that will determine how the agent will appear in the Tivoli Enterprise Portal navigation tree. 
      The max Node ID length is 24 characters.
      Node ID (default is: Primary): 
      

    To use an alternative Node ID, enter it and press Enter. Otherwise, simply press Enter.

    Valid characters for the node ID include A-z, a-z, 0-9, underbar (_), dash (-), and period (.); do not use other characters.

  4. The configuration utility prompts you to specify a TCP socket port that the monitoring agent will use to listen for connection requests from the data collectors.

    Normally, accept the default. The port will only be used for local communication on the host.

      Monitoring Agent Listening Port.
       The Monitoring Agent will use this TCP socket port to listen for connection requests coming from the data collector(s).
       Port Number (default is: 63335): 
      

    Unless you have a special requirement to change the port number, press Enter to accept the default value.

  5. In the next step, you can choose to create a response file to save your configuration settings.

    You can use the response file to perform a silent configuration with the same parameters.

      The wizard can save your settings to a response file. A response file can be used to perform a silent configuration.
      Save Configuration Setting in a Response File 
      [ 1=true,  2=false ] (default is: 2): 
      

    To create a response file, enter 1, then enter the name of the file. Otherwise, enter 2, or press Enter to accept the default.

  6. The following message is displayed, confirming whether the agent will communicate to a Tivoli Enterprise Monitoring Server (TEMs):
      Will this agent connect to a TEMS? 
      [1=YES, 2=NO] (Default is: 1):

    If the IBM Tivoli Monitoring Type is used, select 1. If it is not used (in a deep dive diagnostics only install), select 2 (in this case the configuration process will end).

  7. The configuration utility prompts you for the Tivoli Enterprise Monitoring Server host name:
      TEMS Host Name (Default is: LLVMRH5):

    Type the correct host name and press Enter.

  8. The configuration utility prompts you to choose a network protocol that the monitoring agent will use to communicate with the monitoring server:
      Network Protocol [ip, sna, ip.pipe or ip.spipe] (Default is: ip.pipe):

    Select the protocol that was selected when the Tivoli Enterprise Monitoring Server was installed, and press Enter.

  9. The configuration utility prompts you to select a second (backup) protocol).
      Now choose the next protocol number from one of these:
           - ip
           - sna
           - ip.spipe
           - 0 for none
      Network Protocol 2 (Default is: 0):
      

    If a backup protocol was selected when the Tivoli Enterprise Monitoring Server was installed, enter that protocol and press Enter. Otherwise, simply press Enter.

  10. The configuration utility prompts you for the settings for each protocol that you have selected.

    For example, if you have selected IP.PIPE, it prompts you for the port number:

      IP.PIPE Port Number (Default is: 1918): 

    Type the port number and press Enter, or simply press Enter to accept the default.

    Also, for some protocols including IP.PIPE, the configuration utility prompts you for the KDC_PARTITION name:

      Enter name of KDC_PARTITION (Default is: null):

    You can specify the partition name if it is available, or press Enter without specifying it. You can configure the partition name at a later time.

  11. The configuration utility prompts you whether you want to configure a connection for a secondary TEMS:
      Configure connection for a secondary TEMS? 
      [1=YES, 2=NO] (Default is:2):

    If your environment includes a Tivoli Enterprise Monitoring Server for a failover connection, select 1. In this case, you will need to enter its host name and settings for communication with it (see Steps 7 to 10). Otherwise, press Enter.

  12. The configuration utility displays the following message:

    Press Enter.

  13. The agent configuration is now complete. If the monitoring agent is already started, the following message is displayed:
      Would you like to restart the component to allow new configuration to take effect? 
      [1=Yes, 2=No] (Default is: 1):

  14. Press Enter to restart the component. The new configuration takes effect after the restart.


Parent topic:

Configure the agent using command line