IBM Cast Iron Options: Appliance Vs. Live (SaaS)

Software as a Service (SaaS) is fast becoming the deployment du jour, but appliances haven’t lost favor yet. The decision over an on-premise install or appliance versus an SaaS solution should still be made on a case-by-case basis. IBM Cast Iron offers both options and each enables cloud-to-cloud, cloud-to-on-premise and on-premise-to-on-premise integration and real-time, near-real-time and batch.
Here’s a brief look at both options.

Cast Iron As Appliance

Cast Iron can be deployed as either physical hardware or a virtual machine. With this style of deployment, the Integration Appliance is installed on-premise – normally behind the firewall, but not within a DMZ.
The runtime environments for the dev, test and prod lifecycles are typically separated, each with its own Integration Appliance to access necessary endpoints within the environment.
The user maintains full control of projects and their orchestrations on the appliance through the WMC. The orchestrations are started through activities which include polling, scheduling or an incoming request – an HTTP Receive Request, for example. Data flows through the Integration Appliance and is stored internally as XML variables. Users control the logging for each orchestration.

Cast Iron Live

This multi-tenant, browser-accessed deployment model includes key components for users to design, run and manage integrations all in the cloud. Those components are:

  • A clustered runtime engine that runs the integrations with built-in fault-tolerance and recovery mechanisms
  • A multi-tenant, highly available system to store the designed integrations
  • A load-balancer to intelligently manage the loads throughout the various runtime engines
  • Highly available file systems to store and manage logs that are related to the integrations

The Live version also includes a Design environment with the same capabilities as the on-premise Studio environment
TxMQ specializes in application integration. Initial consultations are free and communications are always confidential. Contact vice president Miles Roty for more information: (716) 636-0070 x228, [email protected].

How The IBM DataPower XB62 Bridges Internal And External (B2B) Integration

One of the more elegant features of the DataPower XB62 appliance is its dual ability to govern internal application integration as well as external B2B (or Trading Partner) integration. In essence, the XB62 bridges the gap between internal and external integration, which is what makes it such a complete solution for so many different types of businesses.
In support of the XB62, IBM states that the company “recognizes the convergence” of internal and external integrations. And it’s obvious that the need for integrations near or at  the edge of the network is growing rapidly. By opting to deploy the XB62 you can better support complex B2B flows and become more flexible in routing and file processing. It’s therefore much easier to bridge between the DMZ and protected networks without sacrificing security. This in turn allows you to attract more partners due to the ease, flexibility and security of the external integration.
One oft-cited example of an XB62 deployment is to have the XB62 sit in the DMZ, where it securely connects to trading partners, but that same appliance also exchanges data with a DataPower X152 appliance within the protected network, which handles all the enterprise service bus functions.
TxMQ successfully deployed a DataPower XB62 solution for Medical Mutual of Ohio that serves as a strong example of the appliance’s secure integration capabilities. Medical Mutual wanted to take on more trading partners and more easily align with government protocols, but lacked the infrastructure to support it. “We needed to set up trading-partner software and a B2B infrastructure so we could move the data inside and outside the company,” says Eleanor Danser, EDI Manager, Medical Mutual of Ohio. “The parts that we were missing were the trading-partner software and the communications piece to support all the real-time protocols that are required from the ACA, which is the Affordable Care Act.”
TxMQ’s DataPower XB62 solution delivered $250,000 to $500,000 annual savings on transaction fees for Medical Mutual, as documented in this story published by Insight Magazine.
For more information on TxMQ’s many DataPower solutions for all industries, contact vice president Miles Roty – (716) 636-0070 x228, [email protected] – for a confidential and free initial consultation.