Skip to main content

RHEL upgrade guide for bare-metal

  • Updated

This document describes the Linux upgrade process for configuring a LAMP stack, the Wildfly J2EE server, and Level Access’s AMP applications on RedHat Enterprise Linux (RHEL) 8.x.

On this page:

Required skills

Level Access expects that customers who self-host their instance of AMP has IT staff with the appropriate level of access, knowledge, and ability to perform basic hosting-related IT tasks, such as:

  • Installation and configuration of server, application, and database software.
  • Email (specifically SMTP) account setup and configuration.
  • Configuration of DNS and other services.
  • Obtaining or creating signed SSL certificates (https/TLS implementation is mandatory).

In larger enterprises, where there are many different IT teams involved in configuration and setup, we recommend assigning a project manager to ensure all appropriate parties are aware of the upgrade requirements.

You'll need administrator or root access on the target computer to run the commands needed to install AMP and the supporting software. You'll also need to ensure that SELinux is not in "enforcing" mode.

Contact AMP support

Current licensed AMP users can enter AMP support inquiries online. For general AMP inquiries relating to licensing, pricing, or use please e-mail us at ampsupport@levelaccess.com or call us at (800) 889-9659.

Prerequisites

Before to upgrading, ensure that your system still meets the minimum requirements. These can be found in AMP on-premise system requirements. An abbreviated list includes:

  • PHP 8.x
  • MySQL 8.x
  • Java 11+
NOTE: You must log out of your AMP instance via your web browser before you begin the upgrade.

Database backup

NOTE: AMP 9.49.x requires at least MySQL 8.0. Previous versions of MySQL are not supported and won't allow AMP to run.

We highly recommended that you take a database snapshot before performing the upgrade. To do this, issue the following command from a computer that has access to the AMP database. Substitute the username, database name, and host that AMP uses to access the database for [DB_USER], [DB_NAME], [DB_HOST]. Substitute the current version of AMP for [VERSION].

mysqldump –no-tablespaces --skip-triggers --single-transaction -u [DB_USER] -p [DB_NAME] -h [DB_HOST] -r amp.[VERSION].db.sql

This generates a file named amp.[VERSION].db.sql in the directory where you run the command.

Upgrade AMP database

Update SQL functions and triggers

  1. Using the command line, navigate to the mysql-install/triggers folder.
  2. Use the MySQL client to import the functions and triggers by entering the following in the command prompt:
cd mysql-install/triggers
 
mysql –u root –p –D [AMP_DB_NAME] < triggers_import.sql
 
mysql –u root –p –D [AMP_DB_NAME] < function_import.sql

Upgrade AMP

Prepare file system

NOTE: AMP 9.49.x requires at least PHP 8.0 is installed. Previous versions of PHP are not supported and will not allow AMP to run.

You'll receive the AMP upgrade file as a zip file inside the AMP-9.49.0-UpdateFiles.zip named amp.zip. Unzip this file and move the resulting amp-install/9.49.0 to the /opt/amp directory.

tar xzf amp.tgz
 
mv amp-install/9.49.0 /opt/amp/
NOTE: If the location of your AMP installation files is somewhere other than locations used in the following steps, adjust the paths appropriately throughout this guide.

Copy/move uploaded assets

AMP stores documents and images that are uploaded on the file system. You can find the documents and images in the following locations:

  • /opt/amp/[VERSION]/amp-[VERSION]/amp/uploads/
  • /opt/amp/[VERSION]/amp-[VERSION]/amp/exports/
  • /opt/amp/[VERSION]/amp-[VERSION]/amp/macro_scripts/
  • /opt/amp/[VERSION]/amp-[VERSION]/documents/
  • /opt/amp/[VERSION]/amp-[VERSION]/iftb_source/
  • /opt/amp/[VERSION]/amp-[VERSION]/private_keys/

To preserve these assets across AMP versions, move these folders from the previous amp-[CURRENT_VERION] folder to the corresponding folder in the amp-9.49.0 folder.

cd /opt/amp/[CURRENT_VERION]/amp-[CURRENT_VERION]/

mv amp/uploads /opt/amp/9.49.0/amp-9.49.0/amp/
   
mv amp/exports /opt/amp/9.49.0/amp-9.49.0/amp/

mv amp/macro_scripts /opt/amp/9.49.0/amp-9.49.0/amp/
 
mv ./documents /opt/amp/9.49.0/amp-9.49.0/amp/
 
mv ./iftb_source /opt/amp/9.49.0/amp-9.49.0/amp/
 
mv ./private_keys /opt/amp/9.49.0/amp-9.49.0/amp/

Update Permissions

Ensure that each of the folders copied in the previous step are readable/writable by the user that Apache is running as. To update permissions, run the update_permissions.sh and hosted_permissions.sh scripts from the tools directory.

NOTE: Before running the scripts, ensure that the EXEC_GROUP value at the top of these scripts is set to a valid group for the Apache user.
cd /opt/amp/9.49.0/amp-9.49.0/tools
 
sudo sh update_permissions.sh
 
sudo sh hosted_permissions.sh

(Optional) Upgrade SSO configuration

If you use the SimpleSAML installation that. Level Access provided with AMP, you can upgrade the SSO SAML service. Learn more about the upgrade process for SSO SAML service.

Edit AMP virtual host

Locate the existing Apache VirtualHost definition for AMP. This could be in a variety of locations on the file system but should be in the location that the apache24-amp.conf file was copied during the initial AMP installation.

  1. Update the DocumentRoot to use the new version path. For example, /opt/amp/9.49.0/amp-9.49.0/amp.
  2. Update the php_admin_value include_path to use the new version path. For example, /opt/amp/9.49.0/amp-9.49.0/includes.
  3. Update the Alias /access-assistant to refer to the /opt/amp/9.49.0/assistant/9.5.1.21 directory.
  4. (Optional) Update the Alias /simplesaml to point to /opt/simplesamlphp/public directory.

Restart Apache

You must restart Apache to update the AMP server with the changes above.

To restart Apache:

  1. Run configtest to ensure that the changes made above to the Apache VirtualHost configuration file do not have any syntax of configuration errors.
    source /opt/rh/httpd24/enable
 
apachectl configtest
  2. Verify the Syntax Ok message appears
    NOTE: If there are problems with the configuration file, an error with a line number will appear. Review and correct the errors until the Syntax Ok message is received.
  3. Issue the command to gracefully restart Apache.
    sudo systemctl restart httpd24-httpd

Log in as System Admin

  1. Go to https://YOUR_SERVER_URL/admin/util/data/schema/update.php.
  2. Enter the credentials of the user whose password was updated in the Update System Admin Password section above at the AMP login screen. You'll be directed to an unformatted page with a schema update message.
    Unformatted success page; shows a message describing that the Schema has been updated.
  3. Select Standard Data Updates. You'll be directed to the Reload AMP Data page.Reload AMP data page, shows a success message.
  4. Select the AMP logo in the page header to return to the new AMP dashboard.

Upgrade Wildfly

Prepare File System

Move the wildfly.tgz file to the Wildfly server and unzip the file. This creates a folder named /wildfly-install which contains the files necessary to configure the JEE system for AMP.

Deploy Webapp

Deploy the AMP Services Web App by copying the AMPJSONServices.war file from the AMP Install files directory to the Wildfly standalone/deployments directory:

sudo -u wildfly cp wildfly-install/AMPJSONServices.war /opt/wildfly/standalone/deployments/

Proxy updates

The spidering-services.json file in the wildfly-install folder has the section with proxy settings.

  1. Add a section with your organization's proxy setting to the spidering-services.json file to your deployment in $JBOSS_HOME/standalone/configuration/spidering-services.json.
  2. Restart JBoss to apply the updates to the spider-services.json for deployed webapps.

Related articles

Comments

0 comments

Article is closed for comments.