Exporting content types using Clarity XML Open Gateway (XOG) results in very large output files. How can we export the configuration to reduce the amount of output generated?
You can use two arguments, singleContentType and no_dependencies, to export individual content types and to limit the amount of data exported for each type. These arguments should be used only for small, incremental updates to content.
Important! Use care when applying these arguments. The user performing the export must have a thorough understanding of content data on the source and target systems.
Exports a specific content type. You must specify the singleContentType argument in the XML read file. The format for the argument in the XML read file is as follows:
(be sure to use the exact mixed case letters for this argument)
<args name="singleContentType" value="content type">
where content type can be any of the following supported content types:
- Job Definitions
- Menu Manager
- Portlet Pages
Limits the amount of data exported for a specific content type. The format for the argument in the XML read file is as follows: (be sure to use the exact mixed case letters for this argument)
<args name="no_dependencies" value="true">
where true exports incremental changes for a content type without dependencies. By default, the no_dependencies flag is false, which means any dependencies that exist for the value specified in the singleContentType argument are exported if the value is not specified.
Adding these arguments to the portlets_read.xml file used to export the portlets will drastically reduce the time to complete as well as the size of the output file.
See the 'Export Content Types Without Dependencies' in the 'XOG Services' section of the CA Clarity PPM XML Open Gateway Developer Guide for syntax.
Keywords: CLARITYKB, how-to, configuration