Developing SharePoint applications that use browser-enabled InfoPath forms requires a lot of interactions with the Web Services and it's usually done via DataSources properties of the InfoPath. You store all your connections to the Web Service into the DataSources and uses properties name to communicate.
The tricky situation of DataSources is in deployment. When you compile and publish InfoPath form it includes the connection settings that you configured locally, and the InfoPath form wont work when you deploy in to another box (UAT or Production) where you services and server names have different names and paths.
The solution is to update the DataSource url dynamically. Posting here the code-snipped I used across several projects. The idea to move the service name to the SharePoint web.config and update DataSources host name by checking if the property contains your service name of "_vti_bin" for the OOTB Web Services.