Installing and Working with J-Link

Installing J-Link

From Creo Parametric 4.0 F000 onward, J-Link is no longer available as a separate installation on the product CD. J-Link is automatically installed when you install Creo Object TOOLKIT Java.

Creo Object TOOLKIT Java is available on the same CD as Creo. When Creo application is installed, one of the optional components is API Toolkits. This includes Creo TOOLKIT, Creo Object TOOLKIT C++, Creo Object TOOLKIT Java and J-Link and so on.

When you select Creo Object TOOLKIT Java and Jlink option, the following directories are created under the Creo loadpoint. J-Link is automatically installed in these directories:

•

<creo_loadpoint>\<version>\Common Files\otk\otk_java—Contains all the libraries specific to Creo Object TOOLKIT Java, which will be used by J-Link application.

•

<creo_loadpoint>\<version>\Common Files\otk_java_doc—Contains documentation files specific to Creo Object TOOLKIT Java, which must be used as reference for J-Link.

•

<creo_loadpoint>\<version>\Common Files\otk_java_free—Contains all the example applications specific to J-Link.

Running J-Link Applications

To run the J-Link applications make the following changes:

•

pfc.jar is no longer supported. The classpath should contain otk.jar instead of pfc.jar.

•

The registry should indicate startup as java. Refer to the section Registry File, for more information.

Standalone Applications

You can start the J-Link application independently at any time, regardless of which models are in session. A registry file contains key information regarding the execution of the program.

Using application programs you can make additions to the Creo Parametric user interface, gather or change data associated with the models in session, or add session-level ActionListener routines. See the section Action Listeners for more information on ActionListeners.

Registry File

A registry file contains Creo Parametric-specific information about the standalone application you want to load.

The registry file called protk.dat is a simple text file, where each line consists of one predefined keyword followed by a value. The standard form of the protk.dat file is as follows:

name             java_demo
startup          java
java_app_class   MyJavaApp
java_app_start   start
java_app_stop    stop
allow_stop       true
delay_start      true
text_dir         <path to text directory used by
                  message and menu related commands>
end

The fields of the registry file are as follows:

•

name—Assigns a unique name to this J-Link application. The name identifies the application when there is more than one in the protk.dat file. The maximum size of the name is 31 characters for the name, plus the end-of-string character.

•

startup—Specifies the method to be used by to communicate with the application. For J-Link applications, set startup to java.

•

java_app_class—Specifies the fully qualified package and name of a Java class. This class contains the J-Link application’s start and stop methods.

•

java_app_classpath—An optional field to specify the full path to the J-Link application classes and archives (including the J-Link archive pfc.jar). Refer to the section CLASSPATH Variables section for more information on the other available mechanisms to set the CLASSPATH. This field has a character limit of 2047 wide characters (wchar_t).

•

java_app_start—Specifies the start method of your program. See the section Start and Stop Methods for more information.

•

java_app_stop—Specifies the stop method of your program. See the section Start and Stop Methods for more information.

•

allow_stop—Stops the application during the session if it is set to true. If this field is missing or set to false, you cannot stop the application, regardless of how it was started.

•

delay_start—Enables you to choose when to start the J-Link application if it is set to true. Creo Parametric does not start the J-Link application during startup. If this field is missing or is set to false, the J-Link application starts automatically.

•

text_dir—Specifies the location of the text directory that contains the language-specific directories. The language-specific directories contain the message files, menu files, resource files and UI bitmaps in the language supported by the J-Link application. The files must be located under a directory called text or text/<language>, if localized messages are used in the application. This field has a character limit of 2047 wide characters (wchar_t).

•

end—Indicates the end of the description of the J-Link application. You can define multiple J-Link applications in the registry files. All these applications are started by Creo Parametric.