Learn how to develop WebSphere Process Server applications and manage resources in a team-oriented CVS environment using WebSphere Integration Developer. This article identifies the artifacts needed for remote version control management, as well as the necessary procedures to develop applications with artifacts remotely managed in a team environment using WebSphere Integration Developer.
This article describes the configuration of IBM® WebSphere® Integration Developer (hereafter, referred to as Integration Developer) workspace in Version 6.0.1 and gives careful attention to the management and generation of the various resources of the Service Component Architecture (SCA) applications developed for WebSphere Process Server (hereafter, referred to as Process Server). It is based on the development of an application that leverages most of the capabilities of the business integration development environment including detailed coverage of the most common components and functionality in Process Server and Integration Developer.
The scenario leverages the team development facilities of Eclipse and Integration Developer using Concurrent Versioning System (CVS) as the primary tool for team development and application version control. The article begins with an analysis of the module’s core elements as well as those pieces generated by Integration Developer. It then discusses the quintessential components of a module as they pertain to business integration development in a team environment. The final sections of this article describe a detailed methodology, as well as the known problems and workarounds, for team-based Process Server application development.
It assumes that the reader has basic knowledge of Service Component Architecture (SCA) and Eclipse.
|Article in PDF format||0604_beers-teamdev.pdf ( HTTP | FTP )||495 KB|