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.

228 <strong>B2B</strong> <strong>Integration</strong> — A <strong>Practical</strong> <strong>Guide</strong> <strong>to</strong> <strong>Collaborative</strong> E-<strong>commerce</strong><br />

MQSeries is supported by most of the leaders in message brokering<br />

<strong>to</strong>ols (besides its own MQSeries Integra<strong>to</strong>r). With its dominance in the<br />

MOM marketplace, MQSeries will be a component of most middleware<br />

solutions.<br />

Microsoft message queue (MSMQ)<br />

Microsoft introduced MSMQ in 1998 as an add-on <strong>to</strong> Windows NT,<br />

and has become a base service in Windows 2000. MSMQ, along with<br />

Microsoft transaction server (MTS), was Microsoft's first attempt <strong>to</strong><br />

penetrate the enterprise computing market. This attempt has culminated<br />

in the recent release of their .NET architecture, which has the potential<br />

<strong>to</strong> thrust Microsoft in<strong>to</strong> a leadership role in the enterprise computing<br />

market. Though slow <strong>to</strong> be adapted, there is definitely interest in<br />

MSMQ, if for any reason, due <strong>to</strong> the Microsoft name.<br />

As with most Microsoft services, MSMQ is implemented using a<br />

series of ActiveX components and DLLs, which provide an API for<br />

accessing its capabilities. MSMQ is Microsoft centric and will only<br />

work within a Microsoft environment. However, gateways such as<br />

Microsoft's host integration server (formerly SNA server) do exist <strong>to</strong><br />

allow MSMQ <strong>to</strong> communicate with other MOM products and other<br />

platforms.<br />

MSMQ uses queue managers in a point-<strong>to</strong>-point model. There are<br />

four types of queues within MSMQ: outgoing, system, public and<br />

private. Messages reside on queues between the time they are written<br />

by one application and the time they are read by another. Queues use a<br />

combination of memory and disk <strong>to</strong> provide s<strong>to</strong>rage consistent with<br />

particular kinds of message.<br />

MSMQ structures its resources around enterprises and sites.<br />

Information about an enterprise and sites is hosted in the message<br />

queue information s<strong>to</strong>re (MQIS) which is a database or distributed<br />

direc<strong>to</strong>ry that MSMQ uses <strong>to</strong> s<strong>to</strong>re information describing the network.<br />

At the enterprise level, a primary enterprise controller (PEC) would<br />

exist on a machine <strong>to</strong> define the information about an enterprise. Within<br />

an enterprise, MSMQ would have sites containing a primary site<br />

controller (PSC) and a backup site controller (BSC), which usually<br />

correlates <strong>to</strong> one physical location.

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

Saved successfully!

Ooh no, something went wrong!