Troubleshooting IDP Reporter Access
Problem
Table 1 provides tips for troubleshooting access to IDP Reporter and statistics collection.
Table 1: Troubleshooting: IDP Reporter
Symptom | Troubleshooting Steps |
|---|---|
Display errors. | In your browser, you must enable Java and JavaScript and allow pop-ups. |
Java heap space errors. | We recommend you set the JRE maximum heap space to 256 MB. If your heap space is between 128 MB and 256 MB, IDP Reporter can be launched but displays a message noting the recommended heap space. If the heap space is set to less than 128 MB, IDP Reporter cannot be launched. To set the Java heap space on a Windows client:
|
Certificate authority warnings | To eliminate certificate authority warnings:
|
IDP service is unreachable. | To restart the service:
|
Reports do not contain statistics. | Ensure you have enabled AVT and started Profiler. |
Use the idp.sh utility to ensure the IDP process is up and running. Restart if necessary | |
Review IDP Reporter log messages in the following locations:
If logs indicate IDP Reporter has stopped or is in a problematic state, restart it with the following command: [root@defaulthost admin]# /etc/inet.d/idprepservice
[start|stop|restart] | |
If data collection is functioning but you do not see expected statistics in particular reports, check your IDP Reporter filter settings. Try removing filters to validate statistics are generated for a particular report. Then reapply filters and verify the report data has changed to reflect the logic of the filter. |

