AMAG Symmetry Configuration

Networking

• The Proxyclick access control client reaches out to Proxyclick servers via port 443. For more information on networking, please refer to the 'Deployment Requirements' section of the Access Control Overview document.
• The access control API listens on port 443 (HTTPS) by default.
• The Proxyclick access control client needs to be able to reach the API.

Licensing

Licenses for the below items will need to be applied within AMAG:

1. Symmetry
2. Data Connect Module
3. XML Open Integration Module

Enable required functions

Proxyclick will connect to the smsXMLWebservice. This XML module needs to be installed alongside AMAG Symmetry and then enabled - a HTTPS connection is required by Proxyclick.

Windows WCF Services must also be enabled.

Install the XML Open Integration Module - this will install a WCF Service named smsXMLWebService located in: C:\\inetpub\\wwwroot\\smsXMLWebService

Update Multimax Import process timing

AMAG will add a delay when Proxyclick adds or updates users. See details in the Notes section to reduce this delay.

Enable multiple cards functionality

From the Maintenance tab select System Preferences then select the Card Settings section.

Ensure that the “Multiple cards” option is checked.

Company Setting

We are able to insert users into a specified Company (partition) within AMAG. Please specify which company we should add users to during deployment

Set up an Installer user

For the Proxyclick integration to work we need a user to be able to log into the smsXMLWebservice service. This user should be configured within AMAG with the Installer permissions.

We recommend using a long, strong password and to not communicate this with anyone over email, but simply use these account details when connecting the Proxyclick client software to AMAG.

Create a Custom Card Format - for QR-based access - M4000 Nodes only

Select the Install tab then default settings and select card formats

Set up a Wiegand card format to match your reader configuration. Further information on QR code reader setup may be found here.

Below is an example QR code format set up for a simple 37bit Wiegand configuration:

Create a Customer Code / Facility Code - for QR-based access

A facility code is required when we create cardholders. When using physical credentials the facility code is encoded to the card and specified within AMAG.

For the QR code tokens we enter, we must have an associated Customer / Facility code within AMAG.

Select the Setup tab then Facility/Customer Codes from the Configuration section.

Configure the Node for use with Proxyclick - for QR-based access

1. Configure the reader to have a 37 bit Wiegand output
2. Select the Install tab then select Node > [YOUR NODE] > Setup > Wiegand Format and select “1 France 37 bit”
3. Ensure the Node is enabled.

Configure the Reader for use with Proxyclick - for QR-based access

1. Select the Install tab then Reader. Select the reader you are configuring then choose Setup > Reader Type and select “Series 600/700/800 using Default Wiegand”
2. Select the Node the reader should be associated with
3. From this page you should also select the “Wiegand” radio button
4. Here you can associate the Facility/Customer Code configured in a previous step above with the readers used by Proxyclick visitors.

Using Physical Credentials - RFID Cards/Fobs

Our Access Card Manager allows physical credentials to be assigned to a visitor via the Proxyclick dashboard. To configure this, we will need to know the Card Format and Customer Code/Facility Code configured for your RFID readers. See Access Card Manager.