Difference between 'Discovery CI Pattern' and 'Discovery Process classifiers '

[sayub]

I am running discovery (regular discovery not Service mapping) and i am getting some warning errors such as

when i click to see the details it shows its missing mandatory attributes

i checked the pattern in the pattern designer and it shows that the mandatory attribute is the version

I have a few questions:

1- What is the best way to check why the version for this tomcat CI is not populated while the other ones did? I went to the Window Server that is running this tomcat and it actually shows the tomcat 8 in BSM map..

2- I checked the windows CI that has this tomcat running and it shows there is tomcat8 running on it. Now i have a process classifier for tomcat which is OOB and has conditions like qualify as tomcat if the name contains tomcat; so i am just not sure why the version for this tomcat failed in discovery pattern while the other were discovered fine.

3- Whats is the difference between discovery CI pattern and discovery process classifier? should i create a process classifier for tomcat8 or do i need to create a pattern? and if i need to create a pattern how can i make sure that it captures the version which failed this time.

4- i am under the impression that discovery patterns need to be created for Service mapping where as for regular discovery (not service mapping) we need to create process classifiers, is that a valid assumption ? Can i run regular discovery to not use discovery patterns and only the process classifiers?

Thanks

[danjohnson · Accepted solution]

For points 1. and 2. The message is basically just saying that the $version variable is empty, so I would start by going into the pattern and enabling debug mode - point debug mode to your windows CI with tomcat on it and the pattern should then give you realtime variable values which will allow you to start troubleshooting why it isn't populating a value.

3. Process classifiers were the tool that we used to identify a specific process as an Application CI. Discovery Patterns are a newer way of extracting all kinds of information from an underlying CI. In the past, you would have had to use a process classifier. Now you could use either process classifiers or patterns for that information. To make sure it captures the version, you need to understand the app. Where is it storing the version info, what command can you use to extract it. Use that command, and send the output to a variable that has the same name as a field in the CI class, and it will populate the field with the output.

4. While it is correct that ServiceMapping definitely needs patterns to work, Horizontal Discovery doesn't necessarily need them (although there are quite a few now that can operate ootb). You can just use process classifiers if you were more familiar with them instead. Personally, I prefer working with patterns.

[sravanpinnamane]

Hello Ayub,

Check with your App Owner/SME.Try to debug Version Step in a tomcat pattern.

If the App owner/SME has done any custom configuration for tomcat server installation, ask for the version path file location.

Add new steps in a tomcat pattern.

There are new steps added for Windows OS in Tomcat Pattern,Jakarta Version. When i was worked on Geneva it was not available.

Thanks,

Sravan