Good morning!

In our APIC v5 environment we use RTVS and have the proxy setup on the mpgw object in Datapower.

We are migrating to APIC v10 on Openshift.  I tried setting this up in a similar fashion on one of the Datapower gateway pods and I can set it up in the Connection Policy/Proxy policy section of the apiconnect api gateway object shown here:


However it disappears when the pod restarts (as expected).  I am trying to insert this configuration using a configMap but I am unable to find any reference to an "apiconnect" object in the file apiconnect.cfg for which I would inject the custom configuration.  Am I thinking this through the right way and if not, is there any guidance on how to properly integrate RTVS in APIC v10 on Openshift?

------------------------------
Jennifer Stipe
------------------------------

I think you're looking for the APIC feature "Gateway Extensions".

This isn't specific to RTVS.

For any configuration that is automatically generated for you, it won't work to manually change it on the gateway, since the auto-generation would periodically overwrite your changes --- as you expected it to, and as you experienced --- not just at pod restart, but also when the API Manager republishes to the API Gateway.

This is one of the purposes of Gateway Extensions.  For an APIGW (which you are using, but unlike the v5 compatibility GW), the Gateway Extensions have two purposes:
1. They can add generic extra gateway functionality, which for k8s also could be done using a configMap.
2. They can *modify* automatically generated configuration, in which case this automatic modification happens every time, so with every publish on every gateway in your cluster / gateway service.

In this case, you're asking to modify the API Gateway object (apigw) itself, which is automatically generated by the publish, therefore you need purpose (2) to modify that automatically.

Just note the name it's generated at on the gateway, and then in the API Manager add the configuration that modifies it --- the same CLI you would otherwise do manually on one gateway --- and that should then be applied every time on every gateway.

Here is the relevant documentation page, specific to the APIGW, for the most recent release 10.0.x:  https://www.ibm.com/docs/en/api-connect/10.0.x?topic=behavior-gateway-extension-guidelines-datapower-api-gateway
It doesn't have an example of modifying the exact property or object you're talking about, but it does have a couple of very equivalent examples of modifying properties on auto-generated objects.

------------------------------
Morris Matsa
------------------------------