|
|
 |
|
|
|
|
|
|
|
Home->Support->Knowledge Base
|
|
|
Title: Enabling java classes to be used as Client Objects in BBj
Description: Any Java class(es) (and any native code that the Java class(es) depend(s) on) that are to be used as client objects in BBj must reside on the client machine as well as on the server machine.
On the server machine the class(es) should be in a jar (or directory) which is specified in the BBjServices CLASSPATH, this can be set using the Enterprise Manager.
The class(es) must also exist on the client in a registered jar, see Jar Registration in the documentation, or a developer license (DVK) must be used. or a nag message will appear. If the client is running BBjServices, then the registered jar must be in BBjServices CLASSPATH, which a can be set using the Enterprise Manager. If the client is a WebStart client then the JNLP file must specify all necessary jars (including jars with native code) to be downloaded to the client. These jars must be signed and put in the directory as specified by the JNLP
Resolution: To run the TechCon Demos (for example) which use Java client objects in BBj, where some of the classes depend on native code, the following must be done:
1) Add Jars to the server's BBjServices CLASSPATH via Enterprise Manager, that contain the java classes that are to be uses as client object.
For the TechCon07 demos this includes the following jar files found in the BBj install directory (when the demos are installed):
BBjThinClient.jar (BBj Jar)
ThirdParty.jar ((BBj Jar)
FontChooser.jar (BBj Jar)
BBjIndex.jar (BBj Jar)
TechConDemosClientFiles.jar
ClientObjects.jar
examples.jar
jfreechart-experimental.jar
jna.jar
swingx.jar
TimingFramework.jar
jic.jar
2) Make sure any native code that these Java classes depend on is in the <bbj install dir/lib directory. For the Techcon07 demos this includes the following for Windows:
jdic.dll
IeEmbed.exe
MozEmbed.exe
3) Register all non Bbj Jars listed in number 1 so that they can be used on the client without being in nag mode. Or get a Developer's license (DVK) from BASIS.
4) If the client is running BBjServices add all the jars listed in step 1 to the BBjServices CLASSPATH via Enterprise Manager. Skip steps 5-7.
5) If the client is running in WebStart, add all native code (for each client platform to be run) to a jar
<jdk install dir>/bin/jar cvf win32-native.jar jdic.dll IeEmbed.exe MozEmbed.exe
6) If the client is running in WebStart, add all jars listed in step 1 and the jar created in step 5 to the JNLP file:
href="LaunchDock.jnlp">
<information>
<title>TechCon07 LaunchDock</title>
<vendor>BASIS International Ltd.</vendor>
<description>LaunchDock</description>
<icon kind="splash" href="BBjEnv.bmp"/>
</information>
<security>
<all-permissions/>
</security>
<resources>
<j2se version="1.5+" inital-heap-size="256m" max-heap-size="256m"/>
<jar href="BBjThinClient.jar"/>
<jar href="ThirdParty.jar"/>
<jar href="FontChooser.jar"/>
<jar href="BBjIndex.jar"/>
<jar href="TechConDemosClientFiles.jar"/>
<jar href="ClientObjects.jar"/>
<jar href="examples.jar"/>
<jar href="jfreechart-experimental.jar"/>
<jar href="jna.jar"/>
<jar href="swingx.jar"/>
<jar href="TimingFramework.jar"/>
<jar href="jdic.jar" />
</resources>
<resources os="Windows">
<nativelib href="webstart2166.jar"/>
<nativelib href="win32-native.jar"/>
</resources>
<application-desc main-class="com.basis.bbj.client.comm.WebStartLauncher">
<argument>-tT2</argument>
<argument>-c"/usr/local/bbj/demos/techcon07/config.bbx"</argument>
<argument>-WD"/usr/local/bbj/demos/techcon07/Workbench"</argument>
<argument>-RHsting3</argument>
<argument>-INFsting3</argument>
<argument>TechConLaunchDock.bbj</argument>
</application-desc>
</jnlp>
7) Sign all jars and put them in the directory as specified in the JNLP.
Last Modified: 04/09/2008
Product: BBj
Operating System: N/A All platforms
|
|
|
| |
|
 |
| |
Copyright 1985 - 2008, BASIS International Ltd. All rights reserved.
5901 Jefferson Street NE, Albuquerque, NM 87109-3432 505.345.5232, info@basis.com
|
|
