The protocols listed here will be picked up by Precise out-of-the-box and shown as exit points. When cross-JVM or cross-CLR communication is involved, the transaction would be tracked end-to-end.

Asynchronous activities, calls, or threads are not supported for end-to-end correlation.

Exit points from Microsoft .NET

  • .NET Remoting
  • .NET Web Services

    The following WS client APIs are supported:

    • Proxy classes generated by wsdl.exe, which extend System.Web.Services.Protocols.SoapHttpClientProtocol (in System.Web.Services.dll)
    • Manually calling the WS using class System.Web.Services.Protocols.SoapHttpClientProtocol or System.Web.Services.Protocols.HttpSimpleClientProtocol
    • Calling System.Net.HttpWebRequest (in System.dll) directly

Exit points from Java

APISupported implementations
JDBCAll(1)
JAX-WSMetro, AXIS 2, CXF, Spring Web Services (HTTP only), and any custom implementation that is using either the javax.jws.WebService or javax.jws.WebMethod annotation.
JAX-RPCSupported for WebLogic 10.3+ using the Sun implementation.
RESTJAX-RS (Jersey), RESTEasy (HTTP only), Restlet (HTTP onlt), Spring RestTemplate (HTTP only)
RMIIIOP (WebLogic 9.2+, WebSphere), T3 (WebLogic 9.2+)
JCo (SAP RFC)JCo 2.x
WTC (WebLogic Tuxedo Collector)WebLogic 9.2+ calling Tuxedo 8.1+
Apache HTTP ClientApache Commons (HTTPClient 3.x), Apache HTTP Components (HTTPClients 4.x)
JMSSupported for synchronous send and receive operations.(2)
DFC (Documentum)All
NoSQL databasesCassandra, HBase(2)
OthersJetS3t (HTTP only), CICS JCA access(2)

Note

(1) When JDBC is wrapped using reflection (e.g. in iBatis), additional configuration may be needed.

(2) Requires configuration.

IDERA |  Products | Purchase | Support |  Community |  Resources |  About Us  | Legal
  • No labels