Upgrading from 2.5 to 3.0 - tsgrp/HPI GitHub Wiki

OCMS Config Updates

With OCMS 3.0 comes the concept of an 'application ID' that can be attached to one or more OCMS instances hitting the same OpenContent. If your OCMS does not specify an application ID, OpenContent will assume an appId of default. OCMS's configs and user folders are now separated out by application ID in the repository. So, for example: /hpi/default/configs and /hpi/default/user. If you would like to upgrade from OCMS 2.5 to 3.0, you can follow this approach:

  1. Create a default folder under /hpi or use another app ID if you've built OCMS with a different ID.
  2. Move your configs and user folders from /hpi to /hpi/{appId}
  3. Login to OCMS 3.0 and verify configs.

Alternatively, you could also simply install a clean OCMS 3.0 in a QA/Test environment:

  1. Install OCMS 3.0 in a QA or Test environment
  2. Configure OCMS based on your existing production environment
  3. Upgrade the production environment to OCMS 2.5
  4. Port the configurations from QA/Test to Production.

Action Configurations

Certain action configured under a prior version of OCMS will require that you remove and re-add the configuration in order to work properly.

  • Split PDF
    • No need to remove entirely. Remove the tracs from the action configuration in order to view them in the Split PDF Action.
  • Get Document Link
  • Advanced Combine to PDF
    • Note that this action is no longer available as a folder action. Use Combine PDF as a group action in View All Docs instead.

Alfresco Chain Versionable

For Alfresco clients on the 2.5 or previous implementation of the Controlled Document solution, upgrading to 3.0 must be done by either:

  • Migrating all content from the old document types to the new Chain Versionable Construct (development required) or
  • Updating OpenContent to use the legacy types and aspects to support the old object model and security