Technology Blog Posts by Members
cancel
Showing results for 
Search instead for 
Did you mean: 

While working with SAP Cloud Integration - Integration Suite, consultants and developers often upgrade adapters to leverage new features, bug fixes, or security enhancements. However, upgrading adapters without understanding the design-time vs runtime behaviour can lead to confusing runtime errors.

In this blog, I’ll walk you through a very common issue that occurs when the adapter version is inconsistent between design time and runtime, why it happens, and how to fix it step by step. We will use SMB adapter as an example however, note that the solution described here is not limited to SMB adapter and applies to any adapter which is consumed from SAP Business Accelerator Hub.

Problem Statement : 

Let’s consider the following scenario where our SAP CI tenant has an iflow using SMB Adapter version 1.2.0 deployed at runtime. Let us assume SAP has announced a new version that has been released (1.3.0).

  1.  Navigate to Discover tab of your tenant and click Copy.
  2. Next, deploy the iflow.

When you execute the iFlow, it fails with an error like the one below:

[CONTENT][CONTENT_DEPLOY][InstanceError] : {"message":"EXCEPTION","childMessageInstances":[{"message":"CAUSE","childMessageInstances":[{"message":"CAUSE","parameters":["org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint

At first glance, the configuration may look correct, credentials are valid, and yet we face the error as failed to resolve endpoint.

Why This Issue Occurs

One of the common root cause of this issue is adapter version mismatch between design time and runtime.

Here’s what happens internally:

  1. When we copy an adapter from Business Accelerator Hub/Discover, it is imported into design time only.
  2. The adapter is not deployed to runtime.
  3. Our iFlow is designed using the latest SMB Adapter 1.3.0 (design time).
  4. At runtime, it still tries to execute the iFlow using SMB Adapter 1.2.0 (runtime).

Since the runtime does not recognize parameters or capabilities introduced in the newer adapter version, it fails while resolving the endpoint.

In short, Design-time adapter version != Runtime adapter version = Execution failure

How to Fix the Issue (Step-by-Step)

Follow the steps below to resolve the SMB adapter version mismatch:

  1. Go to Discover > Integrations
  2. Search for SMB Adapter for SAP Integration Suite
    pulkit_bhatnagar_0-1770271452699.png
  3. Click Copy to copy the latest version (1.3.0) into your tenant.
    pulkit_bhatnagar_1-1770271572413.png

At this point, the adapter exists only in design time but you must also deploy the adapter to runtime as well.

This is the most important step and is often missed.

  1. Navigate to Design > Integrations and APIs
    pulkit_bhatnagar_2-1770271680267.png
  2. Locate the newly copied SMB Adapter (1.3.0)
    pulkit_bhatnagar_3-1770272119450.png
  3. Deploy the adapter. Click on Artifacts tab and then Click on three dots under Actions > Deploy
    pulkit_bhatnagar_4-1770272308603.png
    Wait until the deployment status shows successful.
    pulkit_bhatnagar_5-1770272579826.png

Now, the adapter version will be available at runtime as well. Redeploy your iflow. The iflow will now execute successfully without the endpoint resolution error.

Conclusion

Adapter upgrades in SAP Integration Suite are not just a design-time activity. Adapter versions must always be consistent between design time and runtime.

Whenever you upgrade an adapter from Discover or API Business Hub, always deploy it to runtime immediately before testing your iFlows.

This simple check can save hours of troubleshooting and prevent avoidable production issues.

Hope this blog helps fellow SAP CI consultants and developers facing similar adapter upgrade issues.

Labels in this area