Command Central 10.11 | Deploying Command Central Assets to Integration Cloud (Deprecated) | How Platform Manager Deploys Assets with Dependencies
 
How Platform Manager Deploys Assets with Dependencies
When deploying assets from an asset repository, Platform Manager determines the order in which to install the assets on the target environment based on the type of asset (configuration or product) and the asset dependencies. Platform Manager manages the dependencies between assets at the time it deploys an asset on the target installation.
When deploying product assets and Command Central configuration assets, Platform Manager always installs the configuration assets after it installs the product assets. For example, when Platform Manager deploys "packageA" (product asset for Integration Server) and "COMMON-JDBC" (configuration asset for Integration Server), Platform Manager first installs "packageA" and then applies the "COMMON-JDBC" configuration.
Platform Manager installs the dependent assets before it installs the main asset. For example, when "assetA" depends on "assetB", Platform Manager installs "assetB" before it installs "assetA".
Platform Manager installs all assets included in the repository deploy changeset and compares the dependent assets that it is about to deploy with the dependent assets already installed on the target installation by name. If a dependent asset is already installed on the target installation and is not included in the deploy changeset, Platform Manager installs the main asset, but does not attempt to re-install the dependent asset.
Note that if you want to re-install a dependent asset that is already installed on the target environment, you must include the dependent asset in the changeset.