04.12.2012 Views

Windchill System Administrator's Guide

Windchill System Administrator's Guide

Windchill System Administrator's Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

TestOrganizer<br />

<br />

For all XML files to be imported, the preceding mapping rule will change the<br />

values for tag to TestOrganizer, if the original value for this tag is<br />

TestOrganizer/TestString. Changing the values for other XML files other than<br />

ibaDefinitions.xml may not be the result that is expected. For example, values<br />

would change for the file ABC.xml if it contains the following:<br />

TestOrganizer/TestString<br />

A general approach to overcome this problem is to supply the additional path for<br />

the tag. For example, if we enhance the mapping rule to the following<br />

version, the change prevents the modification of the value in ABC.xml:<br />

<br />

ibaDefinitions/StringDefinition<br />

path<br />

TestOrganizer/TestString<br />

TestOrganizer<br />

<br />

The altered mapping rule would create the following StringDefinition in the<br />

database if it did not already exist:<br />

Another concern is mapping the IBA values to the appropriate IBA definitions for<br />

XML files corresponding to IBAHolder. In general terms, if a mapping rule is<br />

supplied for IBA definitions, a mapping rule should be supplied for the related<br />

IBA values. For example, consider a WTPart, Tag_WTPart_0.xml, which has the<br />

IBA values declared by the following block:<br />

<br />

<br />

Test Organizer<br />

TestString/NestedTestString<br />

My String value for NestedTestString<br />

StringValue<br />

NestedTestString<br />

C-14 <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!