Skip to main content

How to Upgrade I-SRA App Gateway

This article outlines the necessary steps to upgrade the Application Gateway for I-SRA environment. Generally, the upgrade procedure quite same with the installation of the I-SRA App Gateway. I-SRA App Gateway upgrade can be segmented into these procedural steps:

  • Obtaining Token & Installer
  • I-SRA App Gateway Upgrade

Obtaining Token & Installer​

The first procedure to do is to obtain the installation token and the installer file by conducting these steps:

  1. Login to Safous Admin Portal and navigate to Tenant > Services where you can find the Get Token and Download Installer button.

  2. Click Download Installer button. Once you have clicked the Download Installer button, the compressed installer file will begin downloading in your browser.

  3. Click Get Token button. After you click the Get Token button, a App Gateway-up window with two buttons will appear. Click Copy button and paste KEY in your notes application to be used later, then download the token by clicking the Download button.

  4. Copy new installer file safous-ot.tar.gz and token file ot-token.txt to App Gateway and App Gateway server

I-SRA App Gateway Upgrade​

Please refer to the instructions below for upgrading the App Gateway in the Safous I-SRA environment:

  1. Access existing App Gateway Server and extract the Installer.

    :~$ tar xzf safous-ot.tar.gz
  2. Set the environment variable 'KEY' from the Admin Portal.

    :~$ KEY=(Paste KEY from Admin Portal)
  3. Run Installer.

    :~$ cd safous-ot
    :~$ sudo bash ot-installer.sh -k $KEY -f ../ot-token.txt
  4. Input ‘Y’, since this is an existing App Gateway and the certificate file should already exist in your App Gateway.

note

This confirmation dialog is shown when the "custom certificate" deployment option is selected.

  1. The upgrade script will automatically run and restart the App Gateway container after the process is complete.

  2. After the App Gateway upgrade is complete, verify the running containers. There should be three containers running: idac, guacd, and rdp-proxy.

    :~$ sudo docker ps