Setting Package Dependencies
You set package dependencies if a given package needs services in another package to load before it can load. For example, any packages you create for Remedy Adapter services should identify the Remedy Adapter package (WmRemedyAdapter) as a package dependency because they require services in the WmRemedyAdapter to load first. Use the following guidelines:
If you store adapter connections in a different package than adapter services, be sure to:
Set the package dependencies of the package containing the adapter connections to depend on the WmRemedyAdapter package, and
Set the package dependencies of the adapter services package to depend on the package that contains the adapter connections. That is, the package that contains the connection should load before the adapter service package.
When you set this package dependency, it ensures that if someone disables the connection package and then re-enables it, the adapter services will reload correctly.
If both the connection and adapter services are in the same package, set the package dependencies of this package to have to depend on the WmRemedyAdapter package.
For more information about setting package dependencies, see the webMethods Service Development Help for your release.