Importing and Exporting End Points

You can export end points individually, or by group, and import them into another iCM.

Exporting an End Point

To export an end point, right-click on it and choose "Export this end point". The end point and its full namespace are exported.

Exporting Groups

To export a group of End points, right-click on the group and choose "Export this group of end points".

Exports of end point groups will include all of the child groups and the end points within them. The export also includes the full parent namespace.

Importing End Points

To import end points into the library, right-click on the root END POINTS folder and select "Import end points..."

You can choose whether the end points are imported as work in progress, published, or published "for production" (ie with development mode and tracing disabled).

iCM will prompt  you to select the export file you would like to import. Find and select the file and then confirm the import by clicking "Continue this import" in the action panel.

Export files include the parent groups that make up the namespace of the exported end points. That means the group structure will be created in the target iCM, maintaining exactly the same namespace as the source.

If the end points don't already exist in iCM, they will be imported without further interaction.

If the end points do already exist, and there are differences detected, iCM will allow you to view the differences and to choose whether to "Overwrite", "Ignore" or "Rename" the conflicting end points. You may also find that imports cause end points to be updated even when there are no differences between the import and existing content. For example, if both the existing and the imported end point have debug/trace flags enabled, an import and "publish for production" will show that the end points are identical but will still need to update to disable these flags. Version history will let you see these differences.

Care should be taken when importing end points from newer to older releases of iCM. Some end points may rely on JavaScript libraries present in the API Server not present in older versions. While the libraries of one release will be present in future releases, not all libraries will be back-ported to old releases as new functionality is developed.