Maruan Sahyoun : The general approach to this scenario is to create a new cloud configuration for your service and add that cloud service to the page where form is used/added. Now you can have different values to these configuration in your different servers(dev, qa& prod).
And in your code you read these cloud config values rather than the OSGI Configs. I have personally used this approach for many of my forms and it saves a lot of development effort and is also generic as per coding guidelines
Hope this helps !!!
Hey Jagjeet Singh - do you have a blog that shows this approach?
maybe it didn't get across. On the Dev & Test AEM Forms server we'd like to call the Dev & Test processing server. After publishing we'd like to call the Prod processing server from the Prod AEM Forms server. If we define a cloud service wouldn't the service address be the same on both instances of AEM Forms?
The whole point behind making a cloud services is that it is configurable, and you can give the privilege to super-authors and reduce dependency from server administrator.
You can have a configuration parameter for the service url or the server type, and that can be changed as per environment. If you can see how we configure analytics/target/dtm or any such tool using cloud services, you will get a fair idea of what I am trying to convey.
I will try and create a small blog post in a couple of days giving detailed step by step approach for this.
I looked into adding a custom cloud service and think I understood what you are talking about. Will be interested to look at your blog post as soon as this is available. Would it also be possible using a Form Data Model to change the (SOAP) URL from Dev to Production? We are already looking into using Form Data Models as a kind of integration layer.