Package Dependency Requirements and Guidelines

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

A user-defined package must have a dependency on its associated adapter package, WmPeopleSoftAdapter.

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

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

A package that contains the connections must depend 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.

The 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 Packages.

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 Packages.

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