How to deploy or modify a Style when using Identity Management and Governance 7.0+
Originally Published: 2017-04-13
Last Modified: 2023-09-22
Article Number
Applies To
RSA Product/Service Type: Appliance
RSA Version/Condition: 7.0.x
Platform: Wildfly
Platform (Other): 7.0.x
Resolution
provides a utility (customizeACM.sh in /home/oracle/deploy) that allows you to conveniently extract
an aveksa.ear file and use the utility to rebuild a customized version. This utility uses the
/home/oracle/archive directory to store archived aveksa.ear files that have been deployed and to
maintain information about the currently deployed aveksa.ear.
Procedure
1. Log on to the appliance as the admin user.
2. Verify that RSA Identity Governance and Lifecycle is running. Enter
sudo service aveksa_server status
If RSA Identity Governance and Lifecycle is running, the following message displays:
Aveksa Compliance Manager Server is running
If the message indicates that the server is not running, enter
sudo service aveksa_server start
3. Change to the oracle user.
4. Go to /home/oracle/deploy.
5. Run the customizeACM.sh script to extract the .ear file:
customizeACM.sh -c <path to the ear file>
Appendix C: Maintenance 186
Installation Guide
The contents of the .ear are extracted to a directory in the following location:
/tmp/customizeACM/.
Note: If you do not specify the path to the .ear file, the script prompts you to use the currently
deployed .ear file. If you want to use the currently deployed .ear, enter yes. If you do not want
to use the currently deployed .ear, enter no.
6. Go to /tmp/customizeACM/ and modify the extracted files.
a. create a custom directory under /tmp/customizeACM/aveksa.war/
mkdir custom
b. go to /tmp/customizeACM/custom/aveksa.war/
cd custom
c. create a styles directory under /tmp/customizeACM/aveksa.war/custom
mkdir styles
d. copy the Mystyle.zip file into /tmp/customizeACM/aveksa.war/custom/styles
e. unzip MyStyle.zip
7. When you finish modifying the files, run the customizeACM.sh script again to rebuild the .ear
file. From /home/oracle/deploy, enter
customizeACM.sh -d
The script performs the following tasks:
- Archives the new .ear file to the following location, appending a time and date stamp to the
name: /home/oracle/archive.
-Deploys the new customized .ear file.
8. starting on 7.0.2 versions the following command is also required when adding style for the first time.
Add it to the database
insert into t_system_settings values ('CustomStyle', 'custom/styles/MyStlyle');
commit;
Related Articles
An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x Number of Views Using SQL Select nodes with RSA Identity Management and Governance Number of Views When configuring fob-style token profile, the token is configured as PINPad-style when using RSA Authentication Manager 8.… Number of Views Web Page not found when using HTTPS in URL in RSA Identity Management and Governance Number of Views RSA Identity Management and Governance SSLHandshakeException when using a custom Java workflow node on Red Hat Enterprise … Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update How to Forward RSA Authentication Manager 8.4 or Later Logs to Multiple Syslog Servers Using rsyslog RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
