Indication of whether the package is enabled or disabled. The server does not load disabled packages at server initialization and you cannot access elements that reside in disabled packages.

List of startup, shutdown, and replication services, if any, for the package. For more information about startup, shutdown, and replication services and how to identify them, see Running Services When Packages Are Loaded, Unloaded, or Replicated.

Package description. A brief description of the package.

Version information. Package version and build number. The manifest also includes the JVM version under which the package was published. Additionally, the manifest includes the target server version which indicates the minimum version of Integration Server on which the package can be installed. When you create a package, Integration Server uses the current server version as the target server version.

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

Package dependencies, if any, for the package. For a specific package, the developer can identify other packages that the server should load before it loads the elements in a particular package. In other words, the developer can identify when one package depends on another. The developer can also indicate whether the package should or should not reload when a package it depends on is reloaded. For information, see Displaying Information about a Package and IBM webMethods Service Development Help.

Target package name. Name of the package.

Publishing server. The Integration Server that published the package. If the package has not been published, this field contains None.

Extended properties of custom packages.