9.3 Execution
12.1.2 Create Destination in the AEX system
1. Switch back to AEX NWA http(s)://<host>:<port>/nwa 2. Go to tab ”Configuration” and click on “Destinations”.
3. Create “HTTP Destination”: <SID>_105_PP
4. Set URL to “http://<host of <SID>_105>>:<port>/sap/xi/engine?type=entry 5. Maintain SID, client and language.
6. Select “Ignore SLL Server Certificate”
7. Press “next” and choose “Assertion Ticket” for “Authentication”.
8. Save Changes.
9. Execute “Ping”. Result should be “Ping not successful! Received HTTP response 500”
12.2 Design Objects Used
You use the component view Proxy2Proxy_PP_NoMapping in process integration scenario XiPatternOneStepScenario to configure this variant. The following graphic shows the component view:
As described under 3.1, you can navigate to all design objects used from the component view. The following explains the design objects that play a role when using this component view.
Interface Objects
In this variant, the data structures at both the sender and receiver side are the same and no mapping is required. Nevertheless, two different service interfaces are used: outbound interface XiPatternInterface9_Out for the sender and inbound interface XiPatternInterface9_In for the receiver. This is due to the fact that the sender and receivers systems are SAP systems that communicate with each other by the ABAP proxy runtime.
This communication type requires an outbound proxy and an inbound proxy (both generated resp. derived from the outbound resp. inbound interface).
Summary of Design Objects Used
The following table summarizes the additional design objects used.
Design Objects Used
Object Type (Name) Description
Component View
Proxy2Proxy_PP_NoMapping (Process Integration Scenario
XiPatternOneStepScenario)
Describes the process flow and the message exchange for this variant.
Service interface
(XiPatternInterface9_Out)
Describes the interface and data structure of the receiver. The data structure is the same for sender and receiver.
The fault message type is used to handle application-specific errors that occur on the inbound side and that are reported back to the sender.
Service Interface (XiPatternInterface9_In) Message Type (XiPatternMessage9) Fault Message Type
(XiPatternFaultMessage) Data Type (XiPatternDataType9)
12.3 Configuring the Process Integration Scenario
Create the connection to the XI Adapter of the AEX system
To connect the sending client to the Java XI Adapter you have to create a HTTP Destination to the Adapter Engine. Do the following in the application client 105:
1. Call transaction SM59.
2. Create a HTTP Destination to an external system (Type G). As name set JAVA_XI_ADAPTER_AEX_<SID>_PP, as description use Connection to Java XI Adapter in Adapter Engine. As target host set the host name of the adapter engine, as service set (Service No.) the HTTP(S) Port and as path set /XISOAPAdapter/MessageServlet?ximessage=true.
Note: Ensure that you have maintained the proper URL of the “Advanced Adapter Engine of PI system” in SM59 of the sender application.
You may get the warning „Query string not allowed‟ when saving the destination, just press enter to confirm the warning message.
3. Under Logon and Security select Basic Authentication and set the user PIAPPLUSER (or a copy of the PIAPPLUSER) with the corresponding password.
This user and password will be checked against the Advanced Adapter Engine Extended system, where the message is sent to.
4. Save the destination and execute Connection Test. Response Code HTTP 200 means successful connection.
Activating the connection to the Java XI Adapter
To enable the sending application system to send a message to the Java XI Adapter instead of the Integration Server you have to create a filter for the sending interface and have to set the URL to the Adapter Engine in the sending application client. Execute the following steps in the sending client 105:
1. Call transaction SXMSIF.
2. Create a new entry for Sender/Receiver ID with the name JAVA_XI_ADAPTER_AEX_PP_IF9. As description set Call the Java XI Adapter in PI PP Async Demo Examples, as communication Component set
<SID>_105, as interface name and namespace set XiPatternInterface9_Out and http://sap.com/xi/XI/System/Patterns.
3. Save the entry.
4. Call transaction SXMB_ADM, select Integration Engine Configuration.
5. Select the button Change Configuration. Switch to Change Mode and create a new entry with the following settings:
Category: RUNTIME
Parameter: IS_URL
Subparameter: select the Sender/Receiver ID JAVA_XI_ADAPTER_AEX_PP_IF9
Value: dest://JAVA_XI_ADAPTER_AEX_<SID>_PP 6. Save the entry.
Calling the Integration Directory
You perform the following configuration steps in the Integration Directory.
For this scenario, the integrated configuration object is used for configuration.
For more information, see Defining the Integrated Configuration.
First, call the Integration Directory. On the Process Integration initial screen, choose Integration Directory.
To configure this variant, a new configuration scenario is created.
Selecting the Process Integration Scenario
Perform the following steps to select the process integration scenario that you want to configure from the Enterprise Services Repository. Also, enter the name of the configuration scenario (in the Integration Directory) in which you want to group the configuration objects.
1. To call the model configurator, choose Tools Apply Model from ES Repository in the Integration Builder menu bar.
This calls a wizard, which you use to select a model (in this case, a process integration scenario) and create a configuration scenario in the Integration Directory.
2. Make sure that the model type Process Integration Scenario is selected (radio button under Type of ES Repository Model).
3. Choose the input help (for the Name field) ( )
This calls an input help, which displays all process integration scenarios from the Enterprise Services Repository in a list.
4. Select the process integration scenario XiPatternOneStepScenario (software component version SAP BASIS 7.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_Proxy2Proxy_PP_AAE.
7. Choose Finish and then Close.
The system calls the model configurator.
Selecting the Component View
Check whether the component view Proxy2Proxy_PP_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.5).
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>_105 and then choose Apply.
4. Choose Next Role ( ) to navigate to the configuration dialog for the application component Receiver.
5. Assign the same communication component <SID>_105 to the application component Receiver. Follow the same procedure as when assigning the communication component to the application component Sender.
6. Choose Assign.
Configuring the Connection
You perform the following steps to configure the connection of the process integration
scenario. You activate the relevant sender-receiver relation (between the sender and receiver component) and assign both the sender and receiver a (sender or receiver) communication channel. You create the communication channel on the basis of the communication channel templates that the process integration scenario already contains.
1. In the graphical editor, click on the connection between the lanes representing the two application components.
2. This calls the Configure Connection dialog box for the connection between the actions (below the graphical representation of the process integration scenario).
3. On the Configure Connections screen, choose the tab page Connections from Component Assignment. The communication components that you assigned in the previous configuration step are displayed.
The remaining tab pages contain further information about the process integration scenario, for example, the communication channel templates that are defined for the process integration scenario in the Enterprise Services Repository.
4. Assign the 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.
5. Choose Continue.
The default communication channel template on the subsequent screen is that which was assigned to the sender application component in the process integration scenario (name XiPatternChannel_XiSender, software component version SAP BASIS 7.31, namespace http://sap.com/xi/XI/System/Patterns).
6. Choose Continue.
Enter the name for the communication channel on the next screen as XiPatternChannel_XiSender_PP.
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_XiReceiver_PP) based on the default communication channel template (name XiPatternChannel_XiReceiver, 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
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 receiver communication channel after generation.
1. In the editor Display Configuration Scenario (for the open scenario
XiPatternOneStepScenario_Proxy2Proxy_PP_AEX), on the tab page Objects open the communication channel ( ) XiPatternChannel_XiReceiver_PP by double-clicking.
2. As target URL set the entry path for the application client 105: http(s)://server:http-port/sap/xi/engine?type=entry. As Authentication Data, enter client 105 and the user PIAPPLUSER (or a copy of the PIAPPLUSER) with its password in client 105.
Note: 1. in case https then you should specify the host and the whole qualified domain name
2. If receiver server is lower than NW7.10 please consider that the URL should contain the http(s) port. Check the transaction SMICM and use the corresponding http(s) port instead of the URL which is used start the integration directory.
3. Save the communication channel.
Activating the Change List
1. To do this, select the Change Lists tab page in the Integration Directory navigation area.
2. Choose Open Standard Change List.
3. Position the cursor on the Standard Change List node and choose Activate ( ) in the context menu
Check Setup
Before starting with the principal propagation configuration, the scenario is tested without principal propagation. This ensures that the default case work. If the default case does not work, principal propagation also won‟t work.
1. Execute transaction SXIPATT1 (client 105).
2. Check only the checkbox PP.
3. Choose Send.
4. Execute transaction SXMB_MONI
5. Filter messages by Sender-Interface XiPatternInterface9_Out.
6. Message must be processed successfully.
7. Now filter for corresponding message, which is received by the client. Filter messages by Receiver-Interface XiPatternInterface9_In.
8. Message must be processed successfully.
Activating Principle Propagation – Integration Directory 1. Launch Integration Directory
2. Select the Integrated Configuration
XiPatternOneStepScenario_Proxy2Proxy_PP_AAE
3. Check the checkbox “Principle Propagation” on “Inbound Processing” and
“Outbound Processing” tab.
4. In the channel “XiPatternChannel_XIReceiver_PP” select Addressing Typ “HTTP Destination” and in the field “HTTP Destination” add the destination <SID>_105_PP.
5. Activate the changes.
6. Move to the Channel Monitor and stop and start the channel.
Modify Destination in the ABAP client
1. Call transaction sm59.
2. Select destination JAVA_XI_ADAPTER_AEX_<SID>_PP.
3. On tab “Logon & Security” select “Do Not Use a User” and select “Send Logon Ticket without Ref. to Target System”.
4. Save the settings.
Activating Principle Propagation – Sender System 1. Logon to the sending system (<SID>_105) 2. Call transaction SXMB_ADM
3. Execute “Configure Principle Propagation”
4. “Configure Interfaces” (Interface Conf. for Transfer of User IDs)
5. Add the interface XiPatternInterface9_Out with namespace http://sap.com/xi/XI/System/Patterns and the user you are using.
Principle Configuration settings will enforce SAPLogonTicket usage of destination JAVA_XI_ADAPTER_AEX_<SID>_PP.
12.4 Execution
You perform the following steps to check that the process integration scenario is executed without errors.
To run the process integration scenario, you can use a transaction that is available in the SAP PI system, however this transaction should run in the of the business client but not on the client where the Integration Server is available i.e. 001.
1. Logon to the SAP system of the business system, client 105.
3. Enter values for the fields Name, Country, and Tel.
4. Select only the checkbox PP.
5. Choose Send.
6. For verification start NWA using http://<host>:<port>/nwa
7. Navigate to SOA / Monitoring / Message Monitoring and click on the Database Tab.
8. Search for the message and check, if it was processed successfully.
9. Check the “Message Log”, whether the message was entering the SOAP Adapter with your ABAP user.
10. Logon to the ABAP System: <SID>_105 11. Call transaction SXMB_MONI.
12. Find the message you send.
13. Check the details of the message.
If your user is used in the tag <SAP:User> in the RunTime part of the SOAP Header in the Inbound Message of Sender and Receiver, Principal Propagation works correctly.
13 Variant 11: One Sender and One Receiver – synchronous Proxy-to-Proxy Communication using the Advanced Adapter Engine
In this variant, the message is processed via the ABAP proxy runtime; the message is forwarded using the Advanced Adapter Engine Extended. Following the standard
configuration suggested below one application system is used both as sender and receiver of messages.
13.1 Design Objects Used
You use the component view Proxy2Proxy_sync_NoMapping in process integration scenario XiPatternOneStepScenario to configure this variant. The following graphic shows the
component view:
As described under 3.1, you can navigate to all design objects used from the component view. The following explains the design objects that play a role when using this component view.
Interface Objects
In this variant, the data structures at both the sender and receiver side are the same and no mapping is required. Nevertheless, two different service interfaces are used: outbound interface XiPatternInterface2_Out_sync for the sender and inbound interface
XiPatternInterface2_In_sync for the receiver. This is due to the fact that the sender and receivers systems are SAP systems that communicate with each other by the ABAP proxy runtime. This communication type requires an already generated and delivered outbound proxy and an inbound proxy in the application clients.
Summary of Design Objects Used
The following table summarizes the additional design objects used.
Design Objects Used
Object Type (Name) Description
Component View
Proxy2Proxy_sync_NoMapping (Process Integration Scenario
XiPatternOneStepScenario)
Describes the process flow and the message exchange for this variant.
Service interface
(XiPatternInterface2_Out_sync)
Describes the interface and data structure of the receiver. The data structure is the same for sender and receiver.
The fault message type is used to handle application-specific errors that occur on the inbound side and that are reported back to the sender.
Service Interface
(XiPatternInterface2_In_sync) Message Type (XiPatternMessage2) Message Type
(XiPatternMessage2Response) Fault Message Type
(XiPatternFaultMessage)
Data Type (XiPatternDataType2) Data Type
(XiPatternDataType2Response)
13.2 Configuring the Process Integration Scenario
Create the connection to the XI Adapter in the Advanced Adapter Engine
To connect the sending client to the Java XI Adapter you have to create a HTTP Destination to the Adapter Engine. Do the following in the application client 105:
1. Call transaction SM59.
2. Create a HTTP Destination to an external system (Type G). As name set
JAVA_XI_ADAPTER_AAE_SYNC, as description use Synchronous Connection to Java XI Adapter in Adapter Engine. As target host set the host name of the adapter engine, as service set (Service No.) the HTTP(S) Port and as path set
/XISOAPAdapter/MessageServlet?ximessage=true.
Note: Ensure that you have maintained the proper URL of the “Advanced Adapter Engine of AEX system” in SM59 of the sender application.
You may get the warning „Query string not allowed‟ when saving the destination, just press enter to confirm the warning message.
5. Under Logon and Security select Basic Authentication and set the user PIAPPLUSER (or a copy of the PIAPPLUSER) with the corresponding password.
This user and password will be checked against the Advanced Adapter Engine Extended system, where the message is sent to.
6. Save the destination and execute Connection Test. Response Code HTTP 200 means successful connection.
Activating the connection to the Java XI Adapter
To enable the sending application system to send a message to the Java XI Adapter instead of the Integration Server you have to create a filter for the synchronous sending interface and have to set the URL to the Adapter Engine in the sending application client. Execute the following steps in the sending client 105:
1. Call transaction SXMSIF.
2. Create a new entry for Sender/Receiver ID with the name
JAVA_XI_ADAPTER_SYNC. As description set Call the Java XI Adapter synchronously in PI Demo Examples, as communication Component (Service) set <SID>_105, as interface name and namespace set
XiPatternInterface2_Out_sync and http://sap.com/xi/XI/System/Patterns.
3. Save the entry.
4. Call transaction SXMB_ADM, select Integration Engine Configuration.
5. Select the button Change Configuration. Switch to Change Mode and create a new entry with the following settings:
Parameter: IS_URL
Subparameter: select the Sender/Receiver ID JAVA_XI_ADAPTER_SYNC
Value: dest://JAVA_XI_ADAPTER_AAE_SYNC 6. Save the entry.
Calling the Integration Directory
You perform the following configuration steps in the Integration Directory.
For this scenario, the integrated configuration object is used for configuration.
For more information, see Defining the Integrated Configuration.
First, call the Integration Directory. On the Process Integration initial screen, choose Integration Directory.
To configure this variant, a new configuration scenario is created.
Selecting the Process Integration Scenario
Perform the following steps to select the process integration scenario that you want to configure from the Enterprise Services Repository. Also, enter the name of the configuration scenario (in the Integration Directory) in which you want to group the configuration objects.
1. To call the model configurator, choose Tools Apply Model from ES Repository in the Integration Builder menu bar.
This calls a wizard, which you use to select a model (in this case, a process integration scenario) and create a configuration scenario in the Integration Directory.
2. Make sure that the model type Process Integration Scenario is selected (radio button under Type of ES Repository Model).
3. Choose the input help (for the Name field) ( )
This calls an input help, which displays all process integration scenarios from the Enterprise Services Repository in a list.
4. Select the process integration scenario XiPatternOneStepScenario (software component version SAP BASIS 7.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_Proxy2Proxy_SYNC_AAE.
XiPatternOneStepScenario_Proxy2Proxy_SYNC_AAE.