We have some issues in creation of the link between the Business Application and Node (or/and Running Software). In the beginning we manually created the link from the Business Application and the Running Software (like Business Application A – Jboss A).
Having manually created links is no good but I guess the link between Business Application and Node (or/and Running Software) has to be manual in someway. Or if you have some attribute on the node (running software) that tells you which Business Application it belongs to. Or if you use some kind of integration with some other system that tells you that ServerA, ServerB, ServerC, RunningsSoftware1, RunningsSoftware2, RunningSoftware3 belongs to Business Application.
Do you have any ideas/knowledge how customers usually solve this relation?
Another big issue for us (and I guess so that we can have some use of impact rules) is the relations between Business Application and Business Application. We are running WebSphere MQ and almost all of our communication between systems are using this product to send and receive data. Unfortunately it is kind of a BLACK HOLE for us. We can see that Application A is talking with MQ but we can´t see that it is sending messages to Application B. We can just see that MQ is talking with Application B. I think the use of Impact Analysis is useful for us only when we can see which other Business Application that are impacted when we are doing service on Business Application A.
In the beginning we sat down with people responsible for Business Application A and they told us which other Business Application they used or was used of (which way the communication went). So we manually created relations between business Application and business Application. But this is NO good either. At first the responsible for every Business Application had a login to uCMDB and had the rights to maintain this by themselves, but since uCMDB has so weak audit logs they were not allowed to login to the system (and I really don´t think they logged in anyway) and we are not informed when there are changes in this relations.
Do you have any ideas/knowledge how customers usually try to solve this?
We have struggled with uCMDB a couple of years now and have hard times to defend its existence. Haven´t saved us any money yet I´m afraid…
Which are the customers main use of uCMDB and Configuration Manager? Can anyone give us some new ideas?
Sure, we have had some value from it occasionally but if we are talking value for money we are loosing!
(reports on servers not patched, how many jboss do we have - levels..., servers listening on strange ports...
Wbr / Fredrik