Plugin Information

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).

General

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.

Pre-requisites

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.

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.