This section describes how to set up an environment for using JBK Plugin.
To execute an applet with JBK Plugin, check the following points:
Software Requirements
JBK Plugin requires the following software products:
Web browser
JDK or JRE
JBK runtime
For the method of setting an environment for executing each product, see the manual included in the product.
Locations of the Applet Class and the HTML File
The applet class and HTML file for executing the applet can be stored in the same way as when they are stored to execute a usual applet by a browser. Choose either of the following depending on the method of applet execution:
Store the applet class and the HTML file in the Web server. The applet is downloaded into the client machine and executed.
Store the applet class and the HTML file in the client machine. The applet is executed in the local environment of the client machine.
For executing an applet with JBK Plugin, an HTML file must have a tag for JBK Plugin in it, instead of a usual <APPLET> tag. See '2.2.3 How to Create an HTML File for JBK Plugin' for the detail.
Setting of a browser
The following settings are needed according to a browser used.
Up to now,the single thread model made control module (f5cxwpie.ocx) of the JBK Plugin. However, the problem that the applet is not correctly displayed when it opens an empty window when using it in the environment since Internet Explorer 5 and the applet is displayed there might occur. Therefore, f5cxwpie.ocx was changed to the apartment thread model.
Please do the following work when you use f5cxwpie.ocx of the single thread model:
Please replace "[JBK installation folder]\bin\single\f5cxwpie.ocx" with "[JBK installation folder]\bin\f5cxwpie.ocx".(Please take the backup in "JBK installation folder \bin\f5cxwpie.ocx" to restore it to the apartment thread model. )
Please execute the following command.
regsvr32 /u [JBK installation folder]\bin\f5cxwpie.ocx |
Please work by using the backup of "JBK installation folder \bin\f5cxwpie.ocx" according to the same procedure when you restore f5cxwpie.ocx from the single thread model to the apartment thread model.
Setting Environment Variables
JBK plugins use the following environment variables on the client machine when in use:
If the setting has already been made, the setting need not be changed.
If some classes are installed in the client machine and the applet uses the classes, set the path to the classes into the CLASSPATH. Unlike Java Plug-in, JBK Plugin by default uses the CLASSPATH environment variable when executing applets.
Class paths when Java VM used
The Java VM uses two class paths: a boot class path required for Java VM startup and a user class path for execution of applets. JBK Plugin internally sets a specific boot class path at runtime.
For information about the specific boot class path, see the following:
JAR file containing the JBK Plugin classes, i.e.,
"(JBK installation folder)\classes\jbkplugin2.jar" or "(JBK installation folder)\classes\jbkplugin4.jar"
(when "-Xbootclasspath" is specified for the Java VM startup option)
Boot class path specified for the startup option
(when "-Xbootclasspath" is not specified for the Java VM startup option)
Default boot class path of the JavaSE used for the Java VM
The JavaSE default boot class path includes the paths to "rt.jar", "i18n.jar", "jce.jar", "jsse.jar" and "charsets.jar" used by JavaSE.
When the user class path is used,
(when "-classpath" or "-cp" is specified for the Java VM startup option)
the class path specified in the startup option, or
(when "-classpath" or "-cp" is not specified for the Java VM startup option)
the class path specified in the CLASSPATH environment variable
is used. When Java Plug-in is used or if the "CLASSPATH" environment variable does not need to be used, setting the following property in the jbkplugin.properties file disables the CLASSPATH environment variable settings:
jbk.plugin.sw.classpath.use_env=<use-CLASSPATH-environment-variable> |
In <use-CLASSPATH-environment-variable>, specify either of the following:
When the CLASSPATH environment variable settings will be used to start the Java VM.
When the CLASSPATH environment variable settings will not be used to start the Java VM.
Note that the jbk.plugin.sw.classpath.use_env default value is true (use the environment variable).
Note
In the "-Xbootclasspath" startup option, do not include any boot class paths of JavaSEs whose version is different from the one that you intend to use.
If you do so, an incorrect version may be called for Java VM execution, and an incorrect operation or Java VM execution error may result. In addition, downloading classes existing in the CLASSPATH environment variable for applet execution from a Web server may cause a security exception. To guard against such errors, set the class path by adding the -classpath option to the Java VM startup option or set the property above to "false."
