Setting Package Dependencies
If a package requires services in another package, the other package must load before the dependent package can load. Set package dependencies to ensure packages are loaded in the correct order. For example, any packages you create for Adapter for Salesforce services should identify the WmSalesforceAdapter package as a package dependency because they require services in the WmSalesforceAdapter to load first. Use the following guidelines:
Set package dependencies from the adapter service package to the package containing the connection if you configure a connection in one package and the adapter services in another package. 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 this package to have a dependency on the WmSalesforceAdapter package.
In general, packages containing connections should have a dependency set to the adapter package itself. That is, the adapter service package should depend on the adapter connection package, which should depend on the adapter package. Similarly, if the adapter services are in the same package as the connections, the only dependency that you need to set is between the adapter connection package and the adapter package.
For more information about setting package dependencies, see the webMethods Service Development Help for your release.