@efd-hkg,
Enabling auditing starts a process which extracts the data from the Postgres database and copies it to the Append directory of the EVDMLA library. This process uses the Visual Data Builder web application and the SAS Pooled Workspace to perform the extraction.
To debug any problems in the process, you can configure additional logging on the Visual Data Builder web application and the Pooled Workspace server. For SAS Visual Data Builder, add the following XML to the /<SASConfig>/Lev<X>/Web/Common/LogConfig/SASVisualDataBuilder-log4j.xml and restart the Web Application Server.
<category additivity="false" name="com.sas.svcs.content.vdq.batch.audit">
<priority value="INFO"/>
<appender-ref ref="SAS_CONSOLE"/>
<appender-ref ref="SAS_FILE"/>
</category>
The result will be that the extraction process writes a note to the log on the middle tier machine at /<SASConfig>/Lev<X>/Web/Logs/SASServer12_1/SASVisualDataBuilder7.3.log. You can see that it runs the extract every 15 minutes.
in the Pooled Workspace Server set the level of the App.Program logger to INFO in /<SASConfig>/Lev<X>/SASApp/PooledWorkspaceServer/logconfig.apm.xml (or logconfig.xml) and restart the Object Spawner.
<logger name="App.Program" immutability="false">
<level value="INFO"/>
</logger>
The result will be that the extraction process writes a note to the log on the compute machine at /<SASConfig>/Lev<X>/SASApp/PooledWorkspaceServer/Logs/ showing the audit records being coped to the audit_visualanalytics table in the Append directory of the EVDMLA autoload location at /<SASConfig>/Lev<X>/AppData/SASVisualAnalytics/ VisualAnalyticsAdministrator /AutoLoad/EVDMLA/Append.
Do you see anything like that in your environment?
... View more
