d. Rational Rose will give the class a default name (“NewClass”). Begin typing WTDocument;
when WTDocument appears in the drop down list, select it.
Example:
Selecting an Existing Class as Reference
When referencing an existing class, after the existing class has been selected, Rational Rose will open a dialog box:
Deleting Default NewClass
This indicates that the class that was created with the default name (NewClass) will no longer be referenced and can be deleted from the model. This is OK; WTDocument is being referenced, not NewClass.
Select Yes.
Step 7. Create a generalization between the extended class and the extension.
a. Select Tools > Create > Generalization. Use the mouse to select the extension – do not let go of the mouse button – and drag the mouse to the parent class.
There is also an icon to create generalizations.
b. Save the changes.
Step 8. System generate.
a. Select a modeled class, not an OOTB class.
b. Select Tools > Windchill > System Generate.
c. Select all of the check boxes except Module Descriptor. Module Descriptor is a function reserved for R&D.
Example:
d. Select OK.
e. The system generation will open a script. Read the output for errors, and then close this script box:
Example:
Step 9. Compile all Java sources created by system generation.
If this step is not completed, the Method Server will not start with a
java.lang.ClassNotFoundException exception:
(wt.introspection.introspectionResource/6) wt.introspection.WTIntrospectionException:
An introspection error has occured. System message follows:
Nested exception is:
java.lang.ClassNotFoundException: com.customer.doc.CustomerOrder
...
Specifically it will be missing the class files to match the registry
properties
Step 10. Execute generated SQL.
If this step is not completed, the Method Server will not start and will throw a very lengthy wt.pom.DatastoreException exception:
wt.services.ManagerException: wt.util.WTException: (wt.pom.pomResource/0) wt.pom.A persistence error occurred. System message follows:
Nested exception is: wt.pom.DatastoreException: A SQL error has occurred for the "(SELECT ’com.ptc.windchill.enterprise.report.ThirdPartyReportModelData’ FROM
...
This indicates there is no table for the extensions that need to be
persisted.
a. Navigate to the WT_HOME/db/sql/com/customer directory. Access SQL*Plus as the Windchill database user.
b. Always build tables before indexes. Execute the following:
Example:
@Make_pkg_customer_Table.sql
@Make_pkg_customer_Index.sql
c. Exit SQL*Plus.
Step 11. Restart Tomcat and the Method Server.
If this step is not completed, the Method Server does not reload the
registry property files and subsequently does not know about the new
customization.
Step 12. Test.
a. Test in the UI. The function Create Document should have an additional type — com.customer.doc.CustomerOrder:
Example:
when WTDocument appears in the drop down list, select it.
Example:
Selecting an Existing Class as Reference
When referencing an existing class, after the existing class has been selected, Rational Rose will open a dialog box:
Deleting Default NewClass
This indicates that the class that was created with the default name (NewClass) will no longer be referenced and can be deleted from the model. This is OK; WTDocument is being referenced, not NewClass.
Select Yes.
Step 7. Create a generalization between the extended class and the extension.
a. Select Tools > Create > Generalization. Use the mouse to select the extension – do not let go of the mouse button – and drag the mouse to the parent class.
There is also an icon to create generalizations.
b. Save the changes.
Step 8. System generate.
a. Select a modeled class, not an OOTB class.
b. Select Tools > Windchill > System Generate.
c. Select all of the check boxes except Module Descriptor. Module Descriptor is a function reserved for R&D.
Example:
d. Select OK.
e. The system generation will open a script. Read the output for errors, and then close this script box:
Example:
Step 9. Compile all Java sources created by system generation.
If this step is not completed, the Method Server will not start with a
java.lang.ClassNotFoundException exception:
(wt.introspection.introspectionResource/6) wt.introspection.WTIntrospectionException:
An introspection error has occured. System message follows:
Nested exception is:
java.lang.ClassNotFoundException: com.customer.doc.CustomerOrder
...
Specifically it will be missing the class files to match the registry
properties
Step 10. Execute generated SQL.
If this step is not completed, the Method Server will not start and will throw a very lengthy wt.pom.DatastoreException exception:
wt.services.ManagerException: wt.util.WTException: (wt.pom.pomResource/0) wt.pom.A persistence error occurred. System message follows:
Nested exception is: wt.pom.DatastoreException: A SQL error has occurred for the "(SELECT ’com.ptc.windchill.enterprise.report.ThirdPartyReportModelData’ FROM
...
This indicates there is no table for the extensions that need to be
persisted.
a. Navigate to the WT_HOME/db/sql/com/customer directory. Access SQL*Plus as the Windchill database user.
b. Always build tables before indexes. Execute the following:
Example:
@Make_pkg_customer_Table.sql
@Make_pkg_customer_Index.sql
c. Exit SQL*Plus.
Step 11. Restart Tomcat and the Method Server.
If this step is not completed, the Method Server does not reload the
registry property files and subsequently does not know about the new
customization.
Step 12. Test.
a. Test in the UI. The function Create Document should have an additional type — com.customer.doc.CustomerOrder:
Example: