Installation and server requirements
The Continuity solution consists of the following databases:
This database contains the Continuity application, including the mobile (Unplugged) interface and all data.
ACL
The ACL of this database is automatically setup if you create a new Continuity instance. See here for details.
Used to manage Continuity instances and for self-service functions (password recovery, account activation). This database also contains the Continuity login form.
ACL
- Anonymous (reader, write public documents, no roles)
- -Default- (reader, write public documents, no roles)
- LocalDomainServers (manager, [admin] role)
- LocalDomainAdmins (manager, [admin] role)
- <application administrators> (editor, create- and delete documents, [admin] role). This can be the same group as in the adminGroup field of the settings document in the self-service/ config database.
(only required for hosted installations, optional for on-premises installations)
This database must be created from the Domino Directory application template (pubnames). It contains all users and groups that are created in all Continuity instances on this server.
ACL
- Anonymous (no access)
- -Default- (no access)
- LocalDomainServer (full access)
- LocalDomainAdmins (full access)
These are the default Unplugged configuration and log databases that are set up as part of the Unplugged installation process. Continuity registers new instances and users in this database so they receive the mobile application.
ACL
Default ACL as described in the Unplugged documentation.
Continuity uses the following Domino system databases:
- Directory Assistance (normally: da.nsf, only used if Continuity uses a secondary directory): must have an entry for the Continuity secondary directory, including the Group Authorization option. This database is only required if Unplugged is configured to store users in the secondary directory.
- Domino Web Server Configuration (domcfg.nsf): must have an 'login form mapping' to the Continuity login form in the config/ self-service database.
- Continuity requires IBM Domino/ XWork server, v8.5.3 (minimum version, 9.0.1+ is recommended). The version used needs to have either Upgrade Pack 1 or a recent version of the Extension Library installed. Note that Domino 9.0 (and higher) has a compatible version of the Extension Library built-in.
- The user creating a new Continuity instance needs to have rights on the server to create new databases.
- The server should be able to send mail (for notifications send by Continuity). Receiving mail is not required.
- It is strongly recommended that SSL is enabled and enforced for additional security.
The recommended setup for a server containing multiple Continuity instances (hosted installation):
- A Continuity installation consists of two databases: the self-service database and the Continuity template. Instanced of Continuity are created from the Continuity template database. The template has a template name without a version number (e.g. "Continuity template"). The path to that template is entered in the Settings.
- For every new Continuity instance that is created, one database is created (continuity.nsf in the clients folder) that inherits from that template ("Continuity template").
- The process to update the new design with a new version is described here: here.
The setup for an on-premises installation is basically the same as for a hosted installation, but instead of creating multiple instances for different organisations you only create a single instance.
