Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Plugin Information

View WAS Builder on the plugin site for more information.

This plugin allows Hudson to invoke IBM WebSphere Application Server's wsadmin as a build step.

About this plugin

This plugin allows to invoke the wsadmin command of IBM WebSphere Application Server (WAS) 6.0/6.1/7.0 as a build step. It can be used for example to deploy a freshly built application (self-promo: using the RAD Builder Plugin).

This plugin supports:

  • WAS 6.0 (versions 1.0 and 1.1 successfully tested with WAS – should work with other 6.0.2.x versions)
  • WAS 6.1 (not yet tested)
  • WAS 7.0 (version 1.1 successfully tested with Administration Thin Client built from WAS – should work with other 7.0.0.x versions)

User guide

Before adding a WAS build step to a job, the WAS Builder plugin must be configured as follow:

  • First, one or several WAS installations must be defined in Hudson's main configuration panel (cf. upper part of the screenshot below). These WAS installations must not necessarily correspond to some running WAS servers: The plugin simply uses their wsadmin command (the one located in the bin folder of the installed product) to connect to remote servers.
  • Once at least one installation is defined, you need to save the changes and to go back to Hudson's main configuration panel to be able to define the servers that the jobs will use (lower part of the screenshot above).

Once at least one server is defined, it's possible to add some "IBM WebSphere Application Server 6.x/7.x" build steps to your jobs (cf. screenshot below). Most of wsadmin options can be controlled through the GUI. Take a look at the inline help (the little question marks located on the right of each field) to know more about each feature.

The Run if field doesn't correspond to a wsadmin option. It can be used to dynamically enable/disable a build step for a particular run: If Run if is defined (let's say with the STOP_SERVER value) for a build step, then the build step will be run if and only if:

  • a build variable with the same name (in our case, STOP_SERVER) is defined and has a value,
  • or (exclusive) if no build variable with the same name is defined and an environment variable with the same name (still STOP_SERVER in our example) is defined, whether it has a value or nor.

When defining a build step for WAS 6.0, be sure to refer to the inline help to know if you can use it: Some options (job ID, trace file, etc.) are available only for WAS 6.1 or greater.

Version history

Version 1.4 (04/13/2010)

  • The Run if option now allows to use boolean parameters in addition to build or environment variables.

Version 1.3 (04/13/2010)

  • Added an option which allows creating automatically, if the locks-and-latches plugin is installed, one lock per defined WAS server.

Version 1.2 (04/06/2010)

  • Added an option for allowing the wsadmin user/password at the build step level.

Version 1.1 (03/30/2010)

Version 1.0.1 (01/24/2010)

  • Bug fix: Installations defined for slave nodes were not taken into account; The plugin was always referring to the installation on the master node.

Version 1.0 (12/18/2009)

  • Initial release
  • No labels