WebLogic Deployer Plugin

Plugin Information

Plugin ID weblogic-deployer-plugin
Latest Release 1.0
Latest Release Date Jan 3, 2012
Plugin Central Plugin Central 3.2
Sources Github
Support Eclipse Hudson Forum
Issue Tracking Eclipse Bugzilla
Hudson Core (latest) 3.3.3

This plugin deploy artifacts built on a CI server Hudson to a weblogic target (managed server, cluster ...) as an application or a library component.

Thanks for the contribution of IHD team (a ByTel department).


The plugin supports the artifact deployment to the 9.X weblogic environments. All kinds of component such as library or application (ear, war, ejb-jar) are eligible to the deployment.


This plugin is only applicable for maven Job and works with 9.X weblogic version. The deployment to others weblogic versions has not been tested.

Getting Started

Before use it, The plugin has to be configured. It consists of loading the weblogic environments configuration and adding the weblogic library path (i.e /pathtojar/weblogic.jar) which will be used while deploying artifacts.


System Configuration

<?xml version="1.0" encoding="UTF-8"?>
<config xmlns="http://com.bouygtel.dy.hudson.plugin/WeblogicDeploymentPlugin"
xsi:schemaLocation="http://com.bouygtel.dy.hudson.plugin/WeblogicDeploymentPlugin plugin-configuration.xsd">

NB : the ftpHost/ftpUser/ftpPassowrd/remoteDir are used to deploy libraries. Basically, weblogic.remote.host should be the same as weblogic.admin.server.host

  • Classpath : weblogic.jar file path loaded for deployment. If no value is set but the WL_HOME environment variable is found, the plugin will try to load %WL_HOME%/server/lib/weblogic.jar.
  • Java Options : the java options used by the java process when invoking the weblogic library. By default it will be -Xms256M -Xmx256M.
  • Liste d'exclusion : the built artifacts name pattern excluded from post build deployment action.
  • Desactiver : If checked, the plugin execution is disabled.

Job Configuration

If no configuration has been set, the plugin will display an error message

Here is an example of a hudson job configuration

  • environment : the targeted weblogic environment
  • nom : the name used by weblogic to display component
  • targets : the weblogic target ( can be a managed server instance, a cluster or AdminServer). By default the plugin will use the AdminServer. Many targets can be defined and will be separated by un comma symbol.
  • librairie weblogic : If checked, the generated artifact will be deployed as a library component
  • 'Build en echec si erreur au deploiement' : If checked, The current build will be stated as a failed one if the deployment task failed.
  • 'Strategie de deploiement' : Configure which cause(s) will trigger the deployment action. If 'Non specifie' is selected, the deployment occurs each time the job builds. If another ones are selected, the deployement action only occurs when the build was triggered by a chosen cause.
  • 'Deploiement uniquement sur modifications des sources' : If checked, the deployment action only occurs when the build trigger by a parametrized cause AND the SCM step detects any changes.
  • 'Projets déployés requis' : (experimental) specifies a dependence with others job.

User Guide

View deployment Logs


Release Notes

Version 1.0 (Jan 3, 2012)

Initial release.


Add timeout.
Add configuration file xsd validation.
Hide admin password


plugin-post-build plugin-post-build Delete
tier3-hudson-plugin tier3-hudson-plugin Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.