Dismiss
The InnovationQ application will be updated on Sunday, May 31st from 10am-noon ET. You may experience brief service interruptions during that time.
Browse Prior Art Database

A Generic Input and Output Concept for Message Flows in MQSeries Integrator V2 Supporting Physical Segregation of Organizational Units

IP.com Disclosure Number: IPCOM000014775D
Original Publication Date: 2001-Jun-15
Included in the Prior Art Database: 2003-Jun-20

Publishing Venue

IBM

Abstract

1. Introduction MQSeries Integrator V2 (MQSI) is a message broker product that helps integrate applications by managing the flow of information between them. It provides services that let you route messages by using rules that can do any of the following: Read the contents of the message or message header and act accordingly Transform a message Store a message (or part of it) in a database, or retrieve a message (or part of it) from a database Modify a message Publish a message MQSI provides a graphical user interface called the Control Center, with which you can model message flows by placing MQSeries Integrator processing nodes or primitives onto a modeling area, and connecting them. Each message flow must start with at least one input primitive 'MQInput' and typically ends with one output primitive 'MQOutput'. As its communication layer, MQSI uses the MQSeries messaging products. Each input primitive has assigned to it exactly one MQSeries queue, whereas each output primitive can have one or more MQSeries queues assigned to it. The output queue name(s) can be changed during runtime, but for the name of the input queue is specified at configuration time and cannot be changed during runtime. You can connect more than one input primitive to a processing node. Each input primitive then starts a new thread of the same message flow.