Limitations

You can control the monitoring to limit the collection of data to specific services and operations, but you cannot use filter controls to reject messages to specific services or operations. To filter (reject) messages, use the Policy Rules and Actions of the DataPower® Web Services Proxy configuration.

If the transforms (as described in Configuring processing rules for DataPower Web Services Proxy gateways) are not activated, the data collector does not generate a meaningful correlator for messages flowing through the DataPower SOA appliance, so this data does not render properly in the topology, sequence diagram, and pattern views in the IBM® Web Services Navigator.

The DataPower data collector creates metric, content, operation and trace log files, but because message filtering is not supported, it does not create any action log files.

Depending on your configuration, the data collector creates multiple metric and content log files to describe the existence of several different display groups. Each display group is represented as a separate node in the Tivoli Enterprise Portal Navigator view. The log files for each display group hold the data for all of the DataPower SOA appliances that are configured for that display group, which might span multiple DataPower domains and include data from multiple DataPower SOA appliances.

Before you attempt to delete an application domain from DataPower that is being monitored by the DataPower data collector, you must either run the KD4configDC command to disable monitoring of that application domain, or stop the data collector. Otherwise, when you attempt to delete the domain using the DataPower administration console, you receive an error and the domain cannot be deleted.

[ Top of Page | Previous Page | Next Page | Contents | Index ]