Download Wl!!TOP!! Fullclient.jar
Zelda Diomede
For future reference: Following better_use_mkstemp's suggestion (on WLS v12.1.2.0.0), then running wljarbuilder resulted in an incomplete "wlfullclient.jar". - Among others, the cruicial weblogic.jndi.WLInitialContextFactory was missing.
So what I did was to copy wlclient.jar to "weblogic-classes.jar" and, via wljarbuilder, got myself a single, working "wlfullclient.jar".(Make sure you delete the redundant "weblogic-classes.jar" afterwards to avoid future trouble.)
The developer version of WebLogic misses some features. You could reinstall a new instance of WebLogic by the installers.Or as I did, you could run the oracle provided WebLogic docker. It generates a wlfullclient.jar nicely. I just recently did it.
The WebLogic full client, wlfullclient.jar, is deprecated as of WebLogic Server 12.1.3 and may be removed in a future release. Oracle recommends using the WebLogic Thin T3 client or other appropriate client depending on your environment. For more information on WebLogic client types, see Table 2-1.
If you run the WebLogic Full Client from a 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.
For WebLogic Server 10.0 and later releases, client applications need to use the wlfullclient.jar file instead of the weblogic.jar. A WebLogic full client is a Java RMI client that uses Oracle's proprietary T3 protocol to communicate with WebLogic Server, thereby leveraging the Java-to-Java model of distributed computing. For more information on WebLogic T3 communication, see "Using WebLogic RMI with T3 Protocol" in Developing RMI Applications for Oracle WebLogic Server.
Not all functionality available with weblogic.jar is available with the wlfullclient.jar. For example, wlfullclient.jar does not support Web Services, which requires the wseeclient.jar. Nor does wlfullclient.jar support operations necessary for development purposes, such as ejbc, or support administrative operations, such as deployment, which still require using the weblogic.jar.
This error is caused by the self-integrity check that is automatically performed when the RSA Crypto-J library is loaded. (The Crypto-J library, cryptoj.jar, is in the wlfullclient.jar manifest classpath.)
"We are upgrading from WebLogic 10.3.5.0 to 12.2.1.3. Our existing 10.3.5.0 system uses wlfullclient.jar. I understand that this has been deprecated and we are supposed to move to wlthint3client.jar, but that jar is missing a lot of other jars that were conveniently located in the wlfullclient.jar.
When we switch to the wlthint3client.jar, what is the best strategy to ensure the jars that are in wlfullclient.jar but not in wlthint3client.jar are included? Seems like there are 100s of them, which is why the wlfullclient was created per my understanding".
For WebLogic Server 10.0 and later releases, client applications need to use the wlfullclient.jar file instead of the weblogic.jar. A WebLogic full client is a Java RMI client that uses Oracle's proprietary T3 protocol to communicate with WebLogic Server, thereby leveraging the Java-to-Java model of distributed computing. For information on developing RMI applications, see Understanding WebLogic RMI. You cannot integrate clients written in languages other than Java.
Recently I was assigned a task to separate all our old oracle based authentication (using OIM (Oracle Identity Manager) which in turn uses wlfullclient.jar) code into a war file. The project structure is as follows:
We use maven to construct the final ear file. The issue now is that if I exclude the wlfullclient.jar file from the authentication.war file by using provided maven scope, I will see the below error at deployment time
Our system admin found a note (maybe from Oracle before) mentioned that wlfullclient.jar is needed. So I then changed the provided scope to compile scope for this jar and redeployed again. I received the below:
If you use authentication mode, you should replace in WLS 12wlfullclient.jar by wlthint3client.jar. If you have to add manydependencies you can append them like that/path/to/wulfullclient.jar:/path/to/wlthint3client.jar. Theseparator ':' is platform dependent.
"The WebLogic full client, wlfullclient.jar, is deprecated as ofWebLogic Server 12.1.3 and may be removed in a future release. Oraclerecommends using the WebLogic Thin T3 client or other appropriate clientdepending on your environment. For more information on WebLogic clienttypes, see WebLogic Server Client Types and Features."
When deploying to Tomcat, we ran into issues with wlfullclient.jar. the vgn-appsvsc-cma.jar is dependent on the wlfullclient.jar. First of all, it seems weird to be deploying a web app containing wlfullclient.jar to Tomcat, since wlfullclient.jar originates from Weblogic. Here is the deployment error on Tomcat:
Class org.glassfish.tyrul.server.TyrusServerConfiguration exists in wlfullclient.jar which is why we believe it is related to this error. I think this may be a classloader issue that could possibly be resolved, but we have not found the solution yet.
Can someone please help us get back on track here. The Content Management SDK Developer Guide indicates that we should be able to use the API in a web application. Since the cma jar is dependent on wlfullclient.jar, I am leaning toward trying to make work on Weblogic instead of Tomcat. However, I am open to working solutions.
When deploying to Tomcat, we ran into issues with wlfullclient.jar. thevgn-appsvsc-cma.jar is dependent on the wlfullclient.jar. First of all, it seems weird to be deploying a web app containing wlfullclient.jar to Tomcat, since wlfullclient.jar originates from Weblogic. Here is the deployment error on Tomcat:
JBAS015960: Class Path entry schema/weblogic-domain-binding.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Path reference.
JBAS015960: Class Path entry schema/diagnostics-binding.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Path reference.
JBAS015960: Class Path entry schema/diagnostics-image-binding.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid
JBAS015960: Class Path entry schema/kodo-conf-binding.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for
JBAS015960: Class Path entry wlcipher.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Path re
JBAS015960: Class Path entry xmlx.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Path refere
JBAS015960: Class Path entry jconn2.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Path refe
JBAS015960: Class Path entry jConnect.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Path re
JBAS015960: Class Path entry EccpressoAsn1.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Pa
JBAS015960: Class Path entry EccpressoCore.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Pa
JBAS015960: Class Path entry EccpressoJcae.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Pa
JBAS015960: Class Path entry mysql-connector-java-commercial-5.0.3-bin.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point t
JBAS015960: Class Path entry wlbase.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Path refe