Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Orion/Metadata migration"

(Orion 4.0 Migration)
Line 80: Line 80:
 
=== Orion 4.0 Migration ===
 
=== Orion 4.0 Migration ===
  
The server administrator should perform the following steps to migrate the server from 3.0 format to 4.0 format:
+
The server administrator should perform the following steps to migrate the server from the legacy 3.0 format to the simple format:
  
 
* Backup the server. The migration renames project folders, so if there is some issue with the migration, the server may need to be restored to it's original contents.
 
* Backup the server. The migration renames project folders, so if there is some issue with the migration, the server may need to be restored to it's original contents.

Revision as of 18:24, 4 November 2013

Orion 3.0 (CompatibilityMetaStore)

The legacy server metadata is organized as follows:

File / Folder Description
/serverworkspace/.metadata/.plugins/org.eclipse.orion.server.core/.settings/Projects.prefs Project list
/serverworkspace/.metadata/.plugins/org.eclipse.orion.server.core/.settings/SiteConfigurations.prefs Site List
/serverworkspace/.metadata/.plugins/org.eclipse.orion.server.core/.settings/Users.prefs User List, includes preferences, user rights and list of workspaces
/serverworkspace/.metadata/.plugins/org.eclipse.orion.server.core/.settings/Workspaces.prefs Workspace list
/serverworkspace/A folder root of "Project" with project id "A"
/serverworkspace/B folder root of "Project Two" with project id "B"
/serverworkspace/.metadata/.plugins/org.eclipse.orion.server.user.securestorage Equinox Secure Storage for Users and Passwords
/serverworkspace/.metadata/.plugins/org.eclipse.orion.server.core.search Orion Search
/serverworkspace/.metadata/.plugins/org.eclipse.orion.server.core/tasks Orion Tasks

Notes

If you wish to use this legacy Orion 3.0 storage format, you should specify in your orion.conf:

orion.core.metastore=legacy

Orion 4.0 (SimpleMetaStore)

The simple server metadata is organized as follows:

File / Folder Description
/serverworkspace/metastore.json Root of the orion filesystem.
/serverworkspace/an/anthony/user.json Server metadata user file, includes preferences, user rights and list of workspaces
/serverworkspace/an/anthony/OrionContent/workspace.json Server metadata workspace file, includes project list
/serverworkspace/an/anthony/OrionContent/Project.json Server metadata project file, includes content location
/serverworkspace/an/anthony/OrionContent/Project/ folder root of project "Project"
/serverworkspace/an/anthony/OrionContent/Project Two.json Server metadata project file, includes content location
/serverworkspace/an/anthony/OrionContent/Project Two/ folder root of project "Project Two"
/serverworkspace/.metadata/.plugins/org.eclipse.orion.server.core.search Orion Search (no change)
/serverworkspace/.metadata/.plugins/org.eclipse.orion.server.core/tasks Orion Tasks (no change)

Notes

The default layout will now be
orion.file.layout=userTree
, so user folders are organized in a hierarchy. In this case anthony is under /an/anthony on the server.

Orion 4.0 Migration

The server administrator should perform the following steps to migrate the server from the legacy 3.0 format to the simple format:

  • Backup the server. The migration renames project folders, so if there is some issue with the migration, the server may need to be restored to it's original contents.
  • Delete the old index folder /serverworkspace/.metadata/.plugins/org.eclipse.orion.server.core.search. Since the projects are moved, they will be reindexed.
  • Add the properties to the orion.conf configuration file for your server:
orion.core.metastore=simple
orion.file.layout=userTree
  • Start the orion server.
  • Review the migration log in /serverworkspace/.metadata/migration.log to ensure there are no ERROR messages.

Back to the top