- By David Essex
- Aug 15, 2003
The federal government's push for better information sharing among agencies, made more urgent by e-government initiatives and 9-11 intelligence failures, has created strong demand for enterprise software architectures, Web standards and integration tools.
Among the latter, that old chestnut, middleware, has been dusted off. Agency IT managers are searching for better ways to integrate not just the applications and legacy databases of far-flung offices, but the up-to-the-minute wireless communications of border agents, real-time inventory levels in defense procurement and logistics systems, and satellite weather feeds that mean go or no-go to waiting bomber pilots.
Middleware projects are indeed rampant at the federal level. The Army Aviation and Missile Command, for example, used webMethods middleware to pull together legacy technical manuals and other critical information on Blackhawk helicopters to display on a secure Web site. Other Defense Department divisions are working with middleware vendors to build visibility and secure messaging into its emerging, worldwide supply chain network.
Definitions of middleware have evolved, but at bottom they've always been what their name implies: software that sits between two systems'usually applications but sometimes networks'so the systems can communicate directly.
Historically, there have been two main kinds. The first, messaging-oriented middleware (MOM), also known as enterprise messaging, swaps generally simple messages between systems. The second, adapters, employ richer templates that map data between the two.
As the Internet became the network backbone, Web standards such as Extensible Markup Language, Java and its messaging protocol, Java Message Service, and related Web services have been added to bring more universal data sharing among an exponentially growing number of sources.
Middleware products have roots in four infrastructure technologies. MOM platforms and transaction processing monitors like IBM's WebSphereMQ, Tibco and BEA's Tuxedo started decades ago as mainframe and Unix integration tools.Adept at adapting
Another vein is enterprise application integration (EAI), a hot category since the late 1990s that has consolidated down to a handful of companies, notably webMethods, Vitria, SeeBeyond and Tibco. EAI companies made their names building adapters between popular applications such as Oracle Corp. databases and SAP America Inc.'s R/3 enterprise resource planning, and packaging them in a single product. They often include MOM in their integration suites alongside the adapters.
More recently, makers of Web application server infrastructures have sold integration suites geared to their app servers. They've been successfully pushing three-tiered infrastructures that match app servers with integration servers, both powering a third, portal-server box that presents the information collected by the middleware. EAI vendors counter, with some justification, that their integration works with a broader range of platforms.
The newest category contains companies such as SeeBeyond, Software AG, and Sonic MQ that have planted their integration flags in the open Web standards of XML and Java. 'It's a little bit different from classic EAI,' said Joe Gentry, Software AG's director of product marketing. 'It really is designed around a standards interface.'
The accompanying chart in-cludes the main offerings from most of these middleware vendors. It does not show vendors such as BMC Software Inc. of Houston, Candle Corp. of El Segundo, Calif., and MQ Software Inc. of Minneapolis, which sell management tools and add-ons that augment core middleware.
Besides Web standards, the hottest trend affecting middleware design is an effort to relate low-level integration tools to the business processes and people who use the applications. The idea is to use graphical user interfaces, diagrams and other executive-friendly tools to redesign workflows; some middleware, including webMethods', comes with workflow tools.
'First there was EAI, where you connect Application A to Application B,' said John Kiger, BEA's director of product marketing for the WebLogic enterprise platform. 'Connecting A to B was no longer sufficient. You also needed some business logic that would represent the business process that was the driver for integrating A to B.'
More recently, business activity monitoring'so-called dashboards for real-time monitoring of the business processes running on middleware'has begun to be incorporated.
'BAM is a real-time representation of the operational metrics of your business,' said Jim Ivers, senior director of product marketing at webMethods. Integration among vertical layers is starting to take other forms: webMethods Manager, for example, can tell you which business processes are affected by a server crash, according to Ivers.Flexible infrastructure
Along with the demand for integration far beyond internal local networks, the push for open standards has led to a new vision of middleware as a more flexible backbone infrastructure for all sorts of application and network integration.
Vendors and analysts have new acronyms for the phenomenon: enterprise service bus and service-oriented architecture.
ESB implies an XML-based bus analogous to hardware buses on PC motherboards, and into which you plug adapters for specific applications. Ivers likens the adapters to vertebrae in the backbone.
'ESB is a very important topic,' said John Rymer, research vice president at Giga Information Group, a market research company in Cambridge, Mass. 'It addresses one of the problems with middleware: They tend to be very isolated.'
SOA, in contrast, is a catch-all for middleware that works like a Web service, with applications sharing messages while hiding their internal workings from each other. David Essex is a free-lance technology writer based in Antrim, N.H.