Purpose
This guide defines how a CenconX Primary Dispatcher and Secondary Dispatcher use separate Apexx deployments with the same assigned CenconX lock system.
1. Supported configuration
CenconX supports either a single client/database for a single Owner (Primary Dispatcher) or a second client/database for a Secondary Dispatcher. The Secondary Dispatcher can use its own Apexx Series Software Client for assigned locks.
- The CenconX system consists of the CenconX keypad/lock system, the dormakaba Safe Locks mobile app, and dormakaba Apexx Series Software.
- Each Apexx deployment consists of the Apexx Client Software, Apexx API, Apexx Database, and MQTT Broker/Server. The Primary and Secondary Dispatchers each require their own separate deployment and supporting Apexx services.
- Primary and Secondary Dispatcher types do not have identical permissions.
The dual-deployment model provides lock-level collaboration: two dispatcher environments can work with assigned CenconX locks.
2. Tandem operating model
| Primary Dispatcher environment | Shared Functionality | Secondary Dispatcher environment |
| Own Apexx Series Software client/database | The same assigned lock can be represented in both environments | Own Apexx Series Software client/database |
| Primary deployment is configured for the Owner | The lock/keypad is commissioned at the lock and activated in software | Secondary deployment is separately configured for its assigned access |
| Primary maintains its own users, routes and OTC activity | OTC access can be dispatched by either authorized environment | Secondary maintains its own users, routes, and OTC activity |
| Owner/Primary retains functions reserved to Primary | Audit Events are visible in both systems | Secondary operates within its permission set |
3. How the two environments are used together
- Establish the Primary environment. The Owner operates through the Primary Dispatcher Apexx client/database deployment.
- Commission and activate the lock for the Primary Dispatcher. The CenconX lock and keypad are paired and commissioned at the lock. The lock is added to Apexx Series Software using its MCUID, and activation is completed at the lock using the activation package and authorized Admin credentials via a mobile App or USB connection.
- Configure and commission the Secondary Dispatcher. The Primary Dispatcher exports the lock system from its Apexx software. The Secondary Dispatcher imports the lock system into its separate Apexx deployment and designates it as Secondary, rather than Primary. The Secondary Dispatcher relationship is then commissioned at the CenconX lock. The two databases remain separate and are not directly synchronized.
- Operate the deployments independently. Each dispatcher independently manages its own software users, routes, and OTC dispatches while operating against the same assigned CenconX lock. The databases remain separate; however, the lock’s audit trail is shared between the Primary and Secondary Dispatcher deployments.
- Maintain Owner control. The Primary Dispatcher remains the Owner and retains the functions reserved to the Primary role, including removal of the Secondary Dispatcher relationship.
4. Role Division
| Capability | Primary Dispatcher tenant | Secondary Dispatcher tenant |
| Dispatch OTC | Admin, manager, dispatcher | Admin, manager, dispatcher |
| Retrieve/display audits | Administrators and Managers can retrieve audits from the lock. Once retrieved, audits generated by both the Primary and Secondary Dispatchers appear in a single audit list. | Administrators and Managers can retrieve audits from the lock. Once retrieved, audits generated by both the Primary and Secondary Dispatchers appear in a single audit list. |
| Routes | Admin, manager, dispatcher | Admin, manager, dispatcher |
| View access and holiday schedules | Admin, manager | Not Permitted |
| Configure/assign schedules | Admin, manager | Not permitted |
| Configure time delay, dual modes | Admin, manager | Not permitted |
| Create lock entries | Admin, manager | Not permitted |
| Create/remove Secondary tenant | Admin | Not permitted |
| Transfer ownership | Admin | Not permitted |
5. Operating limits and distinctions
- Static Users are available only in the Primary Dispatcher (Owner) database; the Secondary Dispatcher database does not use Static Users.
- The lock supports a maximum of 50 one-time codes assigned or dispatched at one time. When a Secondary Dispatcher is configured, 25 are allocated to the Owner and 25 to the Secondary Dispatcher.
- The Primary Dispatcher supports both Static User and OTC access modes. The Secondary Dispatcher supports OTC access only, in either Single User or Dual User (OTC + OTC) mode.
- Mobile app users receive permissions through Apexx Series Software. When the mobile app connects with the lock, audits can be transferred from the lock to the Apexx Series Software backend database.
6. Architecture boundaries
The following points define the separation between the two deployments:
- The Primary Dispatcher is the Owner. The Primary and Secondary Dispatcher environments are not equal peers.
- Each deployment maintains its own tenant data. However, audits associated with both the Primary and Secondary Dispatchers appear together in a single audit list.The Primary and Secondary deployments must each have their own separate and distinct supporting Apexx services.
- During initial setup, lock-system data is transferred from the Primary to the Secondary deployment through the export and import file. After setup, the Primary and Secondary databases do not transfer data directly to each other.