On this page:
Search the On-Premises EUM Server topics:
The default End User Monitoring deployment assumes that EUM agents (Mobile and Browser) send their data to the EUM Cloud, a cloud-based processor. To deploy EUM completely on-premises, you need to install the EUM Server, the on-premises version of the EUM Cloud, as described here.
The EUM Server receives data from EUM agents, processes and stores that data, and makes it available to the AppDynamics Controller. Certain EUM features—specifically, Browser Request Analytics and Mobile Request Analytics, features of Application Analytics that extend the functionality of Browser and Mobile Analyze—require access to the AppDynamics Events Service.
To set up a complete on-premises EUM Server deployment, therefore, you need to:
- Install the on-premises Controller or prepare an in-service Controller to work with the EUM Server
- Install the on-premises Events Service Deployment and configure it to work with your on-premises Controller
- Install the on-premises EUM Server and configure it to work with your Events Service and Controller.
Deployment Modes for the EUM Server
For demonstration and light testing purposes, the EUM Server can be deployed to the same host as the Controller. For production, however, the EUM Server must be deployed to a separate host.
To install the components on a single host, you run the EUM installer only once on the target machine. For a dual (or split) host installation, you run the EUM installer twice: first on the Controller host, to configure the Controller to work with the EUM Server, and then on the EUM Server host, to install and configure it.
In single host mode, the EUM Server listens for connections on port 7001 or 7002. The secure port, 7002, uses a built-in, self-signed certificate.
In a production environment, the EUM Server is likely to operate behind a reverse proxy. A reverse proxy relieves the performance burden of SSL termination from the EUM Server. It also helps ease certificate management and security administration in general. Further, as the connection point for agent beacons, the Server needs to have the security layer of a proxy between itself and the external Internet.
Using a reverse proxy is the recommended method of setting up HTTPS connections for an on-premises EUM Server. If this is not possible in your installation, however, it is possible to set HTTPS support manually. See information on setting up a custom keystore in Secure the EUM Server.
Embedded Geo Server
The EUM Server includes an embedded Geo Server that provides the geo information. The Geo Server either obtains geo information from your custom Geo Server or by resolving incoming IPv4 address (IPv6 addresses are not supported) with MaxMind open source geo data, Neustar data, or custom geo data.
Add New Geo Data
To add new geo data, you can either add a new MaxMind data file, switch to use Neustar data, or create the custom geo data file geo-ip-mappings.xml and place it in the directory eum-processor/bin/. The EUM Server automatically detects and loads new geo data files.
Update the Geo Server
The Geo Server is updated when you update the EUM Server.
Host Your Own Geo Server
Check an In-Service Controller for the EUM Server
The EUM Server installer makes these changes to the Controller:
- Creates a new database schema in the MySQL database shared with the Controller
- Registers the EUM Server instance with the Controller
- Provisions the EUM-enabled license in the Controller
Before you run the installer on an in-service Controller do the following:
- Check your Controller version. The 4.3 EUM Server works with the AppDynamics Controller version 4.3 or earlier. A Controller works with an EUM Server that is the same or a later version. That is, a version 4.3 Controller works only with a 4.3 or later version of the EUM Server. See Upgrade the EUM Server on information about upgrading the platform.
- Back up the current version of your Controller.
- Choose a time window that has minimum impact on service availability. The Controller must be restarted for the configuration changes made by the EUM Server installer to take effect.
Install the On-Premises Events Service
The Analyze function in Browser RUM and the Crash Report and Analyze components in Mobile RUM rely on the AppDynamics Events Service, the Platform's unstructured document store. The Events Service that is configured by default for EUM is a cloud-based service.
If you are running on-premises and wish to keep all your processing on-prem, after installing and configuring the Controller, you must install an on-premises version of the Events Service as described in this section. Note that relying on the Events Service purely for use with the EUM UI does not require a separate Application Analytics license. Other uses may require a separate license.
There are multiple modes of deploying the Events Service. For detailed information on installing and configuring the Events Service, see Events Service Deployment.
Run the EUM Server Installer
Before starting, get the installer version appropriate for your target system. You can get the installer from the AppDynamics download site.
Run the EUM installer under the same user account on the target machine as the one used to install the Controller, or using an account that has read, write, and execute permissions to the Controller home directory. Installing with incompatible permission levels—for example, attempting to install the EUM Server as a regular user while the Controller was installed by root user—may result in installation or operation errors.
The EUM Server is automatically installed as a Windows service. All upgrades are automatically converted to a Window service.
The installer can be run in three modes:
- Silent mode with varfile
See the following page for details on installing as appropriate for your deployment mode:
- For a demo single host mode, see Install a Single Host (Demo) EUM Server.
For a production dual host mode, see Install a Split Host (Production) EUM Server.
Update the Agents
Start and Stop the EUM Server
The EUM Server is installed as a Windows service automatically. You can manage how you want this service to run using the Local Services dialog.
On Linux, start the EUM server from the eum-processor directory in the EUM home as follows:
For a demonstration environment, run the command as sudo.
On Windows, if you ever need to start the EUM Server manually, you can do so by running:
You can check if the server is running and accessible by going to
http://<hostname>:7001/eumaggregator/ping with your browser. Your browser should display
To stop the EUM Server, pass the stop command to the
eum script. For example, on Linux, from the eum-processor directory, run: