1

I am trying to find a tool which can efficiently help me to map and identify relationships and data flow between applications.

I am not very familiar with UCMDB, but does it help for capturing application relationships?

Any advice would be very helpful.

Thank you

JJunior
  • 2,831
  • 16
  • 56
  • 66

2 Answers2

4

uCMDB/DDMa is exactly that, an automated IT infrastructure inventory and mapping solution which helps you identify components like servers and applications as well as draw relationships between them based on port connections and IP traffic. It utilizes various standard protocols to identify these components, like Telnet/SSH and SNMP, uses WMI, performs SQL on databases, reads configuration files et cetera. Discovery is performed by a probe server, which sends results to a server for processing and reconciliation, resulting in relationships between components. The end result can then be called up in views or models, showing the components in relation to eachother. One can also integrate external datasources with uCMDB and integrate uCMDB with other tooling like BSM and SM.

Rutger
  • 79
  • 1
  • 3
  • hi Thank you for the details. Are you aware of any other tools which would help me achieve similar results? – JJunior Oct 05 '11 at 15:18
  • Hi, yes of course. There's ServiceNow, a cloud based ITSM solution. – Rutger Oct 09 '11 at 10:39
  • 2
    The problem with this is that autodiscovery can only discover what is "discoverable", which implies post-deployment Configuration Items (CIs). Autodiscovery cannot discovery logical CIs, like Application Names, Capabilities, People, Organizations, Cost Centers, etc., which are important for adding context. Also, autodiscovery cannot discovery pre-deploymed CIs, such as computers that are not sitting on the network (e.g. offline laptops). Therefore, while UCMDB captures lots of post-deployed relationships, it's difficult to use it for logical and/or predeployed relationships. – Information Technology Mar 31 '16 at 22:03
2

beside the correct answer from Rutger we have to consider some specific topics once we run discovery ( eg. UCMDB ). HP is calling its Discovery part "UD" ( Universal discovery ). UD is now the merge from DDMi ( Inventory Discovery ) and DDMa ( Application Discovery ). It´s a UCMDB ( like RTSM eg. ( also HO and also a UCMDB ) ). In enterprise solutions we Use UD for the Discovery part and THE UCMDB to collect CMS data. UCMDB in this sense work as a Data-Provider for other Target-Systems like Business-Monitoring, Reporting etc.

RelationShips between CI´s:

here you have to consider the different methods of Discovery: Agent-Based ( ex. DDMi ) AND Agent-Less ( ex. DDMa )! ( both available IN UD )

the agent based dicovery is more or less used to collect technical data like CPU, OS, Installed SW, Memory etc. The agent less part is used to collect data like Running SW, DB etc. It is necessary to get the information about the Intra-Communication Between the CI´s. We also call This APPLICATION-Landscape-Discovery. Instead of an agent you have to give credentials (" the more "rights" you give - The more deep results you earn!")

Combination of both Methods is possible in UD ( UCMDB )

An alternative product is:

IBM Tad4D ( agent based discovery ) IBM TADDM ( agent less discovery )

kina
  • 41
  • 6