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 Oracle Apps Adapter services or notifications should identify webMethods Oracle Applications Adapter package ( WmOAAdapter ) as a package dependency because they require services in the WmOAAdapter to load first. Use the following guidelines:
Set package dependencies from the adapter service or notification package to the package containing the connection if you configure a connection in one package and the adapter services or notifications in another package. That is, the package that contains the connection should load before the adapter service or notification package.
When you set this package dependency, it ensures that if you reload the connection package, the adapter service or notification package will automatically reload. However, if someone disables the connection package and then re-enables it, the adapter service or notification package will not reload automatically. In this scenario, you must reload the adapter or notification package.
If both the connection and adapter services or notifications are in the same package, then no dependencies need to be set.
In general, packages containing connections should have a dependency set to the adapter package itself. That is, the adapter service or notification package should depend on the adapter connection package, which should depend on the adapter package. Similarly, if the adapter services or notifications 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.