DataPower policies

This section provides details of the supplied DataPower policies to enable you to customize them for your specific environment. 

If you simply want to get started using the policy as quickly as possible (with no customization), see Getting started with policies. In order to gain a better understanding of policies, see Policy architecture. 

Related topics

Getting-started-with-policies

Policies-supplied-with-TrueSight-Middleware-and-Transaction-Monitor

Creating-a-policy 

DataPower_Agents_Minimal

No Minimal level is provided for DataPower. Basic is the lowest level of supplied monitoring.

DataPower_Agents_Basic

The Basic level of the DataPower Agent Policies references the basic level of BMM-self-monitoring-policies and then references an Object Policy Group (DataPower_POLICY_Basic) that turns on historical data collection for all key components using the SAMPLE History Template. 

This Object Policy Group contains three nested Object Policy Groups, as shown below.

DataPowerObjectPolicyGroup.png

The DataPower_Infrastructure_Basic Object Policy Group contains the Object Policies to handle the device Itself and the network interfaces.

The DataPower_Services_Basic Object Policy Group contains the Object Policies to handle the five DataPower Service types (WebService Gateways, Multi-Protocol Gateways, Web Service Firewalls, XML Firewalls, and XSL Proxies) as well as Message Count and Message Duration Monitors.

Finally, the DataPower_Common_Basic Object Policy Group contains the Object Policies to handle Stylesheets, XML Managers, and XML Names objects that are common resources used by services.

Each of the Object Policies under the nested Object policy Group has one Policy Action (DataPower_ObjectType_UseHistoryTemplate_SAMPLE) that registers historical data collection for the key properties of each object.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*