ADDM is the utility that you should use for finding the applications!
But, you can only discover applications if you model them first. (Thats the 'thru logic' part).
ADDM wont tell you what your application is without you telling ADDM how to determine which of the discovered components are actually part of the application.
Best is to create some sort of questionnaire for the application owners to fill in.
The questionnaire should have questions like: On which servers is the application running? What tiers does the application consist of? What are the unique identifiers for these tiers? What environments and instances are there? How can one diferentiate between them?
Once you have this information you can start making the patterns that recognize and model the applications. This you can do with CAM if you already have all your components you need in ADDM and only need simple application models or, if you do not have all the components or need to make more complex models, you can create patterns by using the pattern templates that come with ADDM.
You say your applications can be found in certain directories? With patterns you can run commands and look in directories in order to find information for your application model, although looking for running processes would be better most of the times.
Sometimes you can already spot the outline of an application by looking at 'observed communications' in ADDM. If you are lucky you can see the DB server talking with the application server and the application server talking to the webserver. But you won't get applications by just scanning your servers (unless they are in the TKU, but those are just a few). I do not know a tool that does miracles like that.
Regarding reporting, you can extend the reports page in ADDM with you own reports.
This you do by creating an additional report-xml file. You can read all about it here:
Custom queries that you can save can be created with the Query Builder.
Once you have constructed a query and refreshed the output, you can save it by clicking on the save button on the right side of the screen.
More information about query builder can be found here:
What if you are looking to identify software and not a business application instance? In my example, the TKU is discovering some commercial off the shelf software, but we know there is additional software installed on the server and we are not able to see that software through the process list.
Hi Kip, ADDM discovers running software, not installed software. If you have software that isn't covered by the the TKU, you can create a pattern that generates a SoftwareInstance yourself. For this you can use one of the pattern templates that come with ADDM. (Or create one from scratch if you feel confident) If there's no DiscoveredProcess to trigger on, you can try to find another DDD (directly discovered data) node that can be used as a trigger. The pattern can trigger on a certain package for example. Kind regards, Edwin
Thank you for the response. In my situation we have a lot of COTS that is being classified as other when in chart format.
When I click on "other" it will provide a list of the software instances.
I can Then I click on the chart icon again and the list label as other will have a lower count of software instances.
I would like to understand why a have a large number of software instances listed as "other" yet I can click on "other" and get a list of software types. Is there a limitation on the number of software types that can be displayed? Thanks again for the support.
The charts simply limit the number of separate segments they will display. You have so many different products (which is normal, by the way) that it can't display a bar for each one. It displays the most common ones and groups all the others into "others". As you have seen, you can click through to the "others", and then chart them if you want to.
By the way, in ADDM terminology, these are not "applications". They are Software Instances, corresponding to individual running products. When ADDM refers to applications, it means high-level end-user business applications like "corporate messaging" and "CRM", for example, not the lower-level parts they are composed of.
Thank you for the response. It was very helpful.