How to Migrate Existing Storage Parameters to Database Storage
The Weave Server can store information regarding the user's Weave usage, for example the bookmarks that a user saves. This information is stored on the server so that when the user begins a new session, Weave can access these details. There are also some system-wide details that Weave stores and retrieves. As an alternative to storage in the Weave Server, this information can be stored in a database (being any data source configured within Weave).
If you are using Weave's internal system for managing storage parameter, but want to move to database storage, then it's likely that you'll want to migrate your existing storage parameters. To migrate these parameters follow the steps below.
Step-by-step guide
At the OSGi prompt, use the
ustorage save
andstorage save
commands to write the user storage and server storage parameters out to text files, e.g.ustorage save c:/temp/user-store-dump.txt storage save c:/temp/server-store-dump.txt
If a location is specified (as shown above), the contents will be saved to that file otherwise the content will be saved to an internal file location.
Switch over configuration so that a database is used for storage. For details about configuring Weave to use a database for user storage refer to this How-to page.
At the OSGi prompt, use the
ustorage load
andstorage load
commands to read the user storage and server storage parameters from the text files created in Step 1, e.g.ustorage load c:/temp/user-store-dump.txt storage load c:/temp/server-store-dump.txt
If a location is specified (as shown above), the contents will be loaded from that file otherwise the content will be loaded from an internal file location.
Open Weave and check that the previously stored parameters (such as Bookmarks, save Redlines, etc.) are available.
Also refer to the following sections of the Weave System Administrator Guides:
Related articles