Skip to main content
MediaBeacon University

Webhead Installation: Windows


This section will guide administrators through the process of installing a MediaBeacon webhead on Windows. MediaBeacon supports Windows 2008 R2 – Windows Server 2012. 64-bit is required.


To follow these instructions, install the core MediaBeacon application and download the matching webhead .war file.


  1. If the webhead is being deployed on a separate server from MediaBeacon, be sure to install a matching version of Java, either through the MediaBeacon installer or manual download.
  2. Copy these files from a core MediaBeacon installation (e.g. C:\Program Files\MediaBeacon\MediaBeacon\lib) to the JRE’s library extensions (e.g. C:\Program Files\Java\jre1.8.0_91\lib\ext):
    • jniwrap.jar
    • slf4j-api.jar
    • winpack.jar
    • hfscharset.jar
  3. Download and install Tomcat 8.0. Files and documentation are available here:
  4. Copy these files from a core MediaBeacon installation (e.g. C:\Program Files\MediaBeacon\MediaBeacon\lib) to the Tomcat ‘bin’ folder (e.g. C:\Program Files\Apache Software Foundation\Tomcat 8.0\bin):
    • jniwrap.dll
    • jniwrap.lic
    • jniwrap64.dll
  5. Once Tomcat is installed, open the “Configure Tomcat” application. In the “Java” tab, set the “Maximum Memory Pool” to 1024 MB. For higher loads, more memory may be required. Contact MediaBeacon Support with any questions.
  6. If using MySQL, locate the MySQL connector in the MediaBeacon installation. This file will be available after MediaBeacon has connected to MySQL for the first time: C:\Program Files\MediaBeacon\MediaBeacon\lib\mysql-connector-java-5.1.34-bin.jar Copy it to the Tomcat library: C:\Program Files\Apache Software Foundation\Tomcat 8.0\lib

  7. Rename the .war file to match the URL that should be used for accessing the webhead. For example, webhead.war will be accessed at http://localhost:8080/webhead
  8. Copy the renamed .war file to: C:\Program Files\Apache Software Foundation\Tomcat 8.0\webapps Webhead-Portal_Win_4.png
  9. MediaBeacon 8.x will not accept connections from external applications unless they are explicitly whitelisted on the main server. To allow a connection from the webapp:
    1. Go to the “Enterprise” tab on the main MediaBeacon server and click “Applications.”
    2. Click “Add” and manually enter the IP address for the webapp. Alternatively, click “Discover External Applications.” This will open a temporary 2-minute window during which remote applications are allowed to connect to MediaBeacon, automatically adding them to the whitelist.
    3. Click “OK.”
  10. Launch Tomcat.
  11. Navigate to http://localhost:8080/webhead in a web browser (or whatever URL is appropriate, based on the name of the .war file). The browser will be redirected to remote_config.jsp for a first-time setup.

    There shouldn’t be any red icons in the Configuration Checker area. Enter the following information:
    1. Host: Enter the IP address of the core MediaBeacon server relative to the webhead server. If they’re both running on the same machine, localhost is fine.
    2. Port: Use 44444, unless the value for the SOA port was changed on the “Enterprise” tab of the MediaBeacon R3volution server-side GUI application.
    3. Password: The password is set via the “Change Remote Password” button on the “Enterprise” tab of the MediaBeacon R3volution server-side GUI application.
  12. After entering the Host, Port, and Password, click “OK.” A “Continue” button will display if the webhead was able to connect to the main MediaBeacon server.
  13. Click “Continue” to proceed to the MediaBeacon login screen. The webhead is now available for use.

Tomcat as a Service

When installing the webhead on a non-core server, where Tomcat is running as a service, the following must be taken into account:

  1. The tomcat service must be run as a specific user, not 'local system' or 'local service'.
  2. This user should be a 'service user', a non-privileged account that can still do everything webhead needs.
  3. Any java plugins required by the webhead need to be placed within that user's AppData\Local\MediaBeacon\scripts directory.
  • Was this article helpful?