Book Image

Application Development for IBM WebSphere Process Server 7 and Enterprise Service Bus 7

Book Image

Application Development for IBM WebSphere Process Server 7 and Enterprise Service Bus 7

Overview of this book

By adopting an SOA approach in Business Process Management (BPM), you can make your application flexible, reusable, and adaptable to new developments. The SOA approach also gives you the potential to lower costs (from reuse), and increase revenue (from adaptability and flexibility). However, integrating basic SOA constructs (such as Process, Business Services, and Components) and core building blocks of BPM (such as Process Modeling and Enterprise Service Bus) in a real-world application can be challenging.This book introduces basic concepts of Business Integration, SOA Fundamentals, and SOA Programming Model and implements them in numerous examples. It guides you to building an Order Management application from scratch using the principles of Business Process Management and Service Oriented Architecture and using WebSphere Process Server (WPS) and WebSphere Enterprise Service Bus (WESB). The various detailed aspects, features, and capabilities of the product are conveyed through examplesWe begin with essential concepts on Business Integration, SOA Fundamentals and SOA Programming Model. Then we set up the development environment to build your first Hello Process and Hello Mediation applications.Gradually, we build an SOA-based Order Management Application. We cover important aspects and functions of WPS and WESB with numerous practical examples. We show how to analyze your application's business requirements and check if an SOA approach is appropriate for your project. Then you do a top-down decomposition of your application and identify its use cases, business processes, and services. Having built the SOA Application, we introduce you to various non-functional topics, including: Administration, Governance, Management, Monitoring, and Security. We also discuss deployment topologies for WPS and WESB, performance tuning, and recommended practices.
Table of Contents (20 chapters)
Application Development for IBM WebSphere Process Server 7 and Enterprise Service Bus 7
Credits
About the Authors
About the Reviewers
Preface
WID, WPS, and WESB Tips, Tricks, and Pointers
Index

Recommended practices when working in a team environment or when performing team programming


WID provides the capability for a team of developers to develop applications in a team environment and share resources with a central repository.

Using the plugins provided by WID, you can connect to software configuration management repositories like CVS, Rational ClearCase, or other repositories. While the Business Integration perspective and view provides a logical view of the resources within a module, mediation module, and library, the physical files and artifacts themselves can be stored in a repository such as CVS or ClearCase. Some of the recommended practices to adopt when working in a team environment include:

  1. Before starting work on any module, synchronize with the repository.

  2. When you have completed the implementation of a particular component and are ready to check in the module (or library), synchronize with the repository first and accept all incoming changes. Make sure that there are no conflicts. Update and commit changes. Give verbose comments to what were the changes/additions/fixes addressed and so on.

  3. If you want to tag versions to a module or library, you can use the following versioning scheme: version.release.modification (such as, 1.0.0).

  4. If you check out any tagged version, you will have to switch back to the HEAD trunk to conduct normal business with WID.

  5. Avoid concurrent development and merge scenarios http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic/com.ibm.wbit.620.help.addev.doc/topics/cshare.html.

  6. Work in the Business Integration view where possible.

  7. After moving to a new workspace, be cautious of adding new files to source control.

  8. Derived flag can be lost after importing the files into a new workspace (https://bugs.eclipse.org/bugs/show_bug.cgi?id=150578).