Re: From dev to production server – involving connection files

Clay Fox — Mon, 12 May 2008 14:09:34 GMT

Well. You are right the modify process for UDCs is not real good. Even switching is a pain.

You need the UDC files on the production server which you may be able to copy them directly to it and/or modify them as XML.

You also could create new ones and then convert them and have them created on the production site.

Probably best, once they are on the production site, is like you said to go into the manifest and manually change the reference, that way your bindings and things are not getting broken or needing additional work.

From dev to production server – involving connection files

OddGear — Sat, 10 May 2008 16:00:03 GMT

I´ve been working on a InfoPath Form Services project where I was not allow, due to permission policy, to develop the form straight on the production server. So I first implement the solution on a dev server in same domain. Most of the data connections are to web services and databases located on various servers within the network. As recommended in “muti hop” scenario I converted the connections to connection files (udcx) centrally managed. Everything is working properly so it´s time to implement the solution on the production server but I´ve to change the “Connection source” from dev to prod. As I see it ones those connections have been converted it´s not possible to modify them trough Tools->Data connections->connecton_name->Modify.

The only thing I can think of is to save as source file - open the manifest file and manually change it there but can´t imagine that that would be the recommended way.

So my question is: Can this reference be changed? And what would be best practice in this scenario?

Newbie Questions

Re: From dev to production server – involving connection files

From dev to production server – involving connection files