Configuring dependencies between resource groups

Business configurations that use multi-tiered applications can utilize parent/child dependent resource groups. For example, the back end database must be online before the application controller. In this case, if the database goes down and is moved to a different node, the resource group containing the application controller must be brought down and back up on any node in the cluster.

Business configurations that require different applications to run on the same node, or on different nodes can use location dependency runtime policies. See Examples of location dependency and resource group behavior for more information.

The dependencies that you configure are:

• Explicitly specified using the SMIT interface
• Established cluster-wide, not just on the local node
• Guaranteed to occur in the cluster, that is, they are not affected by the current cluster conditions.

You can configure six types of dependencies between resource groups:

• Parent/child dependency
• Start After dependency
• Stop After dependency
• Online On Same Node Location dependency
• Online On Different Nodes Location dependency
• Online On Same Site Location dependency