Opened 15 years ago
Closed 13 years ago
#1112 closed enhancement (fixed)
Maestro: please consider adding some inter-server migration tools
| Reported by: | jbirch | Owned by: | jng |
|---|---|---|---|
| Priority: | low | Milestone: | Maestro-3.0 |
| Component: | Maestro | Version: | |
| Severity: | minor | Keywords: | |
| Cc: | External ID: |
Description
It would be incredible handy to be able to click on a map and say "Migrate to another server", and have all of its dependencies compared against the other server and updated if required.
Data connections may require some thought. There may be connection string differences between test and live that the user would have to be able to modify when writing. Along these same lines, there would have to be the option to not update existing data sources. In this case, another could check would be to ensure that the data source contains all of the attribute required for the layers, etc.
This problem is partially solved by packages, but in an environment like ours where we are trying to encourage standardisation by having both Common and Per-Application sections, it can be difficult to migrate new applications, layers, etc into production.
Attachments (3)
Change History (8)
comment:1 by , 15 years ago
| Status: | new → assigned |
|---|
comment:2 by , 15 years ago
I wonder if this would be better as a repository comparison tool. I use a visual diff tool called Beyond Compare on an almost daily basis for doing directory comparisons. It has a great interface for showing folder and resource differences, and then a file-specific diff tool to show the differences on supported file types. It would be awesome if there was something like this for MapGuide repositories. I'll attach some screen shots.
comment:3 by , 15 years ago
| Milestone: | → Maestro-2.1 |
|---|
comment:4 by , 14 years ago
| Milestone: | Maestro-2.1 → Maestro-2.5 |
|---|---|
| Owner: | changed from to |
| Status: | assigned → new |
I think this is only really practical if Maestro was able to connect to more than one repository at the same time.
comment:5 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I consider the implementation of inter-server migration tools for 3.0 sufficient to satisfy the needs expressed in this ticket.
Hmm, it will take some time to do, but it could be done.
The obvious problem is the dataconnections which have local settings (as you point out).
I imagine that a user can perform this on a map, a weblayout or a fusion application.
A progress bar would show while evaluating what items to update.
A dialog should show the required changes (overwrites). The user should be able to de-select a change, and featuresource overwrites should be disabled, if the featuresource is using external data. This can be determined by looking for the %MG_DATA_FILES% string in the connection properties.
When the user clicks OK, simply copy all resources to the remote server. Perhaps it would be more efficient to just roll a package and send that to the server.
Permissions are tricky, because the users may not exist on the remote server. For starters, permissions could be ignored.