AMP Upgrade Guide


The following placeholders are used in this document to refer to setting specific to your configuration.

  • [INSTALLATION_DIRECTORY] the actual installation directory for your AMP server
  • [AMP_HOST] the fully qualified host name for your AMP instance
  • [APACHE_LOGS] the full path to your apache log directory
  • [AMP_DB_USER] the database user for the AMP database
  • [AMP_DB_PASS] the database password for the AMP database
  • [SERVER_IP] with the IP address of your server (assigned to the fully qualified host name for your AMP instance)
  • [SERVER_ADMIN] with the user who will maintain the AMP install
  • [SSL_OPTIONS] The SSL configuration for your server (see the installation guide)
  • [AMP_SERVICES_URL] is the URL for the WAR file as deployed on the J2EE server
  • Note: All steps are applicable for both Linux and Windows installs unless otherwise specified

Minimum Hardware Requirements

  • Computer: Intel Pentium or compatible, 550 MHz or higher
  • Memory:
    • See J2EE Server
    • With J2EE Server running on the same hardware as Apache/MySQL 6GB (8GB Recommended)
    • Otherwise 2 GB for Apache/MySQL / 4GB for the J2EE Server (6GB Recommended)
  • Hard Disk space: 5GB (database size will grow with the number of reports, if you intend to run large spiders, start at 40GB)

Platform Requirements

  • Apache 2.x
    • mod-rewrite
    • mod-ssl (if SSL is to be used)
    • mod-proxy
    • windows: proxy_connect_module and proxy_http_module
    • linux: proxy_http
    • mod-headers
  • PHP 5.5
  • PHP Extensions
    • php5-curl
    • php5-mysql
    • php5-gd
    • php5-xml
    • mbstring
    • php5-mcrypt
    • php5-tidy
    • ZendGuardLoader -
  • MySQL 5.1.13
  • Java 8 (1.8)
  • J2EE Server - See also J2EE Server
    • Caucho Resin 4.0.30
    • JBoss EAP 6.2
    • WebLogic 12c
  • Firefox 14-39 Firefox Archive
  • Xvfb (on headless Linux/Other environment - not needed for Windows installations)
  • File extraction utilities
    • gzip
    • tar


  • In order for the Project Test Creation to work correctly, the date.timezone setting must be set. See
  • short-open-tag must be On
  • zend_extension=<full_path_to_ZendGuardLoader dll/so>
  • zend_extension=<full_path_to_opcache dll/so>

Helpdesk access

To access Helpdesk, users must be able to reach and in their browsers.

Upgrading AMP

  • Unzip the AMP zip file into a directory on your server
    • SSB recommends storing the AMP builds in a single /amp directory and then installing AMP versions into different sub-directories of this main directory
  • Update your Apache host configuration to point to the new directory
    • Update the DocumentRoot directive to be equal to [INSTALLATION_DIRECTORY]/amp
    • Update the php_admin_value include_path to [INSTALLATION_DIRECTORY]/includes
    • Turn RewriteEngine on (New)
    • Add RewriteConditions/Rule to route /api/ traffic to /api/flight.php (New)
    • You Virtual Host should look something like the example below. Note that this is just a general guideline, the OS/Apache version and setup may differ somewhat
<VirtualHost [SERVER_IP]:443>
RewriteEngine On [SSL_OPTIONS] ServerAdmin [SERVER_ADMIN]@[AMP Host] DocumentRoot "[INSTALLATION_DIRECTORY]/amp" ServerName [AMP_HOST] ServerAlias [AMP_HOST] ErrorLog "[APACHE_LOGS]/amp-error.log" CustomLog "[APACHE_LOGS]/amp-access.log" common <Directory "[INSTALLATION_DIRECTORY]/amp">
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule /api/(.*)$ /api/flight.php [QSA,L] Options FollowSymLinks AllowOverride AuthConfig php_admin_value mysql.default_user [AMP_DB_USER] php_admin_value mysql.default_password [AMP_DB_PASS] php_admin_value include_path "[INSTALLATION_DIRECTORY]/includes" php_admin_value display_errors Off php_admin_value log_errors On php_admin_value short_open_tag On php_flag magic_quotes_gpc Off php_admin_value max_input_vars 10000 </Directory>

<LocationMatch "/BluemixEndpoint">
ProxyPass [AMP_SERVICES_URL]/BluemixEndpoint
Header add Referer "[AMP_HOST]"
RequestHeader set Referer "[AMP_HOST]"
RequestHeader set transport "https"
</LocationMatch> </VirtualHost>

    • For strong SSL configuration parameters, see
    • Modify the SSL configuration file (RedHat: /etc/httpd/conf.d/ssl.conf, Debian: /etc/apache2/mods-enabled/ssl.conf)
      • SSLCipherSuite AES128-SHA:HIGH:!aNULL:!MD5
      • SSLHonorCipherOrder on
      • SSLProtocol all -SSLv3 -TLSv1
    • To use HSTS, add the following to the vhost
      • Header always set Strict-Transport-Security "max-age=63072000; includeSubdomains; preload"
    • To disable TRACE, add the following to the main Apache config file:
      • TraceEnable off
    • To prevent XFRAME, add the following to the apache vhost
      • <FilesMatch ".(php)">
        Header always set X-Frame-Options SAMEORIGIN
    • To prevent secure content from being cached:
      • <FilesMatch "(?<!\.css|\.js|\.jpg|\.gif|\.png)$">
        Header set Cache-Control private, no-cache, no-store, max-age=0, no-transform
  • copy your iftb_source folder from your previous installation to the [INSTALLATION_DIRECTORY] or create a new directory by that name. If you are creating a new directory make sure the user that Apache runs has is able to read, write and execute in that directory
  • copy your uploads folder from your previous installation (inside the amp directory) to the [INSTALLATION_DIRECTORY]/amp if you wish to keep images from your previous installation. If asked to over-write the existing directory, please choose Yes.
      • On Linux systems run the script which will allow your web server to generate AMP reports using InFocus
      • On Linux systems if apache is running as a user who is not in the www-data group (the default apache group on Ubunutu) then the EXEC_GROUP variable in the script should be set to the name of a group that the apache user is in
      • For mobile testing, the following must be run:
        • sudo a2enmod headers
        • sudo a2enmod proxy
        • sudo a2enmod proxy_http
      • Enable Apache modules:
        • proxy_module
        • proxy_connect_module
        • proxy_http_module
  • Restart Apache
    • LINUX
      • /etc/init.d/apache2 restart
    • Windows
      • Using your WAMP tray icon, restart the Apache Service
  • Check that the AMP login page displays when you go to https://[AMP_HOST]/login.php
    • If you are already logged in, it may redirect you to the dashboard and display errors. This is OK!
  • Login to the application as a System Administrator
    • Please note! Upon login, database updates will be running and may take some time to complete.
    • When it's finished, please run Standard Data Updates (select link or navigate to https://[AMP_HOST]/admin/util/data/standard_data_updates.php?submit=true)
  • Next, from the command line on your AMP server, cd to [INSTALLATION_DIRECTORY]/amp/admin/util/data/schema
  • Now, from the command line, import the MySQL stored functions as the MySQL root user by running the following:
    • mysql -u [MYSQL_ROOT_USERNAME] -p -D [AMP_DB_NAME] < function_import.sql
    • Type in the root password when prompted, then wait while it completes
    • mysql -u [MYSQL_ROOT_USERNAME] -p -D [AMP_DB_NAME] < triggers_import.sql
    • Type in the root password when prompted, then wait while it completes


  • After the steps above have been completed, your AMP installation should be ready for use! Please confirm by navigating to [AMP_HOST] and logging in.
  • Once logged in, navigate to the system requirements check page to verify everything is installed: http://[AMP_HOST]/verify.php
  • You are done! Enjoy your improved AMP

J2EE Server

Starting in the Fall 2012 version of AMP, Automated Testing and Spidering are done on the rendered browser source via a Browser (Firefox). This is done via a Services webapp running in a Java Application Server

The AMP Services webapp uses Selenium to control a Browser (Firefox) to render the Web page (including executing javascript) and the HTML is then run through the Testing Engine and results are sent to the AMP report. Since the Browser requires a display, on servers that do not have a GUI/Windowing System Xvfb can be used to run the Browser.

Please see the J2EE Server section of the Installation Guide

Core Updates

SSB BART Group continuously updates AMP's best practices, associated tests and technology platforms. For customers who choose not to use AMP or a custom instance managed by SSB BART Group, but to run their own private instance, SSB BART Group provides core updates separately. The readme file provided in the (ssb_core_updates.tar.gz) zip file describes all the steps needed to install these content updates.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Level Access Support | 800.889.9659
© 2005 - 2018 - Level Access All rights reserved.
Privacy | Security | Credits | License