Select Page

Apache Maven BEA Weblogic 10.3 remote deployment

Apache Maven BEA Weblogic 10.3 remote deployment

In this small post I will show you how to deploy automatically some artifacts of your build into Weblogic 10.3 by using the weblogic-maven-plugin

This plugin will support various tasks within the Weblogic 8.1 and 9.x environment. Such tasks as deploy, undeploy,clientgen,servicegen, and appc are supported as well as many others. The plugin uses exposed API’s that are subject to change but have been tested in 8.1 SP 4-6 and 9.0 – 9.2 MP3. There are two versions of the plugin to support the two environments based on differences in the JDK. The 9.x version is currently being refactored to support the standard JSR supported deployment interface

Weblogic Admin Console

In the protocols section of your Admin server settings page verify that Enable Tunneling is checked (Environment – Server – Protocols).

Preparing Maven dependencies

In a Weblogic 10.3 JDK 1.6 environment the weblogic-maven-plugin requires 17 dependencies!

  • bea\modules\com.bea.core.descriptor.wl_1.1.0.0.jar
  • bea\modules\com.bea.core.descriptor_1.4.0.0.jar
  • bea\modules\
  • bea\modules\
  • bea\modules\com.bea.core.weblogic.lifecycle_1.1.0.0.jar
  • bea\modules\
  • bea\modules\
  • bea\modules\
  • bea\modules\com.bea.core.weblogic.security_2.0.1.0.jar
  • bea\modules\com.bea.core.weblogic.socket.api_1.0.0.0.jar
  • bea\modules\com.bea.core.weblogic.workmanager_1.4.0.0.jar
  • bea\modules\javax.enterprise.deploy_1.2.jar
  • bea\wlserver_10.3\server\lib\wljmsclient.jar
  • bea\wlserver_10.3\server\lib\wls-api.jar
  • bea\wlserver_10.3\server\lib\wlsafclient.jar
  • bea\wlserver_10.3\server\lib\weblogic.jar
  • bea\wlserver_10.3\server\lib\webserviceclient.jar

but this can be reduced to just two by creating an uber jar wlfullclient.jar.

Use the following steps to create a wlfullclient.jar file for a JDK 1.6 client application:

  1. Change directories to the server/lib directory.
    cd WL_HOME/server/lib
  2. Use the following command to create wlfullclient.jar in the server/lib directory:
    java -jar wljarbuilder.jar

You can now deploy this huge jar file wlfullclient.jar  (59 MB) to either your Artifactory/Nexus/Archiva repository.


We need another jar file, this one can be find in bea/modules directory. Install also com.bea.core.descriptor.wl_1.1.0.0.jar into your local maven repository


We are nearly ready, just add your deployment in a profile that is not active by default. This will allow you to deploy only in some special build with –P{profileName} in your continuous server (Hudson/Teamcity/Bamboo)

        <properties> </properties> 
            <plugins> </plugins> 

Here is the whole plugin configuration that you have to put between as usual



  • It is important that is set to true or maven will exit improperly!
  • Define your password as usual in settings.xml
  • Variables ${xxxx}  are self explanatory, use correct values in section of your profile

Good luck! Feel free to ask below if you have any questions.


About The Author

Cédric Walter

I worked with various Insurances companies across Switzerland on online applications handling billion premium volumes. I love to continuously spark my creativity in many different and challenging open-source projects fueled by my great passion for innovation and blockchain technology.In my technical role as a senior software engineer and Blockchain consultant, I help to define and implement innovative solutions in the scope of both blockchain and traditional products, solutions, and services. I can support the full spectrum of software development activities, starting from analyzing ideas and business cases and up to the production deployment of the solutions.I'm the Founder and CEO of Disruptr GmbH.