IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Configure the data collector communication with the Managing Server using command line - WAS agent

If you have configured the data collector to monitor an application server instance, you can later change its configuration for communication with the ITCAM for Application Diagnostics Managing Server for this instance.

In this way, you can:

You can perform such configuration on many configured application server instances at the same time.

If the data collector communicates to the Managing Server, you can also use the Visualization Engine to disable such communication (Administration > Server Management > Data Collector Configuration). See Table 1 for a comparison between these two ways of disabling data collector communication to the Managing Server:


Comparison of ways to disable data collector communication to the Managing Server.

Disable using data collector configuration Disable using Visualization Engine
The application server instance is not listed in the Visualization Engine. The application server instance remains listed in the Visualization Engine.
The Visualization Engine shows no information about the application server instance. The Visualization Engine shows whether the application server instance is up or down; monitoring information is not available.
No system or network resources are used for Managing Server communication. Some system and network resources are used to maintain Managing Server communication.
You do not need to apply maintenance fixes for the agent that only impact Managing Server communication. Apply maintenance fixes for the agent that only impact Managing Server communication.
To re-enable communication, perform data collector configuration again, and restart the application server. To re-enable communication using the Visualization Engine, you do not need to restart the application server.

Complete the following steps to enable, disable, or configure Data Collector communication with the Managing Server:

  1. Run...

      cd /opt/IBM/ITM/bin
      ./itmcmd config -A yn

    The itmcmd utility prompts you whether you want to change 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.Use this option to 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.Use this option to 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.Use this option to unconfigure the data collector from Application 
Server instances. This option will remove all data collector configuration 
and runtime filesfor these instances. It 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.Use this option to 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.Use this option to 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. It 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.Use this option to update data collectors with the new maintenance or 
reverting the update.It 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.Use this option to 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 4 and press Enter to configure the data collector communication with the Managing Server.

  3. The following message is displayed.
    Enable/disable communication to Managing Server for deep-dive diagnostics: 


Description:
    1. Configure or Reconfigure Communication to Managing Server is used
to configure data collectors to communicate with Managing Server (requires
server restart)
    2. Disable data collectors communication to Managing Server is used to temporary disable communication between the DC and the MS. Disable does not unconfigure the MS connection settings from data collector properties files.
It only modifies the property dc.operation.mode (and omit "ms") in 
dc.java.properties file. (requires server restart).  
Select the option:      [ 1=Configure or Reconfigure Communication to the Managing Server, 2=Disable Communication to the Managing Server ] 
(default is: 1): 2
    To enable Managing Server communication that was previously not configured, or to change the address or port of the Managing Server, enter 1. Then, follow Steps 4 to 10. Then go to Step 5.

    If you want to disable communication with the Managing Server, enter 2 and go to the next step.

  4. The configuration utility prompts you for the WebSphere server instance names.
    Input the full name(s) of the WebSphere server instance(s) that you want
to configure. Multiple server instances should be separated by a comma. 
 For example: cells/ITCAMCell/nodes/ITCAMNode/servers/server1, cells/ITCAMCell/nodes/ITCAMNode/servers/server2
Input the full WebSphere Server Instance Name(s) (default is: ):
    Enter the full names of one or several WebSphere server instances for which you want to disable Managing Server communication, separate multiple instance names with commas.

  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 configuration utility prompts you whether this Agent connects to a Tivoli Enterprise Monitoring Server.
    Will this agent connect to a TEMS? [1=YES, 2=NO] (Default is: 1):
    If the IBM Tivoli Monitoring infrastructure is used, enter 1. Otherwise (in a deep dive diagnostics only install), enter 2; in this case the unconfiguration process will be completed

  7. Press Enter repeatedly to accept the existing settings for the connection to Tivoli Enterprise Monitoring Server. Alternatively, you can change these settings; see Steps 7 to 14


Parent topic:

Configure the agent using command line

+

Search Tips   |   Advanced Search