Cleaning Up Message Data

Set a filter.

1. In the Transformation menu of the iFlow editor, choose Filter and position it adjacent to the previous process step. Connect both as you have learned.

   

2. You can optionally change the name of the filter in the General tab of the configuration view that can be expanded from the bottom right of the screen if closed.

Move to the Processing tab and enter/OrderRequestas XPath Expression.

Depending on whether or not you have chosen to work with the pre-configured mappings or your own, your pre-processed message before the filter process step might look different.

In the case of the provided mapping files, a namespace has to be declared within CI. For this, click anywhere outside of the Integration Process pool box to open the Integration Flow configuration view. Navigate to Runtime Configuration and enter the Namespace Mappingxmlns:ns1=http://sap.com/xi/EDI.

This also means that you have to change the XPath Expression in the filter to include the namespace "/ns1:OrderRequest".

If you have elected to work with your own file, you can skip this step. If an error in your filter occurs when testing the iFlow because of not declaring the namespace, you will be able to see this in the lesson "5.5 Deploying and Testing iFlows" (Set TRACE log level to view message payload) and go back to edit the iFlow then. Hovering over the Namespace Mapping input field will allow you to see the accepted format.

Choose Save on the top right of the screen to secure your progress.

In the Transformation menu of the iFlow editor, choose Script → Groovy Script and position it adjacent to the previous Filter process step. Connect both elements via drag and drop.

Click onto the Groovy Script element to access its configuration menu. In the General tab, set the Name to Substitute special characters.

As this script is only needed locally within this particular iFlow, you can provide it directly as a resource. This is now shown for demonstration purposes. In reality, it is common practice to make all functions available via a script collection. This feature will be shown in a later exercise.

For the next step, you need to prepare a file on your local file system or take the .groovy file that you downloaded with the .zip file in the exercise Set Up Your Environment. Name it sub_special_characters.groovy. Enter the following code into this file and save it.

Code snippet

Copy code

import com.sap.gateway.ip.core.customdev.util.Message;
import java.util.HashMap;
def Message processData(Message message) {
    //Body 
      def body = message.getBody(java.lang.String);
      
        body = body.replaceAll("<", "<")
        
        body = body.replaceAll(">", ">")
        
        message.setBody(body)
        
      return message;
}

Copy code

Navigate to theProcessing tab in the configuration view and select Upload from File System. Locate the prepared file sub_special_characters.groovy. Choose OK to proceed.

Select the script resource (path) to familiarize yourself with its workings.

Choose Save to secure your progress.

Select Transformation → Content Modifierand position the element next to the previous process step. Connect both elements.

In the configuration menu of the Content Modifier, change its Name to Create SOAP message.

Move on to the Message Body tab and provide the following input:

Code snippet

Copy code

<soap:Envelope
xmlns:soap="http://www.w3.org/2001/12/soap-envelope"
soap:encodingStyle="http://www.w3.org/2001/12/soap-encoding">
<soap:Body xmlns:m="http://www.example.org/PurchaseOrder">
  <m:Contents>${in.body}</m:Contents>
</soap:Body>
</soap:Envelope> 

Copy code

Choose Save to secure your progress.

Note

At the moment, you can not test this iFlow, because the required End Message event is missing. This will be added in the exercise: Configure Outbound Communication.