![Close [x]](http://dw1.s81c.com/i/c.gif){kind=small}
This article describes how to construct an automated build engine solution for applications developed using IBM WebSphere Integration Developer and maintained using Rational ClearCase as the Software Configuration Management system (SCM). It explains the overall approach used to construct the automated build engine, describes the inhibiting limitation in the current product set, provides a workaround in the form of a plug-in for WebSphere Integration Developer and provides a set of sample build scripts that show how to automate your builds.
Software development project managers frequently require an automated software build process to maximize the efficiency of the development-build-test cycle. A software build process that depends on human interaction is generally error prone, time consuming, and lacks scalability when the number of build artifacts increases significantly.
While the IBM® software portfolio provides the necessary capabilities to support a build automation solution for J2EE applications, you currently cannot automate the building of Service Component Architecture (SCA) applications developed using WebSphere® Integration Developer (hereafter called Integration Developer) V6. Integration Developer facilitates the development of SCA applications for business integration, using technologies such as BPEL business processes, business rules components, business state machines, and WebSphere Enterprise Service Bus (hereafter called ESB) mediation flows. You deploy SCA applications developed with Integration Developer to either a WebSphere Process Server (hereafter called Process Server) runtime, or to an ESB runtime.
This article describes the limitation that currently prevents successful implementation of an automated build engine for these types of applications, and provides an effective workaround. By employing the techniques described in this article and using the provided plug-in for Integration Developer, you can quickly and easily automate builds for applications developed using Integration Developer. If you’re feeling adventurous, we provide detailed instructions on how to write these scripts yourself, or you can cut to the chase, download our build scripts, and start using them right away.
Virtually every build automation system must acquire source code artifacts from a software configuration manager (SCM) such as Rational® ClearCase or CVS. This article describes an approach that uses Rational ClearCase as the SCM. You can use the techniques, WebSphere Integration Developer plug-in, and build scripts in an environment that uses CVS or another SCM with minimal modification.
This article assumes that you have a basic knowledge of service component architecture (SCA), Eclipse, ClearCase, Ant and the serviceDeploy functionality of WebSphere Integration Developer.
Isabelle Mauny, Application and Integration Middleware Software, Pan-European Lab Services Team, provided very valuable feedback during development of this article.
Grant Taylor, Application and Integration Middleware Software, WebSphere Integration Developer Team, developed the plug-in and provided extremely valuable technical and strategic assistance that helped us in the development of this solution.
John Ganci, Scenario Analysis Lab, provided Rational ClearCase infrastructure that helped us to develop the build scripts.
Chad L Smith, Federated Integration Test, provided technical expertise for the development of the Version 1 of this solution.
Jonas Richard, Federated Integration Test, provided technical expertise for the development of the Version 1 of this solution.
| Description | Name | Size | Download method |
|---|---|---|---|
| Article in PDF format | 0711_manekar.pdf | 561KB | HTTP |
| SCA Build Engine zip file | scabuildengine.zip | 7KB | HTTP |
| code sample utilities | com.ibm.wbit.modulerefutil_1.0.0.zip | 4KB | HTTP |
Information about download methods Get Adobe® Reader®
Learn
-
WebSphere Integration Developer Information Center
-
Apache Ant documentation
-
Ant-contrib documentation
-
Deploying applications using ServiceDeploy Ant Task
-
ServiceDeploy command
-
Exporting modules as serviceDeploy files
-
Performing unattended daily builds with WebSphere Studio and Ant -- Part 1
-
Performing unattended daily builds with WebSphere Studio and Ant -- Part 3
-
Team development with WebSphere Integration Developer and WebSphere Process Server: Developing applications using CVS
-
Introduction to packaging in WebSphere Process Server
Get products and technologies
Discuss
Ashwin Manekar is a Solution Test Engineer in the WebSphere Solution Test department at IBM, Raleigh. Ashwin holds a MS degree in Computer Science from the University of North Carolina, Charlotte. You can reach Ashwin at amaneka@us.ibm.com .
David Leigh is an Architect in the IBM SWG Scenario Analysis Lab at the RTP Lab in Durham, NC. You can reach David at dleigh@us.ibm.com.
