Automic Community

Expand all | Collapse all

Banner Agent revert version

Jump to Best Answer
  • 1.  Banner Agent revert version

    Posted 02-26-2020 01:25 PM
    I upgraded the BannerAgent on my development environment recently, and I had an issue.  I contacted tech support and got it resolved, but I am concerned with something going wrong if I upgrade my production environment on a Saturday, so I want to have a contingency plan in place so that if there is a failure, I can revert back to the previous Banner Agent and get the system going again.  My question is, is there a way I can extract the current Banner Agent jar file from the database?  It is not available from Broadcom that I have found.  If I can't get the jar file out of the database, will refreshing the database restore the previous version?  Is there a better way to revert the Banner Agent if the upgrade fails?


  • 2.  RE: Banner Agent revert version

    Posted 02-27-2020 07:53 AM
    Hi Randy, I just over the weekend upgraded out production AM V9.1.1 system to V9.3.1. I upgraded the RA Banner agent from 3.6.1 to 4.0.0 HF1. I am pretty sure I have the 3.6.1, and even older 3.5.2 in my software stack. 99% sure. I was told at one time fro, support how you can load back the Banner agent to a previous version from the RA screen in the GUI. What I have found over the years is sometimes upgrading RA Banner will create new files in your Banner working directories, or introduce the need for a parameter change in your env file for the instance.

    For us under the remote agent directory tree /srv/automate/appworx/prod|test|upgd|amraban/banner/<instance> there is  various files that
    are pointed too from the GUI agent runtime parameters. When I upgraded from 3.5.2 to 3.6.1 I had to make a env file change. For instance for us there is a amraban/banner/banprod directory. Under that there is various UC4* custom files, and a banprod.env.  When you start the agent you will see the files change. The date of the files tells you what changed when you started it.

    We customize some of the files like the UC4custom file, and then I believe a gjajob.shl something like that.  I always do greps before and after the upgrades for items I know we change. This way I check to see if we lost customizations.

    If  I can help you with obtaining a file, let me know.    Richard.Blumlein@colostate.edu

    ok, I looked. Sorry for TMI.. This is how I like to store my source files for my Appman work.    Looks like I have RA 3.5,2, 3.6.1, and 4.0.0.

    Rich

    > pwd
    /software/source/appworx

    > ls -la
    total 16
    drwxrwxr-x 18 appworx automate 4096 Oct 25 10:21 ./
    drwxrwxr-x 36 root system 4096 Aug 03 2015 ../
    drwxrwx--- 3 root system 256 Sep 24 2017 Groovy_2.4.12/
    drwxrwx--- 2 jobusr jobs 256 Jul 18 2018 Oracle_Database_11.2.0.4_JDBC_Driver/
    drwxrwx--- 3 jobusr jobs 256 Mar 30 2019 Oracle_Database_12.2.0.1_JDBC_Driver/
    drwxrwx--- 2 appworx appworx 256 Mar 04 2015 RA_3.5.0/
    drwxrwx--- 3 root system 256 Sep 24 2017 RA_3.5.2/
    drwxrwx--- 3 root system 256 Oct 16 2017 RA_3.6.1/
    drwxrwx--- 2 root system 256 Oct 25 13:54 RA_4.0.0_HF1/
    drwxrwx--- 2 root system 256 Oct 25 13:53 RA_4.0.0_HF1_NoWeb/
    drwxrwx--- 3 root system 256 Sep 24 2017 RA_Banner_Solution_3.5.0/
    drwxrwx--- 4 appworx appworx 256 Feb 17 2014 V80_P12_HF1/
    drwxrwx--- 4 appworx appworx 256 Jan 30 2017 V901_SP1/
    drwxrwx--- 4 jobusr jobs 256 Jan 30 2017 V90_HF1/
    drwxrwx--- 4 appworx appworx 256 Nov 04 2014 V90_P1/
    drwxrwx--- 3 jobusr jobs 256 May 01 2018 V911/
    drwxrwx--- 5 jobusr jobs 256 Jan 07 08:04 V931/
    drwxrwx--- 3 root system 256 Feb 03 2017 apache_2.4.25/






  • 3.  RE: Banner Agent revert version
    Best Answer

    Posted 02-27-2020 11:45 AM
    Hi Randy,
    I forgot to mention some about compatibility You probably already know that various versions of Rapid Automation Banner Solution are mean't for various versions of Applications Manager. When we were at V9.1.1 the compatible release was 3.6.x. When we were looking at upgrading to V9.3.1 the compatible version was 4.0.0+. I found out we needed the NoWeb version.

    Basically if you upgrade to a newer Banner agent, it should be compatible with Applications Manager. If you restore it back, it should still be compatible.

    When we upgraded to V9.3.1 we new if something was bad on the upgrade day we would have to restore directory trees, and also the database.  Since the database is updated, and all these new objects we would of had to restore that too.

    Once we are live, and running for even one business day, it would be really hard to roll back. It is easy to restore the master, and remote agent tree's but not the DB. AM would think all these jobs ran already, and lots of them are transfers.  When this happens we usually deal with it, and
    push on to find a fix or workaround.

    I hope this helps you.  Good luck.

    Rich