ALM 2.2 to ALM 23.1 - ALE Learnset Manager - 23.1 - 23.1 - Brainware - external

ALE Learnset Manager Installation and Upgrade Guide

Platform
Brainware
Product
ALE Learnset Manager
Release
23.1
License
Take a backup of the following database tables of ALM:
  • LEARNSET_DOC
  • LEARNSET_DOC_IMAGE
  • LEARNSET_PROJECT_DATA
  • LEARNSET_PROJECT
  • LEARNSET_DOCCLASS
  • LEARNSET_DOCCLASS_FIELDDECL
  • LEARNSET_FIELDDECL
  • LEARNSET_DOC_FIELD
  • LEARNSET_SCHEDULER

Navigate to the install location of ALM on the server. Example: ...\ALM\WEB-INF\conf. Open alm-config-db.xml and make a note of the username. This is required during the installation of ALM 23.1.

To upgrade ALM from ALM 2.2 to ALM 23.1, complete the following steps:

  1. Ensure that all the existing ALM servers are stopped. There can be multiple servers located in different machines.
  2. Uninstall ALE Learnset Manager by deleting the folder C:\Program Files\Apache Software Foundation\Tomcat<installed version>\webapps\ALM and C:\ALM.
  3. Install ALE Learnset Manager (23.1) on the same machine using the same database user credential that was used with the previous ALE Learnset Manager (v 2.2) installation.
    Note: Do not delete the database.
  4. Verify whether the alm-config-db.xml located in the <Server directory>\ALM\WEB-INF\conf has the entry for aesPwdKey property under the readSecret bean.
  5. Start the servers.
  6. Verify whether Starting: Hyland ALE Learnset Manager 23.1 is printed in the alm-ws.log.
  7. Before logging on to ALE Learnset Manager, clear your browser history and cached files.
  8. Log on to ALE Learnset Manager and verify if the projects created with the previous ALE Learnset Manager (v 2.2) are available.
Note: During upgrade, previous user credentials get deleted and new user credentials (provided by the user during installation) are stored in the database in an encrypted format. In case the new user credentials are same as previous version's (ALM 2.2) credentials, then the user account is recreated in an encrypted format using the dynamic key generated during installation.