Front cover

WebSphere Business siness Integration for SAP AP
WebSphere and SAP integration using WBI Adapters Business connectivity using WBI brokers WBI and SAP XI interoperability scenario

Saida Davies Khirallah Birkler Niall Cargill Tino Friedemann Reinhard Heite Tony Shan Sudha Chandra Veerni Torsten Wilms

ibm.com/redbooks

International Technical Support Organization WebSphere Business Integration for SAP December 2004

SG24-6354-00

Note: Before using this information and the product it supports, read the information in “Notices” on page xxix.

First Edition (December 2004) This edition applies to: Version 8, Release 1, Modification 5.473 of IBM DB2 Version 5, Release 3, Modification 0 of WebSphere MQ + CSD05 Version 5, Release 0, Modification 3 of WebSphere Business Integration Message Broker Version 5, Release 1, Modification 0 of WebSphere Business Integration Server Foundation Version 5, Release 1, Modification 1 of WebSphere Studio Application Developer Integration Edition Version 4, Release 2, Modification 2.2 of WebSphere Business Integration ICS Version 2, Release 4, Modification 0 of WebSphere Business Integration Adapter Framework Version 5, Release 5, Modification 0 of WebSphere Business Integration Adapter for mySAP.com Version 5, Release 5, Modification 2 of WebSphere Business Integration Adapter for mySAP.com Version 2, Release 4, Modification 0 of, WebSphere Business Integration Adapter for JDBC Version 1, Release 1, Modification 0 of WebSphere Business Integration Adapter for Lotus Domino Version 6, Release 0, Modification 0 of Lotus Domino Version 1, Release 0, Modification 0 of WebSphere Business Integration Adapter for SAP XI Version 3, Release 0, Modification 0 of SAP XI
© Copyright International Business Machines Corporation 2004. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxvii Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi The team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxxii Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxix Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxix Part 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Chapter 1. Introduction and book structure . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2 What this book is . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.3 How this book is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.3.1 Part structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.3.2 Chapter structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.4 What this book does not cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Chapter 2. Business Integration technology concepts . . . . . . . . . . . . . . . . 9 2.1 Technology overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.1.1 Business Integration needs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.1.2 Integration challenges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.1.3 Concepts and terminologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.1.4 IBM WebSphere Business Integration product family . . . . . . . . . . . . 14 2.2 IBM Business Integration Reference Architecture. . . . . . . . . . . . . . . . . . . 19 2.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.2.2 Comprehensive Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 2.2.3 Roles and sample artifacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 2.2.4 IBM software offerings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.2.5 Service Oriented Architecture (SOA) . . . . . . . . . . . . . . . . . . . . . . . . 37 2.2.6 e-business on demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 2.3 SAP Enterprise Service Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 2.3.1 People Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 2.3.2 Information Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 2.3.3 Process Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

© Copyright IBM Corp. 2004. All rights reserved.

iii

2.3.4 Application platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 2.3.5 Solution Lifecycle Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 2.3.6 Composite Application Framework . . . . . . . . . . . . . . . . . . . . . . . . . . 49 2.4 Interoperability of WBI and SAP XI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Part 2. Business scenario solution design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Chapter 3. Business case scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 3.1 Business domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 3.1.1 Current business model of Company A . . . . . . . . . . . . . . . . . . . . . . 54 3.1.2 Current business model of Company B . . . . . . . . . . . . . . . . . . . . . . 56 3.1.3 Merger business objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 3.1.4 Unified business model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 3.1.5 Unified business model benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 3.2 Business Use Case definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 3.2.1 Use Case 1 - Product data repository . . . . . . . . . . . . . . . . . . . . . . . . 62 3.2.2 Use Case 2- Internal purchase requisition process . . . . . . . . . . . . . 64 3.2.3 Use Case 3 - Inventory availability validation . . . . . . . . . . . . . . . . . . 66 3.2.4 Use Case 4 - Customer data repository . . . . . . . . . . . . . . . . . . . . . . 69 3.3 Constraints and assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Chapter 4. Solution approaches and technology options . . . . . . . . . . . . . 73 4.1 Basic technology integration components. . . . . . . . . . . . . . . . . . . . . . . . . 74 4.2 SAP specialities regarding business integration . . . . . . . . . . . . . . . . . . . . 77 4.2.1 Support of various SAP releases . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 4.2.2 Support of a staged system landscape . . . . . . . . . . . . . . . . . . . . . . . 80 4.2.3 Support of various SAP R/3 interfaces . . . . . . . . . . . . . . . . . . . . . . . 81 4.3 WebSphere Business Integration product suite capabilities . . . . . . . . . . . 82 4.3.1 WebSphere Business Integration adapters. . . . . . . . . . . . . . . . . . . . 82 4.3.2 WebSphere InterChange Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 4.3.3 WebSphere Business Integration Server Foundation . . . . . . . . . . . . 88 4.3.4 WebSphere Business Integration Message Broker . . . . . . . . . . . . . 91 4.3.5 Integration server selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 4.4 WebSphere Business Integration in the SAP environment . . . . . . . . . . . . 94 4.4.1 WBI Adapter for mySAP.com . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 4.4.2 WBI Adapter for SAP Exchange Infrastructure . . . . . . . . . . . . . . . . 104 Chapter 5. Solution design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 5.1 Business process analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 5.2 Design principles and methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 5.3 System context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 5.3.1 Logical model of Company A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 5.3.2 Logical model of Company B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 5.3.3 Unified model of merged enterprise . . . . . . . . . . . . . . . . . . . . . . . . 114

iv

WebSphere Business Integration for SAP

5.4 System architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 5.5 Communications and connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 5.6 Use Case 1 - Solution overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 5.6.1 Process flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 5.6.2 Technology selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 5.6.3 Solution details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 5.7 Use Case 2 - Solution overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 5.7.1 Process flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 5.7.2 Technology selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 5.7.3 Solution detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 5.8 Use Case 3 - Solution overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 5.8.1 Process flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 5.8.2 Technology selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 5.8.3 Solution detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 5.9 Use Case 4 - Solution overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 5.9.1 Process flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 5.9.2 Technology selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 5.9.3 Solution detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 5.10 Related technology used in this book . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Part 3. Business scenario solution implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Chapter 6. Environment setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 6.1 Technology matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 6.2 Run-time environment overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 6.3 Common installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 6.3.1 Installing IBM DB2 UDB Version 8.1 with FixPack 5. . . . . . . . . . . . 150 6.3.2 Installing WebSphere MQ V5.3 with CSD04 . . . . . . . . . . . . . . . . . . 171 Chapter 7. Use Case 1: WBIMB using WBI Adapter for mySAP.com . . . 173 7.1 Operational model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 7.2 Installation of WebSphere Business Integration components . . . . . . . . . 176 7.2.1 Plan the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 7.2.2 Install Microsoft Windows 2000 Service Packs . . . . . . . . . . . . . . . . 178 7.2.3 Install a Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . 179 7.2.4 Install IBM DB2 UDB V8.1 with FixPack 5 . . . . . . . . . . . . . . . . . . . 179 7.2.5 Install Microsoft Data Access Component (MDAC) V2.7 . . . . . . . . 179 7.2.6 Install WebSphere MQ V5.3 with CSD05 . . . . . . . . . . . . . . . . . . . . 180 7.2.7 Install IBM Agent Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 7.2.8 Install WebSphere Business Integration Message Broker . . . . . . . 180 7.2.9 Install Message Broker FixPacks . . . . . . . . . . . . . . . . . . . . . . . . . . 192 7.2.10 Install WBI Adapter Framework V2.4 . . . . . . . . . . . . . . . . . . . . . . 194 7.2.11 Install WBI Adapter for mySAP.com . . . . . . . . . . . . . . . . . . . . . . . 199 7.3 Configuration of WebSphere Business Integration components . . . . . . . 203

Contents

v

7.3.1 Configure WebSphere MQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 7.3.2 Create a message broker domain. . . . . . . . . . . . . . . . . . . . . . . . . . 210 7.3.3 Configure the WBI Adapter for mySAP.com to access SAP R/3 via ALE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 7.3.4 Configure the WBI Adapter for mySAP.com to access SAP R/3 via the ABAP Extension module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 7.4 Configuration of SAP R/3 - general configuration steps . . . . . . . . . . . . . 233 7.4.1 Configure a SAP Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 7.4.2 Create a CPIC User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 7.4.3 Set up a RFC Destination from SAP R/3 to Gateway . . . . . . . . . . . 234 7.5 Configuration of SAP R/3 to work with the ALE Module of the Adapter . 236 7.5.1 Create a partner logical system . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 7.5.2 Create a local SAP logical system . . . . . . . . . . . . . . . . . . . . . . . . . 237 7.5.3 Create a Distribution Model in the inbound SAP application. . . . . . 239 7.5.4 Create a Distribution Model in the outbound SAP application . . . . 242 7.6 Configuration of SAP R/3 to work with the ABAP Extension Module of the Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 7.6.1 Creating the /CWLD/ namespace . . . . . . . . . . . . . . . . . . . . . . . . . . 243 7.6.2 Install connector transport files for the ABAP Extension Module . . 248 7.6.3 Process the business objects in the ABAP Extension module . . . . 256 7.6.4 Create an Event triggering and detection mechanism . . . . . . . . . . 258 7.7 Development of WebSphere Business Integration Business Objects . . . 273 7.7.1 Create Business Object for the ALE module. . . . . . . . . . . . . . . . . . 274 7.7.2 Create Business Object for the ABAP Extension Module . . . . . . . . 283 7.7.3 Create Message Sets and loading Business Object Definitions . . . 288 7.8 Development of a message flow for the MaterialSynchronization (ALE Module) scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 7.8.1 Create a Message Flow Project . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 7.8.2 Build the message flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 7.8.3 Configure the message flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 7.8.4 Write ESQL for the Compute node . . . . . . . . . . . . . . . . . . . . . . . . . 302 7.9 Development of a message flow for the OrderEventNotification (ABAP Extension Module) scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 7.9.1 Create a Message Flow Project . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 7.9.2 Build the message flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 7.9.3 Configure the message flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 7.10 Deployment of the message flow applications . . . . . . . . . . . . . . . . . . . 310 7.10.1 Deploy a message broker archive. . . . . . . . . . . . . . . . . . . . . . . . . 310 7.11 Run the business scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 7.11.1 Part 1: Run the MaterialSynchronisation (ALE) scenario . . . . . . . 312 7.11.2 Part 2: Run the OrderEventNotification (ABAP Extension Module) Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 7.12 Usage of the Message Broker’s trace to locate errors . . . . . . . . . . . . . 325

vi

WebSphere Business Integration for SAP

7.13 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Chapter 8. Use Case 2: WBISF using WBI Adapter for mySAP.com . . . 327 8.1 Operational model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 8.2 Installation of WebSphere Business Integration components . . . . . . . . . 330 8.2.1 Plan the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 8.2.2 Install WSADIE V5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 8.2.3 Install WBISF V5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 8.2.4 Install IBM Remote Agent Controller V5.1 . . . . . . . . . . . . . . . . . . . 344 8.2.5 Install WBI Adapter Framework V2.4 . . . . . . . . . . . . . . . . . . . . . . . 349 8.2.6 Install WBI Adapter for mySAP.com V5.5 . . . . . . . . . . . . . . . . . . . . 355 8.3 Configuration of WebSphere Business Integration components . . . . . . . 359 8.3.1 Configuration of WebSphere MQ . . . . . . . . . . . . . . . . . . . . . . . . . . 359 8.3.2 Configuration of WBI Adapter for mySAP.com . . . . . . . . . . . . . . . . 360 8.3.3 Configuration of WSADIE V5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 8.3.4 Configuration of WBISF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 8.4 Development of a business process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 8.4.1 Create Business Objects and Connector Configuration . . . . . . . . . 374 8.4.2 Import prepackaged workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 8.4.3 Create the ERP Procurement Service . . . . . . . . . . . . . . . . . . . . . . 392 8.4.4 Create the HR Information Lookup Service . . . . . . . . . . . . . . . . . . 398 8.4.5 Deploy the ERP Procurement service. . . . . . . . . . . . . . . . . . . . . . . 404 8.4.6 Deploy the HR Information Lookup service. . . . . . . . . . . . . . . . . . . 407 8.4.7 Incorporate external services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 8.4.8 Design Internal Order business process . . . . . . . . . . . . . . . . . . . . . 412 8.4.9 Configure the Visual Test Connector . . . . . . . . . . . . . . . . . . . . . . . 431 8.4.10 Configure the mySAP.com Connector . . . . . . . . . . . . . . . . . . . . . 433 8.5 Deployment of the business process . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 8.6 Run the business process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 8.6.1 Create internal orders using the Web client . . . . . . . . . . . . . . . . . . 441 8.6.2 Execute approval activity using the Web client . . . . . . . . . . . . . . . . 454 8.6.3 Review approved internal orders using the Web client . . . . . . . . . . 460 8.7 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464 Chapter 9. Use Case 3: WICS using WBI Adapter for mySAP.com and JDBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465 9.1 Operational model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466 9.2 Installation and configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466 9.2.1 Installing Microsoft Windows 2000 Service Packs . . . . . . . . . . . . . 467 9.2.2 Installation of WebSphere MQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 9.2.3 Configuration of WebSphere MQ . . . . . . . . . . . . . . . . . . . . . . . . . . 467 9.2.4 Installation of IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472 9.2.5 Configuration of IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472

Contents

vii

9.2.6 Installation of Interchange Server . . . . . . . . . . . . . . . . . . . . . . . . . . 475 9.2.7 JDBC Adapter Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 9.2.8 mySAP.com Adapter Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . 496 9.3 Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497 9.4 Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543 9.5 Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548 9.6 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552 Chapter 10. Use Case 4: Integration of SAP XI with WBI InterChange Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555 10.1 Overview of Use Case CustomerDataRepository . . . . . . . . . . . . . . . . . 556 10.2 Operational model for CustomerDataRepository . . . . . . . . . . . . . . . . . 558 10.3 Configuring the adapter for Lotus Domino . . . . . . . . . . . . . . . . . . . . . . 559 10.3.1 The architecture of the adapter for Lotus Domino. . . . . . . . . . . . . 561 10.3.2 Configuring the Domino server for the adapter . . . . . . . . . . . . . . . 562 10.3.3 Configure the Domino connector . . . . . . . . . . . . . . . . . . . . . . . . . 567 10.3.4 Test the configured connector for Lotus Domino . . . . . . . . . . . . . 586 10.4 Configure the adapter for SAP XI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598 10.4.1 The architecture of the adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . 598 10.4.2 Generate Business Object Definitions . . . . . . . . . . . . . . . . . . . . . 599 10.4.3 Define the map Customer_Debmas01 . . . . . . . . . . . . . . . . . . . . . 602 10.4.4 Configure the configuration meta-object . . . . . . . . . . . . . . . . . . . . 604 10.4.5 Configure the XML data handler meta-object . . . . . . . . . . . . . . . . 606 10.4.6 Configure the connector for SAP XI . . . . . . . . . . . . . . . . . . . . . . . 607 10.4.7 Create WebSphere MQ queues . . . . . . . . . . . . . . . . . . . . . . . . . . 610 10.5 Configure SAP Exchange Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . 611 10.5.1 Overview of SAP XI configuration . . . . . . . . . . . . . . . . . . . . . . . . . 612 10.5.2 Register back-end systems in System Landscape Directory . . . . 614 10.5.3 Configure SAP XI using the Integration Directory . . . . . . . . . . . . . 619 10.5.4 Configure the Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . 629 10.5.5 Configure the SAP R/3 back-end system . . . . . . . . . . . . . . . . . . . 631 10.5.6 Define the JMS provider for the SAP XI JMS adapter . . . . . . . . . 633 10.5.7 Test configured SAP XI together with WBI adapter for SAP XI . . 634 10.5.8 Import the XML schema for DEBMAS01. . . . . . . . . . . . . . . . . . . . 639 10.6 Run the scenario CustomerDataRepository . . . . . . . . . . . . . . . . . . . . . 641 10.7 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642 Chapter 11. Best practices and lessons learned . . . . . . . . . . . . . . . . . . . 643 11.1 General hints and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644 11.2 Use Case 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644 11.3 Use Case 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644 11.4 Use Case 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645 11.5 Use Case 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646

viii

WebSphere Business Integration for SAP

Appendix A. Scripts, source, and test data . . . . . . . . . . . . . . . . . . . . . . . 647 Use Case 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648 Use Case 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652 Use Case 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656 Appendix B. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659 Locating the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659 Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659 System requirements for downloading the Web material . . . . . . . . . . . . . 660 How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660 Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661 Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663 IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663 Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663 Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663 How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664 Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665

Contents

ix

x

WebSphere Business Integration for SAP

Figures
2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 2-10 3-1 3-2 3-3 3-4 3-5 3-6 3-7 4-1 4-2 4-3 4-4 4-5 4-6 4-7 4-8 4-9 4-10 4-11 4-12 4-13 4-14 4-15 4-16 4-17 4-18 4-19 4-20 4-21 BI Reference Architecture - Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 20 WBI Reference Architecture - Comprehensive Services . . . . . . . . . . . . 25 WBI Reference Architecture - Artifacts . . . . . . . . . . . . . . . . . . . . . . . . . 29 WBI Reference Architecture - Software offerings . . . . . . . . . . . . . . . . . 32 Adapter architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 SAP NetWeaver overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 SAP NetWeaver standards support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 SAP Exchange Infrastructure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 SAP Web Application Server architecture . . . . . . . . . . . . . . . . . . . . . . . 48 WebSphere Business Integration and SAP Exchange Infrastructure . . 50 Conceptual model of Company A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Conceptual model of Company B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Conceptual model of the merged enterprise . . . . . . . . . . . . . . . . . . . . . 60 Business case diagram - Use Case 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Business case diagram - Use Case 2 . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Business case diagram - Use Case 3 . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Business case diagram - Use Case 4 . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Business Integration with direct connections . . . . . . . . . . . . . . . . . . . . . 74 Business Integration with a central integration broker . . . . . . . . . . . . . . 75 Internal structure of an adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Type description driven by data transformation within an adapter. . . . . 76 Bidirectional communication between an EIS and integration broker . . 77 Different SAP system releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Typical SAP system landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Sketch of a business object Definition “Customer” . . . . . . . . . . . . . . . . 83 Adapter architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Configuration tools for WBI adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 WebSphere InterChange Server Architecture . . . . . . . . . . . . . . . . . . . . 86 On demand Integrated Platform Suite . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Business process execution container architecture . . . . . . . . . . . . . . . . 90 Adapter based integration in WBISF . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 WBI Message Broker extends WBI Event Broker . . . . . . . . . . . . . . . . . 91 WBI Message Broker Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 WBI Adapter for mySAP.com architecture, white board style . . . . . . . . 95 Modules of the WBI Adapter for mySAP.com - detailed view . . . . . . . . 96 Deployment topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 BAPI Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 HDR Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

© Copyright IBM Corp. 2004. All rights reserved.

xi

4-22 4-23 4-24 4-25 4-26 5-1 5-2 5-3 5-4 5-5 5-6 5-7 5-8 5-9 5-10 5-11 5-12 5-13 5-14 6-1 6-2 6-3 6-4 6-5 6-6 6-7 6-8 6-9 6-10 6-11 6-12 6-13 6-14 6-15 6-16 6-17 6-18 6-19 6-20 6-21 6-22 6-23 6-24

RFC Server Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 ALE Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 ABAP Extension Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Architecture of WBI adapter for SAP XI V1.0. . . . . . . . . . . . . . . . . . . . 105 Architecture of WBI Adapter for SAP XI, V2.0 . . . . . . . . . . . . . . . . . . . 106 Logical architecture of Company A . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Logical architecture of Company B . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Logical architecture of merged enterprise . . . . . . . . . . . . . . . . . . . . . . 114 System architecture of merged enterprise . . . . . . . . . . . . . . . . . . . . . . 116 Communications diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Business process flow for Use Case 1a . . . . . . . . . . . . . . . . . . . . . . . 120 Business process flow for Use Case 1b . . . . . . . . . . . . . . . . . . . . . . . 122 Solution detail for Use Case 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Business process flow for Use Case 2 . . . . . . . . . . . . . . . . . . . . . . . . 127 Business process flow for Use Case 3 . . . . . . . . . . . . . . . . . . . . . . . . 132 Solution detail for Use Case 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Business process flow for Use Case 4 . . . . . . . . . . . . . . . . . . . . . . . . 137 Solution detail for Use Case 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Simplified architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Run-time environment diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 IBM DB2 Launchpad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Product Installation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 IBM DB2 Setup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 License Agreement window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Installation type selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Installation Features window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 APPC Support Warning window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Language Selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 User ID configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Set up the administration contact list window . . . . . . . . . . . . . . . . . . . 158 IBM DB2 instance creation window . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 IBM DB2 instance configuration window . . . . . . . . . . . . . . . . . . . . . . . 160 IBM DB2 tools catalog preparation window . . . . . . . . . . . . . . . . . . . . . 161 Health monitor notification contact window . . . . . . . . . . . . . . . . . . . . . 162 Satellite system information window . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Install options review window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Installation in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Setup completion window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 IBM DB2 launchpad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Product installation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Process warning window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 IBM DB2 setup wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Installation progress window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

xii

WebSphere Business Integration for SAP

. . . . . . . . 201 Program group selection . . . . 185 Install type selection page . . . . . 175 Operational model: OrderEventNotification scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Installation summary . . . . . . . . . . . . . . . . . . . 181 Installer welcome page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 The broker services user account page . . . . . . . . . . . . . . . . 215 Broker domain details page . . . . . . . 206 WebSphere MQ Listener properties . . . . . . . . . . . . . . . . . . . . 218 Successful default configuration created . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 The install completion screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 The Software License Agreement page. . . . . . . . . . . . . . . . . . . . 202 MQ Services . . . . . . . . . . . . . . . . 199 License agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-25 7-1 7-2 7-3 7-4 7-5 7-6 7-7 7-8 7-9 7-10 7-11 7-12 7-13 7-14 7-15 7-16 7-17 7-18 7-19 7-20 7-21 7-22 7-23 7-24 7-25 7-26 7-27 7-28 7-29 7-30 7-31 7-32 7-33 7-34 7-35 7-36 7-37 7-38 7-39 7-40 7-41 7-42 Installation completion window . . . . . . . . . . . . . . . . 196 WebSphere MQ library location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Program group selection . . . . . . . . . . . . . . . . 195 Installation directory . . . . . . . . . . . . . . . . . . 202 Final window . . . . . . . . . . . . . . . . . . . 182 The migration prerequisites page . . . . . . . . . . . . . . . . . . . . . . . . . 188 The Security Wizard. . . . . . 195 License agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Operational model: MaterialSynchronization scenario. . . . . . . . . . . . . . . . . . . . . . . . 218 Standard connector properties. . . . . . . . . . . 201 Interchange Server name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 The Getting Started wizard welcome page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Figures xiii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 WebSphere Adapter Framework location . . 217 The Getting Started wizard summary page . 197 Workbench installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Welcome screen . . . . . . . . . . . . . . . . . . . . . . . 192 Language selection . . . . . . . . . . . . . . . . . . . 186 The installation summary page . . . . 176 The Installer language selection dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Language selection . . . 184 The Install location page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 The Message Broker tooling welcome page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Installation summary . . . . . . . 187 WebSphere Business Integration Event Broker install progress . . . . . . . . . . . . . . . . . . . 190 The User Select and Create page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Security Wizard summary page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Welcome screen . . . . . 216 The broker details page . 221 Connector specific properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Final window . . . . . . .

. . . . . . . . . . . .Overview . . . . . .Confirmation of transport import . . . . . . .Select Target Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Repository Namespace view . . . . . . 259 Business Object Repository . . . 268 Add business object . . 267 Change View “IBM CW Object parameter configuration” . . . . . . . . . . . . 241 Transaction we20: Partner profiles . . . . . . . . 271 xiv WebSphere Business Integration for SAP . . . . . . . . . . . 253 Assign transport layer for the development class . .Import Request . . . .Overview . 240 Transaction we21: Ports in IDoc processing . . . . . . 242 Transaction se03 . . . . . . . . . . . . . . . . . . . .Development Tab . . . . . . . . . . . . . . . . . . 270 Add configuration values . . . . . . . . . . . . . . . . . . . . 242 Transaction bd64: Add a message type to the model view . . . . . . . 259 Business Object Repository Browser. . . .Details . . . . . . . . . . . . . . 238 Transaction bd64: Create a model view . . . . . . . . . . . . . . . . . . . . 246 New Entry details . . . . . . . . . . . . . . . . . . . . . 236 Transaction bd54: Logical systems . . . . . . . .Retrieve . . . . 253 Transaction STMS . . . 234 Transaction sm59: RFC Destination . . . . . . . . . . . . . 260 SAP Easy Access main view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Transaction bd64: Add a message type to the model view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Transaction se38 . . . . . . . . . . . . . 251 Transaction STMS . . 263 Change View “Instance Linkages” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-43 7-44 7-45 7-46 7-47 7-48 7-49 7-50 7-51 7-52 7-53 7-54 7-55 7-56 7-57 7-58 7-59 7-60 7-61 7-62 7-63 7-64 7-65 7-66 7-67 7-68 7-69 7-70 7-71 7-72 7-73 7-74 7-75 7-76 7-77 7-78 7-79 7-80 7-81 7-82 7-83 7-84 7-85 Supported Business Objects . .ABAP Editor . . . . . . . . . . . . . 247 Transaction STMS . .Details . . . . . . . . . . . . . . . . . . . . . . . 257 Business Object Builder . . . . . . . . . . . . 269 Add BO_EVENTRIGGER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Generate partner profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Standard properties of the connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Log and Trace File . . . .Add transport request to the queue . . . . . . . . . . . . . . . . . . . . 237 Transaction scc4: Link local SAP logical system to a client. . . . . . . . . . . . . . . . . . . . 266 CW Configuration Objects . . . . . . . 245 Repository Namespace view . . . . . . . . . . . . . . . . . . . . . 261 Event type linkages . . . . . . . . . . . . . . . . 265 IBM CrossWorld Station . . . . . . . 262 Event Type Linkages . . . . . . . . 228 Connector specific properties .Overview view . . . . 224 Log and trace file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Transaction bd64: Create a model view . . . . . . . . . . . . . . . . . . . . . . .Transport Organizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Sales order business object processing . . . . . . . . . . . . . . . . . . . . . . . . 232 Transaction su01: Maintain User . . . . . . . . . 264 Instance Linkages . . . . . . . 239 Transaction bd64: Generate Partner Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Transaction STMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Supported Business Objects for the ABAP Extension & ALE Module . . . . . . .new entries . . . . . . . . . . . . . . . . . .

. . . . . . 289 Deploy to Message Broker workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 New User Project . . . . 273 SAP Object Discovery Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Supply additional information in the Business Object Wizard . . . . . . . . . . 286 Business Objects in the Integration Library . . . . . . . . . . . . 279 Select the IDoc in the Business Object Wizard . . . . . . . . . . . . . . 283 Business Objects in the Integration Component Library . . . . . . . . . . . 315 Test Connector . . . . . . . . . . . . . . . . . . . . . 290 Deploy the Business Objects to the Message Broker Toolkit . . . . . . . . . . . . . . . . . . . 307 The pass through message flow . . . . . . . . . . . . . . . . . . . 297 The MaterialSynchronization_MsgFlow message flow nodes. . . . 281 Business Objects in the Integration Component Library . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 Figures xv . . . . . . . . . . . . . . . . . . . . . . . . . . 287 Business Object in the User Project . . . . . . 293 Define the CwXML format . . . . . . . . . . 299 MQ Input Node Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Create new User Project . . . . . . . . . . . . 277 Select the SAP ODA in the Business Object Wizard . . . . . . . . . . . . . . 316 Test Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Verify the selection in the Business Object Wizard . . . . . . . . . . . . . . 308 MQ Input Node Properties . . . . . . . . . . . .outbound IDoc log information . . . . . . . . . . . . . 298 The MaterialSynchronization_MsgFlow message flow validated. . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 The message flow nodes . . . . . . . . . . . . . . . . . . . . 296 Create a new message flow. 280 Add the IDoc message type in the application specific information . . . . . . . . . . . 313 Transaction we02 . 294 Create a new message flow project . . . . . . . . . . . . . . . 309 Deploy broker archive file . . . . . . . . . . . . . . . . . .Broker preferences . . . . . . . . . . . .Create/Select Profile . . . . . . . . . . . 285 Business Object for the ABAP Extension module . . . . . . . . . . . . . . . . . . . . . . . . . 292 Define the CwXML format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Event distribution . . . . . . . . . . . . . . . .New entry . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Application specific information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Send Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 Properties in the Business Object Wizard . . . . . . . . . . . . . . . . . 293 Message set Default Wire Format and Runtime Parser . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Create a new message flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 Transaction we02 . .Retrieve . . . . . . . . . . . . .7-86 7-87 7-88 7-89 7-90 7-91 7-92 7-93 7-94 7-95 7-96 7-97 7-98 7-99 7-100 7-101 7-102 7-103 7-104 7-105 7-106 7-107 7-108 7-109 7-110 7-111 7-112 7-113 7-114 7-115 7-116 7-117 7-118 7-119 7-120 7-121 7-122 7-123 7-124 7-125 7-126 7-127 7-128 Modify BO Metadata . . . . . . 301 Create a new message flow project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Business Objects in the User Project. . . 311 Transaction bd10 . . . . . 275 Create a new Integration Component Library . 291 Deploy the Business Objects to the Message Broker Toolkit . .inbound IDoc log information . . . . . . . . . 292 Deploy the Business Objects to the Message Broker Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 System Manager . . . . . . . . . . . . . . . . . . .

. . . . . . 333 License agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Final window . . . . . . . . . . . . . . . . .Connect . . . . . . . 345 License agreement . . . . . . . . . . . . . . . 343 Final installation window . . . . . . . . . . . 317 Test Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 Installation destination folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 Registration window . . . . . . . . . . . . . . . . . . . . . 334 Installation summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 Run as service feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 xvi WebSphere Business Integration for SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 Installation type . . . 321 Standard Order created . . . . . . . . . . . . . 348 Final window . . . . . . . . . . . . . . . . 337 License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .SAP_2Connector profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 Select language . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Installation features . . . . . 324 Review the business object data in the Test Connector . . . . . . . . . . . . . . . . . . . . 341 Installation summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 WSAD Integration Edition Launchpad . . . . . . . 344 Install Shield welcome window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Connector Profile . . . . . . . . . . . . . . . . . . .7-129 7-130 7-131 7-132 7-133 7-134 7-135 7-136 7-137 7-138 7-139 8-1 8-2 8-3 8-4 8-5 8-6 8-7 8-8 8-9 8-10 8-11 8-12 8-13 8-14 8-15 8-16 8-17 8-18 8-19 8-20 8-21 8-22 8-23 8-24 8-25 8-26 8-27 8-28 8-29 8-30 8-31 8-32 Test Connector . . . . . . . . . . . . . . . . 339 Installation directory . . . . . . . . . . . . . . . 340 Node name and host name . . . . . . . . 320 Creating a Standard sales order . . . . . . . . . . . . . . 336 Installation wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Welcome window . . . . . . . . . . . . . . . 345 Customer Information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 Remote Agent Controller access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 Incoming business object. . . . . . . . . . . . 346 Java Runtime Environment folder . . . . . . . . . . . . . . . . . . . . . . . . . . 348 Ready to install window . . . . . . . . 318 Test Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Installation directory . . . . . . . . . . . . . . . . . . . 322 Connector trace . . 325 Activate trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 Language selection . . 350 License agreement . . . . . . . . . . . . . . . . . . . . . . . . . 335 WebSphere Business Integration Server Foundation Launchpad . . . . . 319 Transaction va01: Create Sales Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Welcome window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Operational model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 WebSphere Business Integration Server Foundation Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 Security settings. . . . . . . . . . . . . . . . 318 Test Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .New Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . 376 New Business Object using ODA . . . . . . . . . . . . . . 369 Business Process Container database setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 Integration component library settings . . . . . . . . . . 375 Create a new business object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 Figures xvii . . . . 381 Create new connector configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Business Process Container JMS resources . . . . . . . . . . . . . . . . . . . . . . . . 373 New Integration Component Library . . . . . . . . . . . 357 Interchange Server name . . . . . . . . . . . . . . 353 Workbench installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 Business Object properties . . . . . . . . . . . . . . 356 WebSphere Adapter Framework location . . 357 Program group selection . . . . . . . . . . . 383 Connector specific properties . . . . . . . . . . 352 WebSphere MQ library location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Program group selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 Business Process Container JMS setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 Create new local server and configuration. . . . . . . . . . . . . . . . . . . . . . . . . . 351 Installation summary . . . . . . . . . . 381 Open connector template. . . . . . . . . 363 Set environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 Create WebSphere MQ JMS connection factory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 ODA detection . . . . . . . . . . . . 384 New User project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 Browsing the Business Object Repository . . . . . . 355 Welcome window . . . . . . 358 Final window . . . . . . 366 Run administration console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 Search a table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 Business Object properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 Create WebSphere MQ JMS queue destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Set variable DB2_JDBC_DRIVER_PATH . . . . . . . . . . . . . . . . . 378 Select a table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Enable administrative console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 Standard connector properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 Installation summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 Save BO configuration . . . .8-33 8-34 8-35 8-36 8-37 8-38 8-39 8-40 8-41 8-42 8-43 8-44 8-45 8-46 8-47 8-48 8-49 8-50 8-51 8-52 8-53 8-54 8-55 8-56 8-57 8-58 8-59 8-60 8-61 8-62 8-63 8-64 8-65 8-66 8-67 8-68 8-69 8-70 8-71 8-72 8-73 8-74 8-75 Installation directory . . . . . . . . . . . . . . . . . . . . . . . . . . 354 Language selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 Local server name and server type . . . . . . . . . . . . . . . . . . . . . . . 365 Enable WebSphere security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Set variable MQ_INSTALL_ROOT . . . . . . . . 354 Final window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 License agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 Create new Service Skeleton. . . . . . . . . . 410 Create a new Service Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 Drop Notification service . 420 Drop create internal order service . . . . . . . . . . . . . . . . . . . . . 390 Project content directory . . 399 Import wizard . . . . . . . . . . . . . . . . . . 400 Deployment wizard . 409 Add project to Test Server . . . . . . . . . . . . . . . 411 Create a new package . . . . . . . . 419 Expand external services tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418 Select Output operation . . . . . . . . . . . 420 Drop HR Information Lookup service . . . . . . 398 Import from file system. 386 Deploy WAS project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394 Deployment wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 Location for generated classes . . . . . . . . . . . . . . . 393 Generate Deploy Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 Adjust reference binding for Queue Connection factory . . . . . . . . . . . . 395 Inbound service files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 xviii WebSphere Business Integration for SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422 Staff activity properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 Select the export directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 Add project to Test Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 Create Business Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 Select Import data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 Adjust reference binding for Queue Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 Adjust reference binding for Queue Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-76 8-77 8-78 8-79 8-80 8-81 8-82 8-83 8-84 8-85 8-86 8-87 8-88 8-89 8-90 8-91 8-92 8-93 8-94 8-95 8-96 8-97 8-98 8-99 8-100 8-101 8-102 8-103 8-104 8-105 8-106 8-107 8-108 8-109 8-110 8-111 8-112 8-113 8-114 8-115 8-116 8-117 8-118 New user project settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 Select JNDI name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 File structure . . . . . . . . . . . . . . . . . 421 Connect business process nodes . . . . . . . 392 Import wizard . . . . . . . . . . . . . . . 387 Component selection page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 Create a new package . . . . . . . . . . . . . . 396 Select JNDI name . . . . . . . . . . . . . . . . . . . . . . . 412 Create a new Service project . . . . . . . . . . . . . . . . 407 Adjust reference binding for Queue Connection factory . . . . . . . . . . . . . . . . . . . 422 Select activity owner . . . . . 415 Define locations . . . . . . . . . . . . . . . . . . . . . . . . 391 Import from file system. . . . 403 File structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 Create new port and binding . . . . . . . . . . . . . . . 401 Inbound service files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 Folder structure . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . 459 Internal order request list after approval . . . . . . . 457 Approve second order . . . . . . . . . . . . . . . . . . . . . . . . . . 450 Processed order details of first order . . . . . . . . . . 434 Remote server host name . . . . 472 Figures xix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-119 8-120 8-121 8-122 8-123 8-124 8-125 8-126 8-127 8-128 8-129 8-130 8-131 8-132 8-133 8-134 8-135 8-136 8-137 8-138 8-139 8-140 8-141 8-142 8-143 8-144 8-145 8-146 8-147 8-148 8-149 8-150 8-151 8-152 8-153 8-154 9-1 9-2 9-3 9-4 9-5 9-6 9-7 Properties of getHRData . . . . . . . . . . . . . . . . 439 Add projects to remote server . . . . . 435 Review installation directory . . . . . . . 428 File location window . . . . . . . . . . . . . . 426 Add variable for staff activity . . . . . 432 Virtual Test Connector GUI . . . . . . . . . . . . . . . . . . 451 Order details of second order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469 Configuring the queue manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 JNDI name selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426 Deploy code generation properties . . 456 Second order start approval activity. . . . . . . . . . . . . . . . . . . . 440 Login to Web client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Start InternalOrder process . . . . . . . . . . . . 431 VTC profile list . . . . . . . . . . . . 470 Queue manager configuration output . . . . . . . . . . . . . . . . . . . . . . . . . . . 455 Second order details . . . . . . . . . . . . . 463 Operational model . . . . . . . . . . . . . . . . . 437 Remote target directory . . . 448 Internal order request list . . . . . . . . . . . . 425 Select staff activity parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 Order details of third order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 Place third internal order . . . . . . . 430 Create a new VTC Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424 Add variable for request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 Create remote deployment server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458 Reject third order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 Select InternalOrder process . . . . . . . . . . . . . . . . . . . . . . . . . . 461 Second internal order details after approval . . 468 Creating a queue manager . . . . . . . . 424 Add variable for response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 Application server HTTP port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444 Place first internal order . . . . . . . . . . . . . . . . 469 Modifying the Configure Queue manager shortcut . . . . . . . . . . . . . . . 436 Remote target directory type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 Approvers My To Dos list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 Place second internal order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462 Third internal order details after rejection . . . . . . . . . . 466 WebSphere MQ local queue configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 IBM DB2 administrative group creation . . . .

. . . . . . . . . . . . . . . . . . . . . 494 Installation progress . . . . . . . . . . . . . 474 Installation language selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485 Configuration update confirmation . . . . . . . . . . . . . . . . . . . . . . 476 License agreement window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481 Review installation options. . . .9-8 9-9 9-10 9-11 9-12 9-13 9-14 9-15 9-16 9-17 9-18 9-19 9-20 9-21 9-22 9-23 9-24 9-25 9-26 9-27 9-28 9-29 9-30 9-31 9-32 9-33 9-34 9-35 9-36 9-37 9-38 9-39 9-40 9-41 9-42 9-43 9-44 9-45 9-46 9-47 9-48 9-49 9-50 IBM DB2 administration configuration . . 473 Database manager configuration update . . . . . . . . .bat file . . . . . . . . . . . 491 JDBC adapter InstallShield wizard. . . . . . . . . . . . . . . . . 486 WebSphere InterChange Server configuration . . . . . . . . . . . . . 476 Installation directory selection window . 490 JDBC adapter installation language selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497 Integration process . . . . 493 WebSphere InterChange Server name entry window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495 Installation completion . . . 474 ICSREPOS database configuration . . . . . 477 Installation options window . . . . . 489 Installation progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 start_SAP. . .bat file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495 start_SAPODA. . . . . . 473 Create database command . . . . . . 475 WebSphere InterChange Server InstallShield wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492 License agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 Installation summary window . . . . . . . . . . . . . . . . . . . . 489 Installation options review window . . .WebSphere MQ . . 484 WebSphere InterChange Server configuration . . . . . . . . . . 494 Start programs folder name selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 Toolset InstallShield wizard . . . . . . . . . . . . . . . . . . . . . . . . 488 WebSphere InterChange Server installation directory . . . . . . . . . . . . . . . . . . . . . . . . . 486 Installation summary . . . . . . . . . . 492 Adapter installation directory . . . . . . . . . . . . . . . . . . . . . . . 473 DB2 Instance Attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481 Installation progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480 Start programs folder name selection . . . . . . 472 Startup of IBM DB2 command line processor (CLP) . . . . . . . . . . . . . . . . . . . . 493 Installation options review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 Installation completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480 WebSphere InterChange Server service configuration . . . 483 WebSphere InterChange Server configuration . . . . . . . 479 WebSphere InterChange Server name . . . . . 479 IBM DB2 installation location . . . . . . . . . . . . . . . . . . . . . . . . . . 498 xx WebSphere Business Integration for SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482 WebSphere InterChange Server configuration wizard launch window 482 WebSphere InterChange Server configuration . . . . . . . 478 Database selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515 New business object . . 516 Project selection. . . . . . . . . . . . . . . . 514 db2_REC_COM business object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506 Optional parameter prompt . . . . . 502 Create new Business Object Using ODA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .source selection . . . . . . . . . . . . . . 502 New Business Object dialog . . . . . . . 507 Application-specific information . . . . . . . . . . . . . . . . . . .agent selection . . . . 513 db2_AVAILABILITY business object . . . . 516 Create new map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517 Destination business object selection . . . . . . . . . . . . .agent configuration . . . . . . . . . . . . . . . .completion . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 Map name and mapping direction specification . . . . 518 Mapped: sap_bapi_material_availability to Generic_Business_Object 519 Activity diagram for custom verb mapping rule . . . . . . . . . . . . . . . . . . . . . .source selection . . . 499 Warning message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 Business Object Wizard . . . . . . . . . . . . . . . . 500 System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .configure ODA . . 503 Business Object Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524 Custom mapping for db2_AVAILABILITY to Generic_Busines_Object 525 Figures xxi . . . . . . . . 500 Project creation . . . . . . . . . . . . . . . . . . . . . . . . 506 Business object generation . . . . . . . . . . 509 Business Object Wizard . . . . . . . . . . . . . . . . . . . . . . . . 502 Create New Business Object . . . . 510 Business Object Wizard . . . . . . . . . . . . . 512 Business Object Wizard . . . . . . . . . . 520 Map name and mapping direction specification . . . . . . 514 db2_WMDVSX Business Object . 504 Business Object Wizard . . . . . . . . . . . . . .completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512 Business object generation . . . . . . . . . . . . . . . . 508 sap_bapi_material_availability business object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 Business object properties . . . . . . . . . .confirmation of source . . . . . . . . . 503 Business Object Wizard . . . . . . . . . . . . . . . . . 499 WebSphere Studio Workbench . . . . . . . . . . . . . . . . . . 517 Source business object selection. . . . . . . . . . . . . . 523 Mapped: db2_AVAILABILITY object to Generic_Business_Object . . . 510 Business Object Wizard . . . . . . . . . . . . . . . . . . . . . . 501 Launch the SAP Object Discovery Agent (ODA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500 New Integration Component Library . . . . . . . . . . . . . . . . 505 Business Object Wizard . . . . . . . . . . . . . . . . . . . . . . .confirmation of source . . . . . . . . . . . .agent selection . . . . . . . . . 522 Map name and mapping direction specification . . . . . . . . . . . . . . . . . . . .9-51 9-52 9-53 9-54 9-55 9-56 9-57 9-58 9-59 9-60 9-61 9-62 9-63 9-64 9-65 9-66 9-67 9-68 9-69 9-70 9-71 9-72 9-73 9-74 9-75 9-76 9-77 9-78 9-79 9-80 9-81 9-82 9-83 9-84 9-85 9-86 9-87 9-88 9-89 9-90 9-91 9-92 9-93 System Manager preferences window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507 Business Object Wizard . . . . . . . . . . . . . . . . . . . 521 Mapped: Generic_Business_Object to db2_AVAILABILITY object . . . . . . . . . . . . . . 515 Generic_Business_Object . . . . .

. . . . . . . . . . 547 Map compilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544 New user project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548 RFC destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545 WebSphere InterChange Server startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542 Collaboration general properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 Generic_Business_Object to sap_bapi_material_availability_object . . . . . . . . . 537 Scenario naming . . 550 SAP function module selection screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533 SAP connector standard properties . . . . . . . . . . 528 Open file menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528 JDBC template file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 SAP connector-specific properties . . . . . . . . . . . . . 531 JDBC connector map associations . . . . . . 537 Collaboration scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540 Create new collaboration . . . . . . . . . . . . . . . 535 New collaboration template creation . . . . . . . . 546 Deployment . 539 Launch collaboration creation wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . 527 Create new connector . . . . . . . . . . . . . . . . 551 Test function module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536 Edit template definitions . . . . . . . . . . . . . . . 527 New connector template selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543 WebSphere InterChange Server project creation . . . . . . . . . . . . . . . . . . . . . . . 531 JDBC connector supported business objects . . . 530 JDBC connector specific properties . . . . .bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-94 9-95 9-96 9-97 9-98 9-99 9-100 9-101 9-102 9-103 9-104 9-105 9-106 9-107 9-108 9-109 9-110 9-111 9-112 9-113 9-114 9-115 9-116 9-117 9-118 9-119 9-120 9-121 9-122 9-123 9-124 9-125 9-126 9-127 9-128 9-129 9-130 9-131 9-132 9-133 9-134 9-135 9-136 Map name and mapping direction specification . . . . . . . . . 538 Set collaboration target port . . 549 RFC destination creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541 Port bindings . . . . . . . . . . . . . 545 Persistent Name Server startup . . 534 SAP connector supported business objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 SAP connector template file. . . 552 xxii WebSphere Business Integration for SAP . . . . . . 547 Deployment confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544 Location of PerstentNameServer. . . . . . . . . . . . . . . . . . . . . . 539 Set scenario that triggers collaboration . . . . . . . . 535 SAP connector map associations . . . . . . . . . . 536 Scenario creation . . . . . . . . . . . . . . 536 Port creation and assignments . . . . . . . . . . . . . . . . . . 529 JDBC connector specific properties . . . . . . . . . . . . 548 Collaboration template compilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545 Register a WebSphere InterChange Server . . . . . . . . . . . . . . . . . . . 551 Results received as Export parameters . . . . . . . . . 535 Create new collaboration template . . . . . . . . . . . . . . . . . . . . . . . .

. . . 586 Get PortConnector as a copy of DominoConnector.10-1 10-2 10-3 10-4 10-5 10-6 10-7 10-8 10-9 10-10 10-11 10-12 10-13 10-14 10-15 10-16 10-17 10-18 10-19 10-20 10-21 10-22 10-23 10-24 10-25 10-26 10-27 10-28 10-29 10-30 10-31 10-32 10-33 10-34 10-35 10-36 10-37 10-38 10-39 10-40 10-41 10-42 10-43 Business process model of Use Case CustomerDataRepository . . . . . . . . . . . 558 Components of a connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568 Name the new integration library . . . . 577 Create connector configuration . . . 567 Create a new integration library . . . . . . . . . . . . . . . . . . . 575 Move transformation for the Verb and ObjectId attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557 Operational model: CustomerDataRepository implementation . . . . . . 571 Insert the first row for the business object Customer . . . . . . . . . . . . . . . . . . . . . . 560 Architecture of the adapter for Lotus Domino for event processing . . . . . . . . . . . . . . . . . . . . . . 590 Figures xxiii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584 Enter the installation directory of CollaborationFoundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580 Connector specific properties . . . . . 564 Access Control List for Customer Contacts . . . . . . . . . . . . . . . . 571 Customer business object type in the Business Object Designer . . . . . . . . . . . . 569 DominoDocument business object type in Business Object Designer 570 New business object Customer . . . . . . . . 587 Enter PortConnector as ApplicationName . . . . . . . 581 Associated Maps properties. . . . . . . . . . . . . . . . . . . . . . . . . 557 SAP Exchange Infrastructure internal components . . . . . . . . . . . . . . . . . . . . 565 Event Table configuration document . 569 Create New Business Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581 Supported Business Objects properties. . . . . . . . 579 Standard properties of the connector for Lotus Domino . . . . . . 564 Open Event Table database . . 583 Import from Repository File . 566 Elements of the WBI system manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587 Create New Collaboration Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 Create a new map . . . . . . . . . . 568 Business object type DominoDocument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574 Selecting the source of the DominoDocument_Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581 Messaging properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589 Start registering the ICS to the system manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562 Create the Customer Contacts database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577 Execution order of the transformation steps . . . . . 589 Graphical view on Domino2PortConnectorCollaborationObject . . . . . . . . . 572 Mapping of a DominoDocument to a Customer business object . . . . . . . . . . . . . . 588 Bind ports of Domino2PortConnectorCollaboration . . . . . . . . . . . . . 575 Name the map “DominoDocument_Customer” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556 WebSphere InterChange Server internal processing . . . . . . . . . . . 576 Define the initial custom map . . . . . . . 582 Components of a collaboration template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585 Associate Customer business object & Collaboration Foundation ports585 Using the Visual Test Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . 611 General components of SAP XI . . . . . . . . . . . . . . 615 New technical system type Web AS ABAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593 Create new profile for VTC . . . . 613 SAP Exchange Infrastructure Tools . . . . 602 Definition of map Customer_Debmas01 . . . . . . . . . . . . . . . . . . . . . . . . . . 597 Attribute values of received business object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592 Shutdown ITSOC_WICS gracefully . . . . . . . . . . . . . . . . . . 592 Deploy CustomerDataRepository_Proj . 601 Select ROOT attribute as key for business object DEBMAS01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617 New technical system of type Third-Party . 594 Connect the VTC to ICS using the selected profile . . . 601 Save generated business object to CustomerDateRepository library . . . . . . . . . . . . . . . . . . 607 Connector specific properties of the SAPXIConnector . . . . . . . 596 Received business object in VTC . 596 Event in “Event Table” database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609 Shared queues between SAP XI and WBI Adapter for SAP XI . . . . . . . . . 594 Select profile in VTC . . . . . . . . . . . . . 617 New Business System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612 Entities to be configured within the Integration Directory . . . . . . . . . . . . . . . 595 Create “Contact” document in “Customer Contacts” database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605 Insert new row in MO_SAPXIConnector . . . . . . . . . . . . . . .10-44 10-45 10-46 10-47 10-48 10-49 10-50 10-51 10-52 10-53 10-54 10-55 10-56 10-57 10-58 10-59 10-60 10-61 10-62 10-63 10-64 10-65 10-66 10-67 10-68 10-69 10-70 10-71 10-72 10-73 10-74 10-75 10-76 10-77 10-78 10-79 10-80 10-81 10-82 10-83 10-84 10-85 10-86 Specify the ICS instance to the system manager . . . . . . . . . . . . . . . . . . . . 603 Name map Customer_Debmas01 and select Mapping Direction . . . . . . . . . . . . . . . . . . . . . . . . . 605 Define values for MO_SAPXIConnector . . . . . . . 600 Select XML ODA Agent . . . . . . . . 605 Definition of XML data-handler meta-object. 615 Links for configuring Technical and Business Landscape in SLD . 591 Create CustomerDataRepostory_Proj . . . . . . . . . . . . . . . . 610 Overview: SAP XI processing for CustomerDataRepository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591 Call Deploy user project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593 Check that components of ITSOC_WICS are activated . . . . . . . . . . . . . . . . . . . . . . . 609 Specify “Customer_Debmas01” as associated maps . . . . . . . 617 Technical System Wizard for registering InterChange Server . . . . . . . . . . . . . . . . . . . . . . . . 601 Select DEBMAS01 as the source node for ODA generation . 591 Select New ICS Project . . . . . . . . . . . . . . 590 Connect the System Manager to the InterChange Server instance. . . . . . 597 Request processing of the adapter for SAP XI . . . . . . . . . . . . . . . . . 616 Register Software in SLD. . . . . 608 Supported business objects for the SAPXIConnector . . 598 Issuing New Using ODA within the Business Object Designer . . . . . . . . . . . . . . . . . . . . . . . . 600 Enter the file name of the DEBMAS01 XML schema file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604 Name the meta-object MO_SAPXIConnector . . . . . . 616 Technical System Wizard for registering R/3 back end . . . . . . . 618 xxiv WebSphere Business Integration for SAP . . . .

. . . . . . . . . . . .10-87 Definition of business system EnterpriseCore in SLD . . . . . . . . . . . . . . . . . . . . . . . . . . . 641 10-123 Export DEBMAS01 as XSD file . . 618 10-88 Definition of business system MasterDataEntrySystem in SLD. . . 640 10-122 Change list after importing DEBMAS01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625 10-99 Start creating a receiver determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625 10-100 Specification of the receiver determination . . . . . . . . . . 633 10-110 Test configured SAP XI together with WBI adapter for SAP XI . . . . . . . . . . . . . . . . . . . . . . .log. . . 632 10-108 Create distribution model DEBMASFROMXI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634 10-111 Tree view on PortConnector2SAPXICollaboration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628 10-103 Activate the Change List . . . . . . . . . 620 10-90 Start assigning Business System to CustomerDataRepository . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637 10-117 Processed XML Messages within the SAP Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635 10-113 Create business object of type Customer within the VTC . . . . . . . . . . . . 639 10-120 Start importing IDoc from the SAP back end . . . 624 10-98 Sender agreement for sender MasterDataEntrySystem . . . . . . . . . . . . . . . . . 630 10-105 Create port for IDoc adapter . 640 10-121 Choose DEBMAS01 for import . . . . . . . . 636 10-115 Check the business object DEBMAS01 in InterChangeSystem. . . . . . . . . . . . . . . . . . . . . . . 641 10-124 Collaboration object Domino2SAPXICollaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642 Figures xxv . . . . . 631 10-107 Specify RFC destination C11CLNT800 . . . . 629 10-104 RFC destination IDS800 . . . . . . . . . . . . . . . . . . . . . . . . 623 10-96 Module configuration for communication channel JMS2XI . . . . . . . . . . . 622 10-94 XI Settings for communication channel JMS2XI . . . . . . . . . . . . . . . . . . . . . . . 621 10-92 Create a new communication channel . . . . . . . . . . . . . . . . . . . . . . . . . . . 630 10-106 Load metadata for IDoc type DEBMAS01 . . . . . . . . . 638 10-119 Details of received IDoc within SAP R/3 . . . . . . . . . . . . . 627 10-102 Edit receiver agreement . . . . . . . . . 632 10-109 Add message type to the distribution model . . . . . . . . . . 626 10-101 Edit Interface Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637 10-116 SAP XI Integration Engine Monitoring . . . . . . . . . . . . . . . . . . . . . . 623 10-97 Parameter values for communication channel IDOC2IDS . . . 635 10-112 Update user project “CustomerDataRepository_Proj” . 636 10-114 Send the business object . 621 10-93 Parameter values for communication channel JMS2XI . . . . . . . . . . . . . . . . . 622 10-95 Modules for the communication channel JMS2XI . . . . . 620 10-91 Assign Business System EnterpriseCore . . . . . . . . . . . . . . . . . . . . 638 10-118 List of processed IDocs within . . . . . . . . . . . . . 619 10-89 Create scenario CustomerDataRepository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxvi WebSphere Business Integration for SAP .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 534 Host specific configurations: implementation of ICS on node ITSOC . . . . . . . . 2004. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506 ODA configuration parameters . . . xxvii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Standard connector properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Connector queues for the ALE module . . . . . . . . 533 Standard properties . . . . . . . . . . . . . . . . . 212 Standard connector properties. . . . . . . . . . . . . . . . . . . . . . . . . . 146 Run-time environment components . . . . . . . . . . . . . . . . . . . . . . . . 330 Product installation directories . . . . . . 117 Communications mechanisms . . . . . . . . 208 Components created by the Getting Started wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Technology matrix . . 13 Integration terminology . . . . . . . . . . . . . . . . . . . . . . . . . 523 Mapping: Generic_Business_Object to sap_bapi_material_availability526 JDBC Connector: Connector-Specific tab recommended settings . . . . . . . . . . . 529 Standard properties . . . 177 Product installation directories . . . . . . . . . . . . . . . . . . . . . . . . . . 13 IBM WebSphere Business Integration product family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . All rights reserved. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Use Case characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 WebSphere Application Server interaction patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Integration servers in merged enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Connector specific properties . 228 Connector transport files . . . . . 387 Test data . . . . . . . . 249 ODA configuration parameters . . . . . . . 15 Integration brokers characteristics matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510 Mapping: sap_bapi_material_availability to Generic_Business_Object519 Mapping for Generic_Business_Object to db2_AVAILABILITY . . 148 Prerequisites: WebSphere Business Integration Message Broker . . . . . . . . . 503 Recommended business object property values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530 SAP Connector Configuration . . . . . 178 The security groups that are created by the Security Wizard . . . . . . . . . . . . . . . . . . . . 521 Mapping for db2_AVAILABILITY to Generic_Business_Object . . . . 559 © Copyright IBM Corp. . . . . . . . . . . . . . . . . . . . . . 445 ODA configuration parameters . . . . . . . . . . . . . . 278 Software prerequisite list . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Connector specific properties . . . . . . .Tables 2-1 2-2 2-3 4-1 5-1 5-2 5-3 6-1 6-2 7-1 7-2 7-3 7-4 7-5 7-6 7-7 7-8 7-9 7-10 7-11 7-12 8-1 8-2 8-3 8-4 8-5 9-1 9-2 9-3 9-4 9-5 9-6 9-7 9-8 9-9 9-10 9-11 10-1 Integration styles . . . . . . . . . . . 189 Connector queues . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Adapter queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .10-2 10-3 10-4 10-5 10-6 10-7 10-8 10-9 Files to copy into the Domino server directories . . . . . . . . . . . . . . . . . . . .INI . . . . . .sda . . . . . . 633 xxviii WebSphere Business Integration for SAP . . .jar . . . . . . . . . . . . . . . . . 566 Copying NCSO. . . . . . . . . . . . . . . . . . . . . 566 Entries within NOTES. . . . . . . . 614 Adding WebSphere MQ Java libraries aii_af_jmsproviderlib. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .INI for HTTP and IIOP . . . . . . . . . . . . . . . . . . 565 Add-on to NOTES. . . . . 566 Standard properties for the connector for SAP XI . 633 Modifications within the file server/providerlib . . . . . . . . . . 607 Named entities within the SAP XI configuration. . . . .

or service that does not infringe any IBM intellectual property right may be used instead. and products. using. cannot guarantee or imply reliability. IBM may not offer the products.A. serviceability. To illustrate them as completely as possible. modify. INCLUDING. or function of these programs. program. program. program. program. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND. However. The furnishing of this document does not give you any license to these patents. brands. This information contains examples of data and reports used in daily business operations. in writing. to: IBM Director of Licensing. these changes will be incorporated in new editions of the publication. NY 10504-1785 U. or service may be used. which illustrates programming techniques on various operating platforms.S. for the purposes of developing. Consult your local IBM representative for information on the products and services currently available in your area. therefore. marketing. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. and distribute these sample programs in any form without payment to IBM. therefore. using. compatibility or any other claims related to non-IBM products. services. You can send license inquiries. IBM Corporation. and distribute these sample programs in any form without payment to IBM for the purposes of developing. IBM. or features discussed in this document in other countries. or distributing application programs conforming to IBM's application programming interfaces. or service is not intended to state or imply that only that IBM product. BUT NOT LIMITED TO. COPYRIGHT LICENSE: This information contains sample application programs in source language. this statement may not apply to you. Any functionally equivalent product. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. You may copy. it is the user's responsibility to evaluate and verify the operation of any non-IBM product. © Copyright IBM Corp. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.S. 2004. Information concerning non-IBM products was obtained from the suppliers of those products. Any reference to an IBM product. xxix . modify. companies. These examples have not been thoroughly tested under all conditions. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. IBM may have patents or pending patent applications covering subject matter described in this document. This information could include technical inaccuracies or typographical errors.Notices This information was developed for products and services offered in the U. Changes are periodically made to the information herein. marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. THE IMPLIED WARRANTIES OF NON-INFRINGEMENT. IBM has not tested those products and cannot confirm the accuracy of performance. All rights reserved. Some states do not allow disclaimer of express or implied warranties in certain transactions. EITHER EXPRESS OR IMPLIED. North Castle Drive Armonk. or service. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. the examples include the names of individuals. You may copy. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. their published announcements or other publicly available sources.A.

other countries. or both. or both. product. and the Windows logo are trademarks of Microsoft Corporation in the United States.com® Redbooks (logo) ™ Domino® Lotus® Sametime® Domino Designer® Lotus Notes® Tivoli® e-business on demand™ MQSeries® WebSphere® Eserver® Notes® z/OS® Eserver® Parallel Sysplex® The following terms are trademarks of other companies: Intel Inside (logos) and Pentium are trademarks of Intel Corporation in the United States. or both: AIX® Everyplace® pSeries® CrossWorlds® Holosofx® Rational® DB2® IBM® Redbooks™ DB2 Universal Database™ ibm. other countries. xxx WebSphere Business Integration for SAP . in the United States. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems. Inc. Other company. UNIX is a registered trademark of The Open Group in the United States and other countries. and service names may be trademarks or service marks of others. other countries. or both. Windows. Microsoft.Trademarks The following terms are trademarks of the International Business Machines Corporation in the United States. other countries.

2004. and at the same time.0 The business case scenario is specifically contrived to illustrate all integration approaches the above adapters provide. an attempt is made to avoid any fictitious solutions.0 IBM WebSphere Business Integration Adapter for Lotus® Domino® V1.0 IBM WebSphere Business Integration Adapter for JText V5. and the appendixes include the source code and scripts used to create the Use Case environments. The business cases illustrate how important it is to have a flexible middleware that can rapidly create new business processes and connect back-end data within a heterogeneous system landscape.4. the first part of this redbook describes how these requirements are addressed by the IBM WebSphere Business Integration product suite. xxxi .0 IBM WebSphere Business Integration Adapter for SAP Exchange Infrastructure V1.5. The flexible WebSphere Business Integration Server architecture and the wide range of available application and technology adapters offers the customer a very fast implementation cycle by protecting already made investments. The third part describes four of these Use Cases in more technical detail. After a review of the general challenges that business integration middleware has to master. © Copyright IBM Corp.0 IBM WebSphere Business Integration Adapter for JDBC V2. The second part introduces common business integration drivers and develops ordinary Use Cases to demonstrate the capabilities of IBM WebSphere Business Integration servers in general and especially the two actual SAP related IBM WebSphere Business Integration Adapters.4.Preface This IBM® Redbook demonstrates the use of WebSphere® Business Integration products to integrate data and processes located in SAP back-end systems. The following WebSphere Business Integration adapters are utilized to implement the Use Cases: IBM WebSphere Business Integration Adapter for SAP V5. A separate environment is created for each Use Case to implement the respective Use Case scenario.1. All rights reserved. The book explains how WebSphere Business Integration supports the IBM On Demand strategy and how it relates to Enterprise Service Architectures from other vendors like SAP NetWeaver. The final chapter discusses “lessons learned”.

Raleigh Center. This covered the architecture. project management. Tino. A customer facing role with IBM Global Services included the development of services for WebSphere MQ within the z/OS and Windows® platform. and a detailed working knowledge of both IBM and Independent Software Vendors’ operating system software. and implementation of the xxxii WebSphere Business Integration for SAP . has extensive knowledge of IBM z/OS® operating system. scope. design. Khirallah Saida Davies is a Project Leader with the International Technical Support Organization (ITSO).The team that wrote this redbook This redbook was produced by a team of specialists from around the world working at the International Technical Support Organization. Niall. Saida has published several Redbooks™ on various business integration scenarios. She has experience in the architecture and design of WebSphere MQ solutions. Torsten. Reinhard Bottom Left: Tony. She is a certified senior IT specialist and has fifteen years of experience in IT. Figure 1 The Authors: Top left: Sudha. Saida.

he has been working for the Software Group Business Partner Technical Support in the Boeblingen lab. He is an IBM Certified Systems Expert for WebSphere Application Server V5 and has five years of experience with SAP Basis. Niall is a Sun Certified Java™ Programmer for the Java 2 Platform. Khirallah Birkler is an IT Architect for IBM SWG Germany. and architect areas where IBM and SAP software can be used in conjunction. Stuttgart. He has seven years experience in the J2EE software development area. as well as IBM WebSphere Studio Application Developer Version 4 and Version 5. providing updates. from 4. At IBM Software Service for Lotus in Mainz. and assesses all new SAP products. In the last three years. She has a degree in Computer Science and her background includes z/OS systems programming. He has a Bachelor of Science degree in Chemical Engineering from the University of Minnesota. design. and tools. Niall has five years of experience working with WebSphere Application Server and its supporting products. Preface xxxiii . and reviews to complete this redbook. He joined IBM six years ago and has been working in the SAP area for the last two years. re-writes. Khirallah has played an extensive role in further discussions of this redbook. Tino has a public certification as an IT-Systems Engineer and is currently studying for a degree in Computer Science while working as a full-time employee at IBM. tests. Customers. in order to include the customer and the partner requirements as well as experiments into these products. he is responsible for driving the WebSphere technology in the SAP market. He also holds product certifications in IBM WebSphere Application Server Version 4 and Version 5. Tino is also a Certified Lotus Sametime® and WebSphere Studio Developer. Niall Cargill is a Senior IT Specialist with the IBM Software Innovation Center and has been in the IT industry for seven years. Tino is a technical speaker at many public events. He holds a Bachelor of Science degree in Information Technology Management from the University of Cooperative Education. He supports Business Partners. His main responsibility is to evaluate. Tino Friedemann is a IT Specialist with the IBM Software Group. He supports WebSphere and Lotus product development. Germany. such as Cebit. and Developer Camp.0 to the latest NetWeaver release. IBM Software Symposium. Khirallah helps worldwide key customers assess scenarios where IBM software can be placed to complement SAP infrastructures.software on stand-alone systems or on systems in a Parallel Sysplex® environment. Technologies like Meta-Portal initiatives at IBM and SAP adapter innovations in Business Partner products were mainly driven by him. releases. and IBM colleagues all over the world. He joined IBM six years ago and started at the central site of IBM that installs.

tests and assesses all new SAP products. He works for the IBM AMS SAP World Wide Beta Test Site in Germany. in Computing Science from the University of Erlangen. and reviews in order to complete this redbook. he works for the IBM/SAP Collaboration Technology Support Center (CTSC) in Waldorf. He holds a Masters degree in Business Administration from Andhra University. IT security. His areas of expertise include SAP-ABAP/4. After obtaining his degree in Business Information Systems. Torsten Wilms is an IT Specialist at IBM Global Services. re-writes. Sudha Chandra Veerni is a Senior Software Engineer for Miracle Software Systems (I) Pvt Ltd. and IBM Certified e-business Solution Designer. providing updates. He also works in the EMEA AMS IGA on demand Center of Competence. on interoperability scenarios between IBM WebSphere and SAP NetWeaver. and is a Sun Certified Java 2 Programmer. WebSphere MQ.Reinhard Heite is an IT Specialist with IBM Germany. xxxiv WebSphere Business Integration for SAP . and reviews to complete this redbook. Tony Shan is a Lead Systems Architect at Wachovia Bank. he joined IBM in 2001. published in 2004. He has over four years of experience in the IT industry in the areas of EAI / B2B applications and Web Development. He has been a speaker at different conferences and taught courses on various topics in a public corporate training program. SG24-7012. He holds a degree in Computing Science from the University of Bonn and received a Ph. He has extensive experience in leading life-cycle design and development of large-scale distributed systems on diverse platforms using a variety of cutting-edge technologies and unified/agile methodologies. and tools. Tony holds three Masters degrees in Engineering and Science. Currently. as well as a Sun Certified Faculty Instructor. which is the SAP Customer Competence Center within IBM that installs. Tony is also a co-founder of the Greater Charlotte Rational® User Group. Reinhard has played an extensive role in further discussions of this redbook. providing updates. He has fifteen years of experience working for IBM and his areas of expertise include distributed computing. He has experience with SAP and IBM WebSphere products as well as with J2EE and Lotus Notes® software development. releases.NET Environment. Sun Certified Enterprise Architect. The ITSO would like to express its special thanks to the IBM SAP International Competence Center (ISICC) in Waldorf. and designing and implementing e-business solutions. Tony co-authored the redbook WebSphere MQ Solutions in a Microsoft . re-writes. Enterprise Application Integration using WebSphere Business Interchange Server. Germany for hosting this project. Torsten has played an extensive role in further discussions of this redbook. which supports AMS in their efforts to become an on demand business. India. He is a member of numerous professional associations and honorary societies. and WDI.D.

providing the human resources, hardware, software, and access to SAP systems. Sincere thanks to the following persons: Dr. Herbert Kratzer for the loan of the additional hardware during and after the residency period. Jochen Hinrichs, Bernd Shoener, and Reinhard Heite for their assistance in planning and facilitating the residency and the preparation work required to run this residency at the ISICC in Waldorf, Germany. Reinhard Heite for assisting with all the preparation work, which set the team off to a smooth start from the first day of the residency; also, physically moving the machines from floor to floor and looking after the loan hardware. Jens Hagen from SAP for his support and assistance with legal requirements. Holger Kunitz from SAP AG for his valuable consulting time towards the installation and configuration of SAP XI. The ISICC was a special place for the residency. The redbook team would like to thank the following people for their guidance, assistance, and contributions to this project: Dr. Herbert Kratzer, Manager, zServer Software System Evaluation + Test IBM Germany Jochen Hinrichs, Manager Software, IBM SAP International Competence Center IBM Germany Bernd Schoener, IBM/SAP Alliance Technology Executive IBM SAP International Competence Center IBM Germany Reinhard Heite, IT Specialist, IBM/SAP Middleware, IBM Global Services/Application Management Services IBM Germany Thomas Kasemir, Team Lead Lab-based Services for WPC IBM Germany Jonas Grundler, WPC, WPS, and WebService Expert IBM Germany Jens Hagen, Global Partner Manager Software and Global Partner Management SAP AG

Preface

xxxv

Holger Kunitz, SAP NetWeaver RIG, Exchange Infrastructure SAP AG Anthony Lowry, Certified WebSphere Business Integration Tech Sales Specialist IBM USA Morgan D Nerriec, WebSphere Business Integration Level 2 Customer Support IBM Germany Hans Joachim Dresen, Manager, IBM SAP International Competence Center Systems Group IBM Germany Herbert Diether, SAP R/3 on pSeries® IBM Germany Daniel Malhotra, IBM AMS World Wide SAP Beta Test Site IBM Germany Ralph Voelter, IBM AMS World Wide SAP Beta Test Site IBM Germany Rainer Gallus, IBM AMS World Wide SAP Beta Test Site IBM Germany Herbert Diether, IBM SAP International Competence Center IBM Germany Carol Davis, IBM SAP International Competence Center IBM Germany Steve Hellin, IT Architect, WebSphere Business Integration Services IBM USA Tom Reed, Curriculum Development Manager, WebSphere Business Integration IBM USA Wolfgang Preiss, WebSphere Business Integration Level 2 Customer Support IBM Germany Olaf Hoffmann, Software Technical Support Specialist WebSphere ICS & WebSphere Business Integration Adapter IBM Germany Rainer Staib, Leiter Practice Area TS Communications / mySAP Technology IBM Germany

xxxvi

WebSphere Business Integration for SAP

Steffen Hegner, WebSphere Business Integration Technical Presales Central / WebSphere MQ / WebSphere Business Integration Message Broker IBM Germany Sascha Koehler, WebSphere Tech Sales, SWG PubCo IBM Germany Hartmut Grell, Technical Sales, WebSphere Business Integration IBM Germany Edzard Hallenga, Migration, ABAPs, Interfaces, ALE, IDoc, eCATT, and CATT Site IBM Germany The redbook team would like to thank the following people for volunteering to review this book: Julius Peter, WW SAP Alliance Sales Executive, IBM Software Group IBM Austria Roberto P Mascarenhas IBM Brazil Axel J Schwarz, Software IT Architect IBM Germany Steffen Hegner, WebSphere BI Technical Presales Central / WebSphere MQ / WebSphere Business Integration Message Broker IBM Germany Jens Wanske, IT Specialist IBM Germany Daniel Malhotra, IT Specialist IBM Germany Ralph Voelter, IT Specialist, WebSphere Product Landscape IBM Germany Caecilie Hampel IBM Germany Morgan D Nerriec, WebSphere Lab based Services IBM Germany Kai-Hendrik Komp, Senior IT Specialist (accredited) Lotus Software IBM Germany

Preface

xxxvii

Sandro Schwedler, IT Specialist, Software Innovation Team (SWIT) IBM Germany Sebastian Klare, Specialty Software Sales Representative, Business Integration, IBM Germany Elise Sivilay, WebSphere IT Specialist/WebSphere-SAP Integration/Software Innovation Centers IBM Chicago Darren Cacy, Certified I/T Architect IBM Kansas City Naguib Attia, B2B and e-business Integration Industrial Solutions IBM Charlotte Georg Kather, SWG - ISSL - Portal-SAP Competence Team, Central Region, IBM Germany Kay Baumgartel, SWG - IBM Software Services for Lotus, Manager Competitive SWAT Team Central Region IBM Germany Markus Hieronimus, IBM SWG WebSphere Central BUE IBM Germany Axel Sass, SAP SWAT Team Portal Specialist IBM Germany The redbook team would like to thank the following people for providing valuable feedback after a review of this book: Jens Wanske, IT Specialist IBM Germany Daniel Malhotra, IT Specialist IBM Germany Ralph Voelter, IT Specialist, WebSphere Product Landscape IBM Germany Caecilie Hampel IBM Germany Morgan D Nerriec, WebSphere Lab based Services IBM Germany

xxxviii

WebSphere Business Integration for SAP

Become a published author
Join us for a two- to six-week residency program! Help write an IBM Redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You'll team with IBM technical professionals, Business Partners and/or customers. Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you'll develop a network of contacts in IBM development labs, and increase your productivity and marketability. Find out more about the residency program, browse the residency index, and apply online at:
ibm.com/redbooks/residencies.html

Comments welcome
Your comments are important to us! We want our Redbooks to be as helpful as possible. Send us your comments about this or other Redbooks in one of the following ways: Use the online Contact us review redbook form found at:
ibm.com/redbooks

Send your comments in an Internet note to:
redbook@us.ibm.com

Mail your comments to: IBM Corporation, International Technical Support Organization Dept. HZ8 Building 662 P.O. Box 12195 Research Triangle Park, NC 27709-2195

Preface

xxxix

xl

WebSphere Business Integration for SAP

Part 1

Part

1

Overview
This part provides descriptions of the objectives of this redbook project, what it covers and does not cover, an overview of how the book is organized, an introduction to the concepts and terminology used in this publication, and general descriptions of technologies related to the sample business scenario solution illustrated in the later chapters. It also includes more detailed discussion on the IBM WebSphere Business Integration product and SAP integration. Part I is comprised of Chapters 1 to 2. Chapter 1, “Introduction and book structure” on page 3 describes the objectives of this redbook project and a high-level overview of what it covers. Chapter 2, “Business Integration technology concepts” on page 9 explores the integration technologies offered by IBM and SAP. The interoperability of WebSphere Business Integration and an SAP system are addressed.

© Copyright IBM Corp. 2004. All rights reserved.

1

2

WebSphere Business Integration for SAP

1

Chapter 1.

Introduction and book structure
This chapter describes the objectives of this IBM Redbook and provides a high-level overview of what this book covers. It also contains an overview of how this book is organized.

© Copyright IBM Corp. 2004. All rights reserved.

3

1.1 Objectives
Integration of enterprise processes and applications is an important focus area of today’s e-business solutions. In a heterogeneous environment, integration becomes more challenging, as various types of solution options are available for integrating different platforms and technologies. Appropriate integration solutions promise great cost and efficiency benefits by automating and controlling the interactions of disparate systems. They are also the essential supporting technologies for Business Process Management (BPM) and thus an enabler for Business-to-Business (B2B) technology.

1.2 What this book is
This book is about business application and process integration between disparate systems. The primary focus is: WebSphere Business Integration brokers for various integration styles WebSphere Business Integration adapters for SAP integration Application connectivity and process orchestration Some key integration features of business integration are demonstrated in the solution design of a sample business scenario. The capabilities of WebSphere Business Integration (WBI) in application connectivity and process orchestration are shown in the implementation. In particular, the various connectivity approaches of WebSphere Business Integration brokers and adapters to SAP back-end systems are investigated and various combinations of usage scenarios are explored. All brokers and SAP specific WebSphere Business Integration adapters are utilized in the integration solution development. The use of process orchestration in asynchronous workflow processes that use staff interaction are also shown in the book. This book provides an overview of the business integration landscape, but focuses on the capabilities of the WebSphere Business Integration (WBI) product set to incorporate SAP back-end systems into WBI infrastructures. The objectives are listed as follows: Review different technology options for process integration and application connectivity. Justify WebSphere Business Integration for SAP integration. Illustrate different integration styles. Design a solution to a sample business case. Implement the major Use Cases in the solution.

4

WebSphere Business Integration for SAP

Document best practice guidance and lessons learned in integration implementation. Briefly discuss trends and convergence of related technologies.

1.3 How this book is organized
This section describes the organization of this publication.

1.3.1 Part structure
This book follows a structure with the intention to make the reading experience more valuable and to provide separate parts for different interest groups. This redbook consists of three parts: Part 1, “Overview” on page 1 Part 2, “Business scenario solution design” on page 51 Part 3, “Business scenario solution implementation” on page 143 Part I is comprised of Chapters 1 and 2. These chapters describe the objectives of this redbook project, what this book covers, and what this redbook does not cover. It includes an overview of how the book is organized and an introduction to the concepts and terminology used in this publication. It contains general descriptions of the technologies related to the sample business scenario solution built in the later chapters and a more detailed discussion on IBM WebSphere Business Integration products and the SAP NetWeaver technology platform. Part 2 consists of Chapters 3 through 5. Part 2 introduces a sample business case scenario with individual Use Case specifications. It provides an analysis of the integration requirements and a review of various technology options. The last chapter of this part designs a solution to illustrate the integration of SAP back-end systems into a WebSphere Business Integration infrastructure. Part 3 is composed of Chapters 6 to 11. The third part contains system installation and configuration descriptions. Detailed nuts-and-bolts implementations of the solution designed in the early chapters are explained, divided by Use Case to show all the modules of the various adapters that are capable of integrating SAP back-end systems. The last

Chapter 1. Introduction and book structure

5

chapter includes best practices and lesson learned about the implementation as well as future trends.

1.3.2 Chapter structure
The following is an overview of all the chapters in this redbook. Chapter 1, “Introduction and book structure” on page 3: This chapter describes the objectives of this redbook project and includes a high-level overview of what this redbook is about. Chapter 2, “Business Integration technology concepts” on page 9: This chapter explores the integration technologies offered by IBM and SAP. The interoperability of WebSphere Business Integration and the SAP system is addressed. Chapter 3, “Business case scenario” on page 53: This chapter introduces a sample business case scenario and defines four Use Cases as business requirements. Constraints and assumptions are also included for IT implementation. Chapter 4, “Solution approaches and technology options” on page 73: This chapter analyzes the business case scenario and identifies the appropriate integration styles to be used. Various integration technology options are reviewed, with detailed product mappings. Chapter 5, “Solution design” on page 109: This chapter defines a solution to the business case scenario from architecture, process flow, messaging interactions, and operation model perspectives. Appropriate broker and adapter technologies are rationalized. Chapter 6, “Environment setup” on page 145: This chapter specifies the run-time environment for the business case scenario. It contains an environment overview, hardware specifications, technology matrix, and common software installation. Chapter 7, “Use Case 1: WBIMB using WBI Adapter for mySAP.com” on page 173: This chapter shows how to implement the solution designed for Use Case 1 with WebSphere Business Integration Message Broker using WebSphere Business Integration Adapter for mySAP.com. Chapter 8, “Use Case 2: WBISF using WBI Adapter for mySAP.com” on page 327: This chapter shows how to implement the solution designed for Use Case 2 with WebSphere Business Integration Server Foundation using WebSphere Business Integration Adapter for mySAP.com.

6

WebSphere Business Integration for SAP

Chapter 9, “Use Case 3: WICS using WBI Adapter for mySAP.com and JDBC” on page 465: This chapter shows how to implement the solution designed for Use Case 3, WebSphere InterChange Server using WebSphere Business Integration Adapter for mySAP.com and Java Database Connectivity. Chapter 10, “Use Case 4: Integration of SAP XI with WBI InterChange Server” on page 555: This chapter shows how to implement the solution designed for Use Case 4 with Integration of SAP XI and WebSphere Business Integration InterChange Server. Chapter 11, “Best practices and lessons learned” on page 643: This chapter contains the general hints and tips obtained in the design and implementation of the sample business application as well as discussions on the trends and related emerging technology.

1.4 What this book does not cover
This book does not attempt to make a business case for business integration, nor does it categorize integration landscape or define integration patterns. There are many publications on these subjects that can be used as reference. Instead, the primary features of the WebSphere Business Integration product suite is reviewed, and where and when WebSphere Business Integration can be used to incorporate SAP back-end systems is illustrated. All features offered in WebSphere Business Integration product family are not demonstrated in this book, due to the resource and time constraints. Business integration scenarios that utilize WebSphere MQ Workflow are not included in this book. Enterprise features like clustering, scalability, fail-over, and performance are not discussed. The integration standards that are irrelevant to the integration styles covered are not discussed in this publication. Finally, the relevant product documentation must be consulted, if additional information is required for a particular product or tool.

Chapter 1. Introduction and book structure

7

8

WebSphere Business Integration for SAP

All rights reserved. It also addresses the integration of SAP back-end systems to an IBM WebSphere Business Integration infrastructure. © Copyright IBM Corp. 9 . It describes the IBM Business Integration Reference Architecture and the SAP NetWeaver technology stack. 2004.2 Chapter 2. Business Integration technology concepts This chapter gives an introduction to business integration capabilities provided by the IBM WebSphere Business Integration (WBI) product family and explores the integration technologies offered by IBM and SAP.

one-stop-shopping for enterprise applications is usually neither possible nor practical to IT organizations. 2. models. They execute business functions. regardless of how many internal systems the business function cuts across. such as vendors. a customer may call to change his or her mailing address and see whether the last payment was received. concepts. business partners. suppliers. verify the customer’s good standing. Business requirements arise permanently and affect the evolution the fulfillment of a system landscape. check inventory. fulfill the order.1. styles. get a shipping quote. such as traditional legacy systems. The business needs to validate the customer ID. It is not uncommon that an enterprise has dozens of technology islands. Users. Similarly. send a bill. Even simple business requirements can lead to fairly complex and challenging requirements for the affected systems. compute sales tax. With the complex and ever-changing business requirements. and so on. At present. there is no ERP solution in the market that is virtually capable of completely covering an enterprise at the requested level of detail. The driver of this heterogeneous development is the business itself. The fact that any enterprise consists of multiple business areas justifies the rich integration capabilities of appointed business applications that are naturally on demand. these systems are implemented by different technologies and execute on disparate operating system platforms. Every vendor is typically specialized in a specific business area. and countless custom-built departmental solutions. Currently. multiple instances of Enterprise Resource Planning (ERP) systems from different vendors. This processes may easily span 10 WebSphere Business Integration for SAP . In many enterprises. and terminologies used in common business integration scenarios. Naturally. For example.1 Business Integration needs A typical enterprise consists of a heterogeneous system landscape that is historically grown.1 Technology overview This paragraph describes the general technology. This was the rationale in the past and can be the reason for future IT transformations. generally do not think about system boundaries when they interact with a business.2. Enterprises take the opportunity to apply such best-of-breed applications to solve particular business requirements. there are various business application vendors in the market that provide standard solutions in certain business segments. This causes the existence of system landscapes composed of best-of-breed business applications. or even employees. this simple request may span across the customer care and billing systems. a customer placing a new order can require the coordination of many systems.

packaged business applications has become more and more important. 2. the groups that control specific applications have to provide well defined interfaces and methodologies to participate in the overall meshwork of integrated applications and services. A failing or misbehaving integration solution can cost a business a lot of money in lost orders.1. Business applications generally focus on a specific functional area. Business Integration technology concepts 11 . Platform independency and system neutral connectivity and communication paradigms support the successful implementation of such a business integration solution. misrouted payments. single business transaction. From the customer’s perspective. Additionally. Successful enterprise integration needs to establish integration links between these different business units and IT departments. Integration efforts usually have far-reaching implications on the business because of their wide scope. and so on. The business integration solution of choice has to feature special enterprise characteristics in the areas of reliability. scalability. In most situations. and security to deliver a certain quality of service. it is only a fairly simple. However. this technical infrastructure presents only a small portion of the integration complexities. Standard business application software vendors offer integration suites that provide cross-platform integration. Once the processing of the most critical business functions is incorporated into an integration solution. the ability to interface with many other popular. The integration solution has to provide these flexible abstraction layers to bring all participating back ends to a common denominator. As a result. One important constraint of developing integration solutions is the limited amount of control the integration designers typically have over the participating applications. The collaboration between integration designer and application owner is vital for the development of an efficient integration solution. In an integrated enterprise application landscape. Finance. These applications must be integrated in order to support common business processes. Enterprise integration requires a significant shift in IT alignments. such as Customer Relationship Management (CRM). Chapter 2. the applications are legacy systems or packaged applications that cannot be changed just to be connected to an integration solution. The true challenges of integration span far across business and technical issues.2 Integration challenges By definition. many IT groups are organized in alignment with these functional areas. the proper functioning of that solution becomes vital to the business. Billing.across multiple different systems. and dissatisfied customers. enterprise integration deals with multiple applications running on diverse platforms which are distributed.

which is the foundation for further integration efforts. These mechanisms can be categorized by specific characteristics. they can be generally categorized into the following styles: Application Connectivity Process Integration 12 WebSphere Business Integration for SAP . only a few standards have established themselves in this domain. 2. monitoring and change management. The advent of eXtensible Markup Language (XML) is a core building block of system integration solutions. The mix of technologies and the distributed nature of integration solutions make deployment. these skill sets are hard to find within IT organizations or are spread across many different individuals.1. This produces a guarantee that different interests and needs are balanced out and the resulting standards are pillared and promoted by all participants. Despite the widespread need for integration solutions. Resolving semantic differences between systems proves to be a particularly difficult and time-consuming task because it involves significant business and technical decisions. Systems have to understand each other or. XML participating systems use a mutual character set for communication. The past has shown that such a semantic consonance cannot be driven by a single company but must be supported and driven by multiple partners that align to a consortium or a foundation.The usage of common accepted standards is the most promising method of resolution. and assumptions in each participating system. The notion of account can have many different semantics. rather.3 Concepts and terminologies Here we discuss concepts and terminologies. such as synchronous or asynchronous communication style or message oriented integration. operation. operating and maintaining these solutions can be even more daunting. connotations. RosettaNet is a good example for such a consortium. as it defines a common e-business language. aligning processes between supply-chain partners on a global basis. constraints. Beside a common syntax and semantics. the integration solution has to provide a common semantic environment. Beyond having a common syntactical basis. the integration solution must be the mediator between systems. In most cases. Integration styles Although there are significantly different approaches to system integration. business integration solutions have to rely on unified access mechanisms that are common across different systems and platforms. complex tasks that require a rich combination of skill sets. Despite the fact that developing integration solutions is challenging in itself.

Integration terminology There are many terms used in the integration area. Table 2-1 Integration styles Integration term Application Connectivity Process Integration Purpose Communication between two or more applications. The action may return a result or not. Supports setups like hub and spoke. A comprehensive view of systems through a suitable user interface. one to many. Participating parties connect to a central system. Other applications invoke these functions with or without parameterization. Business Integration technology concepts 13 . and exchange data via defined messages.User Interactivity The purpose and mechanism of these styles are illustrated in the following table. Object Request Brokers (ORB) provide a run-time environment for business objects and manage their lifecycle and the access to these objects in a consistent manner. Message oriented middleware Distributed computing model Chapter 2. Share and exchange business information in a consistent manner. These terms and features are listed in the following table. Table 2-2 Integration terminology Integration model File transfer Shared database Remote Procedure Call Definition Applications create files of shared data for others to consume. Coordinate business activities that execute across system boundaries. An application exposes a certain functionality and makes it accessible remotely. Automate and improve business processes. Applications store the data to share in a common database. Compose new processes by incorporating existing business applications. and publish/subscribe. User Interactivity This book primarily focuses on application connectivity and process integration styles. and consume files that others have produced. Deliver relevant business information to respective users. Involve human interactions into process flows.

com/software/integration/wbiadapters/ 14 WebSphere Business Integration for SAP . The prerequisite is that the relevant components expose their business functionality in a common service based notation and that they support a mutual invocation methodology. and improve processes and performance The WebSphere Business Integration product suite implements a hub and spoke approach. or WebSphere Business Integration Message Broker. Adapters ease up connectivity by providing a standardized transition between the broker and the participating system. where the hub is the WebSphere Business Integration Server.Integration model Transactional characteristic Definition Provides an enhanced access mechanism to business entities. Several manipulations can be applied to the business information. from bottom-up application connectivity to top-down business process automation.1.4 IBM WebSphere Business Integration product family IBM WebSphere Business Integration products cover the whole spectrum of business integration. like Java Database Connectivity (JDBC). like SAP. including defined compensation procedures in case of failure. The core of a broker based integration scenario. Integration server Adapter Service choreography 2. processes. and data Connect: Extend processes to your customers and partners Monitor: Control and track business processes Manage: Review. and data enrichment. applications. simulate. This term describes the composition of new business processes by incorporating existing business logic. The spokes are the adapters that connect to applications. analyze. and plan business processes Integrate: Link people. transformation. WebSphere Business Integration Event Broker. systems. such as routing. It connects various components together in a bus or star topology. The IBM WebSphere Business Integration product family provides the following capabilities: Model: Design. A component that acts as mediator between the integration server and a respective integration partner. or to technologies. WebSphere Business Integration Server Foundation.ibm. The execution of business logic is strictly controlled. You can find a list of all available WebSphere Business Integration Adapters at: http://www. The assessor receives detailed feedback on how the transaction proceeded. Adapters can offer a great reuse potential if multiple equal back ends are linked together.

allowing customers to use foundation technologies to compose higher-order composite applications. Business rule beans to embed adaptable business logic into your applications and business processes. and business processes. Table 2-3 IBM WebSphere Business Integration product family Product WBI Server Capability Integrate Model Features WebSphere Business Integration Server provides process services via the WebSphere MQ Workflow and WebSphere Interchange solutions. Web services. accelerates application development. such as pre-built collaborations.The key features of the primary products in the WebSphere Business Integration family are summarized in the following table. Chapter 2. Application adapters for building Web applications and BPEL4WS business processes that integrate with back-end systems. The WebSphere Business Integration Server components can also be surfaced via Web Services Description Language (WSDL). Programming model extensions to accelerate large-scale application development by allowing you to leverage the latest innovations that build on today's J2EE standards. Human Workflow support includes activities that require human interaction as steps in an automated business process. offering an advanced set of integration solutions in conjunction with accelerator technology. The WebSphere Business Integration Server includes: WebSphere InterChange Server WebSphere MQ Workflow WBI Server Foundation Integrate Connect Manage WebSphere Business Integration Server Foundation is the next-generation application server that simplifies build-to-integrate tasks. testing. Business Integration technology concepts 15 . integrating and deploying J2EE applications. J2EE Application Server for deploying enterprise Web services solutions for dynamic e-business on demand™. and enables dynamic application flexibility. Integrated J2EE development environment for building.

Enables the secure and seamless interaction of enterprise applications with numerous users within the intranet and across the Internet. or a packaged legacy system and the underlying transport infrastructure. 16 WebSphere Business Integration for SAP .Product WBI Message Broker Capability Integrate Features Extends the messaging capabilities of WebSphere MQ by adding message routing. Can be considered the spokes that connect applications and technologies to the integration broker hubs. WBI Event Broker Integrate Allows high-performance content and topic-based publish and subscribe message routing between a variety of protocols. and route data through all IBM integration brokers. mainframe. Provides a run-time environment that executes message-flows. and e-business connections for both process integration and application connectivity requirements. technology. Extends business integration to the mobile. wireless. transformation. Includes the WebSphere Business Integration Event Broker. Access. transform. Uses multicast to optimize network utilization when broadcasting information. These message-flows consist of a graph of nodes that represent the processing needed for integrating applications. and publish/subscribe features. WBI Adapter Integrate Enables data to move between an application. such as real-time market data. They provide application. a technology. and telemetry environments from the smallest sensor to the latest PDA.

WBI Connect Connect Full-function. application connectivity and business process modeling. Component-based solution providing robustness and performance. Offers comprehensive security options using Secure Sockets Layer (SSL). and formats. Business Integration technology concepts 17 . enterprise-strength gateway/hub built on a WebSphere Application Server foundation. and helps make programs portable. and Merger/Acquisition. Ensures data delivery that is free from errors and safe from unauthorized access. Simplifies development of Application Programming Interface (API) exits to allow monitoring and implementation of local standards. integrating existing business applications in the process. Division to Division (D2D). the Internet standard for secure communication. Enables integration beyond the enterprise into the extended value chain. WBI Toolset Manage A set of easy-to-use tools that provides customers with administrative and development support for system management.Product WebSphere MQ Capability Integrate Features Facilitates easy exchange of information across different platforms. Business-to-Business (B2B) framework for B2B. Delivers enhanced performance with integrated Java Message Service (JMS). Includes administration tools and design tools. dynamic distribution of workload across available resources. protocols. Support for standards-based transports. Ensures reliable delivery of messages. Chapter 2. making it the JMS provider of choice. Provides high scalability for large trading communities.

display. Provides advanced data validation and standards compliance functions. a dedicated GUI mapping tool that is optimized to build EDI. Business and technical users can utilize the tailored alert system to define. and receive instant alerts on operational results. Provides WebSphere Data Interchange Client. to illustrate how business processes are achieving corporate goals. such as invoices. statistics. validation. and industry-standard or user-defined XML DTDs for mapping and translation. Gives you the ability to stop. Offers a Web application so you can manage your processes from an Internet connection anywhere in the world. and batched information exchange capabilities for Electronic Data Interchange (EDI) standards. or through IBM WebSphere Portal. and gives you the option of deploying on a range of platforms. purchase orders. allowing functional acknowledgements to be generated in response to inconsistencies in data content. and billing forms for exchange with trading partners. to check the pulse of company performance. Provides configuration and administration capabilities that allow the definition of the construction and deconstruction of envelopes. 18 WebSphere Business Integration for SAP . including mainframe-class servers running the secure. application data structures. XML. Delivers ongoing business process improvement by constantly sending real-time data back into process modeling tools. stable z/OS operating system. Allows direct import of EDI standards definitions.Product WebSphere Data Interchange Capability Connect Features Provides advanced translation. WBI Monitor (formerly Holosofx®) Monitor Manage Offers a minute-by-minute view of work items. while they are underway. Tracks your business processes and displays important metrics in a convenient enterprise dashboard. adjust. and redirect details of workflow processes. not estimated. Electronically translates EDI format data. including workload balancing. including the status and workload of each job and user-level. Views business results in real time and analyzes business processes based on real. and application data format transformations.

2. enterprise wide strategies and solutions. Reduce risk and save time and money by using pre-built.2. new integration functions can be easily added. WebSphere Business Integration Workbench: Test. This chapter describes the IBM Business Integration Reference Architecture on different levels: Overview about IBM Business Integration Reference Architecture Comprehensive Services of IBM Business Integration Reference Architecture Roles and Artifacts in the IBM Business Integration Reference Architecture IBM Software Offerings in the IBM Business Integration Reference Architecture It also refers to the Service Oriented Architecture (SOA) and e-business on demand and discusses how these are related to IBM Business Integration.Product WBI Modeler Capability Model Manage Features Models and simulates business processes graphically. As each additional project is addressed. The architecture also supports Service Oriented Architecture strategies and Chapter 2. WebSphere Business Integration Workbench server: A Java 2 Enterprise Edition (J2EE) compliant application that can be deployed on WebSphere Application Server on a variety of platforms. WBI Collaborations Integrate Connect Prebuilt. incrementally enhancing the scope of integration across the enterprise. and validate business processes and software models. customizable business-process templates that deliver most of the necessary code for a wide variety of business processes running on the WebSphere Business Integration Server.2 IBM Business Integration Reference Architecture The IBM Business Integration Reference Architecture (BIRA) shows the key areas of integration capability that are required for comprehensive. Business Integration technology concepts 19 .1 Overview The IBM Business Integration Reference Architecture is a complete and comprehensive architecture that covers all the integration needs of an enterprise. analyze. allowing integration implementations to start at a small project level. simulate. It provides repository management and Web publishing capabilities in a centralized data warehouse. Its services are well integrated and are delivered in a modular way. 2. proven products rather than building custom code.

their expertise. 20 WebSphere Business Integration for SAP . given that the middleware architecture itself is designed using principles of service orientation and function isolation. Yet. while it is important for each person to have a specific set of tool functions based on their role in the enterprise. functional flows. and their role within the enterprise. system interactions. Software Architects need tool perspectives that allow them to model data. Integration Specialists require capabilities that allow them to configure specific inter-connections in the integration solution. version control functions or project management functions) are provided in the Business Integration Reference Architecture through a unified development platform. Programmers need tools that allow them to develop new business logic with little concern for the underlying platform. Business Analysts who analyze business process requirements need modeling tools that allow business processes to be charted and simulated. Figure 2-1 gives an overview of IBM Business Integration Reference Architecture. the tooling environment must provide a framework that promotes joint development.Overview Development Platform Development tools allow people to efficiently complete specific tasks and create specific output based on their skills. and so on. asset management. and deep collaboration among all these people. Development Platform Business Performance Management Services Interaction Services Process Services Information Services Enterprise Service Bus Partner Services Business Application Services Application and Data Access Services Business Application and Data Services Enterprise Applications and Data Infrastructure Services Figure 2-1 BI Reference Architecture .solutions. A common repository and functions common across all the developer perspectives (for example.

This allows users to buy products. Managing these systems requires a set of capabilities that span the needs of IT operations professionals and business analysts who manage the business operations of the enterprise. PDAs. what business process paths may not be performing at maximum efficiency. mobile phones. Collaborative services (also known as communication services) allow people to chat. enroll for classes. and data mining capabilities.Business Performance Management Software Business performance management tools incorporate monitoring capabilities that aggregate operational and process metrics in order to efficiently manage systems and processes. These capabilities are delivered through a set of comprehensive services that collect and present both IT and process-level data. administrative dashboards. Interaction Services User Interaction Services provide the capabilities required to deliver IT functions and data to end users. use white boards. Chapter 2. Information accessed can include syndicated content supplied specifically for the purpose of reuse and integration with other material. voice and so on. for example. it is possible for Line Of Business (LOB) and IT personnel to collaborate and determine. One key feature of the IBM Business Integration Reference Architecture is the linkage between the Development Platform and the Business Performance Management Services. tracking. A portal can be accessed through various channels like Web browsers. or the relationship of system performance to business process performance. allowing business dashboards. Through these displays and services. share calendars. and so on. The ability to deliver run-time data and statistics into the development environment allows analyses to be completed that drive iterative process re-engineering through a continuous business process improvement cycle. meeting the end-user's specific usage preferences. such as a customer representative or salesperson. locate expertise. schedule meetings. All channels share common characteristics. User interaction is handled by a multi-channel access service. This collaboration allows IT personnel and assets to be tied more directly to the business success of the enterprise than they traditionally have been. Self-service (also known as transactional services) enable users to interact with systems directly without going through an intermediary. the impact of system problems on specific processes. Business Integration technology concepts 21 . such as the following: Aggregating geographically distributed structured and unstructured information and services into one place. Content management services provide search. participate in discussion groups. and so on. and other IT level displays to be used to manage system resources and business processes. check account balances.

directory. Partner Services provide the document. replication. One of the ways it does this is through personalization and customization. Process Services Process Services provide the control services required to manage the flow and interactions of multiple services in ways that implement business processes. Business Application Services The IBM Business Integration Reference Architecture also contains a set of Business Application Services that provide run-time services required for new application components. allowing them to participate in new and updated business processes over time. IT 22 WebSphere Business Integration for SAP . replicate. and monitoring of processes across people and heterogeneous systems. business processes involve interactions with outside partners and suppliers. both inside and outside the enterprise. flexible. A business can change how it operates through modeling. The Business Application Services include functions important to the traditional programmer for building maintainable. The process service allows the integration of a complete process end-to-end. and re-usable business logic components. Information Services Diverse forms of business information can be integrated across the enterprise. and analysis over a unified view of information assets to meet business needs.Supporting personalization for a group or an individual. and partner management services required for efficient implementation of Business-to-Business processes and interactions. Business Application Services provide new business logic required to adapt existing business processes to meet changing competitive and customer demands of the enterprise. Infrastructure Services Underlying all these capabilities of the IBM Business Integration Reference Architecture is a set of Infrastructure Services that provide security. automation. access. protocol. Partner Services In many enterprise scenarios. Integrating the systems of the partners and suppliers with those of the enterprise improves efficiency of the overall value chain. One of the more interesting aspects of the interaction service is its ability to be different things to different people. and transform data sources that may be implemented in a variety of ways. Design and implementation of new business logic components for integration enables them to be fully re-usable. transformation. Integration enables coherent search. Information Services provide the capabilities required to federate.

The ability to leverage grids and grid computing are also included in infrastructure services. WebSphere Business Integration Adapters span a wide range of applications and technologies. for example. for a database adapter. This is the part of the adapter that has explicit internal coding and knowledge of how to interact with the application or technology. edge services and clustering services. directory.system management. for example. Enterprise Service Bus ESB provides a standards-based means of application to application communication like Web Services. the application-facing part has database API calls to access the database. and IT operational systems management. For example. WebSphere Business Integration Adapters are run-time components integrated with the business integration system. The usage of prebuilt adapters provides rapid deployment and reduces risk. Business Integration technology concepts 23 . All the adapters are two-faced animals. the virtualization capabilities allow efficient use of computing resources based on load patterns. message transport. The adapter's application specific components are different for each different type of adapter. For an SAP adapter. Adapters are built to present a common client interface to each EIS in a common development tooling. They include: Security service Directory service IT system management service Virtualization service The security and directory services include functions involving authentication and authorizations required for implementing. These interactions typically involve services related to security. Application and Data Access Services Wraps the native Application Programmable Interface (API) of Enterprise Information Systems (EIS) like SAP. The first part of the adapter is its application-facing component. While many infrastructure services perform functions tied directly to hardware or system implementations. single sign-on capabilities across a distributed and heterogeneous system. and mediation. and so on. it contains Business Application Programming Interface (BAPI) calls to access the SAP system. IT system management and virtualization services include functions that relate to scale and performance. and virtualization functions. Chapter 2. others provide functions that interact directly with integration services provided in other elements of the architecture through the Enterprise Service Bus (ESB). IBM has implemented the code to be able to access the applications or technologies. Infrastructure services are underlying and supporting services for the IBM Business Integration Reference Architecture.

the architecture must support a set of services that can be used to implement integration points where and how they are needed. processes. they form the basis upon which people.2. Business Application and Data Services Business Application and Data Services are applications in the existing IT landscape. The architecture defines not just the functional services. Business Applications and Data Services can be integrated with the Enterprise Service Bus using Application and Data Access Services like adapters. The data content that is sent to and from the broker is the IBM Business Object. This has the responsibility for interacting with the broker by forming communication links to send and receive the adapter’s data. The Business Integration Reference Architecture provides a comprehensive set of services to enable Business Integration (see Figure 2-2 on page 25). and data can be integrated. for example. 24 WebSphere Business Integration for SAP . It has the built-in capability to transform the application-originated or destined data to and from a common data representation for transmission to the broker. The services fit into a tiered architecture that clearly define the broad set of services required for a complete integration solution. This component is identical in all adapters.The second part of the adapter is the broker facing component. but the operational ones as well.2 Comprehensive Services For effective business integration. The services represent concerns that should be separated and elaborated as part of the implementation architecture. legacy systems. 2. Collectively.

Design: Allows models to be staged into design using traditional IT tools.Comprehensive Services Model Design Development Platform Implement Test Process Monitoring Interaction Services Delivery Experience Resource Business Performance Management Services Process Services Choreography Transactions Staff Enterprise Service Bus IT Monitoring Information Services Federation Replication Transformation Event Partner Services Business App Services Transport Mediation Application and Data Access Services Event Detect On-Ramp Community Document Protocol Component Interface Core Enterprise Applications and Data Infrastructure Services Business Application and Data Services Figure 2-2 WBI Reference Architecture . Chapter 2. Business Integration technology concepts 25 . Implement: Enables the ability to move developed artifacts into production as part of an organization’s configuration management architecture/standards. Test: Provides the ability to support both unit test as well as integrated test capabilities as part of the basic development tooling. which provide the ability to attribute and extend the models with core IT assets and to develop business processes as well as integration components.Comprehensive Services Development Platform This layer of services comprise the software development platform and support iterative software development. Model: Provides the ability for analysts to work in conjunction with IT to build models that are representative of business processes.

security and entitlements. Resource: Provides run-time management of the portlet components supporting. Process Monitoring: Enables support for traditional Business Activity Monitoring (BAM) by allowing users to have dashboard views into key performance indicators tied to their deployed integration assets/components. Process Services This layer of services provide the ability to aggregate integration components to support coarse grained business functions. Interaction Services This layer of service provides the external interaction services for user and device integration. IT Monitoring: Provides direct visibility into operational run-time behavior as part of the underlying event detection and tooling to allow this information to be integrated with process oriented views as appropriate for the target user. and facilities to manage workflow related endpoints through integration with interaction services. Choreography: Provides the ability to orchestrate integration components into processes that in turn can be used to build other composite processes. and internationalization. delegation. for example. Staff: Allows the ability to integrate people-oriented task management into processes with support for task assignment. such as multi-device support. Experience: Provides the various user-centric services that are responsible for the delivery of a robust user experience.Business Performance Management Services This layer of services comprise the framework for providing visibility into the key metrics associated with run-time management of integration components. including personalization and collaboration. 26 WebSphere Business Integration for SAP . language translation. page aggregation. markup transcoding. Transactions: Enables the ability to support both ACID transactional activities as well as compensatory processing as part of the process framework. Delivery: Enables the interaction framework for different users to interact with the integration framework via portlets and pervasive messaging and includes specialized technologies.

Business Integration technology concepts 27 . Federation: Enables the ability to aggregate data from traditional (for example. Transformation: Enables the translation of data information to support data cleansing and metadata interchange through leveraging SQL and XML standards. Replication: Provides support for automated real-time data synchronization. and service binding resolution services during transport. as well as state management for public process conversations. Protocol: Provides transport level services. business events. text data. such as XML data stores. including authentication. and other edge services for automated document interchange.Information Services This layer of services provide data integration and aggregation over heterogeneous data sources. Mediation: Enables message transformation. such as RosettaNet and AS1/AS2. Document: Enables the support for business protocols. and content stores. Event: Provides event driven services through messaging services to enable the components (and constituent stakeholders) to be responsive to external stimuli. enabling locality of access for data access regardless of source implementation. Enterprise Services Bus Provides inter-connectivity services within the enterprise and across multiple locations or even multiple companies. Transport: Provides communication services for synchronous and asynchronous delivery with varying levels of delivery assurance. for example. Chapter 2. dynamic routing. Relational Database Management System (RDBMS)) and non-traditional sources. document routing. Partner Services This layer of services provides support for traditional Business-to-Business (B2B) partner integration solutions Community: Allows for the management of the trading community for both the hub manager as well as providing partner self-management functions.

messaging systems. a few common requirements are listed below: Regardless of the role. XML. Interface: Provides services for robust bidirectional integration with databases. By applying a clean separation of concerns through the development process. event notification. including one way inbound. relationship navigation.2. object query. 2. management frameworks (for example. Core: Provides run-time services. messaging systems. Component: Provides a run-time environment or container that automatically handles issues such as object persistence. a high degree of collaboration is required across roles.Business Application Services This layer of services provides the framework and operating environment for the run-time management of custom application components. Applications and Data Access Services This layer of services provides for the access and operational interface to existing application and data with support for transactional services and connection services for databases. request-reply. Event Detect: Provides notification services based on the event framework that is supported by the specific application/data source. JMX/CEI). Each role requires specialized tools to accomplish its tasks. and other enterprise applications. and the Messaging and Web Services programming model. 28 WebSphere Business Integration for SAP . which must be part of the general programming model through Java 2 Platform. and transaction management. directory and security. and other data sources. each developer can deploy their artifacts into the architecture based on their role (see Figure 2-3 on page 29). Looking at the various roles.3 Roles and sample artifacts The IBM software development platform provides an integrated and complete set of tools that address the integration problem and address role-based development. Enterprise Edition (J2EE). such as memory management. object instantiation and pooling. and solicit reply patterns to support application and data integration. On-Ramp: Enables application/data integration patterns.

Roles and Sample Artifacts
Business Analyst Architect Integration Specialist Developer Tester

Development Platform

Business Performance Management Services
Interaction Services

Dashboards

Process Services Business Processes

Information Services

Portlets

Data Models

Mediations

Enterprise Service Bus

Business Object Definitions

Partner Services

Business App Services App Components

Application and Data Access Services Adapters Business Application and Data Services

Partner Profiles

Enterprise Applications and Data Infrastructure Services

Figure 2-3 WBI Reference Architecture - Artifacts

Roles
A Business Analyst: – Captures business requirements. – Models and analyzes business processes. – The Business Analyst typically produces Requirements Documents, Use Cases, and Business Process Models. An Architect: – Models applications and data. – Models activities. – An Architect produces Object Models, Data Models, Class Diagrams, Sequence Diagrams, and Activity Diagrams.

Chapter 2. Business Integration technology concepts

29

An Integration Specialist: – Acts as the key specialist across integration technologies. – Configures the integration environment, for example, Messaging infrastructure, and Component configuration, for example, processes, collaborations, and adapters. – Interfaces to other specialists, for example, operations, and RDBMS. – An Integration Specialist produces Message Flows, Process Flows/Collaborations, Connection Configurations, and Adapters. A Developer: – Develops the application from the requirements and models defined by the Business Analyst and Architect. – Many types of developers with specific roles are very common. A development team might have J2EE developers, Business Process Developers, Web Developers, and Portlet developers on their development team. – A Developer produces the application components (in many organizations, developers may be specialized to the development of specific types of artifacts, for example, portlets, stored procedures, J2EE components, adapters, and so on.) A Tester: – Develops test cases for the applications and business processes built by the Architects, Developers, and Integration Specialists. – Tests the application/component to ensure the quality of the application. – A tester produces test cases, runs tests, documents test results, and provides communication for quality control aspects of the software development process.

Sample artifacts
Different run-time artifacts are produced during the development of applications, services, and business processes. These artifacts deploy into various components of the integration architecture. The following are representative of the types of artifacts created and are not meant to describe each in detail.

Business Performance Management Services
Dashboards: Business performance monitoring interfaces to support key constituencies and stakeholders.

30

WebSphere Business Integration for SAP

Interaction Services
Portlets: User interaction artifacts that support user interactions with the underlying integration and enterprise collaboration services.

Process Services
Business Processes: Artifacts describing choreographed aggregation of service endpoints to support composite application processes.

Information Services
Data Models: Data representations/schema artifacts to support federated and replicated data capabilities.

Enterprise Service Bus
Mediations: Routing and transformation artifacts to support enterprise service bus message/service flow attributes. Business Object Definitions: Artifacts that describe common reusable business object definitions.

Partner Services
Partner Profiles: Configuration objects describing business partner interactions including transport, security, and entitlements.

Business Application Services
Application Components: Artifacts produced during application development including J2EE/Java 2 Platform Standard Edition (J2SE) components.

Application and Data Access Services
Adapters: Artifacts providing application access integration, including connection management, transactional support, application-specific metadata, and application specific objects.

2.2.4 IBM software offerings
The IBM Business Integration portfolio has the greatest functional breadth of any middleware vendor. This allows IBM to offer a single vendor solution to customers and providing “best-of-breed” components for integration solutions (see Figure 2-4 on page 32).

Chapter 2. Business Integration technology concepts

31

IBM Software Offerings
WebSphere BI Modeler Development Platform WebSphere Studio

Business Performance Management Services WBI Monitor Interaction Services WebSphere Portal Server Process Services WebSphere BI Server WebSphere BI Server Foundation Information Services DB2 Information Integrator

WebSphere MQ Partner Services WebSphere BI Connect

Enterprise Service Bus Web Services Gateway Business App Services WebSphere Application Server

WBI Event/Message Broker

Application and Data Access Services WBI Adapters HATS DB2 II Classic

Business Application and Data Services

Enterprise Applications and Dataand Data Enterprise Applications

Infrastructure Services

Figure 2-4 WBI Reference Architecture - Software offerings

Development platform
The IBM software development solution is the part of the IBM on demand operating environment that address your design and build needs. This part of the on demand operating environment is referred to as the IBM Software Development Platform. This platform is open, extensible (based on the Eclipse framework), and supportive of your strategic technology direction. This solution spans UNIX®, Windows, IBM ^, and real-time operating systems. And it works hand-in-hand with software execution platforms from Microsoft®, Sun, Borland, and other vendors, which gives you the broadest choice of development options. The Eclipse framework provides an industry standards tool framework. IBM contributed software/R&D as initial Eclipse technology and the Eclipse foundation is now supported by a group of Consortium Members. The support for Eclipse is huge; Download requests topped 3.1 million in first year (with over 18 million to date), consisting of over approximately 880 K developers, companies, or organizations from over 125 countries. More importantly, vendors are committing to Eclipse. Over 175 vendors use Eclipse as their standard solution framework, including significant commitments from TogetherSoft, Serena, QNX, and Merant with hundreds of open source or freeware plug-in projects available.

32

WebSphere Business Integration for SAP

WebSphere Business Integration Modeler
WebSphere Business Integration Modeler helps anyone in the organization, whether it be a business analyst or IT specialist, to capture a business process and clearly define and document the process. Both the current (as-is) and the future (to-be) process can be modeled and compared using the simulation and analysis capabilities of WebSphere Business Integration Modeler. Comparing these processes identifies Return On Investment (ROI) opportunities in the business by changing the process as modeled.

WebSphere Studio
The WebSphere Studio family provides an open extensible Universal Tooling Platform that enables tool integration between vendors as well as providing an extensive set of best-of-breed integrated tools and utilities for application development. In WebSphere Studio Application Developer (WSAD) Integration Edition Version 5.1, business processes can be defined in a new industrial standard called Business Process Execution Language for Web Services (BPEL4WS). Since the BPEL4WS standard does not cover all the functionality needed for process integration, IBM introduced a functional enhancement to BPEL4WS called BPEL4WS Extensions that makes use of designated enhancement points in the BPEL4WS standard. One area of enhancements is the support for person activities (Staff) that are defined as enhanced invoke activities.

Business Performance Management Services
Here we discuss Business Performance Management Services.

WebSphere Business Integration Monitor
The WebSphere Business Integration Monitor solution provides dashboard and alert notification services which interact with the integrated event-based monitoring using messaging services to provide heads-up display for Business Process Management (BPM). WebSphere Business Integration Monitor Version 5.1 provides direct interaction with the Common Event Infrastructure. Business Activity Monitoring enables the tracking of business events across the enterprise, and the value chain. This enables real-time metrics from processes in motion, alerts to provide notification on service levels, and exception conditions. Additionally, the dashboard components are enabled to integrate with additional portlets to provide customized views specific for the role. Lastly, the monitor allows operational capabilities, including stopping, starting, or redirecting processes and can be used in tandem with other IT Monitoring solutions, such as the Tivoli® Monitoring for Business Integration.

Chapter 2. Business Integration technology concepts

33

Interaction Services
Here we discuss Interaction Services.

WebSphere Portal Server
WebSphere Portal Server provides a best-in-class framework for developing and managing user interaction-based integration solutions. WebSphere Portal Server provides page aggregation, markup transcoding, language translation, multi-device support, and internationalization. Multi-device support and internationalization are the static versions of the Markup Transcoding and Language Translation services, respectively. These provide the facilities to easily support multiple languages and devices when portal resources are constructed. Additionally, although not explicitly called out, pervasive messaging is also provided through the WebSphere MQ Everyplace® and Enterprise Service Bus components technology to provide support for additional devices. WebSphere MQ Everyplace suite also provides functions and capabilities associated with the integration of multiple pervasive devices.

Process Services
Here we discuss Process Services.

WebSphere Business Integration Server
WebSphere Business Integration Server provides process services via the WebSphere MQ Workflow and WebSphere Interchange solutions, offering an advanced set of integration solutions in conjunction with accelerator technology, such as pre-built collaborations. The WebSphere Business Integration Server components can also be surfaced via Web Services Description Language (WSDL), allowing customers to use foundation technologies to compose higher-order composite applications.

WebSphere Business Integration Server Foundation
Provides long-duration activities and People-to-App/Staff Services via a native Business Process Execution Language (BPEL) solution. Additionally, the BPEL Process Choreographer solution provides for externalized business rules via the WebSphere Application Server based Business Rule Beans framework. The engine provides for compensating process services as part of overall process flow choreography.

34

WebSphere Business Integration for SAP

Information Services
Here we discuss Information Services.

DB2® Information Integrator
The DB2 Information Integrator provides direct support for data federation and replication over heterogeneous sources, both traditional relational sources as well as non-traditional sources, including text and XML data structures. Through standard interfaces, including SQL, XQuery, DB2 II, it provides full read/write access across diverse data and content sources.

Partner Services
Here we discuss Partner Services.

WebSphere Business Integration Connect
WebSphere Business Integration Connect Advanced/Enterprise provides document exchange services with a rich set of operational tools to manage the trading community. The solution architecture is built on the embedded version of WebSphere Application Server. Additionally, the product provides integrated event/alert management, which is the largest differentiator of the product offering. These tools enable both reactive problem determination via browser-based integration for both the hub and participants as well as an event-driven solution to automatically detect events and notify parties as needed.

Business Application Services
Here we discuss Business Application Services.

WebSphere Application Server
The WebSphere Application Server framework provides the market-leading application server, providing best-in-class support for J2EE, XML, Messaging, and Web Services programming models. It produces the integration of autonomic administration and management, JMX management interface, superior transaction performance, and integrated availability and scalability. Additionally, as mentioned above, the WebSphere Business Integration Server Foundation support for native Business Process Execution Language for Web Services (BPEL4WS) provides an integrated solution for developing service oriented architectures.

Enterprise Service Bus
The ESB architecture construct for end-to-end integration of distributed software applications and components is enabled through a set of messaging solution components, which are standards based, and enable the development of a network of distributed, standards-compliant and platform-neutral interconnection middleware. The ESB provides the connectivity infrastructure for a Service

Chapter 2. Business Integration technology concepts

35

Oriented Architecture. This places the ESB in context, as its reason for being is to support an open, standards based, and service oriented architecture.

Application and Data Access
Here we discuss Application and Data Access.

WebSphere Business IntegrationAdapters
The WebSphere Business Integration Adapters provide connectivity with one consistent framework-based approach and an application specific component, as illustrated in Figure 2-5. All adapters run on the same common framework, ensuring that they can be reused with different brokers as your integration needs change over time. The common framework also allows greater speed and ease of adapter deployment, requiring less skill to install a broad range of adapters.

Adapter Framework

Application Specific Component
Business Object Handlers Global Utility Functions Application Event Notification

Message Transport Driver

Event Message Interface

Java to C++ Translation

JMS

IIOP/ JMS

Figure 2-5 Adapter architecture

The Adapter can be logically divided into two sections: The Application Specific Component – Provides bidirectional connectivity directly to application API (for example, SAP JCo) or technology interface. – Handles the requirements of accessing the application; includes basic initialization and setup methods, business object handling, and event notification.

36

WebSphere Business Integration for SAP

Application

IIOP

Application Interface Functions

Generic Services

The Adapter Framework – Provides the common run-time infrastructure on which a specific adapter is implemented. – Assures uniformity in administration and behavior across the adapter family. – Provides services, such as bidirectional broker interaction, logging, and quality of service. – Handles the requirements of the Transport layer, such as sends and receives BOs, and converts BOs to XML to transport to broker. – Provides Generic Services: BO definition library, subscription manager, logging, and tracing.

Host Access Transformation Services
WebSphere Host Access Transformation Services, or HATS, is the newest addition to the WebSphere Host Integration Solution. HATS delivers improved ease of use of existing 3270 and 5250 applications by dynamically transforming the screens into more Web-like HTML pages for the end user.

DB2 II Classic Federation
DB2 II Classic Federation provides access to mainframe data sources such as IDMS and Adabas. The DB2 II Classic can be used in tandem with the DB2 II solution to provide federated access to mainframe data sources as part of an overall data integration architecture.

2.2.5 Service Oriented Architecture (SOA)
A Service Oriented Architecture is an approach for building distributed systems that deliver application functionality as service to either end-user applications or other services. A SOA defines an architecture that leverages open standards to represent software assets as services. IBM Business Integration supports the SOA today (supports service definition, interaction, and orchestration). SOA also provides the capability for achieving greater responsiveness. It permits a company to leverage a componentized approach to application functionality that allows composite applications and business processes to be created dynamically and literally in real time. Solutions based on an Service Oriented Architecture also deliver tremendous benefits: Lower development costs Less pain when integrating assets across heterogeneous environments Greater reuse of IT assets More effective security and manageability

Chapter 2. Business Integration technology concepts

37

SOA is a distributed software model. The key components of an SOA include: Services Dynamic discovery Messages A service is a callable routine that is made available over a network. It exposes an interface contract, which defines the behavior of the service and the messages it accepts and returns. The term service is often used interchangeably with the term provider, which specifically denotes the entity that provides the service. Interfaces are often published in public registries or directories where they are categorized based on different services offered, just as businesses and their phone numbers are listed in a phone book. Clients (service consumers) can look up a particular service by dynamically querying for services based on various categorization features. This process is referred to as the dynamic discovery of services. Service consumers or clients consume services via messages. Because interface contracts are platform- and language-independent, messages are typically constructed using XML formats that conform to XML schema.

2.2.6 e-business on demand
e-business on demand is defined as:

An enterprise whose business processes (integrated end-to-end across the company and with key partners, suppliers, and customers) can respond with speed to any customer demand, market opportunity, or external threat1.
The new on demand computing environment is an open standards-based, and heterogeneous world, integrated and freely enabled with autonomic capabilities. WebSphere Business Integration supports the transformation to an on demand business. An on demand business has the following characteristics.

IT view
Integrated A business process is mapped to application logic and integrated through middleware. All data is shared across dependent applications without redundancy. Open The application logic and interface is based on open standards, like J2EE and XML. Also, the application’s logic and data is self-describing. Logic and data describe what is used and how it is used, like Java Beans does.
1

Source: Sam Palmisano, IBM Chairman and Chief Executive Officer, in October 2002

38

WebSphere Business Integration for SAP

Virtualized The application has a large degree of redundancy to met its Service Level Agreements. Also, it is able to evolve and execute in the face of disasters or attacks. One way to achieve this is to run the application in a Grid environment. Also, the application is location and time independent to “run once” for all languages and locales. An example would be a SAP R/3 Unicode system. Autonomic The application has self-monitoring and self-healing capabilities. The application has the ability to recover from errors, clean up its data structures if corrupted, and continue running all of the time.

Business view
Responsive Able to sense changes in the environment and to respond dynamically to unpredictable fluctuations in supply or demand, emerging customer, partner, supplier, and employee needs, or unexpected moves by the competition. Variable Able to adapt cost structures and business processes flexibly, to reduce risk, and to drive business performance at higher levels of productivity, cost control, capital efficiency, and financial predictability. Focused Committed to concentrating on core competencies and differentiating tasks and assets; able to use tightly integrated strategic partners to manage tasks ranging from manufacturing, logistics, and fulfillment to human resources and financial operations. Resilient Prepared for changes and threats like computer viruses, earthquakes, or sudden spikes in demand. A business with these attributes requires technology that can support it, but that is not the computing environment that is operating today. No, today's environment is heterogeneous, widely distributed, vertically isolated, and generally more complex than businesses would like. The same IT that is essential to a business' ability to create strategic advantage is also a major obstacle to becoming the kind of fluid, responsive, dynamic business that has been talked about for years. Beyond just transforming department by department, business processes and applications need to integrate horizontally to link data, legacy systems, and

Chapter 2. Business Integration technology concepts

39

custom applications, and this integration requires new levels of data integrity and transaction processing. An infrastructure built on Web services, new development tools, and open standards is needed. On-demand integration, applications that had previously integrated vertically with an operating system and stand-alone processor must now integrate horizontally, application to application. Applications are written to the middleware layer, not to the operating system, and decoupled from the underlying infrastructure.

2.3 SAP Enterprise Service Architecture
This section gives an overview of the SAP NetWeaver technology platform that was announced by SAP in 2003. SAP NetWeaver is the technical foundation for mySAP Business Suite and SAP xApps. It is a rearrangement and consolidation of basic functional and business specific components to support cross-functional business processes. SAP NetWeaver is built on service oriented architecture paradigms and therefore has a lot in common with IBM’s On Demand business strategy. In SAP’s terminology the business applications packaged in the mySAP Business Suite and composed in SAP xApps are mostly referenced as applications that fit into a Enterprise Service Architecture. As shown in Figure 2-6 on page 41, the SAP NetWeaver technology stack can be divided into six core building blocks: People integration Information integration Process integration Application platform Composite application framework Lifecycle management

40

WebSphere Business Integration for SAP

SAP NetWeaver
People Integration
Multi-Channel Access Composite Application Framework Portal Collaboration Life Cycle Management

Information Integration
Business Intelligence Knowledge Management

Master Data Management

Process Integration
Integration Broker Business Process Management

Application Platform
J2EE ABAP

DB and OS Abstraction


Figure 2-6 SAP NetWeaver overview

.NET

WebSphere

This division supports the delivery of business integration capabilities of different levels. The fact that both WebSphere and .Net are mentioned in the official SAP NetWeaver overview chart emphasizes that NetWeaver is designed to interoperate with these primary market technologies. These interoperation capabilities can be pictured as the usage of well-defined APIs and common standards to offer SAP customers who implement SAP NetWeaver reliable bridges between the technology stacks. SAP has introduced the implementation of a huge variety of industry standards in SAP NetWeaver. The adherence and commitment to these standards are a major criteria for the success of the SAP NetWeaver technology. Figure 2-7 on page 42 lists some important industry standards that are supported in the various SAP NetWeaver building blocks.

Chapter 2. Business Integration technology concepts

41

Figure 2-7 SAP NetWeaver standards support

2.3.1 People Integration
People Integration within SAP NetWeaver is responsible for providing the user with the requested functionality with the right information. People that are in touch with the business, both internal and external users, get a seamless user experience regardless of how many systems are involved to fulfill the particular user request. SAP Enterprise Portal is the core component of the People Integration area. It delivers services like: Unification of business data Personalized views on business data Role-based access to business relevant information The Collaboration component is a part of the SAP Enterprise Portal package. It enables user to dynamically get in contact. Supported communication channels are: Shared e-mail and calenders

42

WebSphere Business Integration for SAP

such as interactive Web reports and personalized dashboards.Collaboration rooms Threaded discussions Document stores The Multi-Channel Access module is a layer that is put on top of the People Integration building block as an enabler to reuse existing components like portal and collaboration. The provided services include: Search capabilities Taxonomy Data classification Content management and publishing Chapter 2. SAP BI provides the tools to use information to make the right decision. SAP BI is able to visualize key success factors very flexibly using a wide variety of formats. which is shipped with SAP NetWeaver ’04. For a user or system.3. SAP Business Information Warehouse (BW) is a data warehouse that forms the foundation of the SAP Business Intelligence solution. KM therefore provides a service based single point of access to SAP’s content management system and third-part repositories. SAP Business Intelligence (BI) combines important corporate information from various data sources to enable the enterprise to manage and analyze every single business aspect in a very granular manner.5. set strategy. It extends the reach of existing user interfaces like SAP Enterprise Portal to devices like mobile and handheld devices via wireless and radio frequency technology. Business Integration technology concepts 43 . This transformation is done by classifying and structuring the enterprise data in such a way that it can be interpreted and is usable to the enterprise systems and the corporate user communities. Thus business data and functions can be accessed and executed offline and are replicated and synchronized in a consistent manner.2 Information Integration The Information Integration section includes products that are responsible for making structured and unstructured information available in the enterprise in a consistent and accessible manner. the access methods are transparent regardless of where the information is originally stored. SAP Mobile Infrastructure (MI) is the platform that enables multi-channel access to information and processes. 2. Knowledge Management (KM) in SAP terminology describes the products that are used to turn unstructured information into organizational knowledge. and measure the results of business tactics. The version. is SAP BW 3.

Master Data Management (MDM) is a brand new component in SAP’s business application portfolio. MDM defines only the core business logic. Additionally. how master data consolidation and management can be implemented. new business scenarios can be created using an integrated toolset. MDM is a perfect example of how the various components in the SAP NetWeaver technology stack work together and consume each others services.3 Process Integration Process Integration enables business processes to spread across system boundaries and execute seamlessly across heterogeneous IT landscapes. which belongs to the process integration module of SAP NetWeaver. SAP XI is the technical infrastructure for XML-based message exchange between SAP and non-SAP systems. but is also open to other open standards via pluggable interfaces. where standard formats can be imported and exported. SAP is now offering its own process and system integration suite. While in the past SAP focused on creating business applications with defined system interfaces for integration and the integration itself was done by dedicated system integrators. The technical core component of the process integration layer is the SAP Exchange Infrastructure (XI) (see Figure 2-8 on page 45). Data extraction and distribution services are provided by the SAP Exchange Infrastructure. that is. “Information Integration” on page 43. It enables the sharing of harmonized master data formerly trapped in multiple systems and ensures cross-system data consistency. The products located in this SAP NetWeaver area would be called traditionally middleware in IBM’s terminology. such as the Master Data Management example in 2. SAP XI’s integration capabilities are the foundation for all future SAP applications. 44 WebSphere Business Integration for SAP .3. SAP XI supports industry standards like BPEL4WS. It is already shipped with predefined business process templates from SAP.2. The goal is to have a consolidated master data system that reuses existing IT environments and leverages made investments. 2.3.

monitoring.Figure 2-8 SAP Exchange Infrastructure The Business Process Management (BPM) block pictured in the SAP NetWeaver overview diagram in Figure 3-6 is a component that spans across various SAP NetWeaver areas and can be understood as a virtual product. SAP Business workflow: Embedded within the SAP Web Application Server and automates business processes running within SAP components. which clears up the virtual character of this component: Ad Hoc Workflow: A component of the SAP Enterprise Portal framework that enables individuals to interact with business processes and create new. BPM is used to bring together the right people with the right systems. giving them the required information at the right time. analysis. Traditional SAP users are empowered through this component to interact with business processes. execution. Chapter 2. and optimization Support the business process lifecycle across system boundaries BPM can be divided into three focus areas. ad hoc processes. BPM is a process-centric technology to: Automate business processes within SAP components Enable users to interact with business processes Support the full business process lifecycle from design. but was already available in the pure ABAP based SAP Application Server. Business Integration technology concepts 45 . The component SAP Business workflow is not a new invention of SAP NetWeaver. automation.

Developers can also access the business objects of applications running in the ABAP environment to benefit from their business logic and persistence. SAP and IDS Scheer introduced a strategic co-development to integrate IDS Scheer’s ARIS Process Platform with SAP NetWeaver. and run all SAP NetWeaver applications. and monitor. execute. Developers can implement business logic and persistence with Enterprise JavaBeans (EJB) using the full J2EE environment. Business Server Pages (BSP). J2EE-certified run-time environment that processes the requests passed from the ICM and dynamically generates the responses. The underlying business layer provides the business content in Java or ABAP.3. SAP decided to involve business partners. configure. 2. the user interface can be developed with Java Server Pages (JSP). It provides the complete infrastructure to develop. The major key capability of SAP Web AS is the full support for both the proven ABAP and the innovative open source J2EE technology. This is not done by providing one hybrid interpreter or virtual machine. As mentioned above. deploy. SAP is new in the integration and middleware market. but by coupling the ABAP and the Java interpreter via well-defined interfaces and communication channels. SAP Web AS integrates the ABAP and Java personalities in one application server. It drives complex business processes across business applications and enterprise borders. available as product from SAP or IDS Scheer by mid-2004. Figure 2-9 on page 48 shows that the architecture of SAP Web Application Server can be separated into five areas: Presentation layer: In the presentation layer. In October 2003.4 Application platform The application platform of SAP NetWeaver is the SAP Web Application Server (Web AS). To achieve a fast start in this business area and to speed up the development and release of reliable and accepted products. Business layer: The business layer consists of a full-featured. This component enables business process to execute in heterogeneous system landscapes exceeding SAP applications. The product supports the entire process lifecycle leading to an extended BPM solution allowing the customer to optimize business processes from modeling to monitoring: design. ARIS for SAP NetWeaver. 46 WebSphere Business Integration for SAP . or with Web Dynpro technology.Cross-Component BPM: Part of the SAP Exchange Infrastructure. The goal is to create a comprehensive BPM solution aligning technology with business processes. The business logic can be written either in ABAP or in Java based on the J2EE standard. marks the first milestone on the way to an extended BPM solution and is the crucial point of the BPM building block in the SAP NetWeaver overview (see Figure 2-6 on page 41). model.

Simple Mail Transport Protocol (SMTP). Business Integration technology concepts 47 . Chapter 2. Business logic can be developed completely independent of the underlying database and operating system. and Fast Common Gateway Interface (FastCGI). Database independence is also made possible by support for open standards. modules are available for Hypertext Transfer Protocol (HTTP). SAP propagates the outstanding capabilities of Open SQL for ABAP to Open SQL for Java and offers a variety of standard Application Programming Interfaces (APIs) to application programmers. such as SQLJ. such as Java Data Objects (JDO) and container-managed persistence (CMP) for EJB. are also supported.Integration layer: The integration engine is an integral part of SAP Web AS and allows instant connection to SAP XI. Connectivity layer: The Internet Communication Manager (ICM) dispatches user-interface requests to the presentation layer and provides a single framework for connectivity using a variety of communication protocols. Persistence layer: The persistence layer supports database independence and scalable transaction handling. or the direct use of the Java Database Connectivity (JDBC) API. The database interface ensures optimized data access from within the ABAP environment through Open SQL. Currently. Other technologies. The integration engine provides messaging services that exchange messages between the components that are connected in SAP XI. Simple Object Access Protocol (SOAP). HTTPS (extension of HTTP running under the Secure Socket Layer (SSL)).

the complete lifecycle of business applications has to be supported. and scalability (just to mention a few of them). SAP NetWeaver provides centralized technology for all stages of the software lifecycle: Design of IT landscapes Technical installation Development. and deployment of business applications Operation Change management 48 WebSphere Business Integration for SAP . availability.5 Solution Lifecycle Management This building block addresses special requirements for heterogeneous enterprise system landscapes.3. To ensure the cost-effective operation of such complex environments with the requested quality of service in terms of reliability.3rd Party Apps/ Exchange Browser/ Portal SAP Web Application Server Connectivity Internet Communication Manager Presentation Layer Web Dynpro Integration Layer Integration Engine Business Layer J2EE/ABAP Persistence Database Interface Figure 2-9 SAP Web Application Server architecture 2. testing.

NetWeaver is the standard platform superseding the known mySAP. and gives developers a productive way to create composite applications on top of a set of heterogeneous applications.SAP NetWeaver provides tools. It provides a consistent object model and a rich user experience. called SAP xApps. technical and business documentation. The WebSphere Business Chapter 2.3. flexible. Therefore.4 Interoperability of WBI and SAP XI In January 2003. For future SAP releases.6 Composite Application Framework SAP Composite Application Framework (CAF) includes the methodology. tools. SAP introduced SAP NetWeaver as the new middleware environment for their open standards based. and run-time environment to develop and run composite applications. services oriented application software strategy (Enterprise Services Architecture). 2. SAP XI has to be seen as a given in all future SAP environments. SAP CAF leverages the service based architecture to rapidly compose new business applications out of reusable patterns. The fact that most customers are likely to have both WebSphere Business Integration and SAP XI in place makes the interoperability of both integration infrastructures a major success factor. The application design process is model-driven. tools. SAP XI is SAP's component for business process management and process integration and shipped within the mySAP Business Suite. That means reduced development and deployment time for new applications and business-pattern-oriented integration. Business Integration technology concepts 49 .com technology. A special object access layer decouples underlying systems from business objects and processes. methodologies. Most customers have both integration landscapes in place: SAP XI as an effective solution for integrating within SAP environments and WebSphere Business Integration as the traditional. One core building block of the NetWeaver technology stack is SAP Exchange Infrastructure (XI). Many future SAP solutions like Master Data Management requires SAP XI. WebSphere Business Integration addresses this demand for interoperability by providing a dedicated WebSphere Business Integration adapter that enables WebSphere Business Integration brokers to communicate with an SAP XI broker. and run-time environment to develop and run composite applications. 2. SAP CAF includes the methodology. in order to build applications with as little programming as possible. and proven integration infrastructure leveraging the huge set of existing technology and application adapters. and implementation services.

App B App C WBI Adapter for Siebel WBI Adapter for i2 App A SAP XI Broker IBM WBI Broker SOAP/JMS App D SOAP/JMS WBI Adapter for SAP XI IBM WebSphere MQ Figure 2-10 WebSphere Business Integration and SAP Exchange Infrastructure In addition to the WebSphere Business Integration adapter for SAP XI. IBM and SAP are committed to evolve and implement further standards that ease up business integration activities and make integration across vendor boundaries a feasible task. The Java Connector Architecture (JCA) and the Business Process Execution Language for Web Services (BPEL4WS) are perfect examples for such standards that are driven and supported by both companies. 50 WebSphere Business Integration for SAP .Integration Adapter for SAP XI 1.0 uses common standards like Java Messaging Service (JMS) and SOAP to provide an out of the box integration of this two integration landscape on the message level. as shown in Figure 2-10.

a review of various technology options. a sample business case scenario is introduced with individual Use Case specifications. All rights reserved. 51 . Constraints and assumptions are also included for IT implementation. 2004. providing an analysis of the integration requirements. and a designed to illustrate the interoperability of WebSphere Business Integration and the SAP system. Chapter 3.Part 2 Part 2 Business scenario solution design In this part. “Business case scenario” on page 53 introduces a sample business case scenario and defines four Use Cases in the business requirements. © Copyright IBM Corp. Part 2 consists of Chapters 3 to 5.

“Solution approaches and technology options” on page 73 analyzes the business case and identifies appropriate integration styles to be used. and operation model perspectives. Chapter 5. process flow. Various integration technology options are reviewed with detailed product mappings. messaging interactions. 52 WebSphere Business Integration for SAP .Chapter 4. Appropriate broker and adapter technologies are justified. “Solution design” on page 109 defines a solution to the business scenario from the architecture.

Constraints and assumptions are also included for IT implementation. Business case scenario This chapter is intended to present a sample of a real-world business scenario. Several business Use Cases are defined for demonstration purposes.3 Chapter 3. 53 . © Copyright IBM Corp. to illustrate what challenges two companies face when they decide to merge with each other. All rights reserved. 2004.

1 Business domain This section describes the current state of two companies that decided to merge and some key requirements that need to be taken into account to ensure a seamless integration of two heterogeneous environments. the scenario is intentionally simplified and does not claim completeness or overall soundness. which is one of the key factors for the business success and growth. a sophisticated Sales & Distribution process has been developed through years of evaluations. the infrastructure can be divided into four key parts: eCommerce Portal System Sales & Distribution System Supply Chain System Unconsolidated business applications 54 WebSphere Business Integration for SAP .1 Current business model of Company A Company A is a retailer in the high-tech industry with subsidiaries around the world. The company manufactures a small set of electronic products in their own factory.1. The overall infrastructure for this process comprises a set of best-of-breed business applications and systems that are optimized to guarantee on-time delivery of purchase orders and flexible product information management.3. Due to time and resource constraints. whereas the majority of their product portfolio is supplied from a handful of selected partners. 3. To automate the business activities and optimized management. As illustrated in Figure 3-1 on page 55.

and place orders. Business transactions receive the same quality of service regardless of which user group . Each customer is served with a personalized view of the eCommerce portal. and product distribution. or mobiles.customer or sales agent initiated them. Enhanced usability features ease up the daily tasks and made the eCommerce portal an accepted and well-rated business component. handheld devices. Business case scenario 55 . Beyond customers. who use the traditional sales channel to take phone calls from the clients and enter the order data into the system. the eCommerce portal is also used by the companies sales agents. we were able to customize it to fit Company A’s special business requirements. The system also interacts with various external systems for product information organization and customer data Chapter 3. The Sales & Distribution system is an off-the-shelf product. Customers can access the portal via the Internet using a variety of devices like standard Web browsers. which is adjusted to their special needs and which can be influenced by themselves. tracking. They can browse the product catalog. which handles the order management. search for product information.Customer eCommerce Portal Sales Team HR Team Procurement Team Regular Employee Customer Repository Sales & Distribution Product Master Data Business Application Business Application Corporate Information Intellectual Capital Supply Chain System Suppliers Figure 3-1 Conceptual model of Company A The eCommerce Portal System serves as the primary sales channel for the company. The same business rules and processes are applied to guarantee consistency across the whole enterprise. Although the system is based on a standard software product.

This sophisticated supply chain process enables Company A to handle their suppliers in a uniform way and gaining additional flexibility to adjust their product palette to react in a reasonable time to changing market situations. However. which makes regular operation and maintenance an easy task. The Supply Chain system is an highly customizable ERP product. The company manufactures high quality digital imaging devices in the upper price segment. and specially tailored for the particular needs of Company A with great flexibility. While the eCommerce portal is responsible for providing the customer a first class procurement experience. The uncentralized process model resulted in a number of stovepiped applications and heterogeneous environments. other than this leading-edge Sales & Distribution process. This interaction is based on well-defined and proven interfaces. 3.management as well as supply chain control. There is no common user registry or e-mail infrastructure in place. The systems are highly available. Business information and intellectual capital is distributed across different locations in the company on disparate platforms. and scalability. Most of them are based on open industry standards. The Supply Chain system and the Sales & Distribution system are not manufactured from the same business application vendor. fulfillment and delivery of the customer requests. which automates the supply chain workflow and supplier relationship management. as all parts and components are purchased from various partners and assembled in an installation plant. The system defines a detailed procedure that new suppliers have to fulfill to be qualified to participate in this supply chain network. Business requirements that arise that cannot be covered by the three well-aligned business applications listed above take a lot of time and money to be fulfilled. 56 WebSphere Business Integration for SAP . The heart of Company B’s IT infrastructure is a common groupware infrastructure.1. The overall infrastructure has been built based on open standards. Company B does not maintain its own manufacturing line. Each department hosts its own systems and customer data repository that are needed to run its business. and information updates are in real time.2 Current business model of Company B Company B is a niche player in the high-tech industry. The mounted goods are distributed worldwide mostly via wholesalers. reliability. no enterprise-wide technology solutions have been implemented in the past. which hosts nearly all internal business application in a uniform way. the Supply Chain system guarantees the corresponding execution.

The system supported the internal sales team in processing sales orders received from the wholesalers in a consistent and contemporary way.As illustrated in Figure 3-2. the infrastructure can be divided into three key parts: Sales & Distribution system Assembly plant Groupware infrastructure Customer Wholesale Sales Team HR Team Procurement Team Regular Employee Groupware Infrastructure Customer Data Sales & Distribution Product Master Inventory System Procurement Business Applications HR Corporate Information Finance Assembly Plant Suppliers Figure 3-2 Conceptual model of Company B The Sales & Distribution system is based on a standard business application. Additional sales channels are not established. The reason for this investment was that at this point in time and to date no standard software vendor provides an out-of-the-box solution that covers all requirements. Company B invested a lot of time and money to enhance and modify the standard application by custom development to fulfill special business requirements. An example is Chapter 3. Business case scenario 57 . The Sales & Distribution system features open interfaces that incorporate external data sources and provide Sales & Distribution functionality to external applications.

The next virtual component that acts in concert with the Sales & Distribution system is the Assembly plant. The workplaces of all employees are located within the corporate intranet. or Financing (FI) run their specific business applications on this groupware infrastructure. the focus is set more and more to lower the operation costs of the existing IT environments. but are implemented appropriately. and collaboration rooms belong to the groupware landscape. the tight IT budget is always the limiting factor. Web publishing.1. The Assembly plant consists of a couple of best-of-breed applications that are interconnected and act as a logical entity to the surrounding environment. This should help free up funds that can be used to drive innovations.the externalized inventor system. Corporate information databases as well as collaboration capabilities help to increase the efficiency of frequent tasks.3 Merger business objectives Both companies expect that they can complement each other and perform more efficiently as one company in the marketplace. The groupware infrastructure drives a huge set of people-centric business applications that the employees have to interact with in their daily job. which is tightly connected with the Sales & Distribution system. Even though Company B is open-minded to new technologies. Each supplier is connected in a proprietary manner. The merger of the two companies is driven by various business factors: Benefit from complementary product portfolios 58 WebSphere Business Integration for SAP . Company B has no common blueprint describing the relationship to a supplier but negotiated different contracts with every partner individually. Dedicated departments that ensures that these applications follow certain internal standards with regard to: Usability Operation Maintainability The company has an IT department to maintain and enhance all business relevant applications. Various departments like Procurement. Human Resources (HR). 3. Thus. Neither exchanged data formats nor access mechanisms follow an open industry standard concept. but is still an autonomous business application. This group is responsible for evaluating leading-edge technologies to justify the applicability and feasibility of these technologies to support current business processes. Common services like electronic mail. Company B has a corporate groupware strategy in place. The Assembly plant application landscape is historically grown and is tailored to fit specific supplier and production requirements.

Business case scenario 59 . it must be ensured that the traditional business execution is not disrupted. The final goal is to create a single virtual company. The companies can offer a new merged product catalogue within a very short time frame. Departments that are present in both companies can be pooled together.redbooks. Completely new business processes have to be introduced to expedite and support the merger. 3.4 Unified business model The new enterprise reviews all internal and external business processes step by step to ensure a unified execution of these processes across former company borders.1. but also and especially on the business process level. but belong to the same sector.com/redbooks/SG246354. The new company must become a nimble and competitive enterprise that is able to respond to the changing market conditions in a reasonable time. The unified conceptual model for the merged enterprise is illustrated in Figure 3-3 on page 60 (please refer to the online version. This spares expensive product portfolio adjustments. to see the relevant colors).Achieve cost reduction by sharing common infrastructures Increase efficiency by consolidating business processes Profit from each other specializations in certain business areas Introduce a more flexible company structure The product offerings of the companies do not overlap. Processes of the former companies must go through detailed reviews that reveal weaknesses and areas of improvement. Beyond all these transformation activities. This consolidation would not only take place on the head count level. The HR and FI departments are perfect candidates for such a consolidation. Chapter 3. found at ftp://www.ibm.

60 WebSphere Business Integration for SAP .Customer Wholesale Sales Team HR Team Procurement Team Regular Employee Common Groupware Infrastructure Customer Sales & Distribution Customer Repository Customer Repository Business Applications Corporate Information Policy Service Sales & Distribution Sales & Distribution HR System Procurement System Supply Chain System Suppliers Inventory System Assembly Plant Internal Purchase Requisition System Procurement Team Regular Employee Figure 3-3 Conceptual model of the merged enterprise The green blocks illustrate the existing infrastructure of the former Company A and the yellow blocks the existing infrastructure of the former Company B. which leverage existing assets and add new systems for new processes. Process 2 is a brand-new people-centric process that allows authorized employees to request internal purchase requisitions. This requisition has to pass an approval procedure and finally be placed in the electronic procurement system. Blocks with mixed colors represent unified components. The red lines depicts where the four processes in the new model are located and are discussed in more detail further in this chapter: Process 1 couples both Sales & Distribution systems to enable customers or sales agents to place orders for former Company B’s products through the eCommerce portal.

All employees are connected via e-mail and can access company wide information from their workplace. This central user management concept significantly reduces the administrative overhead. it is a seamless integration. The new product introduction process must become a unique process for all product categories for mid-term and long-term. A central user registry is implemented that provides authentication and authorization services to general business applications via standardized interfaces. For the customer. and storing the new records in a consolidated repository. Together with this initiative. This means adding new customer data through a groupware interface. The open architecture of the eCommerce portal supports this extension perfectly. Availability dates and delivery times are provided consistently across all products. Business case scenario 61 . All specific supplier relationships are substituted with a unique supplier relations process that ensures on-time delivery of goods and a transparent contract negotiation cycle. The eCommerce portal offers a product publication process that all former Company B products have to follow. The role based authorization concept ensures that an employee sees and gets the exact information required for its respective job role. These short term and long term requirements must be executable on the same business integration middleware. The details of these new processes are discussed in the sections that follow. This extends the reach of Company B’s sales market considerably. Process 4 creates a new process to furnish the sales agents. Company B has a company wide groupware strategy in place.5 Unified business model benefits The most significant benefit is to sell the former Company B products through Company A’s eCommerce portal. It is consistent to utilize the existing supply chain when the products are sold in the common eCommerce portal and save costs in the procurement area. The architecture of the existing groupware infrastructure supports this extension. 3. The challenging part for the business integration middleware in the short term is to coordinate the exchange of the assembly information of the former Company B products into the existing supply chain network. a common employee registration process is introduced. The requirement for the underlying business integration middleware is to merge the information from different existing system resources. No adjustments on the portal are required.Process 3 connects the inventory validation logic of former Company B products transparently to the eCommerce portal.1. Another area of synergy is to use Company A’s optimized supply chain to obtain the components required to build the products for former Company B. There is a plan to extend this offering to all employees of the merged enterprise. Chapter 3.

“Business scenario solution implementation” on page 143. This application has to query the HR system for this information and request the approval from the respective person. so it is of vital importance to establish a process where product data is maintained in the new enterprise. payroll. recruitment. The processes have to cover various HR areas like time and travel management. extensibility. and distribution execute in the same environment. These processes must fulfill the requirements of the different job roles in the company and the specifics in the particular countries. 3. This new process guarantees that the traditional businesses keep on running while a smooth transition is started to consolidate both repositories. 62 WebSphere Business Integration for SAP . 3. The product data repository is the new central component of all master data management activities that the company will execute in the future and it has to provide a high level of openness. An example could be an internal process that is triggered by an employee and requires the approval of its manager. and personnel development. the HR solution becomes the central point of access for all applications or processes that require HR specific information. benefits. A product list is stored in the central repository and distributed to the surrounding business components as required. The HR solution enables the staff department to make management analysis of the actual staff structure. Processes for master data creation. Changes are done in the central repository and synchronized.2 Business Use Case definition This section describes four Use Cases in more detail to expose their business workflow processes. Beyond the administrative usage. it is necessary to develop a set of common Human Resources (HR) processes.Product data repository Both companies maintained their own product data repositories. The technical solution design and implementation using comprehensive business integration technologies is covered in Part 3.To manage the increased number of employees efficiently in a unique way.2. The operation of the new product data repository system is done using the existing standard groupware infrastructure so that the induction period for the employees who are maintaining it is as short as possible.1 Use Case 1 . updates. and scalability. The Use Cases are further analyzed from a business perspective only. The goal is that the new repository appears to the affiliated business components as one logical component.

The product repository needs to meet the following requirements: Ensure consistency of product data across all business applications. Distribute product data to external partners without major architectural changes of the product data repository system. Business case scenario 63 . Chapter 3. Ensure easy connectivity of various internal applications and external partners. Figure 3-4 on page 64 shows the business case diagram for Use Case 1. The product data has to be made available in synchronous and asynchronous ways to meet all kinds of demand. The interfaces of the product data repository have to follow common industry standards.

Use Case 1 3. The new process enables employees 64 WebSphere Business Integration for SAP .2 Use Case 2. Having a common internal requisition process in place is essential to achieve cost control and cost savings in the future.ERP System Sales & Distribution Data Synchronization and Transformation Enhanced Event Handling Material Master Data Legacy System Figure 3-4 Business case diagram .2.Internal purchase requisition process Internal purchase requisitions are a major expense factor of the new enterprise.

the originator of the request is informed about the result. orders are placed in the procurement system or rejected. Business case scenario 65 . In both cases. Figure 3-5 on page 66 shows the business case diagram for Use Case 2. Depending on the products ordered. The HR system is an independent company wide application that provides employee and organizational data via open service based interfaces. Based on the decision of the approver. Requests that require approval are presented to the approvers via the same electronic channel using the existing groupware infrastructure. Based on which policies are effective. The order and approval policies are also defined by the procurement department and are located in a separate system. The integration of the existing procurement system is done in a way so that it is exchangeable in the future.to order goods centrally via an electronic channel. The goods available are predefined to ensure a cost efficient procurement process. the new process has to query the enterprise Human Resource (HR) system for employee data to be able to route the approval request to the correct person. Changes in the connected systems do not require changes in the business process. The preselection of these goods is done by the procurement department. Some products can be ordered without approval. while others may require specific approval. Chapter 3. The goal is to use external procurement system providers in the future to handle the complete delivery process of ordered goods. different policies are applied accordingly. The major characteristic of the internal purchase order requisition process is that it is highly flexible and completely independent from the back-end systems it incorporates to fulfill the specific business process.

66 WebSphere Business Integration for SAP . The customer does not recognize that the shown ATP data is retrieved from a different source. The eCommerce portal calculates availability dates of requested goods online by using a unified available to promise (ATP) check business logic. This seamless integration is essential to provide a unified corporate presence to the customer.Use Case 2 3.Inventory availability validation Customers are able to order products from former Company B in the common eCommerce portal.Figure 3-5 Business case diagram .3 Use Case 3 .2.

This means that a certain lead time is added to the order date. The eCommerce portal is able to relate specific products to the respective ATP check business logic and retrieves the information from the right source. This approach does not fulfill the expected quality of service the eCommerce portal delivers to the customer but can be used as a fall-back solution to be able to provide an ATP date at all. An alternative would be to provide static ATP data. Chapter 3. Business case scenario 67 .The ATP check integration is implemented as a non-invasive solution and guarantees that the eCommerce portal business logic on one side and the production system on the other side are not affected. The requested ATP information is real-time data that gives the customer the certainty that the ordered goods are available at the given point in time. The key characteristics of the desired solution are: Seamless integration into existing eCommerce infrastructure Non-invasive integration style Adjustable to reflect changing market situations in a reasonable time Figure 3-6 on page 68 shows the business case diagram for Use Case 3.

Use Case 3 68 WebSphere Business Integration for SAP .ERP System Sales & Distribution Process Automation and Collaboration External Availability Check Legacy System Figure 3-6 Business case diagram .

3. The major challenge for this solution is to integrate two existing components that are already tightly contained in different landscapes. The customer data repository provides synchronous and asynchronous as well as transactional access to the requested data. Different applications require different access methods to the customer data repository. Chapter 3. The steadily increasing range of business wide applications that rely on the correctness and availability of the customer data necessitates that the customer data repository delivers a high degree of reliability and scalability. Existing business applications can still access customer data in the same way they used to. Integration has to be done by coupling two integration infrastructures together without disrupting their original functionality.2. To ensure the high quality of customer data.1. This transformation is done without losing any historical information of the customers. The goal is to have one logical customer data repository that hosts the customer master data of both former companies. Its architecture also supports future extensions to exchange customer data with external partners across enterprise boundaries.Product data repository” on page 62.4 Use Case 4 . Business case scenario 69 .2. specific processes are established for customer data creation. change. “Use Case 1 . and deletion. The key characteristics of the desired solution are: Single point of maintenance Current and consistent customer data Provide different access mechanisms High availability of this business critical data Figure 3-7 on page 70 shows the business case diagram for Use Case 4. This guarantees the consistency and accuracy of the customer data repository for the future.Customer data repository This Use Case has much in common with 3. Future operation of this common customer data repository can be performed via the existing groupware infrastructure to enhance the usability for the employees maintaining the current customer data repository. Like in the master data area. the new enterprise has to establish a common process for customer base maintenance and introduce a common customer data repository. The customer master data has to remain consistent even if it is used by various independent business applications.

Figure 3-7 Business case diagram .Use Case 4 70 WebSphere Business Integration for SAP .

3 Constraints and assumptions To simplify the design. integrity. Scalability. facilitate delivery of a demonstration application. Part of a process is implemented in a transaction as deemed necessary. Company B’s Sales & Distribution system is based on SAP R/3. Secure Sockets Layer (SSL) is a viable option at the transport layer. and disaster recovery topics are not addressed.3. the following requirements and assumptions are established: Company A’s eCommerce portal is a Web-based J2EE application. Minimum exception handling is implemented to deal with errors resulted from incorrect data formats. authorization. Company A’s supply chain system is a standard application. Company B’2 inventory repository is implemented as a relational database. and focus on the integration solutions in a heterogeneous environment. Necessary data protection is designed in the inter-system communications. Minimum system management and monitoring is provided. confidentiality. Company B’s groupware infrastructure is implemented using Lotus Domino technology. availability. and invalid data contents. Chapter 3. encryption. The following supporting system design are not in the scope: Firewalls are not included in the cross-network communications. Business case scenario 71 . Company B’s Material Management system is based on SAP R/3. Security topics like user authentication. insufficient data elements. and non-repudiation is not included. Company A’s Sales & Distribution system is based on SAP R/3.

72 WebSphere Business Integration for SAP .

an overview of the integration brokers and adapters of the WebSphere Business Integration product family as central technology provider is given. Solution approaches and technology options This chapter introduces the technology for implementing the Use Cases that are defined in Chapter 3. Subsequently. 2004. The chapters ends with a discussion of the WebSphere Business Integration adapters for mySAP. “Business case scenario” on page 53.com and SAP Exchange Infrastructure. Then special requirements for SAP integration are collected. The chapter starts by covering general characteristics of the basic technology integration components. 73 . namely integration broker and adapters. All rights reserved.4 Chapter 4. © Copyright IBM Corp.

Each of these bilateral connections would be required to extend at least one of the EISs involved. The complete infrastructure would be very static.4. One of the main challenges is to agree on a common denominator in terms of finding a universal nomenclature and coordinate the different interface types of the various Enterprise Information Systems that have to be integrated. using direct interconnections between the different EISs without an intermediate instance would require extending the existing EISs with connection functionality (Figure 4-1). In addition. a huge effort would have to be spent on maintaining and managing connections from many different places. because changes in one component would require the adjustment of a multitude of affected connections. This would result in the development of dedicated connection solutions for converting data and process logic from one EIS to the other. Figure 4-1 Business Integration with direct connections 74 WebSphere Business Integration for SAP . The heterogeneity ranges from different protocols and data formats at the transport level up to the support of different programing paradigms at the Application Programing Interface (API). It is common that EISs used in different business areas run on different platforms and that each EIS provides a typical interface and access mechanism.1 Basic technology integration components The understanding of business integration within this book is to connect data and processes of existing Enterprise Information Systems (EIS) into an overall business infrastructure. Given the heterogeneity.

for example. synchronization of data from various resources or executing short term or long term business processes. the integration broker may process business logic between connected EISs. The introduction of a central broker together with specific adapters for the connected EIS constitute the adaptive character of this integration architecture. mapping. In addition. Solution approaches and technology options 75 . on the received data before forwarding it. and prevents complex adjustments when the involved back-end systems change. or aggregation.A more manageable and efficient architecture for business integration is to introduce a central integration broker and EIS specific adapters (Figure 4-2 on page 75). The adapter is responsible for transforming the EIS specific data into a common format that is agreed upon with the integration broker. Figure 4-2 Business Integration with a central integration broker The integration broker is responsible for routing data between participating EISs and performing transformations. The integration broker does all processing and transformation based on the common format. Each EIS is connected to the central integration broker using a dedicated adapter. Chapter 4. such as parsing.

a further main characteristic of an adapter is that it runs within its own process. the EIS can be accessed without being changed. Type Description of EIS Specific Data EIS Specific Data of Various Types Transformations Data in Integration Broker Format Figure 4-4 Type description driven by data transformation within an adapter Besides doing the transformations. but it can bundle different interfaces of the same EIS. Adapter Enterprise Information System EIS Specific Outlet Transformations Integration Broker Specific Outlet Integration Broker Figure 4-3 Internal structure of an adapter It is common that a fairly complex EIS can be accessed by various interfaces. In this way. 76 WebSphere Business Integration for SAP . The integration broker must understand only one protocol and one data format when communicating with the adapters . The outlet to the integration broker supports the interface of the integration broker. in this way. This information is stored in configuration files and enables the adapter to cope with EIS specific application data of various data types and access mechanisms during run time. and thus decouples its availability from the other systems to be integrated. The outlet to the EIS understands its given application interface.An EIS specific adapter contains two outlets (Figure 4-3 on page 76): one interfacing to the respective EIS and one interfacing to the integration broker. This can be achieved by configuring the adapter with the description of the exchanged data and the interface type to be used with the EIS (Figure 4-4). An adapter is not limited to supporting only one interface per EIS. This relieves the integration broker from accessing the EIS directly. Additionally. the adapter is an abstraction layer and shields the integration broker from the peculiarities of an EIS.

is called Request Processing. The other scenario. special functionality must be introduced that enables an adapter to retrieve the event by itself.Being an active component. The latest SAP Chapter 4. in which data get forwarded from an integration broker to an EIS. Solution approaches and technology options 77 . this is done using an Event store for buffering events and extending the adapter by a mechanism for detecting events stored there. which are called by the adapter directly. The middle tier is comprised of SAP application server instances. called Event Processing. Request Processing Enterprise Information System Interface to EIS Adapter Integration Broker Event Processing Enterprise Information System Event Store Adapter Integration Broker Figure 4-5 Bidirectional communication between an EIS and integration broker The scenario. usually drives a business integration scenario in that data. the adapter can independently support bidirectional communication between an EIS and the integration broker. The database layer provides the central persistency instance and supports a wide palette of databases of all the major database vendors. 4. The end users are utilizing a specific fat client style SAP graphical user interface (SAPGUI) to access the SAP back-end system. or events. Normally. which distribute the workload among each other to serve the expected requests within a reasonable response time. are produced independently within an EIS and need to be forwarded by its adapter to the integration broker. as shown in Figure 4-5 on page 77. If the EIS cannot be configured to submit events to an external component directly. and is usually based on existing interfaces of an EIS.2 SAP specialities regarding business integration The SAP enterprise server is implemented following a three-tier architecture.

It is not unusual that an SAP infrastructure consists of many different SAP releases on different platforms. With the introduction of the mySAP. this traditional architecture has been extended to support additional standard Internet technologies. 4. The functionality increases and new components for upcoming business areas appear while older releases still have to be maintained and keep on running.com technology. the new SAP Web Application Server (WebAS) comes with an additional Java personality implemented on a full blown Java 2 Enterprise Edition (J2EE) application server. The portfolio goes from standard application modules like Human Resources and Material Management up to industry-specific solutions for the automotive industry or the telecommunication sector. 78 WebSphere Business Integration for SAP . SAP NetWeaver is the current technology platform that delivers business applications on both technology stacks ABAP and Java. These business applications are not static entities but steadily changing components. Integrating the SAP enterprise server into a business integration scenario has to support the various releases of a SAP enterprise system and its most important interfaces. as shown in Figure 4-6 on page 79. The traditional SAP business applications were packaged in so called modules written in Advanced Business Application Programming (ABAP) and executed on the SAP Application Server. Beyond the proven ABAP capabilities.1 Support of various SAP releases SAP provides ambitious business applications in a huge number of business areas.2.releases also introduced standard Web browsers as an additional end-user client type.

with its steadily growing application components. With the latest SAP releases.0 Figure 4-6 Different SAP system releases The complex SAP infrastructure. test and production. in parallel. It is common that the various systems run in a heterogeneous infrastructure. an additional Java technology stack beyond the traditional ABAP stack is included within SAP solutions. such as: Support for different software releases and platforms New releases extend the provided business logic and introduce new interfaces.70 Integration hub SAP Financial Accounting 4. like development. Support for a distributed enterprise architecture The architecture of the business integration solution has to be distributable itself to meet enterprise requirements. The solution must deliver a high degree of adoptability to fit into a multi-staged infrastructure. consisting of multiple SAP environments.6C SAP Quality Management R/3 Enterprise 4. Chapter 4. Solution approaches and technology options 79 .0B SAP Customer Relationship Management 4. makes specific demands on an effective business integration solution.Customer Data SAP Human Resource 4. This increases the numbers of appointed interfaces significantly.

2. as listed below and in Figure 4-7: Development environment Test environment Production environment Test I Performance Dev I Development System Test II Usability Unit Test Production System Transport System Dev II Sandbox tSystem Test III Consolidation Development Stage Test Stage Production Stage Figure 4-7 Typical SAP system landscape The first stage contains SAP systems for core development.4. Multiple developers can work in parallel on the same project without disturbing each other. These custom SAP development efforts are embedded in a proven development architecture. SAP introduced a three-stage development concept. This is a major decision criteria for SAP.2 Support of a staged system landscape SAP business solutions deliver a huge portion of functionality out of the box and SAP applications are highly customizable. A 80 WebSphere Business Integration for SAP . Therefore.

ALE and IDocs ALE can integrate business processes between different back-end systems (SAP and non-SAP). Finally. ALE uses IDocs to pass information in and out of SAP. and high availability are out of scope at this stage. Chapter 4.3 Support of various SAP R/3 interfaces This section gives the reader an introduction and overview about the different types of SAP R/3 interfaces.2. At a certain development status. Electronic Data Interface. Solution approaches and technology options 81 . such as usability. process flow. It is not common to access raw data within the SAP R/3 system directly. other applications also have to prove that functional and nonfunctional requirements are met.sophisticated locking and repository mechanism ensures that the developed assets stay consistent. Production features like load balancing. clustered environment with multiple application servers. It enables the controlled exchange of consistent business data between loosely-coupled SAP application systems and non-SAP systems. At this stage. The focus is to rapidly produce the required application logic. It can be understood as the serialized representation of a business object. performance. One of the prescribed accessing mechanisms has to be used to accomplish this task: Application Link Enabling (ALE) & Intermediate Documents (IDOC) Remote Function Call (RFC) Business Application Programming Interface (BAPI) Batch Data Communications (BDC) Electronic Data Interface (EDI) Web Services (SAP Web Application Server 6. ALE represents an asynchronous communication style. At this point. error handling. This environment must be able to serve the expected workload the custom business application is facing. approved application components are transferred to the production environment. the produced components are transferred to the test environment. which is generally a high available. SAP provides a dedicated transport system to guarantee a consistent replication of newly developed and tested revisions between the different stages. 4.20 and later) Batch Data Communications. and Web Services are not within the scope of this chapter. An IDoc is an information container that has an exactly predefined (structured ASCII) format. and reasonable response times. unit tests are carried out to ensure that the complete application works together as expected.

which describe the common data format handled within WebSphere Business Integration adapters and Integration Broker. the common characteristics of an adapter for business integration are introduced. This section ends with a short presentation of the configuration and development tools. RFCs represent a synchronous communication style. 82 WebSphere Business Integration for SAP .1 WebSphere Business Integration adapters At the beginning of this chapter. It first takes a deeper look at the WebSphere Business Integration adapters.3 WebSphere Business Integration product suite capabilities 4.3. The section starts with a discussion of business objects. Technically. SAP guarantees that the interfaces of the provided standard BAPIs remain stable over a certain release levels.RFCs RFCs are SAP specific Remote Procedure calls in the distributed SAP landscape. Note: A WebSphere Business Integration adapter consists of the adapter’s connector and its configuration and development toolkits like Object Discovery Agent (ODA). This section shows how these general notions are fulfilled by the WebSphere Business Integration product suite. However. 4. the terms adapter and connector are used synonymously within this book. for the sake of simplicity. they are implemented as RFC-enabled function modules for an SAP business object’s method. the technical architecture of the adapter is described. A BAPI can be understood as a class or instance method of business object located within a SAP system. Then. BAPIs BAPIs are an object oriented programming interface. three different integration brokers provided by WebSphere Business Integration are introduced. BAPIs represent a synchronous communication 4.1. This section covers how IBM WebSphere Business Integration adapters implement these general concepts. “Basic technology integration components” on page 74 introduced the general notion of an integration broker and active adapters. ABAP function modules can be marked as remote enabled and made accessible to a RFC client remotely. The SAP system can act as an RFC server or as an RFC client. Subsequently.

Solution approaches and technology options 83 . or a reference to a child business object. Such a record comprises a list of attributes. Customer Account ID type = string Attributes Name type = string Account type = Account cardinality=n Profile type = Profile cardinality = 1 Verbs Create Update ID type = string Credit Data type = string Profile ID type = string Profile Data type = string Figure 4-8 Sketch of a business object Definition “Customer” Technical architecture of WBI adapters A WebSphere Business Integration adapter consists of two parts: the Application Specific Component and the Adapter Connector Framework (Figure 4-9 on page 84). A business object consists of payload data as well as instructions on how to process the data. called verbs.Business objects Business objects define a common format for exchanging data between an adapter and an integration broker (Figure 4-3 on page 76). Chapter 4. like string. Arrays are defined as being child business objects of cardinality n. but differ in the application specific component. like Create. The interpretation of these operations. The payload data is defined as a hierarchical record structure (Figure 4-8). Update and Delete. Processing instructions are defined as standard operations. either having a simple type. within an adapter or integration broker depends on the EIS to be integrated. All connectors share the connector framework.

Technology adapters. call the native interface of an EIS. A business object handler for converting EIS specific data into a business object and vice versa. provide a more generic interface. An event notification mechanism to detect and respond to application events within the EIS. Application adapters. EDI.com. on the other hand. Depending on the type of application interfaces. This can be accomplished by configuring the business object handlers to use a data handler that provides a transformation functionality of a dedicated format. or delimited. like the WebSphere Business Integration adapter for mySAP. like XML. An example is the WebSphere Business Integration adapter for SAP Exchange Infrastructure. The application specific component comprises: A connector base class to initialize and set up the connector.Adapter Application Interface Functions Generic Services Enterprise Information System Application Event Notification Global Utility Functions Transport Layer Business Object Handlers MQ JMS Integration Broker IIOP Application Specific Component Figure 4-9 Adapter architecture Adapter Connector Framework The application specific component of an adapter provides bidirectional connectivity with the interfaces of its connected EIS for request as well as event processing. While for an application adapter the transformation between its native data format and business objects can be built in. 84 WebSphere Business Integration for SAP . usually based on open standards. for integrating a connected EIS. It corresponds to the entities EIS specific outlet and transformations in Figure 4-3 on page 76. a technology adapter must be able to handle data from an EIS of various formats. which is based on JMS. there are two categories of WebSphere Business Integration adapters.

which are listed in Figure 4-10. Connector Configurator Adapter Enterprise Information System Application Specific Component repository Adapter Connector Framework Integration Broker ODA Business Object Designer Figure 4-10 Configuration tools for WBI adapters The Connector Configuration tool is used to create and modify the connector’s configuration file that contains all the parameters. and CORBA IIOP as transport protocols. The various tools that are provided for configuring an WebSphere Business Integration adapter are depicted in Figure 4-10. The application interfaces. In addition. Important configuration parameters are: The business object definitions that the adapter is able to handle. which an EIS offers. This layer supports WebSphere MQ. the connector framework offers generic services like monitoring. the Adapter Connector Framework provides bidirectional interaction with the integration broker by means of the transport layer. logging. The integration broker that is utilized. Solution approaches and technology options 85 . However. Chapter 4. this requires an adapter to be a highly configurable entity. JMS. and tracing. Different transport protocols for communicating with an integration server.Corresponding to the entity “Integration broker specific outlet” within Figure 4-3 on page 76. Configuration and development tools for WBI adapters The concept of an adapter offers integration of existing EISs using ready-made components and hence without developing dedicated integration solutions.

Using the Object Discovery Agent (ODA). In the same way. WebSphere InterChange Server Enterprise Information System Adapter ASBO Controller GBO Business Process Integration Collaboration GBO Controller ASBO Mapping & Cross-Referencing Mapping & Cross-Referencing Figure 4-11 WebSphere InterChange Server Architecture At the heart of the InterChange Server are collaborations. The definitions are stored within a repository that can be accessed by the business object handler within the application specific component of an adapter.ibm. 4. The adapter drives the transformation of EIS. a business object definition can be derived automatically from the data formats provided by a EIS. represented as XML schemas.Business object definitions.3. An actual list is provided at the following URL: http://www. which are software modules that contain code and business process logic that drive interactions between connected EIS. there is an Object Discovery Agent Development Kit (ODK). which consists of a set of APIs to develop a custom ODA. are created and edited using the Business Object Designer tool. and thus corresponds to the type description entity in Figure 4-3 on page 76. The logic of a collaboration comprises static and 86 WebSphere Business Integration for SAP . the connector uses the Data Handler to transform EIS specific data into business objects and vice versa. IBM provides a huge portfolio of application and technology adapters.2 WebSphere InterChange Server WebSphere InterChange Server (Figure 4-11) is a convenient broker for implementing integration scenarios that involve data and process coordination between different EISs with special requirements on centralized business processing rules. Based on the business object definition.com/software/integration/wbiadapters If a given EIS is not supported by an adapter. it can be developed based on a framework provided by the WebSphere Business Integration Adapter Development Kit (ADK).

an SAP R/3 has its own notion of a data describing “Customer” entities. Solution approaches and technology options 87 . like merely copying of attribute data. It may contain simple transformation steps. and relationships are created and maintained using dedicated tools. even self developed mapping operations can be used. mapping. When attributes in a source and destination business object contain equivalent data that is represented differently. the InterChange Server distinguishes between application specific business objects (ASBO) and generic business objects (GBO). the transformation step employs cross-referencing. A GBO can be regarded as an abstraction of related ASBOs.dynamic routing of data. extracting all the attributes that are relevant for exchange and business process logic. Since collaborations only work on GBOs. from a semantic point of view.application independent process logic. A relationship establishes an association between data from two or more business objects and is usually implemented using the contents of database tables. For example. up to more complex operations. Collaborations.to a certain extent . This is a common format for all adapters. ranging from simple piping of data between connected EISs to complex synchronization of data from various sources and multi-step process coordination. like a customer ID or a country code. Chapter 4. Each connected adapter must have a controller as a counterpart within the InterChange Server. it is still dependent on the EIS. An adapter converts EIS specific data into a business object. like joining several source attributes to a destination one. Data mapping is the process of mapping attributes from a ASBO to a GBO and vice versa. these business objects are named ASBO. Hence. In order to separate the process logic as much as possible from the connected EIS. they provide . which is a run-time service that mediates between an adapter and the collaboration on the ICS. however. A GBO is derived from a ASBO through a data mapping and cross-referencing step. containing more or different attributes than related business objects from other EIS. Based on a given mapping API. also called a relationship. which are controlled from within the Eclipse-based workbench System Manager. The mapping and cross-referencing step is performed within the connector controller.

WSADIE provides 88 WebSphere Business Integration for SAP .1 onwards. This is the de facto industry standard for defining and executing business processes in a flexible and platform neutral manner. even if it is marked as deprecated. In addition.3.4. and administer business processes seamlessly across different platforms and system boundaries. execute. The core products that are shown in Figure 4-12 mentioned areas to support the complete business process application life cycle are WebSphere Business Integration Server Foundation V5. It is a Java 2 Enterprise Edition (J2EE) compliant application server built on the entrenched WebSphere Application Server.1 WebSphere Business Integration Modeler V5.1 Figure 4-12 On demand Integrated Platform Suite WBISF supports Business Process Execution Language for Web Services (BPEL4WS).1 WebSphere Business Integration Monitor V5. The goal is to introduce an on demand Integrated Platform Suite that allows you to design. The IBM proprietary standard Flow Definition Markup Language (FDML) is still supported. develop. The WebSphere Studio Application Developer Integration Edition (WSADIE) includes wizard driven migration support to minimize transition times as much as possible. WBISF can be considered as the rebranded name of the WebSphere Application Server Enterprise Edition from Version 5. to allow customers to migrate from FDML to BPEL during a transition period. The rebranding reflects the trend to merge typical integration server capabilities with traditional application server technologies.1 WebSphere Studio Application Developer Integration Edition 5.3 WebSphere Business Integration Server Foundation WebSphere Business Integration Server Foundation (WBISF) is IBM’s next generation integration platform supporting open industry standards.

Short-running processes – Non-interruptible processes that maintain only the active state. WBISF provides the run-time environment for WPC. WPC supports long-running as well as short-running business processes. WPC is also sometimes called the business process container of WBISF or the Business Process Execution (BPE) container. Solution approaches and technology options 89 . – Process state is not persistent. It is implemented as a J2EE application that uses the underlying WebSphere Application Server run-time services and resources. Figure 4-13 on page 90 shows the components of the container. Typical business processes implemented in an enterprise require the interaction of human and IT resources following well-defined rules. – Also mentioned as macroflow. WPC supports service composition as specified by BPEL4WS and enables developers to define the structure and behavior of a business process. – Also mentioned as microflow.tooling support to develop business processes visually using comprehensive editors. Important: There are various names for the same characteristics of business processes: Long-running processes – Interruptible processes that can be suspended and resumed. Business Process Choreographer (BPC) provides support for business-process applications within the WBISF. – Process state is persistent. Chapter 4.

GBOs. WSIF Compensation Observer Audit Trail Navigator Process. The complete WebSphere Business Integration Adapters portfolio can be utilized via the WebSphere Business Integration Adapter Framework. as one integration broker. supports this programing model.Business Process Engine External I/F Session EJBbased API Internal I/F Request Dispatch Process Navigation Data Handling Variables. LDAP Authorization Work itembased Factory Persistent Storage Handler Transient Storage Handler Business Process DB Messagedriven Beanbased API Internal Queue Handler MDB Figure 4-13 Business process execution container architecture The WebSphere Business Integration programing model is based on the adapter based integration of various back-end systems into a common integration broker environment. Mediations. Suitable Mediations are applied on the application specific business objects (ASBO) to generate generic business objects (GBO). Figure 4-14 Adapter based integration in WBISF 90 WebSphere Business Integration for SAP . Activity External Queue Internal Queue People Interaction Work Item Manager Staff Queries User Reg. and Adapters in a WBISF environment. Figure 4-14 illustrates the relationship between ASBOs. WebSphere Business Integration Server Foundation. Conditions Invocation Java.

the application that sends the information knows which application receives the information. The sender application publishes messages that contain the information and applications receive the information according to the topics that they have subscribed to. once-only delivery of each message (see Figure 4-15). WebSphere Business Integration Message Broker provides point-to-point messaging as well as the Publish/Subscribe style of messaging. and even transform the message from one format to another. WBI Message Broker WBI Event Broker WebSphere MQ (Incl JMS) Figure 4-15 WBI Message Broker extends WBI Event Broker In a WebSphere Business Integration brokers environment. interact with databases. In point-to-point messaging.4 WebSphere Business Integration Message Broker WebSphere Business Integration brokers provide a publish/subscribe style of messaging. the complete WebSphere Business Integration Adapters portfolio can be utilized via the WebSphere Business Integration Adapter Framework (see Figure 4-16 on page 92). the application that sends the information does not know which application receives the information. WebSphere Business Integration brokers products use WebSphere MQ’s messaging and queuing technology to transport information between business applications in the form of messages.4.3. WebSphere MQ provides assured. The broker can also manipulate the message content. Chapter 4. In publish/subscribe messaging. Solution approaches and technology options 91 . WebSphere Business Integration Message Broker incorporates and extends WebSphere Business Integration Event Broker. The benefit of point-to-point messaging is that the broker can route the messages according to the message content.

the platforms on which the applications are installed. the integration broker places the resulting message on the WebSphere MQ queue for the connector for application B. and customers. After the message is processed by the message flow. 92 WebSphere Business Integration for SAP . Exchange information between applications regardless of the information format. An adapter converts application specific data into an application specific business object.The logic of a message flow comprises static and dynamic routing of data. Integrate dissimilar computer systems that an organization owns as a result of mergers and acquisitions. The integration broker receives the message and passes it to the message flow. which contain the message routing and transformation logic. ranging from simple piping of data between connected applications to complex synchronization of data from various sources.WBI Message Broker Application A Message Flow Adapter ASBO ASBO Adapter Application B Figure 4-16 WBI Message Broker Architecture The WebSphere Business Integration brokers run time contains message flows. and the geographical locations and time zones of the applications. Note: In contrast to the WebSphere Business Server Foundation and the WebSphere InterChange Server. The business object is placed as a message in the correct XML-based wire format on a WebSphere MQ queue for the integration broker. suppliers. the WebSphere Business Integration brokers use only application Specific business objects (ASBOs) and not generic business objects (GBOs). WebSphere Business Integration Message Broker is used to: Securely connect business applications with those of business partners.

4. Solution approaches and technology options 93 .neutral + .3.5 Integration server selection The WebSphere Business Integration product family offers different integration servers which provide specific strengths in certain integration areas. Available integration servers are: WebSphere Business Integration Server Foundation (WBISF) WebSphere InterChange Server (WICS) WebSphere Business Integration Message Broker (WBIMB) Table 4-1 illustrates the strengths of the different integration servers and can be used to make a decision for a particular integration requirement. Table 4-1 Integration brokers characteristics matrix Characteristic MQSeries® prevalent environment Java oriented environment Next generation platform Make use of prebuild collaborations Business process integration/modelling Standards based solutions Web Services based solutions Human interaction High availability High volume message exchange Dynamic message routing Platform availability Unix Linux zOS + + + + o o + + + WBISF o + + o + + + + + o o WICS o + o + + o + o + o o WBIMB + o o o o o o o + + + Legend: o .strength Chapter 4.

4 WebSphere Business Integration in the SAP environment This section describes the features and functions of the two SAP related WebSphere Business Integration Adapters: WebSphere Business Integration Adapter for mySAP. The WebSphere Business Integration Adapter for mySAP.com WebSphere Business Integration Adapter for SAP Exchange Infrastructure 4.com The WebSphere Business Integration Adapter for mySAP.4. The adapter contains following components: Connector (the run-time component) Connector Configurator tool Business Object Designer tool SAP Object Discovery Agent (SAP ODA) 94 WebSphere Business Integration for SAP .4.com is a software suite consisting of a run-time component and development and administration tools (see Figure 4-17 on page 95).1 WBI Adapter for mySAP.com uses the SAP Java Connector to access SAP R/3 systems.

BAPIs. The SAP ODA is a very innovative component of the WebSphere Business Integration Adapter for mySAP. white board style The Connector Configuration tool is used to create and modify the connector’s configuration. Solution approaches and technology options 95 . which represent SAP R/3 interfaces.com. The Business Object Designer tool generates Business Objects. it uses the SAP Object Discovery Agent (ODA). and RFCs. The run-time component of the WebSphere Business Integration Adapter for mySAP. It connects to the SAP R/3 system and queries it for metadata to get the appropriate interface definitions.Connector Configurator Connector Application Specific Component Connector Framework SAP R/3 WBIMB WICS WAS XML Schema SAP ODA Business Object Designer Figure 4-17 WBI Adapter for mySAP.com is the so called connector.com architecture. This information is used by the Business Object Designer to construct the fairly complex objects which are required at run time. like IDocs. It defines which business objects the connector supports and the connector properties. which consists of: The connector framework An application specific component Chapter 4. Therefore.

The communication type between the adapter and the integration broker is one of following: WebSphere MQ Java Messaging Service (JMS) Internet Inter-ORB Protocol (IIOP) (Object Request Broker (ORB)) The connector can be deployed on different physical locations. the adapter can make use of the Extension Module and the CrossWorld Station in R/3. as illustrated in Figure 4-18.The EDI Data Handler The application specific component comprises different modules. Also.com .detailed view The connector communicates with the SAP R/3 back end via RFC and it uses the SAP Java Connector (SAP JCo) API. Each of these modules address a particular SAP R/3 interfaces type. 96 WebSphere Business Integration for SAP . WBI Adapter ALE Module ABAP Extension Module BAPI Module Hierarchical Dynamic Retrieve Module RFC Server Module Interface iDoc sent to SAP Return “IDoc received” ASBO sent to SAP SAP Application Business Logic Database Asynchronous:IDoc processed Database updated Status to ALE table Converted to IDoc Converted to Dynamic Object Synchronous Status returned ASBO returned w/object key Advanced Event Notification Management/Troubleshooting Tools BAPI processed synchronously with object key feedback Retrieve from SAP tables using standard SAP API SAP Program calls WBI synchronously and waits for response Figure 4-18 Modules of the WBI Adapter for mySAP. as illustrated in Figure 4-19 on page 97.

it does not require any modification or adjustments in the accessed SAP back-end system. Solution approaches and technology options 97 . The discovery agent interprets the interface of a BAPI. this invokes the SAP Remote Function Call (RFC) library to connect to the SAP Gateway of the respective application server. The module uses the standard SAP Java Connector (SAP JCo) to establish a connection to the SAP system. SAP Object Discovery Agent (ODA). generates business object definitions that support BAPIs. BAPI Module The BAPI Module (see Figure 4-20 on page 98) is a Java written subcomponent of the adapter that enables the integration broker to make direct calls to a SAP R/3 application server. Option 4: The connector runs on a server outside the local area network. As an SAP JCo client application. maps its parameters to the business object Chapter 4. Option 3: The connector runs on a own or third party server. The BAPI Module can access any remote enabled function module in the SAP system and represents a non-invasive integration approach.Figure 4-19 Deployment topology Option 1: The connector runs on the SAP R/3 application server. The business object generation utility. Option 2: The connector runs on the integration server.

The main difference to the BAPI Module is that a dedicated RFC module is used to access SAP metadata of existing SAP tables. it supports calls from the integration broker to the SAP application. The module also uses the standard SAP JCo to establish a connection to the SAP system. The HDR Module supports flat tables as well as nested table constructs. The ODA queries the metadata of the respective database tables and populates the business object automatically. Using the SAP ODA in conjunction with the Business Object Designer. WebSphere Business Integration Adapter SAP Java Connector . it supports calls from the integration broker to the SAP application. 98 WebSphere Business Integration for SAP . The Business Object Designer supports the generation of business objects representing SAP tables using the HDR module. The HDR Module is unidirectional.The BAPI Module is unidirectional. and adds the application-specific information for each attribute. All application specific information is filled in to avoid circumstantial manual actions. it is relative easy to create business objects from complex interface structures.attributes. It is also a Java produced subcomponent of the adapter that enables the integration broker to processes hierarchical or flat business objects retrieved from a SAP R/3 application server.JCo SAP RFC Library SAP Back-end System Business Object Handlers RFC Connection SAP Gateway BAPIs RFCs Figure 4-20 BAPI Module Hierarchical Dynamic Retrieve Module The Hierarchical Dynamic Retrieve (HDR) Module (Figure 4-21 on page 99) is very similar to the BAPI Module described above.

Like the other modules of the adapter. Several settings during the wizard driven object creation process tell the Business Object Designer that a RFC Server specific business object handler has to be created. the RFC Server module can also make use of the Business Object Designer and the SAP ODA to rapidly create new business objects. The target SAP system must be configured to accept the RFC Server application on the gateway. Solution approaches and technology options 99 . which poll the application for events. it supports calls from the SAP application to the integration broker.WebSphere Business Integration Adapter SAP Java Connector . This is done by setting up a RFC destination to define the entry point in the SAP Gateway the RFC Server Module is using. As with any SAP JCo RFC Server application. Chapter 4. The RFC Server Module is unidirectional. this invokes the SAP Remote Function Call (RFC) library to connect to the SAP Gateway of the respective application server. The module uses the standard SAP JCo to implement an RFC Server connection to the SAP system. It enables the integration broker to receive business objects from SAP applications that support RFCs. it “pushes” or sends events from the SAP application to the integration broker. Because the RFC Server Module acts as a server to the SAP application. This behavior is very different from other modules.JCo SAP RFC Library SAP Gateway SAP Backend System Business Object Handler RFC Connection RFC_READ_TABLE Figure 4-21 HDR Module RFC Server Module The RFC Server Module (see Figure 4-22 on page 100) acts as a server to the SAP application. The generated Java classes are stored in a different directory than the Java classes created with the other modules.

The SAP application can call the integration broker and the integration broker can call the SAP application. The ALE module uses MQ Series queues for Transaction ID (TID) and IDocs management to guarantee a consistent one time delivery of exchanged data objects. The integration broker sends a integration broker business object to the SAP connector. the ALE Module implements an asynchronous communication style that adds another level of complexity. because it supports bidirectional communication. The connector converts the business object to a table format compatible with the SAP Intermediate Document (IDoc) format. 4.WebSphere Business Integration Adapter SAP Java Connector . The connector uses RFCs to the ALE interface of the SAP R/3 system to pass the IDoc data. 3. Communications from the broker to the SAP system is often called Request processing. The connector checks for subscriptions when processing the data from SAP to the connector. The SAP RFC libraries are used in both directions and the connection endpoint at the SAP system is the SAP Gateway. 100 WebSphere Business Integration for SAP . 2.Integration Broker to SAP 1.JCo RFC Server Specific Business Object Handlers SAP RFC library Register Program ID Multi-threaded RFC Connection SAP Backend System SAP Gateway RFC RFC RFC Client client client Figure 4-22 RFC Server Module ALE Module The ALE Module (see Figure 4-23 on page 101) is much more complex than the BAPI Module and the RFC Server Module. The business object’s data represents a processing request to the connector. Request processing . In addition. while calls initiated by the SAP system are called Event processing.

JCo SAP RFC Library RFC Connection RFC WebSphere Business Integration Adapter ALE Event Processing Business Object Handler SAP Gateway SAP Backend System Register Program ID Multi-threaded RFC Connection RFC RFC client Client WebSphere MQ JMS Connection Figure 4-23 ALE Module ABAP Extension Module The ABAP Extension Module (Figure 4-24 on page 104) enables an integration broker to send business objects to and receive events from SAP R/3 applications. guaranteeing once-only delivery of data from SAP to the connector. 3. ALE Request Processing Business Object Handlers SAP Java Connector . The Java component of the module Chapter 4. The connector converts the data to a integration broker business object before sending it to the integration broker. The connector receives data representing an application event from SAP in IDoc table format via a RFC Server listener thread. 4. Solution approaches and technology options 101 . The connector uses a two-step process with a TID to handle each event storing events in WebSphere MQ queues persistently. Each event from SAP is considered a transaction and persisted in MQSeries queues.Event processing . The connector updates the status of the processed event. The ALE Module is best used for asynchronous communications. whereas the main part is the ABAP portion.SAP to Integration Broker 1. The module consists of components written in Java and ABAP. 2.

Opens an RFC connection to the SAP application using the SAP RFC library and the SAP Gateway. These functions are accessible via SAP transactions and screens. are still easy to maintain and to upgrade. The ABAP components consist of various SAP application function modules. which is using the enhanced functions of this module.utilizes the standard SAP Java Connector (SAP JCo) to establish a connection to the respective SAP system. Some of these ABAP components are developed and delivered as part of the adapter and some are native to every SAP installation. database tables. Polls the SAP application for events. 102 WebSphere Business Integration for SAP . These elements handle the event delivery and business object request processes initiated by the Java component. The CrossWorld Station is a set of R/3 transactions for: Analyzing of adapter logs Monitoring of the adapter Developing inbound and outbound business object definitions Defining event distribution settings Configuring the SAP system to work with the ABAP Extension Module Java components The handle the event delivery and event business object request processes. The ABAP components are delivered in connector transport files to be loaded into an SAP application. and programs. Handles requests from the integration broker and passes the requests to an ABAP component of the connector. The communication is done using a standard RFC connection to the SAP Gateway and executing respective function modules of the ABAP component of the ABAP extension module. The central entry point to access the base functions of the ABAP components of the ABAP Extension Module is called CrossWorld Station. CrossWorld Station After the implementation of the transport files. This guarantees that the SAP system. The ABAP components are all located in a separate name space and do not override any SAP standard objects. the full functionality of the ABAP Extension module is available.

Chapter 4. or delete business objects. which takes the detected event and adds it to an event table in SAP. The main feature of the ABAP Extension Module is its advanced event detection mechanisms and business object handlers that manipulate the most common objects from SAP. change.ABAP components These elements handle the event delivery and business object request processes initiated by the Java components. The adapter enables real-time retrieval of complex objects from SAP or requests to create. and returns the unique ID of any created object. Detects. triggers. The adapter notifies you of the success and status of the object transaction request. The ABAP Extension Module can make use of four mechanisms to detect an event in the SAP application: Code enhancements Batch programs SAP Business Workflow Change Pointer Event detection is the process that is used to verify that an event was generated in the SAP application. In contrast to the other modules of the WebSphere Business Integration Adapter for SAP. The event detection mechanism calls an event trigger. and stores events in the event table. The objects can be retrieved and manipulated to and from SAP in real time. Solution approaches and technology options 103 . Handles business object requests from the Java component by calling the appropriate function modules designed to handle a particular business object type and verb. the ABAP Extension Module is an invasive integration approach. Handles event requests and their subsequent return (event status update) from the Java component. and they can be also retrieved through both request/reply and publish/subscribe models.

Using JMS supports a transactional message exchange between the two integration brokers and is very well suited for business scenarios where data is changed at the downstream back-end systems.JCo RFC Connection ABAP Handlers Tables Tables SAP RFC library SAP Gateway WebSphere Business Integration Adapter Event Notification Poll for Events Function RFC client Modules CWLD Namespace RFC Connection SAP Backend System Figure 4-24 ABAP Extension Module 4. JMS based WBI adapter for SAP XI The WebSphere Business Integration adapter for SAP Exchange Infrastructure V1.2 WBI Adapter for SAP Exchange Infrastructure The adapter that is introduced in this section provides an integration of SAP Exchange Infrastructure into a WebSphere Business Integration scenario. The latter has been released recently and thus is only described in this chapter.4. This adapter is available in a version that supports JMS and one that uses Simple Object Access Protocol (SOAP) over Hypertext Transfer Protocol/extension of HTTP running under SSL (HTTP/HTTPS) as the underlying communication technology. 104 WebSphere Business Integration for SAP .Request Processing SAP Java Connector .0 allows the WebSphere Integration broker to asynchronously exchange business objects with SAP Exchange Infrastructure using a WebSphere MQ based JMS implementation (Figure 4-25 on page 105).

can be integrated as a web service into a WebSphere Business Integration scenario. works similar to the request processing described before. SOAP based WBI adapter for SAP XI The WebSphere Business Integration adapter for SAP Exchange Infrastructure V2. regardless of its downstream EIS. or Chapter 4.0 supports Simple Object Access Protocol (SOAP) over HTTP/HTTPS as the underlying communication technology for requests as well as event processing. In this way: SAP Exchange Infrastructure. WBI_XI_Queue SAP XI XML Message XI_WBI_Queue WBI Adapter for SAP XI Business Object WBI Integration Broker XML Data Handler XML ODA Figure 4-25 Architecture of WBI adapter for SAP XI V1. in which the adapter receives XML messages from SAP Exchange Infrastructure and relays them to the Integration Broker. Both kinds of processing are metadata driven. meaning that major format conversions and message routing functions are defined by meta-objects. the JMS layer makes the appropriate calls to open a queue session and routes the message into a defined WebSphere MQ queue. the adapter calls the XML data handler to convert the business object into an XML message according to a business object type the adapter is associated with.0 On receiving a business object as a request from the InterChange Server. Thereafter. Message generation and checking within the adapter is driven by a business object type that is generated by the XML Object Discovery Agent (ODA) from a corresponding SAP IDoc structure. Solution approaches and technology options 105 . Event processing. The messages sent or received by the adapter are compatible with the IDoc-XML format that is defined by a SAP IDoc structure.The WebSphere adapter for SAP Exchange Infrastructure supports requests as well as event processing.

If the interface description is determined by SAP Exchange Infrastructure. usually using a Web infrastructure. containing a request and optional response.0 In event processing. also of the type of the business objects that are exchanged between the collaboration and the adapter. using WebSphere InterChange Server as the integration broker. Based on this. For this scenario. both WebSphere InterChange Server and SAP Exchange Infrastructure must agree on an interface description of the Web service in the Web Services Description Language (WSDL) format. Using the SOAP data handler. V2. which defines the structure of the SOAP messages and. SAP XI Server SAP XI SOAP Adapter Enterprise Web Server Internet Internet WBI Adapter for SAP XI 2. and Internet in between. For event as well as request processing. and returns it to the collaboration. the business objects are converted into SOAP messages before they are sent to the SOAP adapter of SAP Exchange Infrastructure. a collaboration is exposed as a Web service that is called by the SOAP adapter of the SAP Exchange Infrastructure. the adapter calls the SOAP data handler to convert the message to a business objects. On receiving a response to the request. The collaboration delivers the service call as a top-level business object.0 Collaboration Business Object WBI InterChange Server SOAP over HTTP/HHTPS SOAP Data Handler SAP XI ODA Figure 4-26 Architecture of WBI Adapter for SAP XI. the collaboration can be developed to send 106 WebSphere Business Integration for SAP . thus. a collaboration issues a Web service provided by the SAP Exchange Infrastructure. the collaboration within the InterChange Server must be developed accordingly. firewall.A WebSphere Business Integration scenario can be exposed as a Web service to the SAP Exchange Infrastructure. as well as fault business objects. except that the direction of processing is changed. to the adapter. such as a Web server. the WebSphere adapter provides the SAP XI Object Discovery Agent (SAP XI ODA) that converts a given WSDL definition into a top-level business object type. The steps to be executed in this case are similar to the one described for request processing. In request processing. Figure 4-26 depicts the architecture of this adapter.

or receive business objects to or from the adapter of the generated type. Solution approaches and technology options 107 . For this purpose. The interface description may also be derived from a given collaboration within an event processing scenario. the InterChange Server provides the WSDL Configuration wizard. either within a request or a event processing scenario. which generates a WSDL file for an existing collaboration. Chapter 4.

108 WebSphere Business Integration for SAP .

All rights reserved. Appropriate integration broker and integration adapter selection is rationalized in the design of each Use Case solution.5 Chapter 5. process flow. as designed for all four Use Cases. © Copyright IBM Corp. and data flow. 109 . “Business case scenario” on page 53. 2004. from the standpoint of system architecture. Solution design This chapter defines a technical solution to the business case scenario described in Chapter 3.

Flexible. Table 5-1 Use Case characteristics Use Case Use Case 1 Master data synchronization & Event notification Integration type Application connectivity Purpose Synchronize the master data of two sales systems. The process involves preexisting business applications and provides an approval mechanism. Seamless. Use Case 2 Internal purchase requisition process Process choreography & User integration Allow internal employees to submit purchase requisition requests via a standard process. Each defined Use Case addresses a particular business problem in different business areas. Provides the opportunity to dynamically adjust the system linkages. Table 5-1 categorizes the Use Cases with regard to the integration characteristics and the key technical challenges. Incorporates various systems on different distributed platforms. the technical challenges differ from case to case. and asynchronous event notification. Enable the SD System of Company A to access the inventory system of Company B to get reliable product availability data. real-time integration of remote business logic. performing. “Business case scenario” on page 53. Notify subscribed business components of occurrences. Supports long-running.5. These areas are discussed here in more detail. Use Case 3 Automate inventory availability verification Process automation Use Case 4 Maintain customer data across system boundaries Inventory availability validation Create a new and easy to use interface for the sales team to add new customer records into the customer data repository. 110 WebSphere Business Integration for SAP . such as a placed sales order. Provides system access via the standard groupware infrastructure.1 Business process analysis The business process requirements of the merged enterprise are specified in detail in Chapter 3. Distributes business data to the relevant back-end systems. Embraces human interaction within the process. asynchronous processes. For this reason. Four Use Case definitions were made in that chapter. Technical challenges Consistent and reliable product master data synchronization between ERP systems.

the compulsory business continuity requirements and financial constraints limit the possibility to rebuild from scratch. Another more practical reason for not taking this approach is the attempt to fuse both environments and obtain a crossbreed that has the strengths of both former business models. 5. a tactical solution to efficiently combine both former companies’ infrastructures is to establish a unified technical model by leveraging the existing technical assets in the previously two separate environments.2 Design principles and methodology Various design principles and methodologies are steadily under discussion on how to do business integration most effectively. However. The following principles are followed in the technical design: Reuse existing infrastructure where and when possible to avoid cost of additional hardware and software. Satisfy corporate security requirements for secure applications. and new business processes must be implemented on top of the current infrastructure incorporating existing business functions. Externalize the common business logic via well-defined interfaces. Chapter 5. not rebuild.5. Existing assets have to be analyzed and reused as much as possible. and guidelines. Apply corporate technical standards. Identify business logic that can be exposed as shared services and make them available as componentized modules. Reuse. business logic. Minimize the impact to existing client applications. Solution design 111 . One ideal approach is to establish a new technical model for the merged enterprise and to completely replace the heterogeneous environments that consists of mixed technologies in the former companies. Force consistency with industry standard architectures to build an open platform that is prepared for future growth.3 System context As discussed in the preceding sections. best practices. Ensure that a newly-created process function is a collaboration of loosely coupled subsystems.

this is the eCommerce portal server and the Supply Chain System. The external access to this system is only permitted for dedicated system that must be located in the DMZ.1 Logical model of Company A Figure 5-1 shows the logical architecture of Company A. All other departmental servers reside in the internal trusted network.3. It is protected by a firewall that filters any external accesses to the system except for standard Web browser based activities.5. The Sales and Distribution (SD) system that contains the core business logic and confidential corporate data is located in the secure internal networks segment. which is based on a relational database and tightly integrated with the SD system. Firewall Firewall Salesman Thin Client Salesman Rich-client App Portal Server Customer Thin Client J2EE Sales & Distribution System (A) ERP Customer Data Repository Supply Chain System Supplier Rich-client App External Network DMZ ERP DBMS Internal Trusted Network Figure 5-1 Logical architecture of Company A The eCommerce Portal server is hosted in the Demilitarized Zone (DMZ) and serves customer requests. The internal sales team also uses a Web browser interface to communicate with the Portal Server from the internal trusted network and a rich client application to access the SD system. In this particular scenario. 112 WebSphere Business Integration for SAP . The SD system stores customer master data in a customer data repository.

The SD system is tightly integrated with the Inventory System and the Customer Data Repository. Consequently. all sales orders are handled by the sales team internally. Therefore. Firewall Employee Groupware Client Salesman Rich-client App Sales & Distribution System ERP HR System ERP Procurement System ERP Policy System J2EE Messaging System SA J2EE P Inventory System DBMS Customer Data Repository Assembly Plant Custom Domino Supplier Rich-client App 1 Supplier Rich-client App 2 External Network Internal Trusted Network Figure 5-2 Logical architecture of Company B In contrast to Company A.5.2 Logical model of Company B The logical architecture of Company B is illustrated in Figure 5-2. A salesman uses a rich client application to access the Sales & Distribution (SD) system. Company B has no electronic sales channel. There is no direct interaction between any external network and sales system.3. all servers are allocated inside the internal trusted network. Solution design 113 . Chapter 5.

Company A Assets . to expand the existing business workflows and to realize new processes. 5. Firewall Legend . Suitable integration technologies are used to link systems together. Any supplier uses an appropriate rich client application to communicate with various system components of the Assembly Plant and exchange purpose-built business data.As described. These applications are self-contained and related to certain business areas.New Processes Portal Server (A) Customer Thin Client J2EE Sales & Distribution System (A) SAP UC 1a UC 1b Sales & Distribution System (B) SAP Procurement System (B) SAP UC 2 Salesman Thin Client Firewall Salesman Rich-client App Employee Groupware Client UC 2 Internal UC 2 Purchase Requisiti on System UC 2 UC 2 Inventory System(B) Messaging System (B) J2EE HR System (B) SAP Policy System (B) J2EE UC 3 DBMS UC 4 Customer Data Repository (A) Supply Chain System(A) Supplier Rich-client App External Network ERP DBMS Assembly Plant (B) Custom Internal Trusted Network Customer Data Repository (B) Domino DMZ Figure 5-3 Logical architecture of merged enterprise 114 WebSphere Business Integration for SAP .New Assets . with the addition of the former Company B’s assets. Due to the fact that the secure environment of former Company A is matured and well-established for external interactions. and the supply chain process is automated. the unified architecture primarily takes this infrastructure as the baseline.3. The logical architecture of the merged enterprise is shown in Figure 5-3.Company B Assets . A multiplicity of applications are hosted on distributed servers of the internal groupware infrastructure. They can be accessed by the groupware clients that are installed on all employee workplaces.3 Unified model of merged enterprise The unified model basically combines both infrastructures to form a single virtual environment. the Assembly Plant is not one system. but an arrangement of various best-of-breed and custom applications that were historically grown together.

Use Case 2 is a brand-new process for internal employees to use to leverage the existing groupware application to access a new Internal Purchase Requisition System to submit procurement requests. The detailed rationalization of specific technology selected is provided in each Use Case discussion in the sections that follow. and handle the new business processes. system-level requirements. Each Use Case addresses a special business integration demand. a suitable system architecture is put in place. which are described in 5. Based on the business requirements and technical values of various options discussed in the foregoing chapters. Based on the requirements. Data center operation. Figure 5-4 on page 116 displays the system architecture. Use Case 4 enables Sales & Distribution System A to retrieve the customer data residing in Customer Data Repository B. 5. with limited authentication and authorization. All new servers are deployed to the same subnetwork for testing. and zoning are not under consideration.4 System architecture To simplify the environment setup and deployment in this demonstration. Network and storage requirements are also not considered. New system and integration servers are added to the model. such as monitoring. and scalability are not taken into account in the system architecture. system management. As the unified environment inherently comprises diverse technologies and platforms. to extend the current business processes for the whole family of products from both companies. The selected integration solution for each Use Case must fulfill different functional and technical requirements.4. Chapter 5. backup. such as load-balancing. “System architecture” on page 115. Solution design 115 . a comprehensive integration solution is needed to meet a broad range of integration demands. Use Case 1b is an order event notification from Sales & Distribution System B to A. failover via redundancy. Use Case 1a deals with the product data synchronization from the Sales & Distribution System A to B.The new processes of the four Use Cases are depicted as dotted lines in the diagram. WebSphere Business Integration platform is chosen as the foundation of the integration solutions in all four Use Cases. Use Case 3 handles the product availability validation from the Sales & Distribution System A to the Inventory System.

together with SAP XI Server on ITSOF. Likewise.New Assets .New Processes Firewall Salesman Thin Client Salesman Rich-client App Procurement System (B) Sales & Distribution System (B) SAP SAP Employee Groupware Client UC 2 ITSOD UC 2 UC 2 HR System (B) SAP Policy System (B) J2EE ITSOA Portal Server (A) Customer Thin client J2EE Sales & Distribution System (A) SAP UC1 WBI Message Broker WBI Server Foundation UC 2 UC 2 Inventory System(B) Messaging System (B) J2EE ITSOB UC 3 WBI InterChange Server ITSOF SAP XI Server Customer Data Repository (A) DBMS UC 3 DBMS UC 4 ITSOC WBI InterChange Server UC 4 Supply Chain System(A) Supplier Rich-client App External network ERP Assembly Plant (B) Custom Customer Data Repository (B) Domino Internal Trusted Network DMZ Figure 5-4 System architecture of merged enterprise Five new servers are introduced to the infrastructure to implement the four Use Cases: ITSOA is a WebSphere Business Integration Message Broker system for Use Case 1. ITSOB runs WebSphere InterChange Server for Use Case 3. 116 WebSphere Business Integration for SAP . the WebSphere InterChange Server is also installed on ITSOC for Use Case 4. Table 5-2 on page 117 lists the relevant integration servers in the system architecture.Company A Assets .Firewall Legend . ITSOD hosts WebSphere Business Integration Server Foundation for Use Case 2.Company B Assets .

Solution design 117 .Table 5-2 Integration servers in merged enterprise Server ITSOA WBI Message Broker Server ITSOD WBI Server Foundation Purpose Product master data replication Order event notification Process choreography for internal purchase requisition process HR System Policy Repository Procurement System Messaging Server Human interaction ITSOB WebSphere InterChange Server ITSOC WebSphere InterChange Server ITSO_XI SAP XI Server Inventory availability validation SD System Company A Inventory System Interaction SD System Company A SD System Company B Customer master data replication SAP XI Server Customer Data Repository Company B Customer data routing to SAP back-end system SD System Company A WebSphere InterChange Server on ITSOC Chapter 5.

New Assets .New Processes ITSOA Portal Server (A) Customer Web Browser J2EE SAP WBI SAP Adapter Firewall Salesman Web Browser Salesman Rich-client App SAPGUI Procurement System (B) RFC Sales & Distribution System (B) SAP ABAP/ALE Employee Groupware Client Web Browser HTTP ITSOD RFC HR System (B) BAPI SAP BAPI WBI SAP Adapter Sales & Distribution System(A) RFC ALE/ RFC Server WBI Message Broker ALE SAP WBI SAP Adapter WBI Server Foundation WBI SAP Adapter RFC SOAP/HTTP SOAP/HTTP ITSOB WBI SAP Adapter RFC WBI Inter Change Server Inventory System(B) JDBC DBMS ITSOC Messaging System (B) J2EE Policy System (B) J2EE WBI JDBC Adapter SAP XI IDOC Adapter RFC ITSOF SAP XI JMS Adapter Supplier Rich-client App External network Supply Chain System(A) ER P DMZ Customer Data Repository (A) DB MS SAP XI Server MQ WBI Inter Change Server WBI Domino Adapter WBI XI Adapter IIOP Assembly Plant (B) cust om Customer Data Repository (B) Domino Internal Trusted Network Figure 5-5 Communications diagram The communications mechanisms for all new processes are summarized in Table 5-3.Company A Assets .Company B Assets . Table 5-3 Communications mechanisms Use Case UC 1 Integration server type WBI Message Broker Technologies / Adapters applied SAP ALE for product data replication WBI SAP adapter for order notification WBI SAP adapter WBI JDBC adapter WBI SAP adapter UC 2 UC 3 WBI Server Foundation WebSphere InterChange Server 118 WebSphere Business Integration for SAP .5 Communications and connectivity The intersystem communications and application connectivity for the four Use Cases are displayed in Figure 5-5. Firewall Legend .5.

Use Case 1a The high level business process flow is shown in Figure 5-6 on page 120. but independent. The available technology options are subsequently evaluated and rationalized to select the best option that fits the particular circumstance.Use Case UC 4 Integration server type WebSphere InterChange Server and SAP XI Server Technologies / Adapters applied WBI Domino adapter WBI XI adapter SAP XI IDoc adapter SAP XI JMS adapter 5.Solution overview This section provides a component-level design for Use Case 1. 5.1 Process flow Here we discuss the process flow. Solution design 119 . processes. the solution detail is defined with descriptions of modules and components used. which contains two related. Finally.6. Chapter 5. The process flows are defined from a technical perspective.6 Use Case 1 .

Fail Error status code Create SAP Database End Figure 5-6 Business process flow for Use Case 1a The step-by-step procedure is described as follows: 1. Input data validation and redundancy check Succeed Success Status code SAP System creates a data record.Start Employee enters new product master data. A salesman creates a new product record by entering product information via a SAP graphical user interface (GUI) application. 120 WebSphere Business Integration for SAP . SAP System creates a data record. IDoc generated by System to represent the new product record. Create SAP Database Notify Notify SAP System receives Idoc. Integration System delivers message.

The recipient SAP system validates the incoming IDoc data. The Integration System transforms the necessary data segments and routes the data chunk to the other SAP system.2. A success status code is sent back to the Integration System. an error status code is sent to the Integration System. In case the validation fails. 9. 6. 4. 8. The SAP system creates an Intermediate Documents (IDocs) based on the product data and dispatches it to the Integration System. 3. The GUI App sends the data via the Remote Function Call (RFC) to the SAP system. 7. Use Case 1b The high level business process flow is displayed in Figure 5-7 on page 122. 5. Solution design 121 . the IDoc is process in this SAP system and a new product record is created and stored in the database. Otherwise. which first validates the input data submitted by the user. The SAP system creates a data record that is stored in the SAP database. Chapter 5.

4. which first validates the input data submitted by the user. A salesman creates a new sales order of the new products added to the system in Use Case 1a by entering order information via a SAP GUI application. 2. the Integration System creates a empty data structure and send it back to the SAP System. Create SAP Database System creates an event notification object. 122 WebSphere Business Integration for SAP . The SAP system generates a trigger that represents the occurrence of the new order creation. The GUI App sends the data via RFC to the SAP system. 3. End Figure 5-7 Business process flow for Use Case 1b The step-by-step procedure is explained in the following list: 1. SAP System creates a sales order record. The SAP system creates a data record that is stored in the SAP database. The event is dispatched to the Integration System. 5.Start Employee enters a sales order. Once notified. 6. notify Integration System receives the notification.

Solution design 123 . As a result of the technical evaluation. If the message size is fairly large. the primary challenge is the application connectivity and information exchange.7. but there are subtle differences. The key advantages of ALE are standard structure and operation. and support a broader range of diverse platforms. An IDoc is a container of information in a predefined (structured ASCII) format. Use Case 1a Based on the business process requirements described in the preceding section. The primary candidate options are: InterChange Server Server Foundation Message Broker All these technologies are useful for asynchronous integration purposes. embedded auditing and troubleshooting functionality in SAP. The SAP System populates this data structure with valid values retrieved from the database. Consequently ALE is selected as the adapter to be used in this design. These data needs a reliable transport mechanism like message queues. IDocs are the preferred file format used by SAP R/3 to exchange data with foreign systems. In this situation. In addition. Message Broker shows superior performance. whereas the Message Broker is suitable for application connectivity. 5. Application Link Enabling (ALE) uses Intermediate Documents (IDocs) to pass information in and out of SAP. there are several technology choices available to implement this workflow.2 Technology selection Here we discuss technology selection. Furthermore. The populated data structure is sent to the Integration System. Message Broker can dynamically route the message to appropriate receivers. InterChange Server and Server Foundation fit well into the process integration.6. Chapter 5. it has been determined that the Message Broker is the best choice in this particular circumstance. 8. Message Broker can access the message queues directly in the message-oriented environment. The product data structure contains a fairly large chunk of data. and broad acceptance as the interface technology for SAP to third parties.

or delete an object.6. The arabic numbers describe Use Case 1a and the Latin numbers describe Use Case 1b. The objects can be retrieved and manipulated to and from SAP in real time. The adapter enables real-time retrieval of a complex object from SAP or a request to create. The primary candidate options are: ABAP Extension Module Custom-built code The ABAP Extension Module provides rich functionality within SAP and is therefore considered invasive.Use Case 1b Based on the business process requirements described in the preceding section. a few technology options become available to implement this notification. it takes longer and needs extra effort and skills.3 Solution details The solution to these two workflows in this Use Case is illustrated in Figure 5-8 on page 125. Figure 5-8 on page 125 is used to clarify. It is the only adapter module that supports polling and can be used in conjunction with all other adapter modules to provide this functionality. 5. in which order. change. Even though the custom-build approach works. ALE connectors are installed on both SAP systems for Use Case 1a. The adapter notifies you of the success and status of the object transaction request. The Extension Module has advanced event detection mechanisms and business object handlers that manipulate the most common objects from SAP. whereas the ABAP Extension Module is utilized in Use Case 1b. and returns the unique ID of any created objects. the various steps are triggered in the Use Case. and they also can be retrieved through both request/reply and publish/subscribe models. 124 WebSphere Business Integration for SAP . The WebSphere Business Integration Message Broker is used as the Integration System. so the ABAP Extension Module is the best solution to this problem.

The WebSphere Business Integration system processes the data: a. The connector receives the event notification and sends an empty business object to the ABAP Extension Module in SAP. The connector transforms the IDoc into a business object and sends it to the broker. A sales person creates a product in SAP via the SAP GUI. 2. Use Case 1b i. As soon as a sales order of a product in SAP is created. an event notification is sent to the connector. Solution design 125 . b. iii.com Adapter 4 i ii iv 3b 3c ALE 5 ABAP Extension Module iii SAP R/3 Figure 5-8 Solution detail for Use Case 1 Use Case 1a 1. As soon as the product is added in SAP‘s product repository.com Adapter WebSphere Business Integration Message Broker mySAP. 5. SAP populates the business object with the sales order data and sends the populated business object back to the connector. The broker transforms the business object structure and routes it to the second connector. Chapter 5. 3. c. The connector sends the IDoc to SAP using ALE.1 SAP R/3 ALE 2 3a SAP GUI mySAP. ii. SAP sends the product data in the form of an IDoc to the connector using ALE. The connector transforms the business object into an IDoc. 4. SAP adds the material to its product repository.

1 Process flow The high level business process flow is illustrated in Figure 5-9 on page 127. The connector passes the business object to the message broker for further processing. 5. 5.7 Use Case 2 . Finally. the solution detail is defined with descriptions of modules and components used. 126 WebSphere Business Integration for SAP . The process flow is discussed from a technical perspective.7.iv.Solution overview This section provides a component-level design for Use Case 2. The available technology options are subsequently evaluated and rationalized to select the best option that fits this particular circumstance.

Messaging System Send notification End Figure 5-9 Business process flow for Use Case 2 Chapter 5. Policy System Approval needed? No Yes Human interaction to approve or reject the request via a Web browser. Solution design 127 . Procurement System No Prepare process feedback. Request approved? Yes Place order to the Procurement System.Start Employee logs in for authentication and authorization to access the Internal Purchase Requisition System via a Web browser. Human Resource System Retrieve employee data Retrieve approval policy. Validate input data and retrieve additional information. Employee enters data of an internal purchase order request via a Web browser.

Once authenticated. Otherwise. monitor. the request is routed to the respective person for authorization. There are several products available which offer this functionality and can cover the named functional and technical requirements.The step-by-step procedure is described as follows: 1. 8. WebSphere MQ Workflow supports long-running business process workflows as they interact with systems and people. 9.7. the requester is notified about the rejection. otherwise. 3. It is best suited to analyze. and improve critical business processes that execute in WebSphere MQ prevalent environments. An employee logs in via a Web browser for authentication and authorization to access the Internal Purchase Requisition System.An e-mail notification is subsequently sent to the requester. 5. The Internal Purchase Requisition System retrieves additional employee data from the Human Resource System. Modifications of the actual business process have to be done fairly simple by just adopting the business flow. It is capable of coordinating business process activities that span multiple distributed applications. 10. The Internal Purchase Requisition System confirms that the request is received and processed. 4. all the different business logic providers must be accessed in a general way to enable the process to run regardless of the enterprise service it is utilizing. 2. together with the purchase order number generated if the order was successful. 128 WebSphere Business Integration for SAP . If the request is authorized. 6.2 Technology selection The internal order application is a process driven business integration solution that requires asynchronous and synchronous invocation of existing enterprise services. 7. the order is placed to the enterprise procurement system. WebSphere Interchange Server is a business integration solution for process integration and enterprise application connectivity. the order is placed to the Procurement System. A persistency layer is required to store the process status and progress. If the requested goods do not need any approval. On the process level. 5. The Internal Purchase Requisition System communicates with the Policy Service to retrieve approval policy for the requested goods. The authorizer reviews the request details and decide to accept or reject the request. the employee enters data for a purchase request and submits the order in the browser.

WebSphere Business Integration Server Foundation extends and integrates existing IT assets using a next generation integration platform optimized for building and deploying composite applications. This enables WBISF to use all scalability.There are a huge number of predefined and proven collaborations already available out of the box that can be reused to speed up implementation. including drag-and-drop tools to visually define the sequence and flow of business processes Strong support for activities that require human interaction Standard based support for business processes that integrate with back-end systems Builds on the latest J2EE standards based WebSphere Application Server platform Native support of J2EE and Web Service integration technology The following business process requirements make WBISF the best choice to implement this business process: Strong focus on user interaction and integration Incorporation of existing business processes to create a new business process Existing business processes can be exposed using clearly defined interfaces Support of synchronous and asynchronous communication styles Exchanged data is fairly small .event flow instead of payload processing Requirement to have a standards based and future-proof integration platform Persistency of business processes is implemented by using WebSphere MQ as a queueing mechanism. Solution design 129 . reliability. Major features and benefits are: Support for a standard based model and a grammar for describing the behavior of a business process based on interactions between the process and its partners Comprehensive development environment. and security features of WebSphereMQ out of the box. The run-time architecture is multi-tiered and consists of following components: Business process container: Run-time environment for standard based business processes Adapter framework: Run-time environment for standards based back-end connectivity adapters Development environment: Eclipse based visual tooling Chapter 5.Collaborations graphically define end-to-end processes.

This enables business processes running on WebSphere Business Integration Server Foundation to connect to a huge range of business components without extensive effort by using the WebSphere Application Server built in Web Service support.3 Solution detail This section describes the steps from a component view: 1.Communication layer: WebSphere MQ connecting process container and adapter framework The business process container resides on the application server and can make use of all distribution and clustering mechanisms of WebSphere Application Server. 2. the application places a JMS message into the WebSphere MQ request queue. 5. 3. This makes them a good choice to avoid frequent adjustments in the integrating applications that typically surround an ERP system. An employee uses a standard Web browser to log in to an application and to create an internal purchase order requisition. SAP BAPIs are the standard way to invoke business logic. and puts the response back to the WebSphere MQ response channel. executes the call into the back-end system. SAP guarantees that BAPI interfaces remain unchanged over certain software releases. The back-end connectors are distributable and scalable across different systems and communicate with the process container using WebSphere MQ. The connector takes the message based request. This queue is observed by the WebSphere Adapter for mySAP. 6. business processes can also invoke an enterprise service directly using Web Service technology. The application uses the employees input to execute a synchronous Web Service call at the policy system to find out if the ordered product requires an approval. 4. The application picks up the response and stores the employees mail address information for further processing. 130 WebSphere Business Integration for SAP . The application immediately provides an acknowledgment to the employee and starts the process flow. 5. executes the respective BAPI call in the human resource system. The policy service returns a Boolean value. In addition to the mediate connector approach.7. In the next activity. The connector receives message based requests and translates them into the SAP specific RFC protocol. and puts the response back to the queue in a message format.com that connects to the human resource system (SAP). which is located within SAP ERP systems in a synchronous style.

The approver uses a standard Web browser to log in to the application. the message subject. executes the respective BAPI call in the human resource system. 9. This queue is observed by the WebSphere Adapter for mySAP. 5. A Web Service call is made to a Notification service.The process is halted until the approver processes the staff activity either by accepting or by rejecting the request. and puts the response back in the queue in a message format. the application places a JMS message into the WebSphere MQ request queue. and puts the response back in the queue.If the product requires an approval. Solution design 131 .If the approver accepts the order. the application places a JMS message into the WebSphere MQ request queue. This queue is observed by the WebSphere Adapter for mySAP.Solution overview This section provides a component-level design for Use Case 3.The status of the internal order is updated and the originating employee can review the processed order.com that connects to the procurement system (SAP).The application picks up the response and stores the employee information for further processing. 14. the solution detail is defined with descriptions of the modules and components used. the final step is that the application takes the collected and stored information and sends an notification. 17. executes the respective BAPI call in the human resource system.If the approver rejects the order. The application picks up the response and stores the employee information for further processing. the status field of the order is set to Order rejected. The application recognizes the approver and displays all open work items. 15. The process flow is discussed from a technical perspective. Finally. 16.7. The connector takes the message based request. Chapter 5. a work item is created and displayed in the approver’s work list. If no approval is required. 10. 11. The available technology options are subsequently evaluated and rationalized to select the best option that fits this particular circumstance. and the message body as input parameters and sends an e-mail to a predefined SMTP host.The connector takes the request.com that connects to the procurement system (SAP). This service takes the mail address of the recipient. 8.8 Use Case 3 . 13. 12.In any case.

Query Request Inventory System Integration system delivers result via adapter. System receives Available to promise result data.8. The employee uses the SAP 132 WebSphere Business Integration for SAP .1 Process flow The high level business process flow is shown in Figure 5-10. Integration system retrieves data using adapter. End Figure 5-10 Business process flow for Use Case 3 The step-by-step procedure is described as follows: 1. An employee wants to know if a plant has part X available and how many of part X is available at the location to fill an order. Employee views result in SAP system. System calls remote Available to promise logic. Start Employee enters search criteria in SAP system. Integration system receives function call using adapter.5.

WebSphere InterChange Server allows for the integration of disparate systems with relatively little or no knowledge of the inner workings of the two systems and is best suited to smaller IT shops and businesses wanting swift. 3. The employee then reviews the results of the request from the SAP GUI application without knowledge of all the integration that has occurred behind the scenes. This integration needs to be transparent to the user. The solution that lends itself most to this criteria is the WebSphere InterChange Server. nor does the integration require a great degree of customization. The external inventory availability system locates the item and returns the response to SAP via the integration mechanism implemented. WebSphere Business Integration Message Broker can route messages among queues and re-route as needed based on message contents. Solution design 133 . and support a much broader range of platforms.GUI application to determine the availability of the item. but also allows the additional flexibility to make a front end for managing this process. does not require a significant learning curve. and transparent integrations. the employee fills in the material availability search mask. The WebSphere InterChange Server allows for swift implementation of this integration. nor a great IT investment to implement. The primary candidates to implement this integration are: WebSphere InterChange Server WebSphere Business Integration Server Foundation WebSphere Business Integration Message Broker All of these technologies allow the synchronous processing of the desired integration scenario. and/or to customize the integration greatly. WebSphere Business Integration Server Foundation allows the same level of integration. there are several technology choices available to implement this integration. complete. 4. 2. work with large messages very quickly. does not require the overhead of a customized interface.2 Technology selection Based on the integration requirements of the business process described in the previous section. Via the GUI application. SAP generates a search request and routes it to an external inventory availability system via an integration mechanism.8. Choosing the WebSphere InterChange Server for this integration also allows for the transparent integration Chapter 5. 5.

such as Peoplesoft Enterprise. 134 WebSphere Business Integration for SAP .of other standardized systems.8.3 Solution detail Figure 5-11 on page 135 shows a detailed flow of what occurs in this solution using the WebSphere InterChange Server. Siebel. 5. or other similar systems as the business needs change going forward.

End Figure 5-11 Solution detail for Use Case 3 The step-by-step procedure is described as follows: 1. Employee views result in an SAP system. mySAP. Query Request IBM DB2 Query Result JDBC Adapter transforms IBM DB2 response to business object for WICS.Start Employee enters search criteria in SAP system. The employee uses the SAP Chapter 5. Request SAP System mySAP. WebSphere Interchange Server transforms data.com Adapter transforms request to business object for WICS. An employee wants to know if a plant has part X available and how many of part X is available at the location to fill an order. Response SAP System JDBC Adapter transforms business object to query request for IBM DB2. Solution design 135 . WebSphere Interchange Server transforms data.com Adapter transforms business object to response for SAP.

1 Process flow The process flow of Use Case 4 consists of the following steps (Figure 5-12 on page 137): 1. The available technology options for realizing the process flow are evaluated subsequently. converted from a IBM DB2 object. 3. Thereby. The mySap. new or changed documents within that Lotus Domino database are detected and transmitted subsequently to an SAP R/3 system that hosts the common customer data repository. The employee then reviews the results of the request from the SAP GUI application without knowledge of all the integration that has occurred behind the scenes. 4. The resulting information is passed back through the adapter.GUI application to determine the availability of the item. Using Integration technology. 6. 7. The JDBC WebSphere Business Integration Adapter takes the IBM DB2 Object result and transforms it into a request to IBM DB2 for the desired availability information. 2.9 Use Case 4 . The WebSphere InterChange Server then uses a predefined map to transform this business object into a IBM DB2 object expected by the JDBC WebSphere Business Integration Adapter. Finally. SAP generates a search request and routes it to the predefined RFC server destination that has been defined as the target for the search. 5. back into an SAP business object. 3. Via the GUI application. 2.com WebSphere Business Integration Adapter receives the request and transforms it to a business object understood by the WebSphere InterChange Server. 5. The data entered are stored as a document within a dedicated Lotus Domino database. a solution detail is defined with descriptions of modules and components used. 5. back through the SAP Adapter.9. the employee enters the material availability search. A client representative enters the contact data for a new customer using a Lotus Notes client.Solution overview This section provides a component-level design for Use Case 4. A high level view on the process flow is given first. and finally to SAP. the Lotus 136 WebSphere Business Integration for SAP .

Solution design 137 . Response SAP System JDBC Adapter transforms business object to query request for IBM DB2. Start Employee enters search criteria in SAP system.Domino documents get converted into the SAP defined IDoc structure. WebSphere Interchange Server transforms data.com Adapter transforms request to business object for WICS. Employee views result in SAP system. Query Request IBM DB2 Query Result JDBC Adapter transforms IBM DB2 response to business object for WICS. Request SAP System mySAP. End Figure 5-12 Business process flow for Use Case 4 Chapter 5. before being stored there. mySAP.com Adapter transforms business object to response for SAP. WebSphere Interchange Server transforms data.

In addition.9. Integration technology. the WebSphere InterChange Server is selected for the implementation of Use Case 4. Use Case 4 is about integration of the two enterprise information systems Lotus Domino and SAP R/3. should be accessed only by using the SAP Exchange Infrastructure. WebSphere InterChange Server. it does not understand the format of Lotus Domino databases. The adapter for Lotus Domino can be attached to all the different Integration Servers that have been described in the previous sections. SAP Exchange Infrastructure supports XML-based message exchange between SAP and non-SAP systems. The two integration brokers. Selecting WebSphere MQ as the underlying transport mechanism not only matches the asynchronous nature of the document centric interaction. but also permits you to update the customer data repository with transactional support. Finally. Since the focus of this business process is the integration of disparate systems with a moderate amount of data exchange. However. and SAP Exchange Infrastructure are connected by means of WebSphere MQ queues. Both integration brokers access these queues using their corresponding JMS adapter. Technology selection for this Use Case is driven by the following major requirements: The SAP R/3 back-end system. It understands how to detect new or updated documents within a given Lotus Domino database and supports the bidirectional exchange of these documents between a Lotus Domino Server and a WebSphere Business Integration Server. the WebSphere Business Integration adapter for Lotus Domino is very well suited.2 Technology selection As shown in Figure 5-12 on page 137. which deploys Application Link Enabling (ALE) as the underlying technology. and vice versa. which hosts the customer data repository.5. must be able to transform the native formats of Lotus Notes databases into SAP IDoc structures. an IDoc adapter is selected to connect the SAP Exchange Server with the SAP R/3 back-end system. 138 WebSphere Business Integration for SAP . the Integration technology must be able to automatically detect and handle events that are triggered by the creation or update of documents within the Lotus Domino database. which sits between the Lotus Domino Server and the SAP system. For this purpose. nor can it detect events originating at a Lotus Domino server.

as depicted in Figure 5-13 on page 140.9. Chapter 5. Solution design 139 .3 Solution detail Based on the results of the technology selection. the business process in Figure 5-12 on page 137 is refined.5.

A client representative enters the contact data for a new customer using a Lotus Notes client.Start Client representative enters data of a new customer contact. Lotus Domino Event Listener WebSphere Business Integration Adapter for Lotus Domino WebSphere Interchange Server WebSphere Business Integration Adapter for SAP Exchange Infrastructure WebSphere MQ SAP Exchange Infrastructure Integration Server SAP Exchange Infrastructure IDoc Adapter SAP Exchange Infrastructure JMS Adapter SAP System SAP system creates a customer data record. 140 WebSphere Business Integration for SAP . End Figure 5-13 Solution detail for Use Case 4 1.

This XML message is written to a WebSphere MQ queue using the JMS based WebSphere Business Integration Adapter for SAP Exchange Infrastructure. At the WebSphere InterChange Server. 10. 3. The conversion requires no mapping. 5. the Domino documents is converted into an XML message that conforms to a given SAP IDoc type. 8. the adapter retrieves the corresponding Domino document to the WebSphere InterChange Server. it puts an event document into a event table. 5. the IDoc is received by the SAP R/3 system where it is delivered to an internal process for storing customer data.2. Chapter 5.Finally. When an Event Listener process detects new or updated documents within that Lotus Domino database. Figure 5-14 on page 142 shows the simplified architecture. The IDoc adapter converts the XML message into an IDoc and sends them to SAP R/3 using ALE. The WebSphere Business Integration adapter for Lotus Domino polls the event table. The SAP Exchange Infrastructure Integration Server forwards the XML message to the SAP Exchange Infrastructure IDoc adapter. since WebSphere InterChange Server is responsible for providing messages in an adequate format. 7. The adapter retrieves new XML messages from the queue and delivers them to the SAP Exchange Infrastructure Integration Server. 6.10 Related technology used in this book This book only covers a subset of the hole IBM WebSphere Business Integration and SAP technology. If a new event is detected. The WebSphere MQ queue is polled by the SAP Exchange Infrastructure JMS adapter. 4. 9. Solution design 141 . The data entered is stored as a document within a dedicated Lotus Domino database.

142 WebSphere Business Integration for SAP . The book also shows how to extend the WebSphere Business Integration environment with our own services in the Business Application Service. The book shows how to integrate SAP on the Application (ABAP personality) layer and on the process (Exchange Infrastructure) layer.Business Performance Management Services Process Services Enterprise Service Bus Business Business Application Application Services Services Application and Data Access Services Business Application and Data Services Enterprise Applications and Data Infrastructure Services Figure 5-14 Simplified architecture The Development Tools are used to create custom processes and services that use the Enterprise Service Bus to talk with the adapters.

and detailed nuts-and-bolts implementations of the solution designed in the early chapters. © Copyright IBM Corp. as well as best practices and lesson learned.Part 3 Part 3 Business scenario solution implementation This part contains a system installation and configuration specification. 2004. Part 3 is composed of Chapters 6 to 11. 143 . All rights reserved.

software prerequisites. “Use Case 1: WBIMB using WBI Adapter for mySAP.com and JDBC” on page 465 discusses how to implement the solution designed for Use Case 3. WebSphere Business Integration Server Foundation using WebSphere Business Integration Adapter for mySAP. 144 WebSphere Business Integration for SAP . “Use Case 3: WICS using WBI Adapter for mySAP. Integration of SAP XI with WebSphere Business Integration InterChange Server. “Best practices and lessons learned” on page 643 provides the tips and hints obtained in the design and implementation of the sample business application as well as discussions on the trends and related emerging-technology. WebSphere Business Integration Message Broker using WebSphere Business Integration Adapter for mySAP. Chapter 9. Chapter 8. Chapter 11.com” on page 327 describes how to implement the solution designed for Use Case 2. Chapter 10. WebSphere InterChange Server using WebSphere Business Integration Adapter for mySAP. hardware specifications. server installation.com. It contains an environment overview.com. “Use Case 4: Integration of SAP XI with WBI InterChange Server” on page 555 discusses how to implement the solution designed for Use Case 4.com and Java Database Connectivity. Chapter 7. “Use Case 2: WBISF using WBI Adapter for mySAP. and common configurations. “Environment setup” on page 145 specifies the run-time environment for the business scenario.Chapter 6.com” on page 173 shows how to implement the solution designed for Use Case 1.

“Use Case 4: Integration of SAP XI with WBI InterChange Server” on page 555. and Chapter 10. The subsequent chapters also provide some details on the installation and configurations of the individual Use Cases.com” on page 327. “Use Case 2: WBISF using WBI Adapter for mySAP. 145 . Environment setup This chapter gives a general overview about the environment setup for the implementation of the four Use Cases described in Chapter 7.6 Chapter 6. © Copyright IBM Corp.com” on page 173. “Use Case 3: WICS using WBI Adapter for mySAP. 2004. All rights reserved. “Use Case 1: WBIMB using WBI Adapter for mySAP. Chapter 8.com and JDBC” on page 465. Chapter 9.

com -RFC Server module WebSphere Business Integration Adapter for XI X X X X X X X X X X X X X X X X X #1 #2 #3 X #4 X X X X X 146 WebSphere Business Integration for SAP .12 WebSphere Business Integration Adapter Framework WebSphere Business Integration Adapter for mySAP.6.1.com -ALE module WebSphere Business Integration Adapter for mySAP. a variety of integration technologies are applied in the solution design of the four Use Cases.com -ABAP Extension module WebSphere Business Integration Adapter for mySAP.0.1 Technology matrix As discussed in the previous sections. Table 6-1 summarizes the relevant technologies utilized in each Use Case respectively. Table 6-1 Technology matrix Use Case / Software WebSphere InterChange Server WebSphere Business Integration Message Broker WebSphere Business Integration Server Foundation WebSphere MQ DB2 SAP JCO 2.10 SAP JCO 2.com -Hierarchical Dynamic Retrieve module WebSphere Business Integration Adapter for mySAP.com -BAPI module WebSphere Business Integration Adapter for mySAP.

0.3 ITSOA Windows2000 Adapter for mySAP.de.com ITSO_XI Windows2000 WebSphere InterChange Server 4.com AIX 5. Figure 6-1 illustrates the setup of the run-time environment to realize the overall system architecture.5 Adapter for mySAP.2.2.3.2 Adapter for JDBC SAP R/3 SAP R/3 4.3.3 Adapter for mySAP.2.1 Lotus Domino 6.1 MQ 5. “Solution design” on page 109.0.5 ITSOD Windows2000 Adapter for mySAP.2 SAP SAPR/3 R/3 4.com WebSphere Business Integration Server Foundation 5.3.sapbts.2 DB2 8.0.1 MQ 5.6c MQ 5. sapbts08.2 Run-time environment overview The system architecture is specified in Chapter 5. Environment setup 147 .Use Case / Software WebSphere Business Integration Adapter for JDBC WebSphere Business Integration Adapter for Domino WSADIE #1 #2 #3 X #4 X X 6.2.2 DB2 8.5 Adapter for XI SAP XI 3.5 Figure 6-1 Run-time environment diagram Adapter for Lotus Domino ITSOC Windows2000 Chapter 6.de.ibm.7 ITSOB Windows2000 ITSOE Windows2000 DB2 8.com AIX 4.0 WebSphere InterChange Server 4.0.com siccserv.3.1 MQ 5.com WebSphere Business Integration Message Broker 5.0.0.5 DB2 8. The components and modules for each Use Case are also discussed in detail in that chapter.isicc.ibm.

1 FixPack 5 1.0.1 FixPack 5 2.3.5 8.com ITSOB UC 3 Windows 2000 WebSphere InterChange Server WebSphere MQ DB2 WebSphere Business Integration Adapter for mySAP.2.2 2.com WebSphere Business Integration Adapter for JDBC ITSOC UC 4 Windows 2000 WebSphere InterChange Server WebSphere MQ DB2 WebSphere Business Integration Adapter for XI WebSphere Business Integration Adapter for Domino Version Pro 5.4.2.0.5 8.0.5.0 Pro 4.2 5.2.3 5.0 1.1 FixPack 5 5.5 8.1 148 WebSphere Business Integration for SAP .Table 6-2 lists the primary software packages and products installed on individual run-time machines and in which Use Cases they are used.3.0.3.2 Server 4.5.2 5.4 5.2. Table 6-2 Run-time environment components Host name ITSOA Use Case UC 1 Software Windows2000 WebSphere Business Integration Message Broker WebSphere MQ DB2 WebSphere Adapter Framework WebSphere Business Integration Adapter for mySAP.

Environment setup 149 .3 Common installations The following common software is required for the new servers to be used in the run-time environment: DB2 database engine WebSphere MQ This next section describes the common installation of these two particular products.0.1 FixPack 5 6.0 Pro 3.4 5. Chapter 6. 2.0.3. & 4 UC 1 AIX® SAP R/3 AIX SAP R/3 sapbts08 6.5.com Version Pro 5.6c ITSO_XI UC 3 Windows 2000 SAP NetWeaver Exchange Infrastructure siccserv UC 1.2 ITSOE UC 2 &4 Windows 2000 IBM DB2 Lotus Domino Pro 8.3 4.7 4.2 4.5 2.2 5. 3.0 5.Host name ITSOD Use Case UC 2 Software Windows 2000 WebSphere Business Integration Server Foundation WebSphere MQ WebSphere Adapter Framework WebSphere Business Integration Adapter for mySAP.

150 WebSphere Business Integration for SAP . Figure 6-2 IBM DB2 Launchpad 3. The DB2 Setup Launchpad is displayed (Figure 6-2).1 with FixPack 5 Installation of IBM DB2 is illustrated next.1 Installing IBM DB2 UDB Version 8. Install IBM DB2 Universal Database™ Enterprise Server 8. select DB2 UDB Enterprise Server Edition and click Next.6.1 1. Select Install Products. Launch the setup.1 2. When prompted to choose the product to be installed (Figure 6-3 on page 151).3.exe for IBM DB2 Universal Database Enterprise Server Edition 8.

Environment setup 151 . the Welcome to the DB2 Setup wizard screen is displayed.Figure 6-3 Product Installation window 4. After the Preparing to Install screen. Chapter 6. as illustrated in Figure 6-4 on page 152. Click Next.

Figure 6-4 IBM DB2 Setup Wizard 5. as illustrated in Figure 6-5 on page 153 and click Next. 152 WebSphere Business Integration for SAP . Accept the terms of the License Agreement.

Environment setup 153 . as in Figure 6-6 on page 154 and click Next. Chapter 6.Figure 6-5 License Agreement window 6. Select the Custom option.

If you wish to save the configuration settings for future use on another DB2 installation. – Choose not to install Business Intelligence. – Choose not to install Getting started. – Choose not to install the Application Development tools. 8. The choices made for this DB2 installation are just the items necessary for this project. There are many choices that can be made on the feature installation screen (Figure 6-7 on page 155). Choose Install DB2 Enterprise Server Edition on this computer. Click Next. then also choose Save the settings in a response file.Figure 6-6 Installation type selection window 7. – Click Next. – Change the install directory to C:\SQLLIB. 154 WebSphere Business Integration for SAP .

Environment setup 155 . Figure 6-8 APPC Support Warning window Chapter 6. On the warning screen. click OK.Figure 6-7 Installation Features window 9. as in Figure 6-8.

– Also check the box Use the same user name and password for the remaining DB2 services. and then click Next. the user ID must have administrative rights on this machine.On the user administration screen. Figure 6-9 Language Selection window 11. 156 WebSphere Business Integration for SAP . as in Figure 6-9.10. If the user is a domain user. – If a local user that does not exist is used. DB2 creates the user if provided with sufficient administrative privileges. as in Figure 6-10 on page 157. enter the user information for the administration server.Select the languages you wish to install. – Click Next.

Click Next on the Set up the administration contact list screen. Environment setup 157 .Figure 6-10 User ID configuration window 12. Chapter 6. as in Figure 6-11 on page 158.

On the warning screen in Figure 6-12 on page 159. 158 WebSphere Business Integration for SAP . 14.Choose to Create the DB2 instance and click Next.Figure 6-11 Set up the administration contact list window 13. click OK.

Environment setup 159 . as in Figure 6-13 on page 160.Figure 6-12 IBM DB2 instance creation window 15. Chapter 6.Click Next on the Configure DB2 instances screen.

160 WebSphere Business Integration for SAP .Select Do not prepare the DB2 tools catalog on this computer and click Next (see Figure 6-14 on page 161).Figure 6-13 IBM DB2 instance configuration window 16.

Click Next. Chapter 6.Figure 6-14 IBM DB2 tools catalog preparation window 17.Select Defer the task until after installation is complete on the Specify a contact for health monitor notification screen (see Figure 6-15 on page 162). Environment setup 161 .

as in Figure 6-16 on page 163. Click Next. 162 WebSphere Business Integration for SAP .Select Defer the task until after installation is complete on the Request satellite information screen.Figure 6-15 Health monitor notification contact window 18.

Specify the location to store your response file. and then click Finish. Environment setup 163 . as in Figure 6-17 on page 164.Figure 6-16 Satellite system information window 19. review your current settings. Chapter 6.

Figure 6-17 Install options review window 20.Ensure that the installation is complete (see Figure 6-18 on page 165). 164 WebSphere Business Integration for SAP .

Chapter 6.Figure 6-18 Installation in progress 21. Environment setup 165 .At the Setup is complete screen (see Figure 6-19 on page 166). click Finish.

click Install Product (see Figure 6-20 on page 167). 166 WebSphere Business Integration for SAP . At the IBM DB2 Setup Launchpad. 2. Launch setup.Figure 6-19 Setup completion window Installation of FixPack 5 for DB2 1.exe to begin the installation.

Figure 6-20 IBM DB2 launchpad 3. Choose to install DB2 UDB Enterprise Server Edition and then click Next (see Figure 6-21 on page 168). Environment setup 167 . Chapter 6.

then do so. Depending on the current state of DB2. shut your DB2 down safely from the services panel. – If your DB2 is in a state where it is safe to kill all of the processes. otherwise. or from the command line. click Yes. Figure 6-22 Process warning window 168 WebSphere Business Integration for SAP . – If it is safe to do shut down your DB2 forcibly. the installation may present a list of DB2 processes that are running (see Figure 6-22).Figure 6-21 Product installation window 4. then start this installation again after choosing No.

as illustrated in Figure 6-24 on page 170. After the Preparing to Install screen. The installation should begin.5. Figure 6-23 IBM DB2 setup wizard 6. Environment setup 169 . Click Next. the Welcome to the DB2 Setup wizard screen is displayed (see Figure 6-23). Chapter 6.

Figure 6-24 Installation progress window After the installation finishes. 170 WebSphere Business Integration for SAP . the screen in Figure 6-25 on page 171 should appear.

click the CD-ROM option.3. The CD autoruns. Therefore.3. and then click OK.2 Installing WebSphere MQ V5. In the launchpad. WebSphere MQ must be installed.3 Server is supplied on a CD in the product package. CSD04 is not supplied in the product package. it must be downloaded from the IBM Web site and installed separately. Click Finished. When prompted. then double-click MQLaunch.3. to configure WebSphere Business Integration Message Broker. insert the correct CD. browse to the CD. To install WebSphere MQ V5.exe.Figure 6-25 Installation completion window 7. follow these steps: 1. Chapter 6. 6. Insert the CD that is labelled IBM WebSphere MQ for Windows Version 5. 2.3 with CSD04 All the messaging functionality in WebSphere Business Integration Message Broker is provided by WebSphere MQ. Environment setup 171 . The WebSphere MQ Installation Launchpad opens. If the CD does not autorun. in Windows Explorer. WebSphere MQ V5.

In the WebSphere MQ Installation Launchpad. 6. refer to the WebSphere MQ product documentation and Readme.3 CSD04. However. Click the link to download the most recent FixPack for WebSphere MQ for Windows V5.html This is the IBM Web site from which WebSphere MQ CSDs (also known as FixPacks) can be downloaded. In the first table on the web page. 172 WebSphere Business Integration for SAP . For further instructions. 6. read the accompanying documentation and release notes. Select CSD05. In Services. To install WebSphere MQ V5.ibm. Check that all the WebSphere MQ software and network prerequisites are installed. which is labelled IBM WebSphere MQ (formerly IBM MQSeries). The WebSphere MQ Support page opens. 2. then continue through the download and registration process to download the setup files. click Launch WebSphere MQ Installer to start installing WebSphere MQ. 5. The Services dialog opens. Click Start → Settings → Control Panel → Administrative Tools → Services. A progress bar is displayed while the service stops. Stop all WebSphere MQ services: a. follow these steps: 1. – Install the JMS Messaging feature. 4. when prompted.3. click on the WebSphere MQ for Windows link. previous FixPacks can still be downloaded. select the following options: – Custom installation. right-click IBM MQSeries. then click Stop. In a Web browser.3. This page displays only the most recent FixPack for WebSphere MQ. go to the following URL: http://www-306. A JRE can be installed after WebSphere MQ has been installed.com/software/integration/mqfamily/support/summary/ind ex. Work through the installer and. 4. 3. The FixPack and Interim Fixes page opens. Note that the WebSphere MQ Installation Launchpad cannot detect whether a Java Runtime Environment (JRE) has been installed. In Step 3 of the WebSphere MQ Installation Launchpad. 5. When the setup files have been downloaded. start the Help Center and read the Release Notes. then start the installer and install the CSD. b.

7 Chapter 7. This chapter contains the following topics: Operational model Installation of WebSphere Business Integration components Configuration of WebSphere Business Integration components Configuration of SAP R/3 for WebSphere Business Integration Development of WebSphere Business Integration components Deployment of WebSphere Business Integration components Running the scenario © Copyright IBM Corp.com.com This chapter describes the installation and implementation of SAP R/3 integration scenarios using the WebSphere Business Integration Message Broker and the WebSphere Business Integration Adapter for mySAP. 173 . 2004. Use Case 1: WBIMB using WBI Adapter for mySAP. It gives the reader a primer for configuring SAP R/3 to work with the ALE Module and the ABAP Extension Module of the adapter. All rights reserved.

Sends the IDoc to the SAP R/3 ALE interface. Converts the business object into a IDoc. Transfers the business object to the inbound queue of the destination connector.1 Operational model This Use Case contains two parts: MaterialSynchronization scenario (Figure 7-1 on page 175) This scenario describes the integration of SAP R/3 systems using the WebSphere Business Integration Message Broker and the ALE Module of the WebSphere Business Integration Adapter for mySAP.7. 6. Converts the IDoc into an application specific business object. Passes the business object to the message flow for processing. Puts the business object into the outbound queue of the sending connector. 2.com. Receives an IDoc (message type MATMAS) from the SAP R/3 ALE interface. OrderEventNotification scenario (Figure 7-2 on page 176) This scenario describes the integration of SAP R/3 systems using the WebSphere Business Integration Message Broker and the ABAP Extension Module of the WebSphere Business Integration Adapter for mySAP. The following steps describe the flow of the business processes comprising this Use Case: 1.com. 7. 3. 4. 174 WebSphere Business Integration for SAP . 5.

Chapter 7. 2.com 175 . Use Case 1: WBIMB using WBI Adapter for mySAP. SAP populates the business objects with values from the sales order.Figure 7-1 Operational model: MaterialSynchronization scenario The second part of this Use Case is described with the following flow: 1. 3. 4. The business integration system receives an event notification from the ABAP Extension Module in SAP R/3 as soon as a sales order is created in transaction va01. The business integration system sends an empty business object into SAP. SAP sends the filled business object to the business integration system for further processing.

1 IBM Agent Controller IBM WebSphere Business Integration Message Broker IBM WebSphere Business Integration Adapter Framework IBM WebSphere Business Integration Adapter for mySAP. To obtain a fully functional installation of WebSphere Business Integration Message Broker. all of the prerequisite software must be installed: Microsoft Windows 2000 Service Packs Microsoft Data Access Components (MDAC) V2.Figure 7-2 Operational model: OrderEventNotification scenario 7.7 IBM WebSphere MQ IBM Java Runtime Environment IBM DB2 V8.2 Installation of WebSphere Business Integration components This section describes how to perform an installation of WebSphere Business Integration Message Broker and its prerequisite software. WebSphere Business Integration Adapter Framework.com 176 WebSphere Business Integration for SAP . and WebSphere Business Integration Adapters.

0.7 with Service Pack 1 or V2.1 with FixPack 2 Microsoft Data Access Component (MDAC) V2.0.4 Chapter 7. Used for database connections and other forms of data connections.com 177 .7. and business applications.2 with FixPack 9 or V8. Used to store information about the broker domain configuration.2 IBM WebSphere Business Integration Message Broker IBM WebSphere Business Integration Adapter Framework V5. Facilitates messaging between the Configuration Manager.2. Used by the IBM Agent Controller installer and WebSphere MQ. the brokers.3 V2.7 with Service Pack 1a or V2. Table 7-1 Prerequisites: WebSphere Business Integration Message Broker Prerequisite software Microsoft Windows 2000 Version Service Pack 3 What the software is for Required if running Windows 2000. the prerequisite software shown in Table 7-1 must be installed. and for WebSphere Business Integration Message Broker to function correctly. Used by the message flow debugger in WebSphere Business Integration Message Broker.3.3 with CSD04 or CSD05 IBM WebSphere MQ IBM Agent Controller V5. Java Runtime Environment (JRE) IBM DB2 Universal Database Enterprise Server Edition V1. Required. Use Case 1: WBIMB using WBI Adapter for mySAP. The Service Pack is needed for security. Used for message transformation and routing. such as data sources over the network. and about resources deployed to the broker.1 Plan the installation To obtain a fully functional installation of WebSphere Business Integration for this Use Case. Framework where WBI Adapters can be plugged in.8 V5.1 V7.

Go to the following URL: http://www.com Version V5. Table 7-2 shows the product installation directories of use case 1. If you are running Windows XP. Table 7-2 Product installation directories Directory C:\SQLLIB C:\WBIMB Component IBM DB2 IBM WebSphere Business Integration Message Broker. Service Pack 3 or later must be installed. 7. To install a Microsoft Windows Service Pack: 1.Prerequisite software IBM WebSphere Business Integration Adapter for mySAP.com 178 WebSphere Business Integration for SAP . Most of the prerequisite software products required for the Windows system are supplied in the product package. 2. Software that is not supplied on CDs can be downloaded from the Internet.2. Service Pack 1 or later must be installed. The Service Packs fix bugs in Microsoft Windows 2000 that can prevent WebSphere Business Integration Message Broker from functioning properly.windowsupdate.2 Install Microsoft Windows 2000 Service Packs If you are running Microsoft Windows 2000 on the computer. and provide greater security. Open a Web browser. and Microsoft Data Access Components IBM WebSphere Business Integration Adapters IBM WebSphere MQ Java Runtime Environment C:\WebSphereAdapters C:\WebSphereMQ C:\JRE131 Tip: It is recommended to avoid installation directory names that include spaces.5 What the software is for Specific WBI Adapter to connect SAP back-end systems with WBI infrastructures. inclusive IBM Agent Controller.

3 Install a Java Runtime Environment Although the WebSphere Business Integration Message Broker pre-installed Launchpad does not check for a Java Runtime Environment (JRE) on the computer. To install a JRE: 1. MDAC for database connections is needed. The correct version of MDAC is supplied in the product package. Chapter 7. The WebSphere MQ Installation Launchpad opens. JRE V1.com 179 .The Service Pack can be installed directly from the Windows Update site.3. Use Case 1: WBIMB using WBI Adapter for mySAP.1 with FixPack 5 This installation is covered in 6.1 with FixPack 5” on page 150. 5. “Installing IBM DB2 UDB Version 8.4 Install IBM DB2 UDB V8. 2.1.exe.7 with Service Pack 1. 7. click the + next to Supported Java Runtime Environment 1.0 is supplied with WebSphere MQ V5. Upgrade the installed version of MDAC to Version 2. Work through the installer to complete the installation of the JRE. The installation starts.3 or later to expand that section of the page. Switch to the folder where the installation files are located. on the Software Prerequisites page.3. 3. Follow the directions on the Web site. Double-click MQLaunch. 7.2. Click WebSphere MQ CD. including Open Database Connectivity (ODBC).2. It enables applications to access data from various data storage sources.4.3.7 Microsoft Data Access Components (MDAC) is a collection of DLLs and associated component resources to support a number of different APIs. The IBM 32-bit SDK for Java 2 V1.5 Install Microsoft Data Access Component (MDAC) V2. In the WebSphere MQ Installation Launchpad.1 or above must be installed to run the IBM Agent Controller installer.2. 4. 7.

3 with CSD04” on page 171. and publish/subscribe features. 7.1 or above must have been installed.7 Install IBM Agent Controller The Agent Controller is a daemon process that enables client applications to launch host processes and interact with agents that coexist within host processes. 2. 7.exe to start the installation.exe to start the installation. Before installing IBM Agent Controller. 180 WebSphere Business Integration for SAP .3. select the following options: – When specifying the location of the JRE. “Installing WebSphere MQ V5. The broker provides message routing. 3.exe file.8 Install WebSphere Business Integration Message Broker In this Use Case. the business integration system consists of an integration broker and connectors that allow SAP R/3 systems to exchange data through the coordinated transfer of information in the form of business objects. When prompted.) Double-click MDAC_TYP.To install MDAC V2. The Agent Controller provides a means for extending application behavior so that information regarding the application's execution can be externalized and then collected either locally or remotely. To install IBM Agent Controller: 1.2.3. 7.2. Switch to the folder where the installation files are located. Switch to the folder where the installation files are located.7 with Service Pack 1: 1. The installation starts. – Disable security. Double-click Setup. which contains the java. a Java Runtime Environment (JRE) V1.2. transformation.6 Install WebSphere MQ V5. The IBM Agent Controller setup files are supplied in the product package. Installation of IBM Agent Controller is necessary if the flow debugger in WebSphere Business Integration Message Broker is required to debug message flow applications. 2. browse to the bin directory.3 with CSD05 This installation is covered in 6. This section describes how to install a WebSphere Business Integration Broker.2.

If this dialog is not displayed. then start the installer directly from folder where the installation files are located. select the language in which the installer will be displayed. Click Setup.com 181 . 4. 3. and then click OK (see Figure 7-3). Ensure that an user with administrative privileges. Install When the installer was started. it might be hidden behind another window on the desktop. Click Next to continue. Switch to the folder where the installation files are located. Read and respond to the messages that are displayed on the WebSphere Installation page.exe to start the installer. a command line window opens while the Java Virtual Machine initializes. Chapter 7. in the Installer dialog. Do the following steps: 1. 2. Use Case 1: WBIMB using WBI Adapter for mySAP. Do the following steps: 1. Click on the Launch IBM WebSphere Business Integration Brokers Installation link at the bottom of the WebSphere Installation page. Figure 7-3 The Installer language selection dialog The first page of the installer is displayed (see Figure 7-4 on page 182). but not the user Administrator. is used for the installation.Start the installer If you are not using the pre-install launchpad as a guide through the installation process. The installer starts. 5. When prompted.

then click on the Install Guide button). and then click Cancel. Confirm that the required migration tasks are completed (see Figure 7-5 on page 183). – To continue with the installation. 182 WebSphere Business Integration for SAP .Figure 7-4 Installer welcome page 2. refer to the most recent version of the Install Guide (open the launchpad. and then click Next. – To cancel the installation and perform the required migration tasks. click Yes. If migrating from a previous version of the product. click No.

com 183 . and then click Next. click I do not accept the terms in the license agreement.Figure 7-5 The migration prerequisites page 3. – If the Software License Agreement is not accepted. The installation cannot continue. Use Case 1: WBIMB using WBI Adapter for mySAP. and then click Cancel. The next page of the installer is displayed. Read the Software License Agreement (see Figure 7-6 on page 184) and click one of the following options: – Accept the Software License Agreement by clicking I accept the terms in the license agreement. Chapter 7.

184 WebSphere Business Integration for SAP .Figure 7-6 The Software License Agreement page 4. click Next. When an alternative location is selected. click Next. – To install the product in the default location. click Browse. – To browse to an alternative location. Decide where to install WebSphere Business Integration Message Broker (see Figure 7-7 on page 185).

Use Case 1: WBIMB using WBI Adapter for mySAP. click Custom. click Typical.Figure 7-7 The Install location page 5. Select the type of installation to be performed (see Figure 7-8 on page 186): – To install all of the components that are required.com 185 . Select this option only when you are familiar with the product components. – To select specific components. Chapter 7. This option is recommended for most users.

Figure 7-8 Install type selection page The installer displays a summary screen of the products to be installed (see Figure 7-9 on page 187).0 6. Click Next to install the displayed components. the following components are installed: – WebSphere Business Integration Event Broker – WebSphere Business Integration Message Broker – IBM Message Brokers Toolkit for WebSphere Studio – Webscale Distribution Hub V2. 186 WebSphere Business Integration for SAP . If installing WebSphere Business Integration Message Broker.

Use Case 1: WBIMB using WBI Adapter for mySAP.Figure 7-9 The installation summary page A progress bar is displayed (see Figure 7-10 on page 188.com 187 . Chapter 7. which is an example of the WebSphere Business Integration Event Broker installer).

If installing WebSphere Business Integration Message Broker. 188 WebSphere Business Integration for SAP . the following progress screens are displayed: WebSphere Business Integration Event Broker WebSphere Business Integration Event Broker uninstaller WebSphere Business Integration Message Broker WebSphere Business Integration Message Broker uninstaller IBM Message Brokers Toolkit for WebSphere Studio IBM Message Brokers Toolkit for WebSphere Studio uninstaller Configuring security groups When the installer finishes installing WebSphere Business Integration Message Broker. The wizard creates the user groups that are needed to control the security of WebSphere Business Integration Message Broker’s resources and tasks. The wizard also assigns an administrator’s user account to the relevant groups.Figure 7-10 WebSphere Business Integration Event Broker install progress A separate progress page is displayed for each part of the software. the Security wizard is launched automatically.

The Security wizard creates the security groups shown in Table 7-3. mqbrops mqbrtpic To create and assign a user account to the relevant security groups.com 189 . Use Case 1: WBIMB using WBI Adapter for mySAP. Table 7-3 The security groups that are created by the Security Wizard Group mqbrasgn mqbrdevt mqbrkrs Purpose Allows users to assign message flows and message sets to brokers. Allows users to manage brokers. Allows users to manage topics and access control lists. and the Configuration Manager. On the welcome page of the Security Wizard. view logs. Chapter 7. click Next (see Figure 7-11 on page 190). message flows. and broker domains. Allows users to start brokers. the User Name Server. Allows users to create message sets and message flows. and trace message flows. do the following steps: 1.

Optional: To add another user to the groups. click Back to add another user to the WebSphere Business Integration Message Broker security groups. WebSphere Business Integration Message Broker cannot be run using the default Windows Administrator account. select the user account that is added to all the relevant WebSphere Business Integration Message Broker security groups. – Administrators: The Windows administrators group.Figure 7-11 The Security Wizard 2. From the User name list. The user account is also added to the following groups: – mqm: The WebSphere MQ security group. 3. The user account is added to all of the groups listed in Table 7-3 on page 189. and then click Next (see Figure 7-12 on page 191). 190 WebSphere Business Integration for SAP . Do not select the user name Administrator.

com 191 .Figure 7-12 The User Select and Create page 4. click Finish. Chapter 7. On the summary page (see Figure 7-13 on page 192). Use Case 1: WBIMB using WBI Adapter for mySAP.

perform the following tasks: 1. 192 WebSphere Business Integration for SAP . and before creating and starting a broker.Figure 7-13 Security Wizard summary page Post-installation tasks Before using the product. This is required by the license. Register the product. Ensure that the user ID that is used is a member of the Windows Administrators group in the local security domain.9 Install Message Broker FixPacks The instructions in this section describe how to install a FixPack on top of an installed version of WebSphere Business Integration Message Broker. Use the same user ID that was used to install WebSphere Business Integration Message Broker. 7.2. the following tasks must be completed: Confirm that enough licenses for the number of processors on the computer are available. Before installing the FixPack Before installing the FixPack.

If autorun is enabled. 2. enter the following command: mqsistop usernameserver 3. accept the default install location or specify an alternative. Close the Message Brokers Toolkit. These files are in the root directory of the CD and contain additional information regarding the installation and fixes available in this FixPack. the User Name Server (if applicable). such as the product Readme. including the Configuration Manager. Read the contents of the memo. 4. enter the following command: mqsistop WBRK_BROKER where WBRK_BROKER is the name of the broker. browse the CD and double-click setup. Install the FixPack from a CD To install the FixPack from a CD: 1.exe runs automatically. Chapter 7.2. Close all running programs. Insert the FixPack CD into the CD-ROM drive. 4. Run the executable file that are downloaded.exe. enter the following command: mqsistop configmgr – To stop each broker. 2. When prompted. 5.com 193 . at a command prompt. Install the FixPack from files downloaded from the Web To install the FixPack from files that are downloaded from the Web: 1. If not. Read the contents of the memo. and all brokers on the system: – To stop the Configuration Manager.ptf file and any readme. – To stop the User Name Server.ptf file that accompanies the downloaded file. 3. Use Case 1: WBIMB using WBI Adapter for mySAP. Close all WebSphere Business Integration Message Broker files. setup.html files. The FixPack can be installed from a CD or from files downloaded from the Web. Click Next to extract the files. This file contains additional information regarding the installation and fixes available in this FixPack. Ensure that all WebSphere Business Integration Message Broker services are stopped. Install the FixPack The following instructions describe how to install the FixPack.

Figure 7-14 Language selection 3.exe to start the framework installation.5.2.exe file runs automatically. 194 WebSphere Business Integration for SAP . Press Next on the welcome screen (Figure 7-15 on page 195).4 consists of various subcomponents. The setup. Select English as the language for the install wizard and click on OK (see Figure 7-14). 1.10 Install WBI Adapter Framework V2. 2. Click Finish to close the dialog. The subcomponents are: System Manager Virtual Test Connector Log Viewer Business Object Designer Connector Configurator Important: Make sure that no instance of WebSphere Studio Application Developer Integration Edition or any other Eclipse development environment is running when starting the framework installation.4 The WebSphere Business Integration Adapter Framework V2. 7. Switch to the folder where the installation files are located and execute setupwin32.

com 195 .Figure 7-15 Welcome screen 4. Figure 7-16 License agreement 5. such as C:\WebSphereAdapters. Chapter 7. as the installation destination and press Next (Figure 7-17 on page 196). Accept the license agreement and select Next (Figure 7-16). Enter a directory. Use Case 1: WBIMB using WBI Adapter for mySAP.

196 WebSphere Business Integration for SAP . Figure 7-18 Installation summary 7. Review the installation settings and click on Next (Figure 7-18). The WebSphere MQ Java libraries should be detected automatically (Figure 7-19 on page 197).Figure 7-17 Installation directory 6. Click on Next.

Select Install WebSphere Studio Workbench and plug-ins and click on Next (Figure 7-20). Use Case 1: WBIMB using WBI Adapter for mySAP. Leave the default Program group and click on Next (see Figure 7-21 on page 198). Figure 7-20 Workbench installation 9. Chapter 7.Figure 7-19 WebSphere MQ library location 8.com 197 .

Figure 7-21 Program group selection 10. Figure 7-22 Final window 198 WebSphere Business Integration for SAP .Click on Finish to close the wizard after the installation is complete (Figure 7-22).

com 199 . the Adapter Framework must be installed. Do the following steps: 1. Figure 7-23 Language selection 3. 2. Accept the license agreement and click on Next (Figure 7-25 on page 200).exe to start the installation.com The WebSphere Business Integration Adapter for mySAP. Figure 7-24 Welcome screen 4.com connector and the mySAP.com Object Discovery Agent (ODA). Use Case 1: WBIMB using WBI Adapter for mySAP. Choose English from the drop-down list as the installation language (Figure 7-23).11 Install WBI Adapter for mySAP. Press Next on the Welcome Screen (Figure 7-24).7.com includes the mySAP. Before installing the adapter. Chapter 7. Switch to the folder where the installation files are located and execute the file setupwin32.2.

Figure 7-26 WebSphere Adapter Framework location 6. Select the folder where the Adapter Framework is installed and click on Next (Figure 7-26). On the installation summary screen. 200 WebSphere Business Integration for SAP . click on Next (Figure 7-27 on page 201).Figure 7-25 License agreement 5.

no WebSphere InterChange Server is used. Leave the default Program group and click on Next (Figure 7-29 on page 202). Use Case 1: WBIMB using WBI Adapter for mySAP.Figure 7-27 Installation summary 7. Leave the input field blank and click on Next (Figure 7-28). In this scenario. Chapter 7.com 201 . Figure 7-28 Interchange Server name 8.

Figure 7-30 Final window 202 WebSphere Business Integration for SAP . Click on Finish to close the wizard after the installation is done (Figure 7-30).Figure 7-29 Program group selection 9.

Select the start_SAP_2. Create a shortcut for start_SAP_2.txt.Install a second connector To enable the integration broker to communicate with two SAP systems at the same time.txt) in the new repository directory to match the new connector name. and the integration broker. The target field should look like C:\WebSphereAdapters\connectors\SAP_2\start_SAP_2.3 Configuration of WebSphere Business Integration components This section explains how to configure the components of the WebSphere Business Integration System: WebSphere MQ.com Connector.cfg. Make a copy of the directory c:\WebSphereAdapters\repository\SAP and name it c:\WebSphereAdapters\repository\SAP_2. Use Case 1: WBIMB using WBI Adapter for mySAP.cfg. Right-click on the shortcut and select Properties. It includes the following tasks: Configure WebSphere MQ to work with the WebSphere Business Integration Adapter for mySAP. 7.bat to start_SAP_2.jar with a second connector name.bat SAP_2 WMQI_WAS -cC:\WebSphereAdapters\repository\SAP_2\SAP_2Connector. CN_SAP_2.com and the WebSphere Business Integration Message Broker. Rename the connector definition file (CN_SAP. the business objects. Rename start_SAP. such as CWSAP_2. Rename the new connector class file CWSAP. Name the shortcut mySAP_2. Chapter 7. In the Target field.bat: On Windows. It is necessary that connectors have a unique name: Make a copy of the directory c:\WebSphereAdapters\connectors\SAP and name it c:\WebSphereAdapters\connectors\SAP_2.com 203 .jar. append the string SAP_2 WMQI_WAS -cC:\WebSphereAdapters\repository\SAP_2\SAP_2Connector. right-click on the desktop and select New → Shortcut. Create a WebSphere Business Integration Message Broker Domain. the adapter. Configure the ALE Module of the WebSphere Business Integration Adapter for mySAP. a second instance of the connector must be installed.bat. for example.com.bat file and click Next.

If the queue manager and the connector are on the different machines. The connector can communicate with the queue manager in any of the following modes: Bindings mode: WebSphere Business Integration Message Broker and the connector communicate directly with the queue manager. a queue manager must be configured and also queues for carrying messages between the connector and WebSphere Business Integration Message Broker. The connector uses this information to establish a connection to the queue manager to be used for communicating with the WebSphere Business Integration Message Broker. To learn more about MQSeries messages. see WebSphere MQ Using Java. Bindings mode with remote queue definitions: If WebSphere Business Integration Message Broker and the connector are installed on separate machines. with each machine running its own queue manager. see WebSphere MQ: 204 WebSphere Business Integration for SAP . without using a TCP/IP connection.Configure the ABAP Extension Module of the WebSphere Business Integration Adapter for mySAP. SC34-6066.com uses MQ queues and standard Java Messaging Service (JMS) software as the communication transport mechanism between the connector framework and the broker. 7. Define the queue manager The connector uses a single queue manager to manage all of its interactions with queues.1 Configure WebSphere MQ WebSphere Business Integration Adapter for mySAP. The queue manager and the connector must be on the same machine and must use the same queue manager. The standard properties in the connector’s configuration file contain the queue manager information needed by the connector at startup. the connector is limited to using client mode. To enable WebSphere Business Integration Message Broker to work with a connector. Client mode: Communication occurs through a client connection that uses TCP/IP as its underlying transport.3. the connector and WebSphere Business Integration Message Broker can still communicate with their respective queue managers using bindings mode. but remote queue definitions are also needed. To learn more about MQSeries queues.com. Ensure that the connector’s configuration files contain correctly specified queue and queue manager information. which is provided in this chapter. This is the default mode and is described in “Create a queue manager using the WebSphere MQ Explorer” on page 205. The WebSphere Business Integration system supports several queue managers and queue configurations.

queues. and channels. 7. and WebSphere MQ: Script Command (MQSC) Reference. SC34-6059.Intercommunication. In this example.html Create a queue manager using the WebSphere MQ Explorer Tip: The supplied configure_mq. using the format host. 8.queue. 10.queue. Keep the default settings and click Next. SC34-6055.queue. Click Next.manager. All three of these IBM manuals can be found at: http://www-306. Use Case 1: WBIMB using WBI Adapter for mySAP. select the Queue Managers folder and Action → New → Queue Manager. 5. 6.bat file can also be used to set up the queue manager.com/software/integration/mqfamily/library/manualsa/manua ls/crosslatest. Open the Custom Services folder in the queue manager ITSOA. it would be ITSOA.queue. 1. – Queue manager – Command server – Channel initiator – Listener Chapter 7. Open the WebSphere MQ Explorer from the Windows Start menu. Open the WebSphere MQ Services Console.manager. 2. Name the queue manager.The following MQ services must be run (see Figure 7-31 on page 206). Close the WebSphere MQ Explorer.com 205 .manager.manager. In the WebSphere MQ Explorer. 9.ibm. 4. 3. Click on the queue manager ITSOA.

Figure 7-31 MQ Services 11.Use the host name as the local address. 12. To verify which ports are already in use on the processor. for example. ITSOA. for example. Figure 7-32 shows the Listener properties. and click OK. 13. Set the port to 1414 (default) or to another free port.Right-click on Listener and select Properties. 1416 or 1515. open a command prompt and enter the following command: netstat -a If port 1414 is being used by another queue manager.Go to the Parameters Tab and select the TCP Protocol. type in another port number. Figure 7-32 WebSphere MQ Listener properties 206 WebSphere Business Integration for SAP .

“Configuration of WebSphere MQ” on page 359. see 8. the script mqsetup. Table 7-4 Connector queues Queue name AdminInQueue Usage of the queue Delivers administrative messages from WebSphere Business Integration Message Broker to the connector framework. Delivers fault messages from the connector framework to WebSphere Business Integration Message Broker.com 207 .3. Delivers administrative messages from the connector framework to WebSphere Business Integration Message Broker. For more information about defining queues using the script.1. Also. Delivers request messages from WebSphere Business Integration Message Broker to the connector framework. Delivers event delivery messages from the connector framework to WebSphere Business Integration Message Broker.Define the queues Use MQ commands or the MQ Explorer to define the following local queues (see Table 7-4 and Table 7-5 on page 208) for each connector. AdminOutQueue DeliveryQueue FaultQueue RequestQueue Chapter 7. The connector framework places a message on this queue when it is unable to place the message on the reply-to queue.tst delivered with the WebSphere Business Integration Adapter Framework can be used for defining queues. Use Case 1: WBIMB using WBI Adapter for mySAP.

Queue name SynchronousRequestQueue Usage of the queue Delivers request messages from the connector framework to WebSphere Business Integration Message Broker that require a synchronous response. prefix the queue name with name of the connector. SynchronousResponseQueue Tip: To make it easier to determine the associated queue of each connector. The response message sent to the connector bears a correlation ID that matches the ID of the original message. additional local queues must be defined. name the SAP connector’s event delivery queue SAPCONNECTOR/DELIVERYQUEUE. This queue is necessary only if the connector uses synchronous execution. With synchronous execution. If the ALE module of the adapter is used. This queue is necessary only if the connector uses synchronous execution. Specifies the MQ Series queue that stores TIDs and IDoc data during the ALE Module’s processing of events. the connector framework sends the message to SynchronousRequestQueue and waits for a response back from WebSphere Business Integration Message Broker on the SynchronousResponseQueue. Table 7-5 Connector queues for the ALE module Queue name ArchiveQueue Usage of the queue Specifies the MQ Series queue that archives TIDs and IDoc data after the ALE Module has finished processing events. For example. EventQueue 208 WebSphere Business Integration for SAP . Delivers response messages from WebSphere Business Integration Message Broker to the connector framework sent in reply to a synchronous request.

Chapter 7. name the SAP connector’s archive queue SAPCONNECTOR/ARCHIVEQUEUE. Defines a queue to collect unsubscribed IDoc objects. prefix the queue name with name of the connector.com 209 . For more information about defining queues.bat file can also be used to set up the queues. Unsubscribed IDoc objects previously were placed in the ArchiveQueue. These messages can be resubmitted using the event management utility. WIPQueue UnsubscribeQueue TidQueue Tip: To make it easier to determine the associated queue of each connector. see WebSphere MQ System Administration Guide.com/software/integration/mqfamily/library/manualsa/manua ls/crosslatest. it moves the data in this queue to the EventQueue. Specifies the queue on which messages containing the TID and TID status reside. both of which can be found at: http://www-306. Use Case 1: WBIMB using WBI Adapter for mySAP. Specifies the MQ work-in-progress (wip) queue that holds TIDs and IDoc data while the ALE Module builds the MQ message for the event queue. 1. Open the MQ Explorer and select the Queues folder in the queue manager.ibm.Queue name ErrorQueue Usage of the queue Defines a queue to handle MQ messages that fail between the WIPQueue and the EventQueue.html Create local queues using the MQ Explorer Tip: The supplied configure_mq. resulting in transactions remaining in SAP until the message flow is started. The connector now checks for subscriptions when processing the data from SAP to the connector. After the connector receives all data for an event. For example. SC34-6068 and WebSphere MQ: Script Command (MQSC) Reference. SC34-6055. This property is used by the ALE Module only when processing requests.

5. When you are familiar with WebSphere Business Integration Message Broker. Enter CHANNEL1 as the channel name. 4. Select Action → New → Local Queue.2. This Use Case does not use a User Name Server. 210 WebSphere Business Integration for SAP . 4. broker domains can be created manually. Select from the menu Action → New → Server Connection Channel. Repeat steps 2 and 4 for each ALE channel that is required (one per ALE module.3.bat file can also be used to set up the channels 1. Repeat steps 2 and 3 for each queue listed above.2 Create a message broker domain A message broker domain represents the WebSphere Business Integration Message Broker run-time environment. Open the MQ Explorer and select the Advanced folder in the queue manager. Create channels using the WebSphere MQ Explorer Tip: The supplied configure_mq. A broker domain contains a single Configuration Manager with associated brokers. The following channels are required by the WebSphere Business Integration System. refer to the redbook WebSphere Business Integration Message Broker Basics. Enter SAPCONNECTOR/DELIVERYQUEUE as the queue name. Select the Channels folder. SG24-7090. It may also contain a User Name Server if authentication is used for publish/subscribe messaging. the channels TIDCHANNEL and TIDCHANNEL2 are used). 7. To learn more about broker domains. Define the channels Use MQSeries commands or the MQ Explorer to define server connection channels. 3. 3. 2. In this Use Case. To quickly create a default configuration for WebSphere Business Integration Message Broker run the Getting Started wizard in the Message Broker’s Toolkit.

Create a broker using the Getting Started wizard The Getting Started wizard creates the minimum components that are needed to run a message flow application. A DB2 database for storing the Configuration Manager’s data. Use Case 1: WBIMB using WBI Adapter for mySAP. and the nameserver can be created also using following commands: mqsicreatebroker <BROKER> -i <USERID> -a <PASSWORD> -q <QUEUEMANAGER> -n <BROKER_DB> -u <DB_USERID> -p <DB_PASSWORD> -s <QUEUEMANAGER> -j -P <QM_PORT> mqsicreateconfigmgr -i <USERID> -a <PASSWORD> -q <QUEUEMANAGER> -s <QUEUEMANAGER> -n <CONFIGMNG_DB> -u <DB_USERID> -p <DB_PASSWORD> mqsicreateusernameserver -i <USERID> -a <PASSWORD> -q <QUEUEMANAGER> Table 8-3 lists the components that the wizard creates. A configuration for the queue manager to use a listener port for communication between the Configuration Manager and the Message Brokers Toolkit. Tip: The broker. A link between the domain and the broker. A project within the Message Brokers Toolkit workspace to contain the broker domain connection information. A DB2 database for storing data that is deployed to the broker. A queue manager that is used by the broker and the Configuration Manager if no queue manager exists.manager created in “Create a queue manager using the WebSphere MQ Explorer” on page 205. prerequisite software such as DB2 and WebSphere MQ must have been installed.com 211 .queue. Chapter 7. Use the queue manager ITSOA. In order to run the Getting Started wizard. The wizard creates: A broker. and their default values. the configuration manager.

and an executing set of brokers. The port number conventionally has four digits. that is. Configuration Manager Configuration manager database Broker Broker database Start the Message Brokers Toolkit To run the Getting Started wizard.manager By default. WBRKBKDB. The Configuration Manager is the interface between the workbench. ISTOA_WBIMB. the field for this information is empty.queue. It provides brokers with their initial configuration. and updates them with any subsequent changes.Table 7-6 Components created by the Getting Started wizard Component WebSphere Business Integration Brokers services user account WebSphere Business Integration Broker services DB2 account Broker domain and broker domain connection Server Project Queue Manager name Queue Manager port Description The Windows account. ITSOA. Wait while the installation completes (see Figure 7-33 on page 213). LocalProject. The Windows account. 212 WebSphere Business Integration for SAP . WBRKCMDB. It maintains the broker domain configuration. To start the Message Brokers Toolkit: Click Start → Programs → IBM WebSphere Studio → Message Brokers Toolkit. the configuration repository. Localdomain. open the Message Brokers Toolkit. 1414.

Figure 7-33 The install completion screen

When the installation completes, the Message Brokers Toolkit opens. The welcome information provided on the opening screen of the Message Brokers Toolkit provides the Getting Started information. Read this page to learn more about getting started with the product (see Figure 7-34).

Figure 7-34 The Message Broker tooling welcome page

Running the Getting Started wizard
To create a configuration use the Getting Started wizard, do the following steps: 1. Log on with administrator privileges. 2. On the product welcome page, click Create a default configuration. The Getting Started wizard opens (see Figure 7-35 on page 214). 3. Click Next.

Chapter 7. Use Case 1: WBIMB using WBI Adapter for mySAP.com

213

Figure 7-35 The Getting Started wizard welcome page

4. Enter the information for the user account that is used to run the WebSphere Business Integration Message Broker services, such as the broker (see Figure 7-36 on page 215). – To create a new account, click New user account, then follow the steps to create the new account. – To use an existing account, click Existing user account, then enter the user name and password for the account that is used. The user account must be a member of the Administrators group and the mqm and mqbrkrs security groups. The account must also have enabled the security privilege to “act as part of the operating system”. If the account does not have this privilege, the Getting Started wizard can set it, but it requires you to reboot the computer.

214

WebSphere Business Integration for SAP

Figure 7-36 The broker services user account page

5. Decide which user account is used to access the broker and Configuration Manager DB2 databases: – To use the same user account as in step 4, ensure that the Also use this account for accessing the DB2 databases check box is selected. – To use a different account, clear the Also use this account for accessing the DB2 databases check box. Click Next and complete the information on the next page to specify the account to be used for accessing the DB2 databases. 6. Click Next. 7. In the Queue Manager name field, type the name of the queue manager, for example, ITSOA.queue.manager. 8. In the Queue Manager port field, type the number of the port on which the queue manager listens (see Figure 7-37 on page 216). Port 1414 is the default WebSphere MQ port.

Chapter 7. Use Case 1: WBIMB using WBI Adapter for mySAP.com

215

9. Accept the default Broker Domain name, and select ITSOA.queue.manager as the queue manager name. This is the queue manager created in “Create a queue manager using the WebSphere MQ Explorer” on page 205. 10.Use the default database name values. If components with those names already exist, change the names of the components that the Getting Started wizard creates. The database name has a maximum limit of eight characters. 11.Click Next. The wizard checks whether the a database with the specified name already exists on the computer. If it does exist, confirm it to continue. If continuing, data in the existing database might be lost. Alternatively, type a new name in the Database name field.

Figure 7-37 Broker domain details page

12.Set the Broker name to ITSOA_WBIMB and use the default database name values (see Figure 7-38 on page 217). If components with those names already exist, change the names of the components that the Getting Started wizard creates. The database name has a maximum limit of eight characters.

216

WebSphere Business Integration for SAP

13.Click Next. The wizard checks whether a database with the specified name already exists on the computer. If it does exist, confirm it to continue. If continuing, data in the existing database might be lost. Alternatively, type a new name in the Database name field. The wizard again checks whether the database specified for the broker already exists.

Figure 7-38 The broker details page

14.Accept the default project name for the Server project that the wizard creates. The connection name is not editable, because it was specified previously on the broker domain details page. If a server projects already exists, select one of the existing server projects from the list. If running the Getting Started wizard directly after installing the product, the only option available is LocalProject. 15.Click Next. 16.A summary screen is displayed (see Figure 7-39 on page 218), which lists the choices that are made on previous pages of the wizard. Click Next to start the configuration.

Chapter 7. Use Case 1: WBIMB using WBI Adapter for mySAP.com

217

Figure 7-39 The Getting Started wizard summary page

17.When the configuration is complete, the Getting Started wizard displays a success message (see Figure 7-40).

Figure 7-40 Successful default configuration created

7.3.3 Configure the WBI Adapter for mySAP.com to access SAP R/3 via ALE
The Connector Configurator tool provides a graphical user interface for configuring the connector of the WebSphere Business Integration Adapter for mySAP.com. When you are finished specifying values for the connector’s configuration properties, the Connector Configurator generates a configuration file for the connector and places it in the connector’s local repository.

218

WebSphere Business Integration for SAP

The installer loaded a connector definition file for the connector in c:\WebSphereAdapters\connectors\repository\SAP. The connector definition file provides initial values for some configuration file properties. The first step is to use the Connector Configurator to create a configuration file for the connector. While the connector definition file provides some starting values for the configuration file, the configuration file contains all the standard and application-specific properties for the connector, and specifies its supported business objects. This section contains the following tasks: Create a configuration using the Connector Configurator tool Create a shortcut to the connector’s startup script

Create a configuration using the Connector Configurator tool
1. Start the Connector Configurator by selecting Start → Programs → IBM WebSphere Business Integration Adapters → Tools → Connector Configurator. 2. Select Open → From File. 3. Navigate to the connector’s repository directory and open the file CN_SAP.txt. 4. Fill in the standard properties shown in Table 7-7 and Figure 7-41 on page 221.
Table 7-7 Standard connector properties Property AdminInQueue AdminOutQueue AgentTraceLevel ApplicationName BrokerType Character Encoding ContainerManagedEvents DeliveryQueue DeliveryTransport SAPCONNECTOR/DELIVERYQUEUE JMS Value SAPCONNECTOR/ADMININQUEUE SAPCONNECTOR/ADMOUTQUEUE 5 SAPConnector WMQI ascii7

Chapter 7. Use Case 1: WBIMB using WBI Adapter for mySAP.com

219

Property DuplicateEventElimination FaultQueue jms.FactoryClassName jms.MessageBrokerName

Value false SAPCONNECTOR/FAULTQUEUE CxCommon.Messaging.jms.IBMMQSerie sFactory QueueManagerName:MQChannelName: MQhostname:MQPort (ITSOA.queue.manager:CHANNEL1:ITS OA:1414)

jms.UserName
jms.Password Locale MessageFileName PollFrequency PollEndTime PollStartTime RepositoryDirectory RequestQueue ResponseQueue RFH2MessageDomain RestartRetryCount RestartRetryInterval SynchroneousRequestQueue SynchroneousRequestTimeout SynchroneousResponseQueue WireFormat XMLNameSpaceFormat

User ID of MQ Admin
Password of MQ Admin en_US SAPConnector 10000 HH:MM HH:MM c:\WebSphereAdapters\Repository\SAP SAPCONNECTOR/REQUESTQUEUE SAPCONNECTOR/RESPONSEQUEUE mrm 3 1 SAPCONNECTOR/SYNCHRONEOUSR EQUESTQUEUE 0 SAPCONNECTOR/SYNCHRONEOUSR ESPONSEQUEUE CwXML short

220

WebSphere Business Integration for SAP

Figure 7-41 Standard connector properties

5. Fill in the connector specific properties (see Table 7-8 and Figure 7-42 on page 223).
Table 7-8 Connector specific properties Property ABAPDebug ArchiveDays ApplicationPassword ApplicationUserName ALEUpdateStatus ALESelectiveUpdate ALEStatusMsgCode ALESuccessCode ALEFailureCode ALEFailureText Client 800 52 68 Value false 7 SAP User Password SAP User ID false

Chapter 7. Use Case 1: WBIMB using WBI Adapter for mySAP.com

221

Property DateTimeFormat Group GatewayService Hostname Language LogFileName MaxNumberOfConnections Modules Namespace NumberOfListeners PingFrequency PollQuantity RequestTransport RfcProgramId RFCTraceOn RefreshLogonCycle UseDefaults SAPSystemID Sysnr SAPtid_QueueManager SAPtid_QueueManagerLogin SAPtid_QueueManagerLoginPassword SAPtid_QueueManagerHost SAPtid_MQPort SAPtid_MQChannel SAPtid_Queue SAPALE_Wip_Queue

Value

sapgw00 siccserv.isicc.de.ibm.com® E STDOUT 1 ALE true 1 15000 20 MQ RFCSERVER false

false

00 ITSOA.queue.manager User ID of MQ Admin Password of MQ Admin ITSOA 1414 TIDCHANNEL SAPCONNECTOR/TID SAPCONNECTOR/WIP

222

WebSphere Business Integration for SAP

Property SAPALE_Event_Queue SAPALE_Archive_Queue SAPALE_US_Queue SAPALE_Error_Queue

Value SAPCONNECTOR/EVENT SAPCONNECTOR/ARCHIVE SAPCONNECTOR/US SAPCONNECTOR/ERROR

Figure 7-42 Connector specific properties

Chapter 7. Use Case 1: WBIMB using WBI Adapter for mySAP.com

223

6. Add the Business Object sap_matmas03 and the Message Set ID to the connector’s configuration (see Figure 7-43). Leave the Message Set ID field empty until the message set is created. Get the Message Set ID from the file messageSet.mgset in the Message Set Project using the Message Brokers Toolkit in a later step (refer to 7.7.3, “Create Message Sets and loading Business Object Definitions” on page 288).

Figure 7-43 Supported Business Objects

7. Define the logging and tracing file locations (the files must be created manually before using starting the connector the first time) (see Figure 7-44).

Figure 7-44 Log and trace file

8. The Data Handler properties cannot be filled in when using the WebSphere Business Integration Message Broker. 9. Save the file to the c:\WebSphereAdapters\connectors\repository\SAP folder.

224

WebSphere Business Integration for SAP

Create a shortcut to the connector’s startup script
To start the connector, a shortcut to the start_SAP.bat file located in the Adapter’s folder must be created on the desktop and it must be modified: 1. To create the shortcut, select Start → WebSphere Business Integration Adapters → Adapters → Connectors → Adapter for mySAP.com, click and drag the menu item, and drop it onto the desktop. 2. Right-click on the shortcut and select Properties. 3. In the Properties dialog box, modify the Target field: a. Append, after the path, the connector name SAP to the start_SAP.bat. b. Append, after the connector name, the parameter WMQI_WAS. c. Append the parameter c:\WebSphereAdapters\connectors\SAP\start_SAP.bat SAP WMQI_WAS -cC:\WebSphereAdapters\repository\SAP\SAPConnector.cfg.

7.3.4 Configure the WBI Adapter for mySAP.com to access SAP R/3 via the ABAP Extension module
The connector of the WebSphere Business Integration Adapter for mySAP.com must be configured for the ALE and the ABAP Extension Module. This section shows how to configure the second connector for the ABAP Extension Module. However, both connectors must be configured for the ALE and the ABAP Extension Module, because they are used in both scenarios of this Use Case.

Configure the connector for the ALE Module
The ALE configuration of the second connector is nearly the same as for the first connector. Therefore, refer to 7.3.3, “Configure the WBI Adapter for mySAP.com to access SAP R/3 via ALE” on page 218 for information on configuring the ALE part of the connector. Differences between both ALE configurations: The second connectors uses its own JMS and ALE queues. Also, the connector points to a different SAP system. The connector’s desktop shortcut points to start_SAP_2.bat. The connector name is SAP_2.

Configure the connector for the ABAP Extension Module
1. To configure the connector for the ABAP Extension Module, invoke the Connector Configurator by selecting Start → Programs → IBM WebSphere Business Adapters → Tools → Connector Configurator.

Chapter 7. Use Case 1: WBIMB using WBI Adapter for mySAP.com

225

2. Select File → Open → from File. Then open the Connector Configurator template file CN_SAP.txt in the WBI Adapters repository, for example, c:\WBIAdapters\Repository\SAP\CN_SAP.txt. 3. In the Standard Properties tab give the values as below.
Table 7-9 Standard connector properties Property AdminInQueue AdminOutQueue AgentTraceLevel ApplicationName BrokerType Character Encoding ContainerManagedEvents DeliveryQueue DeliveryTransport DuplicateEventElimination FaultQueue jms.FactoryClassName jms.MessageBrokerName SAP_2CONNECTOR/DELIVERYQUEUE JMS false SAP_2CONNECTOR/FAULTQUEUE CxCommon.Messaging.jms.IBMMQSerie sFactory QueueManagerName:MQChannelName: MQhostname:MQPort (ITSOA.queue.manager:CHANNEL1:ITS OA:1414) User ID of MQ Admin Password of MQ Admin en_US SAPConnector 10000 HH:MM HH:MM c:\WebSphereAdapters\Repository\SAP Value SAP_2CONNECTOR/ADMININQUEUE SAP_2CONNECTOR/ADMOUTQUEUE 5 SAPConnector WMQI ascii7

jms.UserName
jms.Password Locale MessageFileName PollFrequency PollEndTime PollStartTime RepositoryDirectory

226

WebSphere Business Integration for SAP

Use Case 1: WBIMB using WBI Adapter for mySAP.com 227 .Property RequestQueue ResponseQueue RFH2MessageDomain RestartRetryCount RestartRetryInterval SynchroneousRequestQueue SynchroneousRequestTimeout SynchroneousResponseQueue WireFormat XMLNameSpaceFormat Value SAP_2CONNECTOR/REQUESTQUEUE SAP_2CONNECTOR/ RESPONSEQUEUE mrm 3 1 SAP_2CONNECTOR/SYNCHRONEOUS REQUESTQUEUE 0 SAP_2CONNECTOR/SYNCHRONEOUS RESPONSEQUEUE CwXML short Chapter 7.

Figure 7-45 Standard properties of the connector 4. Fill in the values for Connector Specific Properties. Table 7-10 Connector specific properties Property ABAPDebug ArchiveDays ApplicationPassword ApplicationUserName ALEUpdateStatus ALESelectiveUpdate ALEStatusMsgCode Value false 7 SAP User Password SAP User ID false 228 WebSphere Business Integration for SAP . as in Table 7-10 and Figure 7-46 on page 231.

Use Case 1: WBIMB using WBI Adapter for mySAP.Property ALESuccessCode ALEFailureCode ALEFailureText Client DateTimeFormat Group GatewayService Hostname Language LogFileName MaxNumberOfConnections Modules Namespace NumberOfListeners PingFrequency PollQuantity RequestTransport RfcProgramId RFCTraceOn RefreshLogonCycle UseDefaults SAPSystemID Sysnr SAPtid_QueueManager SAPtid_QueueManagerLogin SAPtid_QueueManagerLoginPassword SAPtid_QueueManagerHost Value 52 68 030 sapgw48 sapbts08.com 229 .de.manager User ID of MQ Admin Password of MQ Admin ITSOA Chapter 7.sapbts.ibm.queue.com E STDOUT 1 Extension. ALE true 1 15000 20 MQ RFCSERVER false false 48 ITSOA.

Property SAPtid_MQPort SAPtid_MQChannel SAPtid_Queue SAPALE_Wip_Queue SAPALE_Event_Queue SAPALE_Archive_Queue SAPALE_US_Queue SAPALE_Error_Queue Value 1414 TIDCHANNEL2 SAP_2CONNECTOR/TID SAP_2CONNECTOR/WIP SAP_2CONNECTOR/EVENT SAP_2CONNECTOR/ARCHIVE SAP_2CONNECTOR/US SAP_2CONNECTOR/ERROR 230 WebSphere Business Integration for SAP .

mgset in the Message Set Project using the Message Brokers Toolkit (refer to 7.com 231 .7. Chapter 7. Leave the Message Set ID field empty until the message set was created.3. “Create Message Sets and loading Business Object Definitions” on page 288). Add the Business Object BO_EVENTRIGGER to the connector’s configuration (see Figure 7-47 on page 232). Select the Supported Business Object tab on the Connector Designer – SAPConnector window.Figure 7-46 Connector specific properties 5. Get the Message Set ID in a later step from the file messageSet. Use Case 1: WBIMB using WBI Adapter for mySAP.

In the Trace/Log files tab. 232 WebSphere Business Integration for SAP . 3.cfg to the repository c\WebSphereAdapters\connectors\repository\SAP_2 folder. Save the connector configuration file. 2. 8. Save the file as SAP_2Connector. Figure 7-48 Log and Trace File 7.Figure 7-47 Supported Business Objects for the ABAP Extension & ALE Module 6. Add the value Extension to connector specific property module. The Data Handler properties cannot be filled in when using the WebSphere Business Integration Message Broker. Repeat the ABAP Extension Module configuration for the first connector: 1. Add the Business Object BO_EVENTRIGGER to the first connector’s configuration. define the logging and tracing file locations (the files must be created manually before starting the connector the first time) (see Figure 7-48).

4. Append. To set up a CPIC user ID.1 Configure a SAP Gateway Make sure a SAP Gateway is installed and running on the SAP application server. click and hold on Adapter for mySAP. 7. 3. and drag and drop the item onto the desktop. 1. Append the parameter C:\WebSphereAdapters\connectors\SAP_2\start_SAP_2. Append. The CPIC user ID must be specified in the connector’s configuration file.cfg. Right-click on the shortcut and select Properties. Click on OK.4.general configuration steps This chapter contains the following configuration steps: Configure a SAP Gateway Create a SAP CPIC User ID Set up a SAP RFC destination. the connector name SAP_2 to the start_SAP_2. b. To create the shortcut. Chapter 7. select Start → WebSphere Business Integration Adapters → Adapters → Connectors → Adapter for mySAP. modify the Target field: a. after the path. 7.com.2 Create a CPIC User ID A CPIC user ID is required for accessing the SAP system using the WebSphere Business Integration Adapter for mySAP.Create a shortcut to the connector’s startup script To start the connector.bat file located in the adapter’s folder must be created on the desktop and it must be modified: 1.bat SAP_2 WMQI_WAS -cC:\WebSphereAdapters\repository\SAP_2\SAP_2Connector. Refer to the SAP documentation on how to set up a SAP Gateway. after the connector name.bat. In the Properties dialog box. d. open the transaction su01 (the window in Figure 7-49 on page 234 should appear). the parameter WMQI_WAS. Use Case 1: WBIMB using WBI Adapter for mySAP.com. 2.com 233 .4 Configuration of SAP R/3 .com. 7. c. a shortcut to the start_SAP_2.

5. Enter a name for the user ID (for example. the RFC Server Module of the connector registers with the SAP Gateway. Set the appropriate User Role and User Profile (SAP_ALL is recommended for development purposes). Save the user ID by clicking on Save. WBIADMIN). 234 WebSphere Business Integration for SAP . Figure 7-49 Transaction su01: Maintain User 7. This value must match the value in SAP R/3. Enter a password for the user ID.3 Set up a RFC Destination from SAP R/3 to Gateway During initialization. 3.4. 6. It uses the value set for the RfcProgramId connector-specific configuration property. SAP R/3 must be configured so that the RFC Server Module can create a handle to it. Set the User Type to Communication.2. 4.

open transaction SM59. WBICON. In SAP. do the following steps: 1. enter the name of the RFC destination system. Expand the TCP/IP connections directory. for example. Chapter 7. 2. for example. 5. 3. Enter a description for the new RFC destination. and then press Enter. Set the connection type to T (Start an external program via TCP/IP).To register the RFC Server Module as an RFC destination. The window in Figure 7-50 on page 236 should appear. RFCSERVER. Use Case 1: WBIMB using WBI Adapter for mySAP. 9. 8. Save the RFC Destination by clicking Save. 7. 6. In the RFC destination field. and then click Save. Attention: Test Connection only succeeds if the connector is running.com 235 . 4. Set the Program ID. Click Create (or press F8). Click the Registration button for the Activation Type.

236 WebSphere Business Integration for SAP .5 Configuration of SAP R/3 to work with the ALE Module of the Adapter The SAP application must be configured to work with the ALE Module of the Adapter for mySAP. step-by-step.com. There is a difference in the configuration of the distribution model between the inbound and the outbound SAP application. the configuration of ALE. The SAP configuration must be done twice: for the inbound and the outbound SAP applications. This section describes. Most of the configuration steps are the same.Figure 7-50 Transaction sm59: RFC Destination 7.

Add a entry for the WebSphere Business Integration Adapter for mySAP. 4. Use Case 1: WBIMB using WBI Adapter for mySAP. Each system in the distributed environment must have a unique logical system name (even non-SAP systems like the WebSphere Business Integration Adapter for mySAP. In the SAP application. WBICON. 3. Click OK to continue. The table is cross-client dialog appears. open transaction bd54. Each system in the distributed environment must have a unique logical system name (even non-SAP systems like WebSphere Business Integration Adapter for mySAP.com 237 . Name it.This section contains the following configuration steps: Create a Partner Logical System Create a SAP Logical System Create a Distribution Model for the outbound SAP application Create a Distribution Model for the inbound SAP application Generate Partner Profiles and transactional RFC Ports 7.2 Create a local SAP logical system The logical system is used as the ID for communication. 2. The screen in Figure 7-51 should appear. 1. for example. 7. and supply a description. Chapter 7. Click on Save.5. Figure 7-51 Transaction bd54: Logical systems A Prompt for Workbench request pop-up window is seen.com.com).5.com).1 Create a partner logical system The logical system is used as the partner ID for communication. SAP records information whenever a user changes critical SAP system properties.

In the SAP application. a. Add a entry for the SAP client the Adapter is accessing. e. 3. In this Use Case. Name it with the format <systemname>CLNT<client>. d. for example. Type IDSCLNT800 as the logical system name of the SAP system. The table is cross-client dialog appears. Double-click the entry for the client number. Click on the Table view menu. Link the local SAP logical system to the client. it is client 800. b.To create a local SAP Logical System. do the following steps: 1. Click OK to continue. open the transaction bd54. Open transaction scc4 (see Figure 7-52). Figure 7-52 Transaction scc4: Link local SAP logical system to a client 238 WebSphere Business Integration for SAP . 2. c. and supply a description. Select Display → Change to change the current Display view to the Change view. f. IDSCLNT800.

here. Enter MATMAS into the Message type field (Figure 7-54). Click on Save. for example. Select the Model View that was created and click on the Add Message Type button. Generate a Partner Profile and a transactional RFC Port (the name of the port is generated automatically. . for the Model View (see Figure 7-53). Click on Save.com 239 . it is A000000020) by selecting Environment → Generate Partner Profile. 2. is to be sent to which other logical system. from which logical system. 6. for example. Click on the Create a Model View button. Chapter 7.4. WBICON. 1. specify which message type. 3. Use Case 1: WBIMB using WBI Adapter for mySAP. in the distribution model. Figure 7-53 Transaction bd64: Create a model view 4. open transaction bd64. Figure 7-54 Transaction bd64: Add a message type to the model view 5.5. Enter a Short Text.3 Create a Distribution Model in the inbound SAP application If a message is to be sent from one logical system to another. and a Technical Name. Switch to the edit mode (press F9). 7. In the SAP application. WBI Connection.

Figure 7-55 Transaction bd64: Generate Partner Profile 7. Figure 7-56 Generate partner profile 8. Open transaction we21 and check the port (Figure 7-57 on page 241). Note that a port was generated automatically. The summary is displayed (Figure 7-56). 240 WebSphere Business Integration for SAP .

Open transaction we20 to check the Partner profiles (Figure 7-58). Use Case 1: WBIMB using WBI Adapter for mySAP.Figure 7-57 Transaction we21: Ports in IDoc processing 9.com 241 . Figure 7-58 Transaction we20: Partner profiles Chapter 7.

Generate a Partner Profile and a transactional RFC Port by selecting Environment → Generate Partner Profile. Figure 7-59 Transaction bd64: Create a model view 4.4 Create a Distribution Model in the outbound SAP application If a message is sent from one logical system to another. Enter a Short Text.5. Select the Model View that was created and click on the Add Message Type button. and a Technical Name. 6. Enter MATMAS into the Message type field (Figure 7-60). 242 WebSphere Business Integration for SAP . in the distribution model. Switch to the edit mode (press F9). for the Model View (Figure 7-59).7. In the SAP application. open transaction bd64. for example. Click the Create a Model View button. Click on Save. 3. for example. 2. Figure 7-60 Transaction bd64: Add a message type to the model view 5. from which logical system. is to be sent to which other logical system. . 1. WBI Connection. which message type. specify. WBICON.

2.1 Creating the /CWLD/ namespace Before the transport files for the ABAP Extension Module can be installed. It is the only adapter module that supports polling and can be used in conjunction with all other adapter modules to provide this functionality. Chapter 7. and they also can be retrieved through both request/reply and publish/subscribe models. This section contains the following topics: Creating CWLD namespaces Making the namespace CWLD available for modifications Installing connector transport files for the ABAP Extension Module Processing the business objects in the ABAP Extension module Creating an Event triggering and detection mechanism using Business Workflow 7.7.6. Do the following steps: 1. Expand the Administration menu and double-click on the Display/Change Namespaces option (see Figure 7-61 on page 244).com provides rich functionality within SAP R/3. and returns the unique ID of any created objects. a namespace must be created in SAP R/3. Open the Transport Organizer (transaction se03).com 243 . The objects can be retrieved and manipulated to and from SAP in real time. Use Case 1: WBIMB using WBI Adapter for mySAP. The adapter enables real-time retrieval of a complex object from SAP or a request to create. change. The adapter notifies you about the success and status of the object transaction request.6 Configuration of SAP R/3 to work with the ABAP Extension Module of the Adapter The ABAP Extension Module of the WebSphere Business Integration Adapter for mySAP. The ABAP Extension Module has advanced event detection mechanisms and business object handlers that manipulate the most common objects from SAP. or delete an object.

Transport Organizer 3. Click on the Display → Change (Ctrl+F1) button (see Figure 7-62 on page 245). 244 WebSphere Business Integration for SAP .Figure 7-61 Transaction se03 . The view Display View “Repository Namespaces”: Overview appears.

5. Click the Continue button to close the Information window. Chapter 7. an information window is displayed.Figure 7-62 Repository Namespace view 4. Click the New Entries (F5) button and type /CWLD/ in the Namespace field. If data is being edited by other users. (see Figure 7-63 on page 246).com 245 . Use Case 1: WBIMB using WBI Adapter for mySAP.

new entries 6.:. Type WBI Namespace in the Short text field and type CrossWorlds® in the Owner field (see Figure 7-64 on page 247). expand it (press F4) to see options. 246 WebSphere Business Integration for SAP . Figure 7-63 Repository Namespace view . Select the Namespace role field. and then select Recipient (C).

expand the Administration menu and double-click on the Set System Change option.com 247 .Figure 7-64 New Entry details 7. For the namespace /CWLD/. select Modifiable in the Modifiable column of the Namespace/Name Range row. 2. Make the namespace /CWLD/ available for modifications ABAP objects in the /CWLD/ namespace cannot be modified until the namespace is available for modification. If the system is set up to track customizing changes. Click on the Display >Change (Ctrl+F1) button. a repair license to modify the objects must be available. 3. 4. Click on the Save (Ctrl+S) button. Open the Transport Organizer Tools window (transaction SE03). there is a prompt for a change request that will allow transport of the namespace to another system. Click the Back (F3) button twice. Click on the Save (Ctrl+S) button. Click on the Continue button to close the Information window. Do the following steps: 1. To update SAP4.x delivered ABAP objects. Click the Save (Ctrl+S) button. Double-click on namespace /CWLD/ and enter the repair license. 5. 6. Use Case 1: WBIMB using WBI Adapter for mySAP. Chapter 7. Expand the Administration menu and double-click on the Display/Change namespaces option. 7. Contact IBM technical support to obtain the license.

such as table structures.com (R/3 Version.zip file for detailed information about the transport file. Modifications required by the adapter are handled by these connector transport files. The transports are installed on an SAP R/3 application server. Each transport file is included in a.6.After the namespace is created. These development objects must be imported into the SAP system to provide the specific functionality required by the ABAP Extension Module. 4_Utilities (CWDK900483) 3. which are listed in Table 7-11 on page 249. 4_Tools_Maintenance (CWDK900463) 7. There are seven connector transport files. the transport file for the SAP R/3 Version 4. 4_Delivery (CWDK900487) 5. The Primary. They are not required for the run-time environment. See the transport note included in each transport. Request.com for Windows can be found in the \connectors\SAP\dependencies\transports directory. 1. Utilities. 4_NumberRange (CWDK900337) 6. install the transports in the order listed.x connector transport files. and for UNIX they are found in the /connector/SAP/bin directory. Utilities. To ensure that all necessary tables are created before the data for those tables is added. and Request transport files are required. as described below. For example. 4_Primary (CWDK900333) 2. 7.x Primary transport is located in the 4_Primary. the WebSphere Business Integration transport files can be installed. The transport files for the IBM WebSphere Business Integration Adapter for mySAP. 4_Tools_Development (CWDK900480) The functionality provided by the Primary. functions. 248 WebSphere Business Integration for SAP .4.2 Install connector transport files for the ABAP Extension Module All of the SAP R/3 transports of the WebSphere Business Integration Adapter for mySAP.x) contain a variety of objects. The following is a list of the SAP R/3 Version 4. The Tools_Maintenance and Tools_Development transport files can be installed at anytime after the required transport files are installed. 4_Request (CWDK900455) 4.zip file.zip file. and data. and Delivery transport files is to make the run-time components.

com 249 . which can be used to make customer-specific changes to the triggering logic. 4_Request 4_Delivery Chapter 7. Important: If you are applying this transport file to a system that already has the connector running on it. it contains the log and data elements. This client-independent transport file contains the functionality required to support business object request operations. as well as the restriction include program. which are loaded only once into the system. For example. and maintenance components.Table 7-11 Connector transport files Name of Transport 4_Primary Purpose This transport file contains the development objects. It contains the number range objects. the development classes. the contents of the transport file may overwrite changes that were made to the existing environment. and the dynamic transaction declaration include program. 4_Utilities This client-independent transport file contains objects and functionality that are shared among the request. delivery. including event triggering and event polling. development. Use Case 1: WBIMB using WBI Adapter for mySAP. This client-independent transport file contains the functionality required to support event delivery operations.

future event. Copy the files (data files) that have names beginning with R to the \usr\sap\trans\data directory. Note: Re-importing the Number Range transport file initializes the existing number range intervals for the connector. This transport file can be installed at any time after the Primary transport has been installed. This corrupts the data in the connector’s log. Use these intervals or create the number range intervals themselves. any development done prior to reapplying the transport files are overwritten. Import the transport files by using the SAP R/3 transaction STMS (Transport Management System). 250 WebSphere Business Integration for SAP . a. Log in to the SAP R/3 system.Name of Transport 4_Number Range Purpose This client-dependent transport file contains the four number ranges in their initial state. Copy the transports to the SAP R/3 application server. such as displaying the log statistics and event tables. To install the transports: 1. current event. Attention: If reapplying transports. b. There are two kinds of transport files: a. They do not alter any SAP R/3 programs or modify user exits. and archive tables if those tables are not refreshed before reusing. Copy files (control files) that have names beginning with K to the \usr\sap\trans\cofiles directory. 2. 4_Tools_Maintenance 4_Tools_Development Install connector transport files The connector transport files make all the necessary modifications to SAP R/3 by importing programs and other development objects. This client-independent transport file contains the functionality required to support the development of objects. The functionality required to support maintenance operations.

and then click Import (see Figure 7-66 on page 252). c. and then click on the check mark (see Figure 7-65. g. Click on the Import overview (F5) icon. In the menu bar. Select the transport in the queue that was just added.Add transport request to the queue f. h. select Extras → Other requests → Add. click Yes to attach the import to the queue. Double-click the appropriate queue to be updated. In the menu bar. Chapter 7. click Request.b. Populate the transport request field. When the Add Transport Request confirmation window appears. d.com 251 . Use Case 1: WBIMB using WBI Adapter for mySAP. Figure 7-65 Transaction STMS . e.

for example. select Immediate.Import Request i.Figure 7-66 Transaction STMS . Populate the Target client field (with. 800). and click on the check mark to import the transport file (see Figure 7-67 on page 253). 252 WebSphere Business Integration for SAP .

Figure 7-68 Transaction STMS .com 253 . Use Case 1: WBIMB using WBI Adapter for mySAP. Repeat steps 1 to 3 to import the other transports in the order listed above. In the confirmation dialog box.Figure 7-67 Transaction STMS .Confirmation of transport import 3. Chapter 7. click Yes (See Figure 7-68).Select Target Client j.

There are two options to view the log: 1. change the development class to follow the migration path of the development classes. and then click on the Transport Layer button. Post installation task After the transports are installed. Examine the log to see if the installation was successful. – Double-click the appropriate queue. Use IBM CrossWorlds Station (transaction /CWLD/HOME) to do the following: 1. – Click the Import overview (F5) icon. and then click on the Save button (see Figure 7-69 on page 255).Verify connector transport files installation Verify that transport files were moved to SAP R/3. Use the Transport Management System graphic interface (transaction STMS). Click on the Tools tab. Select the appropriate Transport layer entry. Open the Transport Organizer (transaction SE01). and then select Logs. – Right-click the transport number. 2. – Click Display to see the log. – Populate the Request/Task field with the name of the transport file. 254 WebSphere Business Integration for SAP . 2.

If changes are overwritten. Verify that SAP generated the objects successfully To verify that SAP generated the objects successfully: 1. 2. they must be reapplied manually. Chapter 7.com 255 . Enter /CWLD/CONSTANTS in the Program field (see Figure 7-70 on page 256). These changes can be overwritten by the next release of transport files. Go to the ABAP Editor using transaction SE38.Figure 7-69 Assign transport layer for the development class Note: It is recommended to document outside of SAP any changes made to the development objects in the connector transports. Use Case 1: WBIMB using WBI Adapter for mySAP.

Figure 7-70 Transaction se38 . If you receive the message Programs successfully generated. the business object data is processed the same way. click Generate. 7. Click Select All. 5. and then click Continue (F2). 4. 256 WebSphere Business Integration for SAP . and then click Display.6. From the Program menu. the transports were successfully imported. For example. The processing is the same whether a business object is sent into the SAP application as a retrieve performed as part of event notification or as a business object request. if developing a business object based on a Call Transaction or an IDoc.ABAP Editor 3. Select Source Code. The business object’s verb also does not change the processing.3 Process the business objects in the ABAP Extension module Business object processing for the extension module is the same for all business objects regardless of the specific native SAP API that is used.

The ABAP handler processes the business object data. The connector receives the new business object data. An overview of the business object processing for sales is shown in Figure 7-71. generates business object response data. and returns new business object data to the connector through /CWLD/RFC_DO_VERB_NEXTGEN. The function of an ABAP handler is to get business object data into or out of the SAP application database.Business object processing consists of four steps: The connector converts an application-specific business object into a flat structure containing business object data and passes the data to the SAP application. The connector’s function module /CWLD/RFC_DO_VERB_NEXTGEN dynamically routes the business object data to an ABAP handler. Figure 7-71 Sales order business object processing Chapter 7. for example /CWLD/DYNAMIC_RETRIEVE. Use Case 1: WBIMB using WBI Adapter for mySAP. and uses the business object definition of the application-specific business object to create a new business object to pass to the integration broker.com 257 .

SAP application is tightly integrated with the SAP database and allows very limited access for direct modifications to its database. Go to the Business Object Builder using transaction swo1 (see Figure 7-72 on page 259). an event triggering mechanism in SAP R/3 must be implemented for each WBI supported business object. It is the process of identifying that an event was generated in the SAP application. a Business Workflow for event detection is used. Determine which SAP Business Object to use for triggering Whenever a SAP sales order is created in this Use Case using the transaction VA01 the business process triggers an event for the business object BO_EVENTRIGGER. Business workflow is a cross-application tool within the SAP application that enables SAP R/3 to integrate business tasks between applications. which stores the definitions for each SAP object in the application. Use SAP’s Business Object Repository (transaction swo1) to determine which SAP business object to use for triggering the events. An event detection mechanism has the ability to make a function module call. In order to get events out of SAP R/3. In this Use Case. This tool supplements the existing business functions of the SAP application. the event detection mechanisms are implemented in the application transaction layer above the database. 258 WebSphere Business Integration for SAP . 1. which takes the detected event and adds it to an event table.4 Create an Event triggering and detection mechanism The Adapter for mySAP.7. Therefore. The event detection mechanism calls an event trigger.com is event-driven. Event detection is part of the event triggering process in the ABAP Extension Module. Workflow uses the Business Object Repository (BOR).6. Event detection mechanisms support real-time triggering and retrieval of objects. The standard functions of SAP can be adapted using business workflow to meet the specific requirements of the desired business function.

Chapter 7. and then click Continue (green check) (see Figure 7-73). Click on the Business Object Repository button.com 259 . select All object types in the pop-up screen that appears. Figure 7-73 Business Object Repository Browser 3. Use Case 1: WBIMB using WBI Adapter for mySAP.Figure 7-72 Business Object Builder 2. The Business Object Repository Browser appears.

Figure 7-74 Business Object Repository 5. Note the entries for SalesOrder. and then expand Events. Double-click on BUS2032 Sales Order.4.CREATED. 260 WebSphere Business Integration for SAP . These are the events associated with Sales Order. Expand Sales and Distribution. and then expand Sales (see Figure 7-74 on page 260).

com 261 .Link SAP Events to the WBI queueing Function Module Link the events associated with the SAP business object to the WebSphere Business Integration queueing function module by performing the following steps: 1. In the main window of SAP. select Tools → Business Workflow → Development → Administration → Event Manager → Type Linkages. Figure 7-75 SAP Easy Access main view Chapter 7. Use Case 1: WBIMB using WBI Adapter for mySAP.

In this window. Click on Type linkages. It opens a window called Event Type Linkages (see Figure 7-76). search for the Object Type BUS2032. 262 WebSphere Business Integration for SAP .2. Double click on it and it opens a view called Event Type Linkages Details (see Figure 7-77 on page 263). Figure 7-76 Event type linkages 3.

com 263 . Add the entries shown Figure 7-77. The window Change View “Instance Linkages”: Overview opens (see Figure 7-78 on page 264). Use Case 1: WBIMB using WBI Adapter for mySAP. In the main window of SAP. Chapter 7. navigate to the Tools → Business Workflow → Development → Administration → Event Manager → Instance Linkages. Also an entry must be added to the Instance linkages table to trigger the event: 1.Details 4. 6. Go to the main screen by clicking on Back (F3).Figure 7-77 Event Type Linkages . 5. Save it by clicking on the Save (Ctrl+S) button.

In the Object Type.Overview 2.Figure 7-78 Change View “Instance Linkages” .Details window opens (see Figure 7-79 on page 265). The Instance Linkages . search for BUS2032 and double-click on it. 264 WebSphere Business Integration for SAP .

Retrieve. and Update. RETRIEVED. and SAP uses CREATED. and CHANGED. Go to CrossWorlds Station and transaction /cwld/home (see Figure 7-80 on page 266). To map the objects. WebSphere Business Integration and SAP uses unique naming conventions for business objects and verbs. Retrieve). Add the details shown in Figure 7-79 and click on Save. BO_EVENTRIGGER) and a verb (for example. For example. Map the SAP Business Object to a WBI Business Object The SAP business object name and event must be mapped to the WebSphere Business Integration business object name (for example. Chapter 7.Figure 7-79 Instance Linkages .Details 3. and therefore maps the names and verbs. WebSphere Business Integration uses the verbs Create. Use Case 1: WBIMB using WBI Adapter for mySAP.com 265 . do the following: 1.

and then click on the Config Objects button. the Locked data window appears. The CW Configuration Objects: Overview view appears (see Figure 7-81 on page 267).Development Tab 2. In CrossWorlds Station.Figure 7-80 IBM CrossWorld Station . click on the Tools tab. 266 WebSphere Business Integration for SAP . Click Yes to display the locked data. If someone else is already in this transaction.

Verify that there is an entry mapping for SalesOrder. Click on Yes. a Locked data Window appears. If someone else is already in this transaction.Overview view 3. Verify that a configuration name for SalesOrder.Figure 7-81 CW Configuration Objects . Go to CrossWorlds station by clicking on the Back button.com 267 . 4. Use Case 1: WBIMB using WBI Adapter for mySAP. It opens the window Change View “IBM CW Object parameter configuration”: Overview (see Figure 7-82 on page 268). Click on the Configuration tab and then on the Configuration Values button.Retrieve. 5.CREATED exists. Chapter 7.CREATED to BO_EVENTRIGGER.

2. Return to CrossWorlds home by clicking on the Back button. Click on the New entries button. 4. and then click non Maintain Objects. 268 WebSphere Business Integration for SAP .Overview 6.Figure 7-82 Change View “IBM CW Object parameter configuration” . 1. Configure Event Distribution . and save it (see Figure 7-83 on page 269). 3. BO_EVENTRIGGER. then events do not get picked up. Attention: The Event Distribution tables are case sensitive. If the case does not match. Enter the business object name. for example. Select the Tools tab. Go to CrossWorlds home (transaction /cwld/home).

Chapter 7. Use Case 1: WBIMB using WBI Adapter for mySAP. click on Config Objects. 7.Figure 7-83 Add business object 5. 6. Click on the Back button. Enter BO_EVENTRIGGER.com 269 .Retrieve under the Configuration name and save it (see Figure 7-84 on page 270). In the Tools tab.

9.Retrieve 8.Enter a value for the counter.Figure 7-84 Add BO_EVENTRIGGER. 11.CREATED as the configuration name. 270 WebSphere Business Integration for SAP .Retrieve. for example.Enter a value for the configuration value. BO_EVENTRIGGER. Enter the value SalesOrder. 1. for example. 10. Select the Configuration tab and click on Configuration Values (see Figure 7-85 on page 271).

com 271 .Click on Modify BO Metadata.Go to the Development tab. 15. “Create Business Object for the ABAP Extension Module” on page 283.Click on the Back button. Chapter 7. The data structure looks like the according WebSphere Business Integration business object structure defined with the Business Object Designer tool in 7.Click on Save.Figure 7-85 Add configuration values 12. Enter the values shown in Figure 7-86 on page 272. 13.7.2. Use Case 1: WBIMB using WBI Adapter for mySAP. 14.

click on the Back button. 19. click on the New Entries button and type in the following data: – Object Name: BO_EVENTRIGGER – Counter: A unique number – Connector Name: SAPConnector (name of the SAP adapter) – Server Name: WMQI_WAS (if using the Message Broker) – User: SAP User ID The new entry will look like Figure 7-87 on page 273.Click on the Configuration tab. 17.Go to CrossWorlds home (transaction /cwld/home). When the data is unlocked. Apply changes to this table. 272 WebSphere Business Integration for SAP . and wait until the transaction is unlocked. and then click on the Event Distribution button. and then repeat the previous step. a Locked data window appears. 18.To create a new entry.If someone else is already in this transaction.Figure 7-86 Modify BO Metadata 16.

Use Case 1: WBIMB using WBI Adapter for mySAP. Click Save. Type SAP Workflow triggering for WebSphere.New entry 20. Click the Back button and verify that the entry exists in the table. not generic business objects.Click on the Save button. 3. Return to CrossWorlds station home by clicking the Back button twice. then there is no need to create a customizing request. If an entry already exists. Many of the books in the IBM WebSphere InterChange Server documentation set. If asked for a Customizing request.7 Development of WebSphere Business Integration Business Objects WebSphere Business Integration Message Broker uses only application-specific business objects. cover both environments and therefore refer to both types of business objects. 6. Chapter 7. create a new one at this time: 1. including the Business Object Development Guide. 5. Therefore. Click Enter (green check).com 273 . all references to business objects throughout this chapter refer to application-specific business objects.Figure 7-87 Event distribution . 2. Click on the New button. 4. 7.

Start the SAP Object Discovery Agent Start the Business Object Discovery Agent by selecting Start → Programs → IBM WebSphere Business Integration Adapters → Adapters → Object Discovery Agent → mySAP.7. “discovers” the elements of those objects that correspond to business object attributes and their attributes. The Object Discovery Agent examines specified objects in the application.There are several options to create the Business Object definitions to be used by the WebSphere Business Integration Adapter for mySAP. To start the Business Object Designer tool. and generates business object definitions to represent the information. and RFCs. The window in Figure 7-88 on page 275 should appear. BAPIs. 274 WebSphere Business Integration for SAP . which can refine using the Business Object Designer tool. The following sections shows: How to create a Business Object from the IDoc type MATMAS03 using the SAP Object Discovery Agent and the Business Object Designer tool How to create a Business Object for the ABAP Extension Module from scratch using the Business Object Designer tool 7.com Object Discovery Agent. the System Manager must be launched. Create business object definitions from scratch using the Business Object Designer tool. The SAP Object Discovery Agent generates Business Objects by accessing the SAP data repository using the Dynamic Retrieve Module of the adapter. Also.com can handle SAP standard and customized IDocs.1 Create Business Object for the ALE module This chapter describes how to create a Business Object using the SAP Object Discovery Agent and the Business Object Designer tool. The Adapter for mySAP.com: Use the SAP Object Discovery Agent with the Business Object Designer tool to generate a rudimentary set of application-specific business object definitions. SAP Object Discovery Agent can generate Business Objects using IDoc definition files. The Business Objects are saved in the System Manager to deploy them in a later step to the Message Brokers Toolkit.

a. for example. Right-click on the Integration Components Library and select New Integration Components Library. In the Project name. OrderEventNotification_Lib. create a new Integration Component Library called. 2. b. the System Manager is used to save Business Objects and to deploy them as Message definition files into the Message Brokers Toolkit: 1. In the System Manager perspective. Also. To start the System Manager. Chapter 7.Figure 7-88 SAP Object Discovery Agent Start the WebSphere Business Integration System Manager Using the System Manager.com 275 . Use Case 1: WBIMB using WBI Adapter for mySAP. enter MaterialSynchronization_Lib (see Figure 7-89 on page 276). the Business Object Designer tool can be started. select Start → Programs → IBM WebSphere Business Integration Adapters → Adapters → Tools → System Manager.

b. Right-click on the User Projects folder and select New User Project → New Message broker project. c. In the Project name. 276 WebSphere Business Integration for SAP .Figure 7-89 Create a new Integration Component Library c. 3. In the System Manager perspective. Select the project MaterialSynchronization_Lib as the Integration Component Library and click Finish. Click Finish. enter MaterialSynchronization_Proj. create a new User Project: a.

select File → New using ODA. 3.txt located in the WebSphereAdapters\repository\SAP directory. 1. This is only required if a Business Object is built from scratch. skip this dialog box and click Cancel. In the Business Object Designer. 4. Therefore... 8.. Select Create New Business Object to open the Business Object Designer. Click on the Find Agents button. Use Case 1: WBIMB using WBI Adapter for mySAP. 5. 2. In the Business Object Designer. Open the MaterialSynchronization_Lib Integration Component Library folder and right-click the folder Business Objects...Figure 7-90 Create new User Project Create Business Object for the MATMAS IDoc Use the System Manager to open the Business Object Designer tool.. 6. Select the file BO_SAPIdocControl. select File → Open from file.com 277 . The dialog box that appears asks for a Business Object name. 7. The file contains the Idoc control structure that is a prerequisite for all SAP ALE Business Objects. Select the SAP ODA to connect to (see Figure 7-91 on page 278) and click Next. Chapter 7.

Figure 7-91 Select the SAP ODA in the Business Object Wizard 9. Recommended location: < install directory>/repository/SAP/ 278 WebSphere Business Integration for SAP . Table 7-12 ODA configuration parameters Item Username Password Client ASHostname FileDestination Description SAP logon user name SAP logon password SAP logon client Host name of SAP server Location to save ODA generated files. Enter the SAP system properties and click Next (see Table 7-12 and Figure 7-92 on page 279).

Figure 7-92 Properties in the Business Object Wizard 10. Chapter 7. Figure 7-93 Select the IDoc in the Business Object Wizard 11.Browse the system for the source IDoc type MATMAS03 in the folder IDoc Types.com 279 . Generate from System and click Next (see Figure 7-93).Confirm the selection and click Next (see Figure 7-94 on page 280). Use Case 1: WBIMB using WBI Adapter for mySAP.

The business object definition is saved to both repositories.Save the Business Object Definition to the System Manager by selecting the option Save and also save the Business Object Definition to a separate file by selecting the option Save a copy of the business object definition to a separate file to the connectors’ repositories (for example.Figure 7-94 Verify the selection in the Business Object Wizard 12. because both connectors are using the business object definition. 280 WebSphere Business Integration for SAP . c:\WebSphereAdapters\repository\SAP and c:\WebSphereAdapters\repository\SAP_2).Review the BO properties and click OK (see Figure 7-95). Figure 7-95 Supply additional information in the Business Object Wizard 13.

Chapter 7. In the System Manager perspective the Business Objects are now displayed in the MaterialSynchronization_Lib Integration Component Library (see Figure 7-97 on page 282).14.Go to the General tab and add the message type of the IDoc to the verb that is used. Use Case 1: WBIMB using WBI Adapter for mySAP. Figure 7-96 Add the IDoc message type in the application specific information 15. The message type in this case is MATMAS (see Figure 7-96).Save the Business Object Definition again to the System Manager and to the connectors’ repositories.com 281 .

282 WebSphere Business Integration for SAP . 3. Select the MaterialSynchronization_Proj User Project by right-clicking it and select Update Project.Figure 7-97 Business Objects in the Integration Component Library 1. select MaterialSynchronization_Lib and click Finish. 2. The MaterialSynchronization_Proj user Project contains now the Business Objects (see Figure 7-98 on page 283). In the Dialog Box.

2 Create Business Object for the ABAP Extension Module Use the Business Object Designer to generate a business object definition from scratch for the ABAP Extension Module. Use Case 1: WBIMB using WBI Adapter for mySAP.3. it is not necessary to create a second Business Object definition of the IDoc type MATMAS03 for the second connector. Chapter 7.Figure 7-98 Business Objects in the User Project In a later step (see 7. the System Manager must be launched.com 283 .7. To start the Business Object Designer tool. 7. Because both connectors are using the same application specific Business Objects for the ALE and ABAP Extension modules they can use the same Business Object definitions. a simple flat business object was used. the Business Objects are exported from the user Project to the Message Brokers Toolkit. The Business Objects are saved into the System Manager to deploy them in a later step to the Message Brokers Toolkit. Therefore. “Create Message Sets and loading Business Object Definitions” on page 288). In this Use Case.7.

284 WebSphere Business Integration for SAP .Start the WebSphere Business Integration System Manager The Business Object Designer tool can be started using the System Manager. enter OrderEventNotification_Proj. – In the Project name. To start the System Manager. Figure 7-99 Business Objects in the Integration Component Library In the System Manager perspective. the System Manager is used to save Business Objects and to deploy them as Message definition files into the Message Brokers Toolkit. – Select the project OrderEventNotification_Lib as the Integration Component Library and click Finish (see Figure 7-100 on page 285). select Start → Programs → IBM WebSphere Business Integration Adapters → Adapters → Tools → System Manager. – Right-click on the User Projects folder and select New User Project → New Message broker project. In the System Manager perspective. create a new Integration Component Library named OrderEventNotification_Lib (see Figure 7-99). create a new User Project named OrderEventNotification_Proj. Also.

com 285 . Use Case 1: WBIMB using WBI Adapter for mySAP. 3. 2. Enter the name of the business object. The upcoming dialog box asks for a Business Object name. Right-click on the Business Objects folder.Figure 7-100 New User Project Create a Business Object for the ABAP Extension Module Perform the following steps to generate a business object definition: 1. BO_EVENTRIGGER. for example. In the Attribute Tab of the new business object window. Select Create New Business Object to open the Business Object Designer. Leave the application specific information blank and click OK. 2. enter the attributes shown in Figure 7-101 on page 286. Chapter 7. These attributes are also defined in the ABAP Extension Module in SAP (Figure 7-86 on page 272). Open the Integration Component Library folder OrderEventNotification_Lib. 1.

5. Select the General tab.Retrieve 286 WebSphere Business Integration for SAP . Enter the application specific information value :/CWLD/DYNAMIC_RETRIEVE in the Retrieve verb field (see Figure 7-102).Figure 7-101 Business Object for the ABAP Extension module 4. Figure 7-102 Application specific information .

because both connectors are using the business object definition. Figure 7-103 Business Objects in the Integration Library 8. Right-click it and select Update Project. c:\WebSphereAdapters\repository\SAP and c:\WebSphereAdapters\repository\SAP_2). Chapter 7. In the System Manager. Select the OrderEventNotification_Proj User Project.com 287 . the Business Objects are now displayed in the Integration Component Library (see Figure 7-103). 9. Use Case 1: WBIMB using WBI Adapter for mySAP.6. The business object definition is saved to both repositories.The User Project contains now the Business Objects for the ABAP Extension Module (see Figure 7-104 on page 288). select the Integration Component Library OrderEventNotification_Lib and click Finish. 10. Save the Business Object Definition to the System Manager by selecting the option Save and also save the Business Object to a separate file by selecting the option Save a copy of the business object definition to a separate file to the connectors’ repositories (for example. 7. In the Dialog Box.

Specify the message broker importer path. a. the Business Objects are exported from the user Project to the Message Brokers Toolkit.7. 1.Figure 7-104 Business Object in the User Project In the next section. Open the System Manger by selecting Start → Programs → IBM WebSphere Business Integration Adapters → Tools → System Manger. for example.3 Create Message Sets and loading Business Object Definitions Once the business object definitions for the ALE and the ABAP Extension module have been created. 288 WebSphere Business Integration for SAP .exe. First of all. 7. define the preferences of the broker in the System Manager by selecting Windows → Preferences. c:\WBIMB\eclipse\mqsicreatemsgdefs. they must be imported to the WebSphere Business Integration Message Broker using the Message Broker Toolkit and the System Manager. 2.

b. Select Deploy to Message Broker workspace (see Figure 7-106 on page 290).com 289 . for example. Use Case 1: WBIMB using WBI Adapter for mySAP. and click OK (see Figure 7-105 on page 289).Broker preferences 3. in the System Manager perspective. Specify the workspace directory. the MaterialSynchronization_Proj User Project and right-click on it. Figure 7-105 System Manager . Select. Chapter 7. c:\WBIMB\eclipse\workspace. 4.

select all the Business Objects and click Next (see Figure 7-107 on page 291). 290 WebSphere Business Integration for SAP .Figure 7-106 Deploy to Message Broker workspace 5. In the upcoming Dialog Box.

as the Message Set. MaterialSynchronization_MsgSet. Chapter 7. Set the XML Namespace format to short (see Figure 7-108 on page 292).Figure 7-107 Deploy the Business Objects to the Message Broker Toolkit 6. Enter.com 291 . and select the option Namespace aware. Use Case 1: WBIMB using WBI Adapter for mySAP.

A Dialog Box confirms that the Business Objects were deployed to the Message Broker Toolkit (see Figure 7-109). it must be configured to work with WebSphere Business Integration Adapters. 292 WebSphere Business Integration for SAP . Also. the graphical mapping tool and the code utility can be utilized. Therefore. Open the Broker’s Toolkit by selecting Start → Programs → IBM WebSphere Business Integration Message Brokers → Message Brokers Toolkit. Figure 7-109 Deploy the Business Objects to the Message Broker Toolkit By deploying the Business Objects to the Message Broker Toolkit. Click Finish.Figure 7-108 Deploy the Business Objects to the Message Broker Toolkit 7. namespaces are created for the message set. 1. Configure the Message Set After the Message Set MaterialSynchronization_MsgSet is created. a MessageSet Project named MaterialSynchronization_MsgSet and a Message Set named MaterialSynchronization_MsgSet are created that contain xsd and mxsd files.

Click OK. Use Case 1: WBIMB using WBI Adapter for mySAP. Figure 7-110 Define the CwXML format b. Right-click on Physical properties and select Add XML Wire Format (see Figure 7-110). Figure 7-111 Define the CwXML format 3.2. In the dialog box. Set the Default Wire Format in the messageSet. Switch to the Broker’s Administration perspective and define an XML wire format name called CwXML. Set the Runtime Parser in the messageSet.com 293 .mset file to MRM (see Figure 7-112 on page 294). 4. 5.mset file to CwXML (see Figure 7-112 on page 294). a. enter CwXML in the Name field (see Figure 7-111). Chapter 7.

Save the messageSet. Close the Message Broker Toolkit.Figure 7-112 Message set Default Wire Format and Runtime Parser 6. a. d. 7. 294 WebSphere Business Integration for SAP .cfg. b. In a later step (7.mset file. 8. Update the connector configuration with the message set ID of the Message Set MaterialSynchronization_MsgSet. the Business Objects and other components are deployed to the broker’s run-time environment using the Message Broker Toolkit. Repeat the steps above to deploy OrderEventNotification_Proj to the Message Set OrderEventNotification_MsgSet. c. “Create Message Sets and loading Business Object Definitions” on page 288). Start the Connector Configurator by selecting Start → Programs → IBM WebSphere Business Integration Adapters → Tools → Connector Configurator. Navigate to the connector’s repository directory and open the file SAPConnector.3. Select Open → From File. Switch to the Supported Business Objects tab and enter in the Message Set ID field the Message Set ID of the Message Set MaterialSynchronization_MsgSet (see Figure 7-43 on page 224).7.

In the Broker Application Development perspective. 7. transforms. a project in the Broker Administration Toolkit must be created. The message flow also transforms the Business Object and passes the output SAP ALE Business Object to a second queue.8 Development of a message flow for the MaterialSynchronization (ALE Module) scenario A message flow application is a program that routes. Also. Right-click on the Message Flow Project and select New > Broker Schema. This sections describes how to create a message flow that takes a SAP ALE Business Object from one queue and copies values of the SAP ALE Business Object to a second SAP ALE Business Object. Chapter 7. b. Use Case 1: WBIMB using WBI Adapter for mySAP. c. In the Project Name field.7. A new project called MaterialSynchronization_MsgFlowProj is displayed in the workspace (see Figure 7-113 on page 296). Select File → New → Message Flow Project. create a message flow project called MaterialSynchronization_MsgFlowProj: a. A message flow is deployed and runs in a broker. and manipulates messages. for example MaterialSynchronization_Schema.8. type MaterialSynchronization_MsgFlowProj. Enter a name for the schema.1 Create a Message Flow Project Before you start adding and configuring message flow nodes.com 295 . a message flow file and a message flow schema must be created: 1. and then click Finish.

e. click on MaterialSynchronization_MsgFlowProj to highlight it. c. create the MaterialSynchronization_MsgFlow message flow in the MaterialSynchronization_MsgFlowProj: a. b. In the Name field.Figure 7-113 Create a new message flow project 2. Ensure that the Project field contains MaterialSynchronization_MsgFlowProj (see Figure 7-114 on page 297). type MaterialSynchronization_MsgFlow. Add the schema. d. In the Resource Navigator view. Select File → New → Message Flow. 296 WebSphere Business Integration for SAP . In the Broker Application Development perspective. and then click Finish.

2 Build the message flow This section describes how to implement a message flow and transform business objects using ESQL. Add and connect nodes On the left-side of the Message Flow editor is the Node Palette. which has a list of all the nodes available for to use in the message flow (see Figure 7-115 on page 298). Chapter 7. Use Case 1: WBIMB using WBI Adapter for mySAP.Figure 7-114 Create a new message flow 7.8.com 297 .

though not all. nodes have at least one terminal with which to connect them to other nodes. To build the message flow: 1. Repeat steps 1 and 2 to add a Compute node and an MQOutput node to the canvas. The MQInput node has three terminals. then click somewhere on the canvas. Click the MQInput node to select it from the Node Palette. 298 WebSphere Business Integration for SAP . To define the order that the nodes process an input message. connect them together. The terminals on the MQInput node are labelled Failure. as shown in Figure 7-116 on page 299. 2. the white area to the right of the Node Palette. Out. Make sure that the Selection button (above the Node Palette) is highlighted so that nodes from the Node Palette can be selected. Hover the mouse pointer over each terminal to highlight it and to display its label. 3. Most. and Catch. to add the node to the message flow.Figure 7-115 The MaterialSynchronization_MsgFlow message flow nodes.

The MaterialSynchronization_MsgFlow message flow files and folders in the Resource Navigator view are also highlighted with crosses.1. The error in the Compute node is because no ESQL module. which are indicated by a small white cross on a red background on the MQInput and Compute nodes. was created. To save the MaterialSynchronization_MsgFlow message flow. which defines how the Compute node process input messages. 3. from which the MQInput node takes input messages. The canvas looks similar to the canvas shown in Figure 7-116. Connect the Out terminal of the Compute node to the In terminal of the MQOutput node. as shown in Figure 7-116. Move the mouse pointer and click on the In terminal of the Compute node so that the arrow connects the MQInput node to the Compute node. 4.msgflow. Click on the Connection button (above the Node Palette) so that the nodes can be connected together. Notice that a thin black line with an arrow head appears. the Message Brokers Toolkit validates the message flow. Click on the Out terminal of the MQInput node. 2. select File → Save MaterialSynchronization_MsgFlow. When saving a message flow file. The MaterialSynchronization_MsgFlow message flow has two errors. was entered. Figure 7-116 The MaterialSynchronization_MsgFlow message flow validated. Chapter 7.com 299 . A brief description of each error is given in the Tasks view below the Message Flow editor: The error in the MQInput node is because no name of the input queue. The following sections describe how the errors can be fixed by configuring the nodes. Use Case 1: WBIMB using WBI Adapter for mySAP.

Click on the Selection button at the top of the Node Palette. type MRM. On the Default page in the Message Set field. Configure the node properties To configure the properties of a node: 1. Perform steps 1 and 2 to configure each node as follows: Configure the MQInput node To configure the MQInput node: 1. On the Default page in the Message Domain field. Right-click on the node and then click Properties. type the name of the message set and the message set id. the MQOutput node puts the output message to the SAP_2CONNECTOR/REQUESTQUEUE. sap_matmas03. Open the Properties dialog box for the MQInput node (see Figure 7-117 on page 301). 2. In the MaterialSynchronization_MsgFlow message flow. On the Basic page in the Queue Name field. 300 WebSphere Business Integration for SAP . for example. for example. the Compute node builds an output message that contains a copy of the header and transformed content of the input message.3 Configure the message flow In the MaterialSynchronization_MsgFlow message flow. 3. MaterialSynchronizationMsgSetProj (NUTU955002001). After the Compute node has processed the message. 4.7. when the Compute node receives the input message from the MQInput node. 2. 5. type CwXML. To configure the message flow. the ESQL module that transforms the message must be implemented. On the Default page in the Message Type field. the MQInput node takes an input message from the SAPConnector’s Deliveryqueue called SAPCONNECTOR/DELIVERYQUEUE and passes it to the Compute node. 6. type SAPCONNECTOR/DELIVERYQUEUE. type the name of the business object. two WebSphere MQ local queues must have been created (refer to “Define the queues” on page 207): SAPCONNECTOR/DELIVERYQUEUE SAP_2CONNECTOR/REQUESTQUEUE Also. On the Default page in the Message Format.8.

Configure the Compute node Do not edit any of the properties in the Compute node but take a look at the properties to see what has caused the error: 1. Chapter 7. On the Basic page of the Properties dialog box. type SAP_2CONNECTOR/REQUESTQUEUE. notice that the ESQL Module field contains MaterialSynchronization_MsgFlow_Compute. Open the Properties dialog box for the Compute node.com 301 . Save MaterialSynchronization_MsgFlow.msgflow (press Ctrl-S). Click OK to close the Properties dialog box. 8. ESQL is held in a separate file called. Configure the MQOutput node To configure the MQOutput node: 1. On the Basic page in the Queue Name field.Figure 7-117 MQ Input Node Properties 7. Click OK to close the Properties dialog box. 2. This value is entered automatically when the node is created because the Compute node must contain some ESQL. The Queue Manager Name field can be left empty because the SAP_2CONNECTOR/REQUESTQUEUE queue is on the same queue manager as the SAPCONNECTOR/DELIVERYQUEUE queue. 2. Open the Properties dialog box for the MQOutput node. Use Case 1: WBIMB using WBI Adapter for mySAP. The error on the MQInput node is no longer displayed. in this case.

all the ESQL for the MaterialSynchronization_MsgFlow message flow is stored in a file called MaterialSynchronization_MsgFlow.esql file is created. When the MaterialSynchronization_MsgFlow. 7. When the MaterialSynchronization_MsgFlow. All of the ESQL that belongs to a message flow is stored. 3.esql file is created.esql does not yet exist. it already contains the minimum ESQL that is needed for the Compute node to 302 WebSphere Business Integration for SAP . This section shows you how to implement ESQL natively: 1. Right-click the Message SetProject and select Rebuild Project. and then click on Open ESQL. However.esql. Switch to Project References and select the Message Set Project. 5.esql.8. it automatically opens in the ESQL editor. by default. Right-click the Message Flow Project and select Rebuild Project. Before implementing the ESQL.esql. 7.MaterialSynchronization_MsgFlow. In this case.4 Write ESQL for the Compute node This ESQL demonstrates how to construct a business object for the ALE module of the adapter. By doing this. Switch to Project References and select the Message Flow Project. Right-click on the Message Flow Project and select Properties.esql does not already exist so the Message Brokers Toolkit creates the file in the MaterialSynchronization_MsgFlow Messageflow Project. associate the Message Flow Project with the Message Set Project and vice versa.esql and how to write some simple ESQL for the Compute node. Right-click the Message Set Project and select Properties. an error is displayed in the Tasks view because the file MaterialSynchronization_MsgFlow. Switch to the Resource Perspective. Create the ESQL file To create MaterialSynchronization_MsgFlow. 3. The next section describes how to create MaterialSynchronization_MsgFlow. Also. the ESQL code compilation feature can be utilized. 2. MaterialSynchronization_MsgFlow. Click Cancel to close the Properties dialog box without saving any changes. 4. in a single file. right-click on the Compute node. the graphical mapping feature can be used to transform messages. 6.

esql tab to display MaterialSynchronization_MsgFlow. END WHILE.msgflow. END. or a Database node. The ESQL for the MaterialSynchronization_MsgFlow_Compute module is as follows: CREATE COMPUTE MODULE MaterialSynchronization_MsgFlow_Compute CREATE FUNCTION Main() RETURNS BOOLEAN BEGIN --CALL CopyMessageHeaders().esql and MaterialSynchronization_MsgFlow.*[]). do the following: 1.esql in the ESQL editor again. CREATE PROCEDURE CopyMessageHeaders() BEGIN DECLARE I INTEGER 1. CREATE PROCEDURE CopyEntireMessage() BEGIN SET OutputRoot = InputRoot.*[I]. The MaterialSynchronization_MsgFlow_Compute ESQL module In the MaterialSynchronization_MsgFlow. DECLARE J INTEGER CARDINALITY(InputRoot.esql for the new node.*[I] = InputRoot.msgflow. Close both MaterialSynchronization_MsgFlow. Click on the MaterialSynchronization_MsgFlow. This is the ESQL module that is referenced from the Compute node Properties dialog box. END. WHILE I < J DO SET OutputRoot.successfully validate.esql (Ctrl-S) and then click on the MaterialSynchronization_MsgFlow. Open MaterialSynchronization_MsgFlow. a new ESQL module is also created in MaterialSynchronization_MsgFlow. Save MaterialSynchronization_MsgFlow.com 303 . Use Case 1: WBIMB using WBI Adapter for mySAP. 2.esql file. If another Compute node. Chapter 7. is added to the MaterialSynchronization_MsgFlow message flow. RETURN TRUE. there is a single module of ESQL called MaterialSynchronization_MsgFlow_Compute. SET I = I + 1. and then right-click on the Compute node and click Open ESQL. --CALL CopyEntireMessage().msgflow tab to return to the Message Flow editor. The error on the Compute node is no longer displayed and no items relating to this task appear in the Tasks view. If the ESQL file does not automatically generate some ESQL.

a project in the Broker Administration Toolkit must be created. In the Broker Application Development perspective. Therefore. 7.) and the fifth line (--CALL CopyEntireMessage(). To uncomment the lines. type OrderEventNotification_MsgFlowProj. The fourth line (--CALL CopyMessageHeaders(). and configuring message flow nodes. Also. create a message flow project called OrderEventNotification_MsgFlowProj: a. a message flow file must be created: 1.9 Development of a message flow for the OrderEventNotification (ABAP Extension Module) scenario A message flow application is a program that routes.9. For the Material Synchronization scenario to implement the ESQL.1 Create a Message Flow Project Before starting. The Compute node now parses the lines that instruct the Compute node to copy the header and content of the input message to the output message. it builds an output message without any content. refer to “ESQL module” on page 648.from the start of each line. 2. transforms. END MODULE. adding. Save MaterialSynchronization_MsgFlow. This section describes how to create a simple pass through message flow for the ABAP Extension Module Business Object. Select File → New → Message Flow Project.END. and manipulates messages. the ESQL must be edited: 1. When the Compute node receives the input message. The message that the MQOutput node puts to the OUT queue has the same content as the message that the MQInput node got from the IN queue. b. A new project called OrderEventNotification_MsgFlowProj is displayed. delete -.) of the MaterialSynchronization_MsgFlow_Compute module are commented out so that the Compute module does not parse them. 304 WebSphere Business Integration for SAP .esql. In the Project Name field. and then click Finish (see Figure 7-118 on page 305). The ESQL that is automatically generated does not produce any output. 7. A message flow is deployed and running in a broker.

Use Case 1: WBIMB using WBI Adapter for mySAP. b. In the Name field. d. click on OrderEventNotification_MsgFlowProj to highlight it.Figure 7-118 Create a new message flow project 2. Ensure that the Project field contains OrderEventNotification_MsgFlowProj (see Figure 7-119 on page 306). e. c. create the OrderEventNotification_MsgFlow message flow in the OrderEventNotification_MsgFlowProj: a. Select File → New → Message Flow. and then click Finish. type OrderEventNotification_MsgFlow. Leave the Schema field empty so that the message flow is created in the default schema. In the Broker Application Development perspective. Chapter 7. In the Resource Navigator view.com 305 .

2 Build the message flow This section describes how to implement a simple pass through message flow without computing node. which is a list of all the nodes available for use in the message flow (see Figure 7-120 on page 307).9. Add and connect nodes On the left side of the Message Flow editor is the Node Palette. 306 WebSphere Business Integration for SAP .Figure 7-119 Create a new message flow 7.

and Catch. Repeat steps 1 and 2 to add a MQOutput node to the canvas. to add the node to the message flow. Hover the mouse pointer over each terminal to highlight it and to display its label. Click the MQInput node to select it from the Node Palette. Click on the Connection button (above the Node Palette) so that the nodes can be connected together. the white area to the right of the Node Palette.com 307 . To define the order that the nodes process an input message. Use Case 1: WBIMB using WBI Adapter for mySAP. The MQInput node has three terminals. nodes have at least one terminal with which to connect them to other nodes. 2. connect them together.Figure 7-120 The message flow nodes To build the message flow: 1. 3. as shown in Figure 7-121 on page 308. The terminals on the MQInput node are labelled Failure. 1. Make sure that the Selection button (above the Node Palette) is highlighted so that nodes from the Node Palette can be selected. Out. though not all. then click somewhere on the canvas. Most. Chapter 7.

2. Right-click on the node. The canvas looks similar to the one shown in Figure 7-121. select File → Save OrderEventNotification_MsgFlow. two WebSphere MQ local queues must be available: SAPCONNECTOR/DELIVERYQUEUE SAP_2CONNECTOR/REQUESTQUEUE Configure the node properties To configure the properties of a node: 1.msgflow. Perform steps 1 and 2 to configure each node as follows: Configuring the MQInput node To configure the MQInput node: 1. Open the Properties dialog box for the MQInput node. type SAPCONNECTOR/DELIVERYQUEUE.9. Notice that a thin black line with an arrow head appears. 308 WebSphere Business Integration for SAP . and then click Properties. It puts the output message in the SAPCONNECTOR/REQUESTQUEUE. Click on the Out terminal of the MQInput node. 3. 3. On the Basic page in the Queue Name field. type MRM. To configure the message flow. 2. 2. Move the mouse pointer and click the In terminal of the MQOutput node. To save the MaterialSynchronization_MsgFlow message flow. On the Default page in the Message Domain field.3 Configure the message flow In the OrderEventNotification_MsgFlow message flow. the MQInput node takes an input message from the SAPConnector’s Deliveryqueue called SAP_2CONNECTOR/DELIVERYQUEUE and passes it to the MQOutput node. Figure 7-121 The pass through message flow 7. Click on the Selection button at the top of the Node Palette.

for example.com 309 . On the Basic page in the Queue Name field. type CwXML (see Figure 7-122). BO_EVENTRIGGER. On the Default page in the Message Set field. 2. for example. 5. The Queue Manager Name field can be left empty because the SAP_2CONNECTOR/REQUESTQUEUE queue is on the same queue manager as the SAPCONNECTOR/DELIVERYQUEUE queue. Use Case 1: WBIMB using WBI Adapter for mySAP. Save OrderEventNotification_MsgFlow. 6. 8. Click OK to close the Properties dialog box. On the Default page in the Message Type field. OrderEventNotificationMsgSetProj (NUTU955002001). On the Default page in the Message Format. Click OK to close the Properties dialog box. type SAP_2CONNECTOR/REQUESTQUEUE. Open the Properties dialog box for the MQOutput node. type the name of the message set and the message set ID. type the name of the business object. Chapter 7. The error on the MQInput node is no longer displayed.4.msgflow (Ctrl-S). Figure 7-122 MQ Input Node Properties 7. Configure the MQOutput node To configure the MQOutput node: 1.

bar. ITSOA_Archive. 310 WebSphere Business Integration for SAP .10. There are two methods of deployment that can be used to deploy resources in the Message Broker Toolkit. Right-click on the message broker archive file and select Deploy File from the context menu that is displayed. In the Broker Administration perspective. Add the message flows MaterialSynchronization_MsgFlow and OrderEventNotification_MsgFlow and the message sets MaterialSynchronization_MsgSet and OrderEventNotification_MsgSet to the broker archive. Deploy a message broker archive using Deploy File Deploy a message broker archive using Deploy File: 1. by selecting New → Message Brokers → Message Broker Archive). This shows brokers and their execution groups in the broker domain. This section describes how to deploy a archive using the option Deploy File.1 Deploy a message broker archive There are several ways to deploy a message broker archive within the Message Brokers Toolkit.10 Deployment of the message flow applications Deployment is the method used to send message flows to execution groups within brokers.bar.7. however. for example. The Deploy a BAR File wizard is displayed. Save the broker archive file ITSOA_Archive. this is beyond the scope of this book. although both require that a connection to the Configuration Manager has been established. 4. as shown in Figure 7-123 on page 311. open the message broker archive file to deploy in the Broker Administration Navigator view (create a file with the file extension. There is also an additional method of deploying resources using the mqsideploy utility on the command line.bar. This section shows you how to deploy a message flow application to a broker using a broker archive. 5. 7. 3. 2.

A confirmation message is received from the Configuration Manager if the deploy operation was successful. Click on OK to perform the deploy operation. Chapter 7.com 311 . Select the execution group default to deploy the message broker archive file.Figure 7-123 Deploy broker archive file 6. Use Case 1: WBIMB using WBI Adapter for mySAP. but the Event Log in the Message Brokers Toolkit can be checked for the following success messages in the Event Log in the Message Brokers Toolkit to determine if the deploy operation was successful: BIP2056 and BIP4040.

11 Run the business scenario This section shows you how to run both scenarios of the Use Case: the MaterialSynchronisation. In the inbound SAP application. – Click Execute (F8) (see Figure 7-124 on page 313).7. – Set the Logical system to WBI. Start the second connector by double-clicking on the shortcut on the desktop. 312 WebSphere Business Integration for SAP . open transaction smgw to verify that the connector is connected. In the outbound SAP application.1 Part 1: Run the MaterialSynchronisation (ALE) scenario Start the message flow MaterialSynchronization_MsgFlow using the Message Broker’s Toolkit and make sure the message flow OrderEventNotification_MsgFlow is stopped. – Select Send Material in full.and the OrderEventNotification scenarios.11. Start the first connector by double-clicking on the shortcut on the desktop. In the outbound SAP application. open transaction smgw to verify that the second connector is connected. – Set the message type to MATMAS. open transaction bd10 to send a material: – Add a material. 7.

open transaction we02 to verify that the IDoc was delivered to the connector (see Figure 7-125 on page 314).com 313 . Use Case 1: WBIMB using WBI Adapter for mySAP. Chapter 7.Figure 7-124 Transaction bd10 .Send Material In the outbound SAP application.

Figure 7-125 Transaction we02 . open transaction we02 to verify that the IDoc was delivered to the SAP system (see Figure 7-126 on page 315). 314 WebSphere Business Integration for SAP .outbound IDoc log information In the inbound SAP application.

Creating a Sales Order in SAP. Starting the Adapter for mySAP.2 Part 2: Run the OrderEventNotification (ABAP Extension Module) Scenario This section contains the following topics: Starting the message flow OrderSynchronization_MsgFlow using the Message Broker’s Toolkit and making sure the message flow MaterialSynchronization_MsgFlow is stopped. Starting the Visual Test Connector. – As soon as the sales order is created. The connector sends a empty business object to SAP R/3.com. an event notification is send to the connector.Figure 7-126 Transaction we02 . Chapter 7.11.com 315 . Use Case 1: WBIMB using WBI Adapter for mySAP.inbound IDoc log information 7.

Figure 7-127 Test Connector 2. (see Figure 7-128 on page 317).. Start the Visual Test Connector by selecting Start → Programs → IBM WebSphere Business Integration Adapter → Tools → Visual Test Connector. In the Visual Test Connector. 316 WebSphere Business Integration for SAP . select File → Create/Select Profile. Viewing the result in the Visual Test Connector..– SAP populates that business object with the sales order data and sends the populated business object back to the connector. Starting the Visual Test Connector 1. The window in Figure 7-127 should appear.

Figure 7-128 Test Connector . Figure 7-129 Test Connector .Create/Select Profile 3.com 317 .Connector Profile Chapter 7. Create a new Profile by clicking on the Create new Profile button. Use Case 1: WBIMB using WBI Adapter for mySAP.

SAP_2Connector profile 9. Figure 7-131 Test Connector . Browse for the connector configuration file by clicking on the Browse button. select File → Connect to start the test connector (see Figure 7-132 on page 319). In the menu. Define the broker type. 7. for example. 318 WebSphere Business Integration for SAP . 6. select WMQI. Click OK (see Figure 7-130). Figure 7-130 Test Connector . 5. Since Message Broker is used in this Use Case.New Profile 8. SAP_2Connector. Double-click on the new entry SAP_2Connector (see Figure 7-131).4. Enter the name of the connector.

Create a Sales Order In SAP R/3 Create a sales order in SAP R/3 to test that the environment is set up properly. Use Case 1: WBIMB using WBI Adapter for mySAP. The window in Figure 7-133 on page 320 should appear. 1. it polls for events and it picks up the event as soon as a sales order is created in SAP. When the event notifies the connector. When the connector is up and running.bat shortcut on the desktop. Go to the Create Sales Order transaction (va01).Connect Start the SAPConnector Start the SAPConnector by double-clicking on the start_SAP.Figure 7-132 Test Connector . the connector sends the empty business object BO_EVENTRIGGER to SAP R/3. Chapter 7. SAP R/3 populates this business object with data from the sales order table VBAK and sends it back to the connector.com 319 .

Enter the values shown in Figure 7-134 on page 321 and click on Save. 3. and then press Enter. The Create Sales Order: Overview view appears. Type OR (standard order) as the Order Type.Figure 7-133 Transaction va01: Create Sales Order 2. 320 WebSphere Business Integration for SAP .

Chapter 7.com 321 . The message that states Standard Order has been saved appears. Click Save. Use Case 1: WBIMB using WBI Adapter for mySAP.Figure 7-134 Creating a Standard sales order 4. look at the bottom left corner. In the window that follows (Figure 7-135 on page 322).

Figure 7-135 Standard Order created View the result As soon as the order is created. 1. The connector passes the business object to the broker (see Figure 7-136 on page 323). SAP populates that business object with the sales order data and sends the populated business object back to the connector. 2. the connector picks up the event and sends a empty business object to SAP R/3. 322 WebSphere Business Integration for SAP .

Figure 7-136 Connector trace 3. Use Case 1: WBIMB using WBI Adapter for mySAP. The broker passes the business object through the simple message flow to the Visual Test Connector. Chapter 7.com 323 .

324 WebSphere Business Integration for SAP . The populated business object can be reviewed in the Visual Test Connector by double-clicking on it (see Figure 7-138 on page 325). Figure 7-137 Incoming business object 5. The populated business object arrives in the Test Connector (see Figure 7-137).4.

the DOS command prompt window must be used. 7.12 Usage of the Message Broker’s trace to locate errors To trace the message broker. 1. Use Case 1: WBIMB using WBI Adapter for mySAP. First the trace must be started by entering the command mqsichangetrace <MYBROKERNAME> -u -e <EXECUTIONGROUP> -l debug -r (see Figure 7-139 on page 326) Chapter 7.com 325 .Figure 7-138 Review the business object data in the Test Connector View the log information in the CrossWorld’s station by clicking on the View Log button using transaction /CWLD/HOME.

perform the following two commands: mqsireadlog <MYBROKERNAME> R -u -e <EXECUTIONGROUP> -o Trace1 mqsiformatlog -i Trace1 -o Trace1. which is easy to expand with new interfaces.13 Summary This Use Case describes the complete development lifecycle of an application integration scenario developed with the WebSphere Business Integration Message Broker Toolkit and executed on a WebSphere Message Broker run-time environment with WebSphere Business Integration Adapters. The key capability is the implementation of a central interface infrastructure. The added value of using the ABAP Extension Module is the event notification mechanism in SAP R/3. Also.txt with a text editor to view the trace information.com.Figure 7-139 Activate trace 2. this Use Case describes the ABAP Extension Module of the WebSphere Business Integration Adapter for mySAP. 7. To read the trace.txt 3. 326 WebSphere Business Integration for SAP . which is described in this chapter. and to enable a Enterprise Service Bus. Open the file Trace1.

Use Case 2: WBISF using WBI Adapter for mySAP. 2004.com This Use Case describes how to develop a new business process with WebSphere Studio Application Developer Integration Edition V5.1 and execute it on WebSphere Business Integration Server Foundation. This process is a people-centric enterprise integration approach that incorporates various existing enterprise services to choreograph new business processes. This chapter contains the following topics: Operational model Installation of WebSphere Business Integration components Configuration of WebSphere Business Integration components Development of the business process Deployment of the business process Running the scenario © Copyright IBM Corp.8 Chapter 8. 327 . All rights reserved.

Depending on the reply of the policy service. “Use Case 2 Solution overview” on page 126. This arrangement is only an example of what data a user has to provide. The second process activity checks if the requested material requires an approval or not. These input values are exemplary and do not claim to be a pattern for internal ordering. the user immediately gets a reply that the request is sent. After submission.1 Operational model This Use Case describes an Internal Order scenario that utilizes several existing enterprise services and some newly created services to compose a new business process. the order is directly placed in the enterprise 328 WebSphere Business Integration for SAP . This is done by querying an existing policy system via a Web Service interface.com is used to connect to the SAP back-end system and retrieve data. The WebSphere Business Integration Adapter for mySAP.8. The first enterprise service access retrieves the mail address of the originating user from the existing Human Resource system. Order quantity. To do so. The new process consumes data from the following services: Human Resource system running on SAP and accessed via SAP Remote Function Calls (RFCs) Enterprise Procurement system running on SAP and accessed via SAP RFCs Enterprise policy service exposed with standard Web Services Notification service running on a J2EE application server and accessed via Web Services The business details of this process flow are described in 5. Any employee is able to start a new internal order process by providing some data and submitting the request.7. Employee number. Material number. There are various other combinations that would also make sense. The status of the request can be monitored to verify where the request is currently processed. The internal order requisition needs the following input data: An order description that has a human readable identifier. The run-time environment is a WebSphere Business Integration Server Foundation. Delivery plant. Desired delivery date. the user has to be logged in and authenticated via a standard Web browser.

The approver is an authorized employee who can see all incoming requests in a special inbox. routing. If a request is approved. The Use Case does not provide a custom front-end application. The existing notification service is used in any case to inform the requestor about the result of the request. it is routed to the enterprise procurement system where the internal purchase order is placed. the standard WebSphere Process Choreographer Web client is used to simulate process invocation. Use Case 2: WBISF using WBI Adapter for mySAP. Figure 8-1 Operational model Chapter 8. Instead. the approver decides to approve or decline a request. and execution. The operational model in Figure 8-1 shows how the subcomponents communicate with each other and where they are physically installed.com 329 . Based on the request information. staff interaction.procurement system or routed to a functional approver. The notification service uses the existing e-mail infrastructure to deliver the result to the correct person.

Business process development environment. IBM WebSphere MQ 5.com 8.1 FP2 5.8.1 330 WebSphere Business Integration for SAP . The section covers the following tasks: Installing WebSphere Studio Application Developer Integration Edition (WSADIE) Installing WebSphere Business Integration Server Foundation (WBISF) Installing Remote Agent Controller Installing WebSphere Business Integration Adapter Framework Installing WebSphere Business Integration Adapter for mySAP. Provides message based connectivity between the WBI connector and the integration broker.1 Plan the installation Table 8-1 lists the prerequisite software for this Use Case and why you need to install it.3 CSD05 IBM WebSphere Business Integration Server Foundation IBM WebSphere Studio Application Developer Integration Edition IBM Remote Agent Controller 5.1 5.2.2 Installation of WebSphere Business Integration components This section describes how to install the WebSphere Business Integration components that are required to implement this Use Case. Compilation of generated business object of the mySAP.1 FP 5 1. Integration broker in this Use Case.com Adapter. Table 8-1 Software prerequisite list Prerequisite software IBM DB2 IBM Java Development Kit Version 8.1 What the software is for WebSphere Process Choreographer repository.3. Remote deployment and administration component.

1 WebSphere Studio Application Developer Integration Edition (WSADIE) Version 5.2.Prerequisite software IBM WebSphere Business Integration Adapter Framework IBM WebSphere Business Integration Adapter for mySAP. Detailed instructions on how to install IBM WebSphere MQ is covered in 6.1 is used to develop the business process for this Use Case. Use Case 2: WBISF using WBI Adapter for mySAP. “Installing IBM DB2 UDB Version 8. 5. Table 8-2 Product installation directories Directory C:\IBMRAC C:\SQLLIB C:\WebSphere\AppServer C:\WebSphereAdapters C:\WebSphereMQ C:\WSADIE51 Component IBM Remote Agent Controller IBM DB2 IBM WebSphere Application Server IBM WebSphere Business Integration Adapters IBM WebSphere MQ IBM WebSphere Studio Application Developer Integration Edition Tip: We recommend avoiding installation directory names that include spaces.5 Detailed instructions on how to install IBM DB2 is covered in 6.1 with FixPack 5” on page 150.2.3. The development environment includes a built in server run time that enables the developer to test and debug the application during development.com Version 2.2 Install WSADIE V5.3.3 with CSD04” on page 171. Table 8-2 lists the directories used for the installation of the software components. 8.4 What the software is for Framework where WBI Adapters can be plugged in.com 331 . Specific WBI Adapter to connect SAP back-end systems with WBI infrastructures. “Installing WebSphere MQ V5. Chapter 8.1.

Execute the file launchpad. Select Install WebSphere Studio Application Developer Integration Edition. Figure 8-2 WSAD Integration Edition Launchpad 3. The window in Figure 8-2 should appear. Switch to the folder where the installation files are located. The window in Figure 8-3 on page 333 should appear.1.exe. 332 WebSphere Business Integration for SAP . 2.

Figure 8-4 License agreement 5. The window in Figure 8-4 should appear. Use Case 2: WBISF using WBI Adapter for mySAP. Click Next.com 333 . The window in Figure 8-5 on page 334 should appear.Figure 8-3 Welcome window 4. Accept the license agreement and click Next. Chapter 8.

334 WebSphere Business Integration for SAP . Enter a desired installation directory. Figure 8-6 Installation features 7. and click Next. such as C:\WSAD51. The window in Figure 8-6 should appear. Accept the default installation options and click Next. The window in Figure 8-7 on page 335 should appear.Figure 8-5 Installation directory 6.

Figure 8-7 Installation summary 8. Use Case 2: WBISF using WBI Adapter for mySAP. Click Next. The window in Figure 8-8 should appear. Chapter 8. Click Finish and reboot the machine.com 335 . Figure 8-8 Final window 9.

2. Switch to the folder where the installation files are located.1 as an integration broker to execute the defined business process.bat.2. Select Install the product. 336 WebSphere Business Integration for SAP .8.1 This Use Cases utilizes WebSphere Business Integration Server Foundation V5. Execute the file launchpad. 1. The window in Figure 8-9 should appear.3 Install WBISF V5. Figure 8-9 WebSphere Business Integration Server Foundation Launchpad 3. The window in Figure 8-10 on page 337 should appear.

Figure 8-11 License Agreement 5. Select Next. Use Case 2: WBISF using WBI Adapter for mySAP. Chapter 8.Figure 8-10 Installation wizard 4. The window in Figure 8-12 on page 338 should appear. The window in Figure 8-11 should appear. Accept the license agreement and click Next.com 337 .

Figure 8-12 Installation type 6. Select Custom installation and click Next. The window in Figure 8-13 on page 339 should appear. 338 WebSphere Business Integration for SAP .

Use Case 2: WBISF using WBI Adapter for mySAP. The window in Figure 8-14 on page 340 should appear. Deselect Embedded messaging and click Next. Chapter 8.com 339 .Figure 8-13 WebSphere Business Integration Server Foundation Feature 7.

The window in Figure 8-16 on page 341 should appear. 340 WebSphere Business Integration for SAP . Enter the desired installation directory. Accept the default node name and host name and click Next. The window in Figure 8-15 should appear. and click Next. Figure 8-15 Node name and host name 9.Figure 8-14 Installation directory 8. such as C:\WebSphere\AppServer.

Chapter 8.Deselect to start the WebSphere Application Server as a service and click Next. The window in Figure 8-17 on page 342 should appear. Use Case 2: WBISF using WBI Adapter for mySAP.Figure 8-16 Run as service feature 10.com 341 .

342 WebSphere Business Integration for SAP .Figure 8-17 Installation summary 11. The window in Figure 8-18 on page 343 should appear.Review the installation options and click Next.

Figure 8-18 Registration window 12.Deselect the register check box and click Next.com 343 . Chapter 8. The window in Figure 8-19 on page 344 should appear. Use Case 2: WBISF using WBI Adapter for mySAP.

8.2. In the window shown in Figure 8-20.Click Finish.4 Install IBM Remote Agent Controller V5.Figure 8-19 Final installation window 13. 1.1 This section describes how to set up the IBM Remote Agent Controller. The window in Figure 8-21 on page 345 should appear. Figure 8-20 Select language 344 WebSphere Business Integration for SAP . select English (United States) and click OK.

Use Case 2: WBISF using WBI Adapter for mySAP. Chapter 8. Press Next on the welcome screen. The window in Figure 8-22 should appear. Figure 8-22 License agreement 3. Accept the license agreement and click Next.Figure 8-21 Install Shield welcome window 2. The window in Figure 8-23 on page 346 should appear.com 345 .

Figure 8-23 Customer Information window

4. Enter the user name and organization and select Anyone who uses this computer and click Next. The window in Figure 8-24 should appear.

Figure 8-24 Installation destination folder

5. Select an installation directory, such as C:\IBMRAC, and click OK. The window in Figure 8-25 on page 347 should appear.

346

WebSphere Business Integration for SAP

Figure 8-25 Java Runtime Environment folder

6. Select the folder where the Java Runtime Environment is installed and click Next. The window in Figure 8-26 should appear.

Figure 8-26 Security settings

7. Select the check box Disable Security and press Next. The window in Figure 8-27 on page 348 should appear.

Chapter 8. Use Case 2: WBISF using WBI Adapter for mySAP.com

347

Figure 8-27 Remote Agent Controller access

8. Select the check box Any computer to give every computer the permission to access the Remote Agent Controller and press the Next button. The window in Figure 8-28 should appear.

Figure 8-28 Ready to install window

9. Press the Install button to start the installation. The window in Figure 8-29 on page 349 should appear.

348

WebSphere Business Integration for SAP

Figure 8-29 Final window

10.Press Finish to close the installation wizard.

8.2.5 Install WBI Adapter Framework V2.4
The WebSphere Business Integration Adapter Framework V2.4 consists of various subcomponents. The subcomponents are: System Manager Virtual Test Connector Log Viewer Business Object Designer Connector Configurator Important: Make sure that no instance of WebSphere Studio Application Developer Integration Edition or any other Eclipse development environment is running when starting the framework installation. 1. Switch to the folder where the installation files are located and execute setupwin32.exe to start the framework installation. The window in Figure 8-30 on page 350 should appear.

Chapter 8. Use Case 2: WBISF using WBI Adapter for mySAP.com

349

Figure 8-30 Language selection

2. Select English as the language for the install wizard and click on OK. The window in Figure 8-31 should appear.

Figure 8-31 Welcome window

3. Press Next on the welcome screen. The window in Figure 8-32 on page 351 should appear.

350

WebSphere Business Integration for SAP

Figure 8-32 License agreement

4. Accept the license agreement and select Next. The window in Figure 8-33 should appear.

Figure 8-33 Installation directory

Chapter 8. Use Case 2: WBISF using WBI Adapter for mySAP.com

351

5. Enter a directory, such as C:\WebSphereAdapters, as the installation destination, and press Next. The window in Figure 8-34 on page 352 should appear.

Figure 8-34 Installation summary

6. Review the installation settings and click on Next. The window in Figure 8-35 should appear.

352

WebSphere Business Integration for SAP

Figure 8-35 WebSphere MQ library location

7. The WebSphere MQ Java libraries should be detected automatically. Click on Next. The window in Figure 8-36 on page 353 should appear.

Figure 8-36 Workbench installation

8. Select Install WebSphere Studio Workbench and plug-ins and click on Next. The window in Figure 8-37 should appear.

Chapter 8. Use Case 2: WBISF using WBI Adapter for mySAP.com

353

Figure 8-37 Program group selection

9. Leave the default Program group and click on Next. The window in Figure 8-38 on page 354 should appear.

Figure 8-38 Final window

10.Click on Finish to close the wizard after the installation is done.

354

WebSphere Business Integration for SAP

8.2.6 Install WBI Adapter for mySAP.com V5.5
The WebSphere Business Integration Adapter for mySAP.com includes the core mySAP.com adapter and the mySAP.com Object Discovery Agent (ODA). The WebSphere Business Integration Adapter Framework must be already installed. 1. Switch to the folder where the installation files are located. 2. Execute the file setupwin32.exe. The window in Figure 8-39 should appear.

Figure 8-39 Language selection

3. Choose English from the drop-down list. The window in Figure 8-40 on page 355 should appear.

Figure 8-40 Welcome window

4. Press Next on the Welcome Screen. The window in Figure 8-41 should appear.

Chapter 8. Use Case 2: WBISF using WBI Adapter for mySAP.com

355

Figure 8-41 License agreement

5. Accept the license agreement and click on Next. The window in Figure 8-42 on page 356 should appear.

Figure 8-42 WebSphere Adapter Framework location

6. Select the folder where the Adapter Framework is installed and click on Next. The window in Figure 8-43 should appear.

356

WebSphere Business Integration for SAP

Figure 8-43 Installation summary

7. On the installation summary screen, click on Next. The window in Figure 8-44 on page 357 should appear.

Figure 8-44 Interchange Server name

8. In this scenario, no WebSphere InterChange Server is used. Leave the input field blank and click on Next. The window in Figure 8-45 should appear.

Chapter 8. Use Case 2: WBISF using WBI Adapter for mySAP.com

357

Figure 8-45 Program group selection

9. Leave the default Program group and click on Next. The window in Figure 8-46 should appear.

Figure 8-46 Final window

10.Click on Finish to close the wizard after the installation is done.

358

WebSphere Business Integration for SAP

8.3 Configuration of WebSphere Business Integration components
This section describes how to set up and configure the environment to enable this Use Case to run. The configuration includes setup and configuration of the following components: WebSphere MQ WebSphere Business Integration Adapter for mySAP.com WebSphere Studio Application Developer Integration Edition WebSphere Business Integration Server Foundation

8.3.1 Configuration of WebSphere MQ
The integration broker communicates with the WebSphere Business Integration Adapters using WebSphere MQ. One queue manager and several local queues must be set up. Table 11-3 contains a list of the required queues for one adapter.
Table 8-3 Adapter queues Queue name ADMININQUEUE ADMINOUTQUEUE FAULTQUEUE REQUESTQUEUE RESPONSEQUEUE DELIVERYQUEUE SYNCHRONOUSREQUESTQUEUE SYNCHRONOUSRESPONSEQUEUE Usage of the queue Administration queue to the adapter Administration queue from the adapter Queue for fault messages Synchronous request from the broker to the adapter Synchronous response for requests from the REQUESTQUEUE Asynchronous message from the adapter to the broker Synchronous request from the adapter to the broker Synchronous response for the queue SYNCHRONOUSREQUESTQUEUE

The WebSphere Business Integration Adapters include a batch file that can be used to set up the required queue manager and the queues.

Chapter 8. Use Case 2: WBISF using WBI Adapter for mySAP.com

359

Example 8-2 Command Prompt commands cd C:\WebSphereAdapters\templates configure_mq. Open the file in Notepad and add the text in Example 8-1. 8. channel type and transport method ******************************************************* DEFINE CHANNEL(CHANNEL1) CHLTYPE(SVRCONN) TRPTYPE(TCP) 3.sap.com The WebSphere Business Integration Adapter for mySAP.manager mqsetup. Open the file C:\WebSphereAdapters\bin\CWODAEnv.2 Configuration of WBI Adapter for mySAP. Create a new text file called mqsetup.1.tst 4.com requires a Java 2 Software Development Kit V1.3.10 from the SAP Service Marketplace: http://service.0.bat in Notepad.queue. 2. Open the WebSphere MQ Explorer and check if the queue manager runs and all queues are included.10.bat itsod. 2.0.com/connector 360 WebSphere Business Integration for SAP . 1. Add the bin folder of the IBM Java 2 Java Software Development Kit to the PATH entry.C:\ibmjdk1_3_1\bin 3. Open a command prompt and type in the commands from Example 8-2. Download the SAP JCo V2. Example 8-1 mqsetup.tst **************************************************** * Define the SAP ADAPTER QUEUES **************************************************** DEFINE QLOCAL(SAPCONNECTOR/AdminInQueue) DEFINE QLOCAL(SAPCONNECTOR/AdminOutQueue) DEFINE QLOCAL(SAPCONNECTOR/DeliveryQueue) DEFINE QLOCAL(SAPCONNECTOR/RequestQueue) DEFINE QLOCAL(SAPCONNECTOR/ResponseQueue) DEFINE QLOCAL(SAPCONNECTOR/FaultQueue) DEFINE QLOCAL(SAPCONNECTOR/SynchronousRequestQueue) DEFINE QLOCAL(SAPCONNECTOR/SynchronousResponseQueue) ******************************************************* * Define the channel.tst in the folder C:\WebSphereAdapters\templates. For example: set PATH=”CROSSWORLDS”\bin.3 and the SAP Java Connector (SAP JCO) V2.

and librfc32. Copy the jcosap. sapjcorfc.com 361 .jar. In the Server Configuration outline.1. right-click on the Servers folder. Open WebSphere Studio Application Developer Integration Edition and switch to the server perspective.dll from the jco package into the folders: – C:\WebSphereAdapters\connectors\SAP – C:\WebSphereAdapters\ODA\SAP 8. The window in Figure 8-47 on page 361 should appear. Chapter 8.3. Select New → Server and Configuration. Use Case 2: WBISF using WBI Adapter for mySAP.1 This section describes the setup of an local test environment within WebSphere Studio Application Developer Integration Edition V5. Figure 8-47 Create new local server and configuration 2. 1.dll.4.3 Configuration of WSADIE V5.

5. Double-click on the LocalEE entry in the Server Configuration outline to open the configuration.Figure 8-48 Local server name and server type 3. Enter LocalEE as the Server name and choose Integration Test Environment as the Server type. Click on Finish. 362 WebSphere Business Integration for SAP . 4. The window in Figure 8-49 on page 363 should appear.

com 363 . The window in Figure 8-50 on page 364 should appear. Use Case 2: WBISF using WBI Adapter for mySAP. Select the check box Enable administration console in the Configuration tab. Chapter 8.Figure 8-49 Enable administrative console 6.

Switch to the Variables tab.Figure 8-50 Set environment variables 7. The window in Figure 8-51 on page 365 should appear. 364 WebSphere Business Integration for SAP .

Figure 8-51 Set variable DB2_JDBC_DRIVER_PATH 8. Change the variable MQ_INSTALL_ROOT to the path where you installed WebSphere MQ. Change the variable DB2_JDBC_DRIVER_PATH to point to the file db2java. Use Case 2: WBISF using WBI Adapter for mySAP. For example: C:\SQLLIB\java\db2java. For example: C:\WebSphereMQ Chapter 8.com 365 .zip using the full path.zip Figure 8-52 Set variable MQ_INSTALL_ROOT 9.

Switch to the Security tab. 13. 12.Figure 8-53 Enable WebSphere security 10. 366 WebSphere Business Integration for SAP . 11.Press Ctrl+S to save the settings and close the LocalEE configuration. The window in Figure 8-54 on page 367 should appear.Check the check box Enable security and enter a local operating system user and password.Right-click on the LocalEE entry in the Server outline and select Start.

right-click on the LocalEE entry in the Server outline and select Run administrative console.Figure 8-54 Run administration console 14. The window in Figure 8-55 on page 368 should appear.com 367 . 15.Select Resources → WebSphere MQ JMS Provider. Use Case 2: WBISF using WBI Adapter for mySAP. Chapter 8.After the server has started completely.

17. 368 WebSphere Business Integration for SAP .Figure 8-55 Create WebSphere MQ JMS connection factory 16. 18.Enter SAPConnectionFactory in the Name field.Switch to the Server level and create a new WebSphere MQ Connection Factory.Enter jms/SAPConnectionFactory in the JNDI name field.

The window in Figure 8-56 should appear.com 369 .queue.Enter the name of the queue manager in the Queue Manager field.19.Select Resources → WebSphere MQ JMS Provider. 20.manager. Use Case 2: WBISF using WBI Adapter for mySAP. 21. Figure 8-56 Create WebSphere MQ JMS queue destination Chapter 8. such as ITSOD.Save the configuration.

refer to 8. 6. For a detailed configuration description. Click on server1. Select Servers → Application Server from the navigator. Scroll down and click on Business Process Container Install wizard.3. 8. 24. 23. 3. Scroll down and click on Business Process Container. “Configuration of WSADIE V5.Switch to the Server level and create a new WebSphere MQ Destination.4 Configuration of WBISF The completed business process is deployed onto a WebSphere Business Integration Server Foundation run-time environment. the Business Process Container has to be set up to enable the WebSphere Process Choreographer to execute processes.22. 370 WebSphere Business Integration for SAP . 26.Enter SAPRequestQueue in the Name field. such as SAPCONNECTOR/REQUESTQUEUE. Enter valid credentials at the logon screen and press OK.Restart the application server. Open the Administrative Console. 2.Enter the name of the request queue of the WebSphere MQ installation in the Base Queue Name field. 4.3. Additionally.Enter jms/SAPRequestQueue in the JNDI name field. 1. 5. The window in Figure 8-57 on page 371 should appear.Select OK and save the application server configuration. The same configuration that was done for the local test and development environment has to be done for the run-time environment.1” on page 361. 25. 27.3.

The window in Figure 8-58 on page 372 should appear. Use Case 2: WBISF using WBI Adapter for mySAP. Chapter 8. Select DB2 Universal JDBC Driver Provider (XA) and click on Next.Figure 8-57 Business Process Container database setup 7.com 371 .

Select the WebSphere MQ JMS provider in the JMS provider drop-down list.queue.Enter the same user name in the field Security Role Mapping. 9. Enter the name of the WebSphere MQ queue manager in the field Queue Manager. such as ITSOD. 10. 372 WebSphere Business Integration for SAP . 11.Enter a valid operating system user in the fields JMS User ID and JMS API User ID together with the correct password.manager.Figure 8-58 Business Process Container JMS setup 8.

Chapter 8. Finally. 14. The wizard configures the Business Process Container according to the selections made. restart the application server.Select Create new JMS resources using default values and click Next.12.Click Next. Use Case 2: WBISF using WBI Adapter for mySAP. The window in Figure 8-59 should appear. Figure 8-59 Business Process Container JMS resources 13.com 373 . Check the output for error messages and save the configuration to the master configuration.Review the summary screen and click Finish.

1 Create Business Objects and Connector Configuration This section describes the steps necessary to create the required business objects using the Eclipse based System Manager. 8.com connector. A prepackaged workspace is used as a starting point. the Business Object Designer. The window in Figure 8-60 on page 375 should appear. Attention: The focus of this Use Case is to show how easy it is to choreograph new business processes using WebSphere Business Integration Server Foundation by incorporating existing enterprise services.4. It is highly recommended to implement more application specific exception handling to handle back-end errors and warnings more efficiently. In this Use Case.1 (WSADIE).8. Open the System Manager from the Windows Start Menu. The scenario utilizes two workbenches.1.4 Development of a business process The section describes the development steps to implement the described Use Case scenario. 374 WebSphere Business Integration for SAP . Within WSADIE. a new business process is created that incorporates several encapsulated services. 1. and the Connector Configurator. The System Manager is used to generate business objects from the back-end system and to configure the mySAP. All business process development activities are done in the WebSphere Studio Application Developer Integration Edition V5. The exported business object definitions are used to create two enterprise service applications that are integrated into existing back-end systems. which is delivered in the file Base_Workspace_SAK400. These settings and objects are exported to the file system and imported into WebSphere Studio Application Developer Integration Edition V5. A third service project is defined to hold the Web Services Description Language style description of external services. Exception handling and input validation is purposely limited to a minimum. it is a back-end service exposed via an standard Apache-Axis Web Service interface. This workspace provides the Notification service out of the box.zip.

The window in Figure 8-61 should appear. Use Case 2: WBISF using WBI Adapter for mySAP. Enter SAP_ICL as project name and press Finish. Figure 8-61 Integration component library settings 3.Figure 8-60 New Integration Component Library 2. The window in Figure 8-62 on page 376 should appear. Switch to the System Manager Perspective and select New Integration Component Library from the context menu. Chapter 8.com 375 .

Figure 8-62 Create a new business object 4. Select Create New Business Object from the context menu of the Business Objects folder. Press Cancel on the first pop-up screen and select File → New using ODA from the menu bar. The window in Figure 8-63 should appear. 376 WebSphere Business Integration for SAP . Figure 8-63 New Business Object using ODA 5.

the Business Object Designer queries all metadata from the ODA.com 377 . from the context menu to find the table. The next screen (Figure 8-64) shows the Object Discovery Agent configuration... Figure 8-64 ODA detection After selecting the agent. The next screen (Figure 8-65 on page 378) shows a list of connection data for the SAP system. 7. Chapter 8. Press the Find Agents Button and select the SAPODA entry from the list. Use Case 2: WBISF using WBI Adapter for mySAP. Create and Save a new profile for the SAP R/3 system.6. Select Search for items . Enter pa0105 in the pop-up window to get the table. 8.

Select the result and press Next. The window in Figure 8-66 should appear.In the Business Object properties screen. Figure 8-66 Select a table 10.Figure 8-65 Search a table 9. keep the default prefix and press OK. 378 WebSphere Business Integration for SAP . The window in Figure 8-67 on page 379 should appear.

com 379 . Figure 8-68 Save BO configuration The Business Object for the purchasing request remote function call must be discovered as well. Use Case 2: WBISF using WBI Adapter for mySAP. Chapter 8.Figure 8-67 Business Object properties 11.In the last screen (Figure 8-68). deselect all check boxes and save the business object into the SAP_ICL project.

15.Use the existing profile for the SAP connection. enter Retrieve as the Verb and Yes for the UseFieldName flag. Figure 8-69 Browsing the Business Object Repository 16.Use the menu item New using ODA.Select BOR → Materials Management → Purchasing → Purchase Requisition → BAPI_REQUISITION_CREATE in the Select Source screen (Figure 8-69). 14. 13.12.Select the SAPODA in the configuration screen. 380 WebSphere Business Integration for SAP .In the BO properties screen (Figure 8-70 on page 381).

Close the Business Object Designer and press Refresh in the System Manager. 18.Figure 8-70 Business Object properties 17. Use Case 2: WBISF using WBI Adapter for mySAP. After setting up the business objects. Figure 8-71 Create new connector configuration Chapter 8. the configuration of the adapter must be made.com 381 .Save the Business Object to the SAP_ICL project and press Finish. Select Create New Connector in the context menu of the Connectors folder (see Figure 8-71). 1.

In the standard properties page.. Open the file CN_SAP. Figure 8-72 Open connector template 3.. Enter all generated WebSphere MQ queues and the path to the repository (see Figure 8-73 on page 383).2. Select Open → From File .txt from the WebSphere Business Integration Adapter Framework repository folder. WAS must be selected as the broker. to open the Adapter template (see Figure 8-72). 382 WebSphere Business Integration for SAP .

Figure 8-73 Standard connector properties 4. Enter the SAP access date into the Connector specific properties (see Figure 8-74 on page 384). Chapter 8. Use Case 2: WBISF using WBI Adapter for mySAP.com 383 .

Figure 8-74 Connector specific properties 384 WebSphere Business Integration for SAP .

Use Case 2: WBISF using WBI Adapter for mySAP. 6. Open the User Projects folder and right-click on the New User project entry (see Figure 8-75). select sap_bapi_requisition_create and sap_pa0105 as supported objects. In the New User Project wizard. the components must be deployed in a User Project. type SAP_UserProject as the project name (see Figure 8-76 on page 386). System Manager user projects specify the integration components that are used for some particular purpose.com 385 . Save the adapter as SAPConnector to the SAP_ICL project. After the setup of the business objects and the connector configuration is complete.5. In the supported Business Objects tab. 1. Chapter 8. such as a specific interaction pattern. Figure 8-75 New User project 2.

Select the complete SAP_ICL project to import all the components and press Finish. 1. you can deploy the user projects to the Business Integration perspective for use in the creation of WebSphere Application Server Enterprise Application Archive projects.Figure 8-76 New user project settings 3. 386 WebSphere Business Integration for SAP . After you have created System Manager user projects and populated them with integration components. Right-click on the SAP_UserProject folder and select Deploy WAS Project (see Figure 8-77 on page 387).

Use Case 2: WBISF using WBI Adapter for mySAP. Table 8-4 WebSphere Application Server interaction patterns Interaction pattern AgentDelivery AgentRequest HubOneWay HubRequest Description Synchronous call from the adapter to the Broker Asynchronous call from the adapter to the Broker Asynchronous call from the Broker to the adapter Synchronous call from the Broker to the adapter The given Use Case requires a synchronous communication from the WebSphere Business Integration Server Foundation to the mySAP. Chapter 8.com Adapter.Figure 8-77 Deploy WAS project The next screen (Figure 8-78 on page 388) displays the different adapters and there Business Object dependency.com 387 . It is possible to select four different kinds of interaction patterns (see Table 8-4).

Figure 8-78 Component selection page 2. 388 WebSphere Business Integration for SAP . Select the HubRequest pattern for both business objects and deselect the other integration patterns. The window in Figure 8-79 on page 389 should appear.

1. Select Export to Directory and enter a valid directory name. The business object definition files are saved in . Chapter 8. The connector configuration files (file in XML format with a . 8.wsdl extension. Create an empty folder that becomes the new WSAD workspace.Figure 8-79 Select the export directory 3.cfg or . Use Case 2: WBISF using WBI Adapter for mySAP.xsd format.zip into the workspace directory.con extension) are transformed into Web Services Description Language (WSDL) format and renamed with the . Open WSAD and select the created folder to be the workspace directory.4. Click Finish to export the project. 3.2 Import prepackaged workspace This section describes how to import the prepackaged workspace into the WebSphere Studio Application Developer Integration Edition environment. 4. 2. Extract the content of the file Base_Workspace_SAK400.com 389 . This setup saves the connector configuration files and business object definition files of the user project to the selected directory.

Select Existing Project into Workspace.4. In WSAD. The window in Figure 8-80 should appear.The window in Figure 8-81 on page 391 should appear. 390 WebSphere Business Integration for SAP . Figure 8-80 Select Import data 5... select File → Import ..

Select Finish. Browse to the location of the first project. Repeat this procedure for all extracted subfolders in this sequence: – JavaMailEJB – JavaMailEJBEAR – soapcfg – Notification_Service – Notification_ServiceWeb – Notification_ServiceEJB – Notification_ServiceEAR Chapter 8.com 391 . 8.Figure 8-81 Project content directory 6. 7. Use Case 2: WBISF using WBI Adapter for mySAP.

Switch to the Create a Business Integration Perspective and create a new Service Project. The window in Figure 8-83 on page 393 should appear. 392 WebSphere Business Integration for SAP .8.. 2... Figure 8-82 Import from file system 3. Right-click on the created Service Project and select Import .3 Create the ERP Procurement Service This section describes how to create the service application that implements the part of the Internal Order business process that places the order in the back-end system. The window in Figure 8-82 should appear. 1. Choose to import from File system.4.

Make sure that all files are selected and click Finish. Chapter 8. Select the directory where the exported files from the System Manager are located.com 393 . 5.Figure 8-83 Import wizard 4. Use Case 2: WBISF using WBI Adapter for mySAP. Check if all files are listed below in the newly created Service Project (see Figure 8-84 on page 394).

.Figure 8-84 Generate Deploy Code 6. The window in Figure 8-85 on page 395 should appear. 394 WebSphere Business Integration for SAP ... Right-click on the JMS Binding WSDL file and select Enterprise Services → Generate Deploy Code .

choose EJB and leave the rest unchanged and click Next. Select the Requisition create service and the HubRequest Binding. The window in Figure 8-86 on page 396 should appear. For Inbound binding type.Figure 8-85 Deployment wizard 7. 8. Use Case 2: WBISF using WBI Adapter for mySAP.com 395 . Chapter 8.

396 WebSphere Business Integration for SAP . Adjust the package name if required and leave the rest unchanged. The window in Figure 8-87 on page 397 should appear.Figure 8-86 Inbound service files 9. Click Next.

Adjust the JNDI name of the generated EJB if required and select Finish.Figure 8-87 Select JNDI name 10. Use Case 2: WBISF using WBI Adapter for mySAP. Chapter 8.com 397 . The file structure should look like Figure 8-88 on page 398.

Figure 8-88 File structure 8. Right-click on the created Service Project and select Import . Switch to the Create a Business Integration Perspective and create a new Service Project. 398 WebSphere Business Integration for SAP . The window in Figure 8-89 on page 399 should appear....4 Create the HR Information Lookup Service This section describes how to create the service application that implements the part of the Internal Order business process that retrieves Human Resource information about the person who places the internal order.4. 1. 2.

Chapter 8.com 399 . Use Case 2: WBISF using WBI Adapter for mySAP. The window in Figure 8-90 on page 400 should appear.Figure 8-89 Import from file system 3. Choose to import from File system.

Make sure that all files are selected and click Finish. Select the directory where the exported files from the System Manager are located.. The window in Figure 8-91 on page 401 should appear. 400 WebSphere Business Integration for SAP . 6.. Check if all the files are listed below the newly created Service Project.. Right-click on the JMS Binding WSDL file and select Enterprise Services → Generate Deploy Code .Figure 8-90 Import wizard 4. 5.

Select the Requisition create service and the HubRequest Binding. 8. For Inbound binding type. Use Case 2: WBISF using WBI Adapter for mySAP. Chapter 8. choose EJB and leave the rest unchanged. and click Next.Figure 8-91 Deployment wizard 7. The window in Figure 8-92 on page 402 should appear.com 401 .

402 WebSphere Business Integration for SAP . The window in Figure 8-93 on page 403 should appear.Figure 8-92 Inbound service files 9. Click Next. Adjust the package name if required and leave the rest unchanged.

Adjust the JNDI name of the generated EJB if required and select Finish. Use Case 2: WBISF using WBI Adapter for mySAP.Figure 8-93 Select JNDI name 10.com 403 . Chapter 8. The file structure should look like Figure 8-94 on page 404.

Figure 8-94 File structure 8. Open the deployment descriptor of the generated EJB and adjust the reference bindings (see Figure 8-95 on page 405). The generated EJB defines a reference variable for a WebSphere MQ Connection factory and for a WebSphere MQ Queue destination. The service application exchanges data with the back-end connector via WebSphere MQ. 1. 404 WebSphere Business Integration for SAP .5 Deploy the ERP Procurement service This section describes how to adjust the generated code to run in the local development environment. This references have to be adjusted before the application is deployed to the local test environment.4.

Figure 8-95 Adjust reference binding for Queue Connection factory 2. The QueueConnectionFactory and the Queue reference has to match the WebSphere MQ settings in the Administration Console. Use Case 2: WBISF using WBI Adapter for mySAP.com 405 . such as jms/SAPConnectionFactory and jms/SAPRequestQueue (see Figure 8-96 on page 406). Chapter 8.

. 406 WebSphere Business Integration for SAP . Switch to the Server perspective. Right-click on the LocalEE test server and select Add and remove projects. 5. 6... Right-click on the ERP_ProcurementService Project and select Generate Deployment Code. Switch to the Business Integration Perspective.Figure 8-96 Adjust reference binding for Queue Destination 3. The window in Figure 8-97 on page 407 should appear. 4.

8. 8.4. Add the ERP_ProcurementService Project.Figure 8-97 Add project to Test Server 7. The service application exchanges data with the back-end connector via WebSphere MQ. Chapter 8.com 407 .6 Deploy the HR Information Lookup service This section describes how to adjust the generated code to run in the local development environment. This references have to be adjusted before the application is deployed to the local test environment. Open the deployment descriptor of the generated EJB and adjust the reference bindings (see Figure 8-98 on page 408). The generated EJB defines a reference variable for a WebSphere MQ Connection factory and for a WebSphere MQ Queue destination. Select Finish. Use Case 2: WBISF using WBI Adapter for mySAP. 1.

such as jms/SAPConnectionFactory and jms/SAPRequestQueue (see Figure 8-99 on page 409).Figure 8-98 Adjust reference binding for Queue Connection factory 2. The QueueConnectionFactory and the Queue reference has to match the WebSphere MQ settings in the Administration Console. 408 WebSphere Business Integration for SAP .

Figure 8-99 Adjust reference binding for Queue Destination 3. 6. The window in Figure 8-100 on page 410 should appear.com 409 . Switch to the Business Integration Perspective. Use Case 2: WBISF using WBI Adapter for mySAP. Right-click on the ERP_ProcurementService Project and select Generate Deployment Code. Chapter 8. 5. Switch to the Server perspective.. Right-click on the LocalEE test server and select Add and remove projects. 4...

1. 8. This file is placed into a Service project and can be referenced in a business process.Figure 8-100 Add project to Test Server 7. 410 WebSphere Business Integration for SAP .4.7 Incorporate external services This section describes how to incorporate external services in a complex process choreography scenario. Create a Service Project and name it ExternalServices (see Figure 8-101 on page 411). 8. Select Finish. The process developer requires a service description within a valid WSDL file. Add the HR_InfoLookupService Project.

Figure 8-101 Create a new Service Project 2.com 411 . Use Case 2: WBISF using WBI Adapter for mySAP. Create a package within this project and name it servicedefinition (see Figure 8-102). Figure 8-102 Create a new package Chapter 8.

3. 1. From Windows Explorer. 412 WebSphere Business Integration for SAP .8 Design Internal Order business process The Internal Order business process choreographs a new process by linking existing services’ style applications together. Figure 8-103 Folder structure 8. An application flow defines in which sequence the external services are called. The folder structure should look like Figure 8-103.wsdl file into this package. drag the MaterialApproval.4. Create a Service project and name it InternalOrderProcess_Service (see Figure 8-104 on page 413).

sak400 (see Figure 8-105). Figure 8-105 Create a new package Chapter 8. Use Case 2: WBISF using WBI Adapter for mySAP. Create a package called process.Figure 8-104 Create a new Service project 2.com 413 .

wsdl file into the newly created package.. From the Windows Explorer. The window in Figure 8-106 should appear. Select Java Service Skeleton and click Next. Right-click on the InternalOrderProcess. drag the InternalOrderProcess. Figure 8-106 Create new Service Skeleton 4.. The window in Figure 8-107 on page 415 should appear. 414 WebSphere Business Integration for SAP .wsdl file and select Build from service..3. 5.

Use Case 2: WBISF using WBI Adapter for mySAP.Figure 8-107 Create new port and binding 6. Select Create a new port and binding and click Next. Chapter 8.com 415 . The window in Figure 8-108 on page 416 should appear.

Ensure the Port type name is InternalOrderCallbackPortType and click Next. 416 WebSphere Business Integration for SAP . The window in Figure 8-109 on page 417 should appear.Figure 8-108 Define locations 7.

wsdl file and choose to create a Business process.Figure 8-109 Location for generated classes 8. 10.Right-click on the InternalOrderProcess. 9. Accept the default values and click Finish. as shown in Figure 8-110 on page 418. Example 8-3 Snippet .println("User: " + argUsername + " created successfully purchase order [" + argRequisitionNumber + "].java to open the file within the Java editor. double-click InternalOrderCallbackPortType.InternalOrderCallbackPortType. Use Case 2: WBISF using WBI Adapter for mySAP.out.com 417 . 11." ). In the Service view.Add the following code snippet (Example 8-3) to the user code section of the method just before the return statement.txt System. Chapter 8.

0 Business Process. 418 WebSphere Business Integration for SAP .Select WSAD-IE v5.Figure 8-110 Create Business Process 12. The window in Figure 8-111 on page 419 should appear.

com 419 .process file to start modelling the business process. Use Case 2: WBISF using WBI Adapter for mySAP. Chapter 8.Figure 8-111 Select Output operation 13. drop three Java snippets onto the process and rename them to: – prepareCall – preparepositiveNotification – preparenegativeNotification 17.From the palette.wsdl file.Double-click on the InternalOrder.Switch to the Service perspective and expand the Service projects to see the four required WSDL files (see Figure 8-112 on page 420).Select InternalOrderCallbackPortType and click Finish. drop a Staff activity onto the process and rename it to Approval. 16. 18. 14. 15.Click Browse beside the output operation and select the InternalOrderProcess.From the palette.

22.Figure 8-112 Expand external services tree 19. Figure 8-113 Drop HR Information Lookup service 20. 420 WebSphere Business Integration for SAP .Rename the node to gathered.wsdl file into the process (see Figure 8-113).From the Services view. 21.Click OK if a Java Build Path Notification pops up. drop the sap_pa0105HubRequestServiceEJBService.Select the Retrieve operation.

Select the sendJMail operation.com 421 . Figure 8-114 Drop create internal order service 24. 33. Figure 8-115 Drop Notification service 28. 27. Use Case 2: WBISF using WBI Adapter for mySAP. 25. 34.wsdl file into the process.wsdl file into the process (see Figure 8-115). Chapter 8. 26. 31. 30.wsdl file into the process (see Figure 8-114).Rename the node to createPurchaseOrder.Select the checkMaterial operation.Select the Control Link tool and connect the node.23.Click OK if a Java Build Path Notification pops up. 35. 32.From the Services view.Click OK if a Java Build Path Notification pops up.Select the Retrieve operation.From the Services view. as shown in Figure 8-116 on page 422.Rename the node to checkApprovalPolicy.Click OK if a Java Build Path Notification pops up.From the Services view. drop the MaterialApproval. drop the JavaMailerSOAPService. 29. drop the sap_bapi_requisition_createHubRequestEJBService.Rename the node to notifyRequestor.

Figure 8-117 Staff activity properties 37.Save the process with Ctrl+S. 38.Right-click on the staff activity and select Staff. The window in Figure 8-117 should appear. 422 WebSphere Business Integration for SAP .Highlight Potential Owner and click Change. The window in Figure 8-118 on page 423 should appear.Figure 8-116 Connect business process nodes 36.

41. Use Case 2: WBISF using WBI Adapter for mySAP.Switch from the Process tab to the Server tab and select Run Process as Interruptible. select Users. 40. Chapter 8.In the Verb drop-down list. The window in Figure 8-119 on page 424 should appear.com 423 .Figure 8-118 Select activity owner 39.Enter the Administrator user ID in the Description field and in the Name field and click OK.

The window in Figure 8-121 on page 425 should appear. and then click on Implementation. The window in Figure 8-120 should appear. Figure 8-120 Add variable for request 43. choose Properties.Figure 8-119 Properties of getHRData 42.Select the input terminal. 424 WebSphere Business Integration for SAP . and then click OK.Right-click on the getHRData node. click New Variable.

Choose Properties and then Data.Right-click on the Approval node.Figure 8-121 Add variable for response 44. createPurchaseOrder and notifyRequestor nodes.com 425 . Chapter 8. 48. 47. Use Case 2: WBISF using WBI Adapter for mySAP.Repeat the above steps for the checkApprovalPolicy. 45.Select the output terminal and click New Variable and then click OK. The window in Figure 8-122 on page 426 should appear.Click OK. 46.

50. 51.Figure 8-122 Select staff activity parameters 49. Figure 8-123 Add variable for staff activity 426 WebSphere Business Integration for SAP .Select the output terminal and click New Variable.Enter the Name approvalResult and select Type Built in Boolean from the drop-down list and then click OK (see Figure 8-123).Select the input terminal and choose Variable input from the drop-down list.

Use Case 2: WBISF using WBI Adapter for mySAP. 67. 53. Chapter 8. 60.Enter the code snippet listed in “Prepare negative notification” on page 655.Select Built-in and choose Otherwise from the drop-down list and click OK.sak400 and select InternalOrder. 68.Select the preparepositiveNotification activity and click Show Java. 63. 73.Enter the code snippet listed in “Prepare positive notification” on page 654. 72.52. 70. 66.txt result=getApprovalResult().Approval2createPurchaseOrder.Highlight Condition.process.Highlight Condition.checkApprovalPolicy2Approval. 59.Click OK and save the process with Ctrl+S.Highlight Condition.Select Service Projects → InternalOrderProcess_Service → process.Select Java and click OK.Select Java and click OK.Right-click on the link between the Approval activity and the preparenegativeNotification node and click Properties. 71.Click Show Java and enter the code in Example 8-5 into the user section. 57.getCheckMaterialReturn().com 427 .Click Show Java and enter the code in Example 8-4 into the user section. 65. Example 8-4 Snippet . 69. 54. Example 8-5 Snippet .Enter the code snippet listed in “Prepare Service call” on page 652. 56.Highlight Condition. 58.Select the preparenegativeNotification activity and click Show Java. 62.Right-click on the link between the checkApprovalPolicy activity and the createPurchaseOrder activity and click Properties.Right-click the link between the Approval activity and the createPurchaseOrder activity and click Properties. 64.Right-click the link between the checkApprovalPolicy activity and the Approval node and click Properties.getValue().Select the prepareCall activity and click Show Java. 61. 55.txt result=getCheckMaterialResponse().Select Built-in and choose Otherwise from the drop-down list and click OK.

Right-click on the file and select Enterprise Services → Generate Deploy Code . The window in Figure 8-125 on page 429 should appear. 76. 428 WebSphere Business Integration for SAP .Choose Create a new port and binding.74.. The window in Figure 8-124 should appear. Figure 8-124 Deploy code generation properties 75.Select Inbound binding type EJB and select Next...

com 429 .Figure 8-125 File location window 77. Chapter 8.Accept the default values in the file location screen and click Next. The window in Figure 8-126 on page 430 should appear. Use Case 2: WBISF using WBI Adapter for mySAP.

83.Add the InternalOrderProcess_Service project to run on the local test server... 79.Make sure that all other Service projects that are used in this business process are also deployed.Switch to the Server perspective. 84.Adjust the default JNDI name if necessary and select Finish. 81..Restart the local test server. 80.Select Finish.Figure 8-126 JNDI name selection window 78. 430 WebSphere Business Integration for SAP . 82.Right-click on the LocalEE test server and select Add and remove projects.

The window in Figure 8-127 should appear. Chapter 8. 2. such as C:\eclipse\workspace\SAP_ICL\Connectors\SAPConnector. Type in SAPConnector as the connector name. Use Case 2: WBISF using WBI Adapter for mySAP. Tip: The connector configuration file is located in the workspace directory of the Integration library created earlier in this chapter.4.com 431 .con 1. for example. Open the Visual Test Connector from the Windows Start Menu.9 Configure the Visual Test Connector The Visual Test Connector (VTC) can be used to simulate the Enterprise Information System. 7. Set the Broker Type to WAS. Select File → Create/Select Profile from the menu. The window in Figure 8-128 on page 432 should appear. This section describes how to configure the virtual test connector to pick the original connector configuration file and simulate the SAP system. 3. Press OK. Figure 8-127 Create a new VTC Profile 4. Select the new profile SAPConnector from the profile list and press OK. 6. 8. Select File → New Profile from the menu of the popup. 5. Select the connector configuration file from the Integration Component library project.8.

432 WebSphere Business Integration for SAP . The window in Figure 8-129 should appear. Select File → Connect to start and connect the connector.Figure 8-128 VTC profile list 9. Figure 8-129 Virtual Test Connector GUI The VTC displays all business object that are sent to this connector and allows you to create the appropriate reply messages.

Example 8-6 Snippet . This method is described in the following paragraph with the assumption that the WebSphere Business Integration Server Foundation is installed on a Linux server. Note: Make sure that the remote application server root directory is mapped to a local drive letter before starting to create a new remote server instance.5 Deployment of the business process The completed business process can deployed in two different ways. is up and running.com 433 . This allows the user to easily see if data arrives at the connector or not.bat SAP WAS -cC:\WSADIE50\workspace\SAP_ICL\Connectors\SAPConnector. The window in Figure 8-130 on page 434 should appear. Use Case 2: WBISF using WBI Adapter for mySAP.com Connector component of the adapter can be registered to start as a Windows service or triggered manually as a batch file.startSAPConnector.bat in the connectors\SAP directory (Example 8-6).4. Switch to the server perspective and create a new Server and Server Configuration.10 Configure the mySAP.8. This batch file takes parameters to parameterize the startup of a specific connector. 1. The second method is using the Remote Agent Controller to connect remotely to an application server and install the applications directly out of the development environment. Installing Enterprise Archives is a standard WebSphere Application Server task that can be reviewed in the WebSphere InfoCenter. The default adapter installation includes a batch file called start_SAP. Chapter 8. The first option is to use the export mechanism of the WebSphere Studio Application Developer Integration Edition and generate Enterprise Archive (EAR) files that can be installed on the target run-time application server.txt C: cd C:\WebSphereAdapters\connectors\SAP\ start_SAP.com Connector The mySAP. and the remote agent controller task is also started on the deployment target server. In this Use Case scenario. it is started using a custom batch file.con 8.

Enter RemoteWBISF as the Server name and choose Integration Server as the Server type and click Next. The window in Figure 8-131 on page 435 should appear.Figure 8-130 Create remote deployment server 2. 434 WebSphere Business Integration for SAP .

The Remote Agent Controller.com 435 . Use Case 2: WBISF using WBI Adapter for mySAP.Figure 8-131 Remote server host name 3. is now contacted to retrieve application server specific information (see Figure 8-132 on page 436). Chapter 8. which is installed on the remote server. Enter the full qualified server name into the Host name field and click Next. 4.

Click Next.Figure 8-132 Review installation directory 5. 436 WebSphere Business Integration for SAP . Review the remote application server settings and adjust them if they are not correct. The window in Figure 8-133 on page 437 should appear.

Choose to create a new remote file transfer instance using the Copy file transfer mechanism and click Next. Use Case 2: WBISF using WBI Adapter for mySAP. Chapter 8.com 437 .Figure 8-133 Remote target directory type 6. The window in Figure 8-134 on page 438 should appear.

Figure 8-134 Remote target directory 7. Click Next. 438 WebSphere Business Integration for SAP . The window in Figure 8-135 on page 439 should appear. Enter the local drive letter that maps to the remote application server root directory into the Remote target directory field.

com 439 .Figure 8-135 Application server HTTP port 8.1” on page 361. Set up WebSphere MQ connection factory and queue destination. Before starting the remote server the first time. Enable security. Refer to 8.3.3. Use Case 2: WBISF using WBI Adapter for mySAP. Verify if the correct HTTP port is used and click Finish. the same adjustments have to be done in the remote server configuration. which was done for the local test environment. Adjust WebSphere environment variables for WebSphere MQ and IBM DB2. “Configuration of WSADIE V5. Set up Business process container. Chapter 8. Configuration check list: Enable Administrative Console.

Switch to the Server perspective. Figure 8-136 Add projects to remote server 11. 8. 10..6 Run the business process The complete business process can be executed and tested using the built in WebSphere Process Choreographer Web client. 9. The window in Figure 8-136 should appear. 12.Right-click on the RemoteWBISF server and select Add and remove projects. Any user that has an account in the local operating system where the WebSphere Business Integration Server Foundation is running can place an internal order using the Web client.Add all applications that are required for the business process to run and select Finish. The user 440 WebSphere Business Integration for SAP . restart the remote application server and review the produced log files before deploying any application.Tip: After making all adjustments in the remote application server configuration.. Make sure that no errors are listed in the application server log..Restart the remote application server.

com 441 . Use Case 2: WBISF using WBI Adapter for mySAP.with the user ID Administrator is authorized to approve order requests. The window in Figure 8-137 on page 442 should appear. 1. To simulate approval and rejection scenarios. Chapter 8. 8. an authorized user places three orders. Two orders for products that do require approval. Open the URL http://<hostname>:9080/bpe/webclient in a Web browser. One order for a product that does not require approval.6. The approver is rejecting one order and accepting the others.1 Create internal orders using the Web client This section describes how to create exemplary internal orders using the WebSphere Process Choreographer Web client.

3. Enter valid credentials in the Login form and click OK. 442 WebSphere Business Integration for SAP .Figure 8-137 Login to Web client 2. The window in Figure 8-138 on page 443 should appear. Select Process Templates List → My Templates in the left navigation pane.

Chapter 8. The window in Figure 8-139 on page 444 should appear. Click on the InternalOrder process from the template list.Figure 8-138 Select InternalOrder process 4. Use Case 2: WBISF using WBI Adapter for mySAP.com 443 .

The window in Figure 8-140 on page 446 should appear. 6.Figure 8-139 Start InternalOrder process 5. Fill in all input fields using the test data in Table 8-5 on page 445. Review process settings and click on Start Instance. 444 WebSphere Business Integration for SAP .

Chapter 8.11. Otherwise. Use Case 2: WBISF using WBI Adapter for mySAP.11.2004 00001000 R-4005 1200 1 Restriction: This test data assumes that a standard SAP R/3 IDES system is accessed.2004 00001000 R-1003 or DPC1017 1000 1 Non-approval anything 11.com 445 .Table 8-5 Test data Field name Process instance name deliveryDate employeeNumber materialNumber plant quantity Requires approval anything 11. appropriate test data has to be generated before running the scenario.

446 WebSphere Business Integration for SAP . 8. Select Process Templates List → My Templates in the left navigation pane. 9. Enter order data to request a non-approval product and click on Start Instance.Figure 8-140 Place first internal order 7. Click on the InternalOrder process from the template list.

Enter the order data to request a approval product that requires approval and click Start Instance. The window in Figure 8-141 should appear.com 447 .Enter input mask by clicking on Start Instance. Chapter 8. Figure 8-141 Place second internal order 11.10. Use Case 2: WBISF using WBI Adapter for mySAP.

Select Process Templates List → My Templates in the left navigation pane.Enter the input mask by clicking on Start Instance.Click on the InternalOrder process from the template list. 14. Figure 8-142 Place third internal order 448 WebSphere Business Integration for SAP .12. The window in Figure 8-142 should appear. 13.

Chapter 8.com 449 .Click on the InternalOrder process from the template list. 19. Use Case 2: WBISF using WBI Adapter for mySAP.Enter the input mask by clicking Start Instance.15.Select Process Instance List → Created By Me in the left navigation pane to review all created order requests.Enter the order data to request a approval product that requires approval and click Start Instance. 16. The window in Figure 8-143 on page 450 should appear. 18. 17.Select Process Templates List → My Templates in the left navigation pane.

Figure 8-143 Internal order request list 20. The window in Figure 8-144 on page 451 should appear. 21.The first order is already in the Finished state because it did not require approval.Select the first order to see more details. 450 WebSphere Business Integration for SAP .

Use Case 2: WBISF using WBI Adapter for mySAP.com 451 . The notification e-mail was sent to the listed address. The internal order was created and has the displayed order number.Figure 8-144 Processed order details of first order 22.Select Process Instance List → Created By Me in the left navigation pane to review all created order requests. 23.The output message section displays the reply from the involved back-end systems. Chapter 8.

Figure 8-145 Order details of second order 25.Select the second order to see more details.24.The order is in the Running state. The My To Dos section displays that the process is waiting for the Approval activity to complete. The window in Figure 8-145 should appear. 452 WebSphere Business Integration for SAP .

The order is in the Running state. Chapter 8.Select Process Instance List → Created By Me in the left navigation pane to review all created order requests. The My To Dos section displays that the process is waiting for the Approval activity to complete. 27.26.Select the third order to see more details (see Figure 8-146). Figure 8-146 Order details of third order 28. Use Case 2: WBISF using WBI Adapter for mySAP.com 453 .

6. 454 WebSphere Business Integration for SAP . 1.2 Execute approval activity using the Web client This paragraph describes how to process internal orders that are waiting approval using the WebSphere Process Choreographer Web client. The window in Figure 8-147 on page 455 should appear. 2.29. such as Administrator. Enter the credentials of the authorized approval user ID in the Login form.Click on Logout in the upper right corner. and click OK. 8. Open the URL http://<hostname>:9080/bpe/webclient in a Web browser.

Chapter 8. The window in Figure 8-148 on page 456 should appear. Use Case 2: WBISF using WBI Adapter for mySAP.Figure 8-147 Approvers My To Dos list 3. Select the second order to see more details.com 455 .

Click on the Claim button. The window in Figure 8-149 on page 457 should appear.Figure 8-148 Second order details 4. 456 WebSphere Business Integration for SAP .

Click on the second order entry to start the approval activity. Chapter 8. The second order is now in status Claimed. The window in Figure 8-150 on page 458 should appear.com 457 . Use Case 2: WBISF using WBI Adapter for mySAP.Figure 8-149 Second order start approval activity 5.

In this Use Case. 8. 7.Figure 8-150 Approve second order 6. Click on Complete. the approver has to enter the word true into the value field to approve an internal order or anything else to reject it. 458 WebSphere Business Integration for SAP . Enter true in the value field.

The window in Figure 8-151 should appear.Enter false in the value field.Click on Logout in the upper right corner. Chapter 8. Admit a claim on the third order in the same way as done before for the second order. Use Case 2: WBISF using WBI Adapter for mySAP.com 459 . 11. 12.9. Figure 8-151 Reject third order 10.Click on Complete.

3 Review approved internal orders using the Web client This section describes how to review processed internal orders using the WebSphere Process Choreographer Web client. Enter the credentials of the user ID that was used originally to create the three internal order requests and click OK. The window in Figure 8-152 on page 461 should appear. 460 WebSphere Business Integration for SAP . 3.6. Select Process Instance List → Created By Me in the left navigation pane to review all created order requests. Open the URL http://<hostname>:9080/bpe/webclient in a Web browser. 1. 2.8.

Use Case 2: WBISF using WBI Adapter for mySAP. 5.Figure 8-152 Internal order request list after approval 4. Chapter 8. Select the second internal order entry to display its details. All internal orders are now in status Finished. The window in Figure 8-153 on page 462 should appear.com 461 .

Select Process Instance List → Created By Me in the left navigation pane to review all created order requests. 462 WebSphere Business Integration for SAP . The internal order number and notified mail address is displayed. 7. The internal order has been approved.Figure 8-153 Second internal order details after approval 6.

Figure 8-154 Third internal order details after rejection 9. Select the second internal order entry to display its details. Use Case 2: WBISF using WBI Adapter for mySAP.com 463 . The window in Figure 8-154 should appear. The internal order has been rejected. Chapter 8. No internal order has been placed.8.

A key capability is the reuse of service based enterprise functions to orchestrate new business processes.7 Summary This Use Case describes the complete development lifecycle of a custom business process developed with WebSphere Studio Application Developer Integration Edition (WSADIE) and executed on WebSphere Business Integration Server Foundation (WBISF).8. Beyond the invocation of service based enterprise functions. the new created business process can empower users to interact with the process and influence the process flow. This enterprise services can incorporated even if they are distributed across systems and implemented on different platforms. 464 WebSphere Business Integration for SAP .

This chapter contains the following topics: Operational model Installation of WebSphere Business Integration components Configuration of WebSphere Business Integration components Development of the WebSphere Business Integration components Deployment of WebSphere Business Integration components Running the scenario © Copyright IBM Corp. 465 . 2004. This gives the reader an opportunity to see how quickly an established SAP R/3 system can be integrated with an external system that may not make business sense to be moved to an SAP environment.com and JDBC This chapter describes a SAP integration scenario implementation using the WebSphere InterChange Server (WICS) and the WebSphere Business Integration Adapters for JDBC and mySAP. Use Case 3: WICS using WBI Adapter for mySAP.9 Chapter 9. All rights reserved.com.

9. the WebSphere InterChange Server is used as an integration hub to integrate two systems. and to demonstrate how to unify multiple disparate systems into a homogeneous business processing environment. the aim is to show how it can be used to integrate any number of systems and processes on a larger scale. To obtain a fully functional installation of WebSphere InterChange Server.2 Installation and configuration This chapter describes how to perform an installation of WebSphere InterChange Server and its prerequisite software and WebSphere Business Integration Adapters. Figure 9-1 gives you an overview of the operational model. Based on this simple integration.1 Operational model In this business integration. Figure 9-1 Operational model 9. all of the prerequisite software must be installed: Microsoft Windows 2000 and service packs IBM WebSphere MQ IBM Java Runtime Environment 466 WebSphere Business Integration for SAP .

1 IBM WebSphere Business Integration Adapter for mySAP.tst file to match Figure 9-2 on page 468.2 Installation of WebSphere MQ The installation of WebSphere MQ has been documented earlier.com IBM WebSphere Business Integration Adapter for JDBC 9. Use Case 3: WICS using WBI Adapter for mySAP.IBM DB2 V8. “Installing WebSphere MQ V5.3 with CSD04” on page 171. The service pack may be obtained directly from the Windows Update site http://www.2. Edit the <WICS dir>/mqseries/crosswords_mq.3. or Advanced Server.windowsupdate. Chapter 9.2. Server.1 Installing Microsoft Windows 2000 Service Packs Installation of the WebSphere InterChange Server requires a minimum patch level of Service Pack 4 when installing on Microsoft Windows 2000 Professional.2. 9.com and JDBC 467 .com. please refer to 6.2. 9.3 Configuration of WebSphere MQ 1.

Figure 9-2 WebSphere MQ local queue configuration 468 WebSphere Business Integration for SAP .

manager (see Figure 9-3). Figure 9-4 Modifying the Configure Queue manager shortcut 4.2. Figure 9-3 Creating a queue manager 3. right-click.queue. Chapter 9. Select Programs → IBM WebSphere InterChange Server → IBM WebSphere MQ → Configure Queue Manager (see Figure 9-5 on page 470). Use Case 3: WICS using WBI Adapter for mySAP.manager.com and JDBC 469 . select Properties (see Figure 9-4). In the Target field.queue. Open a command prompt and enter crtmqm itsob. update the queue manager name to itsob. 5. Select Start → Programs → IBM WebSphere InterChange Server → IBM WebSphere MQ → Configure Queue Manager.

Figure 9-5 Configuring the queue manager 6. 470 WebSphere Business Integration for SAP . If it runs successfully. the output looks similar to that of Figure 9-6 on page 471.

Figure 9-6 Queue manager configuration output Chapter 9.com and JDBC 471 . Use Case 3: WICS using WBI Adapter for mySAP.

Enter DB2SET DB2CODEPAGE=1208.2.9. From a DOS prompt. A new DOS window should launch entitled DB2 CLP. 9.1 with FixPack 5” on page 150. “Installing IBM DB2 UDB Version 8.3. enter the following commands: db2 update dbm cfg using SYSADM_GROUP db2adm db2stop db2start The responses should match those in Figure 9-8. enter the following commands: net localgroup db2adm /add net localgroup db2adm db2admin /add net localgroup db2adm administrator /add The responses should match those in Figure 9-7. 3.4 Installation of IBM DB2 The installation of IBM DB2 is common to all the Use Cases in this book. Enter db2cmd.5 Configuration of IBM DB2 1. 472 WebSphere Business Integration for SAP . Please refer to the installation instructions in 6. Figure 9-8 IBM DB2 administration configuration 4. In the new DB2 CLP window.1. Figure 9-7 IBM DB2 administrative group creation 2.2.

com and JDBC 473 . Issue the CREATE DATABASE command. enter attach to db2 user db2admin using sak400. Next. Use Case 3: WICS using WBI Adapter for mySAP. Figure 9-10 DB2 Instance Attach 7. Figure 9-9 Startup of IBM DB2 command line processor (CLP) 6.5. as shown in Figure 9-11. as shown in Figure 9-12. Enter quit at the db2 => prompt. 9. where db2admin is the administrative ID used to access DB2 and sak400 is the password associated with that ID. This creates the WICS repository database to be used. Figure 9-11 Create database command 8. Next. Confirmation that the connection was successful is displayed in Figure 9-10. enter db2 and a screen similar to that of Figure 9-9 on page 473 is displayed. Issue the UPDATE command. Chapter 9.

UNITOFMEASURE VARCHAR (3) . 13.Figure 9-12 Database manager configuration update 10. PLANT VARCHAR (4) . 14. DB2 DB2 DB2 DB2 CONNECT TO ICSREPOS UPDATE DATABASE CONFIGURATION USING MAXAPPLS 60 DEFERRED UPDATE DATABASE CONFIGURATION USING APPLHEAPSZ 4096 DEFERRED CONNECT RESET Figure 9-13 ICSREPOS database configuration 11.The tables used for this example were created using the following SQL: CREATE TABLE DB2ADMIN. ENDREPLLEADTIME DATE . CONSTRAINT CC1084350596672 PRIMARY KEY ( XREFKEY) ) . DOCNUM VARCHAR (10) . "CMMTD_QTY" DECIMAL(18."REQ_QTY" DECIMAL(18. INDICATOR CHARACTER (1) . 0) .AVAILABILITY (XREFKEY) ON DELETE NO ACTION ON UPDATE NO ACTION ) . QTYAVAILABLE DECIMAL (18.0). CUSTNUM VARCHAR (10) .Enter DB2STOP. CHKGRULE VARCHAR (2) . STOCKINDICATOR CHARACTER (10) .0) . WBSELEMENT VARCHAR (24) . ITEMNUM VARCHAR (6) .Enter DB2SET DB2_RR_TO_RS=yes. BATCH VARCHAR (10) .Issue the commands below. NO CACHE ) .CONSTRAINT CC1083933830391 FOREIGN KEY (XREF_KEY) REFERENCES DB2ADMIN."CMMTD_DATE" DATE ."REQ_DATE" DATE . The results should be similar to those in Figure 9-13. 474 WebSphere Business Integration for SAP . CREATE TABLE "DB2ADMIN". 12."REC_COM" ("XREF_KEY" INTEGER NOT NULL . INCREMENT BY 1.Enter DB2START.IN "USERSPACE1" .AVAILABILITY ( XREFKEY INTEGER NOT NULL GENERATED ALWAYS AS IDENTITY (START WITH 1. MATERIAL VARCHAR (18) . STORLOC VARCHAR (4) .

'ST'. '1201'. ENDREPLLEADTIME) VALUES ('5'. CHKGRULE."REQ_QTY" DECIMAL(18.2. click Next (see Figure 9-15 on page 476). '2232'.CREATE TABLE "DB2ADMIN". At the Welcome screen. 'AC'. 258. ITEMNUM. UNITOFMEASURE. MATERIAL. Launch setupwin32."REQ_DATE" DATE .exe to start the installer 2. PLANT."WMDVSX" ("XREF_KEY" INTEGER NOT NULL . '1200'. "LINE_INDEX" INTEGER. '22345'. '1456'.IN "USERSPACE1" . CHKGRULE.AVAILABILITY (BATCH. ITEMNUM. '1200'. STORLOC. QTYAVAILABLE. WBSELEMENT. 'duh'. '2004-05-12') 9. Choose the language for the installer to run in and click Next (see Figure 9-14). Figure 9-14 Installation language selection 3. '2004-05-02') INSERT INTO DB2ADMIN. 'DPC1017'. ENDREPLLEADTIME) VALUES ('6'.The sample data used is as follows: INSERT INTO DB2ADMIN. Use Case 3: WICS using WBI Adapter for mySAP."MRP_ELEMENT" CHAR(12) . '12345'. 'DPC1017'. STORLOC. '1201'.6 Installation of Interchange Server 1. '3456'. Chapter 9. 'ST'. CONSTRAINT CC1083935333609 FOREIGN KEY (XREF_KEY) REFERENCES DB2ADMIN. '1232'. CUSTNUM. QTYAVAILABLE. 47. 'duh'. PLANT. CUSTNUM.0) .AVAILABILITY (BATCH.AVAILABILITY (XREFKEY) ON DELETE NO ACTION ON UPDATE NO ACTION ) . 'AC'. 15. WBSELEMENT. UNITOFMEASURE. DOCNUM. DOCNUM.com and JDBC 475 . MATERIAL.

Accept the license agreement and click Next (see Figure 9-16). Now the License Agreement screen is displayed.Figure 9-15 WebSphere InterChange Server InstallShield wizard 4. 476 WebSphere Business Integration for SAP . Enter the directory to install WebSphere InterChange Server into. Figure 9-16 License agreement window 5. then click Next (see Figure 9-17 on page 477).

After the appropriate installation options are chosen. Chapter 9.com and JDBC 477 .Figure 9-17 Installation directory selection window 6. An options screen is presented to select which items are to be installed. Choose the options denoted in Figure 9-18 on page 478. Use Case 3: WICS using WBI Adapter for mySAP. click Next.

3 for messaging support. Select IBM DB2 V8. Check the box next to Use IBM WebSphere MQ 5.1 as the database type. 478 WebSphere Business Integration for SAP .Figure 9-18 Installation options window 7. Click Next (see Figure 9-19 on page 479).

Click Next (see Figure 9-20). Use Case 3: WICS using WBI Adapter for mySAP. The DB2 installation instructions book shows the correct path as C:\SQLLIB. ITSOB_WICS was used in this Use Case. Figure 9-20 WebSphere InterChange Server name 9. Chapter 9.Figure 9-19 Database selection window 8. Enter the name of the Interchange Server. Enter the directory path to install DB2 into. Click Next (see Figure 9-21 on page 480).com and JDBC 479 .

Figure 9-21 IBM DB2 installation location 10. Figure 9-22 WebSphere InterChange Server service configuration 11. 480 WebSphere Business Integration for SAP . Click Next (see Figure 9-22).Choose to have WebSphere InterChange Server run as a service.Click Next on the Select Program Folder screen (see Figure 9-23 on page 481).

com and JDBC 481 . Figure 9-24 Review installation options 13.Figure 9-23 Start programs folder name selection 12. Chapter 9.Review the summary information and click Next. Use Case 3: WICS using WBI Adapter for mySAP.The installation begins and takes several minutes to complete.

After the installation has completed. (Figure 9-26) Figure 9-26 WebSphere InterChange Server configuration wizard launch window 482 WebSphere Business Integration for SAP . the Interchange Server Configuration Wizard is launched.Figure 9-25 Installation progress 14.

This is typically CHANNEL1. The name of the queue manager (this does not need to be created at this point). Chapter 9. Use Case 3: WICS using WBI Adapter for mySAP.Choose the location for WebSphere InterChange Server’s log file and then click on the WebSphere MQ tab (see Figure 9-27). Enter the WebSphere MQ channel that to be used. Figure 9-27 WebSphere InterChange Server configuration 16. d. b. Port number the WebSphere MQ is listening on.Enter the following information (Figure 9-28 on page 484). Host name of the machine. default is 1414. c.com and JDBC 483 . then click on the Database tab: a.15.

Transactions Database: icsrepos Login: db2admin Password: sak400 Max Connections: Unlimited 484 WebSphere Business Integration for SAP . Max Pools.On the Database tab. Database: DB2 Max Connections.Figure 9-28 WebSphere InterChange Server configuration . enter the following information.WebSphere MQ 17. a. Event Management Database: icsrepos Login: db2admin Password: sak400 Max Connections: Unlimited c. then click Apply (see Figure 9-29 on page 485). b. and Idle Connections should be fine with the default values.

Repository Database: icsrepos Login: db2admin Password: sak400 Max Connections: Unlimited e.com and JDBC 485 . Click OK. Flow Monitoring Database: icsrepos Login: db2admin Password: sak400 Max Connections: Unlimited Figure 9-29 WebSphere InterChange Server configuration .database 18. Chapter 9. Use Case 3: WICS using WBI Adapter for mySAP.d.A confirmation window shows that the WebSphere InterChange Server configuration has been updated (see Figure 9-30 on page 486).

Click Exit (see Figure 9-31).Figure 9-30 Configuration update confirmation 19.A confirmation screen shows that the WebSphere InterChange Server was successfully installed (see Figure 9-32 on page 487). 486 WebSphere Business Integration for SAP . Figure 9-31 WebSphere InterChange Server configuration 20. Click Next.

Figure 9-33 Installation completion Chapter 9.Figure 9-32 Installation summary 21. Use Case 3: WICS using WBI Adapter for mySAP.Choose Yes.com and JDBC 487 . restart my computer and click Finish (see Figure 9-33).

then correct it. click Next (see Figure 9-34). 2.2.Installation of 4. When the welcome screen is displayed.exe 3. Click Next (see Figure 9-35 on page 489).2 toolset patch and server patch.2. Ensure that WICS and all WICS tools are stopped. This field should be prepopulated with the correct value.2 toolset patch and server patch Here we discuss the installation of the the 4.2. Part I: Toolset patch 1. Figure 9-34 Toolset InstallShield wizard 4. enter the directory path where WICS was installed. Launch 4222_toolset_patch. Next.2. If it is not the correct location of the WICS installation. 488 WebSphere Business Integration for SAP .

then click Next (see Figure 9-36). Use Case 3: WICS using WBI Adapter for mySAP. Review the summary information.com and JDBC 489 . Figure 9-36 Installation options review window 6.Figure 9-35 WebSphere InterChange Server installation directory 5. Chapter 9. The installation should begin (see Figure 9-37 on page 490).

Figure 9-38 Installation summary window Part II: Server patch 1.Figure 9-37 Installation progress 7. click Finish (see Figure 9-38). When it has completed. 490 WebSphere Business Integration for SAP . Create a directory inside the WICS installation folder called backup.

jar <temp dir>/lib/xwbase.txt -> backup/InterchangeSystem. Use Case 3: WICS using WBI Adapter for mySAP. Copy the following files to the appropriate location <temp dir>/lib/CrossWorlds. After the wizard initializes.jar 3. the Welcome screen is displayed.7 JDBC Adapter Installation 1.jar <temp dir>/lib/xworacle.com and JDBC 491 .jar <temp dir>/lib/xwutil. Move the following files from the lib folder to the backup folder: lib/CrossWorlds. Unzip the WICS_4.2.jar -> <WICS dir>/lib/xworacle. Click Next (see Figure 9-40 on page 492).txt 4.2. Move the following file from the messages folder to the backup folder: messages/InterchangeSystem. Figure 9-39 JDBC adapter installation language selection 3. 2.jar -> <WICS dir>/lib/xwsqlserver.jar -> <WICS dir>/lib/CrossWorlds. choose the language for installation and click OK (see Figure 9-39).jar->backup/xwbase.jar->backup/CrossWorlds.2_WIN.jar -> <WICS dir>/lib/xwutil.jar <temp dir>/lib/xwsqlserver. 5.2.jar lib/xwbase.zip file to a temporary location.jar->backup/xwsqlserver.jar->backup/xworacle. Launch setupwin32.jar->backup/xwutil.txt -> <WICS dir>/messages/InterchangeSystem. At the language selection screen.jar lib/xwsqlserver.jar lib/xwutil.jar <temp dir>/messages/InterchangeSystem.exe to start the adapter installation.2.txt 9.jar lib/xworacle. Chapter 9.jar -> <WICS dir>/lib/xwbase.

In this Use Case. Enter the directory to install the adapter into. Accept the terms of the license agreement and click Next (see Figure 9-41). Click Next (see Figure 9-42 on page 493). the installation is done in the same directory that WebSphere InterChange Server is installed into. Figure 9-41 License agreement 5. 492 WebSphere Business Integration for SAP .Figure 9-40 JDBC adapter InstallShield wizard 4.

com and JDBC 493 . as shown in Figure 9-44 on page 494. and then click Next (see Figure 9-43). Figure 9-43 Installation options review 7. Click Next. Enter the name of WebSphere InterChange Server. Use Case 3: WICS using WBI Adapter for mySAP. Chapter 9. Review the installation options.Figure 9-42 Adapter installation directory 6.

The installation should begin (see Figure 9-46 on page 495). Enter the name of the program group for the adapters to be added to. 494 WebSphere Business Integration for SAP . The Default was chosen for this Use Case.Figure 9-44 WebSphere InterChange Server name entry window 8. Figure 9-45 Start programs folder name selection 9. Click Next (see Figure 9-45).

Use Case 3: WICS using WBI Adapter for mySAP. Click Finish (see Figure 9-47). a window is displayed stating that the installation has completed successfully. Figure 9-47 Installation completion Chapter 9.com and JDBC 495 .After the installation has completed.Figure 9-46 Installation progress 10.

bat to include the path to the sapjco.dll must also be copied to this location.2.jar (see Figure 9-48).1.2. 4.2.bat file 6. “JDBC Adapter Installation” on page 491. Copy the entire contents of the directory where the sapjco-ntintel-2.1.com Adapter is identical to the JDBC Adapter installation described in 9.2 Installation for use with mySAP. this .1. 2.8 mySAP. Edit <wics directory>\connectors\ODA\SAP\start_SAPODA. 5.zip was unzipped into <wics directory>\connectors\SAP\jco. 3.dll to C:\Winnt\System32 (or into wherever the Windows System directory is). Unzip sapjco-ntintel-2.com Adapter Installation Installation of the mySAP.9.com Adapter 1.zip to a temporary location. Note: Several people have commented that sapjcorfc. 496 WebSphere Business Integration for SAP . Figure 9-48 start_SAPODA. Add <wics directory>\connectors\SAP\jco to the Environment Path & Classpath. In this Use Case.7. Edit <wics directory>\connectors\SAP\start_SAP. Copy the file librfc32. SAP JCO 2.jar (see Figure 9-49 on page 497).2.bat to include the path to the sapjco.dll was not copied to the C:\Winnt\System32 directory and no problems were experienced.

Repeat the process in the opposite direction.bat file 9. Transformation from the SAP specific business object to a generic business object which WebSphere InterChange Server can work with. 3. Figure 9-50 on page 498 gives an overview of the integration process. 2. 4. 5. Extraction of the data from SAP via a WebSphere Business Integration Adapter into an SAP specific business object. Transformation from the generic business object into a IBM DB2 specific business object. Use Case 3: WICS using WBI Adapter for mySAP. 6.com and JDBC 497 . Chapter 9.3 Development In this section. A collaboration process within the WebSphere InterChange Server to perform operations as needed on the generic business object. The integration process involves several steps: 1.Figure 9-49 start_SAP. the integration project is developed. Injection of the IBM DB2 specific business object into IBM DB2 via a WebSphere Business Integration Adapter.

Expand the + button next to Workbench and select Perspective. d. select Window → Preferences.Figure 9-50 Integration process This process development is detailed in the following sections. c. e. Under Available perspectives. 498 WebSphere Business Integration for SAP . The window in Figure 9-51 on page 499 should appear. Project creation 1. b. Once the System Manager is open. a. Click OK. choose System Manager and click on Make Default. Configure the workspace. Launch the System Manager by selecting Start → Programs → IBM WebSphere InterChange Server → IBM WebSphere Business Integration Toolset → Administrative → System Manager.

Figure 9-51 System Manager preferences window 2. Right-click on the Resource icon (see Figure 9-52) and choose Close All.com and JDBC 499 . Use Case 3: WICS using WBI Adapter for mySAP. Figure 9-52 WebSphere Studio Workbench Chapter 9.

then choose New Integration Component Library (Figure 9-55). click OK. An error message is displayed (see Figure 9-53). Figure 9-55 Project creation 500 WebSphere Business Integration for SAP . Figure 9-54 System Manager 5.3. The workspace looks like the window in Figure 9-54. This is normal. Right-Click on Integration Component Libraries. Figure 9-53 Warning message 4. Exit the System Manager Tool and reopen.

Import SAP Business Object 1.com Object Discovery Agent (see Figure 9-57 on page 502). Start the SAP ODA by selecting Start → Programs → IBM WebSphere Business Integration Adapters → Adapters → Object Discovery Agent → mySAP.com and JDBC 501 . Chapter 9. Figure 9-56 New Integration Component Library Creation of Business Objects Here we discuss the creation of Business Objects.6. Use Case 3: WICS using WBI Adapter for mySAP. Enter the project name and click Finish (Figure 9-56).

(Figure 9-60 on page 503). Select File → New Using ODA. Figure 9-59 New Business Object dialog 4. Figure 9-58 Create New Business Object 3... 502 WebSphere Business Integration for SAP . right-click on Business Objects and select Create New Business Object.. In System Manager. (see Figure 9-58).Figure 9-57 Launch the SAP Object Discovery Agent (ODA) 2. Cancel the New Business Object dialog box when it opens (Figure 9-59)..

com and JDBC 503 . Figure 9-61 Business Object Wizard . When the Business Object Wizard opens.Figure 9-60 Create new Business Object Using ODA 5. Chapter 9. Select the SAPODA agent.agent selection 6. The items in Table 9-1 must be specified. SAP logon client. SAP logon password. and then click Next (see Figure 9-62 on page 504 as well). The SAPODA agent appears in the located agents box on the right. Table 9-1 ODA configuration parameters Item Username Password Client ASHostname Description SAP logon user name. and then click Next (Figure 9-61). click on the Find Agents button. Host name of SAP server. The ODA must be given the appropriate information to connect to the SAP system. Use Case 3: WICS using WBI Adapter for mySAP.

On the source selection screen. as shown in Figure 9-63 on page 505. and then click Next. locate and select the BAPI_MATERIAL_AVAILABILITY. Figure 9-62 Business Object Wizard . 504 WebSphere Business Integration for SAP . Recommended location: <wics install directory>/connectors/SAP/client.Item FileDestination Description Location to save ODA generated files.configure ODA 7.

com and JDBC 505 . Use Case 3: WICS using WBI Adapter for mySAP. Chapter 9. On the source confirmation screen.source selection 8.Figure 9-63 Business Object Wizard . click Next (see Figure 9-64 on page 506).

Figure 9-64 Business Object Wizard . enter the values from Table 9-2. the business objects are generated (see Figure 9-66 on page 507). On the Business Object properties screen.confirmation of source 9.The next prompt (Figure 9-65) displays a selection of additional optional parameters for generation. Figure 9-65 Optional parameter prompt 11.Next. Table 9-2 Recommended business object property values Item Prefix Verb ServerSupport UseFieldName Value sap_ Retrieve Yes No 10. Select No. and then click OK. 506 WebSphere Business Integration for SAP .

completion Chapter 9. shut down the ODA SAPODA. Use Case 3: WICS using WBI Adapter for mySAP.Choose to Save the generated objects to the project in the drop-down list.com and JDBC 507 .Figure 9-66 Business object generation 12. Figure 9-67 Business Object Wizard . and then click Finish (see Figure 9-67). open the new business objects in a separate window.

14.13.Click on the General tab. Enter the name of the collaboration. 508 WebSphere Business Integration for SAP . and Unit_of_Measure_for_display are the key fields. In the Application-specific information area (Figure 9-68). Make a note of the name chosen. Leave the child business objects as they are. as it is required later. look at the Server line.Save and close the business object. as in Figure 9-69 on page 509. Notice the name of the BAPI object coming from the server as well as the name of the collaboration processing this object. Figure 9-68 Application-specific information 15.Now the completed business object is presented. Plant. Change the key fields so that Material_number.

. Start the JDBC ODA by selecting Start → Programs → IBM WebSphere Business Integration Adapters → Adapters → Object Discovery Agent -> JDBC Object Discovery Agent. In System Manager. then click Next (see Figure 9-70 on page 510). The JDBCNC agent appears in the located agents box on the right. 5. Chapter 9. click the Find Agents button. 4. 2. 3. When the Business Object Wizard opens..Figure 9-69 sap_bapi_material_availability business object Import DB2 Business Objects 1.com and JDBC 509 . Cancel the New Business Object dialog box when it opens. Use Case 3: WICS using WBI Adapter for mySAP.... Go to File → New Using ODA. right-click on Business Objects and select Create New Business Object. Select this JDBCNC agent..

ibm. Table 9-3 ODA configuration parameters Item UserName Password DatabaseURL DatabaseDriver Value db2admin sak400 jdbc:db2://<hostname>: <port>/database_name com.DB2Driver Description IBM DB2 logon user name IBM DB2 logon password IBM DB2 specific connection URL IBM DB2 driver Figure 9-71 Business Object Wizard .agent selection 6.jcc.db2. and then click Next (see also Figure 9-71).Figure 9-70 Business Object Wizard .agent configuration 510 WebSphere Business Integration for SAP . Now the ODA must be given the appropriate information to connect to the IBM DB2 system. The items in Table 9-3 must be specified.

com and JDBC 511 .confirmation of source Chapter 9. Use Case 3: WICS using WBI Adapter for mySAP. locate and select the AVAILABILITY. and WMDVSX tables. On the source selection screen. REC_COM.source selection 8. as shown in Figure 9-72. Figure 9-72 Business Object Wizard .7. click Next (see Figure 9-73). On the source confirmation screen. and then click Next. Figure 9-73 Business Object Wizard .

The business objects are generated (Figure 9-75). enter db2_ for the Prefix and set Add Stored Procedure to No. Figure 9-75 Business object generation 512 WebSphere Business Integration for SAP . and then click OK. Figure 9-74 Business object properties 10. On the Business Object properties screen (see Figure 9-74).9.

and Figure 9-79 on page 515.The completed business objects are presented. Figure 9-78 on page 514. Use Case 3: WICS using WBI Adapter for mySAP. and then click Finish (see Figure 9-76).completion 12. Save and close the business object.11.Choose to Save the generated objects to the project in the drop-down list. open the new business objects in a separate window.com and JDBC 513 . shut down the ODA JDBCNC. Change the key fields so that the key fields are as in Figure 9-77 on page 514. Chapter 9. Figure 9-76 Business Object Wizard .

Figure 9-77 db2_AVAILABILITY business object Figure 9-78 db2_REC_COM business object 514 WebSphere Business Integration for SAP .

Chapter 9. In System Manager.com and JDBC 515 .Figure 9-79 db2_WMDVSX Business Object Create the Generic_Business_Object 1. as shown in Figure 9-81 on page 516.. Create the business object. 2.. Use Case 3: WICS using WBI Adapter for mySAP. right-click on Business Objects and select Create New Business Object.. Name the new business object Generic_Object_Object. Figure 9-80 New business object 3. and then click OK (see Figure 9-80).

.Figure 9-81 Generic_Business_Object 4. (Figure 9-82). Save the project and close. Right-click on Maps and select Create New Map. Creation of maps Here we discuss the creation of maps.. Figure 9-82 Create new map 516 WebSphere Business Integration for SAP . Mapping from SAP to Generic Business Object 1.

Select InventoryAvailabilityValidation_Lib. Use Case 3: WICS using WBI Adapter for mySAP. and then click Next (see Figure 9-85 on page 518). Chapter 9. and then click Next (see Figure 9-84).2. Figure 9-83 Project selection 3. and then click Next (see Figure 9-83). Select Generic_Business_Object as the destination business object. as the project contains this map. Figure 9-84 Source business object selection 4. Select sap_bapi_material_availability as the source business object.com and JDBC 517 .

A window is displayed where items from the SAP business object can be mapped to the general business object. Figure 9-86 Map name and mapping direction specification 6. Map the fields shown in Table 9-4 on page 519.Figure 9-85 Destination business object selection 5. 518 WebSphere Business Integration for SAP . Mapping is achieved by clicking on the item to be mapped from in the Src table and dragging to the item to be mapped to in the Dest table. Enter a name for the map being created. and then click Finish (see Figure 9-86). and for Mapping Direction choose Application-Specific to Generic.

com and JDBC 519 . in this Use Case. we are doing a Retrieve request. When SAP generates a request. In order to ensure that the proper operations are performed on our request. Expand String in the Library pane and select Replace. Figure 9-87 Mapped: sap_bapi_material_availability to Generic_Business_Object 7. the window should be identical to that of Figure 9-87.Table 9-4 Mapping: sap_bapi_material_availability to Generic_Business_Object Src sap_bapi_material_avail ability Verb Material_Number Plant Unit_of_Measure_for_disp lay Dest Generic_Business_Obje ct Verb MATERIAL PLANT UNITOFMEASURE Rule Custom Move Move Move When mapping the columns has completed. Use Case 3: WICS using WBI Adapter for mySAP. however. Chapter 9. Notice that the Verb has a rule of Custom. a. it always generates a Create request. the Verb must be manipulated. Double-click on the Custom Rule to launch the Activity designer.

520 WebSphere Business Integration for SAP . For an example of what the completed activity diagram should look like. In the Content pane.com business adapter. and close. d. Save the map to the project. Connect the replaced string to the input of ObjGeneric_Business_Object. f. e.b. refer to Figure 9-88. Although the connector specifies that the business object use the Retrieve verb. g. Give the new constant a value of Create. h. compile. Figure 9-88 Activity diagram for custom verb mapping rule 8. Create another constant with a value of Retrieve. Connect the output from Objsap_bapi_material_availability to the input of the Replace. the request coming from SAP always generates a Create. 9. j. drag the Replace icon into the main graphical work area. Save and close the Activity Editor. Right-click in an empty area of the workspace and choose New Constant. i. Connect the output of Retrieve to new string input of Replace. The custom mapping used in this instance is a workaround for RFC Server interaction. Look for this to be resolved in an upcoming service release of the mySAP. Connect the output of the Create constant to the old string input of Replace. c.

The completed mapping matches that shown in Figure 9-90 on page 522. Map the fields as shown in Table 9-5. Use the db2_AVAILABILITY object as the destination.db2_Availability Verb MATERIAL PLANT UNITOFMEASURE Rule Move Move Move Move Chapter 9. Create a new map. as in Mapping from SAP to Generic Business Object. 4.com and JDBC 521 . Table 9-5 Mapping for Generic_Business_Object to db2_AVAILABILITY Src Generic_Business_Object Verb MATERIAL PLANT UNITOFMEASURE Dest . Name the map and choose Generic to Application . Use Case 3: WICS using WBI Adapter for mySAP. Use the Generic_Business_Object as the source. Figure 9-89 Map name and mapping direction specification 5. 3.Mapping from General Business Object to DB2 1. 2.Specific for the Mapping Direction (see Figure 9-89).

3. and close. 2. Name the map and choose Application-Specific to Generic for the Mapping Direction. Create a new map as in Mapping from SAP to Generic Business Object. 522 WebSphere Business Integration for SAP . 4.Figure 9-90 Mapped: Generic_Business_Object to db2_AVAILABILITY object 6. Use the object Generic_Business_Object as the destination. Use the db2_AVAILABILITY as the source. Mapping from DB2 to Generic Business Object 1. Save the map to the project. compile.

The completed mapping matches that shown in Figure 9-92 on page 524.db2_Availability Verb MATERIAL PLANT UNITOFMEASURE QTYAVAILABLE INDICATOR ENDREPLLEADTIME Dest Generic_Business_Object Verb MATERIAL PLANT UNITOFMEASURE QTYAVAILATPLNT INDICATOR ENDREPLLEADTIME Rule Move Move Move Move Move Move Custom Chapter 9.com and JDBC 523 .Figure 9-91 Map name and mapping direction specification 5. Use Case 3: WICS using WBI Adapter for mySAP. Map the fields as shown in Table 9-6. Table 9-6 Mapping for db2_AVAILABILITY to Generic_Business_Object Src .

refer to Figure 9-93 on page 525. Expand Date in the Library pane and select Format change. c.ENDREPLLEADTIME. d.ENDREPLLEADTIME into the date of the Format change. Give the new constant a value of MM/dd/yy. 524 WebSphere Business Integration for SAP .Figure 9-92 Mapped: db2_AVAILABILITY object to Generic_Business_Object 6. Right-click in an empty area of the workspace and choose the New Constant. Connect the output from Objdb2_AVAILABILITY. f. e. For an example of what the completed activity diagram should look like. In the Content pane. b. i. h. Connect the output of the yyyy-MM to the output format of Format change. drag the Format change icon into the main graphical work area. Connect the formatted date into the input of ObjGeneric_Business_Object. Create another constant with a value of yyyy-MM. a. j. g. Double-click on the Custom Rule. which launches the Activity designer. Connect the output of the MM/dd/yy constant to the input format of Format change.

Create a new map. and close.Figure 9-93 Custom mapping for db2_AVAILABILITY to Generic_Busines_Object 7. Use Case 3: WICS using WBI Adapter for mySAP.com and JDBC 525 . Save the map to the project. Mapping from Generic Business Object to SAP 1. compile. 3. Use the Generic_Business_Object as the source. 2. Chapter 9. 4. Name the map and choose Generic to Application-Specific for the Mapping Direction (see Figure 9-94 on page 526). Use the object sap_bapi_material_availability as the destination. as in Mapping from SAP to Generic Business Object.

Figure 9-94 Map name and mapping direction specification 5. Table 9-7 Mapping: Generic_Business_Object to sap_bapi_material_availability Src Generic_Business_Object Verb MATERIAL PLANT UNITOFMEASURE QTYAVAILATPLNT INDICATOR ENDREPLLEADTIME Dest sap_bapi_material_availability Verb Material_number Plant Unit_of_measure_for_display Quantity_available_at_plant_ level Indicator__X___not_available__ N___no_check_ End_of_replenishment_lead_ time Rule Move Move Move Move Move Move Move 526 WebSphere Business Integration for SAP . Map the fields as shown in Table 9-7. The completed mapping matches that shown in Figure 9-95 on page 527.

com and JDBC 527 .. On the New Connector window (Figure 9-97 on page 528). (see Figure 9-96). The JDBC Connector 1. Use Case 3: WICS using WBI Adapter for mySAP. Chapter 9. click Cancel. Figure 9-96 Create new connector 2.Figure 9-95 Generic_Business_Object to sap_bapi_material_availability_object Create connectors Here we discuss the creation of connectors. Right-click on the Connectors Folder and choose to Create New Connector..

Figure 9-98 Open file menu 4... Go to File → Open → From File. (see Figure 9-98). Locate and open CN_JDBC.txt.Figure 9-97 New connector template selection 3. 528 WebSphere Business Integration for SAP . It should be located in <WICS directory>\repository\JDBC\ (see Figure 9-99 on page 529).

Various property sheets for the JDBC Connector are displayed.jcc. Table 9-8 JDBC Connector: Connector-Specific tab recommended settings Property Application Password ApplicationUserName DatabaseURL JDBCDriverClass RDBMSVendor Value used sak400 db2admin jdbc:db2://itsoe.ibm. The properties of interest are listed in Table 9-8.com and JDBC 529 .Figure 9-99 JDBC template file 5. Use Case 3: WICS using WBI Adapter for mySAP. All other properties should remain at their default values (see Figure 9-100 on page 530).DB2Driver IBM Chapter 9.isicc.ibm. Click on the Connector-Specific Properties tab.de.db2.com:50000/i avdb com.

Click on the Standard Property tab. Table 9-9 Standard properties Property AgentTraceLevel ApplicationName BrokerType ControllerTraceLevel Value used 5 JDBCConnector ICS 5 530 WebSphere Business Integration for SAP .Figure 9-100 JDBC connector specific properties 6. Set the properties as specified in Table 9-9 (see Figure 9-101 on page 531 as well).

Be sure to enable Agent Support for the db2_AVAILABILITY object. as in Figure 9-102.Property DeliveryTransport PollFrequency Value used IDL no Figure 9-101 JDBC connector specific properties 7. Use Case 3: WICS using WBI Adapter for mySAP. Figure 9-102 JDBC connector supported business objects Chapter 9. Add the db2_AVAILABILITY object and the Generic_Business_Object.com and JDBC 531 . Click on the Supported Business Objects tab.

Right-click on the Connectors Folder and choose Create New Connector..8. Save to Project and close. It should be located in <WICS directory>\repository\SAP\ (see Figure 9-104). 3. 4. Next.. The SAP Connector 1. Locate and open CN_SAP.. Click on the Associated Maps tab.txt. various property sheets for the SAP Connector are displayed. and then select Map_From_DB2_to_GenBusObj (see Figure 9-103). click Cancel. select Explicit Binding for db2_AVAILABILITY. 2. Figure 9-104 SAP connector template file 5.. 532 WebSphere Business Integration for SAP . All other properties should remain at their default values (see Figure 9-105 on page 533). Figure 9-103 JDBC connector map associations 9. Select File → Open → From File.. Click on the Connector-Specific Properties tab. The properties of interest are listed in Table 9-10 on page 533.. On the New Connector window.

Table 9-10 SAP Connector Configuration Property ApplicationPassword ApplicationUserName Client Hostname Language Sysnr RfcProgramId Modules cargill 800 siccserv.com E 00 INVENTORYAVAILABILITYVALIDATION RfcServer Value used here Figure 9-105 SAP connector-specific properties 6. Chapter 9. Click on the Standard Property tab.de. Set the properties specified in Table 9-11 on page 534 (see also Figure 9-106 on page 534).isicc.com and JDBC 533 .ibm. Use Case 3: WICS using WBI Adapter for mySAP.

as in Figure 9-107 on page 535. Add the sap_bapi_material_availability object and the Generic_Business_Object.Table 9-11 Standard properties Property AgentTraceLevel ApplicationName BrokerType ControllerTraceLevel DeliveryTransport PollFrequency Value used 5 SAPConnector ICS 5 IDL no Figure 9-106 SAP connector standard properties 7. 534 WebSphere Business Integration for SAP . Click on the Supported Business Objects tab. Be sure to enable Agent Support for the sap_bapi_material_availability object.

Right-click on the Collaboration Templates folder and choose Create the New Collaboration Template (see Figure 9-109). Create Collaboration Template 1. Use Case 3: WICS using WBI Adapter for mySAP. Figure 9-109 Create new collaboration template 2.com and JDBC 535 . and then select Map_From_SAP_to_GenBusObj (see Figure 9-108). Chapter 9. and then click OK (see Figure 9-110 on page 536). Enter a name for the template. Figure 9-108 SAP connector map associations 9. select Explicit Binding for sap_bapi_material_availability. Save to Project and close. Click on the Associated Maps tab. A New Template dialog is presented.Figure 9-107 SAP connector supported business objects 8.

. 536 WebSphere Business Integration for SAP . Assign the BO Type of Generic_Business_Object for both ports. Right-click on Scenarios and select New Scenario.. Click on the Ports and Triggering Events tab. an Inbound and an Outbound. (see Figure 9-113 on page 537).Figure 9-110 New collaboration template creation 3. 5. Figure 9-111 Edit template definitions 4. Figure 9-112 Port creation and assignments 7. Add two Ports. Right-click on Definitions and select Open Template Definitions (see Figure 9-111). 6. and then click Apply (see Figure 9-112).

Right-click on the Action Node and select Add service node. Use Case 3: WICS using WBI Adapter for mySAP. then click OK (see Figure 9-114). Figure 9-114 Scenario naming 9.Connect the Action Node to the End Success Node. 11. 12.Connect the Start Node to the Action Node. Give the new Scenario a name. 10.Figure 9-113 Scenario creation 8. Chapter 9. add an Action Node and an End Success Node (see Figure 9-115 on page 538).com and JDBC 537 . In the new scenario window.

14.Click Apply and then Close (see Figure 9-116 on page 539). set the Port to outbound.Right-click on the Service Node and select Properties.. the Verb to Retrieve. 15. and the BO variable to triggeringBusObj.Figure 9-115 Collaboration scenario 13.In the Regular service call area. 538 WebSphere Business Integration for SAP ...

Figure 9-116 Set collaboration target port 16. Right-click on Collaboration and select Create New Collaboration Object (see Figure 9-118 on page 540).Save to Project and Close.com and JDBC 539 . Chapter 9. Use Case 3: WICS using WBI Adapter for mySAP. Implementation 1. click on the drop-down in the Retrieve column of the Inbound Port and select the newly created scenario (see Figure 9-117).Back at the Template Definitions. Figure 9-117 Set scenario that triggers collaboration 17.

select the template that was created previously and give the new Collaboration Object a name. On the Create New Collaboration screen (Figure 9-119 on page 541). 540 WebSphere Business Integration for SAP . and then click Next.Figure 9-118 Launch collaboration creation wizard 2.

Use Case 3: WICS using WBI Adapter for mySAP. Bind the Inbound Port to the SAP Connector and the Outbound Port to the JDBC Connector (see Figure 9-120 on page 542).Figure 9-119 Create new collaboration 3.com and JDBC 541 . Chapter 9.

Figure 9-120 Port bindings 4. 542 WebSphere Business Integration for SAP . Click Finish (see Figure 9-121 on page 543).

4 Deployment 1. In order to deploy the project to the WebSphere InterChange Server. a project must first be created under InterChange Server Projects in User Projects. To do this.Figure 9-121 Collaboration general properties 9. Chapter 9.com and JDBC 543 . Use Case 3: WICS using WBI Adapter for mySAP. right-click on Interchange Server Projects and select New ICS Project (see Figure 9-122 on page 544).

Figure 9-123 New user project 544 WebSphere Business Integration for SAP .Figure 9-122 WebSphere InterChange Server project creation 2. Give the new project a name. and then click Finish (see Figure 9-123). Select the check box next to InventoryAvailabilityValidation_Lib (Figure 9-123).

Locate the installation directory of the WebSphere InterChange Server and go into the bin directory.bat file (see Figure 9-124).bat 4. start the IBM WebSphere InterChange Server. Use Case 3: WICS using WBI Adapter for mySAP. Launch the PersistentNameServer. Figure 9-124 Location of PerstentNameServer. Select Start → Programs → IBM WebSphere InterChange Server → IBM WebSphere InterChange Server → IBM WebSphere InterChange Server (see Figure 9-126). a DOS prompt with the word “Ready” is displayed (see Figure 9-125). When the Persistent Name Server has started successfully.com and JDBC 545 . Next.3. Figure 9-125 Persistent Name Server startup 5. Now the WebSphere InterChange Server must be started so that the project may be deployed to it. Figure 9-126 WebSphere InterChange Server startup Chapter 9.

the User name and Password to access a WebSphere InterChange Server are admin and null. click and drag the project to the server registered in Step 8. By default. This log is found by default in the WebSphere InterChange Server installation directory. This starts the deployment process (see Figure 9-128 on page 547). and the Password. 546 WebSphere Business Integration for SAP .6.log for an entry saying InterChange Server “<the server_name>” is ready. return to System Manager. One way to verify that the server has successfully started is to view the InterchangeSystem. In the InterChange Server Component Management window. Once the WebSphere InterChange Server has started successfully. the User name. respectively (see Figure 9-127). right-click on InterChange Server Instances and select Register Server. 7. 8. Enter the Server name. In the WebSphere Business Integration System Manager window under InterChange Server Projects. Figure 9-127 Register a WebSphere InterChange Server 9.

com and JDBC 547 .As a final check.Figure 9-128 Deployment 10. 12. then right-click on the Collaboration Templates folder and choose Compile All. as seen in Figure 9-129. Use Case 3: WICS using WBI Adapter for mySAP.A warning message maybe received that the project has uncompiled items. Chapter 9. a dialog box is displayed.After the project has deployed successfully. verify that the maps have been compiled on the server also (see Figure 9-130 on page 548). Simply right-click on the Maps folder and select Compile All. Figure 9-129 Deployment confirmation 11.

Log onto the SAP system and go to the Display and Maintain RFC destinations panel (sm59).5 Testing 1.If the Collaboration Objects cannot be started. Click Create (see Figure 9-132 on page 549). Figure 9-131 Collaboration template compilation 9. 548 WebSphere Business Integration for SAP . then compilation of the Collaboration Templates maybe required (see Figure 9-131).Figure 9-130 Map compilation 13.

USE_CASE_2 was used in this configuration. Specify an Activation Type of Registered Server Program. Name the new RFC Destination. 4.Figure 9-132 RFC destinations 2. Use Case 3: WICS using WBI Adapter for mySAP. Chapter 9. 3. Specify a Program ID for the program to use when connecting.com and JDBC 549 . and then save (see Figure 9-133 on page 550).

Figure 9-133 RFC destination creation 5. and click on the Test icon (see Figure 9-134 on page 551). enter the BAPI_MATERIAL_AVAILABILITY Function Module. Go to the Function Builder panel (se37). 550 WebSphere Business Integration for SAP .

Use Case 3: WICS using WBI Adapter for mySAP. Figure 9-135 Test function module Chapter 9. and Unit information. Enter Plant.com and JDBC 551 .Figure 9-134 SAP function module selection screen 6. This is the RFC Destination Specified in Step 2 above. Material. and then click on the Execute icon (see Figure 9-135). 7. Enter the RFC target sys.

9. A key point about this process is how one can effectively plug into SAP and interact with any remote database. This functionality will allow you to integrate with systems that may not yet have 552 WebSphere Business Integration for SAP . Provided everything is done properly. Figure 9-136 Results received as Export parameters 9. a request should go from SAP to WebSphere InterChange Server to DB2 and data should be returned to the SAP Window. The process was developed using tools supplied with the WebSphere InterChange Server. as in Figure 9-136.8.6 Summary This scenario describes a complete business process that is representative of a system integrating with SAP. Congratulations! SAP has successfully integrated with IBM DB2 via the WebSphere InterChange Server.

com and JDBC 553 .adapter support. Chapter 9. The ability to perform such an integration without having to develop custom code greatly enhances a company’s ability to stay current with new code releases of software. Use Case 3: WICS using WBI Adapter for mySAP. Being able to take advantage of new software and new capabilities faster brings a business closer to the realization of the on demand workplace. but use a common database.

554 WebSphere Business Integration for SAP .

WebSphere Business Integration adapter for SAP Exchange Infrastructure. IBM WebSphere InterChange Server. All rights reserved. 2004. are covered. The chapter ends with a description of how to run the overall scenario. and SAP Exchange Infrastructure itself. the configuration of the predominant building blocks of the implementation. Use Case 4: Integration of SAP XI with WBI InterChange Server This chapter describes the implementation of Use Case 4. © Copyright IBM Corp. CustomerDataRepository. and demonstrates how to exchange documents between Lotus Domino databases and SAP R/3 using two Integration Brokers. the operational model is described. 555 . WebSphere Business Integration adapter for Lotus Domino. and SAP Exchange Infrastructure in between. Based on this introduction. The chapter starts with an overview of the underlying business process. After that.10 Chapter 10.

2. Within the WebSphere InterChange Server. Lotus Domino Server 1 Customer Contacts Database 2 IBM WebSphere Business Integration InterChange Server 4 SAP Exchange Infrastructure SAP R/3 5 6 Figure 10-1 Business process model of Use Case CustomerDataRepository 1.10. For the implementation described in this chapter. New or updated documents within this database are detected by the WebSphere Business Integration adapter for Lotus Domino and transferred to the WebSphere InterChange Server. A collaboration object represents an WebSphere InterChange Server internal business process.1 Overview of Use Case CustomerDataRepository The business process that underlies Use Case CustomerDataRepository is depicted in Figure 10-1. Therefore. the process is left rather simple in that it just copies business objects from its input to its output port. the application dependent business object DominoDocument is mapped into a generic business object Customer before it get processed by a collaboration object (Figure 10-2 on page 557). Domino documents get converted into an InterChange Server internal data format called a DominoDocument business object. The process starts when a document representing customer data is created or updated in the Lotus Domino database Customer Contacts. 556 WebSphere Business Integration for SAP . 3.

Use Case 4: Integration of SAP XI with WBI InterChange Server 557 . using JMS as the underlying transport mechanism. this IDoc instance is inserted into the SAP R/3 internal database. the DEBMAS01 business object is transmitted as a XML message by the WebSphere Business Integration adapter for SAP Exchange Infrastructure. where it gets converted into an IDoc of type DEBMAS01. 5. which is an XML representation of a SAP IDoc structure DEBMAS01. 6.Collaboration Object Customer Customer Map Map Adapter for Domino DominoDocument Debmas01 Adapter for SAP XI WebSphere InterChange Server Figure 10-2 WebSphere InterChange Server internal processing 4. The Customer business object is mapped to a DEBMAS01 business object. before it is forwarded to the SAP R/3 back-end system (Figure 10-3). the XML message is received by the corresponding JMS adapter and relayed to the IDoc adapter. Finally. After that. At the SAP Exchange Infrastructure. SAP Exchange Infrastructure JMS Adapter IDoc Adapter Figure 10-3 SAP Exchange Infrastructure internal components Chapter 10.

itsoc IBM WebSphere Business Integration InterChange Server.2. it is assumed that the WebSphere InterChange Server is installed on node ITSOC according to the description given in Chapter 9.1 Oracle 9.0 JMS Adapter SAP Web AS Java. V1. When configuring the WebSphere InterChange Server. V1. the implementation of Use Case CustomerDataRepository consists of four major building blocks: The Domino Server for the creation of Customer documents The WebSphere InterChange Server receiving documents from the Domino Server and relaying them to the SAP Exchange Infrastructure as XML messages The SAP Exchange Infrastructure that receives XML messages from the WebSphere InterChange Server and forwards them to the SAP R/3 as a back-end system The SAP R/3 that is responsible for processing the business logic Each of the four major building blocks is installed and configured on a dedicated node. Therefore. V6. “Use Case 3: WICS using WBI Adapter for mySAP.2. as shown in Figure 10-4.40 siccserv ALE SAP R/3 Enterprise itsoe Lotus Domino Server. 558 WebSphere Business Integration for SAP .2 Operational model for CustomerDataRepository As has been shown in Figure 10-1 on page 556. V6. In particular. For each node. V4.2 WBI Adapter for Lotus Domino. V8.com and JDBC” on page 465.0 itso_xi SAP Exchange Infrastructure (XI) V3. the operational model lists the installed software systems that are relevant to the implementation of the described Use Case. . use the host specific values shown in Table 10-1 on page 559.1 WBI Adapter for XI.0 IBM WebSphere MQ V5.10.0 Figure 10-4 Operational model: CustomerDataRepository implementation This chapter assumes that the systems shown in Figure 10-4 are already installed on their respective nodes.40 IDoc Adapter SAP Web AS ABAP. V6. it only covers the configurations of these systems as far as the implementation of this Use Case is concerned.3 IBM DB2.

5. the general architecture of a connector is described. It starts with the introduction of the architecture of the adapter for Lotus Domino. Before covering the adapter for Lotus Domino in more detail. If.1. must be installed: The XML Data Handler V2.0 Adapter for Lotus Domino Version 1. the name of the WebSphere InterChange Server and the destination folder is required. “Use Case 3: WICS using WBI Adapter for mySAP. the following WebSphere InterChange Server components. the connector agent. Chapter 10.com and JDBC” on page 465.3 Configuring the adapter for Lotus Domino This section describes the configuration and testing of the WebSphere Business Integration adapter for Lotus Domino (adapter for Lotus Domino for short). the following adapters need to be installed on node ITSOC: Adapter for SAP Exchange Infrastructure (SAP XI) Version 1. the same name must be chosen as that of the WebSphere InterChange Server. Before integrating the adapter into the overall implementation.2 Follow the Installation description in Chapter 9. The last part of this section introduces the testing methodology applied within this chapter. the connector controller (Figure 10-5 on page 560). which are provided as their own installation packages. it is tested separately.2 The IBM WebSphere Business Integration Collaboration Foundation Finally.queue.1 with FixPack 1. A connector consists of an application specific part.manager In addition.Table 10-1 Host specific configurations: implementation of ICS on node ITSOC Name hostname InterChange Server name WebSphere MQ queue manager Value ITSOC ITSOC_WICS itsoc. It then covers the configuration of the Domino server and the configuration of the adapter itself. Furthermore. 10. Use Case 4: Integration of SAP XI with WBI InterChange Server 559 . and a more generic part. a Lotus Notes Version 6 client must be installed on ITSOC for configuring the adapter for Lotus Domino and running the Use Case scenario. during the installation.

and converts application data. is still dependent on the application. which the agent creates. which it exchanges with the back-end system. or CORBA IIOP. This business object. Driven by the defined map.Application Data Connector Agent Protocols and Transformations Application Specific Business Object Connector Controller Map Generic Business Object Collaboration Object Figure 10-5 Components of a connector The connector agent communicates with the back-end system using its native formats and protocols. the connector agent must be configured to handle business objects of different types. 560 WebSphere Business Integration for SAP . before it is submitted to a collaboration object. the application dependent business object is transformed into a generic business object within the connector controller. JMS. The connector agent sends the application dependent business object to the connector controller either using WebSphere MQ. If the back-end system sends and receives data of different formats. into the WebSphere InterChange Server internal format of a business object.

Use Case 4: Integration of SAP XI with WBI InterChange Server 561 . the connector agent retrieves the corresponding customer document from the Customer Contacts database. or updated Customer documents. The steps for request processing are similar. The following steps are executed: 1. The connector controller converts the application specific business object DominoDocument to a generic business object Customer before relaying it to the WebSphere InterChange Server for further processing. The connector agent converts the retrieved Domino document into a DominoDocument business object and submits it to the connector controller. 3. it stores it as an event document in the Event Table database. Having detected a new event document. as well request processing.10. a Lotus Domino database. It supports event processing. which allows external back-end systems to store their data in a Lotus Domino database. Figure 10-6 on page 562 gives an overview of the components involved in processing the events occurring within the Lotus Domino database Customer Contacts. Chapter 10. The connector agent of the adapter for Lotus Domino polls the Event Table for unprocessed documents.3. deleted. these steps are not elaborated on in more detail. The Event Listener monitors the Lotus Domino database Customer Contacts for new. If the Event Listener detects such an event. 2. Since the implementation of the CustomerDataRepository only comprises event processing. Part of the adapter is a special process.1 The architecture of the adapter for Lotus Domino The adapter for Lotus Domino supports bidirectional exchange of Lotus Domino documents with external back-end systems using the WebSphere InterChange Server as an intermediate broker. meaning it automatically transfers new or updated documents to the WebSphere InterChange Server. 4. and an Event Table. 5. the Event Listener.

562 WebSphere Business Integration for SAP .2 Configuring the Domino server for the adapter The implementation of Use Case CustomerDataRepository requires a Lotus Domino server on node ITSOE that hosts the Customer Contacts database (Figure 10-4 on page 558).3. Ensure that this Domino user exists and that it has the right to run restricted and unrestricted Java agents on the Domino server. “The architecture of the adapter for Lotus Domino” on page 561. Besides creating the Customer Contacts database. The steps comprise the configuration of a technical user that the adapter needs for accessing the Domino server and the installation of the event processing parts.1. Technical user for the adapter for Lotus Domino The adapter for Lotus Domino uses the credentials of the Domino user Domino Adapter for accessing the Domino databases. the configuration of this Domino server itself must be modified in order to support the event processing.3.InterChange Server Business Object "Customer" 5 Connector Controller Lotus Domino Server Lotus Domino Database "Customer Contacts" Business Object "Domino Document" 4 Connector Agent 3 Event Listener 1 2 Event Table Figure 10-6 Architecture of the adapter for Lotus Domino for event processing 10. as described in 10. The latter must be specified within the server configuration document in the Domino Directory database on the Domino server.

click on the button Create a new database. 2. Open this database and navigate to the folder Configuration → Servers → All Server documents. Call the tool Lotus Domino Designer® and log in with a user with manager privileges. switch to the Security tab. and the select the directory database with the file name names. 2. Open the Lotus Notes client. Use Case 4: Integration of SAP XI with WBI InterChange Server 563 . select File → Database → Open. and add the user Domino Adapter to the item Run restricted Java/JavaScript/COM.nsf. where the new Customer Contacts database is specified. as depicted in Figure 10-7 on page 564. This template provides the contact form that defines the structure of customer documents. This configuration is done using the Lotus Notes client with a user that has Manager privileges on the newly created Customer Contacts database. Creating the Customer Contacts database The Customer Contacts database is created using the standard Lotus Notes database template Personal Address Book. Chapter 10. configure the access privileges for the technical user Domino Adapter so that the adapter can access the database subsequently. The window New Database opens. log in with a user that has administrator privileges. and press OK. Within the Lotus Domino Designer. Open this document. To create the database: 1. After creation.1. choose the server ITSOE.

Figure 10-8 Access Control List for Customer Contacts 564 WebSphere Business Integration for SAP . and add the technical user Domino Adapter to the access control list with the Editor privilege (Figure 10-8).Figure 10-7 Create the Customer Contacts database Assuming that an icon for the database has been added to the workspace... right-click on that icon and select Database → Access Control .

and Update events and save the document. Select New Configuration from the menu bar Enter the name customer. select the Create.nsf nbiald. Chapter 10.gif BIALD_newconfig.gif BIALD_movetotrash. assuming that C:\lotus\Domino is the Domino server root directory. Copy these files as depicted in Table 10-2 to the node ITSOE of the Domino server. Choose ITSOE as the server and BIALD_EventTable as the database and click Open (Figure 10-9).Configuring the Event Table database The installation of the adapter for Lotus Domino delivers the files for the event processing and event listener in the directory C:\WICS\connectors\Domino\dependencies on node ITSOC. Delete. Figure 10-9 Open Event Table database Switch to EventConfigurationView in the navigation pane in the left panel of the opened database.nsf of the Customer Contacts database into the field Database path of the configuration document. Table 10-2 Files to copy into the Domino server directories Files BIALD_emptytrash.gif BIALD_EventTable. Use Case 4: Integration of SAP XI with WBI InterChange Server 565 .dll Description Event Table bitmaps Where to copy on ITSOE C:\lotus\Domino\Data Event Table Event listener C:\lotus\Domino\Data C:\lotus\Domino The Event Table database must be configured to hold documents that describe events in the Customer Contacts database. In the Event Type row. Open the Event Table database that has been installed before using a Lotus Notes Client and select File → Database → Open.

AdminP. Finally.INI for HTTP and IIOP ServerTasks=Update.INI EXTMGR_ADDINS=nbiald. Table 10-3 Add-on to NOTES.Sched.jar 566 WebSphere Business Integration for SAP .INI configuration file on ITSOE. Ensure that these protocols are supported by checking that HTTP and DIIOP are defined for the entry ServerTask in the NOTES.Figure 10-10 Event Table configuration document Modify NOTES.INI configuration file on ITSOE (Table 10-4 on page 558).CalConn.Replica.INI file only become effective after a restart of the Domino server.DIIOP.Router. Table 10-4 Entries within NOTES. which does not contain all the required exceptions.jar Copy file to on ITSOC C:\WICS\connectors\Domino\NCSO.HTTP The modifications of the NOTES.AMgr.jar that contains the Lotus Domino toolkit for Java/CORBA from the Domino server directories on ITSOE to the directory of the adapter for Lotus Domino on ITSOC.INI Add the line in Table 10-3 to the C:\lotus\Domino\NOTES. Note: This replaces the version of the NCSO. as specified in Table 10-5.dll The adapter for Lotus Domino uses HTTP and IIOP for accessing the Domino server. copy the file NCSO. Table 10-5 Copying NCSO.jar Copy file from ITSOE C:\lotus\Domino\java\NCSO. This entry starts the Event listener process together with the Domino server.jar file that comes with the installation of the adapter.DECS.

10. this section ends with a description of a test procedure for the adapter. configuration of the business objects are described. a collaboration object has to be defined additionally. Tools Business Object Designer Map Designer Process Designer Connector Configurator Relationship Designer Integration Library Business Objects Maps Relationships Collaborations Connectors User Project Business Objects Maps Relationships Collaborations Connectors InterChange Server Design Build Unit of Deployment Deploy Figure 10-11 Elements of the WBI system manager Chapter 10. the system manager offers various tools for developing integration applications. the map specification is introduced. All these configurations are performed from within the System Manager that provides an Eclipse-based development and management environment for the WebSphere InterChange Server development projects. Finally. After that. As depicted in Figure 10-11. and deploying the application on the WebSphere InterChange Server. Subsequently. Use Case 4: Integration of SAP XI with WBI InterChange Server 567 .3. managing the components of an application in integration libraries and user projects.3 Configure the Domino connector Configuring an WebSphere InterChange Server adapter for receiving or sending business objects usually consists of the following steps: Definition of the application dependent and generic business object types Definition of maps between the application dependent and generic business object types Configuration of the connector configuration itself For testing a connector configuration. This section starts with a setup of the System Manager environment.

which contains all configuration objects for the Use Case described within this chapter: Select the context menu of the Integration Component Libraries folder within the WebSphere Business Integration System Manager view and choose New Integration Component Library. The business object type DominoDocument provides a complete description of all fields of a document within a Domino database.. 568 WebSphere Business Integration for SAP . Figure 10-13 Name the new integration library Configure the business object DominoDocument The configuration of the connector for Lotus Domino requires an application dependent business object type DominoDocument and a generic business object type Customer (Figure 10-6 on page 562).Setup of the System Manager Start the system manager by issuing Start → Programs → IBM WebSphere InterChange Server → Administrative → System Manager. Create the Integration Component Library CustomerDataRepository_Lib.. An instance of a DominoDocument consists of an array of DominoItem child business objects that each represent the description and contents of a single field within the Domino document (Figure 10-14 on page 569). Figure 10-12 Create a new integration library Fill in the project name CustomerDataRepository_Lib within the New Integration Component Library and press the Finish button (Figure 10-13). (Figure 10-12).

Then select New → Open from file and browse to the file C:\WICS\repository\Domino\BIADominoDocument.Figure 10-14 Business object type DominoDocument The installation of the adapter for Lotus Domino delivers a template for the DominoDocument business object type that must be installed within the library CustomerDataRepository_lib: Navigate to the library CustomerDataRepository_lib within the left pane of the system manager. and select Create New Business Object .txt.. the business object definition of DominoDocument is displayed in the business object designer (Figure 10-16 on page 570). right-click on Business Objects. After successful validation.. Press the Save button and close the Business Object Designer tool. expand it. Figure 10-15 Create New Business Object The window of the Business Object Designer is opened. Chapter 10. Use Case 4: Integration of SAP XI with WBI InterChange Server 569 . (Figure 10-15). Ignore the prompt for specifying Business Object Name and Application Specific Information by pressing the Cancel button.

which is defined for the CustomerDataRepository scenario. the WebSphere InterChange Server supports a two-step mapping scheme. incoming application dependent data is mapped onto a generic business object. contains the essential information that is going to be conveyed from the Customer Contacts database to the SAP R/3 570 WebSphere Business Integration for SAP . Therefore. after some internal processing. in particular for a multi-party scenario.Figure 10-16 DominoDocument business object type in Business Object Designer Create the business object Customer The implementation of Use Case CustomerRepositoryData requires a mapping between input data of type DominoDocument to output data of type DEBMAS01 within the WebSphere InterChange Server (Figure 10-2 on page 557). into the application-dependent structure of the receiving side. In order to limit the number of mappings. The generic business object Customer. which is converted.

right-click on the row with entry ObjectEventId and select Insert above from the context menu (see Figure 10-18). Set the name of the new business object to Customer and press the OK button (Figure 10-17). right-click on Business Objects and select Create New Business Object .. insert the attributes. Start creating the Customer business object by navigating to the library CustomerDataRepository_lib within the left pane of the system manager. Starting with that new row. expand it. It contains an attribute for each field that is to be extracted from a document within the Customer contacts database.. (Figure 10-15 on page 569). Figure 10-17 New business object Customer Within the business object designer. Use Case 4: Integration of SAP XI with WBI InterChange Server 571 . as shown Figure 10-19 on page 572.back-end system. Figure 10-18 Insert the first row for the business object Customer Chapter 10.

the next task is to specify the mapping from the DominoDocument to Customer business object type (Figure 10-6 on page 562). such as copying a source attribute to a destination attribute. The map designer tool supports simple transformation steps. as is illustrated in Figure 10-20 on page 573. called DominoDocument_Customer.Figure 10-19 Customer business object type in the Business Object Designer Define the map from DominoDocument to Customer Having specified the generic business object. as well as the development of customized transformations directly in Java. The latter is applied for the DominoDocument_Customer mapping. since in this case there is only an indirect correspondence between the attributes of the DominoDocument and Customer business objects. This mapping. A map is made up of a series of transformations that define how to calculate the value of each attribute in the destination business object. which offers a graphical development tool for creating and modifying maps. is defined using the Map Designer tool. 572 WebSphere Business Integration for SAP .

. Each DominoItem business object represents a field within a Contact document of the Domino database Customer Contacts.. DominoItem[n] Name = FirstName Type = String Values = . The attribute Name of the DominoItem business object contains the name of the field it is representing.. Each DominoItem contains a child business object DominoItemValue that holds the field value within its attribute value. The details of this algorithm are specified in pseudo-code in Example 10-1 on page 574. the overall business object DominoDocument contains an array of DominoItem business objects.... . DominoItemValue[0] Value = Hans . Use Case 4: Integration of SAP XI with WBI InterChange Server 573 .DominoDocument NoteID = 986 DatabaseName = customer. Items = DominoItem[0] . Based on these structures.nsf ServerName = ITSOE .... DominoItem[n+1] Name = LastName Type = String Values = .. the algorithm for performing the DominoDocument_Customer mapping must traverse the DominoDocument business object and check whether a DominoItem describes an attribute in the Customer business object... FirstName = Hans Customer Figure 10-20 Mapping of a DominoDocument to a Customer business object As has been shown in Figure 10-14 on page 569. Chapter 10. LastName = Meier DominoDocument_Customer Mapping DominoItemValue[0] Value = Meier ...

a simple map is created first.Example 10-1 Pseudo code for the DominoDocument_Customer mapping for each DominoItem array element in DominoDocument if (the value of the attribute “name” holds the name of an attribute of the business object “Customer”) then this attribute of the business object “Customer” gets the value of the related “Value” attribute within the child business object “DominoItemValue” assigned. An exception to the processing of the above is exclude ObjectEventId from mapping. Select the source DominoDocument as the source of the map and press Next (Figure 10-22 on page 575). the custom mapping is defined using the map designer tool. 574 WebSphere Business Integration for SAP . Thereby. A window with New Map with the name of the Integration library appears.. which is then refined using Java code and given mapping-classes. because this attribute is used by the WebSphere InterChange Server for its internal processing purposes In the following steps. Figure 10-21 Create a new map 2. Open the map designer tool by selecting Create New Map. 3. accept this name and press Next. 1.. from the context menu of the Maps folder within the CustomerDataRepository_Lib (Figure 10-21).

Use Case 4: Integration of SAP XI with WBI InterChange Server 575 . 5. Figure 10-23 Name the map “DominoDocument_Customer” Chapter 10. Finally. select Customer as the destination business object and press Next.Figure 10-22 Selecting the source of the DominoDocument_Mapping 4. In the next window. and press Finish (see Figure 10-23). select the mapping direction as being Application-Specific to Generic. name the map DominoDocument_Customer (Figure 10-23).

Note: Even though the custom transformation is independent of any attributes of the source and destination business objects. define a Move transformation for the Verb and the ObjectId attributes (Figure 10-24). which is part of the Map Designer Tool. As a result. Within the Diagram tab. blue arrows from the source to the destination with the rule Move are displayed. Define the initial custom transformation by dragging an arbitrary source attribute onto an arbitrary destination attribute. Figure 10-24 Move transformation for the Verb and ObjectId attributes 6. 7. select the source attribute Verb. Having defined the Move transformations. 576 WebSphere Business Integration for SAP . this initial custom transformation has to be specified in order to be able to open the Activity Editor. in which the DominoDocument_Customer map is specified. Use Ctrl-Drag to move the destination attribute Verb within the destination Customer. The implementation of this algorithm is an example of a custom transformation. the mapping for the other attributes must be developed according to the outline in Example 10-1 on page 574. which contains the Java code to transform the source attributes to the destination attributes. As a first step. a custom rule is displayed behind the source attribute (Figure 10-25 on page 577). Repeat this step for source attribute NoteId and destination attribute ObjectId.The map designer tool appears. and using the Java classes that are part of the WebSphere InterChange Server Mapping API. The Java code is entered using the Activity Editor. As a result.

as shown in Figure 10-26. because otherwise it would not be active. Figure 10-26 Execution order of the transformation steps Save the map by issuing File → Save → To Project and press Yes when prompted to compile the map. This opens the Activity Editor in its Java view. In Map Designer Tool again. because otherwise the custom transformation would overwrite any other transformation. Use Case 4: Integration of SAP XI with WBI InterChange Server 577 . In this view. This code implements the algorithm sketched in Example 10-1 on page 574 in that it uses the WebSphere InterChange Server MAP API to access the attributes of the different source and sink business objects.Figure 10-25 Define the initial custom map Right-click on the Custom symbol within the Rule column and select View Source. Define the execution order of the transformation here. This is important. displaying the Java source code that the map designer generated for the transformation just specified. switch to the Table tab. switch to the edit mode by selecting Tools → Edit Code and replace everything in there with the Java snippet shown in Example 10-2 on page 578. Save the code and close the Activity Editor. Chapter 10.

getBusObjArray("Items"). myDominoItemValue.set(myName.getString("Name"). i++) { // work on each DominoItem business object myDominoItem = myDominoItemArray. Right-click Connectors and select Create New Connector . i < myDominoItemArray. 2...elementAt(i). 1. 578 WebSphere Business Integration for SAP .elementAt(0).getString("Value")). if (myDominoItemArray != null) { for (int i = 0.Example 10-2 Java code for the DominoDocument_Customer mapping { BusObj myDominoItem = null. // Get the items array from the DominoDocument object BusObjArray myDominoItemArray = ObjDominoDocument. if (myDominoItemValueArray != null) { // set the value to the attribute found within destination business object BusObj myDominoItemValue = myDominoItemValueArray.compareTo("ObjectEventId")!=0)) { // destination business object contains an attribute that matches // the entry within the DominoItem BusObjArray myDominoItemValueArray = myDominoItem. (Figure 10-27 on page 579). } } } } } } Create the configuration for the Lotus Domino connector Installation of the adapter for Lotus Domino provides a connector configuration template that is adjusted to the requirements of the implementation of the CustomerDataRepository Use Case. ObjCustomer. Start configuring the connector by expanding the library CustomerDataRepository_Lib in the left panel of the system manager and navigating to the Connectors folder.getBusObjArray("Values"). if ((ObjCustomer.exists(myName)) && (myName.size(). if (myDominoItem != null) { // check if value of attribute "Name" describes // an attribute within ObjCustomer String myName = myDominoItem.

press File → Open → From File . and click Open.. Chapter 10. within the Connector Configurator. A pop-up window appears..txt. which contains the connector configuration template. prompting for a New Connector Name. Ignore that window by pressing the Cancel button. The standard configuration properties appear within the Connector Configurator window (Figure 10-28 on page 580).Figure 10-27 Create connector configuration 3. 4. browse to the file C:\WICS\repository\Domino\BIACN_Domino. Leave all property values as provided.. except for changing the values of properties AgentTraceLevel and ControllerTraceLevel to 5 for testing purposes. Use Case 4: Integration of SAP XI with WBI InterChange Server 579 . Then.

Leave all the other properties as provided. enter the node name of the Domino server (here ITSOE). and provide the user name and the password the adapter uses for accessing the Domino server. For the property DominoServerName. Switch to the Connector specific Properties tab (Figure 10-29 on page 581).Figure 10-28 Standard properties of the connector for Lotus Domino 5. 580 WebSphere Business Integration for SAP . Note that the password is shown in clear text.

the maps to be applied on given business objects are defined. Figure 10-31 Associated Maps properties Chapter 10. Use Case 4: Integration of SAP XI with WBI InterChange Server 581 . Select Agent Support for the DominoDocument entry. Switch to the Supported Business Objects tab and insert Customer and DominoDocument in the column Business Object Name using the drop-down list provided for the fields of this column.Figure 10-29 Connector specific properties 6. since business objects of this type are handled by the connector agent (Figure 10-30). Figure 10-30 Supported Business Objects properties 7. On the Tab Associated Maps. choose the map DominoDocument_Customer from the drop-down list in the field of the column Associated Map right next to the business object DominoDocument and select Explicit Binding (Figure 10-31). In this way.

In the same way. for example. A collaboration can perform various types of Java operations. by selecting File → Save → To File. Finally. switch to the Messaging tab and specify the properties that define the WebSphere MQ manager (Figure 10-32). to complex synchronizations from various data sources. 582 WebSphere Business Integration for SAP . select Properties. only the simple data-piping processing is required.bat Domino ITSOC_WICS -cC:\WICS\repository\sak400\domino\DominoConnector. Example 10-3 DominoConnector start script C:\WICS\connectors\Domino\start_Domino.8.4. in which data get copied from a source to a sink without any filtering or verification.cfg Create a collaboration template Before testing the connector for Lotus Domino (as described in 10. right-click on the entry. Change the entry of the start script within the Program Menu by selecting Start → Programs → IBM WebSphere Business Integration Adapters → Connectors → Lotus Domino Connector. C:\WICS\repository\sak400\Domino\DominoConnector. which contains the business process logic to be applied to the customer business objects within the WebSphere InterChange Server. and ensure that the target field conforms to Example 10-3.cfg. save the configuration to the file. Save the configuration to the project by issuing File → Save → To Project. ranging from simple data piping processing. “Test the configured connector for Lotus Domino” on page 586).3. 10. Figure 10-32 Messaging properties 9. For Use Case CustomerDataRepository.The configuration file is used as a parameter for the start script of the connector agent. you must define a collaboration.

Port: From BO Type: Customer Triggering Events: Customer. From this activity diagram. A collaboration template contains the actual code of a collaboration (Figure 10-33). It consists of: Ports that determine the input and output business object types Scenarios that specify the processing of business objects Triggering events that define which scenarios are started by the arrival of a business object with a certain verb Scenarios might be specified graphically within the WebSphere InterChange Server Process Designer tool using a UML like notation called an activity diagram. Use Case 4: Integration of SAP XI with WBI InterChange Server 583 . Java code is generated.Create Scenario: Main Port: To BO Type: Customer Figure 10-33 Components of a collaboration template Chapter 10.The development of collaborations is divided into the development of a collaboration template and the configuration of a collaboration object.Update Customer.

One of the basic templates is the CollaborationFoundation template that either is installed together with WebSphere InterChange Server or separately. Therefore. a collaboration object can be defined that receives customer business objects from the Domino connector and pipes them to another connector by merely associating the From-Port with the DominoConnector and the To-Port with the other connector. It also supports data-piping as default processing and can be configured to use different business flows by means of property variables. The CollaborationFoundation template is a tool that facilitates the development of various user-defined collaborations. two of which. are actually used in the Use Case implementation. 584 WebSphere Business Integration for SAP .A collaboration object is an instantiation of a template in which the ports get associated with a certain connector. For example. given that a template for the required “data piping” processing is available. Import this file by selecting Import From Repository File from the context menu of the library CustomerDataRepository_Lib (Figure 10-34). The template provides three ports. Figure 10-34 Import from Repository File 2. templates do not have to developed from scratch. Enter the installation directory of the CollaborationFoundation template (Figure 10-35 on page 585). The installation of the CollaborationFoundation provides a repository file for the CollaborationFoundation template in the directory C:\WICS\CollaborationFoundation. Follow the instructions below for installation and configuration of CollaborationFoundation: 1. the To and From port. With WebSphere InterChange Server there are many templates readily available for different business scenarios. but are gained by adjusting an existing one to given requirements.

Double-clicking on the CollaborationFoundation opens it in the Process Designer tool. meaning the arrival of Customer business object with a certain verb. Use Case 4: Integration of SAP XI with WBI InterChange Server 585 . As a result. open the CollaborationFoundation folder and double-click on Definitions. the Template Definition window appears (Figure 10-36). Chapter 10. Delete.Figure 10-35 Enter the installation directory of CollaborationFoundation 3. associate the Verbs Create. Select the port type Customer from the drop-down list in the BO Type column for each port. a warning window appears asking to remove the existing ports. Then compile the generated Java Code by selecting Compile from the File menu and saving the template to the project by selecting File → Save → To Project. Since the template is defined with a default business object Controller. Using this tool. 4. the CollaborationFoundation appears under Category Collaboration Templates. Within the left pane of the Process Designer tool. Apply the changes. Within that window. the Customer business object is assigned to the existing ports. assign the events. Figure 10-36 Associate Customer business object & Collaboration Foundation ports 7. 6. go to the tab Ports and Triggering Events where the associations of the ports to business objects are defined. After clicking No three times. In the same window. and Update with the Main scenario (Figure 10-36). In this case. 5. Do this using the drop-down list in the Verb column. that trigger the execution the Main scenario that is defined in the CollaborationFoundation template.

the port connector can be replaced by the adapter for SAP Exchange Infrastructure without any change to the configuration of the connector for Lotus Domino. Since deployment of the library CustomerDataRepository to the WebSphere InterChange Server and the definition of a collaboration object are prerequisites of this test. This test is conducted using the tool Visual Test Connector (VTC). Taking this approach. Internally. The next paragraph covers the configuration of the PortConnector. these topics are described subsequently. It provides a Graphical User Interface for sending and receiving those business objects that the connector understands to the WebSphere InterChange Server. 586 WebSphere Business Integration for SAP . the VTC is configured with a PortConnector that represents a connector with no underlying code and as such is very well suited for simulation scenarios. which is delivered with IBM WebSphere InterChange Server. a test method for the configured connector for Lotus Domino is described. Note that testing a connector within the VTC tests only the right configuration of a connector.3. The VTC simulates the activities of an arbitrary connector.10. which is directly connected to its Domino server.4 Test the configured connector for Lotus Domino Before proceeding with the configuration of the adapter for SAP Exchange Infrastructure. Visual Test Connector Send "Customer" Receive "Customer" Port Connector InterChange Server Domino Connector Domino Server Figure 10-37 Using the Visual Test Connector In this scenario. Thus. the VTC together with the PortConnector is used as a representative of the SAP Exchange Infrastructure system. it behaves exactly as the connector it simulates. the VTC is used as a driver that receives and sends business objects from a “real” configuration of the Domino connector. The VTC is configured with the configuration profile of the connector to be simulated. A convenient scenario for testing the communication between the connector and its back-end system as well is depicted in Figure 10-37.

It is obtained by copying the configuration of the DominoConnector. name it PortConnector. Figure 10-38 Get PortConnector as a copy of DominoConnector 2. Click on the Standard Properties tab. Figure 10-39 Enter PortConnector as ApplicationName Chapter 10.Configure the PortConnector The configuration of the PortConnector consists of only standard but no connector specific properties. The next steps are performed on the PortConnector copy. and change the property ApplicationName to PortConnector (Figure 10-39). and press Save (Figure 10-38). deleting all its connector specific properties. select File → Save as → To Project. open the Connector Configurator by double-clicking DominoConnector in the CustomerDataRepostory_Lib. Make a copy of the DominoConnector under the name PortConnector. For this purpose. Use Case 4: Integration of SAP XI with WBI InterChange Server 587 . and configuring it to support the Customer business object: 1.

Likewise. highlight the CollaborationFoundation template.. In the Bind Ports window. requires a collaboration object that pipes Customer business objects from the DominoConnector to the PortConnector. enter Domino2PortConnectorCollaboration as the collaboration object name. and select Edit → Delete Row. also bind the DestinationAppRetrieve port. as shown in Figure 10-41 on page 589. 5. Since all ports of a collaboration object must be bound. right-click on it and select Create New Collaboration Objects. 588 WebSphere Business Integration for SAP . Save the configuration to the project by selecting File → Save → To Project. 4. even though it is not used within this scenario. 3.. for example. and delete all rows except for the Customer business object name. C:\WICS\repository\sak400\Domino\PortConnector. In the Create New Collaboration window. Switch to the Connector Specific Properties tab. as well as File → Save → To File. Within the library CustomerDataRepository_Lib. Create this collaboration object from the template CollaborationFoundation by performing the following steps: 1. Define a collaboration object Testing the Domino Connector. as shown in Figure 10-37 on page 586. switch to the Supported Business Objects tab. select all rows.cfg. bind the From port to the DominoConnector and the To port to PortConnector.3. Note that for the communication between the connector agent of the PortConnector and its connector controller. navigate to the Collaboration Objects. Figure 10-40 Create New Collaboration Object 2. and enter the file name. (Figure 10-40). and press Next. a WebSphere MQ queue AP/PORTCONNECTOR/ITSOC_WICS must be configured (see “Prepare WebSphere MQ for the test” on page 589).

queue. Example 10-5 runmqsc for creating the queues runmqsc itsoc. Figure 10-42 Graphical view on Domino2PortConnectorCollaborationObject Prepare WebSphere MQ for the test Before deploying the library to the WebSphere InterChange Server. Define the queues to be created in a file. as specified in Example 10-4. Use Case 4: Integration of SAP XI with WBI InterChange Server 589 .tst DEFINE QLOCAL(AP/DOMINOCONNECTOR/ITSOC_WICS) DEFINE QLOCAL(AP/PORTCONNECTOR/ITSOC_WICS) Then use the file as an input to the runmqsc command. a graphical view on the new collaboration object is shown in the right pane of the system manager displaying the binding just configured (Figure 10-42).Figure 10-41 Bind ports of Domino2PortConnectorCollaboration 4. as in Example 10-5. As a result. Example 10-4 File C:\WICS\repository\sak400\domino\createQueues4Domino.manager < C:\WICS\repository\sak400\domino\createQueues4Domino. Pressing Finish creates the collaboration object. create the WebSphere MQ queues that the connector agents of the PortConnector and the DominoConnector use for the communication with their respective connector controllers.tst Chapter 10.

Ensure that the WebSphere InterChange Server is started. navigate to the InterChange Server Component Management pane within the system manager and call Register Server from the context menu of the folder InterChange Server Instances (Figure 10-43). 590 WebSphere Business Integration for SAP . new server windows specify the ICS instance. right-click. If not.Deploy the CustomerDataRepository Project on ICS Having defined all the components within the library CustomerDataRepository_Lib. using the default user ID and password. Before starting the deployment. Figure 10-44 Specify the ICS instance to the system manager 4. 2. connector configurations. If it is not. 1. as shown in Figure 10-44. the business objects. and select Connect (Figure 10-45 on page 591). Within the Register. start the PersistentNameServer first and then start the InterChange Server. and collaboration objects must be deployed on the WebSphere InterChange Server in order to be executed there. Select ITSOC_WICS from folder InterChange Server instances. maps. Ensure that the WebSphere InterChange Server instance ITSOC_WICS is registered with the system manager. connect the WebSphere InterChange Server to the system manager. Figure 10-43 Start registering the ICS to the system manager 3.

. Right-click on the subfolder InterChange Server Projects and select New ICS Project (Figure 10-46). Figure 10-47 Create CustomerDataRepostory_Proj Chapter 10.Figure 10-45 Connect the System Manager to the InterChange Server instance Next. and press the Finish button. Open the folder User Projects within the left pane of the system manager. Use Case 4: Integration of SAP XI with WBI InterChange Server 591 . Figure 10-46 Select New ICS Project 2. Select the library CustomerDataRepository_Lib from which the project imports its components. define a user project as a unit of deployment. which contains links to those components of a library that should be deployed: 1. A pop-up window appears. name the project CustomerDataRepository_Proj (Figure 10-47).

The reason for this is that the components of the user project get deployed in a different order than is required.. In order to fix this problem.Note: It is a good practice to delete an existing deployed project before deploying a new one. select the WebSphere InterChange Server name ITSOC_WICS and the project and press Finish (see Figure 10-49). Figure 10-48 Call Deploy user project 4. If this is done. select Shutdown → Gracefully from the context menu of the instance ITSOC_WICS (Figure 10-50 on page 593). 6. either deploy the components in a successive order or restart the WebSphere InterChange Server. A return message is displayed that the connector was deployed successfully. 592 WebSphere Business Integration for SAP . do not forget to restart the server 3. In the Deploy Wizard window. The message might contain a hint that a collaboration object cannot be activated because its publisher (the connector) is not available. from the context menu of the user project CustomerDataRepository_Proj (Figure 10-48). For the latter. Figure 10-49 Deploy CustomerDataRepository_Proj 5. Start deploying by selecting Deploy user project..

After restart. “The architecture of the adapter for Lotus Domino” on page 561.Figure 10-50 Shutdown ITSOC_WICS gracefully 7.3.1. it is received and displayed within the test connector. Use Case 4: Integration of SAP XI with WBI InterChange Server 593 . connect the System Manager to the WebSphere InterChange Server and check that the collaboration object. Finally. Figure 10-51 Check that components of ITSOC_WICS are activated Execute the actual test scenario The actual test is started with the creation of a document within the Domino database Customer Contacts. the connectors. Chapter 10. and the map are activated (Figure 10-51). the processing starts as described in 10. After saving it to the database.

that it is connected to the System Manager.1. select File → New Profile.. Create a profile for VTC by selecting File → Create/Select Profile. The new profile appears in the Connector Profile window (Figure 10-53). Start the test by checking that the WebSphere InterChange Server is up and running. Figure 10-53 Select profile in VTC 594 WebSphere Business Integration for SAP . A window called New Profile appears. and press OK. 2. Now configure the VTC for the test: 1.. enter the fields as in Figure 10-52. Figure 10-52 Create new profile for VTC 3. Start the DominoConnector agent with Start → Programs → IBM WebSphere Business Integration Adapters → Connectors → Lotus Domino Connector. and all its components have been started 2. Start the VTC by selecting Start → Programs → IBM WebSphere InterChange Server → IBM WebSphere InterChange Server Toolset → Development → Test Connector. Highlight it and press OK..

Use Case 4: Integration of SAP XI with WBI InterChange Server 595 . Then. 2. Figure 10-54 Connect the VTC to ICS using the selected profile At this point. all components on the node ITSOC are ready for the test. Chapter 10. The next step is to prepare the Lotus Domino side. Create a new Contact document within the opened database. Not all fields need to be specified (Figure 10-55 on page 596). connect the VTC to the WebSphere InterChange Server using the selected profile by selecting File → Connect (Figure 10-54). 1. Open the Customer Contacts database on node ITSOE using a Lotus Notes client.4.

Figure 10-55 Create “Contact” document in “Customer Contacts” database 3. Figure 10-56 Event in “Event Table” database 596 WebSphere Business Integration for SAP . as depicted in Figure 10-6 on page 562. Check that the event listener has detected the document by looking for a corresponding event within the view EventArchiveView of the Event Table database (Figure 10-56). Saving and closing the document starts the event processing.

Chapter 10.4. Finally. Figure 10-57 Received business object in VTC 5. Double-clicking on the business object within the pane BO Request List opens the business object in its own window and displays the values of its attributes (Figure 10-58). Figure 10-58 Attribute values of received business object Note: The adapter for Lotus Domino generates the verb Update for new as well as changed documents within a Domino database (Figure 10-58). Use Case 4: Integration of SAP XI with WBI InterChange Server 597 . the document is received within the VTC (Figure 10-57).

It then describes the generation of business objects of type DEBMAS01. Note that the configuration of SAP Exchange Infrastructure.1 The architecture of the adapter The adapter for SAP Exchange Infrastructure V1.5. the mapping of Customer business objects to the DEBMAS01 business objects is covered. is described in 10. The test of the adapter for SAP Exchange Infrastructure is postponed to the end of that section. This section starts with a description of the architecture of the adapter for SAP Exchange Infrastructure. which is a back-end system from the WebSphere InterChange Server’s perspective.4 Configure the adapter for SAP XI To complete the implementation of Use Case CustomerDataRepository.4.0 (adapter for SAP XI for short) is configured to exchange XML messages that represent IDocs of type DEBMAS01 with SAP Exchange Infrastructure.10. the adapter for SAP Exchange Infrastructure calls the XML data handler that converts the business object into an XML message. The XML message is determined by the business object type that the adapter is 598 WebSphere Business Integration for SAP . “Configure SAP Exchange Infrastructure” on page 611. Subsequently. Figure 10-59 gives an overview of how requests from the WebSphere InterChange Server to SAP Exchange Infrastructure are processed by the adapter. 10. the definition of the meta-objects for configuring the connector and the connector itself are described. Then.0 allows the WebSphere InterChange Server to asynchronously exchange business objects with SAP Exchange Infrastructure using a WebSphere MQ based JMS implementation. the WebSphere Business Integration adapter for SAP Exchange Infrastructure V1. WBI_XI_Queue SAP XI XML Message WBI Adapter for SAP XI Business Object WBI InterChange Server XML Data Handler Figure 10-59 Request processing of the adapter for SAP XI On receiving a business object that represents a request from the WebSphere InterChange Server.

(Figure 10-15 on page 569). The IDoc structure can be downloaded from an Interface Repository available on the Internet at http://ifr. which is described in 10. Launch the XML object discovery agent (ODA) from the program menu by selecting Start → Programs → IBM WebSphere Business Integration Adapters → Adapters → Object Discovery Agent → XML Object Discovery Agent. Both kinds of processing are metadata driven. meaning that major format conversions and message routing functions are defined by meta-objects. The latter approach. since it ensures that the XML messages generated by the WebSphere InterChange Server are compatible with the IDoc structures that the SAP back-end system uses. 1. Regardless of which of the two approaches is taken.com. 10. in which the adapter receives XML messages from SAP Exchange Infrastructure and relays them to the WebSphere InterChange Server. a DOS window is opened. These IDocs are defined by SAP or self-defined. Event processing. displaying that the XML Object Discovery Agent is listening on port 57037. the type of its configured business objects is derived from IDocs. Press Cancel when the pop-up window for New Business Object appears. Then select File → New Using ODA (Figure 10-60 on page 600). navigate to the folder Business Objects. Business object types can be generated from a XML schema using the WebSphere InterChange Server tool XML Object Discovery Agent (ODA).associated with.. is recommended.2 Generate Business Object Definitions A WebSphere Business Integration adapter is configured to transport business objects of a defined type. Chapter 10. 3. works similar to the request processing described before.5. and select Create New Business Objects.sap. 2. the result is a XML schema representing the IDoc structure. Use Case 4: Integration of SAP XI with WBI InterChange Server 599 . In the case of the adapter for SAP Exchange Infrastructure. or imported from the repository of the SAP Exchange Infrastructure system that is used for the implementation of this Use Case..8. There the JMS layer makes the appropriate calls to open a queue session and routes the message.4. “Import the XML schema for DEBMAS01” on page 639. Open the library CustomDataRepository_Lib in system manager. The Business Object Designer opens. This XML message is put into a WebSphere MQ queue. As a result.xsd and shows how to use the XML Object Discovery Agent for generating the business object type from this file. This section assumes that an XML schema for DEBMAS01 is available in the file debmas01.

Figure 10-61 Select XML ODA Agent 5. After pressing Next. The Business Object Wizard appears with the located agent displayed (if not.Figure 10-60 Issuing New Using ODA within the Business Object Designer 4. a window appears showing that the essential parameters for generating business objects are configured. then press Find Agents). Within the Value column. which has been imported before (Figure 10-62 on page 601). fill in the FileName property with the fully specified name of the XML schema file. 600 WebSphere Business Integration for SAP . Pressing on the agent fills the agent’s host and port (Figure 10-61).

In the next window. and press OK on the next window. Use Case 4: Integration of SAP XI with WBI InterChange Server 601 . where properties for all business objects selected might be specified. Figure 10-63 Select DEBMAS01 as the source node for ODA generation 7. Figure 10-64 Save generated business object to CustomerDateRepository library Chapter 10. If the generated business objects are saved to the project in step 6.Figure 10-62 Enter the file name of the DEBMAS01 XML schema file 6. select the XML top level object DEBMAS01 as the source node from which the Object Discovery Agent generates business object definitions (Figure 10-63). it fails to validate the utmost business object definition for DEBMAS01 because it misses at least one key attribute. Confirm this selection on the next page. Click on the option to open the new business objects in a separate window (Figure 10-64).

Since the adapter for SAP Exchange Infrastructure sends XML messages generated from DEBMAS01 business objects. Figure 10-65 Select ROOT attribute as key for business object DEBMAS01 10. are used (Figure 10-66 on page 603). Click on the ROOT attribute as a key attribute and save it to the library by selecting File → Save. which copies a source attribute to the destination attribute. only the standard attribute transformations Move. As the result. which pipes Customer business objects from one connector the other (Figure 10-2 on page 557). the map Customer_Debmas01 is defined. The DEBMAS01 business object is shown in the Business Object Designer. its respective connector controller must map a generic Customer business object to an application specific DEBMAS01 business object For this purpose. the hierarchical business object type DEBMAS01 with several child business objects definitions are generated (Figure 10-65).4. 602 WebSphere Business Integration for SAP . for assigning constant values. Therefore.8.3 Define the map Customer_Debmas01 The adapter for SAP Exchange Infrastructure is connected to the adapter for Lotus Domino using a collaboration object of template CollaborationFoundation. and Set value.

The corresponding segment is defined to contain master customer master contact person data. describe various kinds of customer data. as indicated within the Comment column in Figure 10-66. Select Customer as the source business object on the next page and press Next. 3. Select CustomerDataRepository_Lib as the project. called segments. from the context menu of the Maps folder within the library CustomerDataRepository_Lib (Figure 10-21 on page 574). Figure 10-66 Definition of map Customer_Debmas01 Perform the following steps for defining the map: 1.The sinks of the mapping are determined by the structure of the hierarchical IDoc type DEBMAS01 as defined by SAP. and press Next. As shown in Figure 10-65 on page 602. 2. For the implementation described within this chapter. Select Create New Map. The different components of a DEBMAS01 type. Source attributes that describe the customer contact itself are mapped to attributes within child business object E1KNVKM.. Use Case 4: Integration of SAP XI with WBI InterChange Server 603 .. it has been chosen to map source attributes to different child business object types. the XML Object Discovery Agent generates child business object types for each segment. Source attributes that describe more common company information are mapped to attributes within child business object E1KNA1M. The corresponding segment is meant to contain master customer basic data. The Create New Map wizard opens. Chapter 10.

These additional configuration properties are specified in a format that conforms to a business object structure. Enter the name Customer_Debmas01 for the map and select Generic to Application Specific as the mapping direction. the format is XML. Since these business objects contain data that describe how to handle other business objects. 5. from the context menu of the Business Objects folder within the CustomerDataRepository_Lib (Figure 10-15 on page 569). Figure 10-67 Name map Customer_Debmas01 and select Mapping Direction 10.. it might be necessary to support different message formats (most of the time. 1. the connector for SAP Exchange Infrastructure is supposed to handle business objects of various types.4 Configure the configuration meta-object In contrast to the Domino connector that processes business objects of just one type. And for both directions. For event processing. 604 WebSphere Business Integration for SAP . Press Finish. this means that the adapter must be able to map different message types from SAP Exchange Infrastructure to different business object types of the WebSphere InterChange Server. but you should not be limited to it). The Map Designer window opens (Figure 10-67). select Create New Business Objects.. the adapter must be able to allocate messages derived from various business objects to various queues. Define the map there as shown in Figure 10-66 on page 603 and save the map.4. 6. they are also called meta-objects. For request processing. Select Debmas01 as the destination business object on the next page and press Next.4. To create a configuration for a meta-object for the adapter.

For the new row. set the column values as defined in the new row with the entries shown in Figure 10-70.2. Fill in the name MO_SAPXIConnector for the new meta-object and press the OK button (Figure 10-68). Figure 10-70 Define values for MO_SAPXIConnector Chapter 10. Figure 10-68 Name the meta-object MO_SAPXIConnector 3. which the adapter uses to send XML messages to SAP Exchange Infrastructure. Figure 10-69 Insert new row in MO_SAPXIConnector 4. The Business Object Designer window opens with a new business object definition. Right-click on the first row of the business object definition and select Insert above (Figure 10-69). The New Business Object window opens. The entries specify the queues. Use Case 4: Integration of SAP XI with WBI InterChange Server 605 .

.txt. in this case). 3... since in this implementation no prefix is used for the generated business objects.5 Configure the XML data handler meta-object The XML data handler is a data conversion module whose primary role is to convert business objects to and from XML documents (Figure 10-59 on page 598). 606 WebSphere Business Integration for SAP . Open the library CustomerDataRepository_Lib within the system manager and select Create New Business Object. The attribute NameHandlerClass defines the class name of the name handler. and open it. configuring meta-objects provide much more functionality.. The meta-object contains two important entries: The attribute ClassName specifies the data-handler class to use with the specified MIME type (text_xml. Within the Business Object Designer. in particular for event processing.4. Leave all other values as provided by the template. select File → Open From File.Note: Since the implementation described here only consists of request processing of one business object type. browse to the file C:\WICS\DataHandlers\repository\DataHandlers\MO_DataHandler_XML. from the context menu of the folder Business Objects (Figure 10-15 on page 569). which is responsible for extracting the name of a business object from the root element of an XML message during event processing of the adapter. Set the attribute BOPrefix to blank. However. The hierarchical meta-object MO_DataHandler_Default with references to a child-object MO_DataHandler_DefaultXMLConfig appears within the Business Object Designer (Figure 10-71 on page 607). 2. Its usage from within the connector for SAP Exchange Infrastructure is configured by means of data handler meta-objects. the contents of the meta-object MO_SAPXIConnector can be kept simple.. The installation of the XML data handler delivers a template from which the meta-object can be created: 1. 10.

browse to the file C:\WICS\repository\SAPXI\BIA_CN_SAPXI.Figure 10-71 Definition of XML data-handler meta-object 10.4.6 Configure the connector for SAP XI Having specified the map and all the business objects. except for those values shown in Table 10-6. As before. The template opens in the Connector Configurator. 3. The installation of this connector yields a template for the connector configuration from which to start the configuration: 1. Within the library CustomerDataRepository_Lib.. in the context menu (Figure 10-27 on page 579). the next step is to create the configuration for the connector for SAP Exchange Infrastructure. Use Case 4: Integration of SAP XI with WBI InterChange Server 607 .. press Cancel on the pop-up window New Connector.txt Chapter 10. They are identical to the standard properties of the DominoConnector. 2. Leave the Standard Properties as given within the template. Table 10-6 Standard properties for the connector for SAP XI Property ApplicationName MessageFileName Values SAPXIConnector BIA_SAPXIAdapter. position the cursor on Connectors node and choose Create New Connector. and press Open. select File → Open → From File.txt. Within the Connector Configurator window.

Select the tab Connector Specific Properties and modify the entries as shown in Figure 10-72. 6. The meaning and creation of the queues are explained in Example 10-6 on page 610. Select the tab Supported Business Objects and specify the meta-objects as well as the application specific and generic business objects that the connector works on (Figure 10-73 on page 609).manager/SAPXICONNECTOR/XI_WBI_QUEUE.4.queue. Specify all queues as Uniform Resource Identifier (URI) with the syntax queue://itsoc_wics. 608 WebSphere Business Integration for SAP . Figure 10-72 Connector specific properties of the SAPXIConnector 5. Also ensure that you put in the name of the configuration meta-object MO_XIConnector as a value of the property ConfigurationMetaObject and the value MO_DataHandler_Default for the property DataHandlerConfigMO. The main configurations pertain to the specification of the queues that the connector for SAP Exchange Infrastructure works on.

cfg. After you are finished with the configuration. C:\WICS\repository\sak400\SAPXI\SAPXIConnector.Figure 10-73 Supported business objects for the SAPXIConnector 7. as. 9. This configuration file is needed later on for starting the connector. Chapter 10. since the mapping. save the connector configuration to the project CustomerDataRepository_Lib as SAPXIConnector and also save it to a file location. Use Case 4: Integration of SAP XI with WBI InterChange Server 609 . Finally. change the values within the Messaging tab according to the ones displayed in Figure 10-32 on page 582. is performed by the connector controller. Note that the connector agent does not support the generic business object Customer. which is selected using the tab Associated Maps (Figure 10-74). for example. Figure 10-74 Specify “Customer_Debmas01” as associated maps 8.

Define the queues to be created in a file as specified in Example 10-6. WBI_XI_Queue WBI Adapter for SAP XI SAP XI XI_WBI_Queue Figure 10-75 Shared queues between SAP XI and WBI Adapter for SAP XI The WebSphere Business Integration Adapter for SAP Exchange Infrastructure supports additional administration queues. Their specification here is only given for the sake of completeness. the adapter shares.4.7 Create WebSphere MQ queues As shown in Figure 10-75. Example 10-7 on page 611 gives an overview of these queues. Example 10-6 File:\WICS\repository\sak400\SAPXI\createQueues4SAPXI. with SAP Exchange Infrastructure.tst ********************************************************************/ * SAPXIConnector/XI_WBI_Queue: For reading messages from SAP XI * SAPXIConnector/WBI_XI_Queue: For writing messages to SAP XI * SAPXIConnector/ArchiveQueue: For archiving messages that have been processed * SAPXIConnector/ReplyQueue: For handling reply messages * SAPXIConnector/InProgressQueue: For messages during their processing * SAPXIConnector/ErrorQueue: For messages that could not be processed * SAPXIConnector/UnsubscribedQueue: For messages that are not subscribed * AP/SAPXICONNECTOR/ITSOC_WICS: For delivery between XI connector and ICS ********************************************************************/ DEFINE DEFINE DEFINE DEFINE DEFINE DEFINE DEFINE QLOCAL(SAPXIConnector/XI_WBI_Queue) QLOCAL(SAPXIConnector/WBI_XI_Queue) QLOCAL(SAPXIConnector/ArchiveQueue) QLOCAL(SAPXIConnector/ReplyQueue) QLOCAL(SAPXIConnector/InProgressQueue) QLOCAL(SAPXIConnector/ErrorQueue) QLOCAL(SAPXIConnector/UnsubscribedQueue) 610 WebSphere Business Integration for SAP . if needed. Note that all the queues whose names start with SAPXIConnector are optional for the implementation of this scenario.10. in which application dependent processing events are kept. the queue WBI_XI_Queue for request processing and. the queue XI_WBI_Queue for event processing in which the adapters receives XML messages from SAP Exchange Infrastructure.

manager < C:\WICS\repository\sak400\SAPXI\createQueues4SAPXI. configured SAP Exchange Infrastructure system is up and running node itso_xi. From the perspective of SAP Exchange Infrastructure. WebSphere Interchange Server is the source back-end system from which it receives XML messages using JMS.queue. Chapter 10. It is assumed that a completely installed and. Use Case 4: Integration of SAP XI with WBI InterChange Server 611 .DEFINE QLOCAL(AP/SAPXICONNECTOR/ITSOC_WICS) Then use the file as an input to the runmqsc command. as in Example 10-7. Then the description of the configuration itself follows. This section ends with showing how to test the configured SAP Exchange Infrastructure together with the WebSphere Business Integration adapter for SAP Exchange Infrastructure. “Overview of SAP XI configuration” on page 612 starts with an overview of the general components to be configured for SAP Exchange Infrastructure. R/3 is the destination back-end system where IDocs generated from the XML messages are submitted using the SAP Exchange Infrastructure IDoc adapter (Figure 10-76).1. Example 10-7 runmqsc for creating the queues runmqsc itsoc. WBI InterChange Server JMS Adapter SAP XI IDoc Adapter R/3 Backend Figure 10-76 Overview: SAP XI processing for CustomerDataRepository 10. for general processing.5 Configure SAP Exchange Infrastructure This section describes the required configuration steps for the SAP Exchange Infrastructure (SAP XI) for the implementation of Use Case CustomerDataRepository.5. The following part of this section covers the preparation of the R/3 back-end system.tst 10.

The entities to be configured there are summarized in Figure 10-78 on page 613.5. Design Integration Repository Configuration Integration Directory Runtime Integration Server System Landscape Directory Figure 10-77 General components of SAP XI The operational model shown in Figure 10-4 on page 558 assumes that these components run within a SAP Web Application Server V6.1 Overview of SAP XI configuration Look at Figure 10-77 to get an overview of the major components of SAP Exchange Infrastructure: The Integration Repository provides the environment for the development of integration scenarios. All systems involved in a integration application are registered in the System Landscape Directory (SLD). including business processes and mappings of interfaces. the different objects of an integration scenario are configured. hosting the integration engine. The Integration Server is the central run-time component. and the central adapter engine that is used to connect external systems. processing.10. By use of the Integration Directory. 612 WebSphere Business Integration for SAP . which is responsible for receiving. The main configuration task for Use Case CustomerDataRepository is done using the Integration Directory and the System Landscape Directory.40 for ABAP and J2EE systems on node itso_xi. and forwarding messages.

Note: This is for simplicity reasons. Use Case 4: Integration of SAP XI with WBI InterChange Server 613 . no further mapping processing needs to be done within SAP Exchange Infrastructure. Chapter 10. it is recommended to build the integration scenario in the repository first. SAP R/3 and WebSphere Interchange Server) are registered within the System Landscape Directory and configured as business systems within the Integration Directory. but not for specifying the integration scenario.Business System Sender Outbound Interface Communication Channel (Sender Adapter) Sender Agreement Receiver Determination Integration Server Interface Determination Communication Channel (Receiver Adapter) Receiver Agreement Inbound Interface Business System Receiver Figure 10-78 Entities to be configured within the Integration Directory Since the WebSphere InterChange Server is responsible for generating XML messages. A business system as a receiver gets messages from an inbound interface from SAP Exchange Infrastructure. In a real integration project. A business system that is a sender submits messages over an outbound interface to SAP Exchange Infrastructure. This is the reason why the Integration Repository is only required for importing the IDoc type DEBMAS01 to the WebSphere InterChange Server. which are compatible with the IDoc-XML-format. The two back-end systems (from the perspective of SAP Exchange Infrastructure.

Register these two entities within the System Landscape Directory (SLD) before configuring them as business systems in SAP Exchange Infrastructure. Finally. 2. The administration of the SLD as well as of the Integration Directory is done using a Web front end. The next paragraphs describe how to configure the entities named in Table 10-7 for the implementation of Use Case CustomerDataRepository. The interface determination specifies a sender and a receiver whose inbound interface is to be used at the receiving side. MasterDataEntrySystem represents the WebSphere InterChange Server and EnterpriseCore the SAP R/3 where the customer data get stored. Table 10-7 Named entities within the SAP XI configuration SAP XI Entity Business system sender Business system receiver Communication channel sender Communication channel receiver Inbound interface Outbound interface Names MasterDataEntrySystem EnterpriseCore JMS2XI IDOC2IDS DEBMAS.5. A communication channel has either a sender or receiver direction. The sender agreement specifies the protocol conversions that must be done on a message so that it can be processed by the Integration Server. the receiver agreement determines the protocol conversions that must be done on a message that flows between the Integration Server and the receiver.2 Register back-end systems in System Landscape Directory Within Table 10-7. 4. 3. Start administration of these services from the home 614 WebSphere Business Integration for SAP . The receiver determination defines one or more receivers for a given sender. On its way from a sender to a receiver.Communication channels define the possible physical bindings for the communication of the Integration Server with the business systems or other services.DEBMAS01 DEBMASJMS 10. a message traverses different processing steps that are defined by the configuration objects listed below: 1. Routing conditions can be specified that determine the receiver based on the message content.

page of the SAP Exchange Infrastructure tools. Figure 10-79 SAP Exchange Infrastructure Tools 1. (Figure 10-81 on page 616). such as XIDIRUSER. Use Case 4: Integration of SAP XI with WBI InterChange Server 615 . The home page of the SLD appears.. Figure 10-80 Links for configuring Technical and Business Landscape in SLD 3. The page Technical System Browser is displayed. Click on the System Landscape Directory and log in with a service user that has appropriate privileges. Select Web AS ABAP as the Technical System Type and press the button New Technical System. 2. which is found at http://itso_xi:51100/rep/start/index.jsp (Figure 10-79). select the link Technical Landscape (Figure 10-80) to register the two back-end systems as technical systems to the SLD. Within this page. Chapter 10..

this has no direct impact. as shown in Figure 10-82.Figure 10-81 New technical system type Web AS ABAP 4. register. For the implementation of this Use Case. so just one component of the ICS like WebSphere MQ is chosen (Figure 10-83 on page 617). This opens the Technical System Wizard. within the Software Catalog of the SLD. at least one software system for this system using the link Software Catalog. Figure 10-82 Technical System Wizard for registering R/3 back end 5. Specify the technical details of the R/3 back end. Before specifying the Technical Landscape for the WebSphere InterChange Server back end. 616 WebSphere Business Integration for SAP . Note that the SLD automatically determines the list of software installed on the R/3 system during this registration.

Figure 10-85 Technical System Wizard for registering InterChange Server 8. Choose Third-Party as the Technical System Type and press the button New Technical System (Figure 10-84). Chapter 10. select the link Business Landscape and press the button New Business System on the next page (Figure 10-86 on page 618). specify values for the fields System Name and Host Name (Figure 10-85).Figure 10-83 Register Software in SLD 6. Create the technical landscape for the WebSphere InterChange Server. Use Case 4: Integration of SAP XI with WBI InterChange Server 617 . Within the Technical System Wizard. Starting on the home page of SLD again. and press Finish. select WebSphere MQ from the list of available products on the next page. Figure 10-84 New technical system of type Third-Party 7.

“Configure the SAP R/3 back-end system” on page 631).Figure 10-86 New Business System 9. Figure 10-87 Definition of business system EnterpriseCore in SLD 10. Note that in principle it is possible that R/3 systems can also register automatically at the SLD.5. register the business system MasterDataEntrySystem in SLD. register the business system EnterpriseCore with the definitions shown in Figure 10-87. Note that the logical system name IBMMQ001 is required for configuring the SAP R/3 back-end system (see 10.In the same way. 618 WebSphere Business Integration for SAP . as depicted in Figure 10-88 on page 619.5. Take the values for the entries Client and Logical System Name from the corresponding specifications of the SAP R/3 back-end system. Using the Business System Wizard.

all the entities in SAP Exchange Infrastructure that are relevant to the implementation of Use Case CustomerDataRepository (Figure 10-79 on page 615) need to be configured. and log in using a user with configuration rights. this is done using the Integration Directory only.3 Configure SAP XI using the Integration Directory After completing the registration within the SLD. Start the Integration Directory Call the home page of the SAP Exchange Infrastructure tools (Figure 10-79 on page 615). select the link Integration Directory. Create business systems under a scenario In this application. 1.5. like XIDIRUSER. As described in Figure 10-78 on page 613.Figure 10-88 Definition of business system MasterDataEntrySystem in SLD 10. all configuration objects that are related to the implementation of the Use Case are subsumed under one scenario: CustomerDataRepository. Fill in the name within the Create Object window and save the configuration (Figure 10-89 on page 620). switch to the Scenarios tab and select Object → New from the menu. Chapter 10. Use Case 4: Integration of SAP XI with WBI InterChange Server 619 . To create the scenario. This opens the application Configuration: Integration Builder.

Figure 10-89 Create scenario CustomerDataRepository 2. 620 WebSphere Business Integration for SAP . Repeat this step for MasterDataEntrySystem. disable the button Create Communication channels automatically. Note that the category Service Without Party is dedicated to those business systems that are part of an intercompany or application-to-application (A2A) scenario. 4. Start specifying the business systems EnterpriseCore and MasterDataEntrySystem by opening the context menu of Service Without Party in the scenario CustomerDataRepository and selecting Assign Business System (Figure 10-90). and click Finish (Figure 10-91 on page 621). Figure 10-90 Start assigning Business System to CustomerDataRepository 3. Within the window Assign Business System. Select EnterpriseCore.Select Business System is displayed. click Continue until the task 3.

which represents the JMS based communication from business system MasterDataEntrySystem to SAP Exchange Infrastructure: 1.Figure 10-91 Assign Business System EnterpriseCore Create communication channels Specify the communication channels that connect the business systems to the Integration Server. First. In the same way. Fill in the name JMS2XI of the Communication Channel and press Create. right-click. define the channel JMS2XI. Select Sender as the communication direction and JMS as the adapter type using the help symbol besides the Adapter Type row. a help menu is provided for selecting the transport and message protocol as well as the adapter engine. as shown in Figure 10-93 on page 622. The Create Window pane is displayed. the values for the queue Chapter 10. switch to the Parameters tab and input the values. the configuration window for the JMS2XI communication channel is displayed in the right pane of the Configuration Integration Builder. navigate to Communication Channel below the business system MasterDataEntrySystem. Figure 10-92 Create a new communication channel 2. On the other hand. and select New (Figure 10-92). In this pane. In the navigation pane. As a result. Use Case 4: Integration of SAP XI with WBI InterChange Server 621 . 3.

and must be enumerated explicitly. Figure 10-93 Parameter values for communication channel JMS2XI 4.WBI_XI_Queue are hosted by the queue manager on the WebSphere InterChange Server. Scroll down the configuration pane to JMS2XI and be sure to specify the parameter value Message Payload = JMS Payload within the XI settings (Figure 10-94). Figure 10-94 XI Settings for communication channel JMS2XI 622 WebSphere Business Integration for SAP .

Within the configuration pane. Then define modules for various processing steps of the adapter. which represents the IDoc based communication from the Integration Server to the business system EnterpriseCore. Switch to the Parameters tab there and specify the values shown in Figure 10-97 on page 624. navigate to Communication Channel below the business system EnterpriseCore. For each value in the column Module Key. The interfaces are explained below. specify the interfaces that the processing step is working on (Figure 10-96). create the communication channel IDOC2IDS. switch from the Parameters to the Module pane. Figure 10-96 Module configuration for communication channel JMS2XI In the same way. The configuration window for the communication channel IDOC2IDS is displayed in the right pane. and select New. 2. Chapter 10.5. 1. Then save the configuration. Use Case 4: Integration of SAP XI with WBI InterChange Server 623 . In the navigation pane. Figure 10-95 Modules for the communication channel JMS2XI 6. right-click. fill in the name of the communication channel IDOC2IDS and press Create. In the Create Window pane. as shown in Figure 10-95.

2. Configure sender agreement The sender agreement specifies the processing properties of a message from the business system MasterDataEntrySystem to the Integration Server. right-click. It is actually defined when configuring the Integration Server in 10. In the Create Object window. specify the business system MasterDataEntrySystem as the sender.4. and choose DEBMASJMS as a name 624 WebSphere Business Integration for SAP . Select the Adapter Type by clicking on the input help symbol and choose IDoc from the selection list. Navigate to Sender Agreement within scenario CustomerDataRepository. Make sure that to mark the adapter as Receiver. 1. The value IDS800 of the parameter RFC destination and port specifies a link between the Integration Server and the R/3 back end.Figure 10-97 Parameter values for communication channel IDOC2IDS 3. All the protocol related fields get filled automatically. “Configure the Integration Server” on page 629. and choose New.5. Note: The following steps can be combined. 4. and are described here one-by-one for clarification reasons.

(Figure 10-98).ibm. Chapter 10. Figure 10-98 Sender agreement for sender MasterDataEntrySystem Configure receiver determination For the implementation of Use Case CustomerDataRepository. Use Case 4: Integration of SAP XI with WBI InterChange Server 625 . the receiver determination defines the business system EnterpriseCore as a receiver for the sender MasterDataEntrySystem. Within the Create Object window. 3. specify the sender as done to create the Sender Agreement. Press Create and a window called Edit Sender Agreement appears.com/redbook as its associated namespace. 1.for the outbound interface and http://itso. Navigate to Receiver Determination in the scenario CustomerDataRepository and select New from its context menu (Figure 10-99). where the associated communication channel JMS2XI must be specified. Figure 10-99 Start creating a receiver determination 2.

where you specify the receiver business system EnterpriseCore (Figure 10-94 on page 622). Pressing Create brings up the Edit Interface Determination mode. and namespace fields for the sender.DEBMAS01. specify EnterpriseCore as the receiver. 1. leave all the other fields blank and save the configuration. where the inbound interface DEBMAS. 3. as in Figure 10-101 on page 627.DEBMAS01 and its namespace urn:sap-com:document:sap:idoc:messages for the receiver business system are configured. interface. 2. After pressing Create. Use the input help (Figure 10-101 on page 627). the inbound interface DEBMAS. the Edit Receiver Determination window is displayed. which is used at the business system EnterpriseCore to receive messages from MasterDataEntrySystem. Navigate to the Interface Determination screen in the scenario CustomerDataRepository and select New from its context menu. Within the Create Object window. 626 WebSphere Business Integration for SAP . this time. Figure 10-100 Specification of the receiver determination Configure interface determination In the Interface Determination screen. is started. and.3. fill in the service. Since for the implementation of the Use Case logical routing is not required.

In the Create Object window.Figure 10-101 Edit Interface Determination Configure receiver agreement Complete the configuration within the Integration Directory by specifying the Receiver Agreement object. 1. After creating this object. Chapter 10. Navigate to Receiver Agreement in scenario CustomerDataRepository and choose New from its context menu. specify the receiver communication channel IDOS2IDS and further conditions. which in this case are left empty (Figure 10-102 on page 628). Use Case 4: Integration of SAP XI with WBI InterChange Server 627 .DEBMAS01 with its namespace. specify the MasterDataEntrySystem as the sender and specify EnterpriseCore as the receiver and the inbound interface DEBMAS. 2. 3.

Open the change lists and select the Activate operation from the context menu of Standard Change Lists (Figure 10-103 on page 629). switch to the Change List tab. these are transferred into the run-time cache for execution. While activating the objects in the change list. 628 WebSphere Business Integration for SAP . they do not become active immediately. Within the navigation pane. 2.Figure 10-102 Edit receiver agreement Activate the change lists When configuration objects are saved. but are collected within change lists and have to be activated explicitly: 1.

Use Case 4: Integration of SAP XI with WBI InterChange Server 629 . and select transaction SM59. 2. specify the RFC-Destination from the SAP Exchange Infrastructure Integration Server to the SAP R/3 back-end system.5. Create RFC destination 1. Open the folder RFC Destinations. Given that an SAP R/3 with System ID IDS and client 800 is accessed. and press the Create button. Call the SAP front end. 3.Figure 10-103 Activate the Change List 10.4 Configure the Integration Server The administration of the Integration Server is done using the SAP front end for the SAP Web Application Server. Within that interface. log in to the Integration Server using a service user with appropriate privileges. specify the RFC Destination by giving values for the target SAP R/3 back-end system. Chapter 10. and load the metadata that the Integration Server uses for converting messages received in IDoc XML to the native IDoc format. such as those depicted in Figure 10-104 on page 630. Note that the RFC destination IDS800 is referenced by the specification of the communication channel IDOC2IDS (Figure 10-97 on page 624). click on R/3 connections. a corresponding port.

Load metadata for IDoc DEBMAS01 by selecting the transaction IDX2. and save the data. 2. 630 WebSphere Business Integration for SAP . Figure 10-105 Create port for IDoc adapter 3. Switch to the Special Options tab and ensure that the Unicode flag is set according to whether the destination SAP R/3 system supports Unicode or not. Within SAP. Switch to the Logon/Security tab and specify the credentials of the user that the Integration Server uses for logon to the SAP R/3 back-end system 5. select transaction IDX1. and specify the IDoc type DEBMAS01 as well as the Source Port IDS800 (Figure 10-106 on page 631). Choose the Create symbol. press the Create button. specify the port as shown in Figure 10-105.4. Figure 10-104 RFC destination IDS800 Create a port and load metadata 1.

1.5 Configure the SAP R/3 back-end system For the implementation of Use Case CustomerDataRepository. Define the target host where the Integration Server resides.5. Using transaction BD54.Figure 10-106 Load metadata for IDoc type DEBMAS01 10. 2. make sure that the logical name C11CLNT800 for the SAP Exchange Infrastructure Integration Server and IBMMQ001 for the business system MasterDataEntrySystem. are defined to the R/3 back end. the R/3 back-end system must be configured to receive IDocs of type DEBMAS01 from the Integration Server. This section describes the essential steps for the required ALE customization on the SAP R/3 back-end IDS on node siccserv using the SAP GUI. which represents the WebSphere InterChange Server. then switch to the Logon/Security tab and specify the credentials the SAP R/3 system uses for accessing the integration server. Call transaction SM59 and create a RFC destination called C11CLNT800 between the R/3 back end and the SAP Exchange Infrastructure Integration Server (Figure 10-107 on page 632). Chapter 10. Use Case 4: Integration of SAP XI with WBI InterChange Server 631 .

Select the model DEBMASFROMXI and select Environment → Generate Partner Profile. 632 WebSphere Business Integration for SAP . A window titled Generating partner profile appears. Select transaction BD64. Figure 10-108 Create distribution model DEBMASFROMXI 4.Figure 10-107 Specify RFC destination C11CLNT800 3. switch to the Edit mode. as the receiver of IDocs of type DEBMAS (Figure 10-109 on page 633). represented by the logical name T90CLNT090. 5. Select transaction WE20 and ensure that a partner profile of type Logical system with inbound parameter message type DEBMAS is created. Define the SAP Exchange Infrastructure Integration Server. Create a distribution model to specify the flow of DEBMAS01 IDocs from the Integration Server to the SAP R/3 back end. and name the model DEBMASFROMXI (Figure 10-108). 6. and the SAP R/3 back end. press the Create model view button. Leave all entries as provided and push the Execute button. represented by the logical name C11CLNT800 as sender. Select the new model and push the button Add message type.

some MQ specific Java libraries must be added to a SAP Exchange Infrastructure JMS provider library: 1.ibm.jar com. Modify the file server/provider.mq.sda com.jar com.6 Define the JMS provider for the SAP XI JMS adapter For the implementation described in this redbook.ibm. Add to aii_af_jmsproviderlib.sda to contain the entries shown in Table 10-9.mqbind.jar</jar-name> </jars> Chapter 10. 2.ibm.jar</jar-name> <jar-name>connector. Make a copy of the library and open the copy with a ZIP tool. Table 10-9 Modifications within the file server/providerlib <jars> <jar-name>com. This library is in the ZIP format.mq.mqjms.mqjms.mqbind. The Java libraries can be found in the WebSphere MQ installation path C:\WebSphereMQ\Java\lib.sda within the implementation path of SAP Exchange Infrastructure.5. Hence.jar</jar-name> <jar-name>com.Figure 10-109 Add message type to the distribution model 10.ibm.sda the WebSphere MQ Java libraries shown in Table 10-8. Use Case 4: Integration of SAP XI with WBI InterChange Server 633 .jar</jar-name> <jar-name>com. 3. Table 10-8 Adding WebSphere MQ Java libraries aii_af_jmsproviderlib. Search for the library aii_af_jmsproviderlib.jar 4.xml within the library aii_af_jmsproviderlib. WebSphere MQ is used as the JMS provider for the SAP Exchange Infrastructure JMS adapter.jar connector.ibm.ibm.

the adapter for SAP Exchange Infrastructure is used together with the Visual Test Connector (VTC). Figure 10-111 on page 635 shows its “tree view”. In this way. After deploying the updated user project.5. “Configure the adapter for SAP XI” on page 598 are tested as well. and select Create New Collaboration Objects. navigate to the folder Collaboration Objects. Figure 10-110 shows the combined test scenario. Close aii_af_jmsproviderlib. except that in this case the VTC together with the port connector is used as a sender of Customer business objects.4.7 Test configured SAP XI together with WBI adapter for SAP XI One approach for testing the configuration described in this section is to put an XML message. 634 WebSphere Business Integration for SAP .sda and redeploy it using it with the SDM-tool. The test follows the same approach as in 10. the test scenario is ready to be executed: 1. which conforms to a DEBMAS01 IDoc structure. and the DestinationAppRetrievPort to the PortConnector. the collaboration object is created. In the Bind Ports window. bind the From port to the PortConnector. highlight the CollaborationFoundation template and enter PortConnector2SAPXICollaboration as the collaboration object name.4. whose From port is bound to the PortConnector and whose To port is bound to the SAPXIConnector. the configurations described in 10. from its context menu (Figure 10-40 on page 588). As a producer of the XML message. into the queue WBI_XI_Queue and check that it is delivered correctly to the SAP R/3 system. 10. Visual Test Connector Send "Customer" Port Connector InterChange Server WebSphere MQ WBI Adapter for SAP XI SAP XI SAP R/3 Figure 10-110 Test configured SAP XI together with WBI adapter for SAP XI Prepare the test The mere requirement for testing the configured connector is to create a special collaboration object from the template CollaborationFoundation. 2. After pressing the Finish button. Open the library CustomerDataLib within the system manager. Restart SAP Exchange Infrastructure in order to make these changes effective.5. Within the Create New Collaboration window.3.. 3. the To port to the SAPXIConnector. “Test the configured connector for Lotus Domino” on page 586..

Use Case 4: Integration of SAP XI with WBI InterChange Server 635 . press Finish and Yes to all at the prompt to replace the existing entries within the project. update its user project by opening the folder User Projects within the system manager and selecting Update Project . Then prepare and start the connector for SAP Exchange Infrastructure: 1. 7. Delete all the other collaboration objects from the user project.Figure 10-111 Tree view on PortConnector2SAPXICollaboration 4. 6. and the SAP R/3 back-end system are up and running on their respective nodes (Figure 10-4 on page 558). from the context menu of CustomerDataRepository_Proj (Figure 10-112).. Ensure that CustomerDataRepository_Proj contains only the collaboration object just created. right-click on the connector name. Within the Update project window. Figure 10-112 Update user project “CustomerDataRepository_Proj” 5.. Chapter 10. Select Start → Programs → IBM WebSphere Business Integration Adapters → Adapters → Connectors → SAP Exchange Infrastructure Connector. and select Properties. Then ensure that the Target field contains an entry like that in Example 10-8 on page 636. select the library CustomerDataRepository_Lib (Figure 10-47 on page 591). Run the test Set up the test by checking that WebSphere InterChange Server. SAP Exchange Infrastructure. Deploy CustomerDataRepository_Proj as described in “Deploy the CustomerDataRepository Project on ICS” on page 590. Before deploying the collaboration object.

Following the description in “Execute the actual test scenario” on page 593.cfg 2. it checks that the business object is processed properly by the subsequent systems.log in the Log Viewer. Within the VTC. except that Create as the verb and another value for attribute KUNNR. Then send the business object by selecting Request → Send (Figure 10-114). Then search for a button called DEBMAS01 within the column BusObj with the appropriate time stamp.Example 10-8 SAP Exchange Infrastructure Connector settings C:\WICS\connectors\SAPXI\start_SAPXI. Open the file C:\WICS\InterchangeSystem. say A16. Figure 10-114 Send the business object Use the WebSphere Business Integration Log Viewer tool to confirm that the business object is received and processed by the connector for SAP Exchange Infrastructure properly. Give a (arbitrary) name to the new business object. 636 WebSphere Business Integration for SAP . 2. The actual test starts with sending a business object of type Customer from the VTC. 1. After that. start the VTC. are selected. select the profile.bat SAPXI ITSOC_WICS -cC:\WICS\connectors\SAPXI\SAPXIConnector. Initialize the business object with the values shown in Figure 10-58 on page 597. Start the Log Viewer from the program menu by selecting Start → Programs → IBM WebSphere Business Integration Server → IBM WebSphere Business Integration Toolset → Administrative → Log Viewer. and connect the VTC to the InterChange Server. Press Apply after the change and then start the connector for SAP Exchange Infrastructure using the program menu described above. 2. Figure 10-113 Create business object of type Customer within the VTC 3. 1. select Customer as BO type and press the Create button (Figure 10-113).

Pressing on the button displays the result of mapping the Customer to the DEBMAS01 business object (Figure 10-115). 2.log Next. “Configure the Integration Server” on page 629. After that. verify that the business object is processed by SAP Exchange Infrastructure on node itso_xi: 1. Chapter 10. Within the Integration Engine Monitoring double-click on Monitor for Processed XML Messages (see Figure 10-116). select the time interval for monitoring the events and press the Execute button. Use Case 4: Integration of SAP XI with WBI InterChange Server 637 .3. Log on to SAP Exchange Infrastructure using the SAP front end. as described in 10. Verify that the transmitted DEBMAS01 business object is processed successfully.4.5. the processed XML messages are displayed (Figure 10-117 on page 638). Select transaction SXMB_MONI. Figure 10-116 SAP XI Integration Engine Monitoring 3. Figure 10-115 Check the business object DEBMAS01 in InterChangeSystem. Within the next window.

Note that the right pane of that figure displays the values of the Customer business object that are mapped to the segment E1KNA1M. A double-click on that entry reveals the technical details and the data contents of the IDoc received by SAP R/3 (Figure 10-119 on page 639).Figure 10-117 Processed XML Messages within the SAP Integration Server Finally. Log on to the SAP R/3 back end using the SAP front end. the list of processed IDocs is displayed (Figure 10-118). Select transaction WE02. Ensure that the entry within that list. check that an IDoc is received by the SAP R/3 back-end system that corresponds to the original Customer business object. On the window IDoc. 1. 2. 638 WebSphere Business Integration for SAP . contains the status code 53. list select the time interval for checking processed IDocs and press the Execute button. which corresponds to the business object sent before. Selecting the second segment E1KNVKM displays the other part of the business object values. Figure 10-118 List of processed IDocs within 3. As a result.

Figure 10-119 Details of received IDoc within SAP R/3 10. Chapter 10. 2. 3. This opens the application Design: Integration Builder. This component usually contains a demo example provided by a SAP Exchange Infrastructure installation.8 Import the XML schema for DEBMAS01 This section describes how to export an XML schema of IDoc type DEBMAS01 using the SAP Exchange Infrastructure Integration Repository. Use Case 4: Integration of SAP XI with WBI InterChange Server 639 . Ensure that the R/3 back-end system is defined in the System Landscape Directory (Figure 10-82 on page 616). 1. Select the Objects tab in the navigation pane of the Integration Builder and open the software component SAP BASIS. Start the Integration Repository from the SAP Exchange Infrastructure tools home page (Figure 10-79 on page 615) and log on with a SAP Exchange Infrastructure service user like XIDIRUSER.5.

Ensure that it contains the DEBMAS. log on to the respective R/3 back-end system first with an appropriate user. Figure 10-120 Start importing IDoc from the SAP back end 4.DEBMAS01 for import (Figure 10-121). 5. which starts the import. open the IDocs folder and select DEBMAS. Within the navigation pane. Open the change list of component SAP BASIS. In the next screen. Press Finish on the next screen. In the window Import from SAP System IDS. Figure 10-121 Choose DEBMAS01 for import 6. Close that window when it returns with the message Import Successful. switch to the Change Lists tab. 640 WebSphere Business Integration for SAP .DEBMAS01 entry (Figure 10-122 on page 641).Select the IDocs folder in the SAP BASIS component and call Import SAP Objects from its context menu (Figure 10-120). Select Activate from the context menu of the folder Standard Change Lists and press Activate in the next window.

“Test configured SAP XI together with WBI adapter for SAP XI” on page 634.5.7. follow the description for PortConnector2SAPXICollaboration in 10. The tree view of the resulted collaboration object is shown in Figure 10-124 on page 642. from the menu (see Figure 10-123). Use Case 4: Integration of SAP XI with WBI InterChange Server 641 .DEBMAS01.. “Test configured SAP XI together with WBI adapter for SAP XI” on page 634 paves the way for running the overall scenario CustomerDataRepository.Figure 10-122 Change list after importing DEBMAS01 7.. the connector for Lotus Domino must be linked with the connector for SAP Exchange Infrastructure by defining a collaboration object Domino2SAPXICollaboration whose From port is associated with the DominoConnector and whose To port is bound to the SAPXIConnector.5. Double-click on the entry DEBMAS. The only change is to replace the PortConnector in Figure 10-110 on page 634 with the connector for Lotus Domino in order to get the environment for running the overall scenario. Figure 10-123 Export DEBMAS01 as XSD file 10.7. Chapter 10. To define and deploy this collaboration object. As a consequence. Within the navigation pane.6 Run the scenario CustomerDataRepository The test scenario described in 10. switch back to the Objects tab. Save the XML schema of the IDoc type by selecting Tools → Export XSD. The IDoc structure is displayed within the right pane.

It makes extensive use of InterChange Server mapping technology to transform generic Domino Documents. into business objects that are compatible with a given SAP IDoc structure. and the connector for SAP Exchange Infrastructure (see “Run the test” on page 635). received by the WebSphere Business Integration adapter for Lotus Domino.7. Start the scenario by creating a document in the Lotus Domino database called Customer Contacts (Figure 10-55 on page 596). SAP Exchange Infrastructure. WebSphere InterChange Server and SAP Exchange Infrastructure.7 Summary This chapter describes the implementation of a Use Case that integrates the two back-end systems Lotus Domino and SAP R/3 using the two integration brokers. Then start the connector for Lotus Domino (see “Execute the actual test scenario” on page 593).Figure 10-124 Collaboration object Domino2SAPXICollaboration Before running the scenario. check the intermediate steps as shown in Figure 10-56 on page 596 and in the test description in 10. ensure that the major systems Lotus Domino Server. verify that a corresponding IDoc is received within the SAP R/3 back-end system (Figure 10-119 on page 639). “Test configured SAP XI together with WBI adapter for SAP XI” on page 634. in between. Finally. 10. 642 WebSphere Business Integration for SAP . After that.5. WebSphere InterChange Server. The key capability of this implementation is to demonstrate how an integration broker itself can participate as an enterprise information system in an overall business integration scenario. The implementation uses JMS over WebSphere MQ for a broker-to-broker communication. and SAP R/3 are up and running.

Best practices and lessons learned This chapter contains the tips and hints obtained in the design and implementation of the sample Use Cases. 2004.11 Chapter 11. 643 . © Copyright IBM Corp. All rights reserved.

The Event Distribution tables in SAP R/3 are case sensitive. A Class Not Found Exception will be thrown if you leave it in the start_SAP. In SAP V4.com.bat. If the case does not match.11. Use prefixes in the WebSphere MQ queue name to be able to identify to which adapter a respective MQ queue belongs. Instead. Adjustments like SAP Java Connector (JCo) updates have to be made in both environments. 11.jar is the name for older JCo versions. jco.3 Use Case 2 Do not install the Embedded Messaging feature of the WebSphere Business Integration Server Foundation if you plan to use a WebSphere Business Integration Adapter that communicates via JMS with the integration broker.6c. When configuring the Business Workflow in SAP R/3 V4. install a full WebSphere MQ Server as the Messaging provider.jar does not exist and is not required. it is only one table (Event Type Linkages).jar. start_SAP.bat refers to two jar files named jco. but only the reference to sapjco.7 for the ABAP Extension Module. Use exactly the same SAP JCo version for the SAP ODA and the SAP Connector. 644 WebSphere Business Integration for SAP .1 General hints and tips Make sure you have installed the proper SAP Java Connector version.2 Use Case 1 Make sure all necessary WebSphere MQ queues are implemented before starting the WebSphere Business Integration Adapter for mySAP.jar and sapjco. then events do not get picked up by the WebSphere Business Integration Adapter for mySAP. especially the Unsubscribe and Error queues. jco. there are two transactions and tables that must be configured (Instance Linkages and Event Type Linkages). 11.com version.com.jar is required. The SAP Object Discovery Agent (ODA) uses different startup batch files than the SAP Connector for startup and execution environment configuration. Use the latest WebSphere Business Integration Adapter for mySAP.

If you require a transaction.Verify that the RFC server specific business object handlers are located in the \bapi\server folder of the SAP Connector. Refer to Microsoft Knowledge Base Article . If you do not require a transaction. the new business object is returned in place of the original. It is important that you do not choose to have the collaboration template require a transaction when doing a query. In some circumstances.830473 for further details. The default values may not be adequate for your needs.microsoft. Usually.jar are on the system path or on the JCLASSES entry in all of your batch files that start your adapters and WebSphere InterChange Server. Review SAP Connector properties in test and production environments. because this name is used to generate unique class and package names in WSADIE.jar and the db2jcc_license_cu. Be aware that the Visual Test Connector can only simulate a back end to the integration broker and not vice versa. integration scenarios that ran successfully with the test connector have a malfunction when the real back end is connected. then the new business object is discarded and the original gets return.4 Use Case 3 Ensure that the db2jcc. Chapter 11.com/default. Be aware that the Visual Test Connector cannot simulate a back end outright. Use the Universal Test Client within WebSphere Studio Application Developer Integration Edition (WSADIE) to test generated deploy code. The reason behind this is that a retrieve request creates a new business object on the return trip. Use the Visual Test Connector to replace the target back-end system and verify the correct adapter-broker communication.830473 11. this can exceed command-line limitations on Windows platforms when deploying the generated EJBs. Avoid long names for generated business objects. A transaction scope does not allow you to change the business object to return a new one instead. which can be found at: http://support. This can be done on the activity level and on the process level if an EJB binding has been chosen.aspx?scid=kb.en-us. Best practices and lessons learned 645 .

646 WebSphere Business Integration for SAP .5 Use Case 4 Shut down and restart the InterChange Server after each new deployment.11. Ensure that after a restart each deployed component is started. Do not forget to start the PersistentNameServer before starting the InterChange Server. Do a unit test using the Visual Test Connector after each major configuration step. Clear all unprocessed entries within the Lotus Event Table before starting a new test scenario.

647 . © Copyright IBM Corp. All rights reserved. 2004. source. Scripts. and test data This appendix provides scripts and source code that was implemented in the Use Cases.A Appendix A.

Format = MQFMT_RF_HEADER_2. OutputRoot. OutputRoot.com/websphere/crossworlds/2002/BOSchema/sap_idoccontrol'. OutputRoot.com/websphere/crossworlds/2002/BOSchema/sap_matmas03_e2maram005 '.Field)Version = 2.Field)CodedCharSetId = 1208.MQMD = InputRoot. 648 WebSphere Business Integration for SAP .ibm.com/websphere/crossworlds/2002/BOSchema/sap_matmas03_e2maktm001 '.MQMD.MQRFH2.com/websphere/crossworlds/2002/BOSchema/sap_matmas03_e2mvkem002 '.com/websphere/crossworlds/2002/BOSchema/sap_matmas03_cwdata'. DECLARE ns5 NAMESPACE 'http://www.(MQRFH2. OutputRoot.(MQRFH2.ibm.(MQRFH2.Use Case 1 Here we discuss the scripts and source code for Use Case 1.ibm.MQRFH2.MQRFH2. CREATE COMPUTE MODULE MaterialSynchronization_MsgFlow_Compute CREATE FUNCTION Main() RETURNS BOOLEAN BEGIN CALL CopyMessageHeaders().MQMD.MQMD.MQRFH2. ESQL module The ESQL in Example A-1 shows how to build an IDoccontrol section manually and how to copy or transform values of the incoming IDoc.MQMD.ibm. DECLARE ns4 NAMESPACE 'http://www.ibm.Field)Encoding = 273. OutputRoot.Field)Format = MQFMT_STRING. OutputRoot. DECLARE ns6 NAMESPACE 'http://www.ibm.(MQRFH2.com/websphere/crossworlds/2002/BOSchema/sap_matmas03_e2marcm004 '. DECLARE ns3 NAMESPACE 'http://www. OutputRoot.com/websphere/crossworlds/2002/BOSchema/sap_matmas03'.Encoding = 273. SET SET SET SET SET SET SET SET SET OutputRoot. DECLARE ns2 NAMESPACE 'http://www.Field)Flags = 0.(MQRFH2. OutputRoot. DECLARE ns NAMESPACE 'http://www.ibm.CodedCharSetId = 1208.MQRFH2. Example: A-1 ESQL module BROKER SCHEMA MaterialSynchronization_Schema DECLARE ns1 NAMESPACE 'http://www.

and test data 649 .(MQRFH2.very importend Section this must mache with the Adapter config file set OutputRoot.Field)NameValueCCSID = 1208.verb = 'Create'.MessageType = 'sap_matmas03'.ns:Control_record.ns:Control_record. SET OutputRoot.Properties.ns6:sap_idoccontrol.MRM.ns:Control_record.ns6:Name_of_basic_type= 'MATMAS01'.ns6:sap_idoccontrol.ns6:sap_idoccontrol.ns6:Name_of_table_structur e = 'EDI_DC40'. source.MRM.MRM.ns6:Output_mode = '2'.ns:Control_record.ns6:sap_idoccontrol.Properties.messagedomain = 'mrm'.ns:Control_record. SET OutputRoot.ns6:Client = '800'.ns6:Logical_message_type= 'MATMAS'.SET OutputRoot.ns6:Partner_type_of_sender = 'LS'.verb = 'Create'.MRM. SET OutputRoot.ns:Control_record.MRM. SET OutputRoot.Properties. SET OutputRoot.ns:Control_record.MRM. SET OutputRoot.MRM.MRM.MRM. Appendix A.MRM.ns:Control_record.MRM.ns6:sap_idoccontrol.ns:Control_record. SET OutputRoot.MRM. -.ns6:Sender_port = 'WBI'.ns6:sap_idoccontrol.ns6:IDoc_number = '1'. --SET OutputRoot. set OutputRoot.ns:Control_record.ns6:sap_idoccontrol. set OutputRoot. SET OutputRoot.ns6:sap_idoccontrol.MRM. SET OutputRoot.ns6:Partner_number_of_send er = 'WBI'. SET OutputRoot.Properties. SET OutputRoot.Properties.MessageFormat = 'CwXML'.MessageSet = 'PU4HKDS002001'.ns6:SAP_Release_for_IDoc = '620'.MRM = InputRoot.ns:Control_record. Scripts.ns6:Direction_for_IDoc_tra nsmission= '1'.MRM. SET OutputRoot.ns6:sap_idoccontrol. set OutputRoot.Encoding = 273. SET OutputRoot. SET OutputRoot.ns6:sap_idoccontrol.CodedCharSetId = 1208.ns:Control_record.Properties.ns6:sap_idoccontrol.MQRFH2. SET OutputRoot.ns:Control_record. SET OutputRoot.ns6:sap_idoccontrol.null1208:sap_idoccontrol.MRM.ns6:Status_of_IDoc= '30'.

ns6:Partner_number_of_reci pient = 'BS8CLNT030'.ns4:sap_matmas03_e2maktm001.ns6:sap_idoccontrol.ns5:sap_matmas03_cwdata.ns5:sap_matmas03_cwdata.MRM.MRM.ns4:sap_matmas03_e2maram005.ns5:sap_matmas03_e2maram0 05. SET OutputRoot.ns:Data_record.ns3:MAKTX = '10W30 MOTOR OIL CASE'.MRM.ns4:sap_matmas03_e2maktm001.ns6:sap_idoccontrol.ns4:sap_matmas03_e2maram005.ns3:SPRAS_ISO = 'EN'.MRM. 650 WebSphere Business Integration for SAP .ns4:sap_matmas03_e2maktm001. SET OutputRoot.ns3:sap_matmas03_e2m aktm001.ns:Data_record.ns4:sap_matmas03_e2maram005. SET OutputRoot.ns3:sap_matmas03_e2m aktm001.ns6:sap_idoccontrol.ns6:sap_idoccontrol. SET OutputRoot.ns:Data_record. SET OutputRoot.ns4:sap_matmas03_e2maram005.ns:Data_record.ns6:sap_idoccontrol.MRM.ns:Data_record.MRM.MRM. SET OutputRoot.ns6:sap_idoccontrol.ns4:sap_matmas03_e2maktm001.MRM. SET OutputRoot.SET OutputRoot.ns6:sap_idoccontrol.ns5:sap_matmas03_e2maram0 05.ns6:Receiver_port= 'SAPBS8'.MRM.ns4:sap_matmas03_e2maram005.ns6:IDoc_creation_date= ''.ns6:EDI_ALE_Serialization_ field = ''.ns5:sap_matmas03_cwdata. SET OutputRoot. SET OutputRoot.ns4:sap_matmas03_e2maram005.ns5:sap_matmas03_cwdata.verb = 'Create'.ns3:sap_matmas03_e2m aktm001.ns5:sap_matmas03_e2maram0 05.ns5:sap_matmas03_cwdata.ns6:Partner_type_of_recipi ent = 'LS'.ns:Data_record.ns5:sap_matmas03_cwdata.MRM.ns5:sap_matmas03_cwdata.MRM.ns:Control_record.ns6:ObjectEventId = ''.ns:Data_record.ns5:sap_matmas03_e2maram0 05.ns:Control_record.MRM.ns5:sap_matmas03_cwdata. SET OutputRoot.ns:Control_record.ns6:IDoc_creation_time= ''.MRM.ns:Control_record.verb = 'Create'.size = '1'.MRM. SET OutputRoot.ns3:SPRAS = 'E'.size = '1'.MRM.ns:Control_record.ns3:sap_matmas03_e2m aktm001.ns5:sap_matmas03_e2maram0 05. SET OutputRoot.ns4:sap_matmas03_e2maktm001. SET OutputRoot.ns:Control_record.verb = 'Create'.ns:Data_record.ns5:sap_matmas03_e2maram0 05.ns5:sap_matmas03_e2maram0 05.ns:Control_record. SET OutputRoot.

ns4:sap_matmas03_e2maram005.MRM.ns:Data_record.ns5:sap_matmas03_cwdata.MRM. and test data 651 .ns4:NTGEW = '0.ns4:BRGEW = '0.ns:Data_record. SET OutputRoot.ns5:sap_matmas03_cwdata. SET OutputRoot.ns:Data_record.ns5:sap_matmas03_e2maram0 05. SET OutputRoot.MRM.MRM. SET OutputRoot. SET OutputRoot.ns4:sap_matmas03_e2maram005.ns5:sap_matmas03_e2maram0 05.MRM.ns:Data_record.ns4:MEINS = 'CSE'.ns5:sap_matmas03_e2maram0 05.ns:Data_record.ns:Data_record.ns4:sap_matmas03_e2maram005.ns5:sap_matmas03_e2maram0 05.ns5:sap_matmas03_cwdata.ns5:sap_matmas03_cwdata. source.ns:Data_record.ns5:sap_matmas03_e2maram0 05. SET OutputRoot. SET OutputRoot.000'.ns4:sap_matmas03_e2maram005.ns4:sap_matmas03_e2maram005.ns3:sap_matmas03_e2m aktm001.000'.ns:Data_record.ns:Data_record.MRM. SET OutputRoot.ns5:sap_matmas03_cwdata. Scripts.ns5:sap_matmas03_e2maram0 05.ns5:sap_matmas03_cwdata.ns4:sap_matmas03_e2maram005.MRM.ns4:MTART = 'HIBE'.ns5:sap_matmas03_e2maram0 05.ns:Data_record.ns:Data_record.MRM.ns:Data_record.ns3:MSGFN = '005'.ns4:sap_matmas03_e2maram005.ns5:sap_matmas03_e2maram0 05.ns:Data_record.ns4:MATKL = '010' .ns5:sap_matmas03_e2maram0 05.ns5:sap_matmas03_cwdata.ns4:WESCH = '0.ns5:sap_matmas03_e2maram0 05.000'. SET OutputRoot.ns4:MBRSH = 'M' .ns:Data_record.ns5:sap_matmas03_cwdata.MRM.000'.MRM.ns5:sap_matmas03_e2maram0 05.ns4:VOLUM = '0.ns4:sap_matmas03_e2maktm001.ns5:sap_matmas03_cwdata. SET OutputRoot.ns4:PSTAT = 'KCELB'.MRM.ns4:HOEHE = '0. SET OutputRoot.000'. SET OutputRoot. SET OutputRoot.MRM.ns4:BREIT = '0.ns:Data_record.ns5:sap_matmas03_e2maram0 05.000'.ns5:sap_matmas03_e2maram0 05.ns5:sap_matmas03_e2maram0 05.ns4:sap_matmas03_e2maram005.000'. SET OutputRoot.ns4:sap_matmas03_e2maram005.SET OutputRoot.ns4:sap_matmas03_e2maram005.MRM.ns5:sap_matmas03_cwdata.ns5:sap_matmas03_cwdata.ns4:sap_matmas03_e2maram005.ns4:sap_matmas03_e2maram005.ns4:sap_matmas03_e2maram005.ns5:sap_matmas03_cwdata. Appendix A.ns5:sap_matmas03_cwdata.MRM.ns4:AENAM = 'ODABASHIAN' .ns4:BLANZ = '000'.ns5:sap_matmas03_e2maram0 05.ns5:sap_matmas03_cwdata.ns5:sap_matmas03_cwdata.ns4:sap_matmas03_e2maram005.MRM.ns4:LAENG = '0.ns4:sap_matmas03_e2maram005.

END. RETURN TRUE. Example: A-2 Snippet . String material = getInput(). SET OutputRoot. CREATE PROCEDURE CopyMessageHeaders() BEGIN DECLARE I INTEGER 1.MRM.prepare call // get process input values String id = getInput(). int quantity = getInput().ns4:GEWTO = '0. CREATE PROCEDURE CopyEntireMessage() BEGIN SET OutputRoot = InputRoot.*[]).ns5:sap_matmas03_e2maram0 05. END.getPlant(). WHILE I < J DO SET OutputRoot. DECLARE J INTEGER CARDINALITY(InputRoot.0'.getQuantity(). -.0'.ns4:sap_matmas03_e2maram005. String plant = getInput(). Prepare Service call This code snippet (Example A-2) has to be pasted into the user section of the prepareCall activity.ns5:sap_matmas03_e2maram0 05. SET I = I + 1. // adjust date to have the correct format 652 WebSphere Business Integration for SAP .getDeliveryDate().getMaterialNumber().getEmployeeNumber(). END.*[I].ns5:sap_matmas03_cwdata.ns4:VOLTO = '0. END MODULE.MRM. END WHILE.CALL CopyEntireMessage(). String date = getInput().ns:Data_record. Use Case 2 Here we discuss the scripts and source code for Use Case 2.ns5:sap_matmas03_cwdata.ns:Data_record.*[I] = InputRoot.SET OutputRoot.ns4:sap_matmas03_e2maram005.

setMATERIAL(material). order_lineitems[0].setMaterial(material). source. and test data 653 .setDOC_TYPE("NB"). setCheckMaterialRequest(checkApprovalPolicy_RequestMsg).setVerb("Retrieve"). Scripts.setSubtype_SUBTY("0010").10)+date. order_lineitems[0]. // get Request message object from BProcess container and set new value CheckMaterialRequestMessage checkApprovalPolicy_RequestMsg = getCheckMaterialRequest().date = date. Appendix A. order_lineitems[0]. // create a purchase order line item table which holds all line items Sap_bapi_requisition_createElement.we order only one product to keep the example simple order_lineitems[0] = new Sap_requisition_itemsElement().setSap_requisition_items(order_lineitems). order_lineitems[0].setQUANTITY("" + quantity). order_lineitems[0]. order_lineitems[0]. order_lineitems[0]. getHRData_InputElement.Sap_requisition_itemsElementLocal order_lineitemsTable = new Sap_bapi_requisition_createElement. getHRData_InputElement.substring(3.setPersonnel_number_PERNR(id).substring(6.setGR_PR_TIME("0"). order_lineitems[0].substring(0.setDELIV_DATE(date). order_lineitems[0].setPRICE_UNIT("0").Sap_requisition_itemsElementLocal(). getHRData_InputElement.setBodyPart(getHRData_InputElement).2)+date.setMAT_GRP("002"). // push the specific line imtem into line item table order_lineitemsTable. // prepare Input element Sap_bapi_requisition_createElement createPurchaseorder_InputElement = new Sap_bapi_requisition_createElement().5).setPREQ_ITEM("00000"). // get Request message object from BProcess container and set new value Sap_pa0105RequestMessage getHRData_RequestMsg = getSap_pa0105Request(). getHRData_RequestMsg. order_lineitems[0]. // prepare Input element Sap_pa0105Element getHRData_InputElement = new Sap_pa0105Element(). setSap_pa0105Request(getHRData_RequestMsg).setC_AMT_BAPI("0").setPUR_GROUP("001"). // fill the line item . // create an object for each purchase order line item Sap_requisition_itemsElement order_lineitems[] = new Sap_requisition_itemsElement[1]. checkApprovalPolicy_RequestMsg.setPLANT(plant). order_lineitems[0].

Requisition@itso.println("Requested Plant:" + plant).out.getCommunication_ID_Number_USRID() + "@de. // get Request message object from BProcess container and set new value SendJMailRequestMessage notifyRequestor_RequestMsg = getSendJMailRequest(). System. Prepare positive notification This code snippet (Example A-3) has to be pasted in the user section of the preparepositiveNotification activity. recipients[0] =getSap_pa0105Response().println("Requested QTY:" + quantity). String[] recipients = new String[1]. createPurchaseorder_InputElement. System. System. internalOrder_ResponseMsg.setVerb("Retrieve"). String subject = "Purchase Order Requisition " + purchaseOrderNumber + " accepted". String purchaseOrderNumber = getSap_bapi_requisition_createResponse().println("Requested Delivery date:" + date).setAUTOMATIC_SOURCE("X").getReturnBodyPart(). setSap_bapi_requisition_createRequest(createPurchaseOrder_RequestMsg).println("Requested Material:" + material).out.out. createPurchaseorder_InputElement. internalOrder_ResponseMsg. Example: A-3 Snippet . setOutput(internalOrder_ResponseMsg). // debug info System.createPurchaseorder_InputElement.getReturnBodyPart().println("Employee number:" + id).setStatus("Order placed").getMaterialNumber().setUsername(recipients[0]). fill result fields and place it back CreateInternalOrderResponseMessage internalOrder_ResponseMsg = getOutput().com". createPurchaseOrder_RequestMsg. String from = "Order.setSap_requisition_items(order_lineitemsTable) . String message = "Your order of Material "+ material+ " has been processed. For order tracking purpose use process number: "+purchaseOrderNumber.setBodyPart(createPurchaseorder_InputElement). // get Request message object from BProcess container and set new value Sap_bapi_requisition_createRequestMessage createPurchaseOrder_RequestMsg = getSap_bapi_requisition_createRequest().setSKIP_ITEMS_WITH_ERROR(" ").ibm. System.com". createPurchaseorder_InputElement. internalOrder_ResponseMsg. // get Response message.out.setRequisitionNumber(purchaseOrderNumber).out. 654 WebSphere Business Integration for SAP .preparepositiveNotification // initialize local variables String material = getInput().getNUMBER().

Requisition@itso. internalOrder_ResponseMsg.setStatus("Order rejected"). String message ="Your order of Material "+ material+ " has been declined by the functional approver". Example: A-4 Snippet .com".println("eMail message:" + message). // debug info System.println("Positive Notification block.setUsername(recipients[0]). String subject = "Purchase Order Requisition declined".setRecipients(recipients). Prepare negative notification This code snippet (Example A-4) has to be pasted in the user section of the preparenegativeNotification activity.getCommunication_ID_Number_USRID()+ "@de.out."). System.setFrom("Order.getReturnBodyPart(). and test data 655 .ibm. notifyRequestor_RequestMsg. fill result fields and place it back CreateInternalOrderResponseMessage internalOrder_ResponseMsg = getOutput(). String from = "Order. notifyRequestor_RequestMsg.println("eMail sent to:" + recipients[0]).out.setRecipients(recipients).println("Negative Notification block. Scripts. setOutput(internalOrder_ResponseMsg). notifyRequestor_RequestMsg. notifyRequestor_RequestMsg. Appendix A. // debug info System.").setFrom(from). notifyRequestor_RequestMsg. notifyRequestor_RequestMsg.setMessage(message).preparenegativeNotification // initialize local variables String material = getInput(). setSendJMailRequest(notifyRequestor_RequestMsg).com".setRequisitionNumber("N/A"). source. internalOrder_ResponseMsg. String[] recipients = new String[1].out. internalOrder_ResponseMsg.setSubject(subject).Requisition@itso.com").getMaterialNumber().notifyRequestor_RequestMsg. System. notifyRequestor_RequestMsg. setSendJMailRequest(notifyRequestor_RequestMsg). // get Response message. recipients[0] = getSap_pa0105Response(). System.out.println("eMail subject:" + subject).setSubject(subject).setMessage(message). // get Request message object from BProcess container and set new value SendJMailRequestMessage notifyRequestor_RequestMsg =getSendJMailRequest().out.

ENDREPLLEADTIME DATE . STOCKINDICATOR CHARACTER (10) . ITEMNUM. PLANT VARCHAR (4) . '1232'. '1456'. QTYAVAILABLE. UNITOFMEASURE. INSERT INTO DB2ADMIN. UNITOFMEASURE VARCHAR (3) . '2004-05-02') INSERT INTO DB2ADMIN. WBSELEMENT. 'duh'. This sample can be used in the reproduction of the test scenario. 'DPC1018'. 0) . DOCNUM. 'ST'. CHKGRULE. but it would depend upon the SAP system being tested. DOCNUM VARCHAR (10) . '12345'. MATERIAL. "REQ_QTY" DECIMAL(18. CHKGRULE VARCHAR (2) . '2004-05-12') CREATE TABLE "DB2ADMIN". PLANT. 258.println("eMail sent to:" + recipients[0]). CUSTNUM."REC_COM" ( "XREF_KEY" INTEGER NOT NULL . 656 WebSphere Business Integration for SAP . DOCNUM.AVAILABILITY ( XREFKEY INTEGER NOT NULL GENERATED ALWAYS AS IDENTITY (START WITH 1.System. 258. 'ST'. ENDREPLLEADTIME) VALUES ('6'. INDICATOR CHARACTER (1) . '1200'.out. CUSTNUM VARCHAR (10) .AVAILABILITY (BATCH. STORLOC VARCHAR (4) . Example: A-5 DB2 table creation CREATE TABLE DB2ADMIN. STORLOC.out. 'AC'.0) . NO CACHE ) . 'duh'. STORLOC. QTYAVAILABLE DECIMAL (18. 'AC'. Use Case 3 The sample code in Example A-5 was used to create the DB2 database and tables that were used for testing in the SAP RFC -> JDBC scenario. "REQ_DATE" DATE . MATERIAL. WBSELEMENT VARCHAR (24) . PLANT. ITEMNUM. CONSTRAINT CC1084350596672 PRIMARY KEY ( XREFKEY) ) . '1201'. '12345'. 'DPC1017'. ITEMNUM VARCHAR (6) . '1456'. INCREMENT BY 1. BATCH VARCHAR (10) . CHKGRULE. '1201'. WBSELEMENT. System.AVAILABILITY (BATCH.println("eMail subject:" + subject). CUSTNUM. System. UNITOFMEASURE. ENDREPLLEADTIME) VALUES ('5'.out. QTYAVAILABLE.println("eMail message:" + message). '1232'. '1200'. MATERIAL VARCHAR (18) .

"REQ_DATE" DATE .AVAILABILITY (XREFKEY) ON DELETE NO ACTION ON UPDATE NO ACTION IN "USERSPACE1" .AVAILABILITY (XREFKEY) ON DELETE NO ACTION ON UPDATE NO ACTION IN "USERSPACE1" . Appendix A. CREATE TABLE "DB2ADMIN"."CMMTD_DATE" DATE ."WMDVSX" ( "XREF_KEY" INTEGER NOT NULL . CONSTRAINT CC1083935333609 FOREIGN KEY (XREF_KEY) REFERENCES DB2ADMIN. ) . "CMMTD_QTY" DECIMAL(18. "MRP_ELEMENT" CHAR(12) . Scripts. and test data 657 .0) . "LINE_INDEX" INTEGER. CONSTRAINT CC1083933830391 FOREIGN KEY (XREF_KEY) REFERENCES DB2ADMIN. ALTER TABLE "DB2ADMIN". ) .0)."WMDVSX" ADD CONSTRAINT "CC1083935333609" UNIQUE ("XREF_KEY"). "REQ_QTY" DECIMAL(18. source.

658 WebSphere Business Integration for SAP .

Additional material This redbook refers to additional material that can be downloaded from the Internet as described below. 2004. 659 .B Appendix B. Locating the Web material The Web material associated with this redbook is available in softcopy on the Internet from the IBM Redbooks Web server.redbooks. Point your Web browser to: ftp://www.zip Description This ZIP file contains all the files listed below.com/redbooks Select the Additional materials and open the directory that corresponds with the redbook form number.com/redbooks/SG246354 Alternatively. you can go to the IBM Redbooks Web site at: ibm.ibm. SG246354. © Copyright IBM Corp. Using the Web material The additional Web material that accompanies this redbook includes the following files: File name ALL. All rights reserved.

System requirements for downloading the Web material The following system configuration is recommended: Hard disk space Operating System Processor Memory ALL.zip.zip.zip is approximately 1. Base Workspace SAK400. Windows 2000 or Windows XP (Professional or Server). WorkSpaceBackup Final.25 MB. Pentium® III 500M Hz or better.Use Case 1 Use Case 2 Use Case 2 Use Case 2 Use Case 2 Use Case 3 Use Case 1 WBIMB and Adapter files. and unzip the contents of the Web material zip file into this folder. Use Case 2 All files.zip. Use Case 3 DB2 table creation.zip. 256 MB or higher is recommended. How to use the Web material Create a subdirectory (folder) on your workstation.zip. Snippets. 660 WebSphere Business Integration for SAP .zip.

All rights reserved. Enterprise Edition Java 2 Platform. 661 . 2004. Standard Edition Java Connector Architecture Java Connector Java Data Objects Java Messaging Service Java Runtime Environment IBM ICM IDoc(s) ITSO J2EE J2SE JCA JCO JDO JMS JRE © Copyright IBM Corp.Abbreviations and acronyms ABAP ADK ALE API ASBO B2B BAM BAPI BI BIRA BIW BPC BPE BPEL BPEL4WS BPM BSP CAF CMP CRM D2D DMZ Advanced Business Application Programming Adapter Development Kit Application Link Enabling Application Programmable Interface Application Specific Business Objects Business To Business Business Activity Monitoring Business Application Programming Interface SAP Business Intelligence IBM Business Integration Reference Architecture Business Information Warehouse Business Process Choreographer Business Process Execution Business Process Execution Language Business Process Execution Language for Web Services Business Process Management Business Server Pages SAP Composite Application Framework Container-Managed Persistence Customer Relationship Management Division to Division Demilitarized Zone GBO GUI HDR HR HTTP HTTPS EIS EJB ERP ESB FDML EAR EDI Enterprise Archive Electronic Data Interface (EDI) Enterprise Information Systems Enterprise JavaBeans Enterprise Resource Planning Enterprise Service Bus Flow Definition Markup Language Generic Business Objects Graphical User Interface Hierarchical Dynamic Retrieve Human Resources Hypertext Transfer Protocol Extension of HTTP runnning under the Secure Socket Layer (SSL) International Business Machines Corporation Internet Communication Manager Intermediate Document(s) International Technical Support Organization Java 2 Platform.

JSP KM LOB MDAC MDM MI MQSC ODA ODBC ODK ORB RDBMS RFC ROI SAP JCo SAP ODA SAP XI ODA SAPGUI SD SMTP SOA SOAP SSL TID VTC WAS Web AS WSAD Java Server Pages Knowledge Management Line of Business Microsoft Data Access Components Master Data Management SAP Mobile Infrastructure WebSphere MQ: Script Command Object Discovery Agent Open Database Connectivity Object Discovery Agent Development Kit Object Request Brokers Relational Database Management System Remote Function Call Return On Investment SAP Java Connector SAP Object Discovery Agent SAP XI Object Discovery Agent SAP Graphical User Interface Sales and Distribution Simple Mail Transport Protocol Service Oriented Architecture Simple Object Access Protocol Secure Socket Layer Transaction ID Visual Test Connector WebSphere Application Server SAP Web Application Server WebSphere Studio Application Developer WSDL XI XML Web Services Description Language SAP Exchange Infrastructure eXtensible Markup Language 662 WebSphere Business Integration for SAP .

2004. Note that some of the documents referenced here may be available in softcopy only. SG24-7006 Patterns: Implementing an SOA using an Enterprise Service Bus. Implementing and Administering WebSphere Business Integration Server V4. SG24-6318 WebSphere MQ Solutions in a Microsoft . SC34-6066 WebSphere MQ: Intercommunication. see “How to get IBM Redbooks” on page 664.com/software/integration/wbiadapters Microsoft Windows Update http://www. SG24-6346 WebSphere Business Integration Message Brokers Basics.1 Handbook.ibm. SG24-7090 WebSphere Business Integration Server Foundation V5. SC34-6055 WebSphere MQ System Administration Guide.NET Environment. SG24-7012 Other publications These publications are also relevant as further information sources: WebSphere MQ Using Java.windowsupdate. SC34-6068 Online resources IBM WebSphere Business Integration Adapters http://www.Related publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook. 663 . All rights reserved. SC34-6059 WebSphere MQ: Script Command (MQSC) Reference.2.com © Copyright IBM Corp.2. IBM Redbooks For information on ordering these publications.

Redpapers.com/redbooks Help from IBM IBM Support and downloads ibm. as well as order hardcopy Redbooks or CD-ROMs. Hints and Tips.SAP Interface Repository http://ifr.ibm.com/services 664 WebSphere Business Integration for SAP . view.sap.com/software/integration/mqfamily/support/summary/index. at this Web site: ibm. or download Redbooks.sap. draft publications and Additional materials.com/connector WebSphere MQ Family http://www-306.com SAP Service Marketplace (logon required) http://service. html How to get IBM Redbooks You can search for.com/support IBM Global Services ibm.

115. 118. 283 Business Object Designer tool 86 business object handler 84. 88 Business Process Execution Language for Web Services(BPEL4WS) 33 Business Process Management (BPM) 4. 25. 31 Business Applications and Data Services 24 Business Integration needs 10 Business Integration Reference Architecture 20. 98. 27 Business-to-Business processes 22 B Basic technology integration components 74 Batch Data Communications (BDC. 128–130. 75. 103. 14. 464.Index A ABAP Extension Module 101–103. 123. 173–175. 327. 31 Application Connectivity 12–13 Application connectivity 4 application connectivity 4. 23. 665 . 204. 88–89. 111. 37–40. 203 ALE module 208 an overview of how the book is organized 1 Application and Data Access Services 24. 45 Business Processes 31 business processes 11. 29–30. 17. 81 Business Application Services 22. 124. 33. 243. 99.) 81 best-of-bread components 31 BMs on demand business strategy 40 bottom-up application connectivity 14 BPEL4WS business processes 15 broker-to-broker 642 C capabilities provided by the IBM WebSphere Business Integration (WBI) product family 9 clustering 7. 374. 138 application platform of SAP NetWeaver 46 Application Programing Interface (API) 74 Application Programmable Interface (API) 23 Application Programming Interface (API) 17 Application Programming Interfaces (APIs) 47 Application Specific Business Objects (ASBO) 92 Application specific Business Objects (ASBO) 90 application specific business objects (ASBO) 87 Applications and Data Access Services 28 asynchronous workflow 4 available to promise (ATP) 66 Business Activity Monitoring (BAM) 26 Business Application and Data Services 24 Business Application Programming Interface (BAPI) 23. 644 ABAP Extension module 102. 81. 58–59. 283. 24 Business Integration Reference Architecture (BRA) 19 Business Integration Reference Architecture includes 23 Business integration scenarios 7 Business layer 46 Business Object Designer 95. 128 application connectivity and process integration styles 13 Application Link Enabling (ALE) 81. 612 Business Rule Beans framework 34 Business Server Pages (BSP) 46 Business-to-Business (B2B) 4. 123. 645 Business Performance Management (BPM) 33 Business Performance Management Services 30 Business performance management tools 21 Business Process Choreographer (BPC) 89 Business Process Execution (BPE) 89 Business Process Execution Language (BPEL) 34 Business Process Execution Language for Web Services (BPEL4WS) 50. 14. All rights reserved. 124–125. 28. 243 ABAP extension module 102 ABAP Extension Module Business Object 304 Adapter 14 Adapter Development Kit (ADK) 86 adapters 73 Advanced Business Application Programming (ABAP) 78 Agent Controller 180 ALE and ABAP Extension module 283 ALE Module 173–174. 130 Collaborative services 21 common framework 36 © Copyright IBM Corp. 2004. 44–46. 86. 20–22.

74 Enterprise JavaBeans (EJB) 46 enterprise processes 4 Enterprise Resource Planning (ERP) 10 Enterprise Service Architecture 40 Enterprise Service Bus 24. 104 E e-business on demand 38 e-business solutions xxxiv. 34 Enterprise Service Bus (ESB) 23 Enterprise Service Bus provides 23 Enterprise Services Bus 27 ERP solution 10 eXtensible Markup Language (XML) 12 extension of HTTP runnning under SSL (HTTPS) 104 I IBM Agent Controller 180 IBM Business Integration 37 IBM Business Integration portfolio 31 IBM Business Integration Reference Architecture 9. 21–23 IBM Business Object 24 IBM DB2 439 IBM on demand operating environment 32 IBM Software development platform 28 IBM software development solution 32 IBM Software Offerings in the IBM Business Integration Reference Architecture 19 IBM WebSphere Business Integration 5 IBM WebSphere Business Integration (WBI) product family 9 IBM WebSphere Business Integration adapters 82 IBM WebSphere Business Integration product and SAP integration 1 IBM WebSphere Business Integration product family 14 IBM WebSphere Business Integration products 14 IBM WebSphere MQ 331 IBM WebSphere Portal 18 Information Services 27. 19. 95 container-managed persistence (CMP) 47 Content management services 21 cross-platform integration 11 Customer Relationship Management (CRM) 11 F File transfer 13 Flow Definition Markup Language (FDML) 88 G generic business objects 608 generic business objects (GBO) 87. 31.common repository 20 Comprehensive Services 24 Comprehensive Services of IBM Business Integration Reference Architecture 19 Connectivity layer 47 Connector Configuration tool 85. 31 Integrating the SAP enterprise server 78 666 WebSphere Business Integration for SAP . 4 Eclipse framework 32 eCommerce 112 eCommerce portal 55 eCommerce Portal server 112 eCommerce portal server 112 eCommerce Portal System 55 EDI Data Handler 96 Electronic Data Interchange (EDI 18 Electronic Data Interface (EDI) 81 Enterprise Archive (EAR) 433 Enterprise Information Systems (EIS) 23. 90 generic business objects (GBOs) 92 graphical user interface (GUI) 120 D DB2 II Classic Federation provides 37 DB2 Information Integrator provides 35 Demilitarized Zone (DMZ) 112 design principles and methodologies 111 development platform 25 Development tools 20 Diverse forms of business information 22 Division to Division (D2D) 17 H heterogeneous development 10 heterogeneous sources 35 heterogeneous system 10 heterogeneous systems 22 heterogenous IT landscapes 44 Hierarchical Dynamic Retrieve (HDR) 98 HTTPS 47 Human Resource (HR) 65 Hypertext Transfer Protocol (HTTP) 47.

27 People Integration within SAP NetWeaver 42 Persistence layer 47 Pertner Services 31 Presentation layer 46 Process Integration 12–13. 109. 359. 578. 75–77. 49 mySAP. 128 Process Monitoring 26 Process Services 22. 602. 561. 33. 138. 555 Integration broker 85. 555 Lotus Domino Server 138. 86. 641–642 Lotus Domino database 136. 642. 141. 44. 582. 31 Intermediate Document (IDoc) 100 Intermediate Documents (IDOC) 81 Intermediate Documents (IDocs) 121. 355 Object Discovery Agent Development Kit (ODK) 86 Object Request Brokers (ORB) 13 Open Database Connectivity (ODBC) 179 Overview about IBM Business Integration Reference Architecture 19 overview about the different types of SAP R/3 interfaces 81 overview of the business integration landscape 4 P K Knowledge Management (KM) 43 Partner Services 22. 586. 595. 26. Index 667 . 138. 104 integration broker 73. 565–566. 104. 105. 204 Java Runtime Environment (JRE) 179–180 JavaServer Pages (JSP) 46 JMX management interface 35 N NetWeaver technology stack 49 O Object Discovery Agent (ODA) 82. 568–569. 123 Internet Communication Manager (ICM) 47 Internet Inter-ORB Protocol (IIOP) 96 IT Monitoring 26 iterative software development 25 561–563. 91–92. 138. 336. 644–645 integration broker business object 100 integration brokers 73 Integration challenges 11 Integration layer 47 Integration server 14 Integration styles 12 integration styles 12 Integration terminology 13 Interaction Services 21.com 73 J J2EE Application Server 15 J2EE standards 15 J2EE-certified runtime environment 46 Java 2 Enterprise Edition (J2EE) 19. 106. 96. 555–556. Enterprise Edition (J2EE) 28 Java 2 Platform. 642 Lotus Domino databases 138. 556. 96–102.Integration Broker 82. 85. 26. 90. 105. 44 Process integration 40 process integration 13. 123. 562 Lotus Domino technology 71 Lotus Domino toolkit 566 Lotus Notes databases 138 M Master Data Management (MDM) 44 Message oriented Middleware 13 message type MATMAS 174 message-flows 16 Microsoft Data Access Components (MDAC) 179 middleware architecture 20 mySAP Business Suite 40. 141. 49. 78. 88 Java 2 Platform. 82–83. 138. 559. 642 Lotus Domino server 138. 92. Standard Edition (J2SE) 31 Java Connector Architecture (JCA) 50 Java Data Objects (JDO) 47 Java Database Connectivity (JDBC) 14 Java Message Service (JMS) 17 Java Messaging Service (JMS) 50. 199. 31 L latest SAP releases 79 Line Of Business (LOB) 21 list of all available WebSphere Business Integration Adapters 14 Lotus Domino 136.

9 SAP backend systems 4 SAP Business Information Warehouse (BIW) 43 SAP Business Intelligence (BI) 43 SAP Business Intelligence solution 43 SAP business solutions 80 SAP Business workflow 45 SAP Composite Application Framework (CAF) 49 SAP development efforts 80 SAP Enterprise Portal 42–43 SAP Enterprise Portal framework 45 SAP Enterprise Portal package 42 SAP enterprise server 77 SAP enterprise system 78 SAP Exchange Infrastructure 44. 40. 557 SAP Exchange infrastructure 106 SAP Exchange Infrastructure (XI) 44. 71 Self-service 21 semantic differences 12 Service choreography 14 Service Oriented Architecture 37 Service Oriented Architecture (SOA) 19 Service Oriented Architecture strategies 19 Shared database 13 Simple Mail Transport Protocol (SMTP) 47 Simple Object Access Protocol (SOAP) 104–105 SOAP adapter 106 SOAP data handler 106 Some key integration features of business integration 4 standard interfaces 35 Supply Chain System 54 Supply Chain system 56 supply chain system 71 T Technology overview 10 terms used in the integration area 13 The Adapter Framework 37 The Application Specific Component 36 The Business Application Services 22 The Business Object Designer supports 98 The Collaboration component 42 The main feature of the ABAP Extension Module 103 Tivoli Monitoring for Business Integration 33 top-down business process automation 14 Transaction ID (TID) 100 Transactional characteristic 14 668 WebSphere Business Integration for SAP . 49 SAP Exchange Infrastructure IDoc adapter 141 SAP Exchange Infrastructure Integration Server 141 SAP Exchange Infrastructure JMS adapter 141 SAP graphical user interface (SAPGUI) 77 SAP Java Connector (SAP JCo) 96–97 SAP Mobile Infrastructure (MI) 43 SAP NetWeaver 40–41. 84. 45–46. 60. 555. 97 SAP Object Discovery Agent (SAP ODA) 94 SAP R/3 ALE interface 174 SAP related WebSphere Business Integration Adapters 94 SAP specific WebSphere Business Integration adapters 4 SAP Web Application Server 45–46 SAP Web Application Server (Web AS) 46 SAP Web Application Server (WebAS) 78 SAP xApps 40 SAP XI Object Discovery Agent (SAP XI ODA) 106 Secure Sockets Layer (SSL) 17. 141. 104–106. 49 SAP NetWeaver provides 48–49 SAP NetWeaver technology 5 SAP NetWeaver technology stack 9. 73. 71 Sales and Distribution (SD) 112 SAP application server 77 SAP back-end systems 5. 97. 7. 94. 121 Remote Function Calls (RFCs) 328 Remote Procedure Call 13 requirements for SAP integration 73 Return On Investment (ROI) 33 Roles and Artifacts in the IBM Business Integration Reference Architecture 19 RosettaNet 12 S Sales & Distribution 57 Sales & Distribution process 54. 56 Sales & Distribution System 54 Sales & Distribution system 55–58. 44 SAP Object Discovery Agent (ODA) 95. 46. 138.R Redbooks Web site 664 Contact us xxxix Relational Database Management System (RDBMS) 27 Remote Function Call (RFC) 81.

82. 644 Script Command (MQSC) 205 WebSphere MQ Connection factory 404. 359. 616. 85. 407 Index 669 .com 130–131 WebSphere Application Server 35 WebSphere Application Server (WAS) 34 WebSphere Application Server foundation 17 WebSphere Application Server framework provides 35 WebSphere Business Integration 7.com 94–95. 49. 466 WebSphere Business Integration adapters 73. 73 WebSphere Business Integration product family offers 93 WebSphere Business Integration product suite 7. 404. 141. 598–599. 203–204. 19 WebSphere Business Integration Server components 15. 104–105.U User Interactivity 13 V various technology options 51 Visual Test Connector (VTC) 431 W WBI Adapter 16 WBI Adapter for mySAP. 104 WebSphere Business Integration (WBI) 4 WebSphere Business Integration adapter 49 WebSphere Business Integration Adapter for mySAP. 51.com 218 WBI Collaborations 19 WBI Connect 17 WBI Event Broker 16 WBI Message Broker 16 WBI Modeler 19 WBI Monitor (formerly Holosofx) 18 WBI Server 15 WBI Server Foundation 15 WBI Toolset 17 Web Dynpro technology 46 Web Services (BPEL4WS) 35 Web Services (SAP Web Application Server 6. 588–589.20 and higher) 81 Web Services Description Language (WSDL) 34. 138. 560. 86. 106. 94. 106 Web Services programming models 35 WebSphere Adapter for mySAP. 138 WebSphere Interchange solutions 15 WebSphere MQ 16–17. 14. 34 WebSphere Business Integration Server Foundation 15 WebSphere Business Integration Server Foundation (WBISF) 464 WebSphere Business Integration Server provides 34 WebSphere Business Integration Workbench 19 WebSphere Data Interchange 18 WebSphere Data Interchange Client 18 WebSphere Host Access Transformation Services 37 WebSphere InterChange Server 15. 173–174. 439. 642. 82 WebSphere Business Integration adapters for SAP integration 4 WebSphere Business Integration Adapters portfolio 91 WebSphere Business Integration Adapters provide 36 WebSphere Business Integration brokers 4. 91 WebSphere Business Integration for SAP integration 4 WebSphere Business Integration infrastructure 5 WebSphere Business Integration Message Broker 91 WebSphere Business Integration Modeler 33 WebSphere Business Integration Monitor release 5. 49. 15. 90. 555 WebSphere Business Integration adapter for SAP XI 50 WebSphere Business Integration Adapter Framework 91 WebSphere Business Integration Adapters 23. 407–408. 633. 582. 243 WebSphere Business Integration Adapter for mySAP. 91–92 WebSphere Business Integration Connect Advanced/Enterprise provides 35 WebSphere Business Integration Event Broker 16.1 33 WebSphere Business Integration Monitor solution provides 33 WebSphere Business Integration product family 7. 91–92. 82 WebSphere Business Integration Server 15. 467.com) 237 WebSphere Business Integration adapter for SAP Exchange Infrastructure 104.

WebSphere MQ connection factory 439 WebSphere MQ Everyplace 34 WebSphere MQ Everyplace suite 34 WebSphere MQ Workflow 7. 34 WebSphere Portal Server provides 34 WebSphere Studio Application Developer Integration Edition (WSADIE) 88. 464 WebSphere Studio Application Dveloper (WSAD) 33 WebSphere Studio family 33 670 WebSphere Business Integration for SAP . 15.

0” spine) 0.WebSphere Business Integration for SAP (1.875”<->1.498” 460 <-> 788 pages .

.

.

5. For more information: ibm. A sophisticated Enterprise Service Architecture is required to overcome the challenges implied by such a heterogeneous infrastructure and make the whole enterprise controllable. SAP Exchange Infrastructure is SAP’s strategic technology platform for process integration and connectivity of SAP components and non-SAP components. This IBM Redbook illustrates how to integrate data and processes located in SAP back-end systems using WebSphere Business Integration middleware technology. Customers and Partners from around the world create timely technical information based on realistic scenarios. The WebSphere Business Integration architecture provides different Integration brokers and a multitude of application and technology adapters.Back cover ® WebSphere Business Integration for SAP WebSphere and SAP integration using WBI Adapters Business connectivity using WBI brokers WBI and SAP XI interoperability scenario The need to integrate heterogeneous environments without replacing existing IT infrastructures is growing more and more.com/redbooks SG24-6354-00 ISBN 0738491896 .0 IBM WebSphere Business Integration Adapter for SAP Exchange Infrastructure V1. Experts from IBM. Specific recommendations are provided to help you implement IT solutions more effectively in your environment. It is an essential software component in IBM's e-business on demand strategy. It describes two WebSphere Business Integration adapters: IBM WebSphere Business Integration Adapter for SAP V5. and implemented in different languages.0 These adapters are utilized to demonstrate the integration capabilities they provide. INTERNATIONAL TECHNICAL SUPPORT ORGANIZATION BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE IBM Redbooks are developed by the IBM International Technical Support Organization. running on different platforms. Standard application providers offer a wide range of business applications.

Sign up to vote on this title
UsefulNot useful