Guidelines for Using Package Replication
Keep the following guidelines in mind when using the package replication facility:
Publishers and participating subscribers must use
Integration Server Version 2.0 or later. For the for Automatic Pull feature to work, they must be running Version 4.0 or later. If you are running version 4.0 or later of the
Integration Server and publish to an earlier release of the
Integration Server, the subscriber cannot perform a manual or automatic pull of a package. Instead, the subscriber must wait for the publisher to send the package
Any
Integration Server can publish a package.
Any
Integration Server can subscribe to a package on another
Integration Server.
An
Integration Server can be both a publisher of packages and a subscriber of other packages; however, it cannot be both a publisher and a subscriber of the
same package.
After setting up a subscription, if you delete the user account with which the subscription was set up (the account on the subscribing server that the publishing server uses to log on), the publisher will not be able to log into the subscribing server to send this package.
Be careful when replicating a package that is associated with a port; the new port might decrease security on the target system. For example, suppose you replicate a package that is associated with an HTTP port at 5556. The replication process creates an HTTP port at 5556 on the target server. If the target server normally uses only HTTPS ports because of their greater security, then the new port presents a possible security hole on that server.