Configuring Equivalence Mapping (Information Types)

PTC Arbortext Content Delivery Publishing and Loading > Using Publishing and Loading > TAL Configuration > Configuring Equivalence Mapping (Information Types)

The information and publication types of object types such as PartsList, IE-XML, and PDF are managed through an equivalence mapping file. The file is named equivalence-mapping.xml. It is located at HOME\SW\Config\Applications\DataProcess\Config\Common\Templates\EquivalenceMapping.

In this file, you must map the SIM type of an object to its respective information or publication type in the PTC Arbortext Content Delivery interface.

Based on the mapping, equivalence mapping populates the correct information type and publication type in the XMD output (DCTM_Output) under the Transform phase of PxTAL processing. This is an optional mapping.

This configuration file affects the information type written to the associated .XMD files during the Transform process. This means the mapping must be done prior to running the TAL process for the full bundle and cannot be changed later for an incremental bundle publish and load. In this case, the changes to the file will not affect the bundles that have already been processed.

The following table covers the XML elements defined in the equivalence-mapping.xml file:

Element	Description
<Mappings>	The root element containing multiple mapping elements.
<mapping>	Contains a single mapping entry for a SIM type. Any new supported type requires a new mapping element be defined in this file. • type attribute – holds the SIM type (as present in bundle) • informationType attribute – holds the information type value to be displayed in the PTC Arbortext Content Delivery interface • publicationType attribute – holds the publication type value This attribute is required only if the informationType is of type Publication.
<type>	Contains the source type name which is present in the bundle XML file for which the respective information or publication type is to be fetched.
<informationType>	Contains the information type value to which the source type maps.
<publicationType>	Contains the publication type value to which the source type maps. This attribute is required only if the informationType is a publication type. This element defines the publication type specific mapping • target attribute – holds the SIM attribute information from the bundle • logicalPublicationType attribute – holds the publication type value that will be displayed in the PTC Arbortext Content Delivery interface.
<criteria>	Defines the attribute name whose value in the source input file should match the specified value. There can be zero or more criteria elements. All of the criteria must be matched in order to find the respective information or publication type. In the case where no criteria element is found, the corresponding information/publication type is mapped right away.
<tokens>	Contains multiple token elements.
<token>	Contains the attribute whose value is to be matched in the source input file. The intention behind keeping multiple token elements is to support the case where there are multiple possible attribute names known. The criteria is said to be fulfilled if any of the specified token names is present in the source file and matches the specified value.
<value>	Contains the value of the token name to be matched in the source input file.

The following mechanism must be followed for equivalence mapping to be in effect:

• A mapping exists for the object type or subtype in the equivalence mapping file.

◦ The value for the PTC Arbortext Content Delivery Information Type will be taken from the mapping.

• No mapping exists for an object type or subtype in the equivalence mapping.

◦ The value for the PTC Arbortext Content Delivery Information Type will default to a pre-defined hard-coded value.

• Currently, the Information Type value coming from Windchill Service Information Manager is ignored.

The value to be used in informationType and publicationType should be in conjunction with what the object type has in facets.xml, so as to be reflected correctly in the user interface.

In relation to the above scenarios, since the output of Equivalence Mapping affects the value emitted to the XMD file, the original Information and Publication Type values in the bundle are still available like any other attribute of the bundle. Potentially, you might want to have that information indexed or used as well.

The mapping provided here for information or publication types takes precedence over what has been defined in the publication bundle. The user interface uses the result of this mapping while consulting the user interface configuration file facets.xml.

Following are sample mapping file entries:

<Mappings>

<mapping informationType="partsList" type="com.ptc.arbortext.windchill.partlist.PartList"/>
<mapping informationType="Information" type="wt.epm.EPMDocument|com.ptc.ptcnet.DynamicDocument"/>
<mapping informationType="kit" type="com.ptc.arbortext.windchill.partlist.PartList">
<criteria>
<tokens>
<token>servicekit</token>
</tokens>
<value>true</value>
</criteria>
</mapping>


<publication-mapping target=" wt.part.WTPart|com.ptc.sis.Base|com.ptc.sis.BaseDiv|
com.ptc.sis.PsSection|com.ptc.sis.PsRoot|com.ptc.OwnerManual" logicalPublicationType="OwnersManual"/>

For example, if you want to set the information type of a SIM partsList with the value com.ptc.arbortext.windchill.partlist.PartList, you can do this by declaring the value in the equivalence mapping file:

In addition, if you want to apply the information type based on some filtration criteria, then you can use <criteria> and <token> elements for this purpose. To do this, you must propagate the token name and its value to be matched from the input file:

<mapping informationType="kit"
type="com.ptc.arbortext.windchill.partlist.PartList">
<criteria>
<tokens>
<token>servicekit</token>
</tokens>
<value>true</value>
</criteria>
</mapping>

Similarly for publication type mapping, if you want to set the publication type publication for the SIM object type wt.part.WTPart|com.ptc.sis.PsRoot, then you can use following mapping:

<publication-mapping target="wt.part.WTPart|com.ptc.sis.PsRoot"
logicalPublicationType="publication"/>

The target value is read from the PS specific DMPMap file. If this mapping is not found, then the publication type is determined through a substring operation and it is the value found after the last pipe ( | ) character.

By default, if there is no matching type, then PTC Arbortext Content Delivery displays Information for IE XML and PDF and partslist for Parts Lists. The same is true for Publication type.