From DeveloperWorks, Getting Started with IBM WebSphere Business Services Fabric V6.1:

Draft Redbook, last updated: Tue, 11 Mar 2008

- Discover the value of composite business applications
- Model, assemble, and deploy Fabric solutions
- Learn by example with practical scenarios

WebSphere Business Services Fabric (Fabric) is a comprehensive SOA offering that is designed to extend IBM’s business process management platform to deliver flexible composite business applications.

Everything you need to know about Fabric in one simple book. Finally.

Related Posts

• WebSphere Business Services Fabric, Part 2: Extending the ontology models
• WebSphere Business Services Fabric V6.1.2: Integrating with WebSphere Service Registry and Repository
• Introduction to application server clustering with WebSphere Business Services Fabric
• Adding custom roles in WebSphere Business Services Fabric
• Demystifying WebSphere Business Services Fabric End Point Selection

From DeveloperWorks, What’s new in WebSphere Message Broker V6.1

This article introduces the major enhancements WebSphere Message Broker V6.1, and provides references to related resources, and describes technical aspects of V6.1 that are of interest to
architects, message flow designers, and developers. Readers should have some knowledge of WebSphere Message Broker concepts and features.

I haven’t done much work in Message Broker v6.1 but I know theres a ton of people out there that do. Read the article to find out more about v6.1 of IBM “Advanced ESB”.

Related Posts

• Business Value of WebSphere Message Broker V6.1
• BPEL or ESB: Which should you use?
• What’s new in IBM WebSphere Enterprise Service Bus V6.1
• The top 15 WebSphere MQ best practices
• IBM WebSphere DataPower SOA Appliances Part I: Overview and Getting Started

From DeveloperWorks, Handling unmodeled faults within WebSphere Process Server V6.1

See how BPEL processes can handle unmodeled faults with a user-defined fault handler by using SCA mediation module (ESB) capabilities.

In this article, they talk about handling a scenario where a WSDL SOAP/HTTP service does not define any faults but actually lands up throwing one (StockNoExist). Now, what I would normally do is just edit the WSDL definition used by the BPEL to include the fault definition. This technically works even though the source and target wsdls are different (the fault definition). If you want (or can’t) touch the wsdl then you have to follow the steps in this article to make catching the specific error possible.

Related Posts

• WebSphere Process Server: Repairing Business Processes
• Error Handling in WebSphere Process Server: Developing an Error Handling Strategy
• WebSphere Process Server and RPC/Literal Web Services: Beware Messages defined by ‘type’ instead of ‘element’.
• WebSphere Integration Developer – Namespaces Cannot Span Projects
• WebSphere Enterprise Service Bus – Mediation Flow Component: No Refactoring for WSDL Faults

From DeveloperWorks, Hello World: WebSphere Service Registry and Repository

Manage, govern, and share services across your organization by
using WebSphere Service Registry and Repository. Follow the hands-on
exercises to learn how to navigate the Web interface to publish, find, reuse, and update services.

When ever I get my hands on a new product, I like to go through the “Hello World” example in order to familarize myself with the concept and constructs. In this article, you’ll get familar with IBM’s new SOA repository product: WebSphere Service Registry and Repository. (WSRR)

In a nutshell, WSRR allows you to answer a question that (will one day) plague your SOA: “Who the heck is using my service?”. It’s a product centered around SOA governance. It allows you to browse the relationship between your service, your consumed services and the services consuming you (in addition to a whole lot of other neat stuff).

Related Posts

• Create classification taxonomies programmatically in IBM WebSphere Service Registry and Repository
• WebSphere Business Services Fabric V6.1.2: Integrating with WebSphere Service Registry and Repository
• Establish a policy-driven SOA using WebSphere Service Registry and Repository and WebSphere ESB
• Using DataPower SOA Appliances to query WebSphere Service Registry and Repository
• WSDL Anti-Pattern: The ‘Single XML String’ Service

From DeveloperWorks: Demystifying WebSphere Business Services Fabric End Point Selection:

Learn how the WebSphere Business Services Fabric Dynamic Assembler uses
content, context and contract to dynamically select service endpoints. You’ll learn
how policies are used to select candidate endpoints, and how the Dynamic Assembler
handles policy conflicts and policy resolution.

On the heels of my opening discussion about Fabric and how its a product ahead of it’s time, comes an article from developerWorks that delves into the “how” of the product. This article provides an introduction to the terms that the fabric team likes to toss around: “Policies”, “Assertions”, “Dynamic Assembler” etc.

Related Posts

• WebSphere Business Services Fabric
• WebSphere Business Services Fabric, Part 2: Extending the ontology models
• Getting Started with IBM WebSphere Business Services Fabric V6.1
• Adding custom roles in WebSphere Business Services Fabric
• Introduction to application server clustering with WebSphere Business Services Fabric

From Developerworks, Enabling SCA-MQ integration via MQ bindings:

The MQ Bindings feature in WebSphere Integration Developer V6.0.2, simplifies interoperability between SCA and MQ applications, and makes it easier
to read and write native MQ messages to and from SCA applications.

If you are new to WebSphere Integration Developer and need to connect to MQ, this is the article for you.

Tip: When they create the end-point configuration (Figure 20), they choose to “Specify Properties for configuring WebSphere MQ resources”. This will create the MQ connection factories, Queue definitions and other assorted runtime resources at EAR deployment time. Your administrator will only be able to modify them once the ear is installed to the system. Also when the EAR is uninstalled the resources will be removed. If your administrator has modified the JNDI’s in the meantime, the work will need to be redone.

If you are developing as part of a real project, you should always choose the latter: “Specify JNDI for pre-configured WebSphere MQ resources”. This will allow your WebSphere server administrator to define and modify the resources as needed throughout the production life cycle. They will survive EAR reinstalls and give you full control over your server.

Related Posts

• Introducting the SCA HTTP Binding
• IBM Client Application For JMS – Put JMS messages in queues
• JMS Function Selectors & Method Bindings
• Close WebSphere Integration Developer when updating Fixpacks for WebSphere Process Server
• IBM Certification Tests