Using the MultiStep Probe On WebSphere Datapower

The multistep probe provides step-by-step debugging and state information about the documents that flow through a service. The multistep probe displays the contents of contexts and displays the value of variables at each processing step of a processing rule. A processing rule might contain one or more processing steps. The multistep probe can be an invaluable tool during the development phase of service

applications.

The multistep probe is available for the following DataPower services:

•  XSL Co-Processor
•  XSL Proxy
•  XML Firewall
•  Web Application Firewall
•  Web Service Proxy
•  Multi-Protocol Gateway

Enabling the multistep probe

The multistep probe can be enabled in one of the following ways:v From the object configuration screens by using the probe buttons. This method is available independent of access method. v From the Probe Setting configuration screens. This method is available when the service is accessed from the Objects menu. If accessed through the Services menu, these configuration screens are not available. The probe must be enabled before transactions can be captured and analyzed.

CAUTION:

Do not leave the multistep probe in the enabled state for production conditions.Disable the probe before moving the configuration into production.Restarting the appliance disables the multistep probe.Enabling with probe buttons

To enable the multistep probe using probe buttons, use the following procedure:

1. Click Show Probe on the configuration page of the service. Clicking ShowProbe displays the Transaction List in a new browser window. If the probe is not enabled, the Transaction List shows “no transaction recorded”.

2. Click Enable Probe to enable the probe.Enabling through object configurationTo enable the multistep probe through service configuration, use the following

procedure:

1. Click the Probe Settings tab to enable the multistep probe.

2. After the multistep probe is enabled, click the Probe Triggers tab set triggers.

Until the probe is enabled, no configuration property is available on this configuration screen.