B2B Integration : A Practical Guide to Collaborative E-commerce

More documents

Recommendations

Info

9.1. Introduction Integration Brokers 255 Traditionally, companies have used relatively flat architectures, such as file transfers, APIs and RPCs to integrate internal and external applications. These architectures utilize application specific adapters and messaging middleware. However, flat architectures are not suitable for B2Bi, which requires a more robust, scalable and systematic implementation. Such architectures, being quite rigid, lack the flexibility required in B2Bi. The physical architecture for B2Bi is multi-tiered, which introduces an integration broker between the applications (nodes) being integrated and shields the individual nodes or end points from each other and the actual integration services. Integration brokers, built primarily on messaging middleware, provide an end-to-end integration platform addressing the critical business components required to completely automate business processes across the extended enterprise. They provide wide-ranging, pre-built application adapters and bi-directional connectivity to multiple applications, including mainframe applications. Integration brokers enable data integration by allowing applications to exchange information at the program level (application oriented integration) or data level (data oriented integration). An integration broker extracts data from the source node at the right time, transforms the data, converts the schema and routes the data to the target node. Here, the node can be an application, a program, or a person — as defined in the business process workflow. Communication between applications and an integration broker occurs mostly in the form of messages. An integration broker also provides a repository for archiving, searching and retrieving these messages. Integration brokers do not replace traditional middleware as MOM, RPC and distributed TP monitors. They are in fact built on top of existing middleware technology, most often on messaging middleware. Therefore, in this chapter we will focus on integration brokers built on messaging middleware, also called message brokers. Message brokers are also known as middleware for extranets. A few leading vendors for integration brokers include — IBM MQSeries Integrator; Extricity; BEA eLink; webMethods B2B Enterprise; Mercator Enterprise Broker, WebBroker, CommerceBroker; NEON
256 B2B Integration — A Practical Guide to Collaborative E-commerce eBusiness Integration Servers; SeeBeyond e*Exchange eBusiness Integration Suite; Tibco ActiveEnterprise, ActivePortal, ActiveExchange; Vitria BusinessWare; CrossWorlds Software; and Microsoft BizTalk Server. 9.1.1. Integration brokers enable (best-of-breed) BOB approach A typical medium to large size company needs multiple applications that collectively support its entire business operation. No single software vendor can provide all these applications with elaborate functionalities for each industry. Integration brokers enable enterprises to select solutions from different software vendors that provide greater domain expertise and functional support. With their use, for example, a company can implement Clarify CRM, PeopleSoft Human Resources, Ariba e-Procurement, Oracle Financial, i2 SCM and SAP Utilities. 9.2. Architecture of Integration Brokers Integration brokers are based on one of two distinct fundamental physical architectures: hub-and-spoke and message bus. Another derived architecture, known as multi-hub, connects several integration brokers, each of which is based on hub-and-spoke or message bus architecture. Let's have a closer look at these architectures: 9.2.1. Hub-and-spoke architecture In hub-and-spoke architecture, there is a central server (hub) to which all internal and external applications (spokes) are connected (see Figure 9.1). The central server is actually the integration broker that provides all the integration services. The addition of any new application is extremely simple in this architecture, it simply needs to be plugged into the hub. From there onwards, it can communicate with any other application also connected with the hub. Administration of the integration
Page 1 and 2:
nioioimuc;./! 1011 1 1 .«.•.«!
Page 3 and 4:
This page is intentionally left bla
Page 5 and 6:
Published by Imperial College Press
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
xii B2B Integration — A Practical
Page 15 and 16:
xiv B2B Integration — A Practical
Page 17 and 18:
xvi B2B Integration — A Practical
Page 19 and 20:
xviii B2B Integration — A Practic
Page 21 and 22:
xx B2B Integration — A Practical
Page 23 and 24:
xxii B2B Integration — A Practica
Page 25 and 26:
xxiv B2B Integration — A Practica
Page 27 and 28:
xxvi B2B Integration — A Practica
Page 29 and 30:
xxviii B2B Integration — A Practi
Page 31 and 32:
xxx B2B Integration — A Practical
Page 33 and 34:
xxxii B2B Integration — A Practic
Page 35 and 36:
xxxiv B2B Integration — A Practic
Page 37 and 38:
xxxvi B2B Integration — A Practic
Page 39 and 40:
xxxviii B2B Integration — A Pract
Page 41 and 42:
Page 43 and 44:
4 B2B Integration — A Practical G
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
10 B2B Integration — A Practical
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Chapter 2 Components, Benefits, Cha
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Chapter 4 Enterprise Application In
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Chapter Q Extensible Markup Languag
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244: 204 B2B Integration — A Practical
Page 293: Chapter Q Integration Brokers The f
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Chapter "] 2 Wireless Technologies
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
Page 393 and 394:
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Page 409 and 410:
Company Brience Everypath GadgetSpa
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Page 429 and 430:
Page 431 and 432:
Page 433 and 434:
Page 435 and 436:
Page 437 and 438:
Page 439 and 440:
Page 441 and 442:
Page 443 and 444:
Page 445 and 446:
Page 447 and 448:
Page 449 and 450:
Page 451 and 452:
Page 453 and 454:
Page 455 and 456:
Page 457 and 458:
Page 459 and 460:
Page 461 and 462:
Page 463 and 464:
Page 465 and 466:
Page 467 and 468:
Page 469 and 470:
Page 471 and 472:
Page 473 and 474:
Page 475 and 476:
Page 477 and 478:
Chapter "] 5 E-Marketplaces and Col
Page 479 and 480:
Page 481 and 482:
Page 483 and 484:
Page 485 and 486:
Page 487 and 488:
Page 489 and 490:
Page 491 and 492:
Page 493 and 494:
Page 495 and 496:
Page 497 and 498:
Page 499 and 500:
Page 501 and 502:
Page 503 and 504:
Page 505 and 506:
Page 507 and 508:
Page 509 and 510:
Page 511 and 512:
Page 513 and 514:
Page 515 and 516:
Page 517 and 518:
Page 519 and 520:
Page 521 and 522:
Page 523 and 524:
Page 525 and 526:
Page 527 and 528:
Page 529 and 530:
Page 531 and 532:
Page 533 and 534:
Page 535 and 536:
Page 537 and 538:
Page 539 and 540:
Page 541 and 542:
Page 543 and 544:
Page 545 and 546:
Page 547 and 548:
Page 549 and 550:
Page 551 and 552:
Page 553 and 554:
Page 555 and 556:
Page 557 and 558:
Page 559 and 560:
Page 561 and 562:
Page 563 and 564:
Page 565 and 566:
Page 567 and 568:
Page 569 and 570:
Page 571 and 572:
Page 573 and 574:
Page 575 and 576:
Page 577 and 578:
Page 579 and 580:
Page 581 and 582:
Page 583 and 584:
Page 585 and 586:
Page 587 and 588:
Page 589:
This comprehensive guide reveals th
show all

B2B Integration : A Practical Guide to Collaborative E-commerce

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?