Copying Packages
When copying packages, keep the following points in mind:
You can copy a package to a different server only if you are a member of a group assigned to the Replicators ACL on the source and destination servers and you are logged on to both servers.
Before you copy a package that contains elements with unsaved changes, you must save the changes.
You cannot undo a copy action using the
Edit > Undo command.
If you copy a package that depends on other packages to load (that is, the package has package dependencies), and the required packages are not present on the destination server, the package will be copied but it will not be enabled.
You cannot copy a package to another server if the destination server already contains a package with that name.
Note: Because UNIX directories are case sensitive, Integration Servers running in a UNIX environment will allow packages with similar names to reside on the same server. For example, you can copy a package named orderProcessing to a server that contains a package named OrderProcessing.
When you copy 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 write a message to the server.log.
When you copy 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 not create the port and will write the following warning to the server.log:
[ISS.0070.0030W] Duplicate alias duplicateAliasName encountered creating protocol listener on port portNumber
Note: If you want the port to be created when the package is loaded, use Integration Server Administrator to 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 copy a package from a version of
Integration Server prior to version 9.5 SP1 to an
Integration Server version 9.5 SP1,
Integration Server creates an alias for each port associated with the package.
Integration Server assigns each port an alias. For information about the naming conventions used
Integration Server, see the
webMethods Integration Server Administrator’s Guide.
If the package you are copying is associated with an e-mail listener,
Integration 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 sent with other configuration information about the listener. To enable the listener, go to the
Security > Ports > Edit E-mail Client Configuration Screen and update the
Password field to specify the password needed to connect to the e-mail server.
The
Integration Server to which the package is copied must run in a JVM with a major version that is the same or higher than the JVM version required by the package. For example, if the specified JVM version for a package release is 1.8.0_32, the installing
Integration Server must be running in a JVM that is 1.8 or higher. If the major version of the
Integration Server JVM is less than the JVM version required by the package,
Integration Server installs but does not activate the package
To copy a package between servers
1. In Package Navigator view, select the package you want to copy.
2. Click Edit > Copy.
3. If the package you want to copy contains elements with unsaved changes, Designer alerts you that the package cannot be copied until you save the changes. Click OK to close the alert dialog box. Then, save the changes and repeat the copy action.
4. Select the server where you want to copy the package.
5. Click Edit > Paste.