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.

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

9.3.4. Workflow manager<br />

<strong>Integration</strong> brokers work on the definition and management of the flow<br />

of messages that represent business processes between integrated<br />

applications. Thus, it is imperative for them <strong>to</strong> have a sophisticated<br />

workflow manager, which would allow users <strong>to</strong> visually create workflows<br />

representing inter-company business processes in the form of a sequence<br />

of events, routes, tasks and users. The execution environment should<br />

support event triggers, rules-based processing, threaded conversations,<br />

au<strong>to</strong>matic event notification, timing control, triggers, exception<br />

management and alternative and parallel routing of documents.<br />

Advanced rules-based processing in an integration broker reduces<br />

the messaging overhead with content-based message recognition and<br />

routing. Rules support the creation and dispatch of multiple messages <strong>to</strong><br />

multiple destinations from a single input message, while allowing<br />

different formats for each. The rules can be updated immediately, over<br />

time or on a delayed time frame. This sort of flexibility provides<br />

business users with effective control over business processes in a fast<br />

changing <strong>B2B</strong> environment.<br />

As a typical <strong>B2B</strong> example, an incoming purchase order may require<br />

cross-reference checking with ERP system for valid component<br />

identification number, financial system for verification of credit and<br />

several other necessary steps <strong>to</strong> complete the integration in<strong>to</strong> business<br />

applications. These rules and the associated flow logic should be easily<br />

created within the broker-provided graphical user interface and shared<br />

between maps, reducing development time significantly.<br />

9.3.5. Metadata reposi<strong>to</strong>ry<br />

Metadata reposi<strong>to</strong>ries s<strong>to</strong>re the definitions, formats, data elements and<br />

flow of messages that are used <strong>to</strong> exchange data between companies.<br />

<strong>Integration</strong> brokers can use these defined formats <strong>to</strong> parse and process<br />

messages.<br />

9.3.6. Administration <strong>to</strong>ol<br />

An integration broker should provide a graphical, user-friendly<br />

administration <strong>to</strong>ol that supports wide-ranging administrative functions,

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

Saved successfully!

Ooh no, something went wrong!