The Oracle Database Gateway for IBM WebSphere MQ allows Oracle applications to be seamlessly integrated with applications that use IBM's WebSphere MQ messaging products. This gateway is part of a comprehensive suite of solutions designed to integrate heterogeneous applications and data stores.
The Oracle Database Gateway for WebSphere MQ allows Oracle applications on any platform to communicate with WebSphere MQ applications. No Oracle code is required on the target system.
The gateway implements Remote Procedure Call (RPC) processing and can be used to access any WebSphere MQ system connected to your enterprise-wide network. This allows you to leverage your investment in WebSphere MQ applications, while fully exploiting your distributed Oracle applications.
The Database Gateway for WebSphere MQ provides complete integration with the WebSphere MQ environment. Through messages, programs can communicate across a number of IBM and non-IBM platforms --- without the complexities of direct communication across incompatible protocols, platforms, and networks. And because this communication is asynchronous, a message sent by one program does not interrupt the target program or rely on the target program to be available. The target can retrieve messages from the queue whenever it suits the business need.
Message flow can take many shapes, allowing one-to-one, one-to-many, or many-to-many program relationships. This flexible method of communication is ideal for a wide range of interrelated applications, including e-mail, workflow, data replication, and mobile applications.
Because the gateway communicates with other WebSphere MQ applications through standard WebSphere MQ messages, use of the gateway does not affect WebSphere MQ applications or require any programming modifications to those applications.
The Database Gateway for WebSphere MQ leverages the strength of the industry-leading Oracle database and PL/SQL technologies, so Oracle customers don't need to learn a new API in order to integrate with their WebSphere MQ applications. The tight integration between the database server and the Procedural Gateway also enables you to take advantage of ongoing improvements in Oracle's leading server technology.
Communication with the target WebSphere MQ system is transparent to the client applications. The gateway translates Oracle database stored procedure calls into the required WebSphere MQ calls. WebSphere MQ requests are executed as if they were local Oracle stored procedures. The database server and the gateway's distributed mechanisms work together to shield the application from having to be aware of the physical location of the WebSphere MQ application or queue, the programming logic of the remote application, or even the fact that an WebSphere MQ application is involved.
The Database Gateway for WebSphere MQ, in conjunction with the Oracle database, allows WebSphere MQ operations and database updates to be performed in a coordinated fashion. Oracle two-phase commit protection is extended to the WebSphere MQ environment --- without any special programming.
The Database Gateway for WebSphere MQ runs on a range of leading operating systems. The gateway can exchange messages with WebSphere MQ applications that are on the same machine as the gateway, or on remote machines running any WebSphere MQ-supported operating system.
Any necessary data conversions are performed by stored procedures within the Oracle database. Depending on their business needs, customers can run multiple copies of the gateway --- and support each gateway with multiple database servers, if necessary. This flexibility allows organizations to optimize usage of their system and network resources to meet the availability and operational requirements for each application. By utilizing multiple database servers, customers can avoid having any database server machine serve as a single point of failure.
Deploying multiple Oracle database can also help customers meet the performance requirements of each application, by spreading the conversion workload across multiple servers as needed. The gateway architecture is also designed to enable high performance. The gateway minimizes network activity because it allows users to send messages directly to queues that are local to the target applications. Other WebSphere MQ middleware architectures may incur substantial network overhead, as all messages must be routed to a central message queue hub before they can be retrieved by other applications.
Procedure Call Independence
Visual Workbench Environment
More Database Downloads