Hello Scott,
the section "Copy the required files to CA Business Intelligence JasperReports Server" in the official installation docs is a bit misleading. In fact it is too difficult to execute correctly (and check)
a) the, mistake proven, reality is that the right keystore was not located in \CA\Identity Manager\IAM Suite\Identity Manager\tools\JasperKeyGen\keystore\ but under the JBOSS (Wildfly) installaction (JBOSS_HOME/modules/com/ca/iam/cajasper/main/iam.jks ). I was working with 14.3 vApp version and the iam.jkse in JasperKeyGen and the one deployed in wildfly were different. This lead to failed authentication between Jasper server and vApp.
Maybe the difference was caused by some "after the installation" run of the keygen, but I have waisted a few hours trying to figure it out.
So the installation doc should rather speficy the "used keystore" location as the copy source or at least provide some guidance on the failed authentication. With a hindsight, when I read the documentation for about fitht time, I see the correct path, but it is not quite clear. The steps should be much clearer like this
1. Generate a new keystore
2. Copy the new keystore to IDM Jboss/WL/WAS deployment
3. Copy the same keystore to JasperReportServer
4. Restart both IDM and JasperReportServer
Then there are other reporting installation traps along the way
b) based on my trial and error, I found that the whole OOTB reporting is not assuming split database schemas. In the production setup we separate objecstore/reporting (snapshots) and audit into separate databases. However the OOTB reports simply assume that everything is in one heap and auditing based reports fail. So far I have found the only way to make them work was to change them one by one in reporting and assign them a different JNDI data source.
It would be nice to document this in the installation document and provide if not an OOTB solution, then at least manual DYI list of steps and reports that need to be fixed.
c) the "report server configuration" task is not well documented. In particualar the "proxy" connection option should be explained better - when to use it and what does it mean.
d) last but not least comment to the installlation document is that it copletely lacks a simple to execute verification scenario. Because use of the reporting (especially if you are using split databases) is more likely to fail than to work and it is very peculiar to having many configurations right it turned out to be quite difficult to run at least one, really dummy, report that would verify that the technical setup is working. With the OOTB installation it can be wrong keystore, wrong datasource (in JR or IDM), missing data snapshot, wrong JRS setup, wrong report import, etc. And since the output I got first was a blank page it was very difficult to figure out where was the problem.
Tomáš Fencl
KonzultantCATTA Consulting s.r.o.Na Dolinách 1067/42, Praha 4, 147 00, CZMobil: + 420 602 280 407E-mail: tfencl@catta.cz