This chapter describes how to create the wlfullclient.jar
using the WebLogic JarBuilder tool.
Note:
If you run the WebLogic Full Client from a <java>
task that is invoked in an Ant script, see Running the WebLogic Full Client in a Non-Forked VM, for important information regarding the RSA Crypto-J library, which is included in the wlfullclient.jar
manifest classpath.
Use the following steps to create a wlfullclient.jar file for a JDK 1.7 client application:
Change directories to the server/lib
directory.
cd WL_HOME/server/lib
Use the following command to create wlfullclient.jar in the server/lib
directory:
java -jar wljarbuilder.jar
You can now copy and bundle the wlfullclient.jar
along with cryptoj.jar
with client applications. The wlfullclient.jar
and cryptoj.jar
must be kept in the same directory as the wlfullcient.jar
references cryptoj.jar
in its manifest Class-Path.
Add the wlfullclient.jar
to the client application's classpath.
Note:
JDK 1.7 introduces new manifest file attributes in Update 25 (JDK 7u25). Only the main jar of the Applet or Web Start deployment requires the new permissions attribute. Do not modify the cryptoj.jar
which is a licensed signed jar. See http://www.oracle.com/technetwork/java/javase/7u25-relnotes-1955741.html#jar-att.
Use the following steps to create a wlfullclient.jar file for a JDK 1.6 client application:
Change directories to the server/lib
directory.
cd WL_HOME/server/lib
Use the following command to create wlfullclient.jar in the server/lib
directory:
java -jar wljarbuilder.jar
You can now copy and bundle the wlfullclient.jar
along with cryptoj.jar
with client applications. The wlfullclient.jar
and cryptoj.jar
must be kept in the same directory as the wlfullcient.jar
references cryptoj.jar
in its manifest Class-Path.
Add the wlfullclient.jar
to the client application's classpath.