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. See Activating a Package for instructions on activating a package.

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.