Install the latest server and transcoder packages.
Use the check command to verify that the configuration file is still valid.
$ vidispine check $ vidispine db check
Make sure that the server is stopped. On CentOS 6 or Ubuntu:
$ /etc/init.d/vidispine stop
On systems using systemd:
$ systemctl stop vidispine
Migrate the database:
$ vidispine db migrate
Before migrating you can verify the pending migrations using the --dry-run flag.
$ vidispine db migrate --dry-run
The dry-run output is for informational use only. Do not execute any SQL statements in the output directly.
Start all Vidispine services.
To move from GlassFish to the standalone server application:
- Make sure that GlassFish is stopped.
- Install the server and transcoder packages as described in the installation guide.
- Modify the server configuration to match the GlassFish configuration.
- Use the same database settings.
- Add any custom JVM settings to the service configuration.
- Migrate the database.
- Start the vidispine, solr and transcoder services.
Once all steps have been performed and Vidispine is up and running:
- Re-index items, collections and files to populate Solr.
- Remove GlassFish.
Upgrading without re-indexing¶
It is also possible to avoid the re-index step by moving the existing Solr index to the new location used by the solr service.
Make sure that no application is using Vidispine.
Disable all services except the indexing service to make sure that all pending index updates are sent to Solr and removed from the JMS queue.
$ http put "localhost:8080/API/vidispine-service/disable" $ http put "localhost:8080/API/vidispine-service/service/IndexCruncher/enable"
Then wait until all messages on the JMS queue “IndexQueue” have been processed by watching:
$ /opt/glassfish3/mq/bin/imqcmd list dst
Make sure that the vidispine-solr package is installed and that the solr service is not running.
$ systemctl stop solr
Move the Solr index to the new location.
$ mv /opt/glassfish3/glassfish/solrhome/solr/collection1/data/ /var/lib/vidispine/solr/collection1/data
Start Solr and verify that the new index is in used by checking the document count from the Solr admin page at http://localhost:8983/solr/#/collection1.