Environment Manager
This page refers to an older version of the product.
View the current version of the User Help.
Configuration Dependencies
Dependencies can be created between layers and between the host and another layer which can affect how Configuration Layering works. Nodes, reusable conditions and message library items, from one layer can be referenced in another layer. Nodes may not be able to be deleted or rolled back where a dependency has been created between layers due to shared usage of an item.
In this section:
- Child Node Dependency
- Reusable Node Dependency
- Message Library Dependency
- Reusable Condition Dependency
Child Node Dependency
If a node is added to a layered configuration as a child of a node in a layer, a dependency is created between the layer and the host.
In the example below, the Node L1 is part of a layer that has been added to the host. Node H2 has been added to the layered configuration as a child of Node L1. The layer cannot be removed from the configuration because the host is dependent upon it containing the new node.
The layer cannot be removed from the configuration because the host is dependent upon it containing the new node.
Reusable Node Dependency
If a reusable node from a layer is referenced in a layered configuration a dependency is created between the layer and the host. If a reusable node is referenced as a child node of a node of another layer, a dependency is created between the two layers.
In the example below, reusable nodes RNode L1 and RNode L2 are contained within layers which have been added to the host. RNode L2 is referenced in the Computer Startup trigger as part of the host and RNode L1 referenced as a child of the Node L1.
Layers containing the reusable nodes cannot be deleted because the reusable nodes are referenced in the host and in a node from another layer. To delete the layer containing the reusable nodes all references in the host and other layers must be removed.
Reusable Condition Dependency
If a reusable condition from a layer is referenced in a layered configuration a dependency is created between the layer and the host. A reusable condition added to a node in another layer creates a dependency between the layers.
In the example below, reusable condition RC 1 is part of a layer which has been added to the host. Node 1 is in the host configuration. The layer containing the reusable condition cannot be deleted because the reusable condition is referenced another configuration.
Message Library Dependency
If a message from a layer is used in a lockdown condition added to a layered configuration, a dependency is created between the layer and the host. The same is true if a message from one layer is used in a lockdown condition from a node in another layer.