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.

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

messaging and distributed objects. RPC is a procedural model, which<br />

primarily supports synchronous calls. In addition, RPC carries a<br />

significant amount of network overhead — it can be network hog. The<br />

many levels of services, which once made RPC appealing, also created<br />

the performance bottlenecks which make it very slow across large<br />

networks.<br />

3.4.3. Application oriented integration and <strong>B2B</strong>i<br />

The applications <strong>to</strong> be integrated for <strong>B2B</strong>i support different business<br />

lines of individual companies. This bag of application consist of a mix<br />

of home developed applications, third party solutions (such as ERP,<br />

CRM, SCM) and legacy systems. Their integration with the applications<br />

of the trading partners is much more than just making a remote method<br />

call or making one component talk <strong>to</strong> another remote component.<br />

It is a fairly straightforward task <strong>to</strong> integrate two applications<br />

developed by a single company using the same language and running<br />

on the same platform. However, integrating applications developed and<br />

maintained by different companies using different programming language<br />

and running on different platforms is an extremely daunting effort.<br />

For a successful implementation of this integration pattern, companies<br />

have <strong>to</strong> give away au<strong>to</strong>nomy and develop applications in close<br />

cooperation with the partners. Making any changes <strong>to</strong> support new<br />

business logic or technical feature requires informing and coordinating<br />

with the partners, which makes this integration pattern the least flexible<br />

of all the integration patterns. Because of its inflexibility, which requires<br />

making coding changes for every small change in business flow, this<br />

integration pattern is also the most expensive in the long run. It creates<br />

dependency that can have a major impact on the business operations of<br />

the companies participating in <strong>B2B</strong>i.<br />

Application oriented integration also requires making strict<br />

authentication checks before executing the function or method. The call<br />

<strong>to</strong> functions or methods can contain malicious code as it is usually<br />

made over the Internet. Furthermore, in order for the client programs <strong>to</strong><br />

make RPCs or API calls, a company needs <strong>to</strong> open its firewall, which<br />

can pose security threats. Finally, A2A integration does not help a<br />

company <strong>to</strong> improve business processes.

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

Saved successfully!

Ooh no, something went wrong!