Ask about esb?

[CommunityUser]

Good day all,

Did anybody having good experiences while populating any appdynamics agent into ultraesb environment?

Does the agent compatible with ultraesb, or perhaps it will need some custom patch for it to solve the issues?

Thank you

[CommunityUser]

Right now it looks like we're monitoring a couple ESBs with extensions such as

Mule

http://community.appdynamics.com/t5/eXchange-Community-AppDynamics/Mule-ESB-Monitoring-Extension/idi...

Adeptia:

http://community.appdynamics.com/t5/eXchange-Community-AppDynamics/Adeptia-ESB-Monitoring-Extension/...

If you think that sort of thing might be helpful, you can submit a development request from the link below. Our best ideas come from our customers 🙂

https://singularity.jira.com/secure/CreateIssue!default.jspa

[Arun_Dasetty]

Hi,

Adding to Bradley comments above where extension helps to monitor using machine agent as customer metrics, we see you would like to monitor ultraesb itself and we see UltraESB is a simple process as it is a standalone Java application, correct me if my understanding is wrong, using AppServerAgent java agent we should be able to monitor jvm though you might not see ootb business transaction detection you should be able to define POJO custom rules under Configure -> Instrumentation -> Transaction detection -> custom match rules section and you should be able to see BTs and load in addition to JVM heap data, Hope that informaiton helps.

command sample to start agent for standalone java program:

cmd> java -javaagent:"<agent_dir>/javaagent.jar" -jar ultraesb.jar UltraEsbClassWithMainMethod <jvm args if any>

refer docs https://docs.appdynamics.com/display/PRO40/Install+the+Java+Agent

https://docs.appdynamics.com/display/PRO40/POJO+Entry+Points

Regards,

Arun

[CommunityUser]

Yes, althought the core product is marketed almost exclusively for monitoring app servers, it actually acts on the JVM and so as Arun points out, can be used to monitor just about any java process. More than a few clients do things like this (monitoring java apps not tied to app servers), but it's not well-advertised because it's not the main use case. So just keep that in mind when reading the docs.

[CommunityUser]

...and finally, one other issue that may come up is that when you're configuring custom entry points for apps that were not developed in-house -it's very helpful to know something about the app's code so that you can specify particular classes and methods as the Business Transactions' entry points.

Different vendors and developers will provide different levels of cooperation on providing that sort of info. Here's the menu for a POJO custom entry point to show what data you may have to have available: