Z9OpenService

The Z9OpenService is the bridge between this station's Enterprise Security data model and a Z9/Flex host. Place one instance under the station's Services. Once the station is taken over by a host, the service maintains the connection and keeps the two sides in sync; no per-object configuration is needed on the station side.

What syncs in which direction

• Uploaded to the host (the station is the authority): the access-control doors and their remote modules, door hardware configuration (default access mode, strike time, re-lock), door status (online, locked/unlocked, open/closed, forced, held), and access/door events.
• Downloaded from the host (the host is the authority): people and cards, schedules and holidays, access rights, card formats, and door commands (unlock, access mode changes, lockdown). Downloaded objects appear in Enterprise Security as regular records.

Records not created by Z9/Flex are removed

Z9/Flex is the only source of access control on a station it has taken over. Each time the service connects to the host it deletes every Enterprise Security cardholder, card (badge), access right, and card (Wiegand) format that was not created by Z9/Flex. Records enrolled directly on the station are removed on the first connect and must be managed in Z9/Flex from then on. Schedules and holidays are kept, but any link wired from a schedule or threat level group into a door strike's unlockSchedule, overrideSchedule, threatLevelGroup, or scheduleLockdownThreatLevel input is removed. Other strike inputs, such as unlockInput (for example a fire-alarm release), are not touched. This cannot be turned off.

Before deleting anything, the service saves a copy of everything it is about to remove (cardholders, cards, access rights and who had them, card formats, and removed schedule links) as spreadsheet (CSV) files in a zip under shared/z9flex/purge-archive/ in the station's file space; download it from Workbench under the station's Files > shared. The copy holds cardholder names, card numbers, and keypad PINs, so it can be used to restore the records or move them into Z9/Flex: store it securely. PINs, card numbers, badge IDs and employee IDs made only of digits are written with a leading ' so a spreadsheet keeps leading zeros; remove it when importing them elsewhere. If the copy cannot be saved, nothing is deleted. A copy with exactly the same records is not written twice, and the newest 20 copies are kept.

Actions

• Factory Reset -- clears the host pairing so a different host can take the station over. The station's Enterprise Security data is not touched.
• Log Niagara Data -- writes a read-only snapshot of the station's access-control records to the station log (under z9open.probe), useful when troubleshooting synchronization.

Troubleshooting

The module logs under z9open.* in the station log; synchronization messages show what was received and applied. If a downloaded object does not appear in Enterprise Security, the station log states the reason (for example, a card whose number or facility code does not fit any downloaded card format).