User-Defined Package Dependency Requirements and Guidelines
This section contains a list of dependency requirements and guidelines for user-defined packages. For instructions for setting package dependencies, see webMethods Service Development Help.
When working with user-defined packages, keep in mind the following:
![*](chapterTOC_bullet.png)
When you create user-defined packages, use the package management functionality provided in
Software AG Designer and set the user-defined packages to have a dependency on the adapter package. That way, when the adapter package loads or reloads, the user-defined packages load automatically.
![*](chapterTOC_bullet.png)
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.
![*](chapterTOC_bullet.png)
If the connections and adapter services of an adapter are defined in different packages:
![*](chapterTOC_bullet.png)
A package that contains the connections must have a dependency on the adapter package.
![*](chapterTOC_bullet.png)
Packages that contain adapter services must have a dependency on their associated connection package.
Integration Server will not allow you to enable a package if it has a dependency on another package that is disabled. Before you can enable your package, you must enable all packages on which your package depends.
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.
![*](chapterTOC_bullet.png)
You can give connections, adapter services, and notifications the same name provided that they are in different folders and packages.