000037435 - Changes to JSP files are not reflected until the RSA Identity Governance & Lifecycle application is restarted

Document created by RSA Customer Support Employee on May 3, 2019
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000037435
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition:  7.0.2, 7.1.0, 7.1.1
IssueIf an uploaded JSP file exists in the User Interface (Admin > User Interface > Files) and a new or modified version of that same JSP file is uploaded, the changes specified by the newer JSP file are not reflected until after the RSA Identity Governance & Lifecycle application is restarted.

Cause This is intended behavior.  After uploading a modified JSP file that already exists on the RSA Identity Governance & Lifecycle system, the server needs to be restarted for the changes to take effect.
ResolutionThe resolution is to restart the RSA Identity Governance & Lifecycle application:  As the oracle user, run:

$ acm restart

A fix has been made to 7.0.2 P24, 7.1.0 P07 and 7.1.1 P02 that adds the following error message to the User interface when uploading a newer version of the same JSP file:

After uploading a modified file that already exists in the system, restart the server to apply the changes. You can update custom string properties, security files and style sheets without a server restart.