MQSeries Interface Paves Path Toward App Interoperability
Though the sentiment behind implementing an enterprise application integration (EAI) initiative is typically one of uniformity, there are multiple paths a company can take when tying together its core applications. Recognizing this, the Open Applications Group Inc. (OAGI) announces it has chosen IBM's MQSeries messaging middleware interface as its first messaging middleware standard.
More specifically, the OAGI (Mableton, Ga.) has approved IBM's Application Messaging Interface (AMI)--part of the MQSeries family of middleware--as the basis for the Open Applications Group Middleware Application Programming Interface (API) Specification (OAMAS).
IBM's AMI is designed to facilitate the exchange of messages between applications written in any of the major programming languages and running on a number of heterogeneous platforms. By defining IBM's AMI as a middleware standard, the OAGI expects to streamline the process of producing, integrating and maintaining business applications, lowering costs for both solutions providers and their customers.
"OAGI's adoption of IBM's AMI demonstrates the high regard the industry has for our leading messaging technology," says Bill Reedy, VP of marketing for transaction systems with IBM Software. "Working with organizations such as the OAGI and embracing standards such as XML and Java is part of IBM's ongoing effort to help customers move to e-business."
IBM has firm plans to make the AMI available over an MQSeries messaging foundation for AIX, HP-UX, Sun Solaris, Windows 98 and Windows NT during the third quarter of this year. The AMI's availability for OS/400 and OS/390 will be evaluated and developed based on customer demand, according to an IBM spokesman.