Configuring Multi-Protocol Gateway

Complete these steps on each Multi-Protocol Gateway that you want to display in instance topologies.

Procedure

In the WebGUI, complete the following steps for each Multi-Protocol Gateway that you want to monitor.

  1. In the Configure Multi-Protocol Gateway page, click the name of the Multi-Protocol Gateway that you want to configure.
  2. On the Multi-Protocol Gateway Policy page, configure the policy. Click ….
  3. On the Configure Multi-Protocol Gateway Style Policy page, select an existing Client to Server rule, or click New Rule to create one.
    1. Drag a Transform to the timeline.
      Note:
      1. If a Client to Server rule already exists, add the transform node to it.
      2. If the Client to Server rule has an Authentication, Authorization, and Audit (AAA) node, ensure that the transform node that includes the DataPower agent xslt file precedes the AAA node.
    2. Double-click the Transform rule to edit it.
    3. In the Configure Transform with XSLT style sheet Action window, next to Transform File, select apm_req.xsl from the data store that you uploaded it to. For example, local:///

      If the file does not exist, click Upload to get it from the installed location.

      Tip: In addition to SOAP and REST traffic through the DataPower® appliance, if you want to configure a Client to Server rule to monitor the traffic between DataPower and WebSphere® MQ, apply the apm_req_MQ.xsl file instead of the apm_req.xsl file in this step.
    4. Click Done.
  4. Back on the Configure Multi-Protocol Gateway Style Policy page, select an existing Server to Client rule, or click New Rule to create one.
    1. Drag a Transform to the timeline.
    2. Double-click the Transform rule to edit it.
    3. In the Configure Transform with XSLT style sheet Action window, next to Transform File, select apm_rsp.xsl from the data store that you uploaded it to. For example, local:///

      If the file does not exist, click Upload to get it from the installed location.

      Tip: In addition to SOAP and REST traffic through the DataPower appliance, if you want to configure a Server to Client rule to monitor the traffic between DataPower and WebSphere MQ, apply the apm_rsp_MQ.xsl file instead of the apm_rsp.xsl file in this step.
    4. Click Done.
  5. Back on the Configure Multi-Protocol Gateway Style Policy page, select an existing Error rule, or click New Rule to create one.
    1. Drag a Transform to the timeline.
    2. Double-click the Transform rule to edit it.
    3. In the Configure Transform with XSLT style sheet Action window, next to Transform File, select apm_error.xsl from the data store that you uploaded it to. For example, local:///

      If the file does not exist, click Upload to get it from the installed location.

      Tip: In addition to SOAP and REST traffic through the DataPower appliance, if you want to configure an error rule to monitor the traffic between DataPower and WebSphere MQ, apply the apm_error_mq.xsl file instead of the apm_error.xsl file in this step.
    4. Click Done.
  6. Back on the Configure Multi-Protocol Gateway Style Policy page, on the Advanced tab, set the Monitor via Web Services Management Agent to on, and click Apply.
  7. Click Apply.

What to do next

In some cases, adding transforms for Transaction Tracking may result in DataPower changing the value of HTTP Content-Type headers. You may see web pages with images that do not load, or binary files being rendered as garbled HTML text.

The behavior of DataPower changes when comparing a rule with no XSL transforms to a rule with one or more XSL transforms. If the service handles MIME, MTOM, XOP or other encoded messages, this behavior may be desired, otherwise modify your DataPower configuration to prevent the behavior.

To prevent DataPower from modifying the HTTP Content-Type header, set the variable in each affected rule (var://service/mpgw/proxy-content-type):

  1. Drag an Advanced object to the rule.
  2. Double click the Advanced object to edit it.
  3. Select Set Variable and click Next.
  4. Enter the Variable Name service/mpgw/proxy-content-type and Variable Value 1 and click Done.
  5. Apply the policy and service configuration changes.
  6. Repeat steps 1-5 for each affected rule.