![]() |
![]() |
![]() |
![]() |
![]() |
•
• Oracle MessageQ (OMQ) message queuing bus forms the data highway used to transfer messages between applications by creating a logical interconnection of message queues in a networked environment as shown in Figure B‑1.Figure B‑1 OMQ ArchitectureFigure B‑2 shows the system structure of an application using OTMQ.Figure B‑2 OTMQ ArchitectureTable 1 provides a summary of key OMQ and OTMQ compatibility features.
OTMQ does not support UMA=DISCL OTMQ applications can be deployed centrally or decentrally. By taking advantage of flexible Oracle Tuxedo deployment models, an OTMQ application configures and deploy resources using UBBCONFIG and DOMCONFIG files.
• UBBCONFIG/DMCONFIG (configuration files)
• tmloadcf (administration command)OTMQ provides a tool ("dmqclconv"), to migrate the omq.init file into OTMQ configuration files (UBBCONFIG/DMCONFIG).OTMQ uses the "tmqadmin" command to create/manage queuing resources (Qspace and queues). OTMQ applications should also use the following commands to build clients and servers:
• TuxMsgQ: Message Queue Manager.
• TuxMQFWD: Message Queue Off-line Trade Driver.
• TMQ_NA: Message Queue Naming Server.
• TMS_TMQM: TMS server for OTMQ resource manager.
• TMQ_EVT: TMQ Event reporting process.
• TMQFORWARDPLUS: Message Forwarding server.
• TuxMsgQLD: TMQ Link Driver server.These services can be configured and deployed in the UBBCONFIG file based on application requirements. For more information, see the Oracle Tuxedo Message Queue UBB Server Reference.For OMQ application compatibility, OTMQ supports UMA_SAF in a revised edition. For an OMQ client, if UMA_SAF for a recoverable message is applied, the message is stored in the local DQF . If OMQ is unable to write to the local journal disk file, UMA is used. OTMQ follows this methodology; however, OTMQ stores the message in the local SAF to ensure that the message is recoverable. If the action fails, then UMA is used.Listing 1 provides an example OMQ configuration file-Setup.initListing B‑1 OMQ Configure File-Setup.initAfter running the OTMQ dmqclconv command as follows:dmqclconv -g 1 -f dmq.ini, the converted results are shown in Listing 2.Listing B‑2 Converted ResultsListing 3 shows a QALIAS exampleListing B‑3 QALIASListing 4 shows a CRTLOG example.Listing B‑4 CRTLOG