Designer 10.7 | webMethods Service Development Help | Working with Elements | Moving and Copying Elements | Guidelines for Copying Elements Between Servers
 
Guidelines for Copying Elements Between Servers
*You cannot copy or move a web service descriptor element between servers.
*When you cut and paste or drag elements between servers, Designer retains a copy of the elements on the source server. That is, a move (cut and paste or drag) action is the same as a copy action.
*Designer does not automatically copy an element’s references to the destination server. Instead, it displays a dialog box after the copy alerting you to any unresolved references. You must copy the references to the destination server manually.
*Designer does not automatically update references when copying across servers. Therefore, if you are copying multiple elements from one server to another using Designer and the elements reference each other, you should paste the elements into a location with the same name on the destination server.
*If you are copying an add-in element that has a component that resides on the server, and the destination server does not have that add-in component installed, Designer displays an error message stating that you are attempting to copy an unknown element. Designer does not copy the add-in elements but does copy other elements in the selection. Elements you copy to a folder on a different server adopt the ACL access permissions of the destination folder, even if they had explicitly assigned ACLs on the source server. Folders you copy to a package on a different server inherit the default ACLs for top-level folders.
*When you copy a webMethods Messaging Trigger to another server, the trigger will be pasted in a disabled state. To create the subscriptions identified in the trigger, you must enable the trigger. When you copy a package to another server, the triggers contained in the package will maintain their original state.
*If you are configuring a cluster, use the package replication feature in the Integration Server Administrator to populate the cluster nodes. See webMethods Integration Server Administrator’s Guide for more information about this feature.
*When you move or copy a publishable document type to a destination on the same server, the moved or copied document type remains publishable. When you copy a publishable document type to a different server, Designer converts the publishable document type to an IS document type on the destination server. For more information about making IS document types publishable and synchronizing them with Broker document types, see Working with Publishable Document Types.
Tip:
To retain the status of a publishable document type and its link to a Broker document type, use the package replication functionality in the Integration Server Administrator instead of using Designer to move or copy the package containing the publishable document type. For information about package replication, see webMethods Integration Server Administrator’s Guide.