MG65Migration-Configuring and Loading Data
From MapGuide Best Practices Wiki
The first phase of migration is to configure and load the spatial and tabular data into Autodesk MapGuide Enterprise, and connect to external databases. With Autodesk MapGuide Enterprise, setting up data sources is accomplished by using the Studio software. As with Autodesk MapGuide 6.5, creating an organized data structure is crucial to keeping the data organized. With Autodesk MapGuide Enterprise, rather than creating file folders on the server disk drives, folders are created using Studio. It is recommended that the file folders mimic the existing Autodesk MapGuide structure to maintain consistency. However, if the existing structure is not well organized, the migration process can provide an opportunity to correctly organize file structure and data.
Once the folders have been created, the spatial and tabular data can be imported into Autodesk MapGuide Enterprise using the Studio software. Unlike Autodesk MapGuide 6.5, spatial data sources do not need to be created with the administrator. Studio establishes the data source connection when the data is loaded.
Another major difference between Autodesk MapGuide 6.5 and Autodesk MapGuide Enterprise is that Autodesk MapGuide Enterprise eliminates the need to create elaborate data update routines when loading data. Many administrators of Autodesk MapGuide sites create batch files using the SDF Loader to define a process that updates the spatial data. This process is run either automatically or manually. In many case, administrators do not create update routines but rather execute the entire process manually. With Autodesk MapGuide Enterprise, when data is loaded, a load procedure is created. The load procedure can include several data sets so that when data needs to be updated, the load procedure can be run simply and quickly.
