Using Scripting

Log on to the integration flow DelayedDelivery_Process via Integration Suite.

1. Navigate within the Integration Suite Welcome page to Design → Integrations → DelayedDelivery_Package_CLD900_Date_Number → DelayedDelivery_Process_Number.

2. Following the status after the last exercise step.

   

3. Let's assume that the integration flow has been further edited.

Create a Groovy Script.

1. Set Transformation → Script → Groovy Script component within the Exception Subprocess.

2. Or you can use the context menu by choosing the line between the Error Start and End event. Then, to add a flow step, choose the plus symbol.

   

3. Rename it to Script_readExceptionMessagesToPayload.

   

Write a Groovy Script.

1. Use the Create icon from the context menu of the Script_readExceptionMessagesToPayload component.

   

2. Enter the following data:

   Code Snippet

   Copy codeSwitch to dark mode

   1234567891011121314151617181920212223242526
   import com.sap.gateway.ip.core.customdev.util.Message;
   import java.util.HashMap;
   import groovy.xml.MarkupBuilder;
   def Message processData(Message message) {
    //Body 
    def body     = message.getBody();
    def props    = message.getProperties(); 
    def exStacktrace = props.get("exStacktrace");
    def exMessage = props.get("exMessage"); 
    def stringWriter = new StringWriter();
    def exceptionBuiler = new MarkupBuilder(stringWriter); 
    exceptionBuiler.exception {
    exceptionMessage(exMessage)
    stacktrace(exStacktrace)
    } 
    message.setHeader("Content-Type", "application/xml")
    message.setHeader("CamelHttpResponseCode", 500) 
    message.setBody(stringWriter.toString());
    
    def messageLog = messageLogFactory.getMessageLog(message);
    if(messageLog != null) {
    messageLog.addAttachmentAsString("Exception Messages", message.getBody(), "text/plain")
    }
    
    return message;
   }

   

3. Choose the OK button to save your work.

4. Navigate back to your Integration Process via the bread crumb navigation.

Save as version, deploy, and debug your integration process.

1. Perform the following steps:

   1. Save as version.
   2. Deploy.
   3. Jump to Overview → Manage Integration Content.
   4. Set the log level to trace.
   5. Deploy again.
   6. Jump again to Overview → Manage Integration Content.

2. Navigate to your integration flow Model in Overview → Monitor Message Processing → Message Processing Run.

Deploy it without an Exception and check the Exception Subprocess in the monitoring, which has no messages working with.

Deploy it with an implemented exception error.

1. Navigate to the Call_checkProductID OData adapter. At the Connection tab, change the URL so that it no longer works by adding an x.

   

2. Save and Deploy again, and check your Monitor.

3. At Overview → Monitor Message Processing.

   

4. The message status is Completed and an error message has been created. Check the messages and the attachments under Monitor Message Processing.

   

5. An Exception occurs and the Exception Subprocess is called.

6. Everything works as expected.

7. Remove the error in the URL again so that everything runs without errors again.

Learn more about the Groovy Scripting operations.

1. Navigate back to your Integration Process, open the configuration bar of the Script_readExceptionMessagesToPayload component, and choose the question mark symbol.

Log on to the integration flow DelayedDelivery_Process via SAP Integration Suite.

1. Navigate within the SAP Integration Suite Welcome page toDesign → Integrations → DelayedDelivery_Package_CLD900_Date_Number → DelayedDelivery_Process_Number .

2. Following the status after the last exercise step.

   

3. Imagine that the integration flow has been further modified.

Substitute the timer event with a message start event.

1. Choose Event → Start Message or use the context menu as previously mentioned in the preceding exercises.

2. Delete the Time Event.

   
   

3. Rename the start event to Event_startMessage.

   

Delete the Modify_setPayload component.

1. This segment of your integration flow looks like this now.

   

2. Choose the Save button.