Hi all,
currently Application Dependency Mapping (ADM) only maps Applications during discovery based on TCP connections and running processes.
Unfortunately it looks like OOTB this is not working if you have cannot use discovery. Also with ACC running on your server it´s not working (although we have TCP connections and running processes discovered through ACC).
Luckily there is a very easy way to fix this, which I want to share with you.
The Integration Commons for CMDB provides the whole mapping functionality and the mapping can be triggered per computer CI.
// Initialize the Mapping Helper
var oUtil = new sn_cmdb_int_util.GlobalApplicationDependencyMappingHelper();
// SysID of a computer CI
oUtil.initializeBySysId("e1ab79879734b550f490fe200153afad");
// Map the dependencies based on the tcp connections, running processes and created applications
oUtil.mapCi();So the only thing you have to think of is how to integrate this into your platform. A few examples could be:
- Run a scheduled job for the servers and trigger the mapping (could be time and resource intensive)
- Integrate this into the ACC Collection (your starting point would be AgentDiscoveryHandlerADMHelper. addConnectionsAndRelationshipsToCMDB) but this works only for the "simple" discovery
- Create a BR on the agent which triggers the mapping after "Host data collection" changes to collected
The end result can look like this
Note
There is currently a bug in Integration Commons for CMDB (V. 2.10.0) which you have to fix. In Script Include GlobalApplicationDependencyMappingHelper line 36 you have to change LOG_ID to this.LOG_ID
if (!gs.nil(from_appl) && !gs.nil(to_appl)) {
gs.debug(this.LOG_ID + " In globalApplicationDependencyMappingHelper: Need to relate appl " + from_appl + " to appl " + to_appl + " on port " + matches[i].to.port);
this.createOrUpdateRel(from_appl, to_appl, this.relType, matches[i].to.port);
}
