ITCAM for SOA 7.2 Fix Pack 1

The DataPower configuration file

For the DataPower® data collector, the Data Collector Configuration utility and the KD4configDC command manipulate the contents of a special DataPower configuration file by adding sections to the file when new DataPower monitoring is enabled, and removing sections from the file when monitoring is disabled. Each invocation of the Data Collector Configuration utility or the KD4configDC command adds, updates, or removes one section of the DataPower configuration file. Each section of the DataPower configuration file might be associated with its own data group, or it might be part of a larger data group to which other sections of the configuration file also belong.

The DataPower data collector uses this configuration file to identify the DataPower SOA appliances that are to be monitored and to specify all of the information that is needed to communicate with those appliances. Typical information that is stored for each connection includes host name and port, user ID and password, domains to monitor, and polling interval.

The configuration file is in the ITCAM4SOA_Home/KD4/config directory on Linux or UNIX systems and the ITCAM4SOA_Home/KD4/config directory on Windows systems and is called KD4.dpdcConfig.properties. This file is maintained separately from the existing KD4.dc.properties configuration file. This is a sample DataPower configuration file:

# Sample DataPower data collector configuration file
DataPower.count=3
#
DataPower.host.1=dpbox1
DataPower.port.1=5550
DataPower.path.1=/
DataPower.poll.1=60
DataPower.user.1=admin
DataPower.encpswd.1=#$%*&
DataPower.domainlist.1=default,testdom1
DataPower.displaygroup.1=dpbox1
DataPower.subExpire.1=15
DataPower.maxrecords.1=1000

#
DataPower.host.2=dpbox2
DataPower.port.2=5550
DataPower.path.2=/
DataPower.poll.2=30
DataPower.user.2=user1
DataPower.encpswd.2=&*%$#
DataPower.domainlist.2=userdom1,userdom2,userdom3
DataPower.displaygroup.2=user_doms
DataPower.subExpire.2=15
DataPower.maxrecords.2=1000
#
DataPower.host.3=dpbox2
DataPower.port.3=5550
DataPower.path.3=/
DataPower.poll.3=30
DataPower.user.3=admin
DataPower.encpswd.3=*%$#&
DataPower.displaygroup.3=all_doms
DataPower.subExpire.3=15
DataPower.maxrecords.3=1000

In the example, there are three sections in the configuration file. The properties in each of the three sections provide all of the information that is needed to establish and manage a single connection or session with each DataPower SOA appliance.

Change the information in this configuration file using either the Data Collector Configuration utility or the KD4configDC command. You can only modify the parameters that are set when you first run the Data Collector Configuration utility or when you first issued the KD4configDC command. To set additional parameters, you must manually add them to the configuration file.

Using various combinations of parameters in the Data Collector Configuration utility input pages or in the KD4configDC command, you can achieve different monitoring configurations to separate or aggregate data among domains and appliances. See Considerations for enabling data collection for DataPower monitoring for more information.

Before you configure your DataPower environment for data collection, consult with your local systems management planners to understand which domains on which DataPower SOA appliances are to be monitored and how the data from these domains and appliances should be separated or aggregated for display in the Tivoli® Enterprise Portal.

To set the DataPower.maxrecords property to an optimal value, it is useful to determine the number of transactions that are processed by each of the configured domains. The DataPower.maxrecords property must be set in line with the expected traffic levels of each configured domain. For more information about setting the transaction rate, see Optimizing performance.

Restriction: In an upgrade scenario, to set the maximum number of records for an existing display group, you must add the DataPower.maxrecords parameter manually to the section in the KD4.dpdcConfig.properties file that configures the display group.

Additional properties

Beginning with ITCAM for SOA version 7.2 Fix Pack 1, you can optionally add the following properties manually to the KD4.dpdcConfig.properties file:

DataPower.dimension.domain

Adds the DataPower domain attribute to the Service Inventory_610, the Service Inventory Requester Identity_610, and the Fault Log_610 tables. The domain attribute is added to the Application Server Cluster Name column in each table.

Because the Application Server Cluster Name is a dimensional field within the ITCAM for SOA Reports schema, when you run reports on the Tivoli Data Warehouse, you can display aggregated metric data by domains.

If the DataPower.domainlist parameter contains more than one domain, the DataPower.dimension.domain parameter is treated as being set to false.

DataPower.alias

Assigns an alias to the DataPower host. If this property is set, the alias is added to the Application Server Cell Name column in the Service Inventory_610, the Service Inventory Requester Identity_610, and the Fault Log_610 tables. Alternatively, you can use the DataPower.displaygroup property to create an alias for the DataPower host.

DataPower.multihost.group

The DataPower.displaygroup property defines the name to display for the DataPower appliance node in the Navigator view in the Tivoli Enterprise Portal. When the property is set, data from all DataPower appliances that are associated with the display group is aggregated. The data is available from the single node in the Navigator view.

The display group might be associated with different domains on the single DataPower appliance. In the Service Inventory_610, the Service Inventory Requester Identity_610, and the Fault Log_610 tables, the Application Server Node Name attribute displays the name of this appliance. Alternatively, the display group might be associated with multiple appliances. The Application Server Node Name attribute displays the name of only one of the appliances.

By setting the DataPower.multihost.group property to true, you indicate that there are multiple appliances associated with a display group. The Application Server Node Name attribute is not populated. By setting the property to false, you indicate that the display group is associated with a single DataPower appliance. The name of the DataPower appliance is added to the Application Server Node Name column. If the DataPower.multihost.group property is not specified in the configuration file, the property is set to false.

Feedback