SAP NetWeaver Process Integration 7.3 - Simple Use Cases For Advanced Adapter Engine Extended PDF

SAP NetWeaver 7.
30
SAP NetWeaver
Process Integration
Simple Use Cases for
Advanced Adapter
Engine Extended (AEX)
Document Version 2.0 – January 2011
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 24
F +49/18 05/34 34 20
www.sap.com
© Copyright 2011 SAP AG. All rights reserved. MaxDB is a trademark of MySQL AB, Sweden.
No part of this publication may be reproduced or transmitted in SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver,
any form or for any purpose without the express permission of and other SAP products and services mentioned herein as well
SAP AG. The information contained herein may be changed as their respective logos are trademarks or registered
without prior notice. trademarks of SAP AG in Germany and in several other
countries all over the world. All other product and service names
Some software products marketed by SAP AG and its mentioned are the trademarks of their respective companies.
distributors contain proprietary software components of other Data contained in this document serves informational purposes
software vendors. only. National product specifications may vary.
Microsoft, Windows, Outlook, and PowerPoint are registered These materials are subject to change without notice. These
trademarks of Microsoft Corporation. materials are provided by SAP AG and its affiliated companies
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, ("SAP Group") for informational purposes only, without
MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, representation or warranty of any kind, and SAP Group shall not
pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, be liable for errors or omissions with respect to the materials.
WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, The only warranties for SAP Group products and services are
POWER5, OpenPower and PowerPC are trademarks or those that are set forth in the express warranty statements
registered trademarks of IBM Corporation. accompanying such products and services, if any. Nothing
herein should be construed as constituting an additional
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are warranty.
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. Disclaimer
Some components of this product are based on Java™. Any
UNIX, X/Open, OSF/1, and Motif are registered trademarks of code change in these components may cause unpredictable
the Open Group. and severe malfunctions and is therefore expressively
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, prohibited, as is any decompilation of these components.
VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc. Any Java™ Source Code delivered with this product is only to
be used by SAP’s Support Services and may not be modified or
HTML, XML, XHTML and W3C are trademarks or registered altered in any way.
trademarks of W3C®, World Wide Web Consortium,
Massachusetts Institute of Technology.
Documentation in SAP Developer Network (SDN)
Java is a registered trademark of Sun Microsystems, Inc. You can find this documentation in SAP Developer Network
(SDN) at
JavaScript is a registered trademark of Sun Microsystems, Inc., https://www.sdn.sap.com/irj/sdn/nw-soa 
used under license for technology invented and implemented by Service Bus  Getting Started.
Netscape.
SAP NetWeaver 7.30 – Advanced Adapter Engine Extended Simple Use Cases
1 Preface ........................................................................................5
2 Introduction and Prerequisites ..................................................5
2.1 Introduction .............................................................................................. 5
2.2 Prerequisites............................................................................................ 7
2.2.1 General Prerequisites ................................................................................................... 7
2.2.2 Providing the necessary User and Authorizations ....................................................... 8
2.2.3 Setting Up the File Directories ...................................................................................... 8
2.2.4 Creating the Technical and Business Systems in the System Landscape
Directory of the Advanced Adapter Engine Extended .............................................................. 9
2.2.5 Creating the Technical and Business Systems in the System Landscape
Directory of the PI System ...................................................................................................... 11
2.2.6 Defining Business System Components in the Integration Directory in the
Advanced Adapter Engine Extended ..................................................................................... 13
2.2.7 Defining Business System Components in the Integration Directory in the PI
System14
2.3 Design Objects Used ............................................................................. 15
3 Variant 1: One Sender and One Receiver using the
Advanced Adapter Engine Extended ............................................16
3.1 Configuring the Process Integration Scenario ....................................... 17
3.2 Executing the Use Case ........................................................................ 19
4 Variant 2: One Sender and Two Receivers using Advanced
Adapter Engine Extended..............................................................20
Adapter Engine Extended – with Routing Condition ...................22
Adapter Engine Extended – With Mapping...................................23
Adapter Engine Extended - with XML-Validation .........................25
January 2011 3
7.3 Execution ............................................................................................... 26

8 Variant 6: One Sender and One Receiver using Advanced
Adapter Engine Extended - using Exactly Once In Order ...........27
8.3 Execution ............................................................................................... 29
9 Variant 7: One Sender and One Receiver using
communication between Advanced Adapter Engine Extended
and PI ..............................................................................................30
9.1 Configuring the Process Integration Scenario in the Advanced
Adapter Engine Extended............................................................................... 30
9.1.1 Design Objects Used .................................................................................................. 30
9.1.2 Configuring the scenario on the Advanced Adapter Engine Extended in
Integration Directory ............................................................................................................... 31
9.2 Configuring the Process Integration Scenario in the PI System ............ 33
9.2.1 Design Objects Used .................................................................................................. 33
9.2.2 Configuring the scenario in the PI System ................................................................. 36
10 Variant 8: One Sender and One Receiver using
communication between Advanced Adapter Engine Extended
and PI System - using Exactly Once In Order ..............................39
10.1 Configuring the Process Integration Scenario in the Advanced
Adapter Engine Extended............................................................................... 40
10.1.1 Design Objects Used ...................................................................................... 40
10.1.2 Configuring the scenario on the Advanced Adapter Engine Extended in
Integration Directory ............................................................................................................... 40
10.2 Configuring the Process Integration Scenario in the PI System ......... 42
10.2.1 Design Objects Used ...................................................................................... 42
10.2.2 Configuring the Process Integration Scenario in the PI System .................... 43
10.3 Execution ........................................................................................... 45
11 Appendix .................................................................................46
11.1 Monitoring Tools ................................................................................. 46
11.1.1 Monitoring in Runtime Workbench in the PI System ...................................... 46
11.1.2 Transaction SXMB_MONI in the PI System ................................................... 46
11.1.3 Monitoring in Solution Manager ...................................................................... 47
4 January 2011
1 Preface
Constraints
The texts, references, and graphics contained in this manual have been compiled with utmost
care; nevertheless, it is impossible to guarantee that they are fully without error. SAP cannot
assume any responsibility for the correctness or completeness of the following
documentation; the user alone is responsible for verifying the information contained therein.
SAP will only assume liability for damage arising from the use of this documentation –
irrespective of the pertinent legal basis – in the case of intentional or active negligence, under
no other circumstances will a warranty be made.
Definition
This manual describes simple application cases for the Extended adapter engine for process
integration and all the configuration steps that are necessary to execute the application cases
on 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 run
the use cases.
Additional Documentation
List of related documentation
Documentation Purpose
SAP NetWeaver Library Introduction to demo examples and description of the

documentation: Demo process integration scenarios
Examples
SAP NetWeaver Introduction to Simple Use Cases and description of the

Documentation Simple Use simple use case scenarios for Process Integration
Cases
Configuration of SAP Configuring usage type Advanced Adapter Engine

NetWeaver Process Extended ??
Integration
This document is updated on a regular basis in SAP Developer Network (SDN) at
https://www.sdn.sap.com/irj/sdn/nw-soa  Service 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 of
Advanced Adapter Engine Extended. These instructions will enable you to understand,
configure, and execute simple scenarios (that are based on fundamental communication
patterns), as well as check that the scenarios are executed correctly. The prerequisite for this
document 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 at
present:
January 2011 5
Variant Description
Variants 1, 6, 7 and 8: Represents message exchange between one sender and
one receiver on the Advanced Adapter Engine Extended.
One sender and one receiver
The message processing is done locally on the Advanced
(see 3, 8, 9 and 10)
Adapter Engine Extended.
Variant 6 is executed using EOIO protocol.
Variant 7 is executed between one sender on the Advanced
Adapter Engine Extended and one receiver on the PI
Integration Server.
Variant 8 is executed between one sender on the Advanced
Adapter Engine Extended and one receiver on the PI
Integration Server using EOIO protocol.
Variant 2: Represents message exchange between one sender and
two receivers. The message processing is done locally on
One sender and two
the Advanced Adapter Engine Extended..
receivers (see 4),
two receivers in which the way the message is forwarded to
One sender and two
the receivers is determined by routing conditions The
receivers – with routing
message processing is done locally on the Advanced
condition (see 5)
two receivers. A mapping is executed when the message is
One sender and two
forwarded to one of the two receivers. The message
receivers – with mapping
processing and mapping are done locally on the Advanced
(see 6)
two receivers. A mapping is executed when the message is
One sender and two
forwarded to one of the two receivers. The payload is
receivers – with XML-
validated using XML-Validation in inbound processing of the
Validation (see 7)
adapter engine. The message processing, mapping and
XML validation are done locally on the Advanced Adapter
Engine Extended.
You can aim to learn about the following with the use cases:
 Working with the Enterprise Services Builder – Enterprise Services Repository:
Understanding existing design objects
 Working with the Integration Builder – Integration Directory: Configuring simple scenarios
and understanding created configuration objects
 Working with the runtime: Executing the use cases and checking the results by using
monitoring
SAP provides the required design objects and files for these learning targets. This document
contains a complete set of instructions that enable you to configure and execute the use
cases 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 the
information under 2.2.1.
Within the scenarios file directories on the host of the SAP system on which the Advanced
Adapter Engine Extended and the Integration Server is installed serve as the senders and
6 January 2011
receivers of messages. The use cases rely on file directories (and therefore the file/FTP
adapter) 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 receiver
adapter 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 the
ABAP Integration Server. In variant 8 the messages are processed in sequence.
This document assumes that you will configure the variants in succession, in the order
specified. While it is technically possible to configure the variants in a different order, doing so
would mean that the order of the step-by-step instructions in this document would no longer
be 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 with
configuration. You can then return to the skipped chapters at a later stage for a
better 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 Process
Integration and Advanced Adapter Engine Extended must be correctly installed and
configured. The following table lists the prerequisites and the relevant guides:
List of required steps
Step Documentation
1. You have installed the Advanced Adapter Engine Master Guide – SAP NetWeaver
Extended and SAP NetWeaver 7.30.
Installation Guide – SAP Web AS
ABAP and Java
You can find the corresponding guides

on SAP Service Marketplace in the
Implementation Documentation Center
for SAP NetWeaver Process
Integration 7.3
2. You have imported the content for the Enterprise SAP Note 836200
Services Repository corresponding to the latest
support package/patch into the PI and the
Advanced Adapter Engine Extended System.
The simple use cases are
located in the Enterprise
Services Repository in
the software component
SAP BASIS, software
component version SAP
BASIS 7.30, in the
namespaces
http://sap.com/xi/XI/Syste
m/Patterns.
January 2011 7
3. You have configured the Advanced Adapter Engine Configuration of SAP NetWeaver
Extended and SAP NetWeaver Process Process Integration
Integration.
4. You have configured the System Landscape Configuring, Working with and
Directory (SLD) for the PI and the Advanced Administering System Landscape
Adapter Engine Extended System. Directory
Note that you set up the use cases in your development or test system, but not
in 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 user
XIDEMO with the following roles in the integration server client (001) and in 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 different
file 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 be
able to configure the use cases, the file directories must have been created and described in
the System Landscape Directory. Only then can you access the directories during
configuration in the Integration Directory.
Perform the steps below to create the required directories on the host of the SAP system on
which the Advanced Adapter Engine Extended is installed.
1. Open the file directory of the SAP system, on which the Advanced Adapter Engine
Extended 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 this
purpose 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 the
process integration scenario. Bear this in mind when you define the directory,
and, if applicable, contact your system administrator.
8 January 2011
5. Copy the following three files to directories XiPattern1 and XiPattern6

 ZXiPatternSenderFile1.xml
 ZXiPatternSenderFile2.xml
 ZXIPatternSenderFile3.xml
6. Copy the following file to directories XiPattern4 and XiPattern8
 XiPatternSenderFilesEOIO.zip (This file contains 1000 xml files for the EOIO
scenario, they will be unpacked when executing the scenario.)
These files are provided by SAP in a ZIP file. The ZIP file is located in SAP
Developer Network (SDN) at https://www.sdn.sap.com/irj/sdn/nw-soa 
Service Bus. On the page Service Bus-Based Integration select Getting
Started. On the page Getting Started With Service Bus-Based Integration select
the hyperlink Process Integration – Simple Use Cases – Test Files.
As long as the SDN page is not updated for PI 7.30 the zip File for 7.30
containing 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 on
which the Integration Server is installed. These directories are necessary for Variants 7 and
8.
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 directories
XiPatterns_AAEX and XiPatternsO_AAEX in it.
A work directory already exists on many computers that can be used for this
purpose 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 the
process 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 the

System Landscape Directory of the Advanced
Adapter Engine Extended
Perform the following steps to create the required technical and business systems in the
System Landscape Directory (SLD) for the Advanced Adapter Engine Extended:
January 2011 9
1. To call the System Landscape Directory for the Advanced Adapter Engine Extended
System, open the Advanced Adapter Engine Extended Start Page using the URL:
http://<AEX-Host>:<AEX-Port>/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 in 2.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 Details screen, enter the following information
about the technical system:
 Technical System Identification: Enter a name according to the following naming
convention: <SID>_FileSystem. In this case, <SID> is the system ID of the
Advanced Adapter Engine Extended.
 System Host Name: Enter the host name of the Advanced Adapter Engine
Extended, for example pwdf2638.
9. Choose Finish.
10. Now create seven new business systems. To create the first business system, on the
SLD 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 you
defined previously (dropdown list box in field System).
15. Choose Next.
16. Enter the name <SID>_AAEX_FileSystem_XiPattern1. <SID> 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 (field
Related Integration Server).
19. Choose Finish.
20. Following the same procedure, create business systems with the following names:
 <SID>_AAEX_FileSystem_XiPattern2
Create two more technical systems for the file system of the integration server for variants 7
and 8.
1. To do so, choose New Technical System.
10 January 2011

3. Choose Next.
convention: <SID>_FileSystem. In this case, <SID> is the system ID of the PI
System.
 System Host Name: Enter the host name of the PI System, for example pwdf2638.
5. Choose Finish.
6. Now create two new business systems using this Technical System. To create the first
business 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 <SID>_PI_FileSystem_XiPattern7. <SID> is the system ID of the
PI Integration Server.
13. Choose Next.
14. Specify the Advanced Adapter Engine Extended System as Integration Server (field
Related Integration Server).
15. Choose Finish.
16. Following the same procedure, create another business system with the name
<SID>_PI_FileSystem_XiPattern9.
2.2.5 Creating the Technical and Business Systems in the

System Landscape Directory of the PI System
Perform the following steps to create the required technical and business systems in the
System Landscape Directory (SLD) for the PI System. These steps are necessary for the
Variants 7 and 8.
1. To call the System Landscape Directory, in the SAP menu in the PI Integration Server
choose Process Integration  Start Integration Builder in the user menu.
2. Start the SLD. To do so, on the Process Integration start page, choose System
Landscape Directory.
3. Log on using the XIDEMO user you created in 2.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.
January 2011 11

convention: <SID>_FileSystem. In this case, <SID> is the system ID of the PI
Integration Server.
 System Host Name: Enter the host name of the PI Integration Server, for example
pwdf2638.
9. Choose Finish.
10. Now create two new business systems. To create the first business system, on the SLD
start page, choose Business Systems.
13. Choose Next.
14. Select the technical system of the PI system that you defined previously (dropdown list
box in field System).
15. Choose Next.
16. Enter the name <SID>_PI_FileSystem_XiPattern7. <SID> 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
To enable the communicating between Advanced Adapter Engine Extended and the PI
System create a new technical system.
1. To do so, choose New Technical System.
3. Choose Next.
convention: <SID>_FileSystem. In this case, <SID> is the system ID of the
Advanced Adapter Engine Extended.
 System Host Name: Enter the host name of the Advanced Adapter Engine
Extended, for example pwdf2638.
5. Choose Finish.
6. Now create two new business systems. To create the first business system, on the SLD
start page, choose Business Systems.
9. Choose Next.
10. Select the technical system of the Advanced Adapter Engine Extended system that you
just defined (dropdown list box in field System).
11. Choose Next.
12. Enter the name <SID>_AAEX_FileSystem_XiPattern6. <SID> is the system ID of
the Advanced Adapter Engine Extended System.
12 January 2011
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
<SID>_AAEX_FileSystem_XiPattern8.
2.2.6 Defining Business System Components in the

Integration Directory in the Advanced Adapter
Engine Extended
In the following steps you define communication components for the business systems you
just created in the Advanced Adapter Engine Extended. You need to create communication
components to be able to address the business systems as senders/receivers of messages
when 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 of
messages.
 Define communication channels for outbound message processing (for all relevant
receiver business systems)
You define communication components in the Integration Directory of the Advanced Adapter
Engine Extended.
Therefore, to execute the activities described below, call the Integration Builder (user
interface 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://<AEX-
Host>:<AEX-Port>/dir.
2. On the Advanced Adapter Engine Extended Start Page, choose the hyperlink Integration
Builder (under Integration Directory).
3. Log on using the XIDEMO user you created in 2.2.2. The system opens the Integration
Builder.
You use the steps below to define a communication component (business system
component) in the Integration Directory for each business system.
1. Clear the SLD cache. To do this, select Environment  Clear SLD Data Cache in the
menu of the Integration Builder.
2. In the Integration Builder navigation area, on the Objects tab page, position the cursor on
the Communication Components Without Party node.
3. To call the wizard for assigning business systems, choose Assign Business System in
the 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 corresponding
checkboxes:
January 2011 13
 <SID>_PI_FileSystem_XiPattern7
6. Make sure that the checkbox Create Communication Channels for Following Adapters is
deselected.
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 navigation
area, on the Objects tab 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 Open  Standard Change List.
3. Check that the five communication components you just created are contained in the
change list.
4. Position the cursor on the Standard Change List node and choose Activate ( ) in the
context menu.
2.2.7 Defining Business System Components in the

Integration Directory in the PI System
In the following steps you define communication components on the PI system for the
business systems you just created. You need to create communication components to be
able to address the business systems as senders/receivers of messages when you configure
the process integration scenario in the Integration Directory. For Variants 7 and 8 the
communication components need to be known in the Advanced Adapter Engine Extended
and 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 (business
system components) in the Integration Directory
Only then can you address the business systems as senders or receivers of
messages.
 Define communication channels for outbound message processing (for all relevant
receiver 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 Integration  Start Integration Builder in the user menu.
14 January 2011
5. On the initial screen, choose the hyperlink Integration Builder (under Integration
Directory).
6. Log on using the XIDEMO user you created in 2.2.2. The system opens the Integration
Builder.
You use the steps below to define a communication component (business system
component) in the Integration Directory for each business system.
1. Clear the SLD cache. To do this, select Environment  Clear SLD Data Cache in the
menu of the Integration Builder.
2. In the Integration Builder navigation area, on the Objects tab page, position the cursor on
the Communication Components Without Party node.
3. To call the wizard for assigning business systems, choose Assign Business System in
the 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 corresponding
checkboxes:
7. Make sure that the checkbox Create Communication Channels for Following Adapters is
deselected.
The relevant communication channels are created when the process integration
scenario is configured.
8. Choose Finish.
The system displays the communication components in the Integration Builder navigation
area, on the Objects tab 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 the
change list.
context menu.
2.3 Design Objects Used
This section explains all the design objects that are used for describing the
variants.
January 2011 15
The subsequent description of each variant will refer to the description in this
section; 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 the
process flow at which messages are exchanged between application components (in this
case, the application components Sender and Receiver). Component View
File2File_NoMapping represents the variant with message exchange between Advanced
Adapter Engine Extended and the PI System, whereas the Component View
File2File_NoMapping_InOrder represents the variant with message exchange in EOIO. The
variants only running locally in the Advanced Adapter Engine Extended are not based on
component 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 the
process integration scenario was defined, for the inbound or outbound processing of the
message. You can then use the communication channel template to create the
corresponding communication channel when configuring in the Integration Directory. You
then need to specify all the details, which are only known at configuration time, in the
communication channel.
The specific design objects will be listed in the specific variants below.
3 Variant 1: One Sender and One Receiver

using the Advanced Adapter Engine
Extended
This variant enables you to configure and execute the simplest kind of message exchange:
One sender (file directory XiPattern1) sends a message to one receiver (file directory
XiPattern2). Hereby, the message is exchanged between sender and receiver adapter by
using one Advanced Adapter Engine Extended. No mapping is executed between the
outbound 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
16 January 2011
Service Interface Specifies the communication mode (asynchronous) and references

(XiPatternInterface1) the message type used.
Message Type Describes the message sent at runtime and references the data type
(XiPattermMessage1) used.
Data Type (XiPatternDataType1) Describes the data structure of the message
Communication Channel Templates Specifies the sender (and receiver) adapter configuration details,
for Sender and Receiver which are defined at design time. Communication channel templates
(XiPatternChannel_FileSender, enable a communication channel to be preconfigured at design time.
XiPatternChannel_FileReceiver)
3.1 Configuring the Process Integration Scenario

You 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, see Defining the Integrated Configuration.
Calling the Integration Directory

First, call the Integration Directory. To call the Integration Directory for the Advanced Adapter
Engine Extended System, open the Advanced Adapter Engine Extended Start Page using
the URL: http://<AEX-Host>:<AEX-Port>/dir.
Creating a Configuration Scenario

Perform the following steps to create a configuration scenario to group the configuration
objects.
1. In the Integration Directory main menu, choose Object  New.
2. Under Administration select 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 Profile select Communication Channel.
3. Call the input help ( ) for the Communication Component.

4. Select the communication component <SID>_AAEX_FileSystem_XiPattern1 and
choose Apply.
5. In field Communication Channel enter XiPatternChannel_FileSender.
6. Under Add to Scenario select XiPatternOneStepScenario_AAEX (input help).
January 2011 17
7. Choose Create.
The newly created communication channel is opened.
8. In the menu of the communication channel object editor select Communication
Channel  Apply Template.
9. Select the template XiPatternChannel_FileSender.
10. Choose Apply.
11. Under File Access Parameter in the Source Directory field, enter the path in the file
directory that you defined under 2.2.3. In the case of the sender communication
channel, enter the whole path for the file directory XiPattern1.
Example: C:/<selected path>/XiPatterns_AAEX/XiPattern1

12. In the field Adapter Engine select the central adapter engine.
13. Save the communication channel.
14. Following the same procedure, create the communication channel
XiPatternChannel_FileReceiver (communication component
<SID>_AAEX_FileSystem_XiPattern2) using the template
XiPatternChannel_FileReceiver. Select the central adapter engine and enter the path
for the file directory XiPattern2.
If there already is an entry for the communication component in the Create

Communication Component screen delete it before calling the input help.
Otherwise the input help may not provide the component
16. Save the scenario.
17. Activate the change list.
Creating the Integrated Configuration

2. Under Collaboration Agreement select Integrated Configuration.
3. Call the input help ( ) in the field Communication Component.

4. Select the communication component <SID>_AAEX_FileSystem_XiPattern1
and choose Apply.
5. In the fields Interface and Namespace enter XiPatternInterface1 and
http://sap.com/xi/XI/System/Patterns, respectively.
The input help may not show the interface and namespace. Create the entry
manually or choose Category Any in the F4 Help.
7. Choose Create.
8. In tab Inbound Processing select the communication channel
XiPatternChannel_FileSender. For the software component version of sender
interface select SAP BASIS 7.30.
18 January 2011
9. In the tab Receiver select the communication component

10. In tab Receiver Interfaces for name and namespace enter XiPatternInterface1
and http://sap.com/xi/XI/System/Patterns, respectively. In Software
Component Version set SAP BASIS 7.30.
manually.
11. In the tab Outbound Processing select the communication channel
XiPatternChannel_FileReceiver.
12. Save the integrated configuration.
13. Save the Configuration Scenario.
Activating the Change List

1. To do this, select the Change Lists tab in the Integration Directory navigation area.
3. Position the cursor on the Standard Change List node and choose Activate ( )) 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 file ZXiPatternSenderFile1.xml as
XiPatternSenderFile1.xml.
The File/FTP adapter is designed in a way that a file with exactly this name is
recognized and moved from the source directory XiPattern1 to the target directory
XiPattern2 every 60 seconds. If the configuration was executed without errors, the file
will be moved from the source directory within 60 seconds after it is renamed.
3. Open the directory XiPattern2 and check that the file has arrived.
4. Open the file and check whether the content has changed (compare with the original
file 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 the
Advanced 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 (for
example, the processing period).
5. Choose Go.
The system displays the selected messages in a table. You want to locate the
messages that were sent during execution.
January 2011 19
6. Select the message to be displayed by selecting the appropriate radio button and
then choose Open Message.
The tab Payloads displays the message contents for the various versions of the
message during processing.
4 Variant 2: One Sender and Two Receivers

using Advanced Adapter Engine Extended
This variant extends variant 1 by adding an additional receiver. The message is sent from the
sender to two receivers using the Advanced Adapter Engine Extended, without a mapping
being executed at runtime.
One sender (file directory XiPattern1) sends a message to two receivers (file directory
XiPattern2 and XiPattern3 ). The message is exchanged between sender and receiver
adapter 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 integration
scenario exists for this variant.

When you configure this variant, you will extend the configuration settings from variant 1. You
use the same configuration scenario XiPatternOneStepScenario_AAEX as in variant 1.
Opening the Configuration Scenario

In this variant, the configuration scenario XiPatternOneStepScenario_AAEX created in
variant 1 is extended.
The integrated configuration object is used again for configuration for this scenario. The
model 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.

choose Apply.
5. In field Communication Channel enter XiPatternChannel_FileReceiver.
7. Choose Create.
20 January 2011
8. In the menu of the communication channel object editor, select Communication

9. Select the template XiPatternChannel_FileReceiver.
10. Choose Apply.
11. Under File Access Parameters in the Target Directory field, enter the path in the file
directory that you defined under Error! Reference source not found.. In the case of
the sender communication channel, enter the whole path for the file directory
XiPattern3.

Changing the Integrated Configuration

1. In the Integration Directory main menu, open the Integrated Configuration Object
<SID>_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 and additionally select the communication
component <SID>_AAEX_FileSystem_XiPattern3.
4. In tab Receiver Interfaces select the line for the communication component
<SID>_AAEX_FileSystem_XiPattern3. In the table Receiver Interfaces and
Mappings for name and namespace enter XiPatternInterface1 and
http://sap.com/xi/XI/System/Patterns, respectively. In Software
manually.
5. In the tab Outbound Processing select the line for the communication component
<SID>_AAEX_FileSystem_XiPattern3. In the table Configuration select the
communication channel XiPatternChannel_FileReceiver.

the context menu.

You perform the following steps to check that the process integration scenario is executed
without errors.
January 2011 21
As for the execution of variant 1, in directory XiPattern1, copy the file

ZXiPatternSenderFile1.xml and rename it XiPatternSenderFile1.xml. The file will be moved
from the directory within the next 60 seconds.
Since this variant has two target directories (receivers), check in both directory XiPattern2
and XiPattern3, 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 will
display two messages, one for each of the receivers.
In this variant, two messages are created from the outbound message (one for
each receiver).

using Advanced Adapter Engine Extended –
with Routing Condition
This variant extends variant 2 by adding a routing condition. Depending on the condition, the
message is sent to one of the two receivers.

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

When you configure this variant, you will extend the configuration settings from variant 1 and
2. You use the same configuration scenario XiPatternOneStepScenario_AAEX.
Using the Configuration Scenario

In this variant, the configuration scenario XiPatternOneStepScenario_AAEX created in
variants 1 and 2 is extended.
For this scenario, again the integrated configuration object is used for configuration. The
model configurator is not used in this case.

1. In the Integration Directory main menu, open the integrated configuration object
http://sap.com/xi/XI/System/Patterns
3. In tab Receiver, select the cell for the receiver component
<SID>_AAEX_FileSystem_XiPattern2 in 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 the XPath radio button.
22 January 2011
The data structure of the message is displayed.

7. Expand the structure and select the element CountryCode by 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 US entered for the element
CountryCode are sent to receiver <SID>_AAEX_FileSystem_XiPattern2.
12. Following this procedure, create the routing condition CountryCode = DE for the
configured receiver <SID>_AAEX_FileSystem_XiPattern3.

the context menu.

without errors.
In directory XiPattern1, copy the file ZXiPatternSenderFile1.xml and rename the copied file
XiPatternSenderFile1.xml. The file will be moved from the directory within the next 60
seconds.
Check whether the file has arrived in directory XiPattern2. Open the file and check that the
country code US is entered in the personal data.
There should be no file in directory XiPattern3.
Message monitoring contains one entry for this exchange of messages.
You can repeat this procedure for file ZXiPatternSenderFile2.xml. This file
should arrive in directory XiPattern3 (contains personal data with the country
code DE).

using 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.
January 2011 23

Mapping Objects
The mapping XiPatternInterface1ToInterface2 is executed between the sender and receiver
data structure for receiver <SID>_AAEX_FileSystem_XiPattern3 during message exchange.

use the same configuration scenario XiPatternOneStepScenario_AAEX.
Using the Configuration Scenario

In this variant the configuration scenario XiPatternOneStepScenario_AAEX created in variant
1 and extended in variants 2 and 3 is extended to use a mapping for one of the receivers.
model configurator is not used.

3. In tab Receiver Interfaces select the line for the communication component
<SID>_AAEX_FileSystem_XiPattern3. In table Receiver Interfaces for
mapping select the mapping XiPatternInterface1ToInterface2 from software
component version SAP BASIS 7.30.
4. In tab Outbound Processing, select the line for the communication component
<SID>_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.

the context menu.

without errors.
In directory XiPattern1, copy the file ZXiPatternSenderFile2.xml. Rename the file to
seconds.
24 January 2011
Check whether a file has arrived in directory XiPattern3. Open the file. The structure will have
changed: the first and the second name of the person have been concatenated; the field for
the 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 is
expected in directory XiPattern2 (no mapping executed).

using 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 Advanced
Adapter Engine Extended if the schema is correct, the file will not be picked up if the structure
does not fit.


use the same configuration scenario XiPatternOneStepScenario_AAEX.
Opening the Configuration Scenario

In this variant the configuration scenario XiPatternOneStepScenario_AAEX created in variant
1 and extended in variants 2 to 4 is extended to use XML-Validation to check the structure of
the message.
model configurator is not used.

3. In tab Inbound Processing for Schema Validation select the radio button Validation by
Adapter.
4. Save the Integrated configuration.

the context menu.
January 2011 25
7.3 Execution
without errors.
Execution without Validation Error

For the execution in directory XiPattern1, rename the file ZXiPatternSenderFile1.xml to
seconds.
Check in directory XiPattern2 whether the file has arrived.
proceed as follows:
1. Start the Monitoring by choosing Configuration and Monitoring Home on the Process
Integration start page.
3. Select Database.
5. Choose Go.
then choose Open Message.
Message monitoring displays one message.
Execution with Validation Error

For the execution with wrong XML schema in directory XiPattern1, rename the file
ZXiPatternSenderFile3.xml to XiPatternSenderFile3.xml. The file will not be moved from the
directory within the next 60 seconds. No file should arrive in directory XiPattern2. The
message-processing will not process the message because the message has the wrong
XML-schema. If you check the XML file ZXiPatternSenderFile3.xml, you will see a tag with
the name Email, this tag does not exist in the message type XiPatternMessage1 used in the
outbound interface XiPatternInterface1.
You cannot see the error in message monitoring because the adapter engine does not create
a message out of the file because of the wrong structure. You can only see the error in
channel monitoring. To do this, proceed as follows:
1. Start the Monitoring by choosing Configuration and Monitoring Home on the Process
Integration start page.
2. Select Adapter Engine  Communication Channel Monitoring.
3. Use the Link Advanced to get additional selection fields.
4. Set XiPatternChannel_FileSender as channel name and
<SID>_AAEX_FileSystem_XiPattern1 as communication component to get only the
channel used for this variant.
5. Choose Go.
26 January 2011
The system displays the channel used for picking up the files from the sender
directory. You will see that the channel is in error state because the XML-Validation
found an error in the structure of the payload.
To end the processing delete the file XiPatternSenderFile3.xml from the directory.

using Advanced Adapter Engine Extended -
using Exactly Once In Order
one sender on the Advanced Adapter Engine Extended (file directory XiPatterns4) sends a
series of messages to one receiver on the Advanced Adapter Engine Extended (file directory
XiPatterns5). No mapping is executed between the outbound and inbound interface in this
variant. The messages are delivered in some particular order. Concretely, the file adapter
allows 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 no
mapping is required, the service interfaces XiPatternInterface1O is used for sender and
receiver

The following table summarizes the design objects used.
Design Objects Used
Component View Describes the process flow and the message exchange for this
File2File_NoMapping_InOrder (Process variant.
Integration Scenario
XiPatternOneStepScenario)
Service interface (XiPatternInterface1O) Describes the interface and data structure of the sender and
receiver. The data structure is the same for sender and
Message Type (XiPatternMessage1)
receiver.
Data Type (XiPatternDataType1)

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

objects.
January 2011 27
3. Enter the name XiPatternOneStepScenario_AAEX_EOIO.

4. Choose Create.


choose Apply.
6. Under Add to Scenario select XiPatternOneStepScenario_AAEX_EOIO (input
help).
7. Choose Create.
8. In the menu of the communication channel object editor select Communication
9. Select the template XiPatternChannel_FileSenderO.
10. Choose Apply.
directory that you defined under Error! Reference source not found.. In the case of
the sender communication channel, enter the whole path for the file directory
XiPattern4.
Example: C:/<selected path>/XiPatternsO_AAEX/XiPattern4

XiPatternChannel_FileReceiver (communication component
<SID>_AAEX_FileSystem_XiPattern5) using the template
XiPatternChannel_FileReceiverO. Select the central adapter engine and enter the
path for the file directory XiPattern5.
If there already is an entry for the communication component in the Create

Communication Component screen delete it before calling the input help.
Otherwise the input help may not provide the component
28 January 2011


4. Select the communication component <SID>_AAEX_FileSystem_XiPattern4
and choose Apply.
6. Under Add to Scenario select XiPatternOneStepScenario_AAEX_EOIO (input help).
7. Choose Create.
10. In tab Receiver Interfaces for name and namespace enter XiPatternInterface1
and http://sap.com/xi/XI/System/Patterns, respectively. In Software
manually.

the context menu.
8.3 Execution
without errors.
1. Stop the channel <SID>_AAEX_FileSystem_XiPattern4 | XiPatternChannel_FileSender
in the Configuration and Monitoring Home  Adapter Engine  Communication Channel
Monitoring to make sure no processing runs during the time the files are placed into the
source folder.
January 2011 29
2. On the host of the Advanced Adapter Engine Extended open the file directory
XiPatternsO_AAEX/XiPatterns5. If the output file XiPatternReceiverFile.txt is already
present, delete this file. The execution of this test will create this file if it is not present and
append a series of output files to this file.
3. Open the file directory XiPatternsO_AAEX/XiPatterns4
4. Unpack file XiPatternSenderFilesEOIO.zip in the current directory. This will place a series
of input files XiPatternSenderFile00001.xml, …, XiPatternSenderFile01000.xml.
The File/FTP adapter is configured so that the files are picked in the order sorted by the
file names and moved from the source directory XiPatterns4 to the target directory
XiPatterns5 and the files are concatenated into a single file XiPatternReceiverFile.txt.
5. Start the channel <SID>_AAEX_FileSystem_XiPattern4 | XiPatternChannel_FileSender
in the Configuration and Monitoring Home  Adapter Engine  Communication Channel
Monitoring to start processing the files.
6. Open the directory XiPatternsO_AAEX/XiPatterns5 and check that the files have been
transferred.
7. Open the XML file XiPatternReceiverFileAll.xml which includes the output file and check
whether the content is in the correct order.
The content must be in the correct order with the incremental ID value and the entire
content must be present.
8. Furthermore, you can check the processing of the messages in the message monitoring
as in Variant 1.

using communication between Advanced
Adapter Engine Extended and PI
One sender (file directory XiPattern1) sends a message to one receiver (file directory
XiPattern2). Hereby, the message is exchanged between a sender file adapter on the
Advanced Adapter Engine Extended and a receiver file adapter on the PI system. No
mapping 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
Design Objects Used
30 January 2011

XiPatternChannel_XiReceiver,
9.1.2 Configuring the scenario on the Advanced Adapter

Engine Extended in Integration Directory


objects.
3. Enter the name XiPatternOneStepScenario_AAEX_PI.
4. Choose Create.


4. Select the communication component <SID>_AAEX_FileSystem_XiPattern6 and choose
Apply.
January 2011 31
6. Under Add to Scenario select XiPatternOneStepScenario_AAEX_PI (input help).

7. Choose Create.
8. In the menu of the communication channel object editor select Communication Channel
 Apply Template.
9. Select the template XiPatternChannel_FileSender.
10. Choose Apply.
directory that you defined under Error! Reference source not found.. In the case of the
sender communication channel, enter the whole path for the file directory XiPattern6.

XiPatternChannel_XIReceiver (communication component
<SID>_PI_FileSystem_XiPattern7) using the template
XiPatternChannel_XIReceiver. Enter the URL to the Integration Server as Target URL
(for example http://<PI-host>:<PI-port>/sap/xi/engine?type=entry). As User Name set
PIAPPLUSER (or a copy of the PIAPPLUSER) with the respective User Password in the
Integration Server Client, in field Logon Client set the client of the integration server (e.g.
001).


choose Apply.
6. Under Add to Scenario select XiPatternOneStepScenario_AAEX_PI (input help).
7. Choose Create.
32 January 2011

10. In tab Receiver Interfaces for name and namespace enter XiPatternInterface1 and
http://sap.com/xi/XI/System/Patterns, respectively. In Software Component
Version set SAP BASIS 7.30.
manually.
XiPatternChannel_XIReceiver.

3. Position the cursor on the Standard Change List node and choose Activate ( )) in the
context menu.

the PI System
To enable message flow between the Advanced Adapter Engine Extended and the PI
System you also need to do the configuration in the PI System.
This section explains all the design objects that are used for describing this
variant. There is a step-by-step description of how to access each object. SAP
recommends that you follow these steps directly in the system.
You use the component view File2File_NoMapping in process integration scenario
XiPatternOneStepScenario to configure this variant in the PI System. The following graphic
shows the component view:
January 2011 33
The following describes all the objects that describe the message exchange in this variant in
turn. Starting with the process integration scenario (component view), you can open all the
objects that the component view uses.
1. To call the Enterprise Services Builder (user interface of the Enterprise Services
Repository), choose Process Integration  Start Integration Builder in the user menu.
2. On the Process Integration initial screen, choose Enterprise Services Builder under
3. In the navigation area, open the software component SAP BASIS, software component
version SAP BASIS 7.30, and namespace http://sap.com/xi/XI/System/Patterns.
4. Open the node Process Integration Scenarios.
5. Open process integration scenario XiPatternOneStepScenario by double-clicking.
The process integration scenario editor is opened.
Process Integration Scenario/Component View

A process integration scenario describes the process flow and represents the points in the
process flow at which messages are exchanged between application components (in this
case, the application components Sender and Receiver). Specific communication variants
are represented by different component views. Component View File2File_NoMapping
represents the used variant.
Ensure that component view File2File_NoMapping is displayed in the graphical editor. If it is
not displayed, choose the component view in the preview area on the left by double-clicking.
The component view comprises two actions Send Message 1 and Receive Message 1, which
are linked by an asynchronous communication step (angled arrow).
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 in the component view.
1. To open the interface objects used, double-click the connecting arrow in the component
view.
The connection editor is displayed.
The service interfaces for the sender and receiver are displayed on the Assign Interfaces
tab page: in the case of the sender, it is the outbound interface XiPatternInterface1 and in
34 January 2011
the case of the receiver, it is the same inbound interface XiPatternInterface1. Since the
interface is the same for both the sender and receiver, no mapping is required.
2. To open the service interface XiPatternInterface1, double-click the interface name.
3. In the Service Interface editor you can see that it is an abstract interface.
The interface is abstract because the interface description is not implemented in the
relevant software component.
4. To open the message type, double-click the name of the message type
XiPatternMessage1 (in the service interface editor under Messages).
In the Message Type editor, you can display the data structure of the message. The data
structure is defined by the data type XiPatternDataType1.
Information about a person is structured by different elements in the data structure of the
exchanged message. Details such as the maximum character length are displayed in the
Details column.
Communication Channel Templates

You use communication channel templates to define details, which were defined when the
process integration scenario was defined, for the inbound or outbound processing of the
message. You can then use the communication channel template to create the
corresponding communication channel when configuring in the Integration Directory. You
then need to specify all the details, which are only known at configuration time, in the
communication channel.
1. To open a communication channel template (for example, for the sender), double-click
the name. Further details are displayed in the Display Communication Channel Template
editor.
2. Close all objects and the process integration scenario.

The design objects used are summarized once more in the following table.
Enterprise Services Repository
Design Objects Used
Process Integration Scenario Describes the process flow and indicates the points at which
(XiPatternOneStepScenario) messages are exchanged between the different components. The
component view File2File_NoMapping in particular describes all
variants in which no mapping is executed (interfaces at the sender
and receiver are identical).

January 2011 35
9.2.2 Configuring the scenario in the PI System

You perform the following configuration steps in the Integration Directory of the PI System.
This configuration is needed as the message exchange is done from the Advanced Adapter
Engine Extended system to the receiver adapter in the PI System.
Note the prerequisite steps described in section 2.2.

In configuration, you translate the process described by the process integration scenario
(component view) to an actual system landscape. You have already described the system
landscape in the SLD. The communication components you defined earlier enable you to
address the involved business systems as senders/receivers of messages in the Integration
Directory.
You use the model configurator for the whole configuration procedure. This tool enables you
to use a process integration scenario from the Enterprise Services Repository as a
configuration template and to add further information (which is not known until configuration
time).

First, call the Integration Directory (transaction SXMB_IFR) on the PI System. On the Process
Integration initial screen, choose hyperlink Integration Builder (under Integration Directory).
Selecting the Process Integration Scenario

Perform the following steps to select the process integration scenario that you want to
configure from the Enterprise Services Repository. Also, enter the name of the configuration
scenario (in the Integration Directory) in which you want to group the configuration objects.
1. To call the model configurator, choose Tools  Apply Model from ES Repository in the
Integration Builder menu bar.
This calls a wizard, which you use to select a model (in this case, a process integration
scenario) and create a configuration scenario in the Integration Directory.
2. Make sure that the model type Process Integration Scenario is selected (radio button
under Type of ES Repository Model).
3. Choose the input help (for the Name field) ( )

This calls an input help, which displays all process integration scenarios from the
Enterprise Services Repository in a list.
4. Select the process integration scenario XiPatternOneStepScenario (software component
version SAP BASIS 7.30, namespace http://sap.com/xi/XI/System/Patterns) from the
Enterprise Services Repository and choose Apply.
5. Choose Continue.
6. Enter the name of the configuration scenario as:
XiPatternOneStepScenario_AAEX_PI.
7. Choose Finish and then Close.
36 January 2011
The system calls the model configurator.
Selecting the Component View

Check whether the component view File2File_NoMapping is displayed. If it is not, choose the
menu option Select Component View ( ). On the subsequent screen, select the component
view (in the preview area) by double-clicking.
Assigning Communication Components

You perform the following steps to assign communication components to the application
components of the process integration scenario. You use the business system components
that you created before (see Error! Reference source not found.).
1. In the graphical editor, click on the lane representing the Sender application component.
This calls the Assign Business System Component dialog box for the Sender application
component (below the graphical representation of the process integration scenario).
2. To assign a communication component click in the input field in the Communication
Component column and call the input help ( ).
3. In the subsequent screen, select the communication component
<SID>_AAEX_FileSystem_XiPattern6 and then choose Apply.
4. Choose Next Role ( ) to navigate to the configuration dialog for the application
component Receiver.
5. Assign the communication component <SID>_PI_FileSystem_XiPattern7 to the
application component Receiver. Follow the same procedure as when assigning the
communication component to the application component Sender.
6. Choose Assign.
Configuring the Connection

You perform the following steps to configure the connection of the process integration
scenario. You activate the relevant sender-receiver relation (between the sender and receiver
component) and assign both the sender and receiver a (sender or receiver) communication
channel. You create the communication channel on the basis of the communication channel
templates that the process integration scenario already contains.
1. In the graphical editor, click on the connection between the lanes representing the two
application components.
2. This calls the Configure Connection dialog box for the connection between the actions
(below the graphical representation of the process integration scenario).
3. On the Configure Connections screen, choose the tab page Connections from
Component Assignment. The communication components that you assigned in the
previous configuration step are displayed.
The remaining tab pages contain further information about the process
integration scenario, for example, the communication channel templates that
are defined for the process integration scenario in the Enterprise Services
Repository.
4. Assign the receiver a communication channel. To do so, place the cursor in the field
Communication Channel for the Receiver Component, in the push button bar choose
 Create Communication Channel With Template ( ). In the subsequent wizard
you can create a communication channel based on a communication channel template.
January 2011 37
5. Choose Continue.
The default communication channel template on the subsequent screen is that which was
assigned to the sender application component in the process integration scenario (name
XiPatternChannel_FileReceiver, software component version SAP BASIS 7.30,
namespace http://sap.com/xi/XI/System/Patterns).
6. Choose Continue.
The default name for the communication channel on the next screen is
7. Confirm your selection by choosing Finish.
Generating the Configuration Objects

In the following steps, you generate the relevant configuration objects based on the settings
made in previous steps.
1. Choose the push button Create Configuration Objects ( ).

2. Under General, select the radio button Generation.
3. Choose Start.
The configuration objects are generated based on the settings you made. Once
generation is complete, the generation log is opened. The generation log displays the
results of generation. The generation log enables you to analyze any errors that occurred
during generation.
4. Close the generation log.
5. Close the model configurator. Choose Apply.
Manual Editing
In the following steps, you edit the generated configuration objects manually and enhance the
configuration settings made during generation. In this variant, you must edit the
communication channels after generation.
1. In the editor Display Configuration Scenario (for the open scenario
XiPatternOneStepScenario), on the tab page Objects open the communication channel
( ) XiPatternChannel_FileReceiver by double-clicking.
2. Change to Edit Mode.
3. Under File Access Parameter in the Target Directory field, enter the path in the file
directory that you defined previously (see Error! Reference source not found.). In the
case of the receiver communication channel, enter the whole path for the file directory on
the PI Integration Server XiPattern7.

1. To do this, select the Change Lists tab page in the Integration Directory navigation area.
context menu.
38 January 2011

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
XiPattern6.
2. Rename the file ZXiPatternSenderFile1.xml as XiPatternSenderFile1.xml.
The File/FTP adapter is designed in a way that a file with exactly this name is
recognized and moved from the source directory XiPattern6 to the target directory on
the PI System XiPattern7 every 60 seconds. If the configuration was executed
without errors, the file will be moved from the source directory within 60 seconds after
it is renamed.
3. Open the directory XiPattern7 on the PI Integration Server and check that the file has
arrived.
4. Open the file and check whether the content has changed (compare with the original file
ZXiPatternSenderFile1.xml).
The file must not have been changed when this variant is executed.
proceed as follows:
1. Start the Monitoring by choosing Configuration and Monitoring Home on the Advanced
Adapter Engine Extended start page.
3. Select Database.
5. Choose Go.
6. Select the message to be displayed by selecting the appropriate radio button and then
choose Open Message.
7. The processing in the PI System needs to be checked in the Message Monitoring in the
PI System. Start the Monitoring by choosing Configuration and Monitoring Home on the
PI Start Page and follow the steps described above to find the message on the PI
System.

using communication between Advanced
Adapter Engine Extended and PI System -
using Exactly Once In Order
one sender on the Advanced Adapter Engine Extended (file directory XiPatterns8) sends a
series of messages to one receiver on the PI System (file directory XiPatterns9). No mapping
is executed between the outbound and inbound interface in this variant. The messages are
delivered in some particular order. Concretely, the file adapter allows either the last-modified
timestamp or the filename to be used to order the input files in its directory.
January 2011 39

the Advanced Adapter Engine Extended
Design Objects Used

(XiPatternInterface1O) the message type used.
(XiPatternChannel_FileSenderO, enable a communication channel to be preconfigured at design time.
XiPatternChannel_XiReceiver,
XiPatternChannel_FileReceiverO)
10.1.2 Configuring the scenario on the Advanced Adapter

Engine Extended in Integration Directory


objects.
40 January 2011
3. Enter the name XiPatternOneStepScenario_AAEX_PI_EOIO.

4. Choose Create.


4. Select the communication component <SID>_AAEX_FileSystem_XiPattern8 and choose
Apply.
5. In field Communication Channel enter XiPatternChannel_FileSenderO.
6. Under Add to Scenario select XiPatternOneStepScenario_AAEX_PI_EOIO (input
help).
7. Choose Create.
8. In the menu of the communication channel object editor select Communication Channel
 Apply Template.
9. Select the template XiPatternChannel_FileSenderO.
10. Choose Apply.
directory that you defined under Error! Reference source not found.. In the case of the
sender communication channel, enter the whole path for the file directory XiPattern8.

XiPatternChannel_XIReceiver (communication component
<SID>_PI_FileSystem_XiPattern9) using the template
XiPatternChannel_XIReceiver. Enter the URL to the Integration Server as Target URL
(for example http://<PI-host>:<PI-port>/sap/xi/engine?type=entry). As User Name set
PIAPPLUSER (or a copy of PIAPPLUSER) with the respective User Password in the
Integration Server Client, in field Logon Client set the client of the integration server (e.g.
001).

January 2011 41

choose Apply.
5. In the fields Interface and Namespace enter XiPatternInterface1O and
6. Under Add to Scenario select XiPatternOneStepScenario_AAEX_PI_EOIO (input help).
7. Choose Create.
XiPatternChannel_FileSenderO. For the software component version of sender
10. In tab Receiver Interfaces for name and namespace enter XiPatternInterface1O and
http://sap.com/xi/XI/System/Patterns, respectively. In Software Component
Version set SAP BASIS 7.30.
manually.
XiPatternChannel_XIReceiver.

3. Position the cursor on the Standard Change List node and choose Activate ( )) in the
context menu.

the PI System
You use the component view File2File_NoMapping_InOrder in process integration scenario
XiPatternOneStepScenario to configure this variant. The following graphic shows the
component view:
42 January 2011
Interface Objects
In this variant, the data structures at both the sender and receiver side are the same and no
mapping is required, the service interfaces XiPatternInterface1O is used for sender and
receiver

The following table summarizes the design objects used.
Design Objects Used
Component View Describes the process flow and the message exchange for this
File2File_NoMapping_InOrder (Process variant.
Integration Scenario
XiPatternOneStepScenario)
Service interface (XiPatternInterface1O) Describes the interface and data structure of the sender and
receiver. The data structure is the same for sender and
Message Type (XiPatternMessage1)
receiver.
Data Type (XiPatternDataType1)
10.2.2 Configuring the Process Integration Scenario in

the PI System
To configure this variant, a new configuration scenario needs to be created in the PI System
to enable message flow from the Advanced Adapter Engine Extended to the receiver adapter
in the PI System.
Selecting the Process Integration Scenario

Perform the following steps to select the process integration scenario that you want to
configure from the Enterprise Services Repository. Also, enter the name of the configuration
scenario (in the Integration Directory) in which you want to group the configuration objects.
January 2011 43
1. To call the model configurator, choose Tools  Apply Model from ES Repository in the
Integration Builder menu bar.
This calls a wizard, which you use to select a model (in this case, a process integration
scenario) and create a configuration scenario in the Integration Directory.
2. Make sure that the model type Process Integration Scenario is selected (checkbox under
Type of ES Repository Model).
3. Choose the input help (for the Name field) ( ) and select Process Integration
Scenario in the dropdown listbox.
This calls an input help, which displays all process integration scenarios from the
Enterprise Services Repository in a list.
4. Select the process integration scenario XiPatternOneStepScenario (software component
version SAP BASIS 7.30, namespace http://sap.com/xi/XI/System/Patterns) from the
Enterprise Services Repository and choose Apply.
5. Choose Continue.
6. Enter the name of the configuration scenario as:
XiPatternOneStepScenario_AAEX_PI_EOIO.
7. Choose Finish and then Close.
The system calls the model configurator.
Selecting the Component View

Select component view File2File_NoMapping_InOrder.
Assigning Communication Component

Assign the communication component <SID>_AAEX_FileSystem_XiPattern8 to the
application component Sender and <SID>_PI_FileSystem_XiPattern9 to the application
component Receiver.
Configuring the Connection

You create the communication channel on the basis of the communication channel templates
that the process integration scenario already contains.
1. In the Configure Connections screen, assign the receiver a communication channel. To
do so, place the cursor in the field Communication Channel for the Receiver Component,
in the push button bar choose  Create Communication Channel With Template
( ). In the subsequent wizard you can create a communication channel based on a
communication channel template.
2. Choose Continue.
The default communication channel template on the subsequent screen is that which was
assigned to the receiver application component in the process integration scenario (name
XiPatternChannel_FileReceiverO, software component version SAP BASIS 7.30,
namespace http://sap.com/xi/XI/System/Patterns).
3. Choose Continue.
The default name for the communication channel on the next screen is
XiPatternChannel_FileReceiverO.
4. Confirm your selection by choosing Finish.
44 January 2011
Generating the Configuration Objects

To do so, proceed as described in variant 1.
When you have checked the generation log, close it and save the configuration scenario.
Manual Editing
In the following steps, you edit the generated configuration objects manually and enhance the
configuration settings made during generation. In this variant, you must edit the
communication channels after generation.
1. In the editor Display Configuration Scenario (for the open scenario
XiPatternOneStepScenario_AAEX_PI_EOIO), on the tab page Objects open the
communication channel ( ) XiPatternChannel_FileReceiverO by double-clicking.
2. Under File Access Parameter in the Target Directory field, enter the path in the file
directory that you defined previously (see Error! Reference source not found.). In the
case of the receiver communication channel, enter the whole path for the file directory
XiPattern9.
4. Activate your change lists.
10.3 Execution
without errors.
1. Stop the channel <SID>_AAEX_FileSystem_XiPattern8 | XiPatternChannel_FileSenderO
I in Configuration and Monitoring Home  Adapter Engine  Communication Channel
Monitoring to make sure no processing runs during the time the files are placed into the
source folder.
2. On the host of the PI System open the file directory XiPatternsO_AAEX/XiPatterns9. If
the output file XiPatternReceiverFile.txt is already present, delete this file. The execution
of this test will create this file if it is not present and append a series of output files to this
file.
3. On the host of the Advanced Adapter Engine Extended open the file directory
XiPatternsO_AAEX/XiPatterns8
4. Unpack file XiPatternSenderFilesEOIO.zip in the current directory. This will place a series
of input files XiPatternSenderFile00001.xml, …, XiPatternSenderFile01000.xml.
The File/FTP adapter is configured so that the files are picked in the order sorted by the
file names and moved from the source directory XiPatterns8 on the Advanced Adapter
Engine Extended to the target directory XiPatterns9 on the PI System and the files are
concatenated into a single file XiPatternReceiverFile.txt.
5. Start the channel <SID>_AAEX_FileSystem_XiPattern8 | XiPatternChannel_FileSenderO
in Configuration and Monitoring Home  Adapter Engine  Communication Channel
Monitoring to start processing the files.
6. Open the directory XiPatternsO_AAEX/XiPatterns9 and check that the files have been
transferred.
7. Open the XML file XiPatternReceiverFileAll.xml which includes the output file and check
whether the content is in the correct order.
January 2011 45
The content must be in the correct order with the incremental ID value and the entire
content must be present.
8. Furthermore, you can check the processing of the messages in the message monitoring
on the Advanced Adapter Engine Extended and in the PI System as in Variant 7.
11 Appendix
11.1 Monitoring Tools
11.1.1 Monitoring in Runtime Workbench in the PI System
The message exchange can be monitored in the Configuration and Monitoring Home as
described in the execution chapters and in the Runtime Workbench. To start the Runtime
Workbench monitoring proceed as follows:
1. Start the Monitoring by choosing Runtime Workbench on the PI start page.
(transaction SXMB_IFR)
2. Choose Message Monitoring.
3. Select Integration Engine <SID> as the component and then choose Display.
4. Use appropriate filter criteria to restrict the number of XML messages displayed
(for example, the processing period).
5. Choose Start.
then choose Details.
The tab page Message Contents displays the message contents including all
message versions for the various phases of message processing.
11.1.2 Transaction SXMB_MONI in the PI System

The messages can not only be monitored in the Runtime Workbench but as well in the SAP
system of the Integration Server. To do this, proceed as follows:
1. In the Integration Server client, start Exchange Infrastructure  Integration Engine:
Monitoring (transaction SXMB_MONI)
2. Select Monitor for Processed XML Messages and use the appropriate search criteria
to restrict the number of XML messages displayed (for example time/date)
3. Choose Start
The system displays the selected messages in a table. For more details select the
line of the message and choose Display
4. The system displays the message in detail.
To display the payload before and after the mapping step you have to activate logging in the
Integration server (RUNTIME parameter LOGGING in SXMB_ADM  Integration Server
Configuration). IN this case, every step in the message processing will be persisted and you
can check the payload for each of the steps. To compare the payload before mapping with
the payload after mapping use the following procedure in the details screen of a message in
transaction SXMB_MONI.
1. On the left side in the tree select Inbound Message  Payloads  Main Document
and choose Display contents in window 1.
46 January 2011
The Inbound message payload is displayed.

2. Do the same procedure with Receiver Determination --> Payloads --> Main
Document and choose Display contents in window 2.
The Outbound message payload is displayed.
11.1.3 Monitoring in Solution Manager

The messages can also be monitored centrally in the Solution Manager System. To do this,
proceed as follows:
1. Log into the connected SAP Solution Manager System and call the Solution
Manager Workcenters using transaction SOLMAN_WORKCENTER.
2. Change to Tab Technical Monitors and follow the link to PI Monitoring.
3. Select the PI Domain you want to monitor (for example B4X).
4. Launch the Message Monitor either embedded or in a new window using the
button Message Monitor
January 2011 47

SAP NetWeaver Process Integration 7.3 - Simple Use Cases For Advanced Adapter Engine Extended PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP NetWeaver Process Integration 7.3 - Simple Use Cases For Advanced Adapter Engine Extended PDF

Uploaded by

Copyright:

Available Formats

SAP NetWeaver 7.

7.3 Execution ............................................................................................... 26

List of related documentation

SAP NetWeaver Library Introduction to demo examples and description of the

SAP NetWeaver Introduction to Simple Use Cases and description of the

Configuration of SAP Configuring usage type Advanced Adapter Engine

2 Introduction and Prerequisites

SAP NetWeaver Process Integration (Advanced Adapter Engine Extended)

List of required steps

You can find the corresponding guides

2.2.2 Providing the necessary User and Authorizations

2.2.3 Setting Up the File Directories

5. Copy the following three files to directories XiPattern1 and XiPattern6

2.2.4 Creating the Technical and Business Systems in the

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

2.2.5 Creating the Technical and Business Systems in the

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

13. Choose Next.

2.2.6 Defining Business System Components in the

2.2.7 Defining Business System Components in the

2.3 Design Objects Used

Process Integration Scenario/Component View

Communication Channel Templates

3 Variant 1: One Sender and One Receiver

Summary of Design Objects Used

Design Objects Used

Object Type (Name) Description

Service Interface Specifies the communication mode (asynchronous) and references

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

3.1 Configuring the Process Integration Scenario

For more information, see Defining the Integrated Configuration.

Calling the Integration Directory

Creating a Configuration Scenario

Creating the Communication Channels for Sender and Receiver

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

Example: C:/<selected path>/XiPatterns_AAEX/XiPattern1

If there already is an entry for the communication component in the Create

Creating the Integrated Configuration

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

9. In the tab Receiver select the communication component

Activating the Change List

3.2 Executing the Use Case

4 Variant 2: One Sender and Two Receivers

4.1 Design Objects Used

4.2 Configuring the Process Integration Scenario

Opening the Configuration Scenario

For more information, see Defining the Integrated Configuration.

Creating the Communication Channel for the Second Receiver

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

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

Example: C:/<selected path>/XiPatterns_AAEX/XiPattern3

Changing the Integrated Configuration

Activating the Change List

4.3 Executing the Use Case

As for the execution of variant 1, in directory XiPattern1, copy the file

5 Variant 3: One Sender and Two Receivers

5.1 Design Objects Used

5.2 Configuring the Process Integration Scenario

Using the Configuration Scenario

Changing the Integrated Configuration

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

The data structure of the message is displayed.

Activating the Change List