Using the Data Pool Service for Machine-to-Machine (M2M ...
Using the Data Pool Service for Machine-to-Machine (M2M ...
Using the Data Pool Service for Machine-to-Machine (M2M ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>M2M</strong> components<br />
There are 3 sub-systems involved in an <strong>M2M</strong> implementation.<br />
• The Membership Organization’s (MO) <strong>Data</strong> <strong>Pool</strong> Manager (DPM) system<br />
• The GXS Communications (Comms) Gateway dedicated <strong>to</strong> your service instance<br />
• The Supplier’s system<br />
Once a Comms Gateway has been associated with a DPM instance, all <strong>M2M</strong> files sent from DPM and<br />
received by DPM will flow between <strong>the</strong> DPM instance and its Comms Gateway. This Comms Gateway is an<br />
instance of <strong>the</strong> GXS Enterprise Gateway system. The Comms Gateway exchanges files with <strong>the</strong> <strong>M2M</strong> user<br />
via ei<strong>the</strong>r an AS2 link or via FTP and a dedicated mailbox on your system.<br />
Once <strong>M2M</strong> is selected in <strong>the</strong> company profile and any event causes data <strong>to</strong> flow out of or in<strong>to</strong> <strong>the</strong> DPM<br />
instance, it will always flow between <strong>the</strong> DPM instance and its Comms Gateway regardless of what<br />
communications pro<strong>to</strong>col is being used downstream between <strong>the</strong> end user and <strong>the</strong> Comms Gateway. The<br />
communications pro<strong>to</strong>col chosen by <strong>the</strong> end user has nothing <strong>to</strong> do with <strong>the</strong> link between <strong>the</strong> DPM instance<br />
and its Comms Gateway.<br />
<strong>M2M</strong> Guide <strong>for</strong> Suppliers 1
Change language