The Support Article SA-8595, https://pdn.pega.com/support-articles/changing-gateway-configuration-throws-error has a resolution that is unclear. The prgateway.xml is formed based on the configurations done on the gateway console. To disable the gateway console, the parameter GatewayConsoleConfigurationMode has to be set to "Disabled". When this is done, do we have to move all the configurations set in the prgateway.xml back in to the web.xml? Is the prgateway.xml no longer referred to for tee configurations when the GatewayConsoleConfigurationMode is set to disabled?
The formats and the structure of the xml seems different for example if the prgateway.xml is
Thanks for your response, We have actually done this and were able to solve the issue.
I guess the remaining questions that needs answering is "Is the prgateway.xml no longer referred for the configurations when the GatewayConsoleConfigurationMode is set to disabled in web.xml?". If so all the changes from here on should be done just on the web.xml, and prgateway.xml doesnt need not to be updated. If not then keeping prgateway.xml and web,xml in sync could be the only option to make sure things work. I would wait for the product support team to confirm on this.
In the GatewayConsoleConfigurationMode disabled mode the prgateway.xml will not referred while loading the Gadget.
In the other modes prgateway.xml which gets created in User’s home directory will have this information to make it work. We should manually update the Source Host params, URL params or logging levels on web.xml of prgateway app for loading the gadget without any issues.
Thanks for the confirmation. Our investigation has proved the same thing too.
This seems no where documented.
Especially if some one has changed the location of their config file using the GatewayConfigFile param one assumes it is playing a role, but if the GatewayConsoleConfigurationMode param is set to Disabled then the prgateway.xml seems to be contributing nothing.
More over, even if the value of GatewayConsoleConfigurationMode is set to disabled there are different ways to read the host information, which I thought would have been tricky. But that is for a different discussion altogether.