SAP NetWeaver Process Integration 7.3 - Simple Use Cases for Advanced Adapter Engine Extended (1)

8/12/2019 SAP NetWeaver Process Integration 7.3 - Simple Use Cases for Advanced Adapter Engine Extended (1)

1/47

SAP NetWeaver

Process Integration

Simple Use Cases for

Advanced Adapter

Engine Extended (AEX)

Document Version 2.0 January 2011

SAP NetWeaver 7.30


2/47

Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in

any form or for any purpose without the express permission of

SAP AG. The information contained herein may be changed

without prior notice.

Some software products marketed by SAP AG and its

distributors contain proprietary software components of other

software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,

MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER,

POWER5, OpenPower and PowerPC are trademarks or

registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are

either trademarks or registered trademarks of Adobe Systems

Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of

the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered

trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered

trademarks of W3C, World Wide Web Consortium,

Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc.,

used under license for technology invented and implemented by

Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver,

and other SAP products and services mentioned herein as well

as their respective logos are trademarks or registered

trademarks of SAP AG in Germany and in several other

countries all over the world. All other product and service names

mentioned are the trademarks of their respective companies.

Data contained in this document serves informational purposes

only. National product specifications may vary.

These materials are subject to change without notice. These

materials are provided by SAP AG and its affiliated companies

("SAP Group") for informational purposes only, without

representation or warranty of any kind, and SAP Group shall not

be liable for errors or omissions with respect to the materials.The only warranties for SAP Group products and services are

those that are set forth in the express warranty statements

accompanying such products and services, if any. Nothing

herein should be construed as constituting an additional

warranty.

Disclaimer

Some components of this product are based on Java. Any

code change in these components may cause unpredictable

and severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java Source Code delivered with this product is only to

be used by SAPs Support Services and may not be modified or

altered in any way.

Documentation in SAP Developer Network (SDN)

You can find this documentation in SAP Developer Network

(SDN) athttps://www.sdn.sap.com/irj/sdn/nw-soa

Service Bus Getting Started.

SAP AG

Dietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20

www.sap.com
https://www.sdn.sap.com/irj/sdn/nw-soahttps://www.sdn.sap.com/irj/sdn/nw-soahttps://www.sdn.sap.com/irj/sdn/nw-soa


3/47

SAP NetWeaver 7.30 Advanced Adapter Engine Extended Simple Use Cases

January 2011 3

1 Preface ........................................................................................ 52 Introduction and Prerequisites .................................................. 5

2.1 Introduction .............................................................................................. 52.2 Prerequisites ............................................................................................ 7

2.2.1 General Prerequisites ................................................................................................... 72.2.2 Providing the necessary User and Authorizations ....................................................... 82.2.3 Setting Up the File Directories ...................................................................................... 82.2.4 Creating the Technical and Business Systems in the System LandscapeDirectory of the Advanced Adapter Engine Extended .............................................................. 92.2.5 Creating the Technical and Business Systems in the System LandscapeDirectory of the PI System ...................................................................................................... 112.2.6 Defining Business System Components in the Integration Directory in theAdvanced Adapter Engine Extended ..................................................................................... 132.2.7 Defining Business System Components in the Integration Directory in the PISystem14

2.3 Design Objects Used ............................................................................. 153 Variant 1: One Sender and One Receiver using theAdvanced Adapter Engine Extended ............................................ 16

3.1 Configuring the Process Integration Scenario ....................................... 173.2 Executing the Use Case ........................................................................ 19

4

Variant 2: One Sender and Two Receivers using AdvancedAdapter Engine Extended .............................................................. 204.1 Design Objects Used ............................................................................. 204.2 Configuring the Process Integration Scenario ....................................... 204.3 Executing the Use Case ........................................................................ 21

5 Variant 3: One Sender and Two Receivers using AdvancedAdapter Engine Extended with Routing Condition ................... 22

5.1 Design Objects Used ............................................................................. 225.2 Configuring the Process Integration Scenario ....................................... 225.3 Executing the Use Case ........................................................................ 23

6 Variant 4: One Sender and Two Receivers using AdvancedAdapter Engine Extended With Mapping................................... 23

6.1 Design Objects Used ............................................................................. 246.2 Configuring the Process Integration Scenario ....................................... 246.3 Executing the Use Case ........................................................................ 24

7 Variant 5: One Sender and Two Receivers using AdvancedAdapter Engine Extended - with XML-Validation ......................... 25

7.1 Design Objects Used ............................................................................. 257.2 Configuring the Process Integration Scenario ....................................... 25


4/47


4 January 2011

7.3 Execution ............................................................................................... 268 Variant 6: One Sender and One Receiver using AdvancedAdapter Engine Extended - using Exactly Once In Order ........... 27

8.1 Design Objects Used ............................................................................. 278.2 Configuring the Process Integration Scenario ....................................... 278.3 Execution ............................................................................................... 29

9 Variant 7: One Sender and One Receiver usingcommunication between Advanced Adapter Engine Extendedand PI .............................................................................................. 30

9.1 Configuring the Process Integration Scenario in the AdvancedAdapter Engine Extended............................................................................... 30

9.1.1 Design Objects Used .................................................................................................. 309.1.2 Configuring the scenario on the Advanced Adapter Engine Extended inIntegration Directory ............................................................................................................... 31

9.2 Configuring the Process Integration Scenario in the PI System ............ 339.2.1 Design Objects Used .................................................................................................. 339.2.2 Configuring the scenario in the PI System ................................................................. 36

9.3 Executing the Use Case ........................................................................ 3910 Variant 8: One Sender and One Receiver usingcommunication between Advanced Adapter Engine Extendedand PI System - using Exactly Once In Order .............................. 39

10.1 Configuring the Process Integration Scenario in the AdvancedAdapter Engine Extended............................................................................... 4010.1.1 Design Objects Used ...................................................................................... 4010.1.2 Configuring the scenario on the Advanced Adapter Engine Extended inIntegration Directory ............................................................................................................... 40

10.2 Configuring the Process Integration Scenario in the PI System ......... 4210.2.1 Design Objects Used ...................................................................................... 4210.2.2 Configuring the Process Integration Scenario in the PI System .................... 43

10.3 Execution ........................................................................................... 4511 Appendix ................................................................................. 46

11.1 Monitoring Tools ................................................................................. 4611.1.1 Monitoring in Runtime Workbench in the PI System ...................................... 4611.1.2 Transaction SXMB_MONI in the PI System ................................................... 4611.1.3 Monitoring in Solution Manager ...................................................................... 47


5/47


January 2011 5

1 Preface

Constraints

The texts, references, and graphics contained in this manual have been compiled with utmostcare; nevertheless, it is impossible to guarantee that they are fully without error. SAP cannotassume any responsibility for the correctness or completeness of the followingdocumentation; the user alone is responsible for verifying the information contained therein.

SAP will only assume liability for damage arising from the use of this documentationirrespective of the pertinent legal basisin the case of intentional or active negligence, underno other circumstances will a warranty be made.

Definition

This manual describes simple application cases for the Extended adapter engine for processintegration and all the configuration steps that are necessary to execute the application caseson the basis of SAP NetWeaver.

Intended Audience

This manual is intended to be used by both technology and application consultants.

Structure

The structure of this document follows the sequence of steps required to configure and runthe use cases.

Additional Documentation

List of related documentation

Documentation Purpose

SAP NetWeaver Library

documentation:Demo

Examples

Introduction to demo examples and description of the

process integration scenarios

SAP NetWeaver

Documentation Simple Use

Cases

Introduction to Simple Use Cases and description of the

simple use case scenarios for Process Integration

Configuration of SAP

NetWeaver Process

Integration

Configuring usage type Advanced Adapter EngineExtended ??

This document is updated on a regular basis in SAP Developer Network (SDN) athttps://www.sdn.sap.com/irj/sdn/nw-soaService Bus Getting Started.

2 Introduction and Prerequisites

2.1 Introduction

Use cases are based on simple examples that enable you to learn the main features ofAdvanced Adapter Engine Extended. These instructions will enable you to understand,configure, and execute simple scenarios (that are based on fundamental communicationpatterns), as well as check that the scenarios are executed correctly. The prerequisite for thisdocument is that you have a general understanding of SAP NetWeaver Process Integration.

The following use case variants for the Advanced Adapter Engine Extended are available atpresent:
http://help.sap.com/saphelp_nw73/helpdata/en/48/c7a31cda5e31ebe10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/48/c7a31cda5e31ebe10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/48/c7a31cda5e31ebe10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/48/c7a31cda5e31ebe10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/ac/5eac92a34e45a2831ee59e9bce0f8d/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/ac/5eac92a34e45a2831ee59e9bce0f8d/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/ac/5eac92a34e45a2831ee59e9bce0f8d/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/ac/5eac92a34e45a2831ee59e9bce0f8d/frameset.htmhttps://www.sdn.sap.com/irj/sdn/nw-soahttps://www.sdn.sap.com/irj/sdn/nw-soahttps://www.sdn.sap.com/irj/sdn/nw-soahttp://help.sap.com/saphelp_nw73/helpdata/en/ac/5eac92a34e45a2831ee59e9bce0f8d/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/ac/5eac92a34e45a2831ee59e9bce0f8d/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/ac/5eac92a34e45a2831ee59e9bce0f8d/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/48/c7a31cda5e31ebe10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/48/c7a31cda5e31ebe10000000a42189b/frameset.htm


6/47


6 January 2011

Variant Description

Variants 1, 6, 7 and 8:

One sender and one receiver

(see3,8,9 and10)

Represents message exchange between one sender andone receiver on the Advanced Adapter Engine Extended.The message processing is done locally on the Advanced

Adapter Engine Extended.

Variant 6 is executed using EOIO protocol.

Variant 7 is executed between one sender on the AdvancedAdapter Engine Extended and one receiver on the PIIntegration Server.

Variant 8 is executed between one sender on the AdvancedAdapter Engine Extended and one receiver on the PIIntegration Server using EOIO protocol.

Variant 2:

One sender and two

receivers (see4),

Represents message exchange between one sender andtwo receivers. The message processing is done locally on

the Advanced Adapter Engine Extended..

Variant 3:

One sender and tworeceiverswith routingcondition (see5)

Represents message exchange between one sender andtwo receivers in which the way the message is forwarded tothe receivers is determined by routing conditions Themessage processing is done locally on the Advanced


Variant 4:

One sender and tworeceiverswith mapping(see6)

Represents message exchange between one sender andtwo receivers. A mapping is executed when the message isforwarded to one of the two receivers. The messageprocessing and mapping are done locally on the Advanced


Variant 5:

One sender and tworeceiverswith XML-Validation (see7)

Represents message exchange between one sender andtwo receivers. A mapping is executed when the message isforwarded to one of the two receivers. The payload isvalidated using XML-Validation in inbound processing of theadapter engine. The message processing, mapping andXML validation are done locally on the Advanced AdapterEngine Extended.

You can aim to learn about the following with the use cases:

Working with the Enterprise Services BuilderEnterprise Services Repository:Understanding existing design objects

Working with the Integration BuilderIntegration Directory: Configuring simple scenarios

and understanding created configuration objects

Working with the runtime: Executing the use cases and checking the results by usingmonitoring

SAP provides the required design objects and files for these learning targets. This documentcontains a complete set of instructions that enable you to configure and execute the usecases without any additional special prerequisites.

SAP NetWeaver Process Integration (Advanced Adapter Engine Extended)must be installed and configured, and be error free. In this respect, note theinformation under2.2.1.

Within the scenarios file directories on the host of the SAP system on which the AdvancedAdapter Engine Extended and the Integration Server is installed serve as the senders and


7/47


January 2011 7

receivers of messages. The use cases rely on file directories (and therefore the file/FTPadapter) to keep the technical prerequisites as simple as possible.

In variants 1 to 6 the messages are sent directly from the sender adapter to the receiveradapter without using the ABAP IS runtime to show the possibility of using the Advanced

Adapter Engine Extended. In variant 6 the messages are processed in sequence.

In variants 7 and 8 the messages are sent from Advanced Adapter Engine Extended to theABAP Integration Server. In variant 8 the messages are processed in sequence.

This document assumes that you will configure the variants in succession, in the orderspecified. While it is technically possible to configure the variants in a different order, doing sowould mean that the order of the step-by-step instructions in this document would no longerbe correct.

If you need to configure and execute the use cases as quickly as possible, skip

the chapters concerning the design objects used and start instead withconfiguration. You can then return to the skipped chapters at a later stage for abetter understanding of the various concepts.

2.2 Prerequisites

2.2.1 General Prerequisites

To configure and execute the use cases, SAP NetWeaver with usage type ProcessIntegration and Advanced Adapter Engine Extended must be correctly installed andconfigured. The following table lists the prerequisites and the relevant guides:

List of required steps

Step Documentation

1. You have installed the Advanced Adapter EngineExtended and SAP NetWeaver 7.30.

Master GuideSAP NetWeaver

Installation GuideSAP Web ASABAPand Java

You can find the corresponding guideson SAP Service Marketplace in theImplementation Documentation Centerfor SAP NetWeaver ProcessIntegration 7.3

2. You have imported the content for the EnterpriseServices Repository corresponding to the latestsupport package/patch into the PI and the

Advanced Adapter Engine Extended System.

SAP Note836200

The simple use cases arelocated in the EnterpriseServices Repository inthe software componentSAP BASIS, softwarecomponent version SAPBASIS 7.30, in thenamespaces

http://sap.com/xi/XI/System/Patterns.
https://websmp205.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000735500&https://websmp205.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000735500&https://websmp205.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000735500&https://websmp205.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000735500&http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=00836200&_NLANG=Ehttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=00836200&_NLANG=Ehttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=00836200&_NLANG=Ehttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=00836200&_NLANG=Ehttps://websmp205.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000735500&https://websmp205.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000735500&https://websmp205.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000735500&


8/47


8 January 2011

3. You have configured the Advanced Adapter EngineExtended and SAP NetWeaver ProcessIntegration.

Configuration of SAP NetWeaverProcess Integration

4. You have configured the System LandscapeDirectory (SLD) for the PI and the Advanced

Adapter Engine Extended System.

Configuring, Working with andAdministering System LandscapeDirectory

Note that you set up the use cases in your development or test system, but notin your productive system.

2.2.2 Providing the necessary User and Authorizations

To log on to the SAP system to configure the simple use cases, you have to create a userXIDEMOwith the following roles in the integration server client (001) andin the Advanced

Adapter Engine Extended: SAP_XI_ADMINISTRATOR

SAP_XI_CONFIGURATOR

SAP_XI_MONITOR

SAP_XI_DEMOAPP

2.2.3 Setting Up the File Directories

The variants are based on a very simple system landscape that comprises various differentfile systems (on the host of the SAP system on which the Advanced Adapter Engine

Extended and for variants 7 and 8 on the host where the PI Integration Server is installed).When the use cases are executed, files are moved between file directories. Therefore, to beable to configure the use cases, the file directories must have been created and described inthe System Landscape Directory. Only then can you access the directories duringconfiguration in the Integration Directory.

Perform the steps below to create the required directories on the host of the SAP system onwhich the Advanced Adapter Engine Extended is installed.

1. Open the file directory of the SAP system, on which the Advanced Adapter EngineExtended is installed.

For Example using Windows Explorer on Windows Systems.

2. Create a directory in which you can save files temporarily and create sub directories

XiPatterns_AAEX and XiPatternsO_AAEX in it.

A work directory already exists on many computers that can be used for thispurpose and under which you can create the required directories.

3. Create four further sub directories in the sub directory XiPatterns_AAEX. Suggested

names: XiPattern1, XiPattern2, XiPattern3, XiPattern6.

4. Create three further sub directories in the sub directory XiPatternsO_AAEX. Suggested

names: XiPattern4,XiPattern5, XiPattern8.

You must have authorization to access this directory to be able to test theprocess integration scenario. Bear this in mind when you define the directory,and, if applicable, contact your system administrator.
http://help.sap.com/saphelp_nw73/helpdata/en/ac/5eac92a34e45a2831ee59e9bce0f8d/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/ac/5eac92a34e45a2831ee59e9bce0f8d/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/ac/5eac92a34e45a2831ee59e9bce0f8d/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/48/b6847496655295e10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/48/b6847496655295e10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/48/b6847496655295e10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/48/b6847496655295e10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/48/b6847496655295e10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/48/b6847496655295e10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/48/b6847496655295e10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/ac/5eac92a34e45a2831ee59e9bce0f8d/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/ac/5eac92a34e45a2831ee59e9bce0f8d/frameset.htm


9/47


January 2011 9

5. Copy the following three files to directoriesXiPattern1 andXiPattern6

ZXiPatternSenderFile1.xml

ZXiPatternSenderFile2.xml

ZXIPatternSenderFile3.xml

6. Copy the following file to directoriesXiPattern4 andXiPattern8

XiPatternSenderFilesEOIO.zip (This file contains 1000 xml files for the EOIOscenario, they will be unpacked when executing the scenario.)

These files are provided by SAP in a ZIP file. The ZIP file is located in SAPDeveloper Network (SDN) at https://www.sdn.sap.com/irj/sdn/nw-soa Service Bus. On the page Service Bus-Based Integrationselect GettingStarted. On the page Getting Started With Service Bus-Based Integrationselectthe hyperlink Process IntegrationSimple Use CasesTest Files.

As long as the SDN page is not updated for PI 7.30 the zip File for 7.30containing also the EOIO test files can be found using this direct link:

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f0772595-19eb-2d10-6d93-95d06ed34299

Perform the steps below to create the required directories on the host of the SAP system onwhich the Integration Server is installed. These directories are necessary for Variants 7 and8.

1. Open the file directory of the SAP system on which the Integration Server is installed.

For Example using Windows Explorer on Windows Systems.

2. Create a directory in which you can save files temporarily and create sub directoriesXiPatterns_AAEX and XiPatternsO_AAEX in it.

A work directory already exists on many computers that can be used for thispurpose and under which you can create the required directories.

3. Create a sub directory in the sub directory XiPatterns_AAEX. Suggested name:

XiPattern7.

4. Create a sub directory in the sub directory XiPatternsO_AAEX. Suggested name:XiPattern9.

You must have authorization to access this directory to be able to test theprocess integration scenario. Bear this in mind when you define the directory,and, if applicable, contact your system administrator.

2.2.4 Creating the Technical and Business Systems in theSystem Landscape Directory of the AdvancedAdapter Engine Extended

Perform the following steps to create the required technical and business systems in theSystem Landscape Directory (SLD) for the Advanced Adapter Engine Extended:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f0772595-19eb-2d10-6d93-95d06ed34299http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f0772595-19eb-2d10-6d93-95d06ed34299http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f0772595-19eb-2d10-6d93-95d06ed34299http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f0772595-19eb-2d10-6d93-95d06ed34299http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f0772595-19eb-2d10-6d93-95d06ed34299


10/47


10 January 2011

1. To call the System Landscape Directory for the Advanced Adapter Engine ExtendedSystem, open the Advanced Adapter Engine Extended Start Page using the URL:http://:/dir.

2. Start the SLD. To do so, on the Advanced Adapter Engine Extended start page, choose

System Landscape Directory.

3. Log on using the XIDEMO user you created in2.2.2.

4. On the initial screen of the SLD, choose Technical Systems.

5. Create a new technical system. To do so, choose New Technical System.

6. Select the type Standalone by choosing the appropriate radio button.

7. Choose Next.

8. On the Technical System Wizard - System Detailsscreen, enter the following informationabout the technical system:

Technical System Identification:Enter a name according to the following naming

convention: _FileSystem. In this case, is the system ID of theAdvanced Adapter Engine Extended.

System Host Name: Enter the host name of theAdvanced Adapter Engine

Extended, for example pwdf2638.

9. Choose Finish.

10. Now create seven new business systems. To create the first business system, on theSLD start page, choose Business Systems.

11. Choose New Business System..

12. Select the type Standalone by selecting the appropriate radio button.

13. Choose Next.

14. Select the technical system of the Advanced Adapter Engine Extended system that youdefined previously (dropdown list box in field System).

15. Choose Next.

16. Enter the name _AAEX_FileSystem_XiPattern1 . is the system ID of

the Advanced Adapter Engine Extended System.

17. Choose Next.

18. Specify the Advanced Adapter Engine Extended System as Integration Server (fieldRelated Integration Server).

19. Choose Finish.

20. Following the same procedure, create business systems with the following names:

_AAEX_FileSystem_XiPattern2






Create two more technical systems for the file system of the integration server for variants 7and 8.

1. To do so, choose New Technical System.


11/47


January 2011 11


3. Choose Next.

4. On the Technical System Wizard - System Detailsscreen, enter the following information

about the technical system:


convention: _FileSystem. In this case, is the system ID of thePI

System.

System Host Name: Enter the host name of thePI System, for example pwdf2638.

5. Choose Finish.

6. Now create two new business systems using this Technical System. To create the firstbusiness system, on the SLD start page, choose Business Systems.



9. Choose Next.

10. Select the technical system for the PI Integration Server File System that you just defined(dropdown list box in field System).

11. Choose Next.

12. Enter the name _PI_FileSystem_XiPattern7 . is the system ID of the

PI Integration Server.

13. Choose Next.

14. Specify the Advanced Adapter Engine Extended System as Integration Server (fieldRelated Integration Server).

15. Choose Finish.16. Following the same procedure, create another business system with the name

_PI_FileSystem_XiPattern9.

2.2.5 Creating the Technical and Business Systems in theSystem Landscape Directory of the PI System

Perform the following steps to create the required technical and business systems in theSystem Landscape Directory (SLD) for the PI System. These steps are necessary for theVariants 7 and 8.

1. To call the System Landscape Directory, in the SAP menu in the PI Integration Serverchoose Process Integration Start Integration Builderin the user menu.

2. Start the SLD. To do so, on the Process Integration start page, choose SystemLandscape Directory.

3. Log on using the XIDEMO user you created in2.2.2.

4. On the initial screen of the SLD, choose Technical Systems.

5. Create a new technical system. To do so, choose New Technical System.


7. Choose Next.

8. On the Technical System Wizard - System Detailsscreen, enter the following informationabout the technical system:


12/47


12 January 2011


convention: _FileSystem. In this case, is the system ID of thePI

Integration Server.

System Host Name: Enter the host name of thePI Integration Server, for example

pwdf2638.

9. Choose Finish.

10. Now create two new business systems. To create the first business system, on the SLDstart page, choose Business Systems.



13. Choose Next.

14. Select the technical system of the PI system that you defined previously (dropdown listbox in field System).

15. Choose Next.

16. Enter the name _PI_FileSystem_XiPattern7 . is the system ID of the

Integration Server.

17. Choose Next.

18. Specify the PI System as Integration Server (field Related Integration Server).

19. Choose Finish.

20. Following the same procedure, create the business system with the name_PI_FileSystem_XiPattern9.

To enable the communicating between Advanced Adapter Engine Extended and the PISystem create a new technical system.

1. To do so, choose New Technical System.


3. Choose Next.

4. On the Technical System Wizard - System Detailsscreen, enter the following information

about the technical system:


convention: _FileSystem. In this case, is the system ID of the

Advanced Adapter Engine Extended.

System Host Name: Enter the host name of theAdvanced Adapter Engine

Extended, for example pwdf2638.5. Choose Finish.

6. Now create two new business systems. To create the first business system, on the SLDstart page, choose Business Systems.



9. Choose Next.

10. Select the technical system of the Advanced Adapter Engine Extended system that youjust defined (dropdown list box in field System).

11. Choose Next.

12. Enter the name _AAEX_FileSystem_XiPattern6 . is the system ID of

the Advanced Adapter Engine Extended System.


13/47


January 2011 13

13. Choose Next.

14. Specify the PI System as Integration Server (field Related Integration Server).

15. Choose Finish.

16. Following the same procedure, create another business system with the following name_AAEX_FileSystem_XiPattern8.

2.2.6 Defining Business System Components in theIntegration Directory in the Advanced AdapterEngine Extended

In the following steps you define communication components for the business systems youjust created in the Advanced Adapter Engine Extended. You need to create communicationcomponents to be able to address the business systems as senders/receivers of messageswhen you configure the process integration scenario in the Integration Directory.

To prepare the configuration of the process integration scenario, you must do the following: Define the involved business systems as communication components (business

system components) in the Integration Directory

Only then can you address the business systems as senders or receivers ofmessages.

Define communication channels for outbound message processing (for all relevantreceiver business systems)

You define communication components in the Integration Directory of the Advanced AdapterEngine Extended.

Therefore, to execute the activities described below, call the Integration Builder (userinterface of Integration Directory).

1. To call the Integration Directory for the Advanced Adapter Engine Extended System,open the Advanced Adapter Engine Extended Start Page using the URL: http://:/dir.

2. On the Advanced Adapter Engine Extended Start Page, choose the hyperlink IntegrationBuilder (underIntegration Directory).

3. Log on using the XIDEMO user you created in2.2.2.The system opens the IntegrationBuilder.

You use the steps below to define a communication component (business systemcomponent) in the Integration Directory for each business system.

1. Clear the SLD cache. To do this, select EnvironmentClear SLD Data Cachein the

menu of the Integration Builder.

2. In the Integration Builder navigation area, on the Objectstab page, position the cursor onthe Communication Components Without Party node.

3. To call the wizard for assigning business systems, chooseAssign Business Systeminthe context menu.

4. On the next screen, choose Continue.

The business system components are not assigned to a party.

5. On the next screen, select the following business systems by using the correspondingcheckboxes:




14/47


14 January 2011






_PI_FileSystem_XiPattern7


6. Make sure that the checkbox Create Communication Channels for Following Adaptersisdeselected.

The relevant communication channels are created when the process integration

scenario is configured.7. Choose Finish.

The system displays the communication components in the Integration Builder navigationarea, on the Objectstab page, under Communication Components Without Party Business System.

Perform the following steps to activate the communication components.

1. In the navigation area, choose the Change Lists tab page.

2. Choose OpenStandard Change List.

3. Check that the five communication components you just created are contained in thechange list.

4. Position the cursor on the Standard Change List node and chooseActivate ( ) in thecontext menu.

2.2.7 Defining Business System Components in theIntegration Directory in the PI System

In the following steps you define communication components on the PI system for thebusiness systems you just created. You need to create communication components to beable to address the business systems as senders/receivers of messages when you configurethe process integration scenario in the Integration Directory. For Variants 7 and 8 thecommunication components need to be known in the Advanced Adapter Engine Extendedand in the PI System as messages are exchanges between both.

To prepare the configuration of the process integration scenario, you must do the following:

Define the involved business systems as communication components (businesssystem components) in the Integration Directory

Only then can you address the business systems as senders or receivers ofmessages.

Define communication channels for outbound message processing (for all relevantreceiver business systems)

You define communication components in the Integration Directory.

Therefore, to execute the activities described below, call the Integration Builder (user

interface of Integration Directory).4. To call the Integration Builder, in the SAP System of the Integration Server choose

Process IntegrationStart Integration Builderin the user menu.


15/47


January 2011 15

5. On the initial screen, choose the hyperlink Integration Builder (underIntegrationDirectory).

6. Log on using the XIDEMO user you created in2.2.2.The system opens the IntegrationBuilder.

You use the steps below to define a communication component (business systemcomponent) in the Integration Directory for each business system.

1. Clear the SLD cache. To do this, select EnvironmentClear SLD Data Cachein themenu of the Integration Builder.

2. In the Integration Builder navigation area, on the Objectstab page, position the cursor onthe Communication Components Without Party node.

3. To call the wizard for assigning business systems, chooseAssign Business Systeminthe context menu.

4. Choose Continue.

5. On the next screen, choose Continue.

The business system components are not assigned to a party.

6. On the next screen, select the following business systems by using the correspondingcheckboxes:





7. Make sure that the checkbox Create Communication Channels for Following Adaptersisdeselected.

The relevant communication channels are created when the process integrationscenario is configured.

8. Choose Finish.

The system displays the communication components in the Integration Builder navigationarea, on the Objectstab page, under Communication Components Without Party Business System.

Perform the following steps to activate the communication components.

5. In the navigation area, choose the Change Lists tab page.


7. Check that the five communication components you just created are contained in thechange list.

8. Position the cursor on the Standard Change List node and chooseActivate ( ) in thecontext menu.

2.3 Design Objects Used

This section explains all the design objects that are used for describing thevariants.


16/47


16 January 2011

The subsequent description of each variant will refer to the description in thissection; the relevant design objects will only be listed briefly in each case.

Process Integration Scenario/Component View

A process integration scenario describes the process flow and represents the points in theprocess flow at which messages are exchanged between application components (in thiscase, the application components Sender and Receiver). Component ViewFile2File_NoMapping represents the variant with message exchange between Advanced

Adapter Engine Extended and the PI System, whereas the Component ViewFile2File_NoMapping_InOrder represents the variant with message exchange in EOIO. Thevariants only running locally in the Advanced Adapter Engine Extended are not based oncomponent views because they are using the integrated configuration.

Interface Objects

Interface objects describe the communication mode and the data structure for exchanging

messages. Interface objects comprise service interfaces, message types, and data types,which you can open by means of forward navigation, starting with the Service Interfaces.

Mapping Objects

If the interfaces at the sender and receiver are different, a mapping is required.

Communication Channel Templates

You use communication channel templates to define details, which were defined when theprocess integration scenario was defined, for the inbound or outbound processing of themessage. You can then use the communication channel template to create thecorresponding communication channel when configuring in the Integration Directory. You

then need to specify all the details, which are only known at configuration time, in thecommunication channel.

The specific design objects will be listed in the specific variants below.

3 Variant 1: One Sender and One Receiverusing the Advanced Adapter EngineExtended

This variant enables you to configure and execute the simplest kind of message exchange:

One sender (file directoryXiPattern1) sends a message to one receiver (file directory

XiPattern2). Hereby, the message is exchanged between sender and receiver adapter byusing one Advanced Adapter Engine Extended. No mapping is executed between theoutbound and inbound interface in this variant.

Summary of Design Objects Used

The design objects used are summarized in the following table.

For a general description of the various object types, see SAP Help Portal at:

Enterprise Services Repository.

Design Objects Used

Object Type (Name) Description
http://help.sap.com/saphelp_nw73/helpdata/en/61/fec608bc27654daadb20c1e6da7dd1/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/61/fec608bc27654daadb20c1e6da7dd1/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/61/fec608bc27654daadb20c1e6da7dd1/frameset.htm


17/47


January 2011 17

Service Interface

(XiPatternInterface1)

Specifies the communication mode (asynchronous) and references

the message type used.

Message Type

(XiPattermMessage1)

Describes the message sent at runtime and references the data type

used.

Data Type (XiPatternDataType1) Describes the data structure of the message


for Sender and Receiver

(XiPatternChannel_FileSender,

XiPatternChannel_FileReceiver)

Specifies the sender (and receiver) adapter configuration details,

which are defined at design time. Communication channel templates

enable a communication channel to be preconfigured at design time.

3.1 Configuring the Process Integration ScenarioYou perform the following configuration steps in the Integration Directory of the Advanced


For this scenario, the integrated configuration object is used for configuration.

For more information, seeDefining the Integrated Configuration.

Calling the Integration Directory

First, call the Integration Directory. To call the Integration Directory for the Advanced AdapterEngine Extended System, open the Advanced Adapter Engine Extended Start Page using

the URL: http://:/dir.

Creating a Configuration Scenario

Perform the following steps to create a configuration scenario to group the configurationobjects.

1. In the Integration Directory main menu, choose ObjectNew.

2. UnderAdministrationselect Configuration Scenario.

3. Enter the name XiPatternOneStepScenario_AAEX .

4. Choose Create.

5. Save the configuration scenario.

Creating the Communication Channels for Sender and Receiver

Perform the following steps to create the communication channels.


2. Under Collaboration Profileselect Communication Channel.

3. Call the input help ( ) for the Communication Component.

4. Select the communication component _AAEX_FileSystem_XiPattern1andchooseApply.

5. In field Communication Channelenter XiPatternChannel_FileSender .

6. UnderAdd to Scenarioselect XiPatternOneStepScenario_AAEX (input help).
http://help.sap.com/saphelp_nw73/helpdata/en/48/cfac399bf23e49e10000000a421937/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/48/cfac399bf23e49e10000000a421937/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/48/cfac399bf23e49e10000000a421937/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/48/cfac399bf23e49e10000000a421937/frameset.htm


18/47


18 January 2011

7. Choose Create.

The newly created communication channel is opened.

8. In the menu of the communication channel object editor select CommunicationChannelApply Template.

9. Select the template XiPatternChannel_FileSender .

10. ChooseApply.

11. UnderFile Access Parameterin the Source Directoryfield, enter the path in the filedirectory that you defined under2.2.3.In the case of the sender communicationchannel, enter the whole path for the file directoryXiPattern1.

Example: C://XiPatterns_AAEX/XiPattern1

12. In the fieldAdapter Engine select the central adapter engine.

13. Save the communication channel.

14. Following the same procedure, create the communication channelXiPatternChannel_FileReceiver(communication component

_AAEX_FileSystem_XiPattern2 ) using the template

XiPatternChannel_FileReceiver. Select the central adapter engine and enter the pathfor the file directoryXiPattern2.

If there already is an entry for the communication component in the CreateCommunication Componentscreen delete it before calling the input help.

Otherwise the input help may not provide the component

_AAEX_FileSystem_XiPattern2. 15. Save the communication channel.

16. Save the scenario.

17. Activate the change list.

Creating the Integrated Configuration


2. Under Collaboration Agreementselect Integrated Configuration.

3. Call the input help ( ) in the field Communication Component.

4. Select the communication component _AAEX_FileSystem_XiPattern1

and chooseApply.

5. In the fields Interfaceand Namespaceenter XiPatternInterface1 and

http://sap.com/xi/XI/System/Patterns , respectively.

The input help may not show the interface and namespace. Create the entrymanually or choose CategoryAnyin the F4 Help.

6. UnderAdd to ScenarioselectXiPatternOneStepScenario_AAEX(input help).

7. Choose Create.

8. In tab Inbound Processingselect the communication channel

XiPatternChannel_FileSender . For the software component version of sender

interface select SAP BASIS 7.30.


19/47


January 2011 19

9. In the tab Receiver select the communication component

_AAEX_FileSystem_XiPattern2 .

10. In tab Receiver Interfacesfor name and namespace enter XiPatternInterface1

and http://sap.com/xi/XI/System/Patterns , respectively. In Software

Component Version set SAP BASIS 7.30.

The input help may not show the interface and namespace. Create the entrymanually.

11. In the tab Outbound Processingselect the communication channel

XiPatternChannel_FileReceiver .

12. Save the integrated configuration.

13. Save the Configuration Scenario.

Activating the Change List1. To do this, select the Change Liststab in the Integration Directory navigation area.


3. Position the cursor on the Standard Change Listnode and chooseActivate ( )) in

the context menu.

3.2 Executing the Use Case

You perform the following steps to check that the use case is executed without errors.

1. On the host of the Advanced Adapter Engine Extended, open the file directory

XiPattern1.

2. Rename the fileZXiPatternSenderFile1.xmlas

XiPatternSenderFile1.xml .

The File/FTP adapter is designed in a way that a file with exactly this name isrecognized and moved from the source directoryXiPattern1to the target directoryXiPattern2every 60 seconds. If the configuration was executed without errors, the filewill be moved from the source directory within 60 seconds after it is renamed.

3. Open the directoryXiPattern2and check that the file has arrived.

4. Open the file and check whether the content has changed (compare with the originalfile ZXiPatternSenderFile1.xml).

The file must not have been changed when this variant is executed.Furthermore, you can check the processing in the message in monitoring. To do this,proceed as follows:

1. Start the Monitoring by choosing Configuration and Monitoring Home on theAdvanced Adapter Engine Extended start page.

2. Choose Message Overview.

3. Select Database.

4. Use appropriate filter criteria to restrict the number of XML messages displayed (forexample, the processing period).

5. Choose Go.

The system displays the selected messages in a table. You want to locate themessages that were sent during execution.


20/47


20 January 2011

6. Select the message to be displayed by selecting the appropriate radio button andthen choose Open Message.

The tab Payloadsdisplays the message contents for the various versions of themessage during processing.

4 Variant 2: One Sender and Two Receiversusing Advanced Adapter Engine Extended

This variant extends variant 1 by adding an additional receiver. The message is sent from thesender to two receivers using the Advanced Adapter Engine Extended, without a mappingbeing executed at runtime.

One sender (file directoryXiPattern1) sends a message to two receivers (file directoryXiPattern2 and XiPattern3 ). The message is exchanged between sender and receiveradapter using the Advanced Adapter Engine Extended. No mapping is executed between the

outbound and inbound interface in this variant.


In this variant the same interfaces are used as in variant 1. Note that no process integrationscenario exists for this variant.

4.2 Configuring the Process Integration ScenarioWhen you configure this variant, you will extend the configuration settings from variant 1. Youuse the same configuration scenarioXiPatternOneStepScenario_AAEXas in variant 1.

Opening the Configuration Scenario

In this variant, the configuration scenarioXiPatternOneStepScenario_AAEXcreated invariant 1 is extended.

The integrated configuration object is used again for configuration for this scenario. Themodel configurator is not used in this case.


Creating the Communication Channel for the Second Receiver



2. Under Collaboration Profile, select Communication Channel.

3. Call the input help ( ) for the communication component.

4. Select the communication component _AAEX_FileSystem_XiPattern3andchooseApply.

5. In field Communication Channelenter XiPatternChannel_FileReceiver .

6. UnderAdd to Scenarioselect XiPatternOneStepScenario_AAEX (input help).

7. Choose Create.The newly created communication channel is opened.


21/47


January 2011 21

8. In the menu of the communication channel object editor, select CommunicationChannelApply Template.

9. Select the template XiPatternChannel_FileReceiver .

10. ChooseApply.11. UnderFile Access Parametersin the Target Directoryfield, enter the path in the file

directory that you defined under Error! Reference source not found.. In the case ofthe sender communication channel, enter the whole path for the file directoryXiPattern3.






Changing the Integrated Configuration

1. In the Integration Directory main menu, open the Integrated Configuration Object_AAEX_FileSystem_XiPattern1 / XiPatternInterface1 /http://sap.com/xi/XI/System/Patterns.

2. Switch to change mode ( ).

3. In the tab Receiver add a new line andadditionally select the communication

component _AAEX_FileSystem_XiPattern3 .

4. In tab Receiver Interfacesselect the line for the communication component

_AAEX_FileSystem_XiPattern3. In the table Receiver Interfaces and

Mappings for name and namespace enter XiPatternInterface1and

http://sap.com/xi/XI/System/Patterns , respectively. In Software



5. In the tab Outbound Processingselect the line for the communication component

_AAEX_FileSystem_XiPattern3. In the table Configuration select the

communication channel XiPatternChannel_FileReceiver .


Activating the Change List

1. To do this, select the Change Liststab in the Integration Directory navigation area.


3. Position the cursor on the Standard Change Listnode and chooseActivate ( )) inthe context menu.

4.3 Executing the Use CaseYou perform the following steps to check that the process integration scenario is executedwithout errors.
http://sap.com/xi/XI/System/Patternshttp://sap.com/xi/XI/System/Patternshttp://sap.com/xi/XI/System/Patterns


22/47


22 January 2011

As for the execution of variant 1, in directoryXiPattern1, copy the fileZXiPatternSenderFile1.xmland rename itXiPatternSenderFile1.xml. The file will be movedfrom the directory within the next 60 seconds.

Since this variant has two target directories (receivers), check in both directoryXiPattern2

andXiPattern3, whether the file has arrived. The file should be available in both directories.

The content of the xml file should not change as no mapping is executed.

Check the message monitoring as described for variant 1. The message monitoring willdisplay two messages, one for each of the receivers.

In this variant, two messages are created from the outbound message (one foreach receiver).

5 Variant 3: One Sender and Two Receiversusing Advanced Adapter Engine Extended with Routing Condition

This variant extends variant 2 by adding a routing condition. Depending on the condition, themessage is sent to one of the two receivers.


In this variant, the same interfaces are used as in variant 1. Note that no process integrationscenario exists for this variant.

5.2 Configuring the Process Integration Scenario

When you configure this variant, you will extend the configuration settings from variant 1 and2. You use the same configuration scenarioXiPatternOneStepScenario_AAEX.

Using the Configuration Scenario

In this variant, the configuration scenarioXiPatternOneStepScenario_AAEXcreated invariants 1 and 2 is extended.

For this scenario, again the integrated configuration object is used for configuration. Themodel configurator is not used in this case.


1. In the Integration Directory main menu, open the integrated configuration object_AAEX_FileSystem_XiPattern1 / XiPatternInterface1 /http://sap.com/xi/XI/System/Patterns


3. In tab Receiver, select the cell for the receiver component_AAEX_FileSystem_XiPattern2in the column Condition.

4. Call the condition editor by choosing the input help icon ( ).

5. In the column Left Operand, call the expression editor by choosing the input help icon

( ).

6. In the expression editor, select theXPathradio button.


23/47


January 2011 23

The data structure of the message is displayed.

7. Expand the structure and select the element CountryCodeby using the cursor.

8. Choose OK.

9. In the condition editor, choose the operator =in the column Op.

10. In the column Right Operand, enter US.

11. Choose OK.

You have specified the routing condition CountryCode = US.

At runtime, messages that have the value USentered for the elementCountryCodeare sent to receiver _AAEX_FileSystem_XiPattern2.

12. Following this procedure, create the routing condition CountryCode = DEfor the

configured receiver _AAEX_FileSystem_XiPattern3.







You perform the following steps to check that the process integration scenario is executedwithout errors.

In directoryXiPattern1, copy the file ZXiPatternSenderFile1.xmland rename the copied fileXiPatternSenderFile1.xml. The file will be moved from the directory within the next 60seconds.

Check whether the file has arrived in directory XiPattern2. Open the file and check that thecountry code US is entered in the personal data.

There should be no file in directoryXiPattern3.

Message monitoring contains one entry for this exchange of messages.

You can repeat this procedure for file ZXiPatternSenderFile2.xml. This fileshould arrive in directoryXiPattern3(contains personal data with the countrycode DE).

6 Variant 4: One Sender and Two Receiversusing Advanced Adapter Engine Extended With Mapping

In this variant the scenario from variant 3 is extended. The message is sent to two receivers.A mapping is executed when the message is forwarded to one of the two receivers.


24/47


24 January 2011

6.1 Design Objects UsedIn this variant the same interfaces are used as in variant 1. Note that no process integrationscenario exists for this variant.

Mapping Objects

The mappingXiPatternInterface1ToInterface2is executed between the sender and receiverdata structure for receiver _AAEX_FileSystem_XiPattern3 during message exchange.


When you configure this variant, you will extend the configuration settings from variant 3. Youuse the same configuration scenarioXiPatternOneStepScenario_AAEX.

Using the Configuration Scenario

In this variant the configuration scenarioXiPatternOneStepScenario_AAEXcreated in variant1 and extended in variants 2 and 3 is extended to use a mapping for one of the receivers.

For this scenario, again the integrated configuration object is used for configuration. Themodel configurator is not used.


1. In the Integration Directory main menu, open the integrated configuration object_AAEX_FileSystem_XiPattern1 / XiPatternInterface1 /http://sap.com/xi/XI/System/Patterns


3. In tab Receiver Interfacesselect the line for the communication component_AAEX_FileSystem_XiPattern3. In table Receiver Interfaces for

mapping select the mappingXiPatternInterface1ToInterface2 from software

component versionSAP BASIS 7.30.

4. In tab Outbound Processing, select the line for the communication component

_AAEX_FileSystem_XiPattern3. In the table Configuration, select the

communication channel XiPatternChannel_FileReceiver again as in this

scenario another interface is used(XiPatternInterface2).

5. Save the Integrated configuration.







In directoryXiPattern1, copy the file ZXiPatternSenderFile2.xml. Rename the file to

XiPatternSenderFile2.xml. The file will be moved from the directory within the next 60seconds.


25/47


January 2011 25

Check whether a file has arrived in directory XiPattern3. Open the file. The structure will havechanged: the first and the second name of the person have been concatenated; the field forthe telephone number has a new name.

Monitoring contains one entry for this exchange of messages.

You can repeat this procedure for file ZXiPatternSenderFile1.xml. This file isexpected in directoryXiPattern2 (no mapping executed).

7 Variant 5: One Sender and Two Receiversusing Advanced Adapter Engine Extended -with XML-Validation

This variant extends variant 4 by switching on the XML-Validation to check the schema of the

file to be sent. The message is sent from the sender to two receivers using the AdvancedAdapter Engine Extended if the schema is correct, the file will not be picked up if the structuredoes not fit.


In this variant the same interfaces are used as in variant 1. Note that no process integrationscenario exists for this variant.

7.2 Configuring the Process Integration ScenarioWhen you configure this variant, you will extend the configuration settings from variant 4. You

use the same configuration scenarioXiPatternOneStepScenario_AAEX.

Opening the Configuration Scenario

In this variant the configuration scenarioXiPatternOneStepScenario_AAEXcreated in variant1 and extended in variants 2 to 4 is extended to use XML-Validation to check the structure ofthe message.

For this scenario, again the integrated configuration object is used for configuration. Themodel configurator is not used.


1. In the Integration Directory main menu, open the integrated configuration object

_AAEX_FileSystem_XiPattern1 / XiPatternInterface1 /http://sap.com/xi/XI/System/Patterns


3. In tab Inbound Processingfor Schema Validation select the radio button Validation byAdapter.

4. Save the Integrated configuration.



2. Choose Open

Standard Change List.3. Position the cursor on the Standard Change Listnode and chooseActivate ( )) in

the context menu.


26/47


26 January 2011

7.3 ExecutionYou perform the following steps to check that the process integration scenario is executedwithout errors.

Execution without Validation Error

For the execution in directoryXiPattern1, rename the file ZXiPatternSenderFile1.xmltoXiPatternSenderFile1.xml. The file will be moved from the directory within the next 60seconds.

Check in directoryXiPattern2whether the file has arrived.

Furthermore, you can check the processing in the message in monitoring. To do this,proceed as follows:

1. Start the Monitoring by choosing Configuration and Monitoring Homeon the Process

Integration start page.

2. Choose Message Overview.3. Select Database.

4. Use appropriate filter criteria to restrict the number of XML messages displayed (forexample, the processing period).

5. Choose Go.

The system displays the selected messages in a table. You want to locate themessages that were sent during execution.

6. Select the message to be displayed by selecting the appropriate radio button andthen choose Open Message.

The tab Payloadsdisplays the message contents for the various versions of the

message during processing.

Message monitoring displays one message.

Execution with Validation Error

For the execution with wrong XML schema in directoryXiPattern1, rename the fileZXiPatternSenderFile3.xmltoXiPatternSenderFile3.xml. The file will not be moved from thedirectory within the next 60 seconds. No file should arrive in directoryXiPattern2. The

message-processing will not process the message because the message has the wrongXML-schema. If you check the XML file ZXiPatternSenderFile3.xml, you will see a tag withthe name Email, this tag does not exist in the message typeXiPatternMessage1used in theoutbound interfaceXiPatternInterface1.

You cannot see the error in message monitoring because the adapter engine does not createa message out of the file because of the wrong structure. You can only see the error inchannel monitoring. To do this, proceed as follows:

1. Start the Monitoring by choosing Configuration and Monitoring Homeon the ProcessIntegration start page.

2. SelectAdapter EngineCommunication Channel Monitoring.

3. Use the LinkAdvancedto get additional selection fields.

4. Set XiPatternChannel_FileSender as channel name and_AAEX_FileSystem_XiPattern1 as communication component to get only thechannel used for this variant.

5. Choose Go.


27/47


January 2011 27

The system displays the channel used for picking up the files from the senderdirectory. You will see that the channel is in error state because the XML-Validationfound an error in the structure of the payload.

To end the processing delete the fileXiPatternSenderFile3.xml from the directory.

8 Variant 6: One Sender and One Receiverusing Advanced Adapter Engine Extended -using Exactly Once In Order

This variant enables you to configure and execute the simplest kind of message exchange:one sender on the Advanced Adapter Engine Extended (file directoryXiPatterns4) sends aseries of messages to one receiver on the Advanced Adapter Engine Extended (file directoryXiPatterns5). No mapping is executed between the outbound and inbound interface in this

variant. The messages are delivered in some particular order. Concretely, the file adapterallows either the last-modified timestamp or the filename to be used to order the input files in

its directory.


Interface Objects

In this variant, the data structures at both the sender and receiver side are the same and nomapping is required, the service interfacesXiPatternInterface1O is used for sender andreceiver

Summary of Design Objects Used

The following table summarizes the design objects used.

Design Objects Used


Component View

File2File_NoMapping_InOrder (Process

Integration Scenario

XiPatternOneStepScenario)

Describes the process flow and the message exchange for this

variant.

Service interface (XiPatternInterface1O) Describes the interface and data structure of the sender and

receiver. The data structure is the same for sender and

receiver.Message Type (XiPatternMessage1)

Data Type (XiPatternDataType1)


To configure this variant, a new configuration scenario is created.






28/47


28 January 2011

3. Enter the name XiPatternOneStepScenario_AAEX_EOIO .

4. Choose Create.







4. Select the communication component _AAEX_FileSystem_XiPattern4 andchooseApply.

5. In field Communication Channelenter XiPatternChannel_FileSender .

6. UnderAdd to Scenarioselect XiPatternOneStepScenario_AAEX_EOIO (input

help).

7. Choose Create.


8. In the menu of the communication channel object editor select CommunicationChannelApply Template.

9. Select the template XiPatternChannel_FileSenderO .

10. ChooseApply.

11. UnderFile Access Parameterin the Source Directoryfield, enter the path in the file

directory that you defined under Error! Reference source not found.. In the case ofthe sender communication channel, enter the whole path for the file directoryXiPattern4.

Example: C://XiPatternsO_AAEX/XiPattern4



14. Following the same procedure, create the communication channelXiPatternChannel_FileReceiver(communication component

_AAEX_FileSystem_XiPattern5 ) using the templateXiPatternChannel_FileReceiverO. Select the central adapter engine and enter thepath for the file directoryXiPattern5.

If there already is an entry for the communication component in the CreateCommunication Componentscreen delete it before calling the input help.Otherwise the input help may not provide the component_AAEX_FileSystem_XiPattern5.





29/47


January 2011 29





4. Select the communication component _AAEX_FileSystem_XiPattern4

and chooseApply.

5. In the fields Interfaceand Namespaceenter XiPatternInterface1 and



6. UnderAdd to ScenarioselectXiPatternOneStepScenario_AAEX_EOIO(input help).

7. Choose Create.


XiPatternChannel_FileSender . For the software component version of sender



_AAEX_FileSystem_XiPattern5 .

10. In tab Receiver Interfacesfor name and namespace enter XiPatternInterface1

and http://sap.com/xi/XI/System/Patterns , respectively. In Software



11. In the tab Outbound Processingselect the communication channel

XiPatternChannel_FileReceiver .


13. Save the Configuration Scenario.





8.3 Execution


1. Stop the channel _AAEX_FileSystem_XiPattern4 | XiPatternChannel_FileSenderin the Configuration and Monitoring HomeAdapter EngineCommunication ChannelMonitoringto make sure no processing runs during the time the files are placed into the

source folder.


30/47


30 January 2011

2. On the host of the Advanced Adapter Engine Extended open the file directoryXiPatternsO_AAEX/XiPatterns5. If the output file XiPatternReceiverFile.txt is alreadypresent, delete this file. The execution of this test will create this file if it is not present andappend a series of output files to this file.

3. Open the file directoryXiPatternsO_AAEX/XiPatterns4

4. Unpack fileXiPatternSenderFilesEOIO.zip in the current directory. This will placea seriesof input filesXiPatternSenderFile00001.xml, , XiPatternSenderFile01000.xml.

The File/FTP adapter is configured so that the files are picked in the order sorted by thefile names and moved from the source directoryXiPatterns4to the target directoryXiPatterns5and the files are concatenated into a single fileXiPatternReceiverFile.txt.

5. Start the channel _AAEX_FileSystem_XiPattern4 | XiPatternChannel_FileSenderin the Configuration and Monitoring HomeAdapter EngineCommunication ChannelMonitoringto start processing the files.

6. Open the directoryXiPatternsO_AAEX/XiPatterns5and check that the files have beentransferred.

7. Open the XML fileXiPatternReceiverFileAll.xml which includes the output file and checkwhether the content is in the correct order.

The content must be in the correct order with the incremental ID value and the entirecontent must be present.

8. Furthermore, you can check the processing of the messages in the message monitoringas in Variant 1.

9 Variant 7: One Sender and One Receiver

using communication between AdvancedAdapter Engine Extended and PI

This variant enables you to configure and execute the simplest kind of message exchange:

One sender (file directoryXiPattern1) sends a message to one receiver (file directoryXiPattern2). Hereby, the message is exchanged between a sender file adapter on theAdvanced Adapter Engine Extended and a receiver f ile adapter on the PI system. Nomapping is executed between the outbound and inbound interface in this variant.

9.1 Configuring the Process Integration Scenario in

the Advanced Adapter Engine Extended

9.1.1 Design Objects Used

The design objects used are summarized in the following table.

For a general description of the various object types, see SAP Help Portal at:

Enterprise Services Repository.

Design Objects Used

http://help.sap.com/saphelp_nw73/helpdata/en/61/fec608bc27654daadb20c1e6da7dd1/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/61/fec608bc27654daadb20c1e6da7dd1/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/61/fec608bc27654daadb20c1e6da7dd1/frameset.htm


31/47


January 2011 31

Service Interface

(XiPatternInterface1)

Specifies the communication mode (asynchronous) and references

the message type used.

Message Type

(XiPattermMessage1)

Describes the message sent at runtime and references the data type

used.

Data Type (XiPatternDataType1) Describes the data structure of the message


for Sender and Receiver

(XiPatternChannel_FileSender,

XiPatternChannel_XiReceiver,

XiPatternChannel_FileReceiver)

Specifies the sender (and receiver) adapter configuration details,

which are defined at design t ime. Communication channel templates

enable a communication channel to be preconfigured at design time.

9.1.2 Configuring the scenario on the Advanced AdapterEngine Extended in Integration Directory

You perform the following configuration steps in the Integration Directory of the AdvancedAdapter Engine Extended.

For this scenario, the integrated configuration object is used for configuration.


Calling the Integration Directory

First, call the Integration Directory. To call the Integration Directory for the Advanced AdapterEngine Extended System, open the Advanced Adapter Engine Extended Start Page usingthe URL: http://:/dir.





3. Enter the name XiPatternOneStepScenario_AAEX_PI .

4. Choose Create.







4. Select the communication component _AAEX_FileSystem_XiPattern6and chooseApply.

5. In field Communication Channelenter XiPatternChannel_FileSender.


32/47


32 January 2011

6. UnderAdd to Scenarioselect XiPatternOneStepScenario_AAEX_PI (input help).

7. Choose Create.


8. In the menu of the communication channel object editor select Communication ChannelApply Template.

9. Select the template XiPatternChannel_FileSender .

10. ChooseApply.

11. UnderFile Access Parameterin the Source Directoryfield, enter the path in the filedirectory that you defined under Error! Reference source not found.. In the case of thesender communication channel, enter the whole path for the file directoryXiPattern6.




14. Following the same procedure, create the communication channelXiPatternChannel_XIReceiver(communication component

_PI_FileSystem_XiPattern7 ) using the template

XiPatternChannel_XIReceiver. Enter the URL to the Integration Server as Target URL(for example http://:/sap/xi/engine?type=entry). As User Name set

PIAPPLUSER(or a copy of the PIAPPLUSER) with the respective User Passwordin the

Integration Server Client, in field Logon Clientset the client of the integration server (e.g.001).








4. Select the communication component _AAEX_FileSystem_XiPattern6 and

chooseApply.5. In the fields Interfaceand Namespaceenter XiPatternInterface1and



6. UnderAdd to ScenarioselectXiPatternOneStepScenario_AAEX_PI(input help).

7. Choose Create.


XiPatternChannel_FileSender. For the software component version of sender



33/47


January 2011 33


_PI_FileSystem_XiPattern7 .

10. In tab Receiver Interfacesfor name and namespace enter XiPatternInterface1and

http://sap.com/xi/XI/System/Patterns , respectively. In Software Component

Version set SAP BASIS 7.30.


11. In the tab Outbound Processingselect the communication channe

Documents

SAP NetWeaver Process Integration 7.3 - Simple Use Cases for Advanced Adapter Engine Extended (1)