SOAP-Based WebServices and APM

book

Article ID: 192064

calendar_today

Updated On:

Products

CA Application Performance Management SaaS

Issue/Introduction

Inserting the correlation ID in the SOAP header, as mentioned in the Broadcom documentation, poses a risk of SOAP messages getting rejected due to unexpected headers. While we continue testing configuration in our development environment, I was hoping to get answers to some queries:

  1. Does DX APM provide an alternate method to trace transactions across processes for SOAP based WebServices?
  2. Can RESTful webservices be monitored using the SOA Performance Management bundle provided by DX APM? We have not been able to achieve this even though the insertion/read of correlation ID is enabled for both HTTP and SOAP headers. If REST services are supported, please let us know if manual instrumentation would be needed to get this working.

Cause

NA

Environment

Release : SAAS

Component : APM Agents

Resolution

1. Does DX APM provide an alternate method to trace transactions across processes for SOAP based WebServices?

Answer: In place of using SOAP header for correlation ID insertion, DX APM agent can also switch to using HTTP header for correlation ID to help trace cross-process transactions.


2. Can RESTful webservices be monitored using the SOA Performance Management bundle provided by DX APM? We have not been able to achieve this even though the insertion/read of correlation ID is enabled for both HTTP and SOAP headers. If REST services are supported, please let us know if manual instrumentation would be needed to get this working

Answer: The DX APM agent bundles such as Spring Extension can be configured to monitor certain common RESTful web service implementation.  Please gather the autoprobe logs and agent logs, preferably in DEBUG mode, for review and possible customization if the implementation is not monitored by default.