The IQ Legacy-Bridge is better known as the One-Way-Bridge (OWB). It's name is a little confusing since it is truly does not limit the message traffic to One-Way. It is a unique mechanism for transferring messages from a Messaging Oriented Middleware (MOM) Transport on one platform to a MOM on another platform. The major advantage of the OWB is that it can accomplish the task of transferring the messages between the MOM’s without changing the customer application code. The OWB uses queues on the MOM for the transfer of messages and therefore does not require the customer application code to be changed on either side.
Although the product is called a One-Way-Bridge it really consists of two pieces. This document refers to them as Sides. The Left Side is the side where the OWB Application runs and the Right Side is where the IQJumpEngine runs. The current version of the OWB supports installation of the Left Side on any platform that supports BEA MessageQ and will transfer messages to the Right Side, where IBM MQSeries V5.x, BEA MessageQ 3.2 or 4.0A or 5.x or Microsoft MSMQ MOM’s are running. The OWB was designed to fill a gap in the IDI (Information Design, Inc.) product family for Migration Services. The main area of Migration is from very old VMS VAX’s running DmQ V2.1 or PAMS2.5 to a later version of DmQ or BEA MessageQ or one of the other MOM’s.
The One-Way-Bridge provides a facility to enable a message exchange between the BEA
MessageQ and IBM MQSeries or Microsoft MSMQ or BEA MessageQ or early versions
of DECmessageQ message queuing systems. Application developers can write their
applications using any of the above MOM’s and will not need to make any changes to their
applications in order to send messages to applications on another MOM. The One-Way-Bridge ensures that the integrity of each messages body and headers are
retained intact, during the transfer of the messages between the two message queuing systems. The OWB consists of two components:
- The Left Side runs the OWB application and it will attach to a queue on the DECmessageQ or BEA MessageQ Server that is running on this Host.
- The Right Side must have an IQJumpEngine and a Message Server running on its host. The Message Server can be DECmessageQ or BEA MessageQ or IBM MQSeries or Microsoft MSMQ.
The OWB is installed on the Left side Host and reads the configuration file that is located in the same directory as the OWB. This file is called iqconfig.txt and contains configuration information about the location of the IQJumpEngine and the specifics of the queues to monitor, queues for attachment and the direction of the message flow. When the OWB has completed reading the configuration file it will attach to the specified queue on the local host that is running the DECmessageQ or BEA MessageQ Server. It will then create copies of itself to provide the additional message flow connections specified in the iqconfig.txt file. Upon completion of the process creation activity, all of the OWB copies will send requests for connection to the IQJumpEngine located on the Right Side Host. When the connections have been established, they will then request the Right Side to be attached to specific queues. The messages will then begin to flow. Configuring and starting the OWB could not be simpler, and only requires a single DCL procedure to detach the OWB process. It only needs you to fill out the spaces in the supplied configuration (iqconfig.txt) file template.
|Reads and Writes BEAmessageQ or DECmessageQ messages on OpenVMS VAX.
||Provides access to older systems (legacy) and message services. This enables these systems to be integrated into more modern services.
|Support for multiple Message vendors.
||Enables the user to migrate messages from a legacy system into MQSeries, MSMQ or BEAmessageQ on WinNT, Solaris, HPUX, AIX and OpenVMS (VAX & Alpha).
|Simple Windows style configuration file.
||Makes it easy for the user to configure the queues and locations by supplying the configuration in a readable form.
|Queue Mapping .
||A very simple queue mapping technique has been created that makes it easy to make all of the queue definitions needed to configure the One-Way-Bridge (OWB)
|Uses IDI standard products to create the OWB
||Since the OWB was created using IDI's standard & proven products (IQJump & IQMessenger) there is a high level of reliability.