Troubleshooting DLP Analytics Engine Issues
- Article Number: 000013475
- Products: Forcepoint DLP
- Version: 8.7, 8.6, 8.5, 8.4
- Last Published Date: December 01, 2020
Notes & Warnings
Note The Analytics Engine for 8.7 on the Downloads page is identical to the 8.6 version. If the SQL database is an instance or is using a non-standard port, please confirm that the Forcepoint Management Infrastructure's SQL connection port is not left blank as seen in the installer. This can be confirmed by running a modify of the Infrastructure installer on the Management Server. To confirm that the proper value is set, please run the following query on the SQL Server: SELECT * FROM PA_CONFIG_PROPERTIES WHERE GROUP_NAME = 'DB_CONFIGURATION'; If this port value in Infrastructure is left blank (meaning it is automatically obtained), the value above defaults to 1433, which does not function for SQL instances. |
Problem Description
After configuring the Analytics Engine, the Incident Risk Ranking page is not showing any data. The Incident Risk Ranking is not updating with risk cases on the DLP Dashboard. |
Resolution
Note The changes below require root access. If the Forcepoint Analytics Engine OVA image was used, raise a case with Technical Support for assistance.
Attempting to connect…
Connection succeeded.
Evaluation started.
Evaluation completed. Reporting started. Reporting completed. Runtime:[1093] seconds Completed:[2017-04-18 18:08:23.889309]
2017-08-09 12:40:26,404 HealthCheck Error HTTP request to http://localhost:17515/ae-services generated error: HTTP response code was 404
2017-08-09 12:40:26,405 HealthCheck Error DSSBatchServer: Service [Analytics Engine service] URL: [http://localhost:17515/ae-services] is not alive. please validate the WAR is deployed and has no errors 2017-08-09 12:40:26,407 HealthCheck Error DSSBatchServer: restarting the DSSBatchServer 2017-08-09 12:40:26,407 HealthCheck Error Stopping process: DSSBatchServer
<New id="PaDS" class="org.eclipse.jetty.plus.jndi.Resource">
<Arg></Arg> <Arg>jdbc/PaDS</Arg> <Arg> <New class="com.jolbox.bonecp.BoneCPDataSource"> <Set name="driverClass">net.sourceforge.jtds.jdbcx.JtdsDataSource</Set> <Set name="jdbcUrl">jdbc:jtds:sqlserver://10.50.212.39;ssl=off;databaseName=wbsn-data-security;tds=8.0;appName=wbsn-service</Set> <Set name="username">[SQL UserName]</Set> <Set name="password"> <Call class="com.pa.crypto.crypto.CryptorUtils" name="decrypt"> <Arg type="java.lang.String" id="password">{wsjf.4}[ENCRYPTED PASSWORD]</Arg> <Arg type="java.lang.Integer" id="seed">811514</Arg> <Arg type="java.lang.Integer" id="keylenght">8</Arg> </Call> </Set> <Set name="minConnectionsPerPartition">5</Set> <Set name="maxConnectionsPerPartition">20</Set> <Set name="statementsCacheSize">100</Set> </New> </Arg> </New>
Note Take a backup of both files before editing.
Keywords: DLP Data Security Manager; Linux Analytics Engine; Risk Ranking Report; DLP Dashboard; DLP Console Not Working; Missing Data; SQL Connection |
Article Feedback
Want 24/7 Tech Support?
Learn more