Cloud Application Integration (On-Premises) : Administering Integration Server : Managing Packages : Copying Packages from One Server to Another : The Subscribing Server : About Installing Packages Published by Another Server
About Installing Packages Published by Another Server
 
Installing a Package Published by Another Server
When another server publishes a package to your server, you need to install the published package. You can also perform the following tasks on a package:
*Recover a package. If you install a package that has the same name as an existing package on your server, your server copies the original package to Integration Server_directory \instances\instance_name\replicate\salvage before it installs the new one. This lets you easily revert to the previous version if you are dissatisfied with the new package. For information about reverting to the earlier version, refer to Recovering a Package.
*Activate a package. You can select whether you want the server to immediately activate the package after it installs it. If Integration Server does not activate a package upon installation, Integration Server copies the package to the packages directory, but it is not available for clients to use. To make this package available for clients, you must manually activate it. For more information, refer to Activating a Package.
*Archive a package. You can also archive the package automatically after installing the package. If you choose to archive the package automatically, Integration Server moves the package from the Integration Server_directory \instances\instance_name\replicate\inbound directory to the Integration Server_directory \instances\instance_name\replicate\archive directory. If you do not want to archive a package automatically after installation, you can archive it later. For more information, see Archiving a Package.
Copyright © 2015- 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback