Skip to main content
MediaBeacon University

N3twork Remote Events Node


MediaBeacon’s R3volution product has been designed to grow from one server with multiple applications to a multi-server cluster. Additional servers on the LAN that are connected to the main instance of MediaBeacon are called Remote MediaBeacon Nodes. These are individual applications that are designed to offload processes from the primary MediaBeacon server and to increase the speed with which certain operations are performed. The Nodes are available as an option with MediaBeacon's N3twork Application Bundle and include the Importer Node, Preview Node, and Events Node. Each node can be installed and configured on designated hardware and collaborates with the main MediaBeacon services. Remote MediaBeacon Nodes are available for MediaBeacon Enterprise Pro only. As the demands grow for MediaBeacon to perform tasks faster and more efficiently, additional nodes can be added.

Additional fees may apply for any or all additional nodes added to the system. Nodes are part of the licensing agreement with MediaBeacon, Inc.

This document will describe the Events Node and outline the process for installation, configuration, and setup, with detailed step-by-step instructions. Further training is available by contacting a MediaBeacon representative or visiting the MediaBeacon resources page:



Events is used when the primary MediaBeacon server is watching remote volumes which are being accessed outside of MediaBeacon. MediaBeacon Events is then installed on the remote system and will monitor all filesystem activity on the watched folder and its subfolders. When an asset is copied, moved, deleted, or modified outside of MediaBeacon, it will notify MediaBeacon of the change and update the database.


On Mac, install Java 8, which is required to run MediaBeacon 8.0. Download it from:

To configure Events, launch the Events application as an Administrator-level user. If this is the first launch of Events it will ask to enable File System Updates, select ‘Yes’.

Event Source

Once Events has finished loading, select which filesystem type it is watching:


There are three different available filesystems, two on Macintosh, and two on Windows:

  • macOS
    • Macintosh AFP Server
    • HELIOS ImageServer
  • Windows
    • Windows SFM (Shared Services for Mac)
    • HELIOS ImageServer

Shared Folders

Select the folder that Events should watch. Click on the “+” icon and navigate to the correct folder. Events will then ask for the relative path to the folder that it is watching. If the folder that Events will be watching is the top level of the MediaBeacon share folder, this can be left blank. If the folder is a subfolder of the primary shared directory, enter its path here. For instance, to have Events watch the folder Animated that resides in the Videos folder in the MediaBeacon share folder, enter: Videos/Animated/



Next, configure the database. Events requires access to the same external database that MediaBeacon uses, and is not available when using the built-in database. Select the database that MediaBeacon is using and enter the hostname or IP address where the database resides. This will be the same information as in the MediaBeacon Admin GUI’s database section. Ensure that the host is accessible from the Events server.


Starting Events

Click Save and check Enable Remote Event Server at the top of the Events GUI. If MediaBeacon is using MySQL, Events will need to download the JDBC driver and restart. This is an automatic process that requires access to the internet.  After download and restart, click Start Events. The event server will now watch for filesystem events in the designated folder and notify MediaBeacon when files have been added or modified outside of the web interface.


Port Information

Below are the default ports used to connect.

  • Connects to the database.
  • Was this article helpful?