After installing or upgrading to RSA Identity Governance & Lifecycle version 7.1.0 or above, the WildFly applicationserver log file, $AVEKSA_HOME/wildfly/standalone/log/server.log, is no longer updated.
The <handler name="FILE"/> entry for the WildFly application server log file is missing from the WildFly application server configuration file, $AVEKSA_HOME/wildfly/standalone/configuration/aveksa-standalone-full.xml. Because the file log handler is not configured, the WildFly application server does not log any messages to the WildFly application server log. Only the console log handler is configured in the WildFly configuration file and this information is logged to the application server standard output file, $AVEKSA_HOME/wildfly/standalone/log/stdout.log.
This issue has been reported in engineering ticket ACM-92729.
This issue is resolved in RSA Identity Governance & Lifecycle 7.2.
As a workaround, the WildFly configuration may be modified as follows:
Login as the oracle user
This procedure will modify the $AVEKSA_HOME/wildfly/standalone/configuration/aveksa-standalone-full.xml. Backup this file before proceeding.
This command modifies the $AVEKSA_HOME/wildfly/standalone/configuration/aveksa-standalone-full.xml file as shown below. The parameter <handler name="FILE"/> is added to the root-logger section so that WildFly server information will now be logged to server.log.