Name of the package.

Version number of the package.

A number that a developer assigns to a package each time it is regenerated. For example, a developer might generate version 1.0 of the Ordering package 10 times and assign build numbers 1,2,3,...10. These build numbers are generally used to identify the generations of a package in a development environment.

Minimum version of the Java Virtual Machine (JVM) required to run this package.

The Integration Server on which the package is installed must run in a JVM with a major version that is the same or higher than 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.

The Access Control List assigned to the package. Users associated with this ACL can see the package listed on the Integration Server Administrator or Designer. To see the folders and elements contained in the package, a user must have List access to the folders and elements themselves.

A list of patches that have been applied to this release of the package. These are numbers that are meaningful to your installation, possibly obtained from your problem tracking system.

A description of the package and its intended use.

The name of the company, organization, or server that published the package.

Date, time, and year in which the package was created.

Number of elements that the server successfully loaded. To view the elements that the server has successfully loaded, click the Browse services in < PackageName> link.

Number of elements that the server failed to load. If the server failed to load one or more elements, the Load Errors section of the screen lists the elements that it could not load, along with the reason.

List of the services that you or another administrator have identified as startup services. For more information about startup services, refer to Running Services When Packages Are Loaded, Unloaded, or Replicated.

List of the services that you or another administrator have identified as shutdown services. For more information about shutdown services, see Running Services When Packages Are Loaded, Unloaded, or Replicated.

List of the services that you or another administrator have identified as replication services. For more information about replication services, see Running Services When Packages Are Loaded, Unloaded, or Replicated.

List of the packages the server must load before it loads this package. For more information about package dependencies, see webMethods Service Development Help.

List of packages that depend on this package. If you disable the package, these packages will be affected.

List of other Integration Servers that subscribe to this package. For information on how to copy packages from one server to another, how to subscribe to packages, and how to publish packages to another server, see Copying Packages from One Server to Another.

Displays a list of elements that generated errors and could not be loaded onto the server when the package was installed. When some elements do not load, the load status for the package becomes Partial.

Displays a list of elements that generated warnings when the package was installed. The server was able to load the packages, despite the warnings. When package elements are loaded with warnings, the load status for the package becomes Warnings.

A list of patches or partial packages that have been applied to this release of the package.