Adding Assets to an IS & TN Deployment Set

Deployer 10.7 | Deploying Assets from Source webMethods Runtimes | Adding Assets to an IS & TN Deployment Set

Adding Integration Server Administration Assets

Adding an Entire Package

Adding Package Components

Manually Adding Dependencies to a Package Component in an IS & TN Deployment Set

Adding Package Files

Setting Package Properties

Adding webMethods Files

Adding Trading Networks Assets

Excluding Common Assets

You can add the following types of user-created assets to an IS & TN deployment set:

Integration Server administrative assets such as ports, users, groups, and scheduled tasks, packages, and web service descriptors.

Integration Server packages.

webMethods files.

Trading Networks assets.

Your source and target Integration Servers might have assets in common, and you do not need to deploy them from one environment to another. You can improve Deployer performance by excluding these assets from deployment sets. For instructions, see Excluding Common Assets.

Integration Server introduces new assets from time to time and not all the assets can be deployed using runtime-based deployment. In a runtime-based deployment, Deployer may not be able to recognize new types of Integration Server assets. If a package contains such assets, Deployer displays those assets as unknown types and shows them as unresolved dependencies. While deploying, select Ignore to bypass dependency checking. Those assets cannot be selected individually for deployment. It is recommended to use repository-based deployment.