Johnson Controls - CCure SaaS 

Information

• Manufacturer: Software House
• Product: C-Cure 9000
• Supported Versions: 2.6, 2.7, 2.8, 2.9
• Type: Access Control System

Native Integration: Supported Features

• Relays
  • Pulse
  • On/Off
• Alarms
• Configuration - Via controller, Cluster or server
  • GetConfig
  • Site Syncing

Native Integration: Requirements

Components:

The following components need to be installed on the specified server for this integration:

Cloudlink Server: SV CCure Device

CCure Server: SureView CCure Http Router

[Must be installed in the CCure ServerComponents folder]

Network Requirements:

Native Integration: Device Setup

After installing the CCure http Router in your CCure server, the config file should be update for the following values - Please note that after saving your updates to the config files, the service needs to be restarted for the new configuration to be applied:

Router Config File options

• Port

  • Connection port for the router

• Https

  • True/False if the connection to router is https - Must be true on 443

• EventBatchSize

  • How many alarms to return per call

• CCureServerIsOnServicePack3

  • If the CCure being connected to is using ServicePack 3

• MessageTypesToRequest

  • Defines a list (comma separated string) of all of the object types to receive change states on, only messages for objects in this list will receive alarms. If left blank, all types are listened for. Need to be full CCure names such as: SoftwareHouse.CrossFire.Common.Objects.XFEvent, SoftwareHouse.NextGen.Common.SecurityObjects.iStarDoor

• EventUseDotNameForType

  • Changes how software events are raised, rather than ‘iStarDoor - Door Forced’ the state (Door Forced) will be replaced with whatever the XFEvent - name has set at the end. I.e. Lobby Door.DFO will be raised as ‘iStarDoor - DFO’

• AcknowledgeAlarms

  • If the alarms should receive an acknowledgement call when the event record is acknowledged in site monitor

• SetRestoreOnInactive

  • If there should be a restore alarm raised when an event is acknowledged in CCure

• ManualActionPriority

  • Defines the priority to use when triggering a manual action against the CCure (Default 201)

Please note:

Before you add the device in SureView to connect to CCure system, make sure you have the following:

• A fully licensed CCure server with the "CCure Router" installed
• A configured SureView Device 'CloudLink' Server with the "CCure" integration installed
• All required ports configured (see Components and Communication)
• A User configured on CCure with permissions for the alarms you want to receive in SureView
  • Acknowledge Alarms
  • Edit Alarms
    Override - Open Door
  • View Events
  • View Events and Alarms
  • View Site

To start adding your CCure devices, please go to the Device Setup page in your SureView application:

Device Setup

In order to set up a new device for CCure, after installing the components above and making sure that the ports are open for communication, in the Device page, add a new sync with a type of CCure9000 (On-Prem)

After saving these changes to the new sync system you created, go on the Syncs tab on the left and click on ADD AREA SYNC.

You will get this window to add information on the individual area syncs:

Title: Your title of choice for this sync.

Area: The area that you want the alarms, doors, etc. from this sync to be associated with in your system.

Identifier: You can bring in all devices from a single controller or cluster in your CCure application using this filter (please note the capital C and N in both filters) :

• ClusterName=XXXX

• ControllerName=XXXX

SureView will now automatically sync any Alarms/Doors into the appropriate Area(s) from the specified cluster/controller - this may take a few minutes to complete depending on the quantity of synced items. Once synced, CCure will be ready to use and will start receiving SureView alarms. - the Last sync stat on the previous page will show if the sync has been processed or not. After a successful sync, these numbers (on the left side of the sync setting page) should change reflecting the new number of each item after the sync (example in second image below).

If the sync fails, or does not return any devices, please enable logging on your Cloudlink server using instructions here to see further details on the reason of the failure. 

If the alarms and devices are added successfully, now your SureView system is ready to receive alarms from CCure and you will see them added to your queue.

Please contact your SureView account manager if you have any questions on these steps.

Native Integration: Troubleshooting

If the sync is failing with the following error:

System.Net.Http.HttpRequestException: An error occurred while sending the request.

Check the following:

SSL Certification:

Invalid SSL certificates on the CCure server can stop the sync from making the connection. Please ensure that there is a valid SSL certificate on the server.

Https Respond on Localhost:

Ensure that the CCure server can respond to HTTPS on localhost (if https is enabled) in; to test this, in a browser, type: https://localhost and hit enter, this should give an IIS welcome page even if nothing else.