Question for Advanced Authentication upgrade from 9.1 to 9.1.02(9.1SP2)
search cancel

Question for Advanced Authentication upgrade from 9.1 to 9.1.02(9.1SP2)

book

Article ID: 242969

calendar_today

Updated On:

Products

CA Risk Authentication CA Strong Authentication CA Advanced Authentication

Issue/Introduction

After I complete the AA 9.0-->9.1 upgrade, if I need to re-import 9.0 DB again for the latest data, besides to re-run three db scripts, is there anything I need to do in order to make upgraded AA works with new DB again? What are the steps to upgrade from 9.x version to 9.1SP2 version?

Is there any changes to DB to run the install.sh from 9.1.1 to 9.1.02? if not, I don't have to re-run this patch.

Environment

Release : 9.1

Component :Risk Authentication

Strong Authentication

Resolution

Prerequisite

Advanced Authentication 9.x

Pre-upgrade Steps

Before you upgrade Risk Authentication and Strong Authentication, perform the following steps:

  • For Linux only, ensure you source arwfenv to set environment variables.
  • Ensure the ARCOT_HOME value is set.
  • Create a backup of the entire ARCOT_HOME folder and the database. If these tables are too large to back up, back up at least the following tables and procedures:
    • Tables:
      • ARWFAUTHAUDITLOG_AR
      • ARWFMESSAGES
      • ARWFCONFIG
      • ARRFADVICECODE
      • ARRFADVICECONFIG
      • ARRFCONFIGURATION
      • ARRFSYSPARAMSCONFIG
      • ARRFSERVERS
      • ARRFMESSAGES
      • ARUDSUSER_ARCHIVE
      • ARUDSCUSTOMATTREXT_ARCHIVE
      • ARUDSUSERCONTACT_ARCHIVE
      • ARUDSUSERDEVICES_ARCHIVE
      • ARUDSUSERDEVICES
      • ARUDSUSERCONTACT
      • ARUDSUSERACCOUNT
      • ARUDSCUSTOMATTREXT
      • ARUDSUSER
      • ARUDSUSERAUDITLOG
      • ARUDSCONFIGAUDITLOG
      • ARUDSORGANIZATIONAUDITLOG
      • ARPFCMNPRIVILEGEMAPPING
      • ARADMINROLEPRIVILEGE
      • ARADMINTXID
      • ARUDSUSERACCOUNT_ARCHIVE
    • Procedures:
      • GETNEXTSEQID
      • ARUDSORG_DELETE_SP
  • Stop the Strong Authentication service, the Risk Authentication service, and the Risk Authentication Case Management service.

Upgrade Strong Authentication from 9.x to 9.1 SP2

Extract the contents of the 

CA-AdvancedAuthentication-Patch-<version>-<platform>.zip

 file to the machine that hosts the 9.x version of Strong Authentication and perform the following steps:

  1. Navigate to the extracted folder (

CA-AdvancedAuthentication-Patch-<version>-<platform>

) and run the appropriate file:

    • For Windows, execute install.bat. 
    • For Linux, provide executable permission to install.sh and run the install.sh file.
  1. Follow the on-screen instructions to apply the patch.
  2. Manually execute the following db scripts from the 

<ARCOT_HOME>/dbscripts/<mssql or oracle>/upgrade

 directory on the database machine:

db-config-for-common-9.x-to-9.1.02.sql

db-config-for-strongauth-9.x-to-9.1.02.sql

  1. Stop the application server.
  2. If you previously customized any of the following files on the Strong Authentication server, these changes are overwritten when you install the patch. You must make these changes again to migrate them to Advanced Authentication 9.1 SP2. These files are located in 

$ARCOT_HOME/conf

. 

You only need to complete this step once. Skip this step if you have already completed it while upgrading your Risk Authentication server.

    • adminserver.ini
    • dbtrim.ini
    • dbtrim.properties
    • healthcheck.properties
    • udsserver.ini
    • restapi-log4j.properties
    • restapi.properties
  1. If you are upgrading from Advanced Authentication 9.0.x, or if your existing installation uses the

<ARCOT_HOME>/odbc64v80

 drivers, you must upgrade your ODBC implementation to odbc64. 

You only need to complete this step once. Skip this step if you have already completed it while upgrading your Risk Authentication server.

To verify your version of the ODBC drivers:

    • On Linux, check 

ODBCHOME

 in 

<ARCOT_HOME>/sbin/arwfenv

 (for Strong Authentication) or 

<ARCOT_HOME>/sbin/arrfenv

 (for Risk Authentication).

    • On Windows, check the DSN (data source name) in ODBC DataSource Administrator (64-bit).

See Updating ODBC for Advanced Authentication 9.1 SP2 for procedures on updating to odbc64.

  1. Start the Strong Authentication server and redeploy the following war files from ARCOT_HOME:
    • \java\webapps\arcotadmin.war
    • \java\webapps\arcotuds.war
    • \java\webapps\aa-restapi.war
  2. Restart the application server and verify that the following message appears in /logs/arcotadmin.log: 

Arcot Administration Console Configured Successfully.

  1. Launch the Advanced Authentication administration console and log in to verify that Strong Authentication is working correctly.

Upgrade Risk Authentication from 9.x to 9.1 SP2

Extract the contents of the

 CA-AdvancedAuthentication-Patch-<version>-<platform>.zip

 File to the machine that hosts the 9.x version of Risk Authentication and perform the following steps:

Navigate to the extracted folder (

CA-AdvancedAuthentication-Patch-<version>-<platform>

) and run the appropriate file:

    • For Windows, execute install.bat. 
    • For Linux, provide executable permission to install.sh and run the install.sh file.
  1. Follow the on-screen instructions to apply the patch.
  2. Manually execute the following db scripts from the 

<ARCOT_HOME>/dbscripts/<mssql or oracle>/upgrade

 directory on the database machine:

db-config-for-common-9.x-to-9.1.02.sql

db-config-for-riskauth-9.x-to-9.1.02.sql

  1. Stop the application server.
  2. If you previously customized any of the following files on the Risk Authentication server, these changes are overwritten when you install the patch. You must make these changes again to migrate them to Advanced Authentication 9.1 SP2. These files are located in 

$ARCOT_HOME/conf

You only need to complete this step once. Skip this step if you have already completed it while upgrading your Strong Authentication server.

    • adminserver.ini
    • dbtrim.ini
    • dbtrim.properties
    • healthcheck.properties
    • udsserver.ini
    • restapi-log4j.properties
    • restapi.properties
  1. If you are upgrading from Advanced Authentication 9.0.x, or if your existing installation uses the

<ARCOT_HOME>/odbc64v80

 drivers, you must upgrade your ODBC implementation to odbc64. 

You only need to complete this step once. Skip this step if you have already completed it while upgrading your Risk Authentication server.

To verify your version of the ODBC drivers:

    • On Linux, check 

ODBCHOME

 in 

<ARCOT_HOME>/sbin/arwfenv

 (for Strong Authentication) or 

<ARCOT_HOME>/sbin/arrfenv

 (for Risk Authentication).

    • On Windows, check the DSN (data source name) in ODBC DataSource Administrator (64-bit).

See Updating ODBC for Advanced Authentication 9.1 SP2 for procedures on updating to odbc64.

  1. Stop the application server and redeploy the following war files from ARCOT_HOME:
    • \java\webapps\arcotadmin.war
    • \java\webapps\arcotuds.war
    • \java\webapps\aa-restapi.war
    • \java\webapps\ca-userprofiling-application.war
    • \samples\java\ca-riskauth-sample-application.war
  2. Restart the application server and verify that the following message appears in ARCOT_HOME/logs/arcotadmin.log: 

Arcot Administration Console Configured Successfully.

  1. Start the Risk Authentication server and the Risk Authentication Case Management service.
  2. Launch the Advanced Authentication administration console and log in to verify that Risk Authentication is working correctly.

 

Additional Information

Powered by Wolken Software