Exploring Cloud Integration - Part 8 (Creating and Configuring a Router)

The last article covered validating the availability of productIDs against the order database using an OData query to determine the subsequent processing route. This involved creating a request and reply to an external call.

In today's article, I will set up a router with two routes to manage further processing. If the productID is not found in the database, the process must be terminated in one of the routes. If the ProductID is found, further processing steps will take place in the other route.

Task Flow

I performed the following tasks:

1. Logging on to the integration flow DelayedDelivery_Process.
2. Creating and configuring a Router.
3. Saving as version, deploying, and debugging the integration process.

Prerequisite

The creation of a Request and Reply to an External call has been completed in the last article.

Outcome After This Exercise

Environment

Live SAP BTP account.

Task 1: Logging on to the Integration Flow DelayedDelivery_Process

Steps

1. Logged on to the integration flow DelayedDelivery_Process via Integration Suite.

• Navigated within the Integration Suite Welcome page to Design → Integrations → DelayedDelivery_Package_randomNumber → DelayedDelivery_Process.
• Checked the status after the last exercise step:

Task 2: Creating and Configuring a Router

Steps

1. Set a Router.

• Placed a router component in a known way according to the Call_checkProductID, named it Router_ProductID.

2. Created the following Condition: /ProductSet/count(Product)>0.

• Chose the name Route 1.
• Renamed Route 1 to ProductID_Available at tab General.

• Switched to the Processing tab and unflagged Default Route. The interface changed immediately

• In the Condition field, I entered /ProductSet/count(Product)>0. That means if at least one child product exists, take this path.

Table 14: Route condition

3. Created the default route.

• A default route is essential in all cases, and for this purpose, I utilized a second Message End event. In order to achieve this, I moved the ProductID_Available route slightly downwards.

• Subsequently, I placed a second Message End event above the initial one.

• Named the new End event End_Message_Event.

• At this point, I connected the Router to the new Message End event by utilizing the context menu.

• Changed the name of this new route to No_ProductID_Available.

• Went to the Processing tab, and set this route as the default one.

Task 3: Saving as Version, Deploying, and Debugging thed Integration Process

Steps

1. Saved as version, deployed, and debugged the integration process.

1. I performed the following steps:

〰Save as version.

〰Deploy.

〰Jump to Overview → Manage Integration Content.

〰Set log level to trace.

〰Deploy again.

〰Jump again to Overview → Manage Integration Content.

2. Navigated to the Integration Flow Model in Overview → Monitor Message Processing → Message Processing Run.

3. As the product list contains both an existing and non-existent IDs, it is necessary to follow both paths.

Conclusion

I set up a Router with two routes to manage further processing.

Next Article ▶

Creating a Request and Reply to an external Call (HTTP Call)

Previous Article ◀

Creating a Request and Reply to an external Call (OData Adapter)

Thanks for reading !

Reference

SAP (2024). Developing with SAP Integration Suite

© 2024 SAP SE or an SAP affiliate company. All rights reserved. This article references SAP materials for educational purposes, in accordance with SAP's copyright guidelines.