Versions Compared

Version Old Version 1 New Version Current
Changes made by

Anand Rajaraman

Anand Rajaraman

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In addition to the default ports the 3VR uses for communication*, the following ports will also have to be open to to use the RBH plug-in:

...

Port

Purpose

445, 139

For Windows file sharing

143

For SQL connection

To view the current list of required ports, visit www.3VR.com and click Services & Support > FAQ. Open the FAQ titled “What ports must be open to connect to a 3VR VIP Appliance that’s behind a firewall?”

...

  1. Launch 3VR System Manager.

  2. In the Configure panel, click the plus sign beside the appliance name.

  3. Right-click the Plug-ins folder and select Add Plug-in.

  4. In the resulting Confirm dialog box, click Install to proceed.

  5. Navigate to the folder containing the plug-in file (Plugins.RbhTCPTransaction-Release-1.0.0.XXXXX-7.0) and click to highlight the file.

  6. Click OK. The plug-in will now begin installing.

  7. When the plug-in is installed, it will appear below Plug-ins in System Manager.

Configuring Global Plug-In Settings

  1. Select the RBH Transaction Application (TCP) plug-in. Plug-in settings will appear in the right-hand panel of SystemManager.

  2. Click Edit Settings.

    Image Added

  3. Configure the settings in the Edit Global Settings dialog as follows:

    1. Image Path: this is the network location of the RBH Cardholder image files to be displayed during access events. The value should be of the form “\[IP Address or Hostname]\directory\”, for example \ImageHost-Server\ImageFolder\ or \192.168.0.1\Imagefolder

    2. Network Login: this is a windows authentication login used to gain access to the network drive specified in the Image Path setting (a).

    3. Network Password: This is the windows authentication password for the user used in the Network Login field (b).

    4. Database Name: This is the name of the Microsoft SQL Server database that hosts the RBH database. The default value is “AxiomData”.

    5. Database IP Address: The IP address of the RBH Microsoft SQL Server Database, e.g. “192.168.0.2”.

    6. Database Login: an authorized user name for the RBH Microsoft SQL Server Database specified in Database Name (d).

    7. Database Password: The password for the user name specified in Database Login (f).

    8. Message AP ID: This is the Message ID (in the database at Messages.MessageID) corresponding to the message being sent to the 3VR VIP appliance for Accesspoint type devices.

    9. Message IP ID: This is the Message ID (in the database at Messages.MessageID) corresponding to the message being sent to the 3VR VIP appliance for Input type devices.

    10. Message OP ID: This is the Message ID (in the database at Messages.MessageID) corresponding to the message being sent to the 3VR VIP appliance for Output type devices.

    11. Message Port ID: This is the Message Port ID (in the database at MessagePorts.MPID) corresponding to the message port being used to send messages to the 3VR VIP appliance.

    12. Schedule ID: This is the Schedule ID (in the database at TimeGroups.TGID) corresponding to the schedule being used to send message to the 3VR VIP appliance.

      Image Added

  4. Click OK to save the global plug-in settings.

Binding Cameras to Plug-In

  1. Click the Bound Cameras field, then click the ... button.

  2. In the Bind Plug-in to Cameras dialog box, click the check box [√]beside each camera that should be associated with events from the RBH system.

  3. Click OK to save your changes and return to the Configure panel.

A pop-up will be displayed notifying you that the 3VR system software must be restarted after making changes. Click OK to close the pop-up message and acknowledge the warning. You will restart software as the last configuration step.

Entering Device IDs

  1. After binding cameras to the plug-in (in previous topic), links will appear under Bound Cameras for each camera.

  2. Click a link (for example Edit “1. Front Door”) to edit the settings for that camera.

    Image Added

  3. Type the Device ID of the RBH device that should be associated with this camera. The device ID takes the format of [prefix][device number], where the prefix signifies the type of device:

Type

Prefix

Accesspoint

ap

Input

ip

Output

op

For example, “ap1” corresponds to Accesspoint 1.

...

  • To associate multiple RBH devices with a single camera, type the IDs of all of the devices, separated by a comma with no spaces.

    Image Added

  1. Click OK to save your changes and return to the Configure panel.

  2. Repeat steps 2-4 for any remaining cameras bound to the plug-in in step 4.

Restarting System Software

The 3VR system software must be restarted after initially installing the plug-in or making any changes to its configuration.

  1. In the Configure panel, right-click the appliance name and select Restart 3VR Software.

  2. In the pop-up box that appears, click Restart to proceed. Wait 1-2 minutes for the software to restart.

Verifying Successful Configuration

Use the following steps to verify that the RBH Application plug-in has been correctly configured:

  1. Generate a test event on the RBH device. For example, if it is a door panel, have someone walk through the door.

  2. In 3VR OpCenter, click the Monitor tab to go to the Monitor panel.

  3. Click camera numbers to select the cameras bound to the RBH Application during configuration.

  4. Click the arrow below the camera selector to open the event type drop-down menu.

  5. Select [√]RBH.

    Image Added

  6. Click OK.

  7. If the plug-in has been correctly configured, RBH events will appear in the Monitor panel for each RBH device.

    Image Added

    Verify that RBH events are being generated correctly on all cameras bound to the plug-in during configuration.