The second phase of IBM Corp’s asynchronous messaging technology strategy will deliver two key functions: integration between its MQSeries enterprise code and the volume MQWare ‘Falcon-killer,’ and Java. To compete with Microsoft Corp’s Message Queue Server (Falcon) – which is being bundled with the next version of Windows NT – IBM has already created a […]
The second phase of IBM Corp’s asynchronous messaging technology strategy will deliver two key functions: integration between its MQSeries enterprise code and the volume MQWare ‘Falcon-killer,’ and Java. To compete with Microsoft Corp’s Message Queue Server (Falcon) – which is being bundled with the next version of Windows NT – IBM has already created a high-volume, general purpose, lightweight version of its enterprise-class MQSeries software called MQWare for doing application messaging over TCP/IP. It’s been tailored specifically for use on Windows NT. MQWare does not, however, currently work with MQSeries, which is used to plumb large, custom networks and projects. Enabling the two to work together is phase two of IBM’s messaging strategy, but IBM won’t say when that will be complete. It says an example of where the two could be used together would be a large MQSeries-based system such as a customs operation which wants all importers/exporters to use a particular duty or excise form. Merchants would be able send a completed MQWare-enabled form from an NT system over the internet to the customs house which would be able to receive, read and incorporate it into its mainframe or Unix MQSeries applications. Meantime, IBM is readying a new cut of its full-blown MQSeries enterprise software code-named Armada, for introduction later in the summer. IBM’s going to give MQ- based Java technologies their first outing around the same time in the form of Java code which will reside on a server and enable Java-to-Java, Java-to-any MQ application or Java-to-Microsoft, – Tandem or other third party environments. There will also be a Java client. Having computer systems and software delivered with a pre-bundled MQ ‘black box’ is one idea IBM has for driving MQWare technology to market, but IBM isn’t specific about how or when this might happen.
IBM’s trying to grow an industry around its MQ technologies and third parties are being encouraged to develop products and services for use with core MQ technology. While IBM offers a native security mechanism for MQ, it has also fitted the software with hooks that enable customers and ISVs to plug in their own security mechanisms where required. IBM counts around 40 MQ partners to date. It’s already got Iona Technologies Ltd developing MQ integration with its Orbix object request broker and says other ORB vendors will do likewise. Having got Sybase Inc to MQ-enable its dbQ database messaging system, it expects other vendors to follow suit and will do the same for its own DB2 database. In time IBM expects messages to be stored in databases rather than in the MQSeries application itself. It doesn’t see any conflict or overlap between the crop of self-serving promotional bodies and standards groups which have their fingers in the messaging pie. In addition to BQM they include the MOMA Message-Oriented Middleware Association, the EMA Electronic Messaging Association, the OMG Object Management Group and The Open Group. IBM says it’ll make MQ work with whatever specifications OMG eventually comes up with in the area.