Hi RT,
Per Ivy's comment above, the DP 10.5.0.6xy firmware level does support the invoke 2.3.0 version policy at the Gateway, but the UI doesn't recognize it. That will be resolved in a future release. For your comment "There is no mention of use-http-10 property in invoke version 2.3.0."
That is correct. The Restrict to HTTP 1.0 checkbox option in the UI was deprecated in the 2.3.0 version of the policy. Instead there is a HTTP Version dropdown where you can select 1.0 if you choose.
Given it is deprecated now, I'd assume the use-http-10 property, if found in a version 2.3.0 invoke, will still work for now, but if you're changing versions of the policy you should change to use the supported property for that policy version, i.e. http-version: HTTP/1.0, as support for the use-http-10 property may be removed in the future. Note the documentation link you referenced does indicate the use-http-10 property is only for policy version 2.0.0 and http-version is for policy 2.1.0 and later.
Best Regards,
Steve
------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM
------------------------------
Original Message:
Sent: Fri January 05, 2024 05:09 PM
From: Steve Linn
Subject: invoke policy usage
Hi RT,
Sorry, I should have asked in my previous post, what DataPower version are you using with APIC Version 10.0.5.5?
Thanks,
Steve
------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM
------------------------------
Original Message:
Sent: Thu January 04, 2024 03:29 PM
From: Steve Linn
Subject: invoke policy usage
Hi RT,
Both versions are native policies where the only difference is the latter version has a couple new properties. It would seem to me that the newer version showing up in the user defined category is a UI defect, which I will check with the UI team. Depending upon the version of API Connect you're using, I would expect the latest version to be showing in the policies category so any drag and drop would provide the latest invoke policy capability. If you originally developed the API with a prior API Connect version that setup the older version invoke policy, looking at its policy properties would still show only the 2.2.0 properties if you needed to make any modifications to those properties. If you wanted to add the newer 2.3.0 properties, you could view the source of the API and manually change the policy version to the 2.3.0 version and then the UI would show the new properties with that version. What version of API Connect are you currently using?
Best Regards,
Steve
------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM