SAP NetWeaver Process Integration 7...configuration steps that are necessary to execute the...

SAP NetWeaver Process Integration 7.31

Simple Use Cases for B2B AS2 & EDI Separator Using Integration Flow Configuration

Simple Use Cases for B2B AS2 & EDI Separator using Integration Flow Configuration

2

TABLE OF CONTENTS

1 Preface .............................................................................................................................................. 6 1.1 Constraints ....................................................................................................................................... 6 1.2 Definition .......................................................................................................................................... 6 1.3 Intended Audience ........................................................................................................................... 6 1.4 Structure ........................................................................................................................................... 6

2 Introduction and Prerequisites ...................................................................................................... 6 2.1 Introduction ...................................................................................................................................... 6 2.1.1 AS2 Adapter ...................................................................................................................................... 8 2.1.2 EDI Separator .................................................................................................................................... 8 2.1.3 EDI-XML Converters .......................................................................................................................... 8 2.1.4 SCN Articles ...................................................................................................................................... 8 2.2 Prerequisites .................................................................................................................................... 9 2.2.1 General Prerequisites ........................................................................................................................ 9 2.2.2 Providing the necessary User and Authorizations ........................................................................... 10 2.2.3 Setting up the Third party Tool Infrastructure (AS2 Connector) ...................................................... 10 2.2.4 Configuring the Certificates for authorization and authentication .................................................... 10 2.2.5 Setting Up the File Directories ......................................................................................................... 10 2.2.6 Adding Software Components to PI B2B ADDON product ............................................................. 11 2.3 Design Objects Used ..................................................................................................................... 12 2.3.1 Interface Objects .............................................................................................................................. 12 2.3.2 Mapping Objects .............................................................................................................................. 12 2.4 Working with NWDS ...................................................................................................................... 12 2.4.1 Setting Connection Parameters ....................................................................................................... 12 2.4.2 Opening Perspectives and Views .................................................................................................... 12 2.4.3 Connecting to the Systems .............................................................................................................. 13 2.4.4 Maintenance tool and B2B Seed File .............................................................................................. 13 2.5 Variant 1a: One Sender and one Receiver using the Advanced Adapter Engine Extended – Encryption and Signature with synchronous MDN .................................................................................... 14 2.6 Design Objects Used ..................................................................................................................... 14 2.6.1 Summary of Design Objects Used .................................................................................................. 15 2.7 Configuring the Process Integration Scenario ........................................................................... 15 2.8 Calling the Process Integration Designer ................................................................................... 15 2.9 Creating the Integration Flow ....................................................................................................... 15 2.10 Creating Channels ......................................................................................................................... 16 2.11 Saving and Activating the Configuration Objects ...................................................................... 19 2.12 Configuring the trading partner ................................................................................................... 19 2.12.1 Creating the trading partner ............................................................................................................. 19 2.13 Executing the Use Case ................................................................................................................ 19

3 Variant 1b : AS2 Adapter with EDI Converter (Plain XML and XML to Plain) .......................... 20 3.1 Design Objects Used ..................................................................................................................... 20 3.2 Configuring the Process Integration Scenario ........................................................................... 21 3.3 Calling the Process Integration Designer ................................................................................... 21 3.4 Creating the Integration Flow ....................................................................................................... 21 3.5 Creating Channels ......................................................................................................................... 21 3.6 Saving and Activating the Configuration Object ........................................................................ 22 3.7 Configuring the trading partner ................................................................................................... 22 3.8 Executing the Use Case ................................................................................................................ 22

4 Variant 2a: AS2 Adapter – Encryption, Signature and Compression of the message with Asynchronous MDN ...................................................................................................................................... 23 4.1 Design Objects Used ..................................................................................................................... 23 4.1.1 Summary of Design Objects Used .................................................................................................. 23 4.2 Configuring the Process Integration Scenario ........................................................................... 23 4.3 Calling the Process Integration Designer ................................................................................... 23


3

4.4 Creating the Integration Flow ....................................................................................................... 23 4.5 Creating Channels ......................................................................................................................... 24 4.6 Saving and Activating the Configuration Object ........................................................................ 25 4.1 Configuring the trading partner ................................................................................................... 25 4.1.1 Creating the trading partner on AS2 connector ............................................................................... 25 4.2 Executing the Use Case ................................................................................................................ 26

5 Variant 2b: AS2 Adapter – Encryption, Signature and Compression of the message with Asynchronous MDN and Creation of New XI Message. ............................................................................. 27 5.1 Design Objects Used ..................................................................................................................... 27 5.1.1 Summary of Design Objects Used .................................................................................................. 27 5.2 Configuring the Process Integration Scenario ........................................................................... 27 5.3 Calling the Process Integration Designer ................................................................................... 27 5.4 Creating the Integration Flow1 ..................................................................................................... 27 5.5 Creating Channels ......................................................................................................................... 28 5.6 Saving and Activating the Configuration Object ........................................................................ 29 5.7 Configuring the trading partner ................................................................................................... 29 5.7.1 Creating the trading partner on AS2 connector ............................................................................... 29 5.8 Creation of Integration Flow2 ....................................................................................................... 30 5.9 Creating Channels ......................................................................................................................... 30 5.10 Executing the Use Case ................................................................................................................ 31

6 Variant 3: AS2 Adapter – Decryption and Signature of the message without MDN Signature 32 6.1 Design Objects Used ..................................................................................................................... 32 6.1.1 Summary of Design Objects Used .................................................................................................. 32 6.2 Configuring the Process Integration Scenario ........................................................................... 32 6.3 Calling the Process Integration Designer ................................................................................... 32 6.4 Creating the Integration Flow ....................................................................................................... 32 6.5 Creating Channels ......................................................................................................................... 33 6.6 Saving and Activating the Configuration Objects ...................................................................... 35 6.7 Configuring the trading partner ................................................................................................... 35 6.7.1 Creating the trading partner on AS2 connector ............................................................................... 35 6.7.2 Adding test data to the configured trading partner .......................................................................... 36 6.8 Executing the Use Case ................................................................................................................ 36

7 Variant 4a: AS2 Adapter – No Decryption and No Signature of the message with Signed Async MDN ..................................................................................................................................................... 37 7.1 Design Objects Used ..................................................................................................................... 37 7.1.1 Summary of Design Objects Used .................................................................................................. 37 7.2 Configuring the Process Integration Scenario ........................................................................... 37 7.3 Calling the Process Integration Designer ................................................................................... 38 7.4 Creating the Integration Flow ....................................................................................................... 38 7.5 Creating Channels ......................................................................................................................... 38 7.6 Saving and Activating the Configuration Objects ...................................................................... 41 7.7 Configuring the trading partner ................................................................................................... 41 7.7.1 Creating the trading partner on AS2 connector ............................................................................... 41 7.7.2 Adding test data to the configured trading partner .......................................................................... 42 7.8 Executing the Use Case ................................................................................................................ 42

8 Variant 4b: AS2 Adapter – Duplicate message handling Feature in AS2 ................................ 42 8.1 Design Objects Used ..................................................................................................................... 43 8.2 Configuring the Process Integration Scenario ........................................................................... 43 8.3 Calling the Process Integration Designer ................................................................................... 43 8.4 Creating the Integration Flow1 ..................................................................................................... 43 8.5 Creating Channels ......................................................................................................................... 43 8.6 Creating the Integration Flow2 ..................................................................................................... 46 8.7 Creating Channels ......................................................................................................................... 46 8.8 Execution and Verification ............................................................................................................ 48


4

9 Variant 5: AS2, EDI Separator (ANSI X12 transaction sets 830, 856, 997) and EDI-XML Converter ........................................................................................................................................................ 49 9.1 Configuring the Integration Flows ............................................................................................... 50 9.1.1 Calling the Process Integration Designer ........................................................................................ 50 9.1.2 Creating the integration Flows ......................................................................................................... 50 9.1.2.1 Integration Flow 1: Sender: AS2 Adapter, Receiver: EDI Separator. .............................................. 50

9.1.2.2 Integration Flow 2: Sender: EDI Separator & EDI-XML Converter module, Receiver: File adapter 51


9.1.2.4 Integration Flow 4: Sender: EDI Separator, Receiver: AS2 adapter ............................................... 52

9.1.3 Configuring the integration Flows .................................................................................................... 52 9.1.3.1 Integration Flow 1: Sender: AS2 Adapter, Receiver: EDI Separator. .............................................. 52



9.1.3.4 Integration Flow 4: Sender: EDI Separator, Receiver: AS2 adapter ............................................... 58

9.2 Configuring the trading partner ................................................................................................... 61 9.2.1 Creating the trading partner on AS2 connector ............................................................................... 61 9.2.2 Adding test data to the configured trading partner .......................................................................... 62 9.3 Saving and Activating the Configuration Objects ...................................................................... 62 9.4 Executing the Use Case ................................................................................................................ 62

10 Variant 6: AS2, EDI Separator (ANSI X12 transaction sets 830, 856, 997), EDI-XML Converter & Conversion Using the Maintenance Tool ................................................................................................ 70 10.1 Configuring the Integration Flows ............................................................................................... 70 10.1.1 Integration Flow 3: Sender: EDI Separator & EDI-XML Converter module, Receiver: File adapter 70 10.2 Saving and Activating the Configuration Objects ...................................................................... 70 10.3 Executing the Use Case ................................................................................................................ 71

11 Variant 7: AS2, EDI Separator (EDIFACT: DELFOR and DESADV) and EDI-XML Converter . 71 11.1 Configuring the Integration Flows ............................................................................................... 73 11.1.1 Calling the Process Integration Designer ........................................................................................ 73 11.1.2 Creating the integration Flows ......................................................................................................... 73 11.1.2.1 Integration Flow 1: Sender: AS2 Adapter, Receiver: EDI Separator. .......................................... 73



11.1.2.4 Integration Flow 4: Sender: EDI Separator, Receiver: AS2 adapter ........................................... 74

11.1.3 Configuring the integration Flows .................................................................................................... 75 11.1.3.1 Integration Flow 1: Sender: AS2 Adapter, Receiver: EDI Separator. .......................................... 75



11.1.3.4 Integration Flow 4: Sender: EDI Separator, Receiver: AS2 adapter ........................................... 81

11.2 Configuring the trading partner ................................................................................................... 84 11.2.1 Creating the trading partner on AS2 connector ............................................................................... 84 11.2.2 Adding test data to the configured trading partner .......................................................................... 85 11.3 Saving and Activating the Configuration Objects ...................................................................... 85 11.4 Executing the Use Case ................................................................................................................ 85

12 Variant 8: AS2, EDI Separator (Odette: AVIEXP and DELINS) and EDI-XML Converter ......... 92 12.1 Configuring the Integration Flows ............................................................................................... 92


5

12.1.1 Calling the Process Integration Designer ........................................................................................ 92 12.1.2 Creating the integration Flows ......................................................................................................... 92 12.1.2.1 Integration Flow 1: Sender: AS2 Adapter, Receiver: EDI Separator. .......................................... 92



12.1.3 Configuring the integration Flows .................................................................................................... 93 12.1.3.1 Integration Flow 1: Sender: AS2 Adapter, Receiver: EDI Separator. .......................................... 93



12.2 Configuring the trading partner ................................................................................................... 99 12.2.1 Creating the trading partner on AS2 connector ............................................................................... 99 12.2.2 Adding test data to the configured trading partner ........................................................................ 100 12.3 Saving and Activating the Configuration Objects .................................................................... 100 12.4 Executing the Use Case .............................................................................................................. 100

13 Variant 9: AS2, EDI Separator (VDA: 4905 and 4913) and EDI-XML Converter ..................... 101 13.1 Configuring the Integration Flows ............................................................................................. 101 13.1.1 Calling the Process Integration Designer ...................................................................................... 101 13.1.2 Creating the integration Flows ....................................................................................................... 101 13.1.2.1 Integration Flow 1: Sender: AS2 Adapter, Receiver: EDI Separator. ........................................ 101



13.1.3 Configuring the integration Flows .................................................................................................. 102 13.1.3.1 Integration Flow 1: Sender: AS2 Adapter, Receiver: EDI Separator. ........................................ 102



13.2 Configuring the trading partner ................................................................................................. 107 13.2.1 Creating the trading partner on AS2 connector ............................................................................. 107 13.2.2 Adding test data to the configured trading partner ........................................................................ 108 13.3 Saving and Activating the Configuration Objects .................................................................... 109 13.4 Executing the Use Case .............................................................................................................. 109


6

1 Preface

1.1 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. 1.2 Definition This manual describes simple application cases using Integration Flow configuration for B2B and all the configuration steps that are necessary to execute the application cases on the basis of SAP NetWeaver 7.31. 1.3 Intended Audience This manual is intended to be used by both technology and application consultants. 1.4 Structure The structure of this document follows the sequence of steps required to configure and run the use cases.

2 Introduction and Prerequisites

2.1 Introduction Use cases are based on simple examples that enable you to learn the main features of the B2B AS2 Adapter Configuration and EDI Separator Configuration for the 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 scope of this test case is to test the following features of the AS2 adapter and EDI-Separator.

AS2 Adapter

Verification of signature for ensuring non-repudiation

Signed MDN

Compression of message payload

Encryption of message payload for message integrity

Signing of message for non-repudiation

Encryption of message payload for message integrity

Synchronous signed MDN with request and verification of MIC (Message Integrity Check) and signing

Decryption of message payload for verifying message integrity

Separating the combined message by the use of EDI Separator adapter EDI Separator

ANSI X.12 message with Transaction Set Identifier Codes and Interchange Sender/Receiver Id specified

Edifact with message type, version, release number, interchange sender and receiver identification and code qualifier specified

Odette with message type, version number, Interchange sender and recipient identification and code qualifier specified.

VDA with message type, customer and vendor number specified

Acknowledgement (positive) message generation for ANSI X.12 message type The following use case variants for the Advanced Adapter Engine Extended are available at present:


7

Variant Description

Variant 1: One sender and one receiver-with synchronous MDN

Represents message exchange between one sender and one receiver on the Advanced Adapter Engine Extended (AEX) with encryption and signature of the message followed by sending the synchronous MDN. The message processing is done locally on the Advanced Adapter Engine Extended.

Variant 2:

One sender and one receiver-with Asynchronous MDN

Represents message exchange between one sender and one receiver on the Advanced Adapter Engine Extended (AEX) with encryption, signature and compression of the message followed by sending the Asynchronous MDN. The message processing is done locally on the Advanced Adapter Engine Extended.

Variant 3:

One sender and one receiver- with unsigned synchronous MDN

Represents message exchange between one sender and one receiver on the Advanced Adapter Engine Extended (AEX) with decryption and signature of the message followed by sending unsigned the synchronous MDN. The message processing is done locally on the Advanced Adapter Engine Extended.

Variant 4:

One sender and two receivers – with signed synchronous MDN

Represents message exchange between one sender and one receiver on the Advanced Adapter Engine Extended (AEX) without decryption and signature of the message followed by sending the synchronous MDN. The message processing is done locally on the Advanced Adapter Engine Extended.

Variant 5:

AS2, EDI Separator (transaction set 830, 856, 997) and EDI-XML Converter (X.12 to XML)

Represents message exchange parting from a trading partner as ASC X12 message containing two message types (transaction sets), being converted into XML and split by the EDI separator. Additionally an acknowledgment message (transaction code 997) is generated and sent back to the trading partner via AS2 adapter

Variant 6:

AS2, EDI Separator (transaction set 830, 856, 997), EDI-XML Converter (XML to X.12) & Conversion Using the Maintenance Tool

Based on the scenario in variant 5 by adding the module converter to one of the file receivers and using the maintenance tool to convert one of the received messages to xml and back to X.12.

Variant 7: AS2, EDI Separator (EDIFACT: DELFOR and DESADV) and EDI-XML Converter

On this variant, an EDIFACT multi-message containing two message types (DELFOR and DESADV) is sent by a trading partner. The message is split by the EDI Separator, converted into XML and sent to a file receiver.

Variant 8: AS2, EDI Separator (Odette: AVIEXP and DELINS) and EDI-XML Converter

On this variant, an Odette multi-message containing two message types (AVIEXP and DELINS) is sent by a trading partner. The message is split by the EDI Separator, converted into XML and sent to a file receiver.

Variant 9: AS2, EDI Separator (VDA: 4905 and 4913) and EDI-XML Converter

On this variant, a VDA multi-message containing two message types (4905 and 4913) is sent by a trading partner. The message is split by the EDI Separator, converted into XML and sent to a file receiver.

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

Working with the AS2 protocol and AS2 adapter

Configuring The EDI Separator adapter and splitting different types of messages

Using the EDI-XML Convertor module and maintaining control data on the maintenance tool


8

Working with the Process Integration Designer in NWDS: Configuring simple scenarios and understanding created configuration objects

Working with the runtime: Executing the use cases and checking the results by using the monitoring tools

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.

2.1.1 AS2 Adapter The AS2 Adapter enables data transfer using the AS2 protocol. AS2 (stands for Applicability Statement 2) is a protocol is used to transport data securely and reliably over the Internet, based on HTTP and S/MIME. The partners are always connected via the tried and tested HTTP(s) protocol. The AS2 process is a clear choice thanks to its effective firewall administration capability, signature, encryption, return receipt/acknowledgement (MDN) and rapid response times. Detailed information on the AS2 protocol can be found in RFC 4130. 2.1.2 EDI Separator The EDI Separator is a component providing the feature of splitting incoming mass EDI messages into single messages. It is implemented as a PI Adapter and therefore can be used on sender and receiver adapter channels that are configured to perform the splitting function. Furthermore, the adapter controls the “content based receiver determination”. This feature of the adapter offers the possibility to use content-based routing (message identification) and split mass messages according to interfaces based on message type and partner. The SAP NW PI EDI Separator adapter supports 4 EDI formats which are:

ANSI ASC X12

EDIFACT

ODETTE

VDA For at least one of the variants described in this document, the format ANSI ASC X12 will be used. Configuration details will be explained on the corresponding variant. 2.1.3 EDI-XML Converters EDI-XML converters are set of modules which convert from EDI formats to XML and vice-versa. All format-specific conversions are called via own modules. On this simple use case, The ASC X12 message is converted using the module called “localejbs/X12ConverterModule”. This Java-Bean is able to recognize automatically whether it is an X12 or an XML message and can process them correspondingly. A maintenance tool is available via web, where the control data for the conversions can be maintained and conversions can be made. More information on

2.4.4 2.1.4 SCN Articles Additional information can be found on the respective articles published on SAP Community Network:

Link Title

AS2 Adapter Learning Series SAP NetWeaver Process Orchestration, business to business add-on 2c AS2 Adapter

http://www.ietf.org/rfc/rfc4130.txthttp://scn.sap.com/docs/DOC-28941


9

EDI Separator Adapter

Learning Series SAP NetWeaver Process Orchestration, business to business add-on 2f EDI Separator Adapter

All in one guide for Add-on Solutions

All in one Guide ADD-On Solutions for SAP NetWeaver Process Orchestration

2.2 Prerequisites 2.2.1 General Prerequisites To configure and execute the use cases, SAP NetWeaver with usage type 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 SAP NetWeaver 7.31.

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. You have imported the content for the Enterprise Services Repository corresponding to the latest support package/patch.

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/System/Patterns.

3. You have configured SAP NetWeaver Process Integration.

Configuration of SAP NetWeaver Process Integration

4. You have configured the System Landscape Directory (SLD).

Configuring, Working with and Administering System Landscape Directory

5. You have installed the NetWeaver Developer Studio.

You can find the corresponding guides on SAP Service Marketplace at https://service.sap.com/installnw73 Under Installation - Standalone Engines and Clients Installation – Clients Inst. and Update - SAP NetWeaver Developer Studio 7.3 EHP1 (SP04).

6. You have installed the SFTP & PGP Add-on.

You can download the B2B add-on from the following location: http://service.sap.com/swdc -> Browse our Download Catalog - > -> Installation and Upgrades -> SAP NetWeaver and complementary products -> PI SFTP PGP ADDON.

7. You have installed the PI B2B Add-on.

You can download the B2B add-on from the following location: http://service.sap.com/swdc -> Browse our Download Catalog - > -> Installation and Upgrades -> SAP NetWeaver and complementary products -> PI B2B ADDON

http://scn.sap.com/docs/DOC-28948http://scn.sap.com/docs/DOC-28948http://scn.sap.com/docs/DOC-26612http://scn.sap.com/docs/DOC-26612http://scn.sap.com/docs/DOC-26612https://websmp206.sap-ag.de/instguidesnw73https://websmp206.sap-ag.de/instguidesnw73http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=00836200&_NLANG=Ehttp://help.sap.com/saphelp_nw73/helpdata/en/48/a9b8c87e28674be10000000a421937/content.htmhttp://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/b6847496655295e10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/b6847496655295e10000000a42189b/frameset.htmhttps://service.sap.com/installnw73


10

2.2.2 Providing the necessary User and Authorizations To log on to the AEX system to configure the simple use cases, you have to create a user XIDEMO with the following roles in the Advanced Adapter Engine Extended:

SAP_XI_CONFIGURATOR _J2EE

SAP_XI_MONITOR_J2EE 2.2.3 Setting up the Third party Tool Infrastructure (AS2 Connector) In this document all the scenarios described are based on the third party tool called AS2 Connector by /n Software. This third party software has been used just as an example for configuration of trading partners for the purpose of sending and receiving the AS2 message payloads. You are free to use any third party software and configure your scenario based on AS2 adapter. The third party software can change in your case. The scenarios described in this document are based on /n Software AS2 connector, therefore you need to configure the trading partners which will be used for the communication with the PI system on the variants described in this document. Please note that the PIs public Key certificate is used by the AS2 connector in some variants and therefore should be present on the system hosting the AS2 connector and when configuring a trading partner the path to the PI public key certificate will be needed. E.g. “/PI_Test-cert.crt” 2.2.4 Configuring the Certificates for authorization and authentication Some of the AS2 scenarios need encryption, decryption and signing of the payload, for this 2 pairs of keys (public & private key pair) and 2 public key certificates one each for each partner are needed. The public-private key pair and public key certificates can be generated in NWA. The scenarios described on this document will use (if any) the public/private key pairs listed on the following table.

For more information you can read the relevant articles as listed on 2.1.4

NW Key Storage View Entry Description

AS2_CERTIFICATE Partner_Test-cert Partners Public Key Certificate

AS2_CERTIFICATE PI_Test-cert Own Public Key Certificate

AS2_KEYSTORE PI_Test Own Private Key

2.2.5 Setting Up the File Directories The variants are based on a simple system landscape that comprises various different file systems (on the host of the SAP system on which the Advanced Adapter Engine Extended is installed). When the use cases are executed, files are moved between file directories and/or the third party software. 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 PI Designer. 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 the sub directories

Inputfiles and Receiver

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 further sub directories in the sub directory Inputfiles. Suggested names: Tradacoms, ANSI, Odette, Edifact.


11

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.

4. Copy the files to their respective directory under Inputfiles:

ZB2B_ANSI.xml

ZB2B_Tradacoms.xml

ZB2B_Odette.xml

ZB2B_Edifact.xml

ZB2B_input.txt

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.

5. Create one more directory: AS2-EDISEP

6. Under AS2-EDISEP create the following sub-directories: 830, 856, output-edifact, output-

odette and output-vda

7. Additionally, the following files will be needed for sending messages from the trading partner:

B2B_ansix12SenderMessage_830_856.txt

B2B_ansix12SenderMessage_830_856_error.txt

B2B_edifactSenderMessage_DELFOR_DESADV.txt

B2B_edifactSenderMessage_DELFOR_DESADV_error.txt

B2B_odetteSenderMessage_AVIEXP3_DELINS3.txt

B2B_vdaSenderMessage_4905_4913.txt

2.2.6 Adding Software Components to PI B2B ADDON product

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)://:/dir.

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

3. Log on using your user you created.

4. On the initial screen of the SLD, choose Products.

5. Filter for PI B2B ADDON product and check for B2B MAPPING KIT 1.0 software component version is available in Software Components tab. If not proceed with below associations steps.

6. On the initial screen of the SLD, choose CIM Instances.

7. Filter for B2B MAPPING KIT 1.0 for class Software Component Version.

8. Click on New Association.

9. Filter for *B2B* with Association Type Software Features Software Component and Associated Class as Product Instance.

10. Select PI B2B ADDON 1.0: JAVA COMPONENTS and click on Associate. A message for successful association is displayed.

11. Now software component version B2B MAPPING KIT 1.0 will be available in list of Software Components for PI B2B ADDON product.

Business Components used in the scenarios :

http://scn.sap.com/docs/DOC-26566http://scn.sap.com/docs/DOC-26566


12

__B2B_BC_AS2_V1

__B2B_BC_AS2_V2

__B2B_BC_AS2_V2b

__B2B_BC_AS2_V3

__B2B_BC_AS2_V4

__B2B_BC_AS2_EDISEP_V5_01













2.3 Design Objects Used 2.3.1 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. 2.3.2 Mapping Objects If the interfaces at the sender and receiver are different, a mapping is required. The specific design objects will be listed in the specific variants below 2.4 Working with NWDS 2.4.1 Setting Connection Parameters If not done yet, open the SAP NetWeaver Developer Studio. Set the connection data for accessing the Integration Directory under the menu Process Integration → Change Preferences. The connection details to the Advanced Adapter Engine Extended System have to be maintained using URL or AEX-Host and AEX-Port, click on “test connection” to verify if the connection is successful. Click on Apply for saving changes. On the same menu (Process Integration → Change Preferences), under the following path: Web Services → Enterprise Services Browser, set the connection details for the ESR System using ESR-Host and ESR-Port. Once done, click on Apply and exit the menu by clicking on OK. 2.4.2 Opening Perspectives and Views For creating Integration Flows, the Process Integration Designer perspective is needed. To call the SAP Process Integration Designer perspective, follow the menu path: Window → Open Perspective → Other → SAP Process Integration Designer. Please note that not all views of this perspective (shown as tabs on the left side of the NWDS) will be opened by default. If missing you can manually open them by using the Show view icon located on the bottom-left corner of the NWDS. After selecting one view you can change its tab position using drag & drop with the mouse. You will need at least the following views: PI Explorer, Enterprise Services Browser, PI Runtime Explorer and Change Lists.


13

Optionally, you can also call the “Enterprise Services Repository” Perspective: To call the Enterprise Service Browser in the SAP NetWeaver Developer Studio follow the menu path Window → Open Perspective → Other → Enterprise Services Repository. Once done, you can quickly switch between perspectives by selecting the desired one on the top-right corner of the NWDS. 2.4.3 Connecting to the Systems Before proceeding to connection ensure that you have set the connection parameters as described previously. On the SAP Process Integration Designer perspective connect to the systems using the common logon

option by clicking the connect icon located on the top toolbar ( ). Provide your credentials on the pop-up window. This will connect automatically to both, the AEX and the ESR systems.

On the connection pop-up window, you can select the check-box “Use common credentials for directory and repository” if your credentials are the same for both systems.

Alternatively, you can also use the common logon using the Menu Process Integration → Connect There is also the possibility of connecting to the ESR only. If you would like to connect only to the ESR, use the connect icon located on the Enterprise Service Browser view. 2.4.4 Maintenance tool and B2B Seed File SAP PI B2B, specifically the XML converter uses two different types of tables B2B_X12_CTRL_* (contain rules for creating the nesting structure for the conversion of the messages) and B2B_X12_DEF_* manage information for generating the XML Definition Schemes (XSD‟s). For the variant described in this document, we only have to ensure that the tables are populated. This is done using the maintenance tool for EDI Content Manager available at B2B Integration Cockpit. Follow the next steps:

Open B2B Integration Cockpit (proceed with user credentials if prompted): https://host:port/webdynpro/resources/sap.com/b2b~home/B2BHome

Then click on EDI Content Manager.

Please check if the data is already available: Go to tab “Ansi X.12” – Tables - B2B_X12_CTRL_IF. If the table is empty you need to import the B2B seed file. If not, you can skip the next steps.

Copy the B2B seed file locally

Import the “B2B seed file”: On the maintenance tool, go to tab “Ansi X.12” – Tables – Import, browse for your local copy of the B2B seed file and click on „Import“

Since the file is larger than 20 MB, you will get the following warning message:

https://host:port/webdynpro/resources/sap.com/b2b~home/B2BHome


14

After a couple of minutes the import will be complete. Please note that no confirmation will be displayed. If you want to see the import result, you can have a look at the import log file. The location for the log file is displayed on the previous warning message. After the import, the control data is available on the tables:

Repeat the same steps for Plain, VDA, Odette, Tradacoms and EDIFACT.

2.5 Variant 1a: One Sender and one Receiver using the Advanced Adapter Engine Extended – Encryption and Signature with synchronous MDN

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

One sender (file directory Inputfiles) sends a message to one receiver. Hereby, the message is

exchanged between sender and receiver adapter by using one Advanced Adapter Engine Extended. Mapping is executed between the outbound and inbound interface and the message is being converted into

the Tradacoms type in this variant.

2.6 Design Objects Used

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

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.

The following describes all the objects that describe the message exchange in this variant in turn. There are two possibilities to learn more about the design objects, the Enterprise Services Builder and the Enterprise Service Browser. To call the Enterprise Service Browser in the SAP NetWeaver Developer Studio first set the connection data for accessing the Enterprise Services Builder under the menu Window → Preferences. Under Web Services


15

→ Enterprise Services Browser the connection details to the ESR System have to be maintained using ESR-Host and ESR-Port.

1. To call the Enterprise Services Browser follow the menu path Window → Open Perspective → Other → Enterprise Services Repository.

2. Use the Connect Button to connect to the Enterprise Services Builder. 3. In the navigation area, open the software component B2B TOOLKIT software component version

B2B TOOLKIT 1.0, and namespace http://sap.com/xi/XI/AS2 4. Open the node and ensure that the adapter metadata for AS2 is present under the namespace. 5. Again ensure that the software component B2B MAPPING KIT 1.0 is available, as this contains the

mapping objects which will be consumed in the variants described

All the design objects can also be checked directly in the Enterprise Services Builder. To call it call the Process Integration Tools Page http://:/dir and from there open the Enterprise Services Builder.

2.6.1 Summary of Design Objects Used The design objects used are summarized once more in the following table

Object Type (Name) Description

Service Interfaces (INVOIC.INVOIC02

SI_INBOUND_EDI_TRADACOMS_INVOIC)

Specifies the communication mode (asynchronous) and references the message type used.

Message Type (INVFILTO9) Message Type (INVFILTO9)

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

2.7 Configuring the Process Integration Scenario In configuration, you use the design objects in the process integration scenario for the 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 from the Process Integration Designer. You perform the following configuration steps in the SAP Process Integration Designer for the Advanced Adapter Engine Extended. 2.8 Calling the Process Integration Designer Open the SAP NetWeaver Developer Studio, connect and open the Process Integration Designer view as

described in 2.4 2.9 Creating the Integration Flow Perform the following steps to create a new integration flow.

1. In the Process Integration Designer choose New → Integration Flow ( ). 2. In category Enterprise Integration Patterns select the Point-to-Point Pattern and set the name and ID

of the Integration Flow as AS2_Variant1_IntFlowScenario_.

3. Choose Next. 4. To assign Business component to sender, right click on the sender -> New Business component ->

name as __B2B_BC_AS2_V1-> Click Finish.

5. As Interface select INVOIC.INVOIC02.

6. In Tab Receiver Systems as Receiver component select the Business component __B2B_BC_AS2_V1 using the input help for the Receiver Name.

7. As Receiver Interface select SI_INBOUND_EDI_TRADACOMS_INVOIC.

8. Choose Finish.


16

9. The integration Flow will be displayed in a graphical overview.

10. On the line representing the message flow to receiver __B2B_BC_AS2_V1 in the

context menu select Add Mapping. 11. Select the mapping object in the graphical view. The properties tab will open.

12. Using the Browse functionality select the operation mapping OM_INVOIC02_TO_INVOICTO9.

2.10 Creating Channels 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.

1. In the graphical editor, right-click on channel for the sender component. Select Apply Channel Template. The Choose Channel Template screen will open.

2. Select the template B2B_AS2_FileSender of software component version B2BTOOLKIT 1.0 and

press OK. Change to the channel view. 3. In tab Adapter Specific under File Access Parameter in the Source Directory field, enter the path in

the file directory that you defined previously (see 2.2.3). In the case of the sender communication channel, enter the whole path for the file directory Inputfiles. Example: \\host\\AS2\Inputfiles\Tradacoms.

4. As File Name Tradacoms.xml should be set automatically.

5. In the graphical editor, right-click on channel for the receiver component. The channel view will open

and then name the channel, as in this case named it as B2B_AS2_ReceiverAS2_Variant1.

6. In adapter type field browse and select AS2 adapter.

7. Go to Adapter-Specific tab and under General tab fill the details as given below in the table

Header Field Field Name Value

Recipient Recipient URL

e.g. http://host:port/Receiver.aspx

Basic Authentication

Username

Password

Checked Use your credentials

Message Filename File_var1.txt

MessageID left MessageID right

.*

.*

Own AS2Name

AS2 name which is transmitted in the AS2 message as AS2-From-Parameter

e.g. AS2___var01


17

Recipient AS2 Name

AS2 name which is transmitted in the AS2 as AS2-To-Parameter e.g. testas2

Own email- address

The email address which is transmitted in the AS2 message as sender. e.g. @sap.com

Message subject The message subject which is transmitted in the AS2 message as sender. e.g. AS2_Scenario_sign_enc

Content-Type Content type with which the message is marked. application/edi-x12

Charset

Charset conversion

Source encoding

Destination encoding

Checked UTF-8 UTF-8

8. Navigate to the tab Signature and Encryption and fill the details as given below in the table:

Header Field Field Name Value

Signature Sign message View to own public key certificate

Check the sign message

The NWA key-storage view in the sending partner (SAP PI -initiator), which contains the self (own) public key certificate e.g. AS2_CERTIFICATE / PI_Test-cert for both (view and alias)

Alias of own public key certificate

The alias (or name) under which the self (own) public key certificate is stored See above

View to own private key The NWA key-storage view in the sending partner (SAP PI - initiator),


18

which contains the self (own) private key e.g. AS2_KEYSTORE / PI_Test for both (view and alias)

Alias of own private key The alias (or name) under which the self (own) private key is stored see above

Encryption Encrypt message Check the encrypt message box Checked

Algorithm The encryption algorithm to be used (default is AES 128. The other available values are AES 192, AES 256, 3DES and RC2 3DES

View to recipient‟s public key certificate

The NWA key-storage view in the sending partner (SAP PI- initiator), which contains the receiving partner‟s (responder) public key certificate AS2_CERTIFICATE / Partner_Test-cert

View to recipient‟s public key certificate

The alias (or name) under which the receiving partner‟s (responder) public key certificate is stored AS2_CERTIFICATE / Partner_Test-cert

9. Now go to MDN tab and give the details as below:

HEADER FIELD FIELD NAME VALUE

MDN Message Delivery Notification

Select Synchronous

Verify MIC Request Signing Verify Signature

Checked Checked Checked

View to signer‟s public key certificate

The NWA key-storage view in the sending partner (SAP PI- initiator), which contains the receiving partner‟s (responder) public key certificate AS2_CERTIFICATE / Partner_Test-cert


19

Alias of signer‟s public key certificate

The alias (or name) under which the receiving partner‟s (responder) public key certificate is stored

AS2_CERTIFICATE / Partner_Test-cert

1. Go to Module Tab and Add Converter module Tradacoms converter

“localejbs/GenericConverterModule”. For adding the converter module bean click on the

Add button. Move the GenericConverterModule module bean to the first position by clicking on

the Move Up button which is present at the right hand side. The final screen should look like as

given below:

2.11 Saving and Activating the Configuration Objects In the following steps, you save the integration flow with all its objects and activate it for the runtime.

1. Save the Integration Flow by pressing the save button ( ). 2. Use the Activate entry in the context menu of the integration flow

AS2_Variant1_IntFlowScenario_ to activate the configuration. 3. Use the Deploy entry in the context menu of the integration flow

AS2_Variant1_IntFlowScenario_ to deploy it in the runtime. 2.12 Configuring the trading partner 2.12.1 Creating the trading partner 2.13 Executing the Use Case You perform the following steps to check that the use case is executed without errors. Here the whole execution is described on the basis of third party /n software . In this variant the third party has been used for receiving the message . Third party can vary in your case . For the configuration of third

party in /n software please refer the section 2.2.3.

1. On the host of the Advanced Adapter Engine Extended, open the file directory Tradacoms. 2. Rename the file ZB2B_Tradcoms.xml as B2B_Tradcoms.xml. 3. The File adapter is designed in a way that a file with exactly this name is recognized and moved

from the source directory to the AS2 Recipient 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.

4. Open the third party software (In this case /n software) http://host:port/Default.aspx 5. Go to Incoming Tab select the trading partner “SAPPI___01”. The tab content

shows the successfully received messages.

6. Also the “Logs” tab shows the logs of the incoming messages (successful transmissions and errors if any) and the MDN requested by the sender will be available in the “Logs”.

OR

http://host:port/Default.aspx


20

7. As the third party software will be installed in a server. You can also go to the file structure of the server where the third party is installed and can also check the Incoming file on the basis of the party.

8. Open the received file and compare with the original file ZB2B_Tradcoms.xml and verify the content

of the received file. Received File can be found on: \\host\as2data\AS2___var01\Incoming The file must have been changed to tradacoms format when this variant is executed.

Furthermore, you can check the processing of the message in monitoring. You can do this in channel and message monitoring. To do this, proceed as follows: Channel Monitoring:

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

2. Choose Adapter Engine → Communication Channel Monitor 3. Use appropriate filter criteria to restrict the number of channels displayed. On the very right hand

side select Advanced to get all possible filter criteria displayed. To select your channels, put in the channel ID (you can find it in the channel editor screen) into the communication channel field, press Go and select your sender channel from the list.

4. Check that the channel is running without error. 5. In the Processing Details section you can find the processing logs and the links to the processed

messages. The link can be followed to get the message details. 6. In the processing log you can see the encryption and signing of the message has been done as you

have chosen these features in the scenario. Message Monitoring:

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

2. Choose Adapter Engine → Message Monitor. 3. Select Database. 4. Use appropriate filter criteria to restrict the number of XML messages displayed (for example, the

processing period). On the very right hand side select Advanced to get all possible filter criteria displayed and open the Message Header Data section. To select using your Integration Flow name put in the Integration Flow name into the field Integration Flow.

5. Choose Go. 6. The system displays the selected messages in a table. You want to locate the messages that were

sent during execution. 7. Select the message to be displayed by selecting the appropriate radio button and then choose Open

Message. 8. The tab Payloads displays the message contents for the various versions of the message during

processing.

Note: This scenario described in this variant contains encryption and signing of message. You can also try with different combination like without signing and with encryption or with signing and with encryption option and test the scenario.

3 Variant 1b : AS2 Adapter with EDI Converter (Plain XML and XML to Plain)

This variant enables you to configure and execute: One sender (file directory Inputfiles) sends a message to one receiver. Hereby, the message is exchanged between sender and receiver adapter by using one Advanced Adapter Engine Extended and the EDI Converter has been used in the scenario which will convert the message into Plain Message. 3.1 Design Objects Used To call the ESR proceed as outlined in variant 1.

file://host/as2data/AS2_%3cSID%3e_%3cUser-ID%3e_var01/Incomingfile://host/as2data/AS2_%3cSID%3e_%3cUser-ID%3e_var01/Incoming


21

3.2 Configuring the Process Integration Scenario In configuration, you use the design objects in the process integration scenario for the 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 from the in the Process Integration Designer. You perform the following configuration steps in the SAP Process Integration Designer for the Advanced Adapter Engine Extended. 3.3 Calling the Process Integration Designer Follow the procedure mentioned in variant1. 3.4 Creating the Integration Flow Perform the following steps to create a new integration flow.


of the Integration Flow as AS2_Variant1b_Integration_FlowScenario. 3. Choose Next. 4. As Sender Business componet select the Business component

__B2B_BC_AS2_V1 you imported from SLD using the Browse… button.

5. As Interface select XiPatternInterface1.

6. In Tab Receiver Systems as Receiver componet select the Business component

__B2B_BC_AS2_V1 using the input help for the Receiver Name.

7. As Receiver Interface select XiPatternInterface1.

8. Choose Finish. 9. The integration Flow will be displayed in a graphical overview.



2. Select the template XiPatternChannel_FileSender of software component version SAP BASIS

7.31 and press OK. Change to the channel view. 3. In tab Adapter Specific under File Access Parameter in the Source Directory field, enter the path in

the file directory that you defined previously (see 2.2.6). In the case of the sender communication channel, enter the whole path for the file directory Inputfiles. Example: ../../../../SYS/global/Connectivity_Test/B2B/AS2/Inputfiles.

4. As File Name AS2_Converter.txt should be set.

5. Go to the Module tab and Add Odette converter “localejbs/PlainConverterModule”.

For adding the converter module bean, click on the Add button. Move the converter module bean to

the first step by clicking on the Move Up button which is present at the right hand side. The final

screen should look like as given below:


22


and then name the channel, as in this case named it as B2B_AS2_ReceiverAS2_Var1.


8. Go to Adapter-Specific tab and under General tab fill the details as given in the variant1 table.

Uncheck the characterset conversion check box.

9. Navigate to the tab Signature and Encryption and fill the details as given in the variant1 table.

10. Now go to MDN tab and give the details as given in variant1. Note: An MDN (Message Delivery Notification) is a functional acknowledgement of receipt generated by the receiving party to positively or negatively acknowledge the success/failure/error in receipt of the original AS2 message.

11. Now go to Module tab and similarly add converter module “localejbs/PlainConverterModule” as given below

3.6 Saving and Activating the Configuration Object Proceed as described in variant1. 3.7 Configuring the trading partner You can reuse the trading partner that was created and configured in variant 1. 3.8 Executing the Use Case Here the whole execution is described on the basis of third party /n software . In this variant the third party has been used for receiving the message . Third party can vary in your case . For the configuration of third

party in /n software please refer the section 2.2.3. 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 Inputfiles.

2. Rename the file ZAS2_Converter.txt as AS2_Converter.txt

The File adapter is designed in a way that a file with exactly this name is recognized and moved from the source directory to the AS2 Recipient 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 third party software (In this case /n software) http://host:port/Default.aspx 4. Go to Incoming Tab select the trading partner “SAPPI___01” (created in variant 1).

The tab content shows the successfully received messages.

5. Also the “Logs” tab shows the logs of the incoming messages (successful transmissions and errors if any) and the MDN requested by the sender will be available in the “Logs”.

OR

6. As the third party software will be installed in a server. You can also go to the file structure of the server where the third party is installed and can also check the Incoming file on the basis of the party.(Please refer the section 2.2.6 for checking the file).

http://host:port/Default.aspx


23

7. Open the received file and compare with the original file ZAS2_Converter.txt and verify the

content of the received message should be same and the format of the received message will be Plain . The size of the file should be compressed (size of the format should be lesser than the original file) when this variant is executed.

Furthermore, you can check the processing of the message in monitoring. You can do this in channel and message monitoring. To do this, proceed as given in variant1.

4 Variant 2a: AS2 Adapter – Encryption, Signature and Compression of the message with Asynchronous MDN

This variant enables you to configure and execute: One sender (file directory Inputfiles) sends a message to one receiver. Hereby, the message is exchanged between sender and receiver adapter by using one Advanced Adapter Engine Extended and the mapping used in the scenario will convert the message into the ANSI type. 4.1 Design Objects Used To call the ESR proceed as outlined in variant 1. 4.1.1 Summary of Design Objects Used The design objects used are summarized once more in the following table.



SI_INBOUND_EDI_ANSIX12_INVOICE)


Message Type (ASC810_004010) Describes the message sent at runtime and references the data type used.

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

4.2 Configuring the Process Integration Scenario In configuration, you use the design objects in the process integration scenario for the 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 from the in the Process Integration Designer. You perform the following configuration steps in the SAP Process Integration Designer for the Advanced Adapter Engine Extended. 4.3 Calling the Process Integration Designer Follow the procedure mentioned in variant1. 4.4 Creating the Integration Flow Perform the following steps to create a new integration flow.


of the Integration Flow as AS2_Variant2_IntFlowScenario_ 3. Choose Next. 4. To assign Business component to sender right click on the sender -> New Business component ->

name as __B2B_BC_AS2_V2-> Click Finish.


24



7. As Receiver Interface select SI_INBOUND_EDI_ANSIX12_INVOICE.


10. On the line representing the message flow to receiver __B2B_BC_AS2_V2 in the

context menu select Add Mapping. 11. Select the mapping object in the graphical view. The properties tab will open.

12. Using the Browse functionality select the operation mapping OM_INVOIC02_TO_ASC810_4010.





the file directory that you defined previously (see 2.2.3). In the case of the sender communication channel, enter the whole path for the file directory Inputfiles\ANSI. Example: \\host\\AS2\Inputfiles\ANSI

4. As File Name ANSI.XML should be set .





Uncheck the characterset conversion check box. AS2___var02 as Own AS2Name

8. Navigate to the tab Signature and Encryption and fill the details as given in the variant1 table

and check the Compress message check box.




Select Asynchronous

MDN target-URL http:/:port/AS2/mdn

Request signing

Check the request signing Checked

Algorithm SHA1

View to signer‟s public key

file://host/%3cselected_path


25

certificate


Create new XI message for received MDN

None

Note: An MDN (Message Delivery Notification) is a functional acknowledgement of receipt generated by the receiving party to positively or negatively acknowledge the success/failure/error in receipt of the original AS2 message. 4.6 Saving and Activating the Configuration Object Proceed as described in variant1. 4.1 Configuring the trading partner 4.1.1 Creating the trading partner on AS2 connector Proceed as Variant 1

1. On “Organization Name”, type: SAPPI___02 2. On “AS2 Identifier”, type: AS2___var02 3. On “Partner URL”, type: http://:/AS2/

http://host:port/AS2/AS2DispatcherServlet__V2

4. On “Connection Info” select the following options:

Category Field Name Value

Outgoing Message Security

Sign Outgoing Data Encrypt Outgoing Data

Unchecked Unchecked

Incoming Message Security

Require Signature Require encryption

Checked checked

Compression Compress Outgoing Data Checked

Connection timeout (sec) Restrict the use of signing and encryption algorithms…

600 Unchecked

5. On “MDN Receipts” select the following options:


Request MDN Receipt Checked

Security Signed / Unsigned Signed

Delivery Synchronous / Asynchronous Asynchronous


26

6. On “Trading Partner Certificates” provide the following data:


Trading Partner Certificate - Encryption

\PI_Test-cert.crt

Security Trading Partner Certificate - Signature

\PI_Test-cert.crt

Delivery Trading Partner Certificate - SSL Server Authentication

Can be left empty

7. Click on “Save Changes”

4.2 Executing the Use Case Here the whole execution is described on the basis of third party /n software . In this variant the third party has been used for receiving the message . Third party can vary in your case . For the configuration of third

party in /n software please refer the section 2.2.3. 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 Inputfiles.

2. Rename the file ZB2B_ANSI.xml as B2B_ANSI.xml.

The File adapter is designed in a way that a file with exactly this name is recognized and moved from the source directory to the AS2 Recipient 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 third part software http://host:port/Default.aspx?a=Incoming go to Incoming Tab select the trading partner “SAPPI___02”. The tab content shows the successfully received messages. Received File can be found on: \\host\as2data\ AS2___var02\Incoming

4. Also the “Logs” tab shows the logs of the incoming messages (successful transmissions and errors if

any) and the MDN requested by the sender will be available in the “Logs”.

5. Check in the “Received Transmissions” if a file was received and an MDN was generated.

OR

6. As the third party software will be installed in a server. You can also go to the file structure of the server where the third party is installed and can also check the Incoming file on the basis of the party.

7. Open the received file and compare with the original file ZB2B_ANSI.xml and verify the content of

the received file and size of the file as the file must be changed to ANSI format and the size of the format should be lesser than the original file when this variant is executed.

Furthermore, you can check the processing of the message in monitoring. You can do this in channel and message monitoring. To do this, proceed as given in variant1.

http://host:port/Default.aspx?a=Incomingfile://host/as2data/%20AS2_%3cSID%3e_%3cUser-ID%3e_var02/Incoming


27

5 Variant 2b: AS2 Adapter – Encryption, Signature and Compression of the message with Asynchronous MDN and Creation of New XI Message.

The feature tested here for AS2 adapter is, creation of new XI message specifically for MDN tracking .

Integration Flow 1: Sender: File Adapter, Receiver: AS2 Adapter. The message is sent from the file adapter and AS2 adapter receives the message.

Integration Flow 2: Sender: AS2 Adapter , Receiver: File adapter The MDN will be received at the AS2 sender, new XI message will be generated in the communication channel monitoring and then the MDN will be sent to the file adapter (receiver).

5.1 Design Objects Used To call the ESR proceed as outlined in variant 1. 5.1.1 Summary of Design Objects Used The design objects used are summarized once more in the following table.



SI_INBOUND_EDI_ANSIX12_INVOICE)


Message Type (ASC810_004010) Describes the message sent at runtime and references the data type used.

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

5.2 Configuring the Process Integration Scenario In configuration, you use the design objects in the process integration scenario for the 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 from the in the Process Integration Designer. You perform the following configuration steps in the SAP Process Integration Designer for the Advanced Adapter Engine Extended. 5.3 Calling the Process Integration Designer Follow the procedure mentioned in variant1. 5.4 Creating the Integration Flow1 Perform the following steps to create a new integration flow.


of the Integration Flow as AS2_Variant2b_IntFlowScenario_ 3. Choose Next. 4. To assign Business Component to sender, right click on the sender -> New Business component ->

name as __B2B_BC_AS2_V2b-> Click Finish.



28


7. As Receiver Interface select SI_INBOUND_EDI_ANSIX12_INVOICE.


10. On the line representing the message flow to receiver __B2B_BC_AS2_V2b in

the context menu select Add Mapping. 11. Select the mapping object in the graphical view. The properties tab will open.

12. Using the Browse functionality select the operation mapping OM_INVOIC02_TO_ASC810_4010.





the file directory that you defined previously (see 2.2.3). In the case of the sender communication channel, enter the whole path for the file directory Inputfiles\ANSI. Example: \\host\\AS2\Inputfiles\ANSI

4. As File Name ANSI.XML should be set .





Uncheck the characterset conversion check box. AS2___var02 as Own AS2Name

8. Navigate to the tab Signature and Encryption and fill the details as given in the variant1 table

and check the Compress message check box.




Select Asynchronous

MDN target-URL http:/:port/AS2/mdn

Request signing

Check the request signing Checked

Algorithm SHA1

View to signer‟s public key certificate

file://host/%3cselected_path


29


Create new XI message for received MDN

Both positive and negative MDN

Referenced MDN Channel

Channel Name AS2 Sender channel name (from Integration Flow2)

Communication Component AS2 Sender Communication Component (from Integration Flow2)

5.6 Saving and Activating the Configuration Object Proceed as described in variant1. 5.7 Configuring the trading partner 5.7.1 Creating the trading partner on AS2 connector Proceed as Variant 1

1. On “Organization Name”, type: SAPPI___02b 2. On “AS2 Identifier”, type: AS2___var02b 3. On “Partner URL”, type: http://:/AS2/ http://host:port/AS2/AS2DispatcherServlet__V2b

4. On “Connection Info” select the following options:


Outgoing Message Security

Sign Outgoing Data Encrypt Outgoing Data

Unchecked Unchecked

Incoming Message Security

Require Signature Require encryption

Checked checked

Compression Compress Outgoing Data Checked

Connection timeout (sec) Restrict the use of signing and encryption algorithms…

600 Unchecked

5. On “MDN Receipts” select the following options:


Request MDN Receipt Checked

Security Signed / Unsigned Signed

Delivery Synchronous / Asynchronous Asynchronous


30

6. On “Trading Partner Certificates” provide the following data:


Trading Partner Certificate - Encryption

\PI_Test-cert.crt

Security Trading Partner Certificate - Signature

\PI_Test-cert.crt

Delivery Trading Partner Certificate - SSL Server Authentication

Can be left empty

7. Click on “Save Changes”.

5.8 Creation of Integration Flow2 Perform the following steps to create a new integration flow.

1. In the Process Integration Designer choose New → Integrati

SAP NetWeaver Process Integration 7...configuration steps that are necessary to execute the...

Documents

Transcript of SAP NetWeaver Process Integration 7...configuration steps that are necessary to execute the...