The Magoo Blueprints provide design hints, sample architectures and solutions for common scenarios in Service Oriented Architectures and general Web Service and XML programming.
Connection Options for WebSphereMQ
MagooClient/MagooServer support two different models for connecting to WebSphereMQ - a native connector utilizing the IBM Base classes as well as a more generic JMS approach. This overview looks at:
Working with RabbitMQ
MagooClient can be easily plugged into a RabbitMQ architecture - this brief example illustrates how it can be configured for both queue and topic exchanges:
MagooClient and Apache ActiveMQ/CXF Blueprint
This blueprint provides a fully-worked example of human intervention within an asynchronous SOA message-flow based on ActiveMQ/CXF and includes:
Integrating MagooClient with JMS SOA
This blueprint guides you through the steps involved in integrating MagooClient into a JMS-based SOA. The scenario is based on the correction and/or completion of a Packing Slip by a manual operator. This blueprint covers:
User Tasks and BPEL Processes
This blueprint describes a model for using MagooClient as a partner within a BPEL process. It includes a fully-worked example illustrating asynchronous interaction between two user roles and a BPEL process. Topics covered include:
WebLogic User Tasks
This blueprint shows how interaction with a user via a JMS queue can be used as a mechanism for correcting errors in an order-fufillment Web Service. This is a common issue within business processes where application logic is incapable of handling particular errors and human intervention is required. This scenario is based on a WebLogic 8.1 Windows installation and some knowledge of WebLogic is assumed. Code samples and instructions are provided to allow you to build the demo yourself. As the JMS API provides a standard means for interacting with messaging providers, the steps for configuring MagooClient will be similar for other JMS-compliant vendors.