Integration Server 10.11 | Integration Server Administrator's Guide | Managing Packages | Copying Packages from One Server to Another | Version Checking
 
Version Checking
 
Who Can Subscribe?
Guidelines for Using Package Replication
When the administrator on the subscribing server installs the package, the subscribing server performs some version checking:
Target server verifies that
Target JVM Version
The target server is running the same or a later version of the JVM, as specified during release creation. If this requirement is not met, the subscribing server issues a warning and installs the package but does not activate it.
The target Integration Server must run in a version of the JVM whose major version is greater than or equal to the JVM version required by the package. For example, if the specified JVM version for a package release is 1.8.0_32, the installing Integration Server must be running in a JVM that is 1.8 or higher. If the major version of the Integration Server JVM is less than the JVM version required by the package, Integration Server installs but does not activate the package.
See Activating a Package for instructions on activating a package.
Package Version
For a full release
For a patch release
The version of the package on the target server is earlier than or the same as the package being installed. If this requirement is not met, package installation fails.
The version of the package on the target server exactly matches the version required by the release (as specified during release creation). If this requirement is not met, package installation fails.
For example, if you create a new release and specify that it contains Version 2.0 of the wmExample package, the wmExample package on the target system must be release 2.0 or earlier.
For example, if you create a new release that contains a patch for wmExample package version 2.0, and you specify that the target package must be version 2.0, package installation will fail if the target package is not version 2.0.
This restriction prevents you from inadvertently installing an old version of a package over a newer one.
This restriction gives you greater control over how and where patches are applied. This is useful because patches are typically release dependent.