Skip to main content
Solved

Multiple versions of an IFS REST API

  • December 5, 2024
  • 1 reply
  • 35 views

Forum|alt.badge.img+6
  • Sidekick (Employee)
  • 22 replies

Hi,

I have an Apps10 integration project involving several interconnected applications, and IFS is one of them. The interfaces use REST APIs.
As part of the deployment of these interfaces, I have a request to manage versions of the REST APIs so that they can identify the version number of the interface in the url and activate one or the other.
Has anyone ever had to manage different versions in an IFS API? Is there a way to do it?
for example :
<url>/main/ifsapplications/projection/v1/CommissionReceiverGroupsHandling.svc/CommissionReceiverGroups
<url>/main/ifsapplications/projection/v2/CommissionReceiverGroupsHandling.svc/CommissionReceiverGroups
<url>/main/ifsapplications/projection/v2.1/CommissionReceiverGroupsHandling.svc/CommissionReceiverGroups

Thank you

Fabrice

Best answer by Rifki Razick

Hi,

The version number (v1) in the url path cannot be changed and it’s controlled by the framework. You will most likely have to rename your endpoints instead. You also cannot deploy different implementations of the same projection (e.g. CommissionReceiverGroupsHandling.projection) into the same installation

 

View original
Did this topic help you find an answer to your question?

1 reply

Rifki Razick
Hero (Employee)
Forum|alt.badge.img+9
  • Hero (Employee)
  • 72 replies
  • Answer
  • December 6, 2024

Hi,

The version number (v1) in the url path cannot be changed and it’s controlled by the framework. You will most likely have to rename your endpoints instead. You also cannot deploy different implementations of the same projection (e.g. CommissionReceiverGroupsHandling.projection) into the same installation

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings