How to avoid disappearing of customerstrings.properties file after restarting application server?
Thanks in advance.
The fix is also available in 7.0.0 Patch 05
How did you import the file? As far as concerned it should not be removed if you import it from Admin > User Interface > Files.
I imported it from Admin > User Interface > Files. By the way, i restarted application server of Version 22.214.171.124720 P04. Maybe, it is only occured on patch 04. I'll try it on patch 02 version as well.
Just to make sure, you uploaded it under Files and then chose Customer Strings in the drop down, right?
I executed acm restart command. After checking same screen, customerstrings.properties file is disappeared.
I tried same thing on Version 126.96.36.199432 P02. I executed below commands.
su - admin
After server is running, i check Admin -> User Interface -> Files. Files are not disappeared.
I re-tried same thing on Version 188.8.131.52720 P04. I executed below commands.
After server is running, i check Admin -> User Interface -> Files. Files are disappeared.
Wow- so I can let the team internally here at RSA know about this, but I wasn't aware that 7.0 Patch 4 is even officially released at this time (Patch 03 was only relatively recently released)- so I'm not sure if it's just an artifact of it being an unofficial release, or if it's something to be fixed prior to release.
I'm not able to reproduce this on that version. Sorry to repeat Boris's question, but you selected "Customer Strings" in the dropdown before you uploaded AND when you went back to the page after restart? Also, the file name needs to start with "customerstrings" and end with ".properties".
Do you see the customized strings reflected in the UI? You can check the T_AV_FILES table in the database to see if the customerstrings.properties file is there.
This issue is not occured on Version 184.108.40.206432 P02. Did you try to reproduce on Version 220.127.116.11720 P04?
Please apply below steps on Version 18.104.22.168720 P04.
1. Upload customerstrings.properties file
2. Restart application server with using same commands in screen shot.
3. Check customer strings table again.
I realised something interesting when comparing both t_av_files table of Version 22.214.171.124720 P04 and Version 126.96.36.199432 P02.
When i check T_AV_FILES for Version 188.8.131.52720 P04, i see five paths are recorded. We see here multiple paths because uploading same file more than once because it disappears on UI after restarting application server.
When i check T_AV_FILES for Version 184.108.40.206432 P02, i see one path is recorded. Problem is not occured on Version 220.127.116.11432 P02.
The problem seems to be that aveksa.war is appended with a series of alphanumeric characters in your P04 environment. Those characters must change after each restart, which is why the customerstrings.properties file can't be restored after the restart. Maybe something has changed with the deployment process. I'll see if I can track down a change like this.
This problem is still present in Patch 04.
After every restart custom dashboard components are deleted..
I logged a bug against P04 to get this looked at closer.
(Note that at the time of this writing 7.0 P04 has not been officially released yet.)
We got an email from RSA regarding release of P04. We did applied the P04 as per RSA recommendation and it wiped off all the files :Images,dashboard Images,JSP pages, customer strings,Security Files. There is nothing under Admin->UI->Files.
From: email@example.com [mailto:firstname.lastname@example.org] Sent: 06 September, 2016 8:08 AMTo: Subject: [**EXTERNAL**] RSA Announces the Availability of RSA Via Lifecycle and Governance 7.0.0 Patch 04
Dear Valued RSA Customer,
RSA announces the availability of Patch 04 for RSA Via Lifecycle and Governance version 7.0.0. This release contains numerous fixes and improvements. See the RSA Via L&G 18.104.22.168 Release Notes for additional information about the contents of the patch.
Recommendation:RSA strongly recommends that customers upgrade to this latest update. Please note that all patches are cumulative.
Obtaining Software and Documentation:The Release Notes are accessible under the RSA Via Lifecycle and Governance 7.0 documentation space.
You can access the RSA Via L&G 7.0.0 patch 04 software via the RSA Via Lifecycle and Governance 7.0 Downloads space on RSA Link. At the bottom of this Downloads page when you select the "Additional Downloads" link you will be presented with a list of products that you are entitled to based on the RSA products you have purchased. Select the appropriate license link to access the available RSA Via Lifecycle and Governance software downloads. If you do not have this license in your list of products, then please contact RSA Customer Support.
For additional documentation, downloads, and more, visit the RSA Identity Governance and Lifecycle page.
RSA has a defined End of Primary Support policy associated with all major versions. Please refer to the Product Version Life Cycle for additional details.
RSA Customer Support
This is due to a change in the way temporary directories are named for deployed EAR files when the server is started, which is not accommodated by the application code. The issue is being addressed at this time and should be available in an upcoming patch release.
In the interim, the workaround is to re-upload the custom file(s) whenever the server is restarted.
And specifically in response to/confirmation of Vishwanath Babali's post, this issue is specific to Wildfly EAR file deployments and applies to all types of custom files that can be uploaded via the Admin --> User Interface --> Files screen, including:
This is a known issue, RSA is working on solution for this.
FWIW, this is appearing in 7.0.1 as well.
The fix was included in 7.0.1 P01.
Has 7.0.1 P01 been released? Neither I nor my customer can see it in Download Central.
It has not been released yet. We are in the process of testing right now
Sean Miller | Senior Manager, Software Engineering | RSA
O: (519) 954 8162
RSA Identity Governance and Lifecycle Community: https://community.rsa.com/community/products/governance-and-lifecycle
Thanks Sean. Is there any ETA or workaround available? This seems like a pretty serious defect.
Retrieving data ...