xxx3

Registry Properties
associationRegistry.properties ,Sorted alphabetically by classes that have modeled relationships, one line for each class with a modeled relationship.Two classes are typically required for a relationship, so each link usually is listed twice,once for each side of the relationship.Example of a WTPartUsageLink connecting WTPart and WTPartMaster:
wt.part.WTPart=wt.part.WTPartUsageLink...
wt.part.WTPartMaster=wt.part.WTPartUsageLink
classRegistry.properties, Sorted by class name and identifies the full package for the class.
Example of WTPart and WTDocument:
WTDocument=wt.doc...
WTPart=wt.part
descendentRegistry.properties, Sorted by super class and lists sub classes or the super class, one line for each sub class.Example of several link classes inheriting from wt.vc.struct.IteratedUsageLink:
wt.vc.struct.IteratedUsageLink=wt.doc.WTDocumentUsageLink
wt.vc.struct.IteratedUsageLink=wt.epm.structure.EPMMemberLink
wt.vc.struct.IteratedUsageLink=wt.part.WTPartUsageLink
modelRegistry.properties, Sorted by package name and identifies the classes in each package, one line for each class in the package.
Example of some of the classes in the wt.part package:
wt.part=PartMaster
wt.part=PartVersion
wt.part=WTPartUsageLink
wt.part=WTPartReferenceLink
wt.part=WTPartMaster
wt.part=WTPart
Note: Customization can be de-installed by using either WT_HOME/bin/modelUninstall or by removing all references to the customization from these property files.
Demo 6-1: Extend WTDocument
Objectives
● Create a new package structure.
● Extend a Windchill class.
● Model new attributes.
● Implement the customization.
Scenario
A customer has identified a requirement for a new business information type similar to WTDocument with some additional attributes. This demonstration will show how to model a custom WTDocument with the required attributes.
Step 1. Open the Windchill model.
a. Start Rational Rose.
b. Open WT_HOME/src/wt/WTDesigner.mdl.
c. When asked to Load subunits of WTdesigner.mdl?, select Yes:
Example:
---
Step 2. Create the package structure in Rational Rose.
a. Using the Browser, navigate to Logical View > <<assembly>> wnc and open the diagram SystemGeneration diagram.
---
SystemGeneration Diagram
b. Select Tools > Create > Package.
There is also an icon to create a package.
c. Use the cross-hairs to position the package.
d. The default name for a package will be NewPackage.
e. Rename the package from NewPackage to com. To rename the package, select the name on the package and type the new name com.
---
New Package Added
Step 3. Open the com package and create another package named customer.
Step 4. Open the customer package and create another package named doc.
a. This package will conflict with an existing package by the same name, so a different package creation process will be used.
b. To create a package with the same name as an existing package, first create the package.
c. Instead of renaming the package in the diagram window, use the browser window on the left side in Rational Rose to rename the package to doc.
d. To open the new package in the browser window, right-click on the new package and select Select In Browser.
You can also expand the “Logical View” structure in the Rational Rose
browser and navigate to com > customer.
e. When the warning message appears Package "doc" now exists in multiple name spaces, select OK.
Example:
---
Package in Multiple Name Spaces
Step 5. Control the custom units.