Logical Connections and Runtime Processes

Resolving The Problem

Logical connections and run time processes are created to represent the runtime state information at a particular point in time and, while they are used to create objects that are part of the configuration,
they are objects that TADDM utilizes to create higher level relationships.

Logical connections are used to represent connections between runtime processes and the information contained in the logical connection may be used to create IpDependency and
TransactionalDependency relationships if both the source and target of the dependency are
present in the database.

It is frequently the case, particularly in larger environments using ECMDB, that one end of the logical connection is not discovered because it resides in another domain. Until all the information is present at the ECMDB level the correct dependency cannot be generated from the logical connection.

So it is considered a normal situation to have only one end of a logical connection present in the database.

The connection information is contained in the ApplicationServer Runtime tab of the details display for both the source and target objects.
Deleting one end of the connection still leaves the other end with a potential (and missing) connection which needs to be displayed which requires that the logical connection continue to exist. As the
runtime processes related to the logical connection are cleaned up, the logical connections are also cleaned up as part of the TopologyBuilder phase which runs after discovery.

Instances of the class LogicalConnection should not be used outside of TADDM internal processing mechanisms and are not represented as CIs. As TADDM evolves the treatment of logical connections may change and any reports based on logical connections will need to be modified to work with the current treatment.