In WebSphere and WebLogic implementations of RSA Identity Governance & Lifecycle, the WorkPoint.log file which is used by the workflow engine to log information and heap dump files are written to the root directory ( / ). These files are supposed to be written to the same directory as the other application log files, such as the aveksaServer.log and aveksaServerInfo.log files. When the WorkPoint.log file is not written to the common logging directory, it will not be available for download from the Server Nodes tab under Logs (Admin > Server Nodes tab).
This can cause space issues since most installations do not allocate much space to this file location.
A WorkPoint.log can be found in the application log directory but it is a static file and no data is written to it. The functioning WorkPoint.log is incorrectly written to the root directory.
This issue is due to a change in the way WebSphere and WebLogic start the RSA Identity Governance & Lifecycle application. The workflow environment may be started before the RSA Identity Governance & Lifecycle application and consequently unable to retrieve the log file location from the RSA Identity Governance & Lifecycle application.
The solution is to set the parameter that specifies the file location so that it is available to the workflow engine when Workpoint is started. The parameter is called log.dir which can be set on the application server. To define this variable, follow the same procedure as defined in the RSA Identity Governance & Lifecycle Installation Guide for setting the JVM arguments for the ACMProviderURL.
You can define the location for the WorkPoint.log file and heap dumps wherever you would like but RSA recommends using the existing application log directory in order to make the WorkPoint.log available for download from the RSA Identity Governance & Lifecycle user interface (System > Server Nodes tab).
Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the application log directory for WebSphere and WebLogic implementations. For WebSphere this may be similar to /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/imgNode01Cell/aveksa.ear/aveksa.war/log. For WebLogic this may be similar to $WL_HOME/user_projects/domains/aveksaDomain/servers/aveksaServer/tmp/_WL_user/aveksa/5y3cp0/aveksa.war/log/.
The server node(s) will need to be restarted for the changes to take affect.
If RSA Identity Governance & Lifecycle is deployed on a cluster, this resolution needs to be applied on all nodes of the cluster.
Redeploying the application will change the file location back to the root directory.