I just got a note that our Neo tenants will be updated to Apache Camel 3.14. This is because we have some custom adapter development on our Neo tenants. I would imagine that this will also impact Cloud Foundry/Integration Suite. And I’m also surprised that the Neo will get this update. 

Update Oct 2023: It seems like the Integration Suite is also getting this information now. So if you have custom adapters ask for a trial tenant and upgrade your adapters. 

Update Feb 2024: The Camel has not been applied. As I understand probably some problems that has postponed the update. During the Integration Suite update in January it sounded like the update will be applied in Q2 2024. 

Update Aug 2024: There is a new plan for the upgrade. Which seems to be a much shorter timeline than expected. Please ensure you have your adapter updated. See the presentation page 35 forward.

Update October 2024: There are come challenges with Camel expression that you must know. We have added this plus created a tagging rule for the Figaf tool to simplify the journey. 

Update March 2025: Many have already have gotten their tenants updates and new problem added. 

If you have some groovy scripts that are using camel or low level framework call it would be a good idea to have a good number of test cases for your landscape. That way you can catch problems much faster without and fix the issues before it hit your productive systems. I have no idea of what can be affected and if there is any impact. I sure hope that there are non. 

OFFER: If you want to use Figaf to test your upgrade for FREE. Sign up for our free migration edition. Install Figaf and start creating test cases. You can follow the guide. Once you have run  and created a few test cases (there is 10 free) then write support and we will upgrade to 100. 

Offer only valid until 30 September 2024.

Simple Expression problems

There seems to be some problems related to Camel Expressions where there have been some problems that you need to consider. 

3383568 List of possible changes

This note list the properties that could cause problems when migrating. 

Confusion on ${in.body}

There is some confusing elements about the ${in.body} will still work see . It links to the next note that just covers something about upper case of the object and it still mentions that in.body will work. We have a tagging rule for in.body cases also, but we also don’t know if it is a problem and if it will be fixed. 

3383659 – SimpleParserException After Upgrade to Camel Runtime 3.14.

Here the problem is the way expressions uses upper case in the Simple Expression for instance ${in.Body}. In Camel 2 you first get this as a runtime error where in Camel 3.14 you get it as a deploy time error. I dont think this is a big problem.

3516570  Problem with operators using \n \r \t

There seems to be a problem with ${in.body.replaceAll(“[\r\n]”, “”)}. In Camel 2 this worked but in camel 3.14 you need to replace this with a groovy script. This is something that can cause problems in the iflows where you use the expressions. 

3435465 Usage of Property in filter steps

In the filter “${property.propertyname}” needs to be changed to “${exchangeProperty.PropertyName}”. It mentions filter steps where it is executed and where SAP may not have performed the mapping to the Camel step.

3404057 No more polls in schedule

If you have a scheduler that is not going to be triggered anymore it will give a error in the deployment. I dont think this is a big problem because you probably then dont want the flow to be run anymore. Then it is just to undeploy it. 

3383568 – General Splitter 

General Splitter component work differently for some scenarios if Splitter XPath expression and Grouping configuration were unexpectedly overridden by the returned headers from the Global Flow. See more 

Find the problematic iflows

In Figaf we have a tool to search a full PI or Cloud Integration sytestem. It is our Tagging concept. We have added two rules that allow you to search for property in filter or the \n \r \t in all your iflows. To use this do the following 

1. Signup for Figaf DevOps or Migration Edition
2. Install it locally
3. Add the license key
4. Connect to SAP Cloud Integration
5. Possible create a dummy agent for SAP PI
6. Go to the tagging page and download the latest json file
7. Upload it to your tenant under tagging rules
8. Perform the tagging
9. Check the iflows that have been marked

We have tried our best to understand SAP’s challenge and created a search for it. We cannot guarantee that we will find all issues, but at least it is a good place to start. 

The original message

Currently, SAP is running 2.24 according to CPITracker, or in the email, it lists 2.14. 2.24 is from 2019 so it is quite old.

You can see the help page is already online.

It is exciting that the version will be upgraded and hopefully give Cloud Integration better performance and hopefully some new features.

Once you get the tenant started you can try test the migration. Here I show you how easy it is to create an run tests with Figaf.

 

Why Camel 3.14

According to the documentation is Camel 3.14 the last Long Term Support of Java 8. So moving to a newer version will have a huge impact because it will require updating other components and breaking the possibility of running on SAP PI/PO. I’m not sure if this also will mean you need to upgrade your PI system to support the cases.

Once Edge Integration Cell becomes GA in the next few months, upgrading the Java and Camel versions will be possible. Though probably not before 2025 to ensure customers get enough time to move versions.

What SAP will enable is interesting. It seems like it will have lower memory usage and more components that can be switched on. And it is a more modulized setup. 

If you have the old OEM adapters from Advantco, then they will most likely not work anymore. So you will need to migrate before this date or purchase their new adapters.

 

Testing

SAP will be testing the change will be minimal for their upgrade. There will be some impact of the adapters as stated in the email that you will need to test.

I don’t know what the impact of the changes will be in terms of your integration. If you are using some low-level APIs, then it could have an impact and will require you to change the setup. There could also be potential problems with some ways of processing and how the adapters will react.

I recommend setting up 25% of your iflows as test cases to ensure they perform normally. Then request the test tenant and perform you test on it. If you want to speed up the test then getting Figaf to help test the upgrades with will simplify the testing. I’m though biased, and I have no idea of the impact. Having a good automated test will enable you to document the changes with SAP before the upgrade giving you or SAP time to resolve the differences.

If you want to be testing this upgrade. You can use our Free migration edition since it will give you two months of Cloud Integration Testing as a trial. This will give you time to test the impact on your own data.