Deployer 10.5 | Deploying Assets from a Source Asset Repository | Resolving Dependencies | Resolving Dependencies Manually
 
Resolving Dependencies Manually
Perform the following procedure to resolve dependencies manually.
*To manually resolve dependencies
1. In the Unresolved Dependencies column for the deployment set, click Check.
Deployer shows all unresolved dependencies on the Unresolved Dependencies page as follows:
*The Referenced Asset Composites column lists the missing referenced assets.
*The Unset/Add/Ignore column offers the possible ways you can resolve the unresolved dependency.
*The Assets column shows the dependent assets.
2. Click one of the following options to set how Deployer should resolve each unresolved dependency. If you want to resolve all assets in a composite the same way, you can set the resolution at the composite level rather than at the level of the individual assets.
Option
Description
Unset
This is the default status. If you click Unset after you have made another selection (Add or Ignore) Deployer resets the assets to an unresolved status. Use this option if you set the assets in a composite to either Add or Ignore and want to start over.
Add
Adds the referenced asset to the deployment set. Use this option if the referenced asset does not exist on the target server and you want to deploy the referenced asset to it.
For Integration Server, CloudStreams, Trading Networks, or Broker (including JNDI) assets, you can choose to add the referenced asset or the entire composite that contains the referenced asset. Adding only the referenced asset to the deployment set instead of the entire composite is referred to as partial deployment.
Note:
For partial deployment of JNDI assets, export JMS destinations into one JNDI context at a time for partial deployment. Partial deployment of JMS destinations into multiple JNDI contexts is not supported.
Ignore
Ignores the asset. Use this option if you want to bypass dependency checking for the referenced asset so you can continue working.
Note:
Before deploying, make sure that either the referenced asset exists on the target server or that the referenced asset is unnecessary. If the referenced asset does not exist on the target server, Deployer might not deploy correctly; if it can deploy, the deployed assets will not run correctly.
3. Click Save.
*Deployer moves dependencies you resolved using the Add option to the Name column of the Deployer > Projects > project > Define page, in the left-hand pane. If you added only a subset of Integration Server, Trading Networks, CloudStreams, or Broker (including JNDI assets) assets rather than an entire composite (partial deployment), Deployer displays as a sibling of .
*Deployer adds dependencies you resolved using the Ignore option to the Name column of the Deployer > Projects > project > Define page, but the dependency remains listed on the Unresolved Dependencies page.