SAP NetWeaver SAP NetWeaver Process Integration Simple Use Cases for Advanced Adapter Engine Extended (AEX)

(1)

SAP NetWeaver

Process Integration Simple Use Cases for Advanced Adapter

Engine Extended (AEX)

Document Version 1.0 – March 2012

SAP NetWeaver 7.31

(2)

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 SAP‟s 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) titled

Simple Use Cases for Advanced Adapter Engine Extended. T +49/18 05/34 34 24

F +49/18 05/34 34 20 www.sap.com

(3)

1 Preface ... 6

2 Introduction and Prerequisites ... 6

2.1 Introduction ... 6

2.2 Prerequisites ... 8

2.2.1 General Prerequisites ... 8

2.2.2 Providing the necessary User and Authorizations ... 9

2.2.3 Special Prerequisites for Configuring Variants 10 and 12 ... 10

2.2.4 Special Prerequisites for Configuring Variant 17 ... 11

2.2.5 Setting Up the File Directories ... 11

2.2.6 Creating the Technical and Business Systems in the System Landscape Directory of the Advanced Adapter Engine Extended ... 12

2.2.7 Defining Business System Components in the Integration Directory in the Advanced Adapter Engine Extended ... 14

2.2.8 Special Prerequisites for Configuring Performance Monitoring Parameter ... 15

2.3 Design Objects Used ... 15

3 Variant 1: One Sender and One Receiver using the Advanced Adapter Engine Extended ... 16

3.2 Configuring the Process Integration Scenario ... 19

3.3 Executing the Use Case ... 22

3.4 Virus-Scanning for Messages: ... 24

4 Variant 2: One Sender and Two Receivers using the Advanced Adapter Engine Extended ... 27

5 Variant 3: One Sender and Two Receivers using Advanced Adapter Engine Extended – with Routing Condition ... 29

5.4 Copy configuration scenario with content ... 30

6 Variant 4: One Sender and Mulitple Receivers using Advanced Adapter Engine Extended – with Dynamic Receiver Determination ... 32

6.1 Prerequisite - Creating Value Mapping Group ... 32

7 Variant5: One Sender and Two Receivers using Advanced Adapter Engine Extended – With Message Mapping ... 35

(4)

8 Variant 6: One Sender and Two Receivers using Advanced

Adapter Engine Extended – With XSLT Mapping ... 38

8.2 Modifying Configuration Scenario... 39

9 Variant 7: One Sender and Two Receivers using Advanced Adapter Engine Extended - with XML-Validation ... 40

9.3 Execution ... 41

10 Variant 8: One Sender and One Receiver using Advanced Adapter Engine Extended - using Exactly Once In Order ... 42

10.3 Execution ... 46

11 Variant 9: One Sender and One Receiver - Proxy-to-Proxy Communication using the Advanced Adapter Engine ... 46

11.3 Execution ... 52

12 Variant 10: One Sender and One Receiver - Proxy-to- Proxy Communication using the Advanced Adapter Engine and Principle Propagation ... 52

12.1 Prerequisites ... 53

12.1.1 Activating Principle Propagation – Trust Relationship Settings ... 53

12.1.2 Create Destination in the AEX system ... 53

12.4 Execution ... 59

13 Variant 11: One Sender and One Receiver – synchronous Proxy-to-Proxy Communication using the Advanced Adapter Engine ... 61

13.3 Execution ... 66

14 Variant 12: One Sender and One Receiver – synchronous Proxy-to-Proxy Communication using the Advanced Adapter Engine and Principle Propagation ... 68

14.1 Prerequisites ... 68

14.1.1 Activating Principle Propagation – Trust Relationship Settings ... 68

14.1.2 Create Destination in the AEX ... 68

(5)

14.4 Execution ... 74

15 Variant 13: One Sender and One Receiver - Proxy-to- Proxy Communication using the Advanced Adapter Engine whereas Receiver send back an Acknowledgment ... 76

15.2 Execution ... 79

16 Variant 14: One Sender and One Receiver - Proxy-to- Proxy Communication using the Advanced Adapter Engine using Packaging... 81

16.1 Packaging ... 81

16.3 Execution ... 84

17 Variant 15: One Sender and One Receiver using Advanced Adapter Engine Extended – with Parameterized Mapping ... 86

17.3 Execution ... 91

17.4 Execution with Channel Scheduling ... 92

18 Variant 16: One Sender and Two Receivers using Advanced Adapter Engine Extended – with Message Order at Runtime ... 94

18.2 Configuring the scenario in Integration Directory ... 96

18.3 Execution ... 99

19 Variant 17: One Sender and One Receiver using Advanced Adapter Engine Extended – With Mapping and encrypted persistent storage (PCI-compliant) ... 100

19.2 Configuring the Scenario in Integration Directory ... 102

20 Appendix ... 105

20.1 Setting up the system for payload encryption ... 105

20.1.1 Creating the Keystore and generating the encryption key ... 105

20.1.2 Global configuration of the MessagingSystem for persistence layer encryption 108 20.2 Monitoring Tools ... 110

20.2.1 PI Component Monitor for NWA ... 110

20.2.2 Monitoring in Solution Manager ... 113

20.2.3 PI Communication Channel Monitor Enhancement for NWA ... 113

20.2.4 Configuration for data collection in Performance Monitor ... 114

(6)

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 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 Engine Extended

This document is updated on a regular basis in SAP Developer Network (SDN) and is available as Simple Use Cases for Advanced Adapter Engine Extended.

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:

(7)

Variant Description Variants 1, 8, 9, 10, 11, 12,

13, 14, 15, and 17:

Represents message exchange between one sender and one receiver on the Advanced Adapter Engine Extended (AAEX). The message processing is done locally on the Advanced Adapter Engine Extended.

Variant 8 is executed using EOIO protocol.

Variants 9 to 14 are using PROXY clients to send and receive the messages, Variants 11 and 12 are executed synchronously. Variant 13 is using acknowledgments.

Variant 14 is using packaging. Variants 10 and 12 are using principal propagation.

Variant 15 is using parameterized mapping.

In Variant 17 the message payload is stored encrypted on the database. The payload can be seen unencrypted in Message Monitoring.

Variant 2 and 4:

One sender and two receivers

Represents message exchange between one sender and two receivers. The message processing is done locally on the Advanced Adapter Engine Extended.

Represents message exchange between one sender and two receivers. The receivers are determined on the fly using mapping via Extended Receiver Determination.

Variant 3:

One sender and two receivers – with routing condition (see 5)

Represents message exchange between one sender and two receivers in which the way the message is forwarded to the receivers is determined by routing conditions The message processing is done locally on the Advanced Adapter Engine Extended.

Variant 5 and 6:

One sender and two receivers – with mapping

Represents message exchange between one sender and two receivers. A mapping is executed when the message is forwarded to one of the two receivers. The message processing and mapping are done locally on the Advanced Adapter Engine Extended.

Variant 5 uses Message Mapping.

Variant 6 uses Mapping based on XSL (Extensible Stylesheet Language) transformation program.

Variant 7:

One sender and two receivers – with XML- Validation (see 98)

Represents message exchange between one sender and two receivers. A mapping is executed when the message is forwarded to one of the two receivers. The payload is validated using XML-Validation in inbound processing of the adapter engine. The message processing, mapping and XML validation are done locally on the Advanced Adapter Engine Extended.

Variant 16:

One sender and two receivers – with Sender EOIO and Mapping Order At Runtime for one Receiver (see 20)

Represents message exchange between one sender and two receivers. Sender has EOIO setting to handle EOIO message for multiple receivers. At one of receiver, Mapping Order At Runtime setting is done to check retrieved

messages follow the order of definition as per the

agreement. The message processing and mapping 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:

(8)

 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 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

(9)

1. You have installed the Advanced Adapter Engine Extended and SAP NetWeaver 7.31.

Master Guide – SAP NetWeaver 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 7.3 and SAP NetWeaver 7.3 including Enhancement Package 1

2. Software Component version for SAP_BASIS in Sender Proxy System

To execute variants 9 – 15, Sender Proxy system should have 731 version for SAP_BASIS Software Component.

You can also use Application System client (e.g. 105) of a PI – Dual Stack system as Sender Proxy System.

3. You have imported the content for the Enterprise Services Repository corresponding to the latest support package/patch into the PI and the Advanced Adapter Engine Extended System.

SAP Note 836200

The simple use cases are located in the Enterprise Services Repository in the software component SAP BASIS, software component version SAP BASIS 7.31, in the namespaces

http://sap.com/xi/XI/Syste m/Patterns.

4. You have configured the Advanced Adapter Engine Extended and SAP NetWeaver Process

Integration.

Configuration of SAP NetWeaver Process Integration

5. You have configured the System Landscape Directory (SLD) for the PI and the Advanced Adapter Engine Extended System.

Configuring, Working with and Administering System Landscape 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

(10)

2.2.3 Special Prerequisites for Configuring Variants 10 and 12

In Variants 10 and 12, principal propagation will be used during message processing. For this kind of data exchange trust relationship settings have to be done. These tasks need to be carried out by a system administrator because global system configuration is affected.

Ask the system administrator to do the setup if you have not the rights. Maybe parts of the steps are already done!

Activating Principle Propagation – Trust Relationship Settings 1. Logon to the sending system (<SID>_105)

2. Call transaction STRUSTSSO2 3. Select System-PSE

4. Double_Click in the field Own-Certificate  Owner

5. In the Certificate Frame press the button “Export Certificate”

6. Logon to AEX NWA http(s)://<host>:<port>/nwa 7. Switch to tab Configuration

8. Press link Certificates and Keys 9. Select Keystore-View “TicketKeystore”

10. In the Details Tab create entry for <SID>_105 and upload certificate.

11. Now Maintain ACL Security Provider.

12. Go Back to the Configuration tab. Press link “Trusted Systems”.

13. Press button “Add trusted system”

14. Add <SID>, client and assign certificate to upload (certificate from <SID>_105).

15. Note the client information shown below the SID of the AEX.

16. Go Back to the Configuration tab.

17. Press link Certificates and Keys

18. Select Keystore-View “TicketKeystore” and select entry “SAPLogonTicketKeypair- cert”

19. Export entry.

20. Logon to receiving system (again <SID>_105) 21. Call transaction STRUSTSSO2

22. Select System-PSE

23. Upload the certificate (which was exported at the AEX) and press button “Add to Certificate List”.

24. Then press button “Add to ACL” and enter AEX <SID> for System ID and the client number from step 15 for client.

25. Save your settings.

(11)

2.2.4 Special Prerequisites for Configuring Variant 17

In Variant 17 data will be encrypted before being persisted in the database. For this kind of encryption, the J2EE Engine needs to be configured upfront. Concretely, a secure keystore with a certain name needs to be created and a suitable key needs to be placed in that keystore. Furthermore the AEX needs to be configured to use that particular key for the process of encrypting message payloads. These tasks need to be carried out by a system administrator because global system configuration is affected.

The documentation of these configuration steps is available in the appendix chapter 20.1.

2.2.5 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, XiPattern1_PCI, XiPattern2_PCI, XiPattern3, and XiPattern10.

4. Create three further sub directories in the sub directory XiPatternsO_AAEX. Suggested names: XiPattern4, XiPattern5.

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.

5. Copy the following three files to directory XiPattern1

 ZXiPatternSenderFile1.xml

 ZXIPatternSenderFile3.xml

 ZXIPatternSenderFileParamMap.xml

 ZXiPatternSenderFileMapOrderRuntime.xml 6. Copy the following file to directory XiPattern4

 XiPatternSenderFilesEOIO.zip (This file contains 1000 xml files for the EOIO

(12)

7. Copy following file to directory XiPattern10

 ZXIPatternSenderFile1.xml

8. Copy the following files to directory XiPattern1_PCI:

These files are provided by SAP in a ZIP file. The ZIP file for 7.31 containing also the EOIO test files is available in SAP Developer Network (SDN) and can be found using the direct link EHP 1 for SAP NetWeaver Process Integration 7.3 – Test Files for Simple Use Cases.

2.2.6 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:

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(s)://<AAEX-Host>:<AAEX-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.

(13)

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

 <SID>_AAEX_FileSystem_XiPattern1_PCI

Create one more technical system for the Logical system of the ABAP (ERP R/3 backend) proxy server for variants 11 - 16.

1. To do so, Login to the R/3 system.

2. Go to transaction /nrz70.

3. Enter following details of the PI AEX system for RFC Connection to SLD.

 Gateway Host: Enter the host name of PI system, for example pwdf2638.

 Gateway Service: Enter the service of the PI System, for example sapgw10. (You can get this information from Administration -> Settings within SLD.

4. Click Start SLD Data Collection Now (F5).

5. Click Yes on confirmation pop-up.

6. Message for successful data collection will be displayed as RFC call successful. Exit the transaction.

7. Go to SLD of the Advanced Adapter Engine Extended System. To do so, on the Advanced Adapter Engine Extended start page, choose System Landscape Directory.

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

9. Entry as <SID> on <server> will be available as AS ABAP type in the list of Technical Systems.

10. Now create one new business system using this Technical System. To create the business system, on the SLD start page, choose Business Systems.

11. Choose New Business System.

12. Select the type AS ABAP by selecting the appropriate radio button.

13. Choose Next.

14. Select the technical system for the R/3 Logical System that you just defined (dropdown

(14)

15. Select the client for the R/3 Logical System (e.g. 105) 16. Choose Next.

17. Enter the name <SID>_105. <SID> is the system ID of the R/3 server.

18. Choose Next.

19. Choose Next.

20. Specify the Advanced Adapter Engine Extended System as Integration Server (field Related Integration Server).

21. Choose Finish.

2.2.7 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(s)://<AAEX-Host>:<AAEX-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:

(15)

 <SID>_105

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.8 Special Prerequisites for Configuring Performance Monitoring Parameter

Collecting data about the performance of message processing on the Advanced Adapter Engine is deactivated by default and requires activation in Net Weaver Administrator. These tasks need to be carried out by a system administrator because global system configuration is affected.

The documentation of these configuration steps is available in the appendix chapter 20.2.4.

2.3 Design Objects Used

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

(16)

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.

3.1 Design Objects Used

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.

The subsequent description of each variant will refer to the detailed step-by-step description in this section; the relevant design objects will only be listed briefly in each case.

(17)

You use the component view File2File_NoMapping in process integration scenario XiPatternOneStepScenario to configure this variant. The following graphic shows the component view:

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) for the Advanced Adapter Engine Extended System, open the Advanced Adapter Engine Extended Start Page using the URL: http(s)://<AAEX-Host>:<AAEX- Port>/dir..

2. On the Process Integration Tools page, choose Enterprise Services Builder under Enterprise Services Repository.

3. In the navigation area, open the software component SAP BASIS, software component version SAP BASIS 7.31, 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 three variants without a mapping. Component View File2File_WithMapping represents the variant that includes a mapping.

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,

(18)

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 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.

Mapping Objects

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

Navigate to the connection editor and choose the Assign Mapping tab page.

You can see that a mapping has not been assigned for the connection between the two (identical) service interfaces.

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. In the connection editor, choose the Assign Communication Channel Template tab page.

One communication channel is specified for both the sender and receiver:

(XiPatternChannel_FileSender for the sender, XiPatternChannel_FileReceiver for the receiver.

2. 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.

3. Close all objects and the process integration scenario.

Summary of Design Objects Used

The design objects used are summarized once more in the following table.

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

Enterprise Services Repository Design Objects Used

(19)

Object Type (Name) Description

Process Integration Scenario (XiPatternOneStepScenario)

Describes the process flow and indicates the points at which 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).

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 Communication Channel Templates

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.2 Configuring the Process Integration Scenario

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).

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

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(s)://<AAEX-Host>:<AAEX-Port>/dir.

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.

(20)

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.31, 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.

7. Choose Finish and then Close.

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 2.2.7).

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_XiPattern1 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>_AAEX_FileSystem_XiPattern2 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.

(21)

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 sender a communication channel. To do so, place the cursor in the field Communication Channel for the Sender 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.

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_FileSender, software component version SAP BASIS 7.31,

namespace http://sap.com/xi/XI/System/Patterns).

The default name for the communication channel on the next screen is XiPatternChannel_FileSender.

7. Confirm your selection by choosing Finish.

8. Following the same procedure (see step 4-7), assign the application component of the receiver a communication channel (XiPatternChannel_FileReceiver) based on the default communication channel template (name XiPatternChannel_FileReceiver, software component version SAP BASIS 7.31, namespace http://sap.com/xi/XI/System/Patterns).

Generating the Configuration Objects

In the following steps, you generate the relevant configuration objects based on the settings made in previous steps.

1. If not already selected, select the flag for Configuration for Advanced Adapter Engine.

2. Choose the push button Create Configuration Objects ( ).

3. Under General, select the radio button Generation.

4. Choose Start.

The integrated 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.

5. Close the generation log.

6. Close the model configurator. Choose Apply.

7. 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

(22)

1. In the editor Display Configuration Scenario (for the open scenario

XiPatternOneStepScenario_AAEX), on the tab page Objects, open the communication channel ( ) XiPatternChannel_FileSender by double-clicking.

2. Under File Access Parameter in the Source Directory field, enter the path in the file directory that you defined previously (see 2.2.4). In the case of the sender

communication channel, enter the whole path for the file directory XiPattern1.

Example: C:/<selected path>/XiPatterns/XiPattern1 3. Save the communication channel.

4. Activate it by using the menu Communication Channel  Activate.

5. To check if the channel works you can directly jump to the channel monitoring using the menu path Communication Channel  Channel Monitoring

6. The PI Communication Channel Monitoring page will open up where you can do a self test for the channel. To do this click on the button Ping Channel.

7. The status page for the channel will show up with detailed information of the executed self test.

8. Following the same procedure, edit the communication channel XiPatternChannel_FileReceiver (communication component

<SID>_AAEX_FileSystem_XiPattern2). Enter the path for the file directory XiPattern2.

9. Save the communication channel and activate it.

10. Open the Channel Monitoring and check the status of the channel.

Activating the Change List

1. To do this, select the Change Lists tab page in the Integration Directory navigation area.

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

3.3 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.

(23)

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.

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.

Check Performance Monitoring of the message in NWA/PIMON

Performance Monitoring is often required to gauge the performance of the Adapter Engine by measuring the bytes processed over a given time period. It would be a useful piece of information for the Administrators to get an idea about time spent by messages in various stages of its lifecycle. Performance Monitoring for message exchange can be done for parameters as

1) Message put in to the queue

2) Message retrieved from the queue and 3) 'Call Sap Adapter' module.

4) Any other custom module.

To start Performance monitoring proceed as follows:

1. Start the Monitoring by choosing Configuration and Monitoring Home on PI Tools Home Page

2. Choose Monitoring -> Adapter Engine

3. Click on link Performance Monitor. New Screen opens up titled “PI Performance Monitoring: Overview”

4. Click on button Advanced Selection and Filter for Receiver Channel

“XiPatternChannel_FileReceiver” in Outbound Channel Field

5. Entries with respect to above filter criteria are displayed in an hourly interval aggregation. Table will display following details of Message flow in the aggregation intervals

a. Message Size (Bytes)

b. Average Processing Time (Milliseconds) c. Total Processing Time (Milliseconds)

6. Select one entry of the Table. Message Scenario table with further details (directory objects involved in message flow) along with Average Message Size and Total Message size value will be displayed. An entry within this table is automatically selected.

7. Further another table titled “Message Processing Details” is displayed for above entry. This table has two tabs.

a. Module Information tab - Information about time taken (Minimum Time, Maximum Time and Average Time) by different modules to process the message. Check existence of following modules

(24)

ii. MS:Message_Put_In_Queue

iii. MS: Message_Remove_From_Queue

iv. Optional – other custom module if Channel processing this message has custom adapter module

b. Message Information tab - Information about size of message. Value in this is same as per first table.

8. Use appropriate filter criteria (for example, the processing period) and check for more message and their performance parameters.

9. A field Aggregation Interval is available to provide the time that db will write out collected performance data to disk, and therefore allow it to be visualized on UI.

Aggregation Interval varies as per selection of Time Interval. Check for following combination of Time Interval and their corresponding Aggregation Interval

a. Last 12 Hours – 15 Minutes and 1 Hour b. Today – 15 Minutes, 1 Hour and 1 Day c. Yesterday – 1 Hour and 1 Day

d. Last Seven Days – 1 Hour and 1 Day e. This Week – 15 Minutes, 1 Hour and 1 Day f. Last Week – 1 Hour and 1 Day

g. This Month – 15 Minutes, 1 Hour and 1 Day h. This Year – 15 Minutes, 1 Hour and 1 Day

i. User-Defined Selection - 15 Minutes, 1 Hour and 1 Day along with an option to Select Start Date/Time and End Date/Time

10. Open Performance Monitoring in NWA via http(s)://<host>:<port>/nwa -> SOA ->

Monitoring -> PI Performance Monitoring

11. Repeat Steps 3 – 9 and Compare UI and displayed data. It should be same

3.4 Virus-Scanning for Messages:

The Virus Scan Interface that is part of SAP NetWeaver allows you to include external virus scanners in an SAP system and to scan files or documents processed by SAP applications for viruses.

In order to test the Virus Scanning of Messages on the JAVA side we consume the above simple scenario & enhance it. In the message payload, the virus is attached [treated as malicious by the Virus Scanner not a real virus].

Prerequisites:

To test this scenario a virus scanner needs to be configured first

1. To configure the Virus Scan Interface in the Java environment, NWA is needed to define the required settings for scanner groups (NWA  Configuration  Security  Virus Scan Provider), the virus scan adapter and scan profiles. The configuration of the Virus Scan Provider service is stored in the Configuration Manager of the JEE Engine.

New PI Virus Scan Profile Profile Name pi_Messaging

Profile Description Process Integration Messaging Reference Profile <Default Profile>

(25)

2. Logon to SAP NetWeaver Administrator and go to Configuration  Infrastructure  Java System Properties .Search for service XPI Adapter: XI and specify the following Java system properties (see table).

Service Property Possible Values

XPI Adapter: XI xiadapter.virusscan.active 0 - inactive (default) 1 - active

XPI Adapter: XI xiadapter.virusscan.profile pi_Messaging (default) XPI Adapter: XI xiadapter.virusscan.mode 1 - attachments (default)

2 - attachments + main payload

XPI Adapter: XI xiadapter.virusscan.content_type 1 - binary (default) 2 - all content types Modifying the Configuration:

In this scenario we check the Virus scanning of the Messages - Specific to the Scenario [Virus scanning can be enabled Globally or Specific to scenario]. Scenario Specific virus scanning can be achieved at both Inbound and Outbound Processing.

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 tab Inbound Processing Tab, Go to the Virus Scan field and for the scenario specific, choose the option Virus scan by Adapter for scanning the infected message .(You can also try the Virus scan configuration at the Outbound Processing Tab).

4. Save the integrated configuration.

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

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

Execution:

The scenario will be executed with following different ways  1. Sending virus within main payload.

2. Sending virus within the attachment.

3. Sending infected payload without activating virus scanner.

4. Sending message after deleting virus from the main payload and attachment and then retest

Sending virus within main payload

1. In order to test the virus scanner send the infected payload as given below.

X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*

(26)

For sending, place above content in a file and name the file as XiPatternSenderFile.xml and place it at sender location.

2. In the sender channel, change the name of sender file. Save and activate.

3. Start the Communication channels consumed in the scenario. On starting these channels the virus scanner will scan the infected messages and throw the error at the sender channel.

Sending virus within attachment

You can also try the virus scanner functionality with the attachment of another file with the main payload and try to send the message as described in the execution step.

1. Open the sender channel in edit model.

2. Under source tab Click on the Additional file(s).

3. Under File List, enter a name of your choice for each additional file.

4. Now add four different fields and its value.

Name Value

Additional_File.namePart ".xml"="_test.xml"

Additional_File.optional NO Additional_File.type BIN Additional_File.encoding UTF-8

For more information, see Specifying Additional Files in the Sender File Adapter.

5. The file XiPatternSenderFile_test.xml is the file attached with the main payload. For creation of attachment file, place the content(EICAR string) given below in a file and name it as XiPatternSenderFile_test.xml and place the file at sender location.

X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*

6. Save and activate.

7. Now start the channels to see scanning of the infected file.

8. After message flow on sender, you will see error thrown on sensing the virus:

Sending infected payload without activating virus scanner

1. Open the integrated configuration object <SID>_AAEX_FileSystem_XiPattern1 / XiPatternInterface1 / http://sap.com/xi/XI/System/Patterns

2. Switch to change mode ( ).

3. In tab Inbound Processing Tab, Go to the Virus Scan field and for the scenario specific, choose the option No Virus scan .(You can also try the Virus scan configuration at the Outbound Processing Tab) save and activate.

4. Start the channel and check whether the infected file is getting scanned or not on setting the No virus scan in The Integrated Configuration. The channels should be successfully executing without detecting virus in the file.

Sending message after deleting virus from the main payload and attachment and then retest

(27)

1. Edit sender communication channel and place file XiPatternSenderFile1.xml in the File name field and unmark the additional file option.

2. Start the communication channels consumed in the scenario. Now check whether the message is processed successfully. The channel should be successfully processed the message.

4 Variant 2: One Sender and Two Receivers using the 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.

4.1 Design Objects Used

In this variant the same interfaces are used as in variant 1. .

4.2 Configuring the Process Integration Scenario

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 of this scenario.

For more information, see Defining the Integrated Configuration.

Opening the Configuration Scenario

Perform the following steps to open the configuration scenario that you created in variant 1.

1. In the Integration Directory, open configuration scenario

XiPatternOneStepScenario_AAEX. To do so, in the Integration Directory navigation area, choose the tab page Scenarios and open the configuration scenario

XiPatternOneStepScenario_AAEX by double-clicking.

If you followed the configuration sequence suggested in this document, the configuration objects that were generated in variant 1 are displayed in the configuration scenario.

2. Change to Edit Mode.

3. Start the model configurator. To do so, press the button Model Configurator.

(28)

The model configurator loads the same process integration scenario as in variant 1.

Selecting the Component View

Check that the component view File2File_NoMapping is selected. If it is not, under

Configuration Steps, 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

Additionally, assign the application component Receiver the business system component

<SID>_AAEX_FileSystem_XiPattern3.

Configuring the Connection

The communication channels selected for variant 1 are displayed for the relation from sender communication component <SID>_AAEX_FileSystem_XiPattern1 and receiver component

<SID>_AAEX_FileSystem_XiPattern2. If this is not the case, select them again by using the input help.

For the relation from the sender component <SID>_AAEX_FileSystem_XiPattern1 and receiver component <SID>_AAEX_FileSystem_XiPattern3, proceed as follows:

 Assign the communication channel XiPatternChannel_FileSender (communication component <SID>_AAEX_FileSystem_XiPattern1) that you created previously to the sender component. To do so, position the cursor on the input field in the column Communication Channel (in the composite column Sender Business System Components for A2A) and call the input help ( ).

 Using the communication channel template, create a new communication channel for the receiver communication component <SID>_AAEX_FileSystem_XiPattern3. To do so, proceed as described in variant 1.

Generating the Configuration Objects

Proceed as described in variant 1. Once you have checked the generation log, close it and save the configuration scenario.

Manual Editing

Manually edit the new communication channel XiPatternChannel_FileReceiver for

communication component <SID>_AAEX_FileSystem_XiPattern3 as in variant 1. Under File Access Parameter in field Source Directory, enter the path for the file directory XiPattern3 (see 2.2.5).

Save the channel and execute the Channel Ping as described in the variant 1.

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.