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

I was recently given a copy of the new book Application Development for IBM WebSphere Process Server 7 and Enterprise Service Bus 7 to review. In general, I’m very impressed. The authors do a good job of explaining general SOA concepts, and the components of the respective IBM products which are used in implementing these concepts, right down to the nitty-gritty of how to implement a sample scenario (with thorough walk-through steps and screenshots). They cover both the key concepts of mediation flows and BPEL-based business processes. The book is light on a few subjects (it doesn’t really discuss the WebSphere Adapters, for example, and the chapter on deployment is a bit light – see the Production Topologies Redbook for more detail), and the hints ‘n’ tips chapter seems messy, but generally, it seems excellent for a beginner trying to learn these products.

(In the interests of disclosure, I received only a free copy of the book for this review).

5 Responses to Application Development for IBM WebSphere Process Server and Enterprise Service Bus 7.0

  1. Websphere 7 says:

    IBM promisses a great advancement in Websphere 7 that the earlier version as a websphere developer for 6 years now I would like to see these advancements take place
    We really got fed up with IBM lake of support for new Java technologies
    hope this change

  2. Allan Lang says:

    There is something which confuses me about this book. It takes a WID-only approach to development for WPS / ESB, and where it talks about a ‘top-down’ approach, this starts in Business Integration view and ends in Integration Developer view. I thought that IBM tended to recommend a top-down approach starting with Business Modeller and only doing the minimum of tidy-up in WID. What actually works best in practice?

  3. Allan, good point. I think it depends on what you’re trying to achieve. For a start, WebSphere ESB-only projects don’t tend to make much sense for Business Modeller, as it doesn’t really cover the ESB domain – so they will make most sense in WID.

    Also, even for artifacts built for WPS (i.e. BPEL), I don’t think it’s cut and dried. For large or complex projects that are focused on process improvement, Business Modeller is still the ideal route – especially using it for its core competency, modelling of processes. But it is true to say that on a small project, where the business domain and the processes to be constructed are well understood, you could start out in WID and be OK. Unfortunately, as with all such things, you’ll find differing opinions. I have found that a combination of both works best in practice for most large real-world projects, but the book does describe a perfectly valid approach.

    Hope that helps,

  4. Pavan Kumar Reddy says:

    Andrew, I am a beginner trying to learn BPEL. I have a question related to creating predefined constant strings in business process, like we have enums in java where we can predefine certain values, will visual snippet in business process support something similar to enum in java (apart from using custom java snippet).

    For example if i had to use the string constants “STR1”, “STR2”, “STR3” – instead of hard coding these values across the business process, is it possible to predefine these constants at one place so that at later point if we need to change values of these string constants, it will be easy to modify them at one place.


  5. Hi there! I could have sworn I’ve been to this web site
    before but after going through a few of the posts I realized
    it’s new to me. Anyhow, I’m definitely happy I found it and I’ll be book-marking it and checking back often!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: