webMethods 10.2 | Service Development Help | Managing Packages
 
Managing Packages
 
Creating a Package
Documenting a Package
Viewing Package Settings, Version Number, and Patch History
Assigning a Version Number to a Package
About Copying Packages Between Servers
Reloading a Package
Comparing Packages
Deleting a Package
Exporting a Package
About Package Dependencies
Assigning Startup, Shutdown, and Replication Services to a Package
A package is a container that is used to bundle services and related elements, such as specifications, IS document types, IS schemas, and triggers. When you create a folder, service, IS document type, or any element, you save it in a package.
Packages are designed to hold all of the components of a logical unit in an integration solution. For example, you might group all the services and files specific to a particular marketplace in a single package. By grouping these components into a single package, you can easily manipulate them as a unit. For example, you can copy, reload, distribute, or delete the set of components (the “package”) with a single action.
Although you can group services using any package structure that suits your purpose, most sites organize their packages by function or application. For example, they might put all purchasing-related services in a package called “PurchaseOrderMgt” and all time-reporting services into a package called “TimeCards.”
On the server, a package represents a subdirectory within the IntegrationServer_directory\instances\instance_name\packages directory. All the components that belong to a package reside in the package’s subdirectory.

Copyright © 2017-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release