Specialized Administration > Tailoring Business Objects > Type and Attribute Management > Type and Attribute Management Command-Line Tools > Exporting and Importing Type Information > Exporting Types > Creating an Export Definition File
  
Creating an Export Definition File
To perform an export, you must first create an export definition file. The export definition file can have any name, for example DefinitionExporter.xml. The format for the export definition file is shown in the following example:
<?xml version="1.0"?>
<!DOCTYPE NmLoader SYSTEM "standardX26.dtd">
<NmLoader>
<csvExportDefinition handler="com.ptc.core.lwc.server.
TypeDefinitionExporter.beginExportDefinition">
<csvtoLocation>D:\temp</csvtoLocation>
<csvtoFileName>documents.xml</csvtoFileName>
<csvexportDefClass>com.ptc.core.lwc.server.LWCTypeDefinition</csvexportDefClass>
<csvexportNames>wt.doc.WTDocument</csvexportNames>
</csvExportDefinition>
</NmLoader>
The example export definition file instructs the exporter to export the metadata of the wt.doc.WTDocument type and all of its subtypes to load files in the following location, where # is the number suffix appended to the generated type load file: D:\temp\documents_#.xml.
The following table describes the elements which can be nested within the <csvExportDefinition> element in the export definition file:
Element
Description
<csvtoLocation>
Specifies where type load file is generated. Any value specified for this element must be an absolute path. If this element is not specified, the type load file is generated to the temporary directory for your Windchill installation, as specified in the wt.temp property.
This element is optional.
<csvtoFileName>
Specifies the name of the type load files generated by the export. The load files have a number suffix appended at the end of the file name, for example TypeLoadFile_3.xml. The number of load files generated depends on the base definition data required to support the type definition being exported. At least two load files are always generated.
This element is required.
<csvexportDefClass>
Specifies the object class being exported. Possible values are:
• com.ptc.core.lwc.server.LWCTypeDefinition—to export types.
• com.ptc.core.lwc.server.LWCEnumerationDefinition—to export global enumerations and their organizers.
This element is required.
<csvexportNames>
Specifies the name of the type or global enumeration to be exported in the type load file.
• For types, use the internal name of the type as seen in the Manage Types window of the Type and Attribute Management utility. The named type, and all of its subtypes, will be exported.
• For global enumerations, use the internal name of the global enumeration as seen in the Manage Global Enumerations window of the Type and Attribute Management utility.
This element is optional. If this element is not specified, then all types or all global enumerations will be exported, based on the class specified for <csvexportDefClass>.
<csvmode>
Specifies the mode that the export is run with. Possible values are:
• 0—All localized values will be exported as part of the XML file. This is the default.
• 1—All localized values will be exported into rbInfo files.
• Other export modes should be run only with the guidance of Technical Support.
This element is optional.