Showing results for 
Show  only  | Search instead for 
Did you mean: 

Problems monitoring adeptia with appdynamics


Hi All,


In the environment of our customer, we are trying to monitor the complete set of applications.
They have several, each with different functions, but we are having trouble to monitor all transactions on the Enterprise Service Bus (ESB).
That is a major problem for us: all important traffic is flowing through the enterprise service bus but we are missing 95% of the transactions in the transaction overview.

To eloborate a little more on the application itself first: Adeptia is an enterprise sevice bus application translating messages where needed and routing them to the proper endpoint.
It is comprised of two Java Virtual Machines, which communicate via RMI with eachother. One is the kernel component which does the translating and routing and one is the webrunner, on which the webservices are running (entrypoints and the webinterface for developers and operations).Both have a (working) Java agent attach to them.


A typical use case would be: A message arrives from the gateway application over a service (the gateway (CA API Gateway) is also monitored with an agent) and sent to adeptia via a webserivce. Some translation would be done and subsequently the message would be sent to the backend (of which we also monitor most with appdynamics).

As said we are monitoring both the JVM's of adeptia and we have succesfull connection between the agents and the controller. We are seeing plenty of transactions mostly javabeans ans some traffic of the webfrontend of adeptia. However we are missing most the webservice that run on adeptia and provide entrypoints for the service. Also we are missing most of the endpoins from which adeptia sends the messages to other applications of which some are also monitored. We have tried to make some custom rule detection, but none seem to help in finding the missing transactions. What can we do to make these transactions visible?





Adeptia is not a product that we have built out of the box configuration for, so you will need to configure entry points (method(s) where work starts within Adaptia) and exit points (method(s) where work is delegated downstream) in order to be able to visualise the missing flows.


You may find the uninstrumented code detection feature useful for this, provided the exit points are instrumented.  If not, you will need to take some thread dumps to determine which methods need to be instrumented.


Our customer success team will be able to assist with this if you get stuck.


Warm regards,




Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.

Hi Peter,


Thank you for your reply. We have already tried some different settings for custom transaction detection and entry/exit point settings for adeptia. I wanted to provide a little more information, perhaps someone can provide as with a little insight into what we might be doing wrong. 


The use case we are currently investigating is this:

 A Case management system (monitored with appdynamics) is sending soap requests to adeptia (the broker, also monitored with appdynamics). The entrypoint is adeptia looks like this: /wsx/services/BeantwoordVraag_GMN_WSPROV_StUF_BG_0310_beantwoordVraag_GV_ABG


interestingly enough: from the dashboard of our case management system we can see the endpoint of the broker but only as HTTP endpoint. In fact we would expect to see the broker application as it is also monitored in appdynamics and the transactions do not stop in the broker. in fact the continue to the data warehouse application, where some data is retrieved and returned back via the broker to the case management system. The datawarehouse application is also monitored with appdynamics. We are also missing the endpoint for the datawarehouse in adeptia.


I added some screenshots of the set-up:

1 Business transaction detection rule for a servlet 

2 business transaction detection rule for a web service

3 exit point now: shopwing the HTTP endpoint rather than the adeptia application

4 transactions in adeptia

5 the dashboard of adeptia


Can someone explain if we are setting the transaction detection up correctly? And does it have anything to do with the fact we are using soap services?





were you able to solve your problem?