What happens to Access Fulfillment Express (AFX) during an Aveksa Compliance Manager (ACM) patch installation on a RSA Identity Governance & Lifecycle software or hardware appliance
Originally Published: 2018-04-05
Article Number
Applies To
RSA Product/Service Type: Identity Governance & Lifecycle
RSA Version/Condition: 7.0, 7.1
Platform: Hardware and Software Appliances based on WildFly with local AFX installations
Issue
Resolution
The /home/oracle/AFX/upgrade/upgradeAFXServer.sh script is run during the patch installation.
We do backup and restore data from /home/oracle/AFX/activemq/data after the AFX reinstall:
A log file named is written to /home/oracle with a name of afx-server-upgrade-<date and time stamp>.log. The timestamp will be different and dependent on the patch installation date and time. For example, afx-server-upgrade-04-04-2018.22.39.44.log.
Related Articles
Application of RSA Identity Governance & Lifecycle 7.0.2 patch 07 fails to start Aveksa Compliance Manager (ACM) for remot… Number of Views RSA Governance & Lifecycle Integration: SAP Number of Views ACM-100162 || PV_USER_ALL_ACCESS view does not include custom attributes post 7.1.1 installation Number of Views Requests in state "Waiting On Dependencies" remain stuck in the fulfillment phase in RSA Identity Governance & Lifecycle Number of Views Active Directory Account Collector fails with 'Naming Exception happened' in RSA Identity Governance & Lifecycle Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device SecurID Tokens How to implement SAML SSO Authentication with Microsoft Azure Active Directory and RSA Identity Governance & Lifecycle Do TCP Agent using API ver. 8.5 & 8.6 need a new sdconf.rec file after a new Primary is promoted? RSA Authentication Manager 8.9 Patches and Hotfixes Readme
Don't see what you're looking for?
