Package Dependency Requirements and Guidelines

Dependency requirements and guidelines for user-defined packages are as follows. For instructions for setting package dependencies, see the webMethods Service Development Help for your release.

By default, the WmSiebelAdapter package has a dependency on the WmART and the WmWin32 packages. Do not change this dependency.

A user-defined package must have a dependency on the WmSiebelAdapter package.

These dependencies ensure that at startup Integration Server automatically loads or reloads all packages in the proper order: the WmART package first, the adapter package next, and the user-defined package(s) last. The WmART and the WmWin32 packages are automatically installed when you install the Integration Server. You do not need to manually reload the WmART or the WmWin32 packages.

If the connections and adapter services of an adapter are defined in different packages, then:

A package that contains the connection(s) must have a dependency on the adapter package.

Packages that contain adapter services must depend on their associated connection 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 will reload automatically.

Integration Server will not allow you to 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 a Package.

The Integration Server will allow you to 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 the adapter package before you disable the adapter package. For information about disabling packages, see Disabling a Package.

You can name connections and adapter services the same name provided that they are in different folders and packages.

If user-defined packages are properly configured with a dependency on the adapter package, at startup Integration Server automatically loads or reloads all packages in the proper order as follows: