Currently we are implementing Advance reporting. We have installed and Jaspersoft, DWH and works fine locally.
We have the problem of “Page not found” when advance reporting is been invoked from CA PPM.
Below are our setups
Below is the page is displayed when we invoke the Advance reporting
Also the port on which the Jaspersoft running is not exposed through the Common URL[Used using the load balanced], but can be assessed internally using machine name and port [eg: http://ReportServer:9081/Report].
We also tested the Advance reporting using standalone CA PPM Service and and it works fine.
Appreciate if someone can help on this to resolve the Advance reporting.
What is your exact Clarity version? Is your HTTPS configured to be handled externally in your properties.xml (what is the value for sslType and enableSSLPort for the app) ? Does the Jaspersoft shows as Available when you go in CSA - Reporting tab?
Please let me know.
Nika HadzhikidiCA TechnologiesPrincipal Support Engineer
We are using Clarity 14.2. fix pack 5.
Page not found error is fixed by adding the below statement in the ModJK module of Apache2.0
JkMount /<JasperReport>* <worker>
HTTPS is configured using Apache 2.0 and load balanced using ModJK too hit the CA PPM app service on each server.
In Properties.xml file will have sslType="external" enableSSLPort="false"
Now I am getting a different issue. When the Advance Reporting is invoked the page looks scrambled and see the error in the application log as
com.niku.union.security.SecurityException: Could not retrieve Session from peristence.
Page scrambled issue got fixed as well. We used the connector port 8009 which was used by Jaspersoft connector port as well. Changed the CA PPM connector port. It worked
I'm very pleased to hear that changing the CA PPM connector port worked. As an FYI to you, we have comprehensive documentation about installing and configuring Advanced Reporting with Jaspersoft that is available here:
This is an additional resource that you may choose to reference, and it also contains troubleshooting information.
John W. George