Hello Vishal: The situation you describe is working as designed. The majority of the configuration on DataPower for API Connect integration cannot be persisted (marked external). The configuration of the gateway service on DataPower that is used by API Connect must come 100% from API Connect and uses the definitions from API manager (the underlying YAML files). If you need to extend the configuration that the gateway service needs, you must use gateway extensions as you state. Therefore, it appears that you problem is appropriately setting up the use of gateway extensions so that these extensions are "pushed" to DataPower when the gateway service on DataPower starts.
For clarity, the only "objects" on DataPower that are persisted are the ones the API Connect states you must configure on DataPower (that is based on platform). This is basically only the "API Connect gateway service" that uses the "gateway-peering manager" that uses "gateway peering" instances.
------------------------------
F Hackerman
------------------------------
Original Message:
Sent: Thu June 15, 2023 01:48 PM
From: Vishal Ghadage
Subject: DataPower gateway losing all custom changes after every reboot/restart
Hi Gyus,
Recently I have created an environment of APIC V10.0.5.2 and identify one issue. I am using RPM base DataPower Service which is deployed on Red Hat Linux 8. In my current environment i have modified the webapi MPGW with custom changes like (JSON Setting and Suppressed some Hedears). Everything works fine till this point but whenever I reboot or restart the services. All webapi MPGW values reset to default.
I have tried to deploy a gateway extension as well but still I am not able to resolve this issue.
Need your help to resolve this issue
------------------------------
Vishal Ghadage
------------------------------