Windchill System Administrator's Guide
Windchill System Administrator's Guide
Windchill System Administrator's Guide
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
IBA Value<br />
Type Identifier<br />
Organization ID<br />
Most conflicts for IBA Values are non-overridable in the following meaning. The<br />
following if violated make non-overridable conflicts:<br />
• The IBA type should be the same if the IBA path are the same.<br />
• The IBA values should be matching if the IBA path are the same.<br />
• The XML file and the existing IBAHolder must have the same IBA values,<br />
including the number of IBA values.<br />
Some conflicts are overridable, for example, the precision for float values, ratio<br />
values, and unit values.<br />
If an object is Typed, such as WTPart or WTDocument instance, then it will carry<br />
a value with tag which declares the associated soft type or hard<br />
type in the XML file. This value is always non-overridable unless they are<br />
matched exactly.<br />
If the organization of Organization ID included in the export data is not found, the<br />
conflict is overridable. In such a case, if the software is configured to override<br />
conflicts, the default organization is used.<br />
Reforming Custom Modeled Attributes<br />
If an object with custom modeled attributes is exported from system A and then<br />
imported into system B where the object does not include the custom modeled<br />
attributes, the import fails. The custom modeled attributes should be exported as<br />
IBAs. This section explains how to write a mapping rule for use in export to<br />
insure that import will be successful in a such a case.<br />
Using such a rule introduces achieves three goals:<br />
• Using an export mapping rule like the one described in this section means that<br />
the custom modeled attributes will be ignored.<br />
• The tags, especially the root tag, should be mappable so that the XML files<br />
can be handled by the import system.<br />
• The DTD specified in the XML should be mappable so that the new DTD is<br />
recognized and the XML files can be validated by the import system.<br />
As an example, assume there is a Class SubTypeOfWTPart, which extends<br />
wt.part.WTPart, with one additional attribute mySubTypeAttr1. At export side is<br />
the corresponding handler with a customer DTD Customer-DTD.dtd, which is not<br />
included in IXB framework. The export system has the handler to export<br />
SubTypeOfWTPart, but unfortunately the import system does not have this<br />
handler.<br />
C-24 <strong>Windchill</strong> <strong>System</strong> Administrator’s <strong>Guide</strong>
Change language