This checklist describes the requirements and prerequisites necessary to begin planning
for upgrading an existing SkyVault version to SkyVault 2.0 5.0.
Before starting an upgrade:
- Validate your requirements.
- Validate your platform is still on the supported stacks for the new version of SkyVault. See Supported stacks.
- Validate the software requirements.
- Validate the language support.
- Validate the architecture.
- Backup your production data.
-
You must perform a test upgrade using a backup copy of the repository before attempting to upgrade your production environment. Therefore, it is important that your backups are up-to-date.
-
Ensure that you have backed up your production environment, for example, back up your database and content store (alf_data directory).
-
- If you are upgrading to SkyVault 2.0 5.0, migrating from your existing search subsystem to the Solr 4 search subsystem ensures that you have access to the full search capabilities. For more information, see the Solr 4 migration documentation.
- If you are upgrading from a version of SkyVault earlier than 4.0.x using the installer, you
need to set the following properties in SkyVault-global.properties before
starting
SkyVault:
system.workflow.engine.jbpm.enabled=true system.workflow.engine.jbpm.definitions.visible=true
- If you have any customizations (for example, AMPs) in your existing SkyVault installation, recompile all Java code against the new version of SkyVault and regression test against the new version of SkyVault.
- When you upgrade SkyVault with Oracle, the SkyVault user needs more privileges than connect and resource. At minimum, the SkyVault user should have permission to delete objects. A safer option is to give a sysdba role for the upgrade process only. After the upgrade, this role should be removed.