Why do some AAI Insight reports work but others do not?
Article ID: 254707
Updated On:
Products
Issue/Introduction
When running reports in AAI's Insight, some of the reports will load properly while others do not.
You may see errors in the Insight logs like:
Invalid URL. If you are using an IPv6 address, please ensure that the address is bounded by left and right brackets. Ex: jdbc:datadirect:driver://[xxxxxx]:50000;databaseName=DBNAME
Or:
ERROR ReportExecutionJob,quartzScheduler_Worker-1:366 - The report was not completed. An error occurred while executing it. (Error UID: dff064db-7f4f-4017-8f39-7c17166c6fe7)
com.jaspersoft.jasperserver.api.JSException: jsexception.error.creating.connection
Arguments:
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.JdbcDataSourceService.createConnection(JdbcDataSourceService.java:64)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.BaseJdbcDataSource.setReportParameterValues(BaseJdbcDataSource.java:49)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.JdbcDataSourceService.setReportParameterValues(JdbcDataSourceService.java:69)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.fillReport(EngineServiceImpl.java:1806)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportFill.runWithDataSource(EngineServiceImpl.java:1143)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportFill.runReport(EngineServiceImpl.java:1072)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportRunnable.run(EngineServiceImpl.java:967)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$SynchronousExecutor.execute(EngineServiceImpl.java:945)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.fillReport(EngineServiceImpl.java:651)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.executeReportUnitRequest(EngineServiceImpl.java:2068)
at com.jaspersoft.jasperserver.api.engine.jasperreports.domain.impl.ReportUnitRequest.execute(ReportUnitRequest.java:67)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.execute(EngineServiceImpl.java:529)
at sun.reflect.GeneratedMethodAccessor1150.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
Resolution
Insight uses two different method to pull report data from AAI.
- AAI database calls
- AAI API calls
The reports below use a direct connection from Insight to the AAI databases, if these reports are not working there is likely an issue with the Database configuration entered for the Reporting Server configuration or the port between the Insight server and the AAI database server is blocked.
You can test the connection in the Insight server's jasperserver-pro website directly, see this KB for how to do this: https://knowledge.broadcom.com/external/article?articleId=241188
If all connection details are correct and no ports are blocked, restart AAI and try to update the reporting server configuration again.
Database Reports
Trending Jobs Data Table
Job End Time Graph
Job Run History Graph
Job Run History Data Table
Jobstream Runs SLA Report
Jobstream Runs with Max SLA Report
Login History Ad Hoc View Report
The reports below use an API connection to the AAI server's API, these would be sensitive the FQDN's domain matching up, which was corrected via the hosts file.
API reports
Job Dependency Data Table
Batch Progress Report
Daily Batch Cycle Report
Jobstream Runs in Cycle
If the API reports are not working, but the Database reports are, verify the FQDN hostname is used in all configuration for the reporting server, and verify you are accessing AAI with the FQDN in the URL.
See this document for all places to verify the Domain Name in the FQDN match up: https://knowledge.broadcom.com/external/article/205564/aai-insight-not-showing-the-full-list-of.html
Feedback
