This page applies to an earlier version of the AppDynamics App IQ Platform.
See the latest version of the documentation.

Skip to end of metadata
Go to start of metadata

On this page:

The AppDynamics Platform Admin application automates the task of installing and administering the Events Service. Before installing an Events Service node, you need to install the Platform Admin application, as described on this page. 

About the Platform Admin Application

Though the Platform Admin Application can run on the same host as the Controller and, if installed, the embedded Events Service, it is recommended that you install it on a separate host. However, in any case, the machine you choose to run the application must meet the requirements for all the components that run on that machine, as outlined below. While they may run on the same machine, the Platform Admin application runs on a separate MySQL instance than the Controller. This allows the Platform Admin application to manage the Controller's instance, independent from the Controller host, creating a lightweight setup that consumes less memory.

The Platform Admin application prevents multiple users from running commands at the same time. If a second user attempts to run a command while another command is in progress, the second command is not completed and an error message appears indicating that another command is in progress. To avoid such conflicts, the application should generally be used by a single user at a time.  

Disk Space Requirements

The Platform Admin application requires 3 GB of free space to install.  

At a minimum, the host must have enough disk space for the Platform Admin application and a demo-sized platform, which includes a Controller that requires 50 GB of free space.

Network Protocol Requirements

The Platform Admin requires SSH or Secure File Transfer Protocol (SFTP) to be properly configured and enabled.

Software Requirements

On systems that run Linux, you must have cURL and netstat installed. Netstat is required by the Controller since the Platform Admin and the Controller reside on the same host. Linux systems must also have the libaio library installed. This library provides for asynchronous I/O operations on the system. 

The following table shows how to install libaio on some common flavors of the Linux operating system.

Linux FlavorCommand
Red Hat and CentOS

Run the following command: yum install libaio


Run the following command: sudo apt-get install libaio1

FedoraInstall the libaio RPM from the Fedora website.
DebianUse a package manager such as APT to install libaio (as described for the Ubuntu instructions above). 

Install the Platform Admin Application

Before starting, get the Platform Admin Application installer version appropriate for your target system. You can get the installer from the AppDynamics download site. When ready, follow these steps to install the application:

  1. Install the Platform Admin application with the following command: 





    The installation wizard launches. 

  2. Follow the steps in wizard to complete the installation. 

When finished, the Platform Admin application command line interface is ready to use. 

After the installation has completed, you may be presented with Java system preferences warnings. These warnings are benign and occur only during non-root installations.

Silent Installation 

To use the silent installation method, add the -q option, the response file, and destination directory to the command to run the installer.  For example, in Linux, run the following command:

./platform-setup-64bit-linux.sh -q -varfile ~/response.varfile -dir ~/appdynamics/platform

If you are running this command as a non-root user, the installation path specified as the dir argument value should be an absolute path, not a relative path as shown in the example. 

For a Windows system:

platform-setup-64bit-windows.exe -q -varfile c:/response.varfile -dir C\:\\AppDynamics\\Platform 

Sample response file for silent installation: 



platformAdmin.databasePassword= ENTER_PASSWORD
platformAdmin.databaseRootPassword= ENTER_PASSWORD
platformAdmin.adminPassword= ENTER_PASSWORD

The platformAdmin.dataDir property is optional.  




The platformAdmin.dataDir property is optional.  

If you install the Platform Administration Application on AWS, use the public DNS for the serverHostName value.

Platform Admin Application Command Line

The Platform Admin application command line utility allows you to perform orchestration tasks in an automated way.

Logging into and out of the Platform Admin Application

Commands for logging in, logging out, and resetting your password for the Platform Admin application are:

  • login --user-name <admin_username> --password <admin_password>
    If it has been more than one day since your last session, you will have to log in before you are able to use the command line utility. You will also have to log in again if you see the following error message:

    error: Command failed due to an error: Unauthorized
    API code 401
    Session expired. Please login and run the command again.
  • logout
  • reset-password
    If you forget your admin password or run into a 401 error, run this command to reset your password to its default value, admin. You will need to log out then log back in for this change to take effect.

Starting and Stopping the Platform Admin Application

Commands for stopping, starting, and checking the version of the Platform Admin application are:

  • start-platform-admin
  • stop-platform-admin 
  • show-platform-admin-version

The Platform Admin application must be running to install or administer Events Service nodes.

Additional Platform Admin Application Commands

You can view all available commands by running the following command:

./platform-admin.sh -h

And you can view details of a specific command by running the following command: 

./platform-admin.sh <command> -h
  • No labels