Cast Iron integration into the current IBM ESB stack

So where does Cast Iron fit into the IBM Websphere stack?Cast Iron primary used for Cloud to on-premise integration. Where you can create a message flow diagram using the Cast Iron Studio and deploy that flow to the following environments:

1. Cast Iron Appliance (which is now the Datapower XH35 Cast Iron V5.1)

http://www.castiron.com/ibm/websphere/datapower/castiron/appliance/xh35

2. The virtual Cast Iron appliance which can be installed in VMWare.

3. Amazon EC2

So how can you integrate Cast Iron with current IBM ESB’s:

1. Datapower XI50

2. Websphere Message Broker

3. WESB (Websphere ESB)

The simple answer is:

1. Websphere MQ

2. Web Services

Cast Iron integrates natively to Websphere MQ and any Web Services call can be made. This is a great addition to the IBM Stack and will be a great solution for customers that want to do any cloud integration.

Using WebSphere Transformation Extender with IBM Enterprise Service Bus products

The transformation to a service-oriented architecture (SOA) includes aspects that cover the entire lifecycle of a solution, from inception, to design and development, to its ultimate deployment and management. IBM® published an SOA Reference Architecture that helps structure and position these aspects into a number of different components, and the IBM SOA Foundation includes a set of products that address specific components within the overall architecture. This article is the first of several that will discuss how products that are part of the IBM SOA Foundation can be used together. First up: how to add advanced transformation capabilities to IBM’s set of Enterprise Service Bus (ESB) products: WebSphere® Message Broker, WebSphere ESB, and WebSphere DataPower®. This content is part of the IBM WebSphere Developer Technical Journal.

For more information see the following link:

http://www.ibm.com/developerworks/websphere/techjournal/0804_flurry/0804_flurry.html

Deployment Patterns for ESB – Global, Direct, Brokered or Federated

  • Global ESB: All services share one namespace, and each service provider is visible to every service requester across a heterogeneous, centrally administered, geographically distributed environment. Used by departments or small enterprises where all the services are likely to be applicable throughout the organization.
  • Directly connected ESB: A common service registry makes all of the services in several independent ESB installations visible. Used where services are provided and managed by a line of business but made available enterprise-wide.
  • Brokered ESB: Bridge services that selectively expose requesters or providers to partners in other domains regulate sharing among multiple ESB installations that each manages its own namespace. Service interactions between ESBs are facilitated through a common broker that implements the bridge services. Used by departments that develop and manage their own services, but share a few of them, or selectively access services provided across the enterprise.
  • Federated ESB: One master ESB to which several dependent ESBs are federated. Service consumers and providers connect to the master or to a dependent ESB to access services throughout the network. Used by organizations that want to federate a set of moderately autonomous departments under the umbrella of a supervising department.

Datapower XI50, XS40, XA35 role in an ESB

Every Datapower Appliance has their own role inside an ESB (Enterprise Service Bus). Below we expose where each Datapower device will be better suited aligned with its functionality.

What role does each Datapower appliance have inside an ESB?See the image  below which explains the model of each appliance with regards to its functionality.