IMPORTANT:
this is not a Support Forum! Experienced users might answer from time to time questions posted here. If you need a professional and reliable answer, or if you want to report a bug, please contact Altova Support instead.

Profile: TSwartz
About
User Name: TSwartz
Forum Rank: Newbie
Real Name:
Location Eagan, MN
Occupation:
Interests:
Gender: None Specified
Statistics
Joined: Wednesday, September 18, 2019
Last Visit: Thursday, September 19, 2019 1:18:06 PM
Number of Posts: 1
[0.01% of all post / 0.00 posts per day]
Avatar
Last 10 Posts
Topic: Migration process
Posted: Wednesday, September 18, 2019 7:24:05 PM
I'm a relatively new Altova MapForce/FlowForce user; we just started using the system. Can anyone recommend documentation on best practices for a migration process?

I'm thinking specifically about the .MFD files in MapForce and both the Jobs and Mappings in FlowForce. Obviously, I create them in Dev, where they point to dev Data Sources and file server locations. When it comes time to migrate them up to Test, and then Production, is there a process that does not include manually changing the Data Source(s), Credentials, Directories, etc.?

Thanks!
PS I did search here and elsewhere for this, but found nothing helpful.

Use of the Altova User Forum(s) is governed by the Altova Terms of Use.