Cloud Application Integration (On-Premises) : Service Development : Managing Packages : About Package Dependencies : Identifying Package Dependencies
Identifying Package Dependencies
Keep the following in mind when creating package dependencies:
*When you identify a package dependency, you must indicate the version number of the package that needs to load first. For example, the “Finance” package might depend on version 2.0 of the “FinanceUtil” package. It is possible that the services and elements needed by a dependent package are contained in more than one version of the same package. For example, the “Finance” package might depend on version 2.0 or later of the “FinanceUtil” package.
*Make sure that you do not create circular package dependencies. For example, if you identify “FinanceUtil” as a dependent package for the “Finance” package, do not identify “Finance” as a dependent package for the “FinanceUtil” package. If you create circular package dependencies, neither package will load the next time you start the Integration Server.
*If you create new adapter services and adapter notifications, you should save them in packages that identify the webMethods AdapterName package as a package dependency.
*Only one version of a package can be installed at one time. If the available version of the package specified in the package dependency is not the correct version, Integration Server does not load the dependent package. Integration Server writes a dependency load error for the dependent package to the server log.
To identify a package dependency
1. In Package Navigator view, select the package for which you want to specify package dependencies.
2. Click File > Properties.
3. In Properties for PackageName dialog box, select Package Dependencies.
4. Click .
5. In the Add Dependent Package dialog box, enter the following information:
In this field...
Enter...
Package
The name of the package you want Integration Server to load prior to loading the package selected in the Package Navigator view. Type the name of the package in the Package field or click Browse to choose the dependent package.
Version
The version number of the package you specified in the Package field.
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.
6. Click OK.
7. Click OK in the Properties for PackageName dialog box.
Copyright © 2015- 2017 Software AG, Darmstadt, Germany. (Innovation Release)
Product LogoContact Support   |   Community   |   Feedback