Package Dependencies

The Package Dependencies page displays the packages on which this package is dependent. For example, if a package needs the services in another package to load before it can load, you need to set up package dependencies. You might also want to identify package dependencies if a startup service for a package invokes a service in another package. The startup service cannot execute if the package containing the invoked service has not yet loaded.

Property	Description
Package	The name of the package you want webMethods Integration Server to load before the package selected in Package Navigator.
Version	The version number of the package you want loaded. More than one version of the same package might contain the services and elements that a dependent package needs Integration Server to load first. A dependency declared on a version is satisfied by a package with a version that is equal to or greater than the specified version. For example, to specify versions 3.0 or later of a package, type 3.0 for the version number. To specify versions 3.1 or later, type 3.1.0 for the version number. You can also use an asterisk () as a wildcard in the version number to indicate that any version number equal to or greater than the specified version will satisfy the package dependency. If any version of the package satisfies the package dependency, type .* as the version number.

Use this button...	To...
	Add a package dependency.
	Insert a blank row for a package dependency.
	Delete the selected package dependency.
	Edit the selected package dependency.