How to identify methods.

Hi Jaydatt

WEll - in case you really dont get any information from the client I suggest the following

Approach 1 - Analyze Auto Sensor Data
dynaTrace automatically captures method execution times on PurePaths in case these methods impact performance. Now - if you click through the use case in the application I assume you will have actions such as "Search", "Login", "Report" or "Buy" which may take a while to execute. Please execute these transactions and then open the PurePath Dashlet. If you are the only one on the application all PurePaths you see should be the ones you just created. Now - look at these individual PurePaths and see if there is anything along that PurePaths that looks like what you need to define your Business Transactions. If it is a search you may want to watch out for methods that have search in their name. Once you found methods of interest on the PurePath you can simply right click on that method an either
a) create a Sensor Rule
b) create a Measure (this will automatically create a sensor for you)
c) create a business transaction (this will automatically create a measure and sensor for you)

Approach 2 - Analyze Loaded Methods
Go to your System Profile -> click on Sensors. Thats the place where you define custom Sensors so that you can pick up method arguements or return values of method calls. When you click on Browse you get to the Class Browser. Select your Agent Group (Tier) and then click on the little button next to the drop down. You will then see all loaded methods by that Agent Group. You can use the search feature in the Class Browser by start typing a name you look for. So - if it is a search feature you are interested in I would type "search". The Class Tree will then only show classes and methods that contain that name. Pick those that make sense.

Approach 3 - Analyze HTTP Parameters
Most often you create your BTs based on parameters that get passed from the WEb Frontent to your application. dynaTrace can capture these parameters through the Servlet and ASP.NET Sensor. Go to the Sensor Configuration for your Agent Group that represents your Frontend WEb Server Tier - click on Properties next to Servlet or ASP.NET. In there you can find a table where you can specify to capture all HTTP Parameters by specifying an asterisk in the name column. Once you close the System Profile Dialog dynaTrace will now capture all HTTP Parameters for every Web Requests. You can look at these parameters by opening the Details dialog of the Entry Point Node in your PurePaths. REMEMBER: capturing every parameter is great to get to know which parameters you can capture - but - once you figured out which parameters you really need you have to remove the "*" and specify the individual parameter names. This is a golden rule in dynaTrace - only capture what you really need

I also recommend checking out our webinars on Business Transaction Management: dynaLearn Webinar - Business Transaction Management - February 2, 2012

I hope this helps as a start