We're in the same boat. We are setting up an identical 'TEST' platform to mirror production for all the regular reasons (patches, upgrade, etc) and that will include the ability to upgrade/test all of our service connect routines.
We are also making a small Virtual Server on one of out VM hosts where we will install only the basic Progress appserver layer so that we can have a dedicated Service Connect 'DEV' platform (the admin tool, workflow designer, etc will be installed here as well).
What we've found in using the .Net refs, is that we've been introducing corruption in the workflows when trying to redirect them between Test/Pilot/Production, and that the other shortcuts are not perfectly reliable. So, with this setup, we can move our production workflows from Prod, to Dev, to Test without introducing the corruption and nicely sandbox each iteration of testing.
Good luck!
Mike
We are also making a small Virtual Server on one of out VM hosts where we will install only the basic Progress appserver layer so that we can have a dedicated Service Connect 'DEV' platform (the admin tool, workflow designer, etc will be installed here as well).
What we've found in using the .Net refs, is that we've been introducing corruption in the workflows when trying to redirect them between Test/Pilot/Production, and that the other shortcuts are not perfectly reliable. So, with this setup, we can move our production workflows from Prod, to Dev, to Test without introducing the corruption and nicely sandbox each iteration of testing.
Good luck!
Mike