Weblogic WLFULLCLIENT

Prior to the release of weblogic server 10.0, weblogic.jar file could be bundled with the client applications to use some advanced features like:
 - Enhanced JDBC and WLS specific JMX interfaces
 - WLS t3 and iiop client

For information on these featuresOracle Link:

But from WLS 10.0, to use these features, wlfullclient.jar is needed by the client applications. If the applications still use weblogic.jar, it may result in a ClassNotFoundException.

wlfullclient.jar is not available for jdk 1.4, it is only supported and can be made for jdk 1.5 and 1.6.

There are 2 ways of creating wlfullclien.jar using the jarBuilder Tool from the installer. Here is an example of creating the jar file for WLS 10.3, jdk 1.6.

Method 1: - Set the java environment.
 - Run the command C:\BEA1036\wlserver_10.3\server\lib>java -jar D:/BEA1036/modules/com.bea.core.jarbuilder_1.2.0.0.jar

Method 2: - Set the java environment.
 - Run the command C:\BEA1036\wlserver_10.3\server\lib>java -jar wljarbuilder.jar -profile wlfullclient

Both the commands create the wlfullclient.jar file in the C:\BEA1036\wlserver_10.3\server\lib directory. This jar file should now be bundled with client applications and should be added to the client application’s classpath for use.

Client	Type	Language	Protocol	Client Class Requirements	Key Features
Java EE Application Client (Thin Client) (Introduced in WebLogic Server 8.1)	RMI	Java	IIOP	wlclient.jar JDK 1.4 and higher	Supports WLS clustering. Supports many Java EE features, including security and transactions. Supports SSL. Uses CORBA 2.4 ORB. See Developing a Java EE Application Client (Thin Client).
JMS Thin Client (Introduced in WebLogic Server 8.1)	RMI	Java	IIOP	wljmsclient.jar wlclient.jar JDK 1.4 and higher	Thin client functionality WebLogic JMS, except for client-side XML selection for multicast sessions and JMSHelper class methods. See WebLogic JMS Thin Client.
JMS SAF Client	RMI	Java	IIOP	wlsafclient.jar wljmsclient.jar wlclient.jar JDK 1.4 and higher	Locally stores messages on the client and forwards them to server-side JMS destinations when the client is connected. See Reliably Sending Messages Using the JMS SAF Client.
T3	RMI	Java	T3	wlfullclient.jar	Supports WLS-Specific features. Fast, scalable. No CORBA inter-operability. See Developing T3 Clients.
J2SE	RMI	Java	IIOP	no WebLogic classes	Provides connectivity to WLS environment. Does not support WLS-specific features. Does not support many Java EE features. Uses CORBA 2.3 ORB. Requires use of com.sun.jndi.cosnaming. CNCtxFactory. See Developing a J2SE Client.
WLS-IIOP (Introduced in WebLogic Server 7.0)	RMI	Java	IIOP	wlfullclient.jar	Supports WLS-Specific features. Supports SSL. Fast, scalable. Not ORB-based. See Developing a WLS-IIOP Client.
JMX	RMI	Java	IIOP	wljmxclient.jar	See Accessing WebLogic Server MBeans with JMX.
WebServices	SOAP	Java	HTTP/S	wseeclient.jar	See Invoking a Web Service from a Stand-alone Client.
CORBA/IDL	CORBA	Languages that OMG IDL maps to, such as C++, C, Smalltalk, COBOL	IIOP	no WebLogic classes	Uses CORBA 2.3 ORB. Does not support WLS-specific features. Does not support Java. See Developing a CORBA/IDL Client.
C++ Client	CORBA	C++	IIOP	Tuxedo libraries	Interoperability between WLS applications and Tuxedo clients/services. Supports SSL. Uses CORBA 2.3 ORB. See Developing a WebLogic C++ Client for a Tuxedo ORB.
Tuxedo Server and Native CORBA client	CORBA or RMI	C++	Tuxedo- General- Inter-Orb-Protocol (TGIOP)	Tuxedo libraries	Interoperability between WLS applications and Tuxedo clients/services. Supports SSL and transactions. Uses CORBA 2.3 ORB. See Developing Clients for CORBA Objects.