IBM Tivoli Composite Application Manager Agents for WebSphere Applications Version 7.2, for J2EE Version 7.1.1, for HTTP Servers Version 7.1

Executing the configuration script in prompt mode

You must configure the data collector for each application server instance that you want to monitor.

The ITCAM Data Collector for WebSphere® Configuration Utility referred to here as the configuration script is a menu driven command-line utility for configuring the ITCAM Data Collector for WebSphere.

When you run the configuration script in prompt mode, when you are prompted for values, the applicable default value is displayed in brackets at the end of the prompt. If you enter no value, the script uses the default value. The default value also provides an example of the format of the value that is required.

The default location for the configuration setup script is: /u/itcam72/bin. For a list of the options for running the script command, see Configuration Options.

You must login as a WebSphere administrator who has permission to administer the application server configuration before you run the config.sh script.

To configure the data collector to monitor one or more server instances, complete the following procedure:

Log in as a WebSphere administrator with permission to administer the application server configuration, you can use "su -s userid" if you have the appropriate permission.
Complete one of the following procedures:
1. If you are running the application server in a Network Deployment environment, make sure that the Deployment Manager and the node agent are running.
2. If you are running the application server in a stand-alone environment, ensure that the instance of the application server that is being monitored by ITCAM for WebSphere Application Server is running.
To set any of the configuration options as environment variables before running the configuration script, export the environment variables. By setting options in the command-prompt, the config.sh script uses them as the new default values. Defaults on the command-prompt override defaults that are set by exported environment variables. Here are examples of how to export an environment variable from a command-prompt:
```
export ITCAM_CONNTYPE=RMI
export ITCAM_USER=b8admin
```
When you export these variables, the config.sh script uses them as the default values. When prompted, you do not need to enter a value, instead just press Enter.
To run the configuration script, run the following command:
```
./config.sh [options]
```
The utility starts and displays the IP addresses of all network cards found on the local computer system and prompts you to specify the interface to use for the data collector:
```
List of TCP/IP interfaces discovered: 
  1. 9.111.98.108 
Enter a number [default is: 1]: 
```
Enter the number that corresponds to the IP address to use.
The utility prompts you to enter the WebSphere Application Server configuration home directory:
```
Enter WebSphere home directory [default is: /u/WAS80]:
```
Enter the HFS path name of AppServer_home, for example, /u/WAS800B/beta/tvt7006/AppServer and press Enter. The configuration script uses this path to search for the wsadmin.sh script. The wsadmin.sh script is used to configure the target application server for ITCAM for WebSphere Application Server monitoring. If the path is a valid, the utility issues the following message:
```
Searching for wsadmin locations under WAS configuration home:
/u/WAS800B/beta/tvt7006/AppServer
```
If the path is not a valid WebSphere Application Server configuration home directory, the utility issues a message, for example
```
Searching for wsadmin locations under directory: /u/WAS800B/beta/tvt7006
```
The utility prompts you to select which of the listed wsadmin.sh scripts to use
```
Choose WebSphere wsadmin.sh to use
1. /u/WAS800B/beta/tvt7006/AppServer/bin/wsadmin.sh
2. /u/WAS800B/beta/tvt7006/AppServer/profiles/default/bin/wsadmin.sh
Enter a number [default is: 2]:
```
Note: The list should not include Deployment Manager or Node Manager servers. Any application server wsadmin.sh script will work, but we recommend the wsadmin.sh script in the AppServer_home/profiles/default/bin directory because the wsadmin.sh script uses the wsadmin.properties file associated with it.
Enter the number that corresponds to the wsadmin.sh that you want to use. The utility then returns the value of the WebSphere Application Server profile home:
```
WebSphere Home: /u/WAS800B/beta/tvt7006/AppServer WebSphere Profile: default
```
The utility indicates whether WebSphere Global Security is enabled for the WebSphere Application profile you have specified:
```
WebSphere Global Security is enabled.
```
If global security is not enabled, skip to step 14.
The utility prompts you to specify whether to retrieve security settings from a client properties file:
```
Do you want to retrieve security settings from a client properties file 
(soap.client.props or sas.client.props)? 
[1 - YES, 2 - NO] [default is: 2]: 
```
The Data Collector communicates with the WebSphere Administrative Services using the Remote Method Invocation (RMI) or the SOAP protocol. If global security is enabled for a profile, you must specify the user ID and password of a user who is authorized to log in to the IBM® WebSphere Application Server administrative console for the profile. Alternatively, you can encrypt the user name and password and store them in client properties files before configuring the data collector. You must use the sas.client.props file for an RMI connection, or the soap.client.props file for a SOAP connection.
Enter 1 to allow the utility to retrieve the user name and password from the appropriate client properties file and skip to step 14. Otherwise, enter 2 to enter the user name and password.
```
CFG1018I Enter WebSphere admin user name:
CFG1019I Enter WebSphere admin password:
```

While the search is executing the utility displays an updating status:

Searching for servers under profile: default
Connecting to profile......................
Start finding servers for profile default
Installing or upgrading IBM Tivoli Composite Application Manager for SOA on Windows 3
Processing default.............
Finding servers done successfully for profile default
Finished finding servers for profile default
Successfully executed searching servers for Profile: default

The utility searches for all application server instances under the default profile. The utility displays all servers that have not been configured yet for data collection and all servers that have been configured to use the current version of the ITCAM Data Collector for WebSphere.

The utility prompts you to select one or more application server instances from the list:
```
Choose one or more servers to configure/unconfigure for data collection:
Application servers not yet configured:
1. beta.tvt7006.b8sr00f(default)
Application Servers configured by the current version:
2. beta.tvt7006.b8sr00a(default)
3. beta.tvt7006.b8sr00b(default)
Enter a number or numbers separated by commas, or enter * to select all:  
```
Note: For a Network Deployment or Extended Deployment environment, the Node Agent and Deployment Manager must be running. For a stand-alone environment, application server instances must be running during the configuration of the data collector.

Note: Ensure that the application server instances you select are the actual nodes that host the applications or services you want to monitor.
Enter the number that corresponds to the application server instance to configure for data collection or enter * to configure all application server instances for data collection. To specify a subset of servers, enter the numbers that represent the servers separated by commas. For example: 1,2,3.
In the Integration with ITCAM for SOA Agent section, the utility provides an option for integrating the data collector with the ITCAM for SOA agent.
```
Do you want to integrate with an ITCAM for SOA Agent? [1 - YES, 2 - NO] 
[default is: 2]:
```
You must install and configure the ITCAM for SOA Agent and its application support files, and optionally configure topology support to complete the installation and configuration of the ITCAM for SOA Agent. For more information about installing and configuring the ITCAM for SOA Agent, see IBM Tivoli Composite Application Manager for SOA Installation Guide 7.1.1.

Enter 1 to integrate the data collector with the ITCAM for SOA Agent. Otherwise, enter 2.
In the Integration with ITCAM Agent for WebSphere Applications section, the utility provides an option for integrating the data collector with the ITCAM Agent for WebSphere Applications.

You can integrate the data collector with ITCAM Agent for WebSphere Applications, or with the ITCAM for Application Diagnostics Managing Server, or with both.
```
Do you want to integrate with an ITCAM Agent for WebSphere Applications?
 [1 - YES, 2 - NO] 
[default is: 2]:
```
You must install and configure the ITCAM Agent for WebSphere Applications and its application support files to complete the installation and configuration of the ITCAM Agent for WebSphere Applications. For more information about installing and configuring the ITCAM Agent for WebSphere Applications, see IBM Tivoli Composite Application Manager Agent for WebSphere Applications Installation and Configuration Guide.
Enter 1 to integrate the data collector with the ITCAM Agent for WebSphere Applications. Otherwise, enter 2 and skip to step 21.
You are prompted to enter the host name of the ITCAM Agent for WebSphere Applications.
```
Enter the host name or IP address of the ITCAM Agent for WebSphere Applications TEMA:  
[default is: 127.0.0.1]:
```
Enter the fully qualified host name or IP address of the ITCAM Agent for WebSphere Applications Monitoring Agent. The Monitoring Agent is located on the local host, so you do not need to change the default.
You are prompted for the port number of the ITCAM Agent for WebSphere Applications Monitoring Agent.
```
Enter the port number of the ITCAM Agent for WebSphere Application TEMA:  
[default is: 63335]:
```
You can change the port that is used for communication between the data collector and the ITCAM Agent for WebSphere Applications Monitoring Agent. This communication is on the local host; the default port is 63335. You can change the port at a later time, but it is normally most convenient to set it when initially configuring the data collector.
Enter the port number of the Monitoring Agent.
The utility prompts you for the server alias. The alias that you set becomes the name of the Tivoli® Enterprise Portal node containing the monitoring information for this application server instance. The default is the node name combined with the server name.
```
Enter the server alias for server server1 in node node1  [default is: node1server1]: 
```
Accept the default or enter another alias.
In the Integration with ITCAM for Application Diagnostics Managing Server section, the utility provides an option for integrating the data collector with the ITCAM for Application Diagnostics Managing Server, installed on a separate Windows, Linux, or UNIX server, for deep-dive diagnostics. For information about installing the Managing Server, see IBM Tivoli Composite Application Manager for Application Diagnostics Managing Server Installation Guide.
You are prompted to specify whether you want to integrate the data collector with a Managing Server.
```
Do you want to integrate with an MS? [1 - YES, 2 - NO] 
[default is: 2]:
```
Note: To integrate with ITCAM for Application Diagnostics Managing Server for deep-dive analysis, you must have ITCAM for Application Diagnostics 7.1 installed.

Note: If you decide not to configure the Managing Server at this time, you can still configure the data collector to communicate with the Managing Server later.
Enter 1 to integrate with the Managing Server. Otherwise, enter 2 and skip to step 25.
You are prompted to specify the host name of the Managing Server:
```
Enter the host name  or IP address of the  MS
[default is: 127.0.0.1]:
```
Enter the fully qualified host name of the Managing Server.
You are prompted to specify the port number of the Managing Server:
```
Enter the code base port number of the MS
[default is: 9122]:
```
The port number is codebase port on which the Managing Server is listening.

Note: The port number is defined as the value of the key "PORT_KERNEL_CODEBASE01" in the .ITCAM61_MS_CONTEXT.properties file located under the Managing Server Home directory. See IBM Tivoli Composite Application Manager for Application Diagnostics Managing Server Installation Guide.
The configuration tool attempts to connect to the Managing Server and retrieve the value for the MS_home directory. If successful, it produces a message similar to the following message:
```
MS home directory is: /opt/IBM/itcam/WebSphere/MS
```
If the connection to the Managing Server is not successful, you are prompted to enter the value for the MS_home directory:
```
Enter ITCAM Managing Server install directory [default is C:\IBM\itcam\WebSphere\MS]:
```
If prompted, enter the value of the MS_home directory.
The utility prompts you to specify whether you want to configure advanced settings for the Managing Server.
```
Do you want to configure advanced settings for the MS? [1 - Yes, 2 - No]
[default is: 2]:
```
Enter 1 to configure advanced settings. Otherwise, enter 2 and skip to step 29.
You are prompted to enter the range of RMI port numbers that the data collector uses to accept incoming connections from the Managing Server:
```
Enter the RMI port numbers [default is: 8200-8299]:
```
Note: Make sure that the ports are not being blocked by the firewall or other applications.

Enter the RMI port numbers.
You are prompted to enter the range of Controller RMI port numbers:
```
Enter the range of Controller RMI port numbers 
[default is: 8300-8399]:
```
Enter the RMI Controller port numbers.
You are prompted to enter the RFS port number of the Managing Server:
```
Enter the RFS port number of the MS: [default is: 9120]:
```
Enter the RFS port number.
In the Integration with ITCAM for Transactions section, the utility provides an option for integrating the data collector with ITCAM for Transactions.
Note: To integrate the data collector with ITCAM for Transactions, you must install ITCAM for Transactions within an IBM Tivoli Monitoring environment.
You are prompted to specify whether you want to integrate with ITCAM for Transactions:
```
Do you want to integrate with ITCAM for TT? [1 - YES, 2 - NO] 
[default is: 2]:
```
After you have configured the data collector to support ITCAM for Transactions, you then must perform some additional configuration. For details of further configuration options and how to view the aggregated transaction information, see IBM Tivoli Composite Application Agent for WebSphere Applications Configuring and Using TTAPI.
Enter 1 to integrate the data collector with ITCAM for Transactions. Otherwise, enter 2 and skip to step 34.
You are prompted to specify the ITCAM for Transactions z/OS® subsystem name:
```
Enter the ITCAM for Transactions z/OS subsystem name [default is: CYTZ]:
```
Enter the ITCAM for Transactions z/OS subsystem name.

You are prompted to specify the ITCAM for Transactions z/OS directory path:

Enter the ITCAM for Transactions z/OS directory path [default is: /usr/lpp/cyt/jar/IBM ]

In the Integration with Tivoli Performance Viewer section, the utility provides an option for integrating the data collector with Tivoli Performance Viewer (TPV).
```
Do you want to integrate with Tivoli Performance Viewer? [1 - YES, 2 - NO] 
[default is: 2]
```
This is the step that configures ITCAM for WebSphere Application Server 7.2 support for WebSphere Application Server 8.5.x. Following configuration, metrics are visible in the WebSphere Application Server administrative console in the Tivoli Performance Viewer.

ITCAM for WebSphere Application Server 7.2 support for WebSphere Application Server 8.5 includes the ITCAM Data Collector for WebSphere. Enter 1 to integrate the ITCAM Data Collector for WebSphere with the Tivoli Performance Viewer. Otherwise, enter 2.
In the Advanced Settings section, the utility provides options for performing advanced configuration of the data collector. The utility prompts you to specify whether to change the garbage collection log path:
```
Do you wish GC log data included in output? [1 - YES, 2 - NO] [default is: 2]:
```
Enter 1 to include verbose GC output in the WebSphere output. Otherwise, enter 2..

In the Data collector configuration summary section, the utility provides a summary of the data collector configuration that will be applied to the specified application server instances:

1) List of servers selected

   - WAS server: beta.tvt7006.b8sr00a(default) 
       WAS cell: beta 
        WAS node: tvt7006 

       WebSphere Profile home    : 
         /u/WAS800B/beta/tvt7006/AppServer/profiles/default 

       wsadmin location          : 
         /u/WAS800B/beta/tvt7006/AppServer/profiles/default/bin/wsadmin.sh 

                     WAS version : 8.0.0.1 
                       Deployment : Network deployment 
                         JVM mode : 64bit
                     Server alias : node1server1
               Configuration home : /u/itcam72/CONFIG 

 2) Integrate with ITCAM for SOA Agent : Yes 

 3) Integrate with ITCAM Agent for WebSphere Applications : Yes 

       TEMA hostname or IP address : 127.0.0.1 
                TEMA port number : 37275 
                      Monitor GC : No 

 4) Integrate with ITCAM for AD Managing Server : Yes 

       MS hostname or IP address : devapp-lnx-s06.usca.ibm.com 
         MS codebase port number : 9122 
               MS home directory : /opt/bvt/IBM/itcam/WebSphere/MS 

 5) Integrate with ITCAM for Transactions : Yes 

                    TT subsystem : CYTZ 
                    TT directory : /u/itt72/smpe/usr/lpp/cyt/jar/IBM 

 6) Integrate with Tivoli Performance Viewer : Yes 

 7) Advanced settings :  

                Collect SMF data : Leave 
             GC output to sysout : No 


Configuration sections:
 1) List of servers selected 
 2) Integrate with ITCAM for SOA Agent 
 3) Integrate with ITCAM Agent for WebSphere Applications 
 4) Integrate with ITCAM for AD Managing Server 
 5) Integrate with ITCAM for Transactions 
 6) Integrate with Tivoli Performance Viewer 
 7) Advanced settings

The summary section provides options to reconfigure parts of the data collector configuration before applying the changes and an option to exit the configuration tool without applying your changes. Enter the number that represents the section you want to edit. Enter * to reconfigure all sections. Enter a to accept your changes. Enter q to exit the ITCAM Data Collector for WebSphere Configuration Utility without configuring the data collector.

Up to this point, no configuration changes have been made, which means, it is safe to exit without affecting the WebSphere Application Server configuration.

When you enter a to accept your changes, you are prompted to specify whether you want to create a backup of your current WebSphere Application Server configuration:
```
Do you want to backup current WebSphere configuration? [1 - YES, 2 - NO]
[default is: 2]:
```
Enter 1 to create a backup of the current configuration. Otherwise, enter 2.
The changes are applied and a status message is presented to indicate that the configuration of the data collector for the profile is complete:
```
Successfully executed Configuring for Cell: beta Node: tvt7006 Profile: default
```
After configuring the data collector to monitor application server instances, you must restart the instances. The Data Collector configuration takes effect when the application server instances are restarted.

The ITCAM Data Collector for WebSphere Configuration Utility creates a log of all the configuration operations, including any error conditions. You might be requested to provide the log contents to IBM software support. The log file is located here: config_home/data/config-trace.log

Feedback