AudienceView Connect
AudienceView Documentation

AudienceView Patch and HotFix Installation Guide

 

Once a patch has been released using the Release Packaging Automation process follow the following process to patch a client.

Pre-Patch Preparation

  1. Connect to the client following the steps in the VPN Access portion of the PA-DSS Implementation Guide.
  2. Browse to http://electron/ and download the latest patch for your version as well as the latest Migration package.
  3. Transfer the downloaded .ZIP files to the App server using the steps in the AudienceView Software Distribution portion of the PA-DSS Implementation Guide.
  4. Login to AVConnect using the credentials provided by your account manager.
  5. Browse to the Documents section and download the release notes for the patch of AudienceView that you are applying.
  6. Using File Checksum Integrity Verifier (FCIV) as recommended by the AudienceView Software Distribution portion of the PA-DSS Implementation Guide compute the MD5 hash of both the .ZIP patch and the .ZIP migration package.
    1. Run the Cmd prompt as Administrator.
    2. Change the directory to the FCIV folder.
    3. Run fciv.exe C:\AudienceView\Build\audienceview_x_x_x.zip, where x_x_x is the AudienceView version number.
    4. MD5 hash will appear in the cmd prompt.
  7. Ensure the MD5 hashes computed in Step 6 matches the MD5 hashes contained in the release notes obtained in Step 5.
  8. Notify all active users that the system will be temporarily down.
  9. On the App Server open IIS.
  10. Stop the site and App Pool named ClientNameProdDesktop where ClientName is the name of the Client being patched.
    Information
    If any additional sites or servers are being used with the same DB those sites should also be stopped.
  11. On the DB Server open Sql Studios.
  12. Backup DB ClientNameProd.

Upgrade Libs

  1. On the App server.
  2. Unzip the patch zip file to C:\AudienceView\Build\audienceview_x_x_x replacing x_x_x with the version number.
  3. Browse to the C:\AudienceView\Build\audienceview_x_x_x\Libs folder.
  4. Right-click on the registerlibs.bat file.
  5. Select Run as administrator.
  6. Right-click on the regcaptcha.bat file.
  7. Select Run as administrator.
  8. Browse to the C:\AudienceView\Build\audienceview_x_x_x\Libs\AVS Gateways folder.
  9. Right-click on the CopyDLLs.cmd file.
  10. Select Run as administrator.
  11. Browse to the C:\AudienceView\Build\audienceview_x_x_x\Libs\Payment Gateways folder.
  12. Right-click on the CopyDLLs.cmd folder.
  13. Select Run as administrator.

Upgrade UI

  1. On the App server.
  2. Copy the C:\AudienceView\Build\audienceview_x_x_x\UI folder into the C:\AudienceView\Client_Name folder.
  3. Rename C:\AudienceView\Client_Name\ProdDesktop to C:\AudienceView\Client_Name\ProdDesktop_oldVersionNumber.
  4. Rename C:\AudienceView\Client_Name\UI to C:\AudienceView\Client_Name\ProdDesktop
  5. Browse to the C:\AudienceView\Build\ClientName\ProdDesktop_oldVersionNumber folder.
  6. Copy the current connection string found on line 29.

    tsApp.setConnectString("COPY THIS PORTION")
     
  7. Right-click on the global.asa file.
  8. Select Edit.
  9. Browse to the C:\AudienceView\Build\ClientName\ProdDesktop folder.
  10. Right-click on the global.asa file.
  11. Select Edit.
  12. Replace the current connection string found on line 29 with the one copied in Step 8.

    tsApp.setConnectString("REPLACE THIS PORTION")
     
  13. Save and close the global.asa file.

Upgrading the DB Schema

  1. On the App server.
  2. Unzip the Migration package .ZIP file to C:\AudienceView\Build\Migration.
  3. Run the Cmd prompt as Administrator.
  4. Change the directory to C:\AudienceView\Build\Migration\VersionUpgrade\z.z\y_y_y_x_x_x, where z.z is the version of AudienceView that the client will be using, y_y_y is the AudienceView version number that the client will be migrating from, and x_x_x is the AudienceView version number that the client will be migrating to.
    Information
    If there is no folder ending in the patch number being applied no DB Schema changes are needed and proceed to the Sanity Check section.

    .

  5. Run VU_launch_y_y_y_x_x_x.bat --du [dbuser] --dp [dbpass] – s [dbserver] – dn [dbname]
  6. Fill in the following values provided by your sql administrator:
    • Set dbuser = The database user name.
    • Set dbpass = The database user password.
    • Set dbserver = The IP address of your sql server.
    • Set dbname = ClientNameProd.

Sanity Check

  1. On the App Server open IIS.
  2. Start the site and App Pool named ClientNameProdDesktop as well as any other sites and app pools using the same database.
  3. Open a browser.
  4. Browse to https://localhost:8080/.
  5. Login using your AudienceView 'User name' and 'Password'.
    These will be the same as before the patch.
  6. Select Box Office from the 'User Role' dropdown.
  7. Press SHIFT+A.
  8. A pop-up will appear with the current Libraries being used. Confirm that this matches the patch that was applied and that after the 'Build Date' the words [Unofficial Build] do not appear.
  9. Click 'Apply'.

Cleanup

To remove unnecessary files, complete the following:

  1. On the App Server.
  2. Close all of the files and software that remain open.
  3. Delete the patch and migration .ZIP files.
  4. Browse to the C:\AudienceView\Build folder.
  5. Locate the old AudienceView Version folder. Delete the entire audienceview_y_y_y folder.
  6. Delete the entire Migration folder.
  7. audienceview_x_x_x should be the only folder remaining.
  8. Browse to the C:\AudienceView\Build\ClientName folder.
  9. Delete the entire ProdDesktop_oldVersionNumber folder.
  10. On the database server, delete the backup created in Step 12 of the Pre-Patch Preparation section.
  11. Notify all active users that the system is running.