Troubleshooting CABI JasperReports Server Integration

Symptom:
casp1042
Unified_CABI_Feature
Unified JasperSoft reports integrate successfully with 
DX NetOps Spectrum
, but shows no reports in the repository.
 
Symptom:
 
CABI and 
DX NetOps Spectrum
 integrates successfully, but then shows no reports in the repository.
 
Solution:
 
To avoid performance problems of the default values, add the following changes to the mySQL parameters:
  1. Change the mySQL configuration at \my.cnf (Linux) or my.ini / my-spectrum.cnf (Windows). 
  2. Search for “max_allowed_packet”.
    Before change : max_allowed_packet=1M
    After Change : max_allowed_packet=16M
  3. Save the file and re-start the mySQL server. Once it is up, perform the integration step, on the OC web administration page "Jasper integration" once more. Once it completes successfully, log into Jaspersoft and check for the reports.
For more information refer to CABI JasperReports Server and 
DX NetOps Spectrum
 integration related support article.
Clicking on the 'Name' link in JasperReports Server results in a Bad Request. 
 
Symptom: 
 
If 
DX NetOps Spectrum
 OneClick is in the https mode and the user cross launches 
DX NetOps Spectrum
 from JasperReports Server, that results in a bad request exception. 
 
Solution:
 
To avoid the bad request exception:
  1. Navigate to the Administrator > Report manager > Preferences page.
  2. Update the OneClick server entry to https.  
After updating the OneClick server entry to https, the bad request exception is not seen. Once the entries are updated, under 'Preferences' page, the values are saved in the registry table.