Skip to content
This repository has been archived by the owner on Aug 11, 2021. It is now read-only.

Steps for an upgrade to a new version

Jump to bottom
Mark Leusink edited this page May 15, 2014 · 2 revisions

A new version of Continuity consists of 2 templates: the Continuity application and self-service database.

Here are the steps to upgrade to that new version (written by Richard Sharpe):

  1. Open the template in or 8.5.3 (or higher) client and 'clean' the project. We were getting some corrupted java class errors and I'm not sure if this was a case of the template being built in Notes 9 and back-ported to 8.5.3. A 'Clean' recompiles the classes.

  2. On our public demo server version, in the nsf, edit BBBase.js to uncomment line 3 and comment line 4 - allowing demo users to be 'Ted Barnhouse' for the BB (better user experience for folks wanting to see the BB UI) //var userName = "CN=ted.barnhouse/O=ZetaComm"; var userName = session.getEffectiveUserName();

  3. Sign the template on the CY server with the TS Admin id file

  4. Refresh any Continuity instances, changing the template name to inherit from in the continuity.nsf properties

  5. Sign the template on the Demo server with the server ID.

  6. Refresh any Continuity instances, changing the template name to inherit from in the continuity.nsf properties

  7. Log in to Continuity with your Admin account and open Settings - change the 'Continuity Template Database Path' to point to the new template version. (Both servers).

Alternatively...

If the database setup is performed as written here: https://github.com/teamstudio/Continuity/wiki/Application-architecture,-installation-and-requirements steps 4, 6, and 7 aren't needed anymore. They are replaced by:

  1. Sign and clean the new (two) databases and refresh the self-service as well as the Continuity template on the server with the new design.
  2. Optionally, you can then refresh one of the Continuity instances (a 'test' instance) from the Continuity template (that now holds the updated design). Since that instance already inherits from the standard template, you don't need to change the template name and can just perform a refresh.
  3. If everything looks Ok: start the Designer task on the server to update all Continuity instances.

Testing the new version

The Continuity application now features a system test page (systemTest.xsp) that can be used to perform a set of tests to check if the application is working correctly.

Clone this wiki locally