Software AG Products 10.7 | Integrating On-Premises and Cloud Applications | Service Development | Comparing Integration Server Packages and Elements | Guidelines for Comparing Packages, Folders, and Elements
 
Guidelines for Comparing Packages, Folders, and Elements
 
Comparing Integration Server Elements
Comparing Integration Server Folders
Keep the following points in mind when using the compare tool:
*The results of the compare tool are useful only when you compare elements that are of the same type.
*When you compare two packages, folders, or elements, Designer opens the compare editor only if there are one or more differences between the items compared. If there are no differences to show, Designer displays a message to indicate this.
*You can only view differences, if any, using the compare editor. For details, see Working with the Compare Editor. If you want to modify a package, folder or any other element, use the navigator or editor provided for this purpose.
*You can only compare packages, folders, and elements from the same version of Integration Server. Comparison of assets across different versions of Integration Server is not supported. Internal changes in assets from one release to another might result in functionally identical assets being reported as different.
*To compare assets on different Integration Servers, Designer must be connected to both Integration Servers.
*When comparing folders, Designer does not compare properties.
*When comparing packages, Designer compares package contents such as template files, *.jar files, and HTML files only for packages on Integration Server version 10.5 or higher. For more information about comparing packages, see Comparing Integration Server Packages.
*The compare tool compares the assets by comparing whichever asset is alphabetically second against the asset that is alphabetically first in ascending order from A to Z. For example, if you compare two document types named folderA:docTypeA and folderB:docTypeB, Designer compares the folderB:docTypeB document type against folderA:docTypeA. In the Change List panel, the differences are given relative to document type folderA:docTypeA. For example:
*If document type folderA:docTypeA includes a field that does not exist in document type folderB:docTypeB document type, the Change List panel lists the field as Added.
*If folderB:docTypeB includes a field that does not exist in folderA:docTypeA the Change List panel lists the field as Removed. The Content panel displays document type folderA:docTypeA on the left and document type folderB:docTypeB on the right.
*If the document types contain variables of the same type but with different names, the Change List panel lists the field as Renamed.