04.12.2012 Views

Windchill System Administrator's Guide

Windchill System Administrator's Guide

Windchill System Administrator's Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Mapping Rules<br />

<strong>Windchill</strong> Import and Export allow mapping that either excludes attribute<br />

information, or maps it to other attributes during exporting and importing<br />

operations. Mapping attributes can adapt data to new environments that cannot<br />

accept the data in its original format. PTC supports three methods of mapping:<br />

• mapping through special rules:<br />

Mapping through rules is the simplest method, but is not as powerful as<br />

mapping through XSL transformation.<br />

• mapping through XSL transformation:<br />

Mapping through XSL transformation requires knowledge of XML and XSL.<br />

The XSL transformation functions are called by a form of special rule.<br />

• mapping through rules that call Java functions:<br />

A software engineer with Java expertise is required to map data through rules<br />

that call Java functions.<br />

Mapping rules can resolve situations announced by conflict messages during<br />

<strong>Windchill</strong> Import and Export.<br />

This appendix describes mapping rules and then describes conflict messages.<br />

Mapping Through Special Rules<br />

Mapping rules can be written to apply to a specific export or import process or a<br />

set of such processes. The rules reside in either or both of two types of ASCII<br />

XML files that can also include properties that control import and export<br />

operations. You set properties in mapping rules files by editing the files, and you<br />

cannot use the xconfmanager utility for this purpose. If you are not setting<br />

properties through a graphical user interface or in a mapping file, you add or edit<br />

properties with the xconfmanager utility, which is discussed elsewhere in this<br />

guide.<br />

• Client-based Files -- These files are selected by browsing in the graphical<br />

interface. These mapping rules file can have any name and can be located<br />

anywhere that the software can access and read them. These files govern if<br />

they conflict with generalized files.<br />

• Generalized Files -- These files provide rules for either import operations or<br />

export operations. Their names must end in .xml. They are in either of two<br />

specific locations whose names define their functions:<br />

\<strong>Windchill</strong>\codebase\registry\ixb\export_settings<br />

\<strong>Windchill</strong>\codebase\registry\ixb\import_settings.<br />

This appendix shows examples of the two type of files in the following two<br />

sections. After the examples you will see a section about properties, and several<br />

sections explaining rules (with examples).<br />

C-4 <strong>Windchill</strong> <strong>System</strong> Administrator’s <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!