Sample Applications for J-Link
This section lists the sample applications provided with J-Link.
Sample Applications
The J-Link sample applications are available in the location <creo_jlink_loadpoint>.
Note
You must set the configuration option regen_failure_handling to resolve_mode in the Creo Parametric session before running the sample application install_test. From Creo Parametric2.0 M060 onward, a configuration file (config.pro) has been provided for the install_test application. The config.pro contains the regen_failure_handling option.
InstallTest
Location
Main Class
<creo_jlink_loadpoint>/otk_java_appls/install_test
StartInstallTest
The application StartInstallTest is used to check the J-Link synchronous installation. It verifies the following:
•  Application start and stop functions.
•  Menubar functions.
•  Custom UI functions.
•  Sequences, arrays, exceptions, and action listener functions.
Testing the J-Link Synchronous Installation
After the system administrator has installed J-Link, compile, link, and run a simple J-Link application on the machine you intend to use for development. Test if the installation of J-Link is present, complete, and visible from your machine.
To test the synchronous J-Link installation:
1. Set the path and CLASSPATH variables to include the Java Development Kit as described in Java Options and Debugging.
2. Set the CLASSPATH to include the J-Link synchronous archive and the current directory.
On Windows set the CLASSPATH as: 
set CLASSPATH=<creo_loadpoint>\<version>\Common Files
\text\java\otk.jar;%CLASSPATH%
3. Compile the java files in the directory using the command javac *.java.
Note
The java file AsyncInstallTest.java is not compiled because it is used in the asynchronous mode only. Before compiling, rename this file to a non-Java file, that is, AsyncInstallTest.bak.
4. Create a config.pro file if you are using Java 1.1. Add the following line to this file:
jlink_java2   off
Note
For more information on the supported JDK versions for synchronous J-Link refer to http://support.ptc.com/partners/hardware/current/support.htm.
5. Run Creo Parametric.
The Creo Parametric File menu has a new button, added by the J-Link application, called J-Link Install Test. When you choose this button, the J-Link application displays a custom dialog indicating whether the installation test has succeeded:
Image
Note
On Windows the results dialog may appear behind the Creo Parametric window. Use Atl-Tab to switch to the Java dialog.
InstallTest
Location
Main Class
<creo_jlink_loadpoint>/otk_java_appls/install_test
AsyncInstallTest
The application AsyncInstallTest is used to check the J-Link asynchronous installation. It verifies the following:
•  Asynchronous J-Link setup
•  Creo Parametric start and stop methods
•  Menubar functions
•  Custom UI functions
•  Sequences, arrays, exceptions, and action listener functions
Testing the J-Link Asynchronous Installation
To test the asynchronous J-Link application:
1. Set the path and CLASSPATH variables to include the Java Development Kit as described in Java Options and Debugging.
2. Set the CLASSPATH to include the J-Link asynchronous archive and the current directory.
On Windows set the CLASSPATH as: 
set CLASSPATH=<creo_loadpoint>\<version>\Common Files
\text\java\pfcasync.jar;%CLASSPATH%
3. Set the library path to include the asynchronous library and make sure that PRO_COMM_MSG_EXE is set.
On Windows set the library path as: 
set path=<creo_loadpoint>\<version>\Common Files\<machine type>\lib;%PATH%
set PRO_COMM_MSG_EXE=<creo_loadpoint>\<version>\Common Files
\<machine type>\obj\pro_comm_msg.exe
4. Compile the java files in the directory using the command javac *.java.
Note
•  The java file StartInstallTest.java does not get compiled as it is used in the synchronous mode only. Before compiling, rename this file to a non-java file, that is, StartInstallTest.bak.
•  Remove any .class files compiled previously using synchronous J-Link.
•  Rename or remove the registry file (creotk.dat, protk.dat, or prodev.dat) from the location from where you are running the J-Link asynchronous test.
5. Run the application java [asynchronous flags] AsyncInstallTest <command to run Creo Parametric>.
jlinkexamples
Location
Main Class
<creo_jlink_loadpoint>/otk_java_appls/jlinkexamples
pfcExamplesMenu.java, however note that not all examples may be tied to this class.
The application jlinkexamples is a collection of the example source files for J-Link. It covers most of the areas of J-Link.
jlinkasyncexamples
Location
Main Class
<creo_jlink_loadpoint>/otk_java_appls/jlinkasyncexamples
Many independent examples
The application jlinkasyncexamples is a collection of the asynchronous example source files for J-Link.
Parameter Editor
Location
Main Class
<creo_jlink_loadpoint>/otk_java_appls/jlink_param
com.ptc.jlinkdemo.parameditor.ParamEditor
The parameter editor example demonstrates a synchronous J-Link user interface that governs parameters and parameter values in the model. Setup and run the J-Link Parameter Editor example using the following:
1. Set the path and CLASSPATH variables to include the Java Development Kit as described in Java Options and Debugging.
2. Set the CLASSPATH to include the jlink_param directory and the J-Link synchronous Jar file (otk.jar). Refer to the section Testing the J-Link Synchronous Installation for more information on setting the CLASSPATH.
3. Compile the code.
On Windows, execute the batch file compile.bat.
4. Start Creo Parametric from a directory containing the protk.dat file. Create or retrieve any model that contains parameters.
5. Select J-Link Parameter Editor from the Applications Menu. The system will display a graphical interface that contains a list of parameters for the selected model as shown in the following figure.
Image
The parameter editor also supports the following customized types of parameters:
•  Use the editor to create parameters with descriptive names (user interface names) of up to 80 characters. The value of the assigned user interface name will be displayed as the parameter name in the J-Link user interface.
•  Creating parameters that follow specific rules:
○  Enumerated lists
○  Specified ranges
○  Specified ranges, with values limited to a certain increment (for example, any multiple of 5 between 0 and 100).
When you open the J-Link user interface, the parameter value is governed by the rules assigned to it. If the parameter value is changed to fall outside the permitted values it will be highlighted in red.
Round Checker Utility
Location
Main Class
<creo_jlink_loadpoint>/otk_java_appls/jlink_elev
com.ptc.jlinkdemo.round.RoundChecker
The round checker example demonstrates a synchronous J-Link utility that monitors the values assigned to round dimensions. If the value of any modified or newly created round is reduced below a programmed limit, a J-Link user interface will appear with information about the violation.
Use the following steps to setup and run the example:
1. Set the path and CLASSPATH variables to include the Java Development Kit.
2. Set the CLASSPATH to include the jlink_elev directory and the J-Link synchronous jar file (otk.jar).
3. Compile the code.
On Windows, execute the batch file compile.bat.
4. Load any Creo Parametric model with rounds. Modify the round to less than 0.5. A J-Link dialog that identifies the problem will be displayed. The same dialog will appear if a new round that does not adhere to the specified dimensions is created.
Save Check Utility
Location
Main Class
<creo_jlink_loadpoint>/otk_java_appls/jlink_elev
com.ptc.jlinkdemo.savecheck.SaveChecker
The save check example demonstrates a synchronous J-Link utility that presents a user interface that identifies if any problems exist in the model you are about to save. If any problems exist in the assigned parameter values or if a material has not been assigned to a part, the user interface will appear with information about the problems.
The instructions to setup and run the save check example is similar to the instructions for the round checker utility. To access the interface, choose Tools ▶ Perform Release Checks.