Define application without using DAD
Calling all authoring gurus!
We monitor alot of custom applications in our SCOM-environment and as most of the apps don’t have the complexity needed only a few of them modelled using the distributed application designer (DAD). Apart from that we have a internally developed web portal which funtion as a CMDB, Documentation system, knowledge base and a customer portal.
This internal web solution/portal are querying SCOM (and other software) for server status etc. What we now want to do is to display alerts and status for applications. For now all application components are put in to groups, but there are alot of groups and only a few of them are “applications”. Using a naming context for the groups which in fact are applications is’nt exactly water tight and poeople tend to do wrong things. Is there any other way we can define objects as an application other than using DAD or a strict naming context for groups?
BR
Martin Ehrnst
You can add a property to all of your server, this property can contain your application details. The property can be filled automatically by a discovery.
Then create groups in a sealed MP and add the server with the specific property dynamic to the group.
Because the MP is sealed nobody can add server manually.
Answer this question
To reply or comment, use the 'Comment' link on the relevant answer or question.