Copy Customized Java Annotated Files
Use the following instructions to incorporate your Java annotation customizations into the target installation:
1. If you have not done so already, install and configure Windchill Information Modeler into your Windchill solution.
2. Locate the following customization files from your source system:
◦ System files (for example, Java property files, icon and image files, and HTML files)
◦ Source code (for example, Java classes)
◦ Hand-implemented SQL scripts
◦ Resource bundles
3. Back up all of these files to a separate storage medium.
4. Copy all of these files into a corresponding location in your new target installation.
5. Upgrade the customized source code dependent on deprecated components in the test installation. For further instructions, see the Dealing with Deprecated APIs section that follows.
6. Build all customizations:
ant -f bin/tools.xml customer_build
This command compiles all bundles and Java classes, generates SQL scripts, and applies any column and bundle customizations that have been made. To see the individual targets that are run, execute the customer_build.help target.
7. Execute the following command to apply Column Length customizations, if applicable.
ant -f bin/tools.xml custom_column -Dgen.input=<package name>
For example:
ant -f bin/tools.xml custom_column -Dgen.input=wt.doc.*
8. Create a new database user to own the database and load the DDL for the database. This DDL should include declarations of schema objects for storing your custom objects.
9. Execute the windchill wt.load.WindchillLoader command with options of your choice to load the initial dataset for this new database.
10. Start the Windchill server manager and method server, and perform a basic system health check to verify that the test installation functions without errors now that your customizations have been incorporated.
Dealing with Deprecated APIs
With each new release, PTC deprecates some APIs. A deprecation is a Java class, method, or field (that is, an API) that has been marked with the @depricated tag. This tag indicates that the deprecation has been superseded by a new class, method, or field, respectively. If your customizations depend upon APIs that PTC has deprecated, deprecation warnings appear as you compile them. PTC recommends that, as part of the upgrade process, you eliminate the deprecated API with its superseding APIs to fix all source code.
To fix the source code that depends on deprecations, perform the following steps for every customized Java package until all use of deprecations is eliminated:
1. Compile a customized Java package source code to report deprecated warnings.
a. For each deprecation, find the dependent Javadoc HTML page of the Java class and identify the replacement of the deprecated item.
b. Edit your customized Java class to use the replacement of the deprecated item.
c. Repeat steps a and b until all reported deprecations are fixed in the Java package.
2. Repeat the entire process until the Java package recompiles without any deprecation warnings.