BridgeGate Platform

BridgeGate Upgrade to 9.x Guide (Windows)

74 views May 15, 2019 May 15, 2019 admin 0

The BridgeGate 9.0 upgrade process is an automated process and is described below. Review the Release Notes(Notes Section) for any important considerations before proceeding forward with the upgrade. The automated upgrade will attempt to rename the bridgegate folder. If any applications/services/processes (other than the BridgeGate related services) are installed and accessing files inside the BridgeGate folder, stop them before proceeding. If any services under the BridgeGate folder are running, the automated installation will fail because it will not be able to rename the BridgeGate folder. Ensure that the User logged into the server to run this installer has administrator permissions to rename the BridgeGate folder. If the User does not have permissions the update will fail.

Back-out Plan

  1. Stop All BridgeGate Services and MySql
  2. Make a copy of the bridgegate folder named bridgegate_80_bkup
  3. Make a copy of c:\my.cnf
  4. To verify there are no locks, rename the bridgegate folder to “bridgegateTMP”, then rename it back to “bridgegate”
  5. Perform the 9.x upgrade
  6. If the upgrade fails, delete the bridgegate folder
  7. Put a copy of the backup my.cnf back to c:\my.cnf
  8. Rename bridgegate_80_bkup to c:\bridgegate
  9. Restart All BridgeGate Services and MySql

Automated Upgrade

  1. The Installer will perform the following upon selecting the Drive Letter from the Installer, (after you select OK to proceed with the Automated Upgrade):
  2. Stop all BG Services
  3. Rename the existing installation by adding the version number and todays date i.e. c:\bridgegate_VERSION_TODAYSDATE such as c:\bridgegate_8.0.23_180506.
    This is referenced in some of the following steps as BG_BACKUP_LOCATION.
  4. Copy the existing my.cnf to the /mysql dir under the BG_BACKUP_LOCATION and rename it by adding the version number and todays date i.e. c:\my.cnf_VERSION_TODAYSDATE such as my.cnf_8.0.23_180506 which in our example would be located here c:\bridgegate_8.0.23_180506\mysql\my.cnf_8.0.23_180506.
  5. Create a new bridgegate directory on the same drive.
  6. Extract the installation files into that new bridgegate directory.
  7. Restore the previous configuration information into the new Install location, from the BG_BACKUP_LOCATION.
    • /accounts
    • /FTPServer
    • /AS2Server
    • /data_archive
    • /data_history
    • /db_history
    • /ext – this should restore any customer plugins, etc.
    • The pre-existing my.cnf was not deleted so it will still be the file used when mysql is restarted.
    • /conf – the following files will be restored.
      • bridgegate.xml
      • BGLic.xml
      • lic.keystore
      • log4j.xml
      • urlrewrite.xml
    • /bin – the following files will be restored.
      • bg_service.conf
      • bg_as2_service.conf
      • bg_ftp_service.conf
      • bg_ssh_service.conf
    • /server/conf – the following files will be restored.
      • server.xml
    • /server/webapps – any customer files or dirs not normally installed by BridgeGate. The normal files or dirs that will NOT be restored include:
      • ROOT.war
      • ROOT
      • update.war
      • update
      • downloads
  8. Move The old bridgegate’s database schema files to the new bridgegate installation.
    • /mysql/data
  9. Copy the old bridgegate’s x509 certificates referenced in bridgegate.xml X509_KEYSTORE PATH_TO_KEYSTORE.
  10. Update the restored bridgegate.xml with VERSION=”9.0″ and insert under DB_ARCHIVE 2 new attributes:
    • ACTIVE_TRANSACTION_LOCATION=”/bridgegate/db_history”
    • HISTORICAL_TRANSACTION_LOCATION=”/bridgegate/db_history/backup”
  11. Start each of the installed BridgeGate services.

Verify Upgrade

  1. Ensure All BridgeGate services are started
  2. Verify you can login to the Portal
  3. Verify you can login using BGWorkbench
  4. Verify Scheduler is running via Portal
  5. Run test workflows
  6. If installed verify FTP Server and/or SFTP server is working.

Was this helpful?