JBoss.orgCommunity Documentation

RiftSaw 2.2.0.Final

Getting Started Guide

  1. JBossAS (version 5.1.0.GA or higher) jdk6 version, available from http://www.jboss.org/jbossas, and please upgrade the web service stack to version 3.2.2.GA, as described in the following 'Upgrade web service for JBoss AS' section.
  2. JBossESB (version 4.9 or higher), should download the jbossesb-4.9.zip, available from http://www.jboss.org/jbossesb. This is only required to run the ESB/BPEL examples.
  3. RiftSaw, available from http://www.jboss.org/riftsaw
  4. Ant, available from http://ant.apache.org
  1. Install JBossAS

    Unpack the JBossAS installation into the required location.

  2. Install JBossESB

    This is only required if you want to run the ESB/BPEL examples.

    Unpack the JBossESB installation into a location alongside the JBossAS installation. Then follow the instructions in the JBossESB installation (install/readme.txt), to deploy JBossESB into the JBossAS environment.


    If you intend to install the jbossesb, it must be deployed to the application server before riftsaw.

  3. Install the RiftSaw distribution

    Unpack the RiftSaw distribution into a location alongside the JBossAS installation.

    • Edit the install/deployment.properties file to update the JBossAS location, JBoss AS instance, database and JBossESB location.
    • From the install folder, run:

      ant deploy -Ddatabase=... -Dws.stack=... -Dws.version=...

      to deploy RiftSaw to JBossAS, specifying a database and mandating the upgrade of the web service stack for JBossAS. The list of available databases, and how they should be configured, is explained in the next sub-section; the list of options for update of the web service stack is discussed in the one following it.


      Please note that RiftSaw should not be deployed while JBoss AS is running.


    The above installation steps are meant to be for riftsaw single server deployment, if you want to deploy riftsaw that supports clustering, you either need to specify the JBoss AS instance as 'all' config, or add '-Dclustering.support=true' in the command line. For detail, please refer to userGuide's RiftSaw Clustering Support chapter.

To de-install the RiftSaw distribution,

This chapter provides a getting started guide to the examples. Further information on the individual examples can be found in the samples folder.

If using the Eclipse BPEL editor, bundled with JBoss Tools, then you can import the quickstart samples as Eclipse BPEL projects, by selecting the import menu item on the left navigation panel in Eclipse, and choosing the General->Existing Projects into Workspace option. Then select the individual sample you wish to import, or alternatively select the ${RiftSaw}/samples/quickstart folder to select multiple (or all) samples for import. Please see the RiftSaw User Guide for information on how to deploy the BPEL samples to the server.

Before deploying any of the examples, you need to start the JBossAS server and ensure that RiftSaw has been installed. This can be achieved by testing whether the BPEL Console (as discussed in the User Guide) is available.

The BPEL example we are going to try out is the simple 'hello world' example. This is located in the ${RiftSaw}/samples/quickstarts/hello_world folder.

The first step is to deploy the example to the running JBossAS server. This is achieved using the following command:

ant deploy

When the ant script indicates that it has completed successfully, the next step is to invoke the BPEL process we have just deployed.

This can be achieved using either the supplied ant script,

ant sendhello

Or by using any SOAP client, such as SOAPUI (available from http://www.soapui.org/).

The WSDL definition is located in the bpel folder, and can be used to initialise the SOAPUI client. The service location is: http://localhost:8080/Quickstart_hello_worldWS.

An example message can be found in the messages subfolder.

When the message is submitted to the BPEL process, the response received is:

If you then wish to modify the example and deploy a new version, you will need to either update the 'version' property within the build.xml, or specify the version when performing the command, e.g.

ant -Dversion=2 deploy

and similarly when undeploying,

ant -Dversion=2 undeploy


When modifying a previously deployed BPEL deployment, it will be necessary to either undeploy the previous version, or increment the version number. If you attempt to deploy a BPEL deployment unit with the same name as an already deployed unit, then the server will generate an exception.


Currently the version must be specified as a single integer value. Non-numeric values, such as versions expressed in a major.minor.incremental (maven style), will result in an exception when deployed to the server.