Package Dependency Considerations for Namespace Node Packages
Following are dependency requirements and guidelines for namespace node packages:
A namespace node package must have a dependency on its associated adapter package, and the adapter package must have a dependency on the WmART package. For more information about setting package dependencies, see the
webMethods Service Development Help for your release.
Setting these dependencies ensures that at startup Integration Server automatically loads or reloads all packages in the proper order:
WmART package.
Adapter package.
Node package(s).
The WmART package is automatically installed when you install Integration Server. You must not manually reload the WmART package.
Keep connections for different adapters in separate packages so that you do not create interdependencies between adapters. If a package contains connections for two different adapters, and you reload one of the adapter packages, the connections for both adapters is reloaded automatically.
You cannot enable a package if it has a dependency on another package that is disabled. That is, before you can enable your package, you must enable all packages on which your package depends. For information about enabling packages, see
Enabling and Disabling Packages.
You can disable a package even if another package that is enabled has a dependency on it. Therefore, you must manually disable any user-defined packages that have a dependency on your adapter package before you disable the adapter package.
If the namespace nodes of an adapter are located in multiple packages, see
Package Dependency Considerations for
Namespace Nodes. For more information about setting package dependencies, see the
webMethods Service Development Help for your release.