Dependency Mapping Flow

This section provides a brief overview of the basic flow that occurs during dependency mapping:

  1. The first service connection point (SCP) is generated from the service entry URL of the business element.
  2. Each service connection point triggers a new discovery job against the host and listening port if their owner has direct or indirect consumer-provider relationship with the business element in the scope.
  3. A running software instance and its deployable components are discovered. Their SCPs are also generated.

    At this step, the process first uses configuration signatures to discover the running software, and then uses TCP connection if configuration signatures are unsuccessful. The process no longer uses TCP connection if configuration signatures succeed.

  4. The dependency job queries all discovered running software CIs against the IP address, listening port, and service context in the SCPs generated in the previous step.

    If one’s (provider) IP address, listening port, and service context match the corresponding data in the other’s (consumer) SCP, the consumer-provider relationship is created between the two running software CIs (or deployable components).

    Note The dependency mapping process also creates the containment relationship between business element and its immediate next-hop.

  5. Repeat from step 2 to discover the next hop.

The following diagram illustrates the dependency mapping flow and shows how the topology map is updated during the process.