Visibility API is a "connector" application that delivers data from ACR to Insight. Primarily this feature is utilized to view ACR output within Insight dashboards.
Visibility API is available for all platforms where ACR is hosted. The installer is located within the "client" section of the download page. At the time of this article's publication, v9.3 is the latest release and may be found within the following link :
If a working setup of Visibility API suddenly stops sending data from ACR to Insight, the following steps should be taken to troubleshoot :
1 ) Review ACR's SYSOUT
This will allow the team to confirm if the issue is simply stemming from the Job itself. When an ACR job hit's an ABEND, or if the JCL is not defined correctly to send information through Visibility API, the SYSOUT will detail why this occurred. Additional details on reading a SYSOUT may be found within the following article :
2 ) Review Visibility API's logging
If the ACR SYSOUT review does not turn up a lead, the information may have been successfully sent to Visibility API and hit an issue within that step's processing. Many times when an issue is hit within this piece, the issue is stemming from a communication issue with the Insight server itself. More information on Visibility API logging may be found within the following article :
3 ) Review Insight's logging
If both the ACR SYSOUT and Visibility API logs do not return an ERROR or provide a tangible lead, the Insight logging will be the next point of review.
- "igx.log" ( located within Insight's <install_home>/logs directory )
- "server.log" ( Wildfly setup, located within Insight's <install_home>/wildfly/<jvm>/log directory
- "systemout.log" ( WebSphere setup, provided by team's WebSphere admin )
Alternatively the above logs may be gathered by generating a diagnostic support package from Insight