On this page:
-cswitch. The console mode prompts you for the equivalent information that appears in the GUI installer screens, as described below.
In addition, you can run the installer using a Response file (for unattended installations). See Installing with the Silent Installer.
This mode is for demonstration and light testing only. If you are using the Events Service, it must be on a separate host.
If you do not already have an existing on-premises Controller, install it as described in Custom Install.
To install the Demo Installation, you are required to do the following:
From a command prompt, navigate to the directory to which you downloaded the EUM Server installer.
Change permissions on the downloaded installer script to make it executable, as follows:
chmod 775 euem-64bit-linux-4.5.x.x.sh
Run the script as follows:
Run the installer:
Usernames and passwords can only consist of ASCII characters. In addition, passwords cannot include the characters '^', '/', or '$'.
Note that ports shown here are the location both to which the EUM Agents send their beacons and from which the Controller fetches the processed beacon data. Click Next and click Finish.
After installing the EUM server, you must perform three additional post-installation tasks:
Configure the Events Services properties in the eum.properties file (optional)
To provision the EUM license:
For the demo installation, Events Services configuration is not required for the EUM Server to start.
To configure the Events Service properties in the
eum.propertiesfile for editing.
eum.propertiesfile, enter the following values:
appdynamics.es.eum.keyvalue in the Administration Console:
eum.properties file, restart the EUM Server.
To connect the EUM server with the AppDynamics Controller:
eum.cloud.host:– This tells you where the Controller will poll for EUM metrics
eum.beacon.host: eum-host-name:7001– This tells you where the JS agent will be configured to send out the beacons over the HTTP protocol
eum.beacon.https.host:– This tells you where JS agent will be configured to send out the beacons over the HTTPS protocol
eum.mobile.screenshot.host: eum-host-name:7001– This tells you where the Controller will look for mobile screenshots
Instead of using the installer in GUI mode, you can use the silent installer to perform an unattended installation. The silent installer takes a response file as a source for the initial configuration settings. It's useful for scripting installation or performing large scale deployments.
To use a response file for a Demo installation:
Create a file named
response.varfile on the machine on which you will run EUM installer with the following:
sys.adminRights$Boolean=false sys.languageId=en sys.installationDir=/AppDynamics/EUM euem.InstallationMode=demo euem.Host=controller euem.initialHeapXms=1024 euem.maximumHeapXmx=4096 euem.httpPort=7001 euem.httpsPort=7002 mysql.databasePort=3388 mysql.databaseRootUser=root mysql.dbHostName=localhost mysql.dataDir=/usr/local/AppDynamics/EUM/data mysql.rootUserPassword=singcontroller mysql.rootUserPasswordReEnter=singcontroller eumDatabasePassword=secret eumDatabaseReEnterPassword=secret keyStorePassword=secret keyStorePasswordReEnter=secret eventsService.isEnabled$Boolean=true eventsService.serverScheme=http eventsService.host=eventsservice_host eventsService.port=9080 eventsService.APIKey=1a234567-1234-1234-4567-ab123456
Modify values of the installation parameters based on your own environment and requirements. Particularly ensure that the directory paths and passwords match your environment.
Run the installer with the following command:
./euem-64bit-linux-4.5.x.x.sh -q -varfile response.varfile
On Windows, use:
euem-64bit-windows-4.5.x.x.exe -q -varfile response.varfile