Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Application Development for IBM WebSphere Process Server 7 and Enterprise Service Bus 7

You're reading from   Application Development for IBM WebSphere Process Server 7 and Enterprise Service Bus 7 A Service Oriented Architecture approach has many benefits for your applications, including flexibility, reusability, and increased revenue. You can exploit those benefits to the fullest by following this step-by-step tutorial for WPS and WESB.

Arrow left icon
Product type Paperback
Published in Jul 2010
Publisher Packt
ISBN-13 9781847198280
Length 548 pages
Edition 1st Edition
Languages
Arrow right icon
Toc

Table of Contents (20) Chapters Close

Application Development for IBM WebSphere Process Server 7 and Enterprise Service Bus 7
Credits
About the Authors
About the Reviewers
Preface
1. Introducing IBM BPM and ESB FREE CHAPTER 2. Installing the Development Environment 3. Building your Hello Process Project 4. Building Your Hello Mediation Project 5. Business Process Choreography Fundamentals 6. Mediations Fundamentals 7. Sales Fulfillment Application for JungleSea Inc. 8. Walk the Talk 9. Building the Order Handling Processes 10. Integration with Various Applications 11. Business Space 12. Deployment Topologies 13. Management, Monitoring, and Security WID, WPS, and WESB Tips, Tricks, and Pointers Index

Process Services


As identified in the previous chapter, our application consists of two process services—OrderHandling and CustomerInterfaceManagement, as shown in the following figure:

Note

How to read the preceding diagrams:

The outer boxes represent the modules of the process service. The module names represent the actual module name in the Sales Fulfillment Application in WID. The inner boxes with the module box represent the components in the module assembly that make up the module and the << >> signifies the type of implementation used to develop that component. Lastly, << >> on the arrows defines the interrelationships between modules/components/layers and how they are integrated together.

For example, the module ProcessServices-OrderHandling in WID contains two components, namely, TrackAndManageCustomerOrder and HandleOrderFallout, which are both implemented as long running BPEL processes. TrackAndManageCustomerOrder in the event of a fallout invokes HandleOrderFallout...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image