Unconfigure the data collector for application server instances using GUI

IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Unconfigure the data collector for application server instances using GUI - 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 do this, perform the following steps:

Enter the Agent Configuration window. See Enter the Agent Configuration window.
Figure 1. Unconfiguring the data collector for application server instances, window 1
Select Unconfigure data collectors from Application Servers and click Next.
Select the server instance(s) you want to unconfigure. All the instances monitored by this installation of the agent are listed.

Instance(s) must be running during the configuration.
For Network Deployment environment the Node Agent and Deployment Manager must also be running.
Set the connection parameters for the application server instances. By default, the information that was set during initial data collector configuration for each instance will be displayed (except username and password). The following table lists the fields:

Fields for establishing data collector and application server communication

Field What to do
Host Name Type the fully qualified host name or IP address of the application server instance that the data collector monitors. Do not include a protocol in the host name. For example, type...
myserver.ibm.tivoli.com
...not...
https://myserver.ibm.tivoli.com

If using a Network Deployment environment, provide the host name of the deployment manager instead.
Connector Type Select the type of connection the data collector and application server will use for communication.
Port If you selected SOAP as the connector type, enter the SOAP port used by the application server instance.
The SOAP port is identified in the AppServer_home/profiles/profile_name/config/cells/cell_name/nodes/node_name/serverindex.xml file for the instance of application server that the data collector will monitor.
If using Network Deployment, provide the SOAP port of the deployment manager instead.
If you selected RMI as the connector type, enter the RMI port used by the application server instance.
Username Only for Global Security enabled. Type the user ID of a user authorized to log on to the WAS administrative console. This user must have the agent role on the application server.
Alternatively, to retrieve the user ID from a properties file, select Use 'soap.client.props' or 'sas.client.props'.
Password Only for Global Security enabled. Type the password corresponding to the user specified in the Username field.
Alternatively, to retrieve the password from a properties file, select Use 'soap.client.props' or 'sas.client.props'.

Figure 2. Unconfiguring the data collector for application server instances, window 2
Check the boxes next to any instances you no longer want to monitor. Then, click Next.
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.
Figure 3. Unconfiguring the data collector for application server instances, window 3
To create a response file, check the box Save your settings in a response file and click Browse to select the file location; otherwise leave the box unchecked. If you uncheck Apply data collector Unconfiguration, the unconfiguration will not be applied; you can still save it in the response file. When the boxes are set correctly, click Next.
The configuration utility will validate the applications server connection and apply the unconfiguration.
Figure 4. Unconfiguring the data collector for application server instances, window 4
Click Next.
WebSphere unconfiguration summary information is displayed.
Figure 5. Unconfiguring the data collector for application server instances, window 5
To export the summary report to a file, click the button...
Export Summary Report
The application server needs to be restarted before the data collector configuration takes effect. Click Home to return to the Agent Configuration window, or click OK to complete the configuration process. If you click OK, the TEMS Connection window is displayed.
If IBM Tivoli Monitoring is not used (in a deep dive only installation), make sure No TEMS is selected, and click Save. Otherwise

Parent topic:
Configure the agent using GUI

+
Search Tips | Advanced Search

Field	What to do
Host Name	Type the fully qualified host name or IP address of the application server instance that the data collector monitors. Do not include a protocol in the host name. For example, type... myserver.ibm.tivoli.com ...not... https://myserver.ibm.tivoli.com If using a Network Deployment environment, provide the host name of the deployment manager instead.
Connector Type	Select the type of connection the data collector and application server will use for communication.
Port	If you selected SOAP as the connector type, enter the SOAP port used by the application server instance. The SOAP port is identified in the AppServer_home/profiles/profile_name/config/cells/cell_name/nodes/node_name/serverindex.xml file for the instance of application server that the data collector will monitor. If using Network Deployment, provide the SOAP port of the deployment manager instead. If you selected RMI as the connector type, enter the RMI port used by the application server instance.
Username	Only for Global Security enabled. Type the user ID of a user authorized to log on to the WAS administrative console. This user must have the agent role on the application server. Alternatively, to retrieve the user ID from a properties file, select Use 'soap.client.props' or 'sas.client.props'.
Password	Only for Global Security enabled. Type the password corresponding to the user specified in the Username field. Alternatively, to retrieve the password from a properties file, select Use 'soap.client.props' or 'sas.client.props'.