AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.


    Skip to end of metadata
    Go to start of metadata

    You are viewing an old version of this page. View the current version.

    Compare with Current View Page History

    « Previous Version 16 Next »

    On this page:

    Your Rating:
    Results:
    1 Star2 Star3 Star4 Star5 Star
    0 rates
    You can run the installer in one of three modes. The GUI and silent installation methods are described below. To start the installer in interactive console mode, start the installer with the -c switch. 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.

    About the Demo Installation

    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

    Installation Requirements

    To install the Demo Installation, you are required to do the following:

    • Install and run a Controller instance on the same host machine before starting the EUM Server installation.
    • Install the EUM Server with the same user account used to install the Controller, or use an account that has read, write, and execute permissions to the Controller home directory.

    Installing with the GUI Installer

    1. Start the installer: 
      • On Linux: 

        1. From a command prompt, navigate to the directory to which you downloaded the EUM Server installer. 

        2. Change permissions on the downloaded installer script to make it executable, as follows:

          chmod 775 euem-64bit-linux-4.5.x.x.sh
        3. Run the script as follows:

          ./euem-64bit-linux-4.5.x.x.sh
      • On Windows: 

        1. Open an elevated command prompt (run as administrator) and navigate to the directory to which you downloaded the EUM Server installer. 
        2. Run the installer:

          euem-64bit-windows-4.5.x.x.exe
    2. In the Welcome screen, click Next.
      The License Agreement page appears.  
    3. Scroll to the end of the license agreement, accept the license agreement and click Next to continue. 
    4. Select the directory in which you want to install the server and click Next.  
    5. Choose Demo for the installation mode. In this mode, the installer looks for a Controller on the current host and an Events Service on a separate host. It then installs the EUM Server on the same host as the Controller. Click Next.
    6. In the Database Setup dialog box:
      1. Enter a password in the Root User Password field.
      2. Enter and confirm a password for the eum_user database user account.
    7. In the End User Monitoring Server Setup screen:
      1. Enter the HTTP or HTTPs listening ports on the EUM Server at which the Controller will connect to the EUM Server (the default HTTP port is 7001 and HTTPS is 7002).
      2. Enter a new key store password and confirm it.

      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.

    Post-installation Tasks

    After installing the EUM server, you must perform three additional post-installation tasks:

    • Provision the EUM license
    • Configure the Events Services properties in the eum.properties file (optional)

    • Connect the EUM server with the AppDynamics Controller

    Provision the EUM License

    To provision the EUM license:

    Linux

    1. Log in to your EUM Server. 
    2. Change to the directory with the script for provisioning licenses: $> cd $EUM_HOME/eum-processor
    3. Provision each license, one at a time, on the EUM Server by running the following command: $> ./bin/provision-license <PATH_TO_EUM_LICENSE>


     

    The command needs to be run from the $EUM_HOME/eum-processor directory or it will fail.

    Windows

    1. Log in to your EUM Server. 
    2. Change to the directory with the script for provisioning licenses: $> cd $EUM_HOME\eum-processor
    3. Provision each license, one at a time, on the EUM Server by running the following command: $> .\bin\provision-license.bat <PATH_TO_EUM_LICENSE>


    The command needs to be run from the $EUM_HOME\eum-processor directory or it will fail.

    Configure the Events Service Properties

    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.properties file:

    1. Navigate to and start your Controller.
    2. Using the CLI, navigate to the bin directory.
    3. Open the eum.properties file for editing.
    4. In the eum.properties file, enter the following values:
      1. analytics.enabled=true
      2. analytics.serverHost=<hostname>, where <hostname> is the host where the event service is running
      3. analytics.accountAccessKey=<eum_key>, where <eum_key> is the Events Service key that appears as the appdynamics.es.eum.key value in the Administration Console:

        The configuration should appear similar to the following example:

    5. After updating the eum.properties file, restart the EUM Server.

    Connect the EUM Server with the AppDynamics Controller

    To connect the EUM server with the AppDynamics Controller:

    1. Log in to the Administration Console.
    2. Set the following Controller properties:
      1. eum.cloud.host: http://localhost:7001 – This tells you where the Controller will poll for EUM metrics
      2. 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
      3. eum.beacon.https.host: https://eum-host-name:7002 – This tells you where JS agent will be configured to send out the beacons over the HTTPS protocol
      4. eum.mobile.screenshot.host: eum-host-name:7001 – This tells you where the Controller will look for mobile screenshots

    Installing with the Silent Installer

    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:

    1. 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
    2. Modify values of the installation parameters based on your own environment and requirements. Particularly ensure that the directory paths and passwords match your environment.  

    3. 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
    • No labels