This document is intended to instruct users on how to synchronize an XPressEntry system with a CCURE9000 Access Control System (CCURE).
2.Setting Up CCURE to Synchronize with XPressEntry
It is assumed CCURE is installed on server and it is available to the XPressEntry system.
2.1.Order of Operations
- Set up CCURE License Options
- Enable Synchronization from XPressEntry
- Set up XPressEntry Data
3.Setup CCURE Data and Settings
For every physical XPressEntry handheld reader, you should have two logical readers in the CCURE System. They should be distinguished with the words “Entry/Exit” or “IN/OUT” as you see fit.
XPressEntry sends activities to the CCURE system through placeholder doors in CCURE. In most situations, you should add two readers (an exit and an entry) for each door. Typically there is one XPressEntry handheld for each door you are tracking. We will go into the way this works when we review XPressEntry.
3.3.Adding XPressEntry Handhelds
After creating LAN chains and nodes, we can add the handheld readers to the system. Under the install tab, select Reader. For each physical Xpress Entry handheld that you have, create two logical handhelds in the Symmetry system; one for entry and one for exit. Under the setup tab, select the company the reader belongs to. In the “Connected To” grouping, select the node you created above as well as the type of controller you had selected for the node. Each reader created in the same node will have a different port number. Select OK when finished.
4.XML Open Integration Module
4.1.Applying the License Key
When you purchased the XPressEntry integration from Software House, a license option was sent to you to enable the XPressEntry integration on the CCURE server. Make sure this is added using the “InsertLicenseOption.exe” command as specified.
XPressEntry uses a module called “Data Manager” to synchronize Cardholders/Cards with CCURE.
From the main page of XPressEntry, go to XPressEntry / Settings (CTRL+S)
From the Settings page, select the General Tab
When setting up a Data Manager, it is important to set “Log Level” to “SQL” (top left Figure 7). This will allow you to see logged entries when you sync. Select “Save Settings” after making this change. After setup is complete and the data synchronization is correct, it is suggested that you set “Log Level” to “Critical”.
5.2.Reader Profile Tab
The Reader Profile Tab is where you configure the handhelds.
The only important change to make on this tab is to make sure “Door Readers” is the only mode that is checked under “Validation Methods”. Select “Save” at the top right when finished.
If you would like to assign permissions using areas in your CCURE integration, please contact Telaeris.
5.3.Data Manager Tab
From the Settings page select the Data Manager Tab
- Type- This is the integration type. Select CCURE 9000.
- Setup Data Manager- Sends you to the setup form for the CCURE data manager.
- Save and Apply Settings- Saves all settings from the setup form, update frequencies, and activity Synchronization options.
- Update Frequency options- Sets and clears the intervals in which the data manager updates XPressEntry.
- Immediate sync functions- Runs an immediate update.
- Activity Synchronization options- Used to send XPressEntry handheld activities to CCURE and track CCURE occupancies in XPressEntry.
Set the Update Frequency to as often as you want the system to update.
There are three different types of Sync that you can set intervals for.
- Full Sync Update- This sync will grab all relevant records from CCURE and update them in XPressEntry. If there are a large number of users in CCURE, this sync option can take some time.
- Partial Sync Update- This sync will grab records from all tables which are NOT user data. This will not grab user clearances, but will grab clearances, doors, readers and other supporting tables. This is useful when you are making changes to the setup of XPressEntry in CCURE, but don’t want to synchronize all users.
- Activity Sync Update- Use this sync to send XPressEntry Events to CCURE. These events will show up as CCURE events. The “Activity Synchronizing” section contains two options.
- Sync Data Manager Activities with XPressEntry – Not used
- Sync XPressEntry Activities to Data Manager – If you want the activities from the XPressEntry Handhelds to show up in CCURE, you should check this option.
All of these options can be changed at any time. Changing any option will take effect only once you’ve pressed “Save and Apply Settings”.
5.4.AMAG Setup Page
Press the “Setup Data Manager” button to get the AMAG specific setup screen.
- Symmetry Server information
- Symmetry Database connection string
The first thing you want to look for is the Web Service instance. This file will be an .asmx file on the web server. (Ex. http://www.service.com/smsXMLWebService/smsXMLWebService.asmx)
The username and password fields represent the username and password necessary to log into Symmetry.
A database connection string is also required to fully synchronize the correct Symmetry information with XPressEntry. The connection string type is a SQL Server connection string.
If you do not wish for the password in the database connection string to be visible, you can replace the password with @Password. In the Connection String Password field, type your password. The password will replace @Password in the connection string. (ex. Password=@Password will be converted to Password=”Connection String Password Field”)
5.5.AMAG Activity Setup
The activity settings change the way activities from the handhelds are viewed in Symmetry. All activities in XPressEntry are viewed as alarms in Symmetry. On this form, you can change the priority of an access granted or access denied alarm, as well as the color of the text of the alarm itself (These settings are reflected in Symmetry only).
There is also a Test tab used for creating test queries against the Symmetry database. This tab uses the connection string on the Connection tab.
Press Save Settings and exit the setup form. Select “Full Sync Now” to test your setting changes. The log view at the bottom will display the result of the sync, according to the log level set in the “General” tab.
6.Setup XPressEntry Data
Once the AMAG System is set up and synchronizing, you will see all of this data represented in XPressEntry under the Add/Edit Info tab. Data which is imported from AMAG cannot be changed and is greyed out.
Here is a sample of a properly synchronized user:
Users in XPressEntry have the same access to the reader groups and access groups as they do in Symmetry. XPressEntry does not support Cardholders directly associated to a single reader.
Entry/Exit permissions in XPressEntry are set by doors. Doors contain two readers, an exit and an entry reader. Door access is determined by the User’s access to the door’s reader. For entry, permission is based on the user’s access to the door’s external entry reader. For exit, permission is based on the user’s access to the door’s external exit reader.
Doors should be set by the user for each Handheld Reader in XPressEntry.
The XPressEntry Integration with Amag does not require additional start and end zones. For most situations, each door’s zones should be set to the default: outside and building.
- Zones- For each door, set the start zone to Outside and the end zone to Building. This helps to determine directionality.
- External Readers- Attach the logical entry and exit readers that you created in Symmetry to a door.
XPressEntry requires that you manually set up the doors in the system. There should be a door in XPressEntry for each physical station that an employee will have a handheld. To create a door, select “Add New” at the bottom of the form. Enter a name that clearly describes what this door represents. Select “Outside” for Start Zone and “Building” for End Zone. “External Entry Reader” is one of the entry readers you created in Symmetry. “External Exit Reader” is one of the Exit readers you created in Symmetry.
In XPressEntry’s Amag integration, it is not necessary to associate any reader in the system with a handheld. This association can be done on the handheld when it comes time to scan.
A handheld unit can logically represent any reader in the building. When the handheld is issued to an employee at a specific door, the employee must first set the door on the handheld. The XPressEntry Reader that the handheld represents is based on whether the handheld is in entry mode or exit mode.
For example, let us say that you have handheld A stationed at door A. Door A has two readers associated with it: Reader A-Entry and Reader A-Exit. The employee holding the handheld sets the handheld’s door to Reader A. When the employee sees a cardholder walking towards the building, he sets the handheld to Entry mode and scans the cardholder’s badge. The handheld in entry mode identifies itself as reader A-Entry and sends an activity to the server.
Later, there is heavy volume exiting Door B. Door B has two readers associated with it: Reader B-Entry and Reader B-Exit. The employee from door A is called to help and brings handheld A. He sets the door on his handheld to Door B and the mode to Exit. When he begins scanning people walking out of the door, the handheld identifies itself as Reader B-Exit and sends each scan as an activity to the server.
XPressEntry will synchronize activities to Symmetry if that option has been set by Data Manager.
Entry/Exit activities will be sent to the Alarm Manager in Symmetry. The alarm will contain the following information.
- What the event was (ex. Scanned Badge 12345: Access Denied)
- Where the badge was scanned (ex. Back Door Entry Reader)
- Who was scanned
- Time the scan occurred
- Priority of the scan (Set by XPE Amag Data Setup)