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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Integration</strong> Brokers 261<br />

• Parsing;<br />

• Intelligent routing;<br />

• Extracting key identifiers and identifying specific processing rules;<br />

and<br />

• Guaranteed secured message delivery.<br />

The messaging services determine when and how the messages are<br />

routed, what <strong>to</strong> do with a message if the receiving application is not<br />

ready <strong>to</strong> receive it and several other features typical of a message<br />

broker.<br />

An integration broker can be built either on messaging middleware<br />

or provide adapters for message oriented middleware or message buses.<br />

In either case it has <strong>to</strong> enable guaranteed messaging of both the<br />

structure (syntax) and the meaning (semantics) of the data between<br />

applications. Many integration broker software vendors use MQ Series<br />

for message queuing.<br />

Message flow control is an important feature that an integration<br />

broker has <strong>to</strong> support for effective performance results. Assume a<br />

situation in which the source application is generating messages at a<br />

rate much faster than they can be received by the destination. In such<br />

a scenario, messages accumulate in the broker's memory, which may<br />

reduce the available CPU resources for other tasks. It should be able <strong>to</strong><br />

throttle the source application, using flow control <strong>to</strong> avoid losing<br />

messages and slowing down the message throughput of the broker as<br />

a whole. Additionally, the broker should provide robust performance<br />

in the event of server overload and network congestion — all of<br />

which may result in a high number of unretrieved messages in the<br />

message queue.<br />

Each trading partner in a <strong>B2B</strong> application may have its own<br />

preferences in terms of transaction sets, message formats, communication<br />

transports, access privileges, routing and transformation rules and tracking<br />

and error-handling requirements. <strong>Integration</strong> brokers should support all<br />

these cus<strong>to</strong>mizable preferences and enable message routing that directs<br />

data according <strong>to</strong> conditions set by the business. They should also<br />

enable message formatting so that applications can exchange information<br />

after adapting the presentation of the content <strong>to</strong> the requirements of the<br />

environment.

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

Saved successfully!

Ooh no, something went wrong!