Installing a Package Published by Another Server

A package coming from the publisher already has a List ACL associated with it, specifically, the List ACL that was assigned to the package on the publishing server.

The installing user does not need to be a member of that ACL to install the package; however, users on the subscribing server must be members of the package's List ACL in order to display the package on Integration Server Administrator pages.

Important:
Be sure the server where you are installing the package has an ACL with the same name as package's List ACL. If the List ACL does not exist, no users will be able to display the package on Integration Server Administrator pages.

If the package you are installing has dependencies on another package that does not exist on your server, the server will install the package but will not enable it. You will not be able to enable the installed package until the dependencies are satisfied.

If the package you are installing is associated with an e-mail listener, the server will install the package but will not enable the listener. This is because the password required for the Integration Server to connect to the e-mail server was not set with other configuration information about the listener. To enable the listener, go to the Server > Ports > Edit email client configuration and update the Password field to specify the password needed to connect to the e-mail server.

When you install a package from another Integration Server, it is possible that an HTTP URL alias associated with the new package has the same name as an HTTP URL alias already defined on your Integration Server. If Integration Server detects a duplicate alias name, it will display load warnings on the Packages > Management > package_name page. For more information about duplicate HTTP URL aliases, refer to Portability of URL Aliases and Possible Conflicts.

When you install a package from another Integration Server, it is possible that a port alias for a port in the new package has the same alias as a port already defined on your Integration Server. A port alias must be unique across the Integration Server. If Integration Server detects a duplicate port alias, it will display load warnings on the Packages > Management > package_name page. Additionally, Integration Server will not create the port and will write the following warning to the server.log:

[ISS.0070.0030W] Duplicate alias duplicateAlias encountered creating protocol listener on port portNumber

Note:
If you want the port to be created when the package is loaded delete the existing port with that alias, create a new port that has the same properties as the just deleted port, and then reload the package containing the port with the duplicate alias. Integration Server creates the port when the package is reloaded.

When you install a package released from a version of Integration Server prior to version 9.5, Integration Server creates an alias for each port associated with the package. For more information about the port alias created by Integration Server, see About the Port Alias.

If hot deployment of packages is enabled, Integration Server installs the package using the hot deployment process. For more information about hot deployment, see Hot Deployment of Packages.

Important:
Make sure that packages you install come from a legitimate source, such as a replication from another server. If you are not sure, check with the developers in your organization to verify that an authorized person updated the package. Unknown packages might contain code that could damage your server.

5. If you want Integration Server to make the package available immediately following installation, select the Activate upon installation check box in the Option field.

6. If you want Integration Server to archive the package automatically after installation, select the Archive upon installation check box. This check box is selected by default.