- Manufacturer: Software House
- Product: C-Cure 9000
- Type: Access Control System
- Site Syncing
Components and Communication
|Component||Location||Outgoing communication||Incoming communication|
|C-Cure Router Service||C-Cure Server||443 TCP to Receiver Service||443 TCP from Device Plugin|
|C-Cure Receiver Service||Sureview Device Server||N/A||443 TCP from Router Service|
|C-Cure Device Plugin||Sureview Device Server||443 TCP to Router Service||N/A|
|CCure 9000 Server||Sureview Server||TCP 9001||Communication for receiving alarms|
|Sureview Server||CCure 9000 Server||TCP 9000||Communication for Get Config/Syncing/Relay control|
CCure 9000 Licence
Confirm that the CCure 9000 licence is valid by loading the CCure 9000 "License Manager" application. A valid licence should have an expiry date set in the future, and the section next to "CrossFire" should read Current version licensed.
CCure 9000 Setup
CCure 9000 typical setups are based on hierarchical structures consisting of Clusters (where there can be multiple, underneath the Company Name) and Collections (where there can be multiple, underneath Clusters).
Collections are digital representations of alarm panels, and typically contain the doors, outputs, readers and alarms that can be used with Sureview. Using the CCure 9000 "Administration Workstation" a user is able to add devices that will be used for monitoring.
Typically the interface would look like this:
1. Setting up SureView Router service on the C-Cure 9000 Server
The installer for the CCure 9000 Router service requires installation as an administrator.
- Run the SVCCure9000Router-1.0.0.*.exe installer on the C-Cure 9000 server. It may be necessary to uninstall an old version by going to 'Program and Feature' in the server's 'Control Panel' and choosing 'Uninstall'.
Choose the root path of the C-Cure 9000 server (defaults to the Tyco install path)
- Navigate to the ServerComponents folder <Tyco install path>\CrossFire\ServerComponents (using above example would be C:\Program Files (x86)\Tyco\CrossFire\ServerComponents).
- Find the file SVCCure9000Router.exe.config and edit it:
- In the config file change the ImmixHost and ImmixPort values to point to the Sureview Server Host value and Port Number. (The default port is 9001 but can be configured if it is required). The service will need to be restarted when changing any config values.
- Navigate to the ServerComponents folder <Tyco install path>\CrossFire\ServerComponents (using above example would be C:\Program Files (x86)\Tyco\CrossFire\ServerComponents) and run the executable file InjectionScriptRunner.exe.
2. Installing the C-Cure Device on to the Surview ServerNOTE: Install the "CCure 9000" device integration before installing the "CCure 9000 Receiver Service"
- Run the Sureview Package Installer.
- Select the device CCure 9000 integration.
- Install as normal (no additional prompts).
3. Installing the C-Cure Alarm Receiver Service on to the Sureview Server
NOTE: Install the "CCure 9000" device package before installing the "CCure 9000 Receiver Service" package.
- Run the Sureview Package Installer.
- Make sure the "CCure 9000" device integration is already installed.
- Select the "CCure 9000 Receiver Service" package and continue to click Next until the service is installed.
4. Setting up C-Cure Root Devices in Sureview
For every C-Cure Server that will work with Sureview you will need to configure a "Root" device within Sureview. This "Root" device is used to catch all alarms that can't be decoded for a particular C-Cure server.
- Add a new device in Sureview with a meaningful name such as "C-Cure Swansea Root Server"
- Set up the device with the C-Cure Server's Host value and Port Number (default 9000). Leave the Username, Password and Controller Name/Cluster Name blank.
NOTE: It is recommended to run Get Config on a Root device.
- It is recommended that every site that contains a C-Cure 9000 device should also contain a C-Cure 9000 Root device.
5. Setting up C-Cure Servers in Sureview
There are two methods of configuring C-Cure servers in Sureview. Individually using "Get Configuration" or automatically using "Syncing".Synchronisation
For Site Syncing please refer to the Site Syncing Support Page
To set up Sureview for synchronising with CCure 9000 is it important to understand how they are linked. Take the following setup in CCure 9000:
Firstly set up a 'Sync System' with the connection details of the SVCcure9000Router server. Click 'Setup', 'Edit Settings' then click on the site and choose the 'Sync System' tab:
Next click 'Set Up', then 'Edit Sites' then 'Next' to get to the 'Site Syncing' tab. It is possible to either sync an entire Cluster by setting the 'Identifier' as follows:
After the synchronisation has completed, you'll get all the CCure 9000 Controllers (Office iStar) that exist underneath the Cluster, as well as the Cluster itself (Test Cluster).
Or one can sync on an individual controller by setting the 'Identifier' as shown below:
For individual CCure 9000 devices, use Get Configuration in the following way:
- Navigate to Site Setup of the Site you want to add a C-Cure device to.
- Click "Add a new device" and select "CCure 9000" from the drop down list.
- Enter the Host value and Port Number for the C-Cure Server (leaving the Username and Password blank).
- Enter one of the following:
- Controller Name = <Controller Name>
- Cluster Name = <Cluster Name>
- <Controller Name>
- Press the "Get Config" button
- The doors, outputs and alarms for the relevant C-Cure Controller or C-Cure Cluster will be populated in the configuration section. Select the items you wish to add, and click the DONE button when you are finished.
"Get Configuration" supports getting the information for configured Doors, Outputs and Alarms on the C-Cure 9000 Server only.
|Host||IP address or host name of the C-Cure 9000 server (where the C-Cure 9000 system runs)|
|Port||The port used to connect to the SureView Router service that runs on the C-Cure 9000 server. The default value is 9000, but this can be configured in the service's config file.|
|Controller Name / Cluster Name||
Can be one of the following:
The C-Cure 9000 system does not come packaged with any predetermined alarms, and will instead attempt to decode and add any alarms that get sent to it dynamically, allowing greater use of the Global Alarm Configuration.
Individual alarms (and actions) can be manually added if needed (or can be configured using the heuristic alarm configuration).
|Input1||The Object ID of the source of the alarm (door, alarm input etc)|
|Input2||The Object ID of the cause of the alarm if available (person opening door etc)|
The event that was triggered. (The Event Type List is automatically downloaded from the C-Cure Server)
|Date Time On Server||The time that the event was triggered (according to the C-Cure 9000 server software)|
|Extra Text||The text of the alarm will be populated with the name of the source object and the name of the cause object when available.|
Input 2 Object Types
|Input2 Value||Object Type||Level|
|8||Event||Root (unless downladed to a Controller)|
|19||Time Spec||Root (unless downloaded to a controller)|
- The receiver service sends heartbeat commands to the router service.
- If the receiver service stops being able to heartbeat the router, an alarm is triggered.
- Heartbeat failure alarms will continue to be triggered whilst no heartbeats are received.
- A final alarm confirming heartbeats have begun will be raised when communication has been re-established.
Get Configuration (or syncing) Fails
- Confirm that port 9000 (default) is open outgoing from all Sureview Servers that are running the SureView Proxy Service to all C-Cure Servers (incoming)
- Confirm that the C-Cure Device package "CCure 9000" is installed on all Sureview Servers running Device Proxy.
- Confirm that you are using the correct "Controller Name / Cluster Name" value in the device setup.