To ensure that there is no disruption of in-flight tasks, it is important that you set the package dependencies correctly. During hot deployment of packages, Integration Server employs the block and wait approach on all assets in the packages that are being deployed as well as all its identified dependents. If you do not set the dependencies, Integration Server might go ahead with the invocation of an asset. If the asset is being upgraded at that time, the invocation could fail with an error.

For example, if you have not explicitly specified “FinanceUtil” as a dependent package of the “Finance” package, Integration Server will not wait for the completion of the execution of an asset in “FinanceUtil” package before deploying the “Finance” package. This could result in the hot deployment of the “Finance” package failing. Integration Server will wait for the completion of the execution of an asset in “FinanceUtil” package before hot deploying the “Finance” package only if you explicitly specify “FinanceUtil” as a dependent package of the “Finance” package. For more information about package dependencies, see webMethods Service Development Help.