Sample import record migration file

This sample XML file shows one of each of the five export records. The ExportData utility exports four XML files:

  • usersAndContactsN.xml
  • groups.xml
  • categories.xml
  • doctypes.xml

The usersAndContactsN.xml file contains contact and operator records similar to the following.

<migrationdoc>
	<contacts>
		<contact.name _type="Text"><![CDATA[owner,otto]]>
		</contact.name>
		<user.id _type="Text"><![CDATA[1296]]></user.id>
		<full.name _type="Text"><![CDATA[owner, otto]]></full.name>
		<email _type="Text"><![CDATA[oowner@hp.com]]></email>
		<contact.phone _type="Text">
		<![CDATA[858792.3416]]></contact.phone>
		<operator.id _type="Text"><![CDATA[oowner]]></operator.id>
	</contacts>
	<operator>
		<application.name_type="Text">
		<![CDATA[menu.manager]]></application.name>
		<command _type="Boolean"><![CDATA[true]]></command>
		<company _type="Text"><![CDATA[PRGN]]></company>
		<contact.name _type="Text">
		<![CDATA[Tremain, Johnny]]></contact.name>
		<email _type="Text"><![CDATA[jt@hp.com]]></email>
		<ess.access.only _type="Boolean">
		<![CDATA[false]]></ess.access.only>
		<expire.password _type="Boolean">
		<![CDATA[false]]></expire.password>
		<full.name _type="Text"><![CDATA[Tremain, Johnny]]>
		</full.name>
		<locked.reason _type="Decimal"><![CDATA[0]]>
		</locked.reason>
		<login.revoked _type="Boolean"><![CDATA[false]]>
		</login.revoked>
		<msglog.lvl _type="Decimal"><![CDATA[1]]></msglog.lvl>
		<name _type="Text"><![CDATA[johnny]]></name>
		<names _type="Array">
		 <names _type="Text"><![CDATA[name]]></names>
		 <names _type="Text"><![CDATA[string1]]></names>
		</names>
		<no.lock.user _type="Boolean"><![CDATA[true]]>
		</no.lock.user>
		<password _type="Text"><![CDATA[johnny]]></password>
		<profile.change _type="Array">
		 <profile.change _type="Text">
		 <![CDATA[KM COORDINATOR]]></profile.change>
		</profile.change>
		<values _type="Array">
		 <values _type="Text"><![CDATA[MAIN MENU]]></values>
		 <values _type="Text"><![CDATA[HOME]]></values>
		</values>
	</operator>
			.
			.
			.
</migrationdoc>

The groups.xml file contains Knowledge Management group records as follows:

<migrationdoc>
	<kmgroup>
		<id _type="Text"><![CDATA[KMGM01311]]></id>
		<name _type="Text"><![CDATA[HR Owner Group]]></name>
		<operators _type="Array">
		<operators _type="Text"><![CDATA[jowens]]></operators>
		<operators _type="Text"><![CDATA[rtillman]]>
		</operators>
		<operators _type="Text"><![CDATA[ssmith]]></operators>
		</operators>
	</kmgroup>
		.
		.
		.
</migrationdoc>

The categories.xml file contains kmcategory records similar to the following record. Note that the id in this sample record is KM42T and ends with a "T". Each id in the kmcategory table must end with a unique character such as "T" because the search engine logic depends on having a category id with a unique delimiter to determine where one category id ends and the next category id begins.

<migrationdoc>
	<kmcategory>
		<level.in.hierarchy _type="Decimal">0</level.in.hierarchy>
		<name _type="Text">HR Employment FAQs</name>
		<id _type="Text">KM42T</id>
		<permission _type="ArrayStructure">
		 <kmprofile _type="Text">KMP005</kmprofile>
		 <kmgroup _type="Text">KMG02</kmgroup>
		</permission>
		<permission _type="ArrayStructure">
		 <kmprofile _type="Text">KMP002</kmprofile>
		 <kmgroup _type="Text">KMG011</kmgroup>
		</permission>
		<permission _type="ArrayStructure">
		 <kmprofile _type="Text">KMP001</kmprofile>
		 <kmgroup _type="Text">KMG012</kmgroup>
		</permission>
	</kmcategory>
		.
		.
		.
</migrationdoc>

The doctypes.xml file contains kmdoctype records similar to the following:

<migrationdoc>
	<kmdoctype>
		<name _type="Text"><![CDATA[errormsg]]></name>
		<description _type="Text"><![CDATA[Description of an error
		message</description>
		<display.name _type="Text"><![CDATA[Error Message/
		Cause]]></display.name>
		<format.edit _type="Text"><![CDATA[kmdocument.errormsg]]>
		</format.edit>
		<format.new _type="Text"><![CDATA[kmdocument.errormsg]]>
		</format.new>
		<format.view _type="Array">
			<format.view _type="ArrayStructure">
			 <view.data _type="Text"><![CDATA[<table style=]>
			 </view.data>
			 <view.description _type="Text"><![CDATA[This is the
			 Default ]]></view.description>
			 <view.seclevel _type="Decimal"><![CDATA[60]]>
			 </view.seclevel>
			 <view.name _type="Text"><!
			 [CDATA[Default ErrMsgCauseView]]></view.name>
			 <view.roles _type="Array">
				  <view.roles _type="Text"><![CDATA[KMGM010]]>
				  </view.roles>
			 </view.roles>
			</format.view>
		</format.view>
	</kmdoctype>
		.
		.
		.
</migrationdoc>

Related topics

Knowledge Management migration
XML file specification for Knowledge Management migration