AppDynamics Application Intelligence Platform

3.8.x Documentation

PDFs

Videos

Release Notes

Mule ESB 3.4 and previous releases are supported.

Mule ESB (Enterprise Service Bus) is an integration platform with many different connectors for integrating applications and supporting service oriented architectures. By default, AppDynamics detects the Mule ESB endpoint. However, in some situations, you may need to create a servlet exclude rule.

The App Agent for Java supports Mule ESB as follows:

Tracks Business Transactions to Remote Services and Tiers

No configuration required: The App Agent for Java detects business application calls through Mule ESB service connections to remote services and tiers. Mule ESB is automatically detected and continuing tiers are recognized. Asynchronous correlation is enabled by default. Business transaction naming is dependent on business transaction discovery.

Detects incoming HTTP  to the Mule ESB HTTP endpoint when it performs as a servlet

No configuration required: If your application takes the output of the Mule ESB HTTP endpoint and makes it perform like a servlet, the App Agent for Java detects incoming HTTP to the Mule HTTP Endpoint as a servlet. 

Detects SOAP or RESTful operations beyond the Mule ESB HTTP Endpoint

Servlet Exclude Rule Required: Mule ESB can function as a transport connector.In some cases the Mule ESB HTTP endpoint is an entry point to another application component. For example, the Mule ESB HTTP endpoint can be an entry point to an application that ends with a CXF SOAP service or a JAX-RS RESTful endpoint further in the tier. By default, the App Agent for Java treats the Mule ESB HTTP output as a servlet, an endpoint in the application and doesn't see the the CXF SOAP or JAX-RS RESTful operation further in the flow. In order to see the SOAP or RESTful operation, we need to exclude the Mule ESB HTTP servlet.

For example, we have an application using Mule ESB services at this URI: http://muleapp1:8080/

            There are some HTTP response servlets on: http://muleapp1:8080/httpResponseService/

                                 and there is a CXF SOAP endpoint on: http://muleapp1:8080/webservicenedpoint/

To see the CXF SOAP endpoint, we need to create a servlet exclude rule on uri:http://muleapp1:8080/webservicenedpoint/

We do not need to create a servlet exclude rule when the Mule ESB HTTP endpoint continues to another tier or for exit points within Mule ESB.

See also, Mule ESB Startup Settings.

  • No labels