2.2.1 General Prerequisites
To configure and execute the use cases, SAP NetWeaver with usage type Process Integration and Advanced Adapter Engine Extended must be correctly installed and configured. The following table lists the prerequisites and the relevant guides:
List of required steps
Step Documentation
1. You have installed the Advanced Adapter Engine 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
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
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.
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
ZXiPatternSenderFile2.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
7. Copy following file to directory XiPattern10
ZXIPatternSenderFile1.xml
8. Copy the following files to directory XiPattern1_PCI:
ZXiPatternSenderFile2.xml
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.
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_XiPattern3
<SID>_AAEX_FileSystem_XiPattern4
<SID>_AAEX_FileSystem_XiPattern5
<SID>_AAEX_FileSystem_XiPattern10
<SID>_AAEX_FileSystem_XiPattern11
<SID>_AAEX_FileSystem_XiPattern12
<SID>_AAEX_FileSystem_XiPattern1_PCI
<SID>_AAEX_FileSystem_XiPattern2_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
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:
<SID>_AAEX_FileSystem_XiPattern1
<SID>_AAEX_FileSystem_XiPattern2
<SID>_AAEX_FileSystem_XiPattern3
<SID>_AAEX_FileSystem_XiPattern4
<SID>_AAEX_FileSystem_XiPattern5
<SID>_AAEX_FileSystem_XiPattern10
<SID>_AAEX_FileSystem_XiPattern11
<SID>_AAEX_FileSystem_XiPattern12
<SID>_105
<SID>_AAEX_FileSystem_XiPattern1_PCI
<SID>_AAEX_FileSystem_XiPattern2_PCI
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.