 | Mr.
Spencer
T.
Murata
(murata@us.ibm.com), Software Engineer, Technical Support Professional,
IBM
13 May 2008 This article is a supplement to the information documented in IBM® Rational® Build Forge® Help, and it provides some additional insight into what a Build Forge Adaptor is.
System requirements
Although this article is applicable to adaptors in general, for any version of IBM® Rational® Build Forge®, the specific examples here are only applicable to Version 7.0.1 and later.
Overview
As a process automation tool, Build Forge must be able to handle many different logical paths from a single decision. Much like a real-life workflow, the path may not strictly be binary from a single point, and it can branch or loop in any number of ways.
The question is how to represent this in Build Forge, and the answer is with Adaptors.
Adaptors are the crucial bit of functionality that allows Build Forge to represent multiple branches from a single bit of input.
Without Adaptors, you are only using the regular steps in Build Forge, which function in much the same way as a make file. The steps execute something on a client machine and get output back: binary action. That is the very basic kind of integration, which is very easy to set up in Build Forge. But more than integration, Build Forge allows a rudimentary branching logic and looping ability.
Note: This document does not duplicate the information already published in IBM Rational Build Forge Help. If you have not already done so, you should first review that help, which can give a fuller appreciation of the subject covered in this article.
Download | Description | Name | Size | Download method |
|---|
| Adaptors Help Guide | adaptors.pdf | 81KB | HTTP |
|---|
Resources Learn
Get products and technologies
Discuss
|  | |  |