18.04.2013 Views

B2B Integration : A Practical Guide to Collaborative E-commerce

B2B Integration : A Practical Guide to Collaborative E-commerce

B2B Integration : A Practical Guide to Collaborative E-commerce

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Middleware Technologies 227<br />

Program A makes an MQPUT call specifying not a local queue but<br />

a local definition of a remote queue. This definition identifies a queue<br />

on another queue manager. The queue manager <strong>to</strong> which Program A is<br />

connected puts the message on a special queue called a transmission<br />

queue. The message is then au<strong>to</strong>matically sent along the channel<br />

connecting the two queue managers. The receiving queue manager puts<br />

the message on the queue that was originally specified by Program A.<br />

This message is s<strong>to</strong>red on the queue until it is retrieved by Program B,<br />

after Program B has issued an MQGET call.<br />

MQSeries can support three kinds of transactional operations as<br />

follows:<br />

• Internal Transactions — MQSeries supports internal operations and<br />

transactions related <strong>to</strong> the actual messages. Messages are managed<br />

using transactional controls, allowing it <strong>to</strong> commit or rollback/resubmit<br />

messages in the event of a failure. In that case, all messages would<br />

rollback and the original input message would be reinstated on the<br />

queue.<br />

• External Transactions — MQSeries supports external transactional<br />

managers, such as TP moni<strong>to</strong>rs. MQSeries can commit or rollback all<br />

message processing, based upon the success or failure of the external<br />

transaction. In the event of a failure, all messages would rollback and<br />

the original message would be reinstated on the queue. In this mode,<br />

MQSeries is acting as a so-called resource manager. MQSeries can<br />

integrate with any X/Open XA compliant transaction manager, such<br />

as BEA Tuxedo and IBM's CICS.<br />

• Self Transactional — MQSeries can act as a transaction manager,<br />

managing messaging and other X/Open XA-compliant resources, such<br />

as databases. This allows MQSeries <strong>to</strong> support transactions without<br />

the use of a TP moni<strong>to</strong>r or application server. MQSeries does not<br />

provide all the capabilities of an enterprise TP moni<strong>to</strong>r, but it can be<br />

a good fit where a need for transaction management is at a minimum.<br />

MQSeries provides intelligent routing, allowing servers <strong>to</strong> forward<br />

messages along the shortest path available. Intelligent routing will<br />

also route messages around networks which have failed or which are<br />

experiencing problems.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!