IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Unconfigure the data collector from application server instances using command line - WAS agent

If you no longer want the data collector to monitor an application server instance, you can unconfigure the data collector from it.

To unconfigure the data collector, perform the following steps:

  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 3 and press Enter to unconfigure the data collector from application server instances.

  3. The following message is displayed.
      WebSphere Server Unconfiguration :
      
      No 'WebSphere Server Unconfiguration' settings available.
      Edit 'WebSphere Server Unconfiguration' settings.
       [1=Add, 2=Edit, 3=Del, 4=Next, 5=Exit] (default is: 5):

    Enter 1.

  4. The configuration utility prompts you for the WebSphere server instance names.
      Input WebSphere Server Instance Name 
      For example: cells/ITCAMCell/nodes/ITCAMNode/servers/server1
      (default is: ): 

    Enter the full names of one or several WebSphere server instances that you no longer want to monitor with the data collector. Separate multiple instances with commas (for example, cells/Cell01/nodes/Node01/servers/server1, cells/Cell01/nodes/Node01/servers/server2)

  5. The configuration utility prompts you for the host name or IP address of the WebSphere administrative server.
      Input the WebSphere administrative server host name or IP address. (If it has not changed since the configuration was applied, then you can leave
      this value blank)
      Input Server Admin Host Name (default is: ): 

    If the WebSphere administrative server has not changed since this instance was configured, press Enter. Otherwise, enter the WebSphere administrative server fully qualified host name or IP address (for example, 9.123.98.67).

  6. Select the WebSphere administrative server connection type.
      The WebSphere administrative server connection type. 
      (If it has not changed since the configuration was applied,  then you can leave this value blank)
      Select Server Connection Type [ 1=SOAP, 2=RMI ]
       (default is :1):

    If the WebSphere administrative server connection has not changed since this instance was configured, press Enter. Otherwise, enter 1 for a SOAP connection, or 2 for an RMI connection.

  7. The configuration utility prompts you for the server administrative port number.
      The WebSphere administrative server SOAP or RMI connect port number.
      (If it has not changed since the configuration was applied,  then you can leave this value blank)
      Input Server SOAP or RMI connect port (default is: ):

    If the WebSphere administrative server port has not changed since this instance was configured, press Enter. Otherwise, enter the port number.

  8. The configuration utility prompts you whether you want to use the user name and password stored in the client properties file, if WebSphere Global Security is enabled.
      Do you want to use the user name and password stored in soap.client.props
       or sas.client.props of WebSphere?
      Use the user name and password stored in client properties?
       [ 1=Yes, 2=No ] (default is: 2):

    To use the user name and password stored in the properties file, enter 1. To enter the user name and password, enter 2; then, when prompted, enter the WebSphere administrative user name and password. If WebSphere Global Security is disabled, enter 2, and press Enter when prompted for the user name and password.

  9. The following message is displayed.
      'WebSphere Server Unconfiguration' settings:
      Please input WebSphere Server Instance 
      Name= cells/Cell01/nodes/Node01/servers/server1
      Edit 'WebSphere Server Unconfiguration' settings.
       [1=Add, 2=Edit, 3=Del, 4=Next, 5=Exit] (default is: 5):

    If you want to unconfigure the data collector for more WebSphere application server instances, enter 1 and go to Step 4. Otherwise, press Enter.

  10. 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.

  11. 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

  12. 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