Publishing a Package
Publishing a package to other Integration Servers involves two tasks:
Creating a release. To publish a package, your server creates a distribution file that contains the information for the package.
When you create the distribution file, you select what information to include in the file.
You can select all files to send, or just some. In addition, you can request a
full release or a
patch release. With a full release, the new package entirely replaces the old package on the subscriber's server. With a patch release, the files in the patch release replace the versions of those files in the target package; all other files in the target package remain intact. See
Overview of Package Replication for more information about how full and patch releases differ.
After you indicate the files to include in the release, the server places all the selected files into a single, compressed file (a zip file). It places the zip file in the Integration Server_directory \instances\instance_name\replicate\outbound directory. If the outbound directory already contains a zip file for this package, the server overwrites the existing file.
Sending the release. After you create the release, you can send it to the subscribing servers.
A subscribing server receives the zip file containing the release in its inbound directory ( Integration Server_directory \instances\instance_name\replicate\inbound). If a zip file for the package already exists in a subscribing server's inbound directory, the server overwrites it. The zip file remains in the inbound directory on the subscribing server until the administrator of that server installs the package.
A developer can set up the package to execute a service when you create the release. When you begin to create the release, this service executes before the list of files to be zipped is displayed. You can use this service to write state and configuration information for the package to a file. This file will be included with the other zipped files included in the release. For instructions on setting up replication services, see webMethods Service Development Help.
