![]() ![]() ![]() |
![]() |
|
|
![]() ![]() ![]() ![]() ![]() |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Return to B2B and Agents Trying to achieve B2B integration by programming does not scale due to the high number of combinations of B2B protocols like EDI or RosettaNet, business processes, document formats, back end applications and trading partners. Furthermore, programming does not provide the necessary flexibility, reliability, and consistency. Instead, a set of B2B integration modeling constructs is proposed in this paper that allow to model B2B integration dynamically: B2B protocol, application protocol, workflow types, transformation, binding, trading partner and business event ![]() DiSC'03 © 2003 Association for Computing Machinery |