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

Version 1 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.

The WAS Builder plugin has not yet been released.

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 (version 1.x successfully tested with WAS 6.0.2.15 – should work with other 6.0.2.x versions)
  • WAS 6.1 (won't be tested)
  • WAS 7.0 (not tested yet)

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. 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 be able to use:

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 disable a build step for a particular run: If Run if (let's say with the STOP_SERVER value) is defined 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 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

  • No history for the moment: The plugin has not yet been released (coming very soon).
  • No labels