Relationship options settings
Specify relationship options for deployable or composition units in an asset deployed as part of a business-level application. Specifying a relationship declares a dependency relationship that a deployable unit or composition unit has on another asset deployed as a shared library in the same business-level application.
From the admin console, click...
Applications > Application Types > Business-level applications > application_name > deployed_asset_name > Relationship options. This help also pertains to wizard pages that are shown when we add multiple deployable or composition unit assets to a business-level application. These pages are shown for the Define relationship with existing composition units and Options for creating new composition units to satisfy asset relationships wizard steps.
A business-level application consists of composition units. When we add an asset to a business-level application, the product creates a composition unit for the asset. The composition unit name can be different from the name of the asset being deployed. The list of deployed assets shown for a business-level application consists of the composition unit names for the deployed assets. The relationships defined in this page are composition unit relationships. The deployable units listed for a composition unit are those we chose from the associated asset when adding the asset. Composition unit relationships are expressed as deployable unit dependencies on other composition units belonging to the same business-level application. Only a composition unit for an asset deployed as a shared library can be specified as a dependency. We can map each deployable unit to a target independently from the others. Modifying relationships in this page only affects the composition unit, not the associated asset.
To specify relationship options, select a deployable unit and click a button.
Button Resulting action Set Relationships Display a page through which we can add or change relationships for the deployable unit. Specify a relationship if a deployable unit depends on another asset deployed as a shared library in order to run. This button is on the Set relationship options page.
Enable Match Targets If the deployable unit has a dependency relationship defined, click Enable Match Targets to map the related deployed assets to the same deployment targets as the dependent deployable unit. Disable Match Targets If the deployable unit has a dependency relationship defined, click Disable Match Targets if the related deployed assets do not need to be deployed to the same targets as the deployable unit.
Deployable unit name or composition unit name
Name of the deployable unit or the composition unit of the selected deployed asset.
Relationship
Composition unit names for all relationships defined for the associated deployable unit.
This setting is on the Set relationship options page.
By default, a deployable unit has no relationships. To add or change related composition units, do the following:
- Select the deployable unit.
- Click Set Relationships.
- Select the composition units that the deployable unit requires by moving them from the Available list to the Selected list.
- Click OK.
Match targets
Indicates the match targets value selected for the associated deployable unit. Default is true.
A match targets value of true maps the composition units listed under Relationship to the same deployment targets as the associated deployable unit. Typically, deploy related composition units to the same targets as the dependent deployable unit in order for the deployable unit to run.
A false value indicates that the related composition unit can map to deployment targets which are different from the deployment targets of the deployable unit.
To set the value to true, select the deployable unit and click Enable Match Targets. To set the value to false, select the deployable unit and click Disable Match Targets. To set this value, the deployable unit must have a related composition unit.
If we have multiple deployable units and the security configuration supports multiple domains, the deployable units must be in the same security domain.
Related:
Business-level applications Create business-level applications with the console Update business-level applications Business-level application collection