Changes between Version 8 and Version 9 of MapGuideRfc23

Timestamp:

09/28/07 11:40:43 (17 years ago)

Author:

stevedang

Comment:

--

MapGuideRfc23

@@ -11 +11 @@
 ||Last Modified||Steve Dang [[Timestamp]]||
 ||Author||Steve Dang||
-||RFC Status||adopted||
-||Implementation Status||under development||
+||RFC Status||implemented||
+||Implementation Status||completed||
 ||Proposed Milestone||2.0||
 ||Assigned PSC guide(s)||(when determined)||
@@ -42 +42 @@
 Modifications need to be made to the !MapGuide server and its installer:
 
-1. The server will detect a version mismatch at startup, and throw an exception along with instructions on how to upgrade.
+A. The server will detect a version mismatch at startup, and throw an exception along with instructions on how to upgrade.
 
  Like other exceptions thrown at startup time, this Version Mismatch exception will stop the server from running:
@@ -51 +51 @@
  The error message will include a brief description about the problem and a reference to the detailed upgrade documentation.
 
-2. During setup, the installer will back up the existing repositories if necessary, then run the upgrade utilities (which will do nothing if the repositories have already been upgraded). In rare/complex situation, the installer may encounter some upgrade problem (e.g. different combinations of versions of repositories, including no longer supported ones, etc.). When this happens, the installer will continue the installation without the upgrade, and at the end, it will display a brief description about the problem and a reference to the detailed upgrade documentation. Note that, the installer will need to install the upgrade utilities so that they can be run independently at a later time. This is useful when:
+B. During setup, the installer will back up the existing repositories if necessary, then run the upgrade utilities (which will do nothing if the repositories have already been upgraded). In rare/complex situation, the installer may encounter some upgrade problem (e.g. different combinations of versions of repositories, including no longer supported ones, etc.). When this happens, the installer will continue the installation without the upgrade, and at the end, it will display a brief description about the problem and a reference to the detailed upgrade documentation. Note that, the installer will need to install the upgrade utilities so that they can be run independently at a later time. This is useful when:
 
  * The version mismatch detected by the server or the upgrade problem encountered by the installer does occur.
  * The user would like to restore previously backed up repositories, then upgrade them without rerunning the installer.
+
+Here are the manual steps on how to upgrade the repositories:
+
+1. Shut down the existing !MapGuide Server (e.g. "1.2.x") if it is running.
+
+2. Change to the !RepositoryAdmin directory (e.g. "C:\Program Files\!MapGuideOpenSource\Server\!RepositoryAdmin\" or "/usr/local/mapguide/server/RepositoryAdmin/").
+
+3. Run !BackUpOnlineRepositories.bat (or !BackUpOnlineRepositories.sh).
+
+4. Run !RestoreRepositories.bat (or !RestoreRepositories.sh).
+
+5. Un-install the existing !MapGuide Server. Note that the existing repositories will not get removed.
+
+6. Install the new !MapGuide Server (e.g. "2.0.0"). Note that the Server will fail to start if it tries to open old repositories.
+
+7. Shut down the newly installed Server if it started successfully (because it created new repositories on a different location).
+
+8. If the new !MapGuide Server is installed on a different location than the old one, delete the Repositories directory then copy/move the old one to the new location (e.g. "C:\Program Files\!MapGuideOpenSource\Server\Repositories\" or "/usr/local/mapguide/server/Repositories/").
+
+9. Change to the !RepositoryAdmin directory (e.g. "C:\Program Files\!MapGuideOpenSource\Server\!RepositoryAdmin\" or "/usr/local/mapguide/server/RepositoryAdmin/").
+
+10. Run !UpgradeRepositories.bat (or !UpgradeRepositories.sh).
+
+11. Run !SetupRepositoryIndices.bat (or !SetupRepositoryIndices.sh).
+
+12. Restart the Server. It should successfully open the upgraded repositories.
+
+Note that the upgrade could take longer time if you have large repositories.
 
 == Implications ==