Page tree
Skip to end of metadata
Go to start of metadata

Please replace $java with the correct Java Runtime Environment installation folder name, such as C:\Program Files\jdk1.8.0_xxx.

Please replace $activemq with the correct ActiveMQ installation folder name, such as C:\Program Files\apache-activemq-5.x.x.

See Software packages and download locations for the download locations of the Oracle JRE and Apache ActiveMQ.

Installing the Java Runtime Environment

Apache ActiveMQ requires a Java Runtime Environment. In this step, the Oracle Java Runtime Environment will be installed. We currently recommend using Oracle Java 8.

Installing the Java Runtime Environment

  • Login as local administrator on the server.
  • Download the Oracle Java Runtime Environment Server JRE.
  • Unzip the JRE to a folder on the server, e.g. to C:\Program Files\

Installing Apache ActiveMQ

In this step, Apache ActiveMQ will be installed.

Installing the Apache ActiveMQ broker

  • Login as local administrator on the server.
  • Download the Apache ActiveMQ ZIP file.
  • Unzip ActiveMQ to a folder on the server, e.g. to C:\Program Files\

Configuring the JRE

  • Open the wrapper configuration file in $activemq\bin\win64\wrapper.conf.
  • Configure the path to the JRE by amending the wrapper.java.command. Make sure to replace the $java variable!
wrapper.java.command=$java\jre\bin\java

Setting up ActiveMQ as a Windows Service 

  • Run the batch file $activemq\bin\win64\InstallService.bat. This will install the ActiveMQ service. By default, the service is not started.
  • Open Services (Start -> Run -> services.msc).
  • Open the properties of the ActiveMQ service.
  • Verify that "Startup type" is set to Automatic.
  • Start the Service.
  • Verify that ActiveMQ is running by visiting http://localhost:8161/admin/ and logging in using account  'admin' and password 'admin'.

Configuring the Windows Firewall

The ActiveMQ configuration used by MyTimetable uses two TCP ports:

TCP portDescription
61616ActiveMQ broker
8161ActiveMQ Web Console

By default, we will only allow access to the Web Console on localhost. TCP port 61616 needs to be accessible from the MyTimetable front-end server(s). 

  • Login as local administrator on the server.
  • Open "Windows Firewall with Advanced Security".
  • Create a new "Inbound Rule" and pick "Custom":

  • Allow all programs:

  • Allow TCP port 61616:

  • Add the remote IP address(es) of the MyTimetable front-end(s):

  • Select "Allow the connection":

  • Give the firewall rule a name and description:

  • Click Finish.

 

 

  • No labels