RCO M5 Configuration for Accessy

This step-by-step guide will go through all the necessary configuration required to integrate RCO M5 with Accessy.

Configuration Steps

1. Hosting environment

2. System Requirements and Features

3. Import licences

4. Create operator for Accessy

5. Configure:

   • Devices

   • Access group

   • System settings

   • Accessy User

   • M5 User API

6. Getting operational

1. Hosting Environment

Accessy integrates with RCO M5 Server through the M5 User API.

M5 User API is running as a web application in Microsoft Internet Information Server (IIS). It is required to configure the IIS to only accept connections over TLS port 443 (HTTPS). This requires installation of a certificate from a trusted CA such as Thawte, Verisign etc. Self-signed certificates will not be accepted by Accessy integration.

It is highly recommended that the M5 Server and M5 User API is running on separate networks as the M5 User API will be exposed to the internet. Communication from the M5 User API to the M5 Server is done over port 8090, configure the firewall accordingly.

2. System Requirements and Features

System Requirements

The Accessy-integration requires the following system requirements from RCO:

• M5 Server: 5.48 or above

• M5 User API: 1.3.2 or above

Always use a full MSSQL-server for the M5 Server. While SQLite will work, it may cause unwanted issues.

Do not use any proxy service in front of M5 User API. The security token generated at login verifies the origin IP address at requests. The origin IP address will be different when networking through a proxy!

Monitoring of RaServiceHost.exe is highly recommended as history shows that this process gets non responsive at times which means that Accessy app will not be able to request pulse open to any door in the system.

Features

• Pulse Open (“Button1”)

• Force Open (“Button2”)

3. Import Licenses

Run the stand alone program called "R-card M5 Registrering" to import the licenses needed. These are:

• The M5 User API need a license.

• Doors to be available in Accessy needs a license each. I.e. if 14 doors are to be available, the license needs to be valid for at least 14 doors.

Contact Accessy if you need to purchase licenses.

Once licenses are registered the M5 Server needs to be restarted. Also make sure to restart the service named "RA Service Host".

4. Create Operator for Accessy

• Set a name and password (this should NOT be shared with Accessy) - do not use special characters (&, ~, \ etc) in the "Operatör" password.

• In the configuration for the "Operatör", check "R-Card M5 API-operatör"

• Add a new "Säkerhetsgrupp":

• Make sure that the "Säkerhetsgrupp" has the required rights and then click "Medlemmar":

• In "Medlemmar", make sure that all devices and card readers to be controlled are present in the list to the right:

• Add the new "Säkerhetsgrupp" to the "Operatör":

5.1 Configure Devices

• Each device to be available in Accessy needs to be configured with "Styrning från RCO Access app":
  

  

  Don't forget to hit "Save" in the top-left corner (floppy disc icon).

5.2 Configure Access Group

• Create a "Behörighetsgrupp" and make sure to check the option "Styrning från RCO Access App":

  

• Add the devices/doors to be controlled from Accessy:

  

  
  

• Create a schedule - it is HIGHLY recommended that this is set to "Alla dagar" unless there are real valid reasons:

  

  
  

NOTE! If this is set to anything other than "Alla dagar", please make sure to inform Accessy administrators to mirror the schedule in Accessy when assigning access to members of their Accessy subscription.

5.3 Configure System Settings

• Go to "Inställningar" - "Inställningar" and then "Konfigurera användarfält". Check "Lösenord för webb" and "E-post":

  

  Set "Fält för inloggning i RCO Access (ej lägenhet)" to "E-post":
  

  

  
  
  5.4 Configure Accessy User

• Create a new user.

• Enter "Lösen för webb" - this will be the Accessy user password

• Enter "E-post" (does not have to be a real email) - this will be the Accessy user name:
  

  

• Add a new card/tag to the user

• Set the "ID-kod" to any number of your choice (minimum of 9 digits)

• Set any "PIN-kod" of your choice

• Add the "Behörighetsgrupp" that you created in "Configure access group"

  

  
  
  
  

5.5 Configure M5 User API

• Configure the M5 User API configuration file. Default location: C:\inetpub\wwwroot\M5UserAPI\rco\rcoservers.config

• Server-ID: set as needed (often in numerical order). You may configure the M5 User API to communicate to several M5 Servers, in that case the server id need to be unique per server.

• URL: location of the M5 Server

• Identity: name of the server*

• Username: name of the "Operatör"

• Password: password for the "Operatör"

When this configuration is done, restart the IIS server.

* The system name can be found in the top bar of the RCO window:

6. Submit Integration Data

To set up the integration in Accessy, you must choose a “home subscription” for it. Many customers will only have one subscription (for instance Company AB@Company AB), but if they have multiple subscriptions, please check with the customer or Accessy which subscription the integration should be connected to. This is important as it can not easily be changed afterwards.

1. Login to the partner portal at https://partner.accessy.se and select "submit integration"

2. Type the full name of the subscription.

3. Choose RCO M5.

4. Input the details required along with contact details.

5. Submit the data. Accessy will get back in touch once the integration is up and running.