Jazz reporting service: error loading imported ready-to-use reports

I cannot figure out from the error log contents (above) what actually failed during the import. There were multiple authentication expired token errors but I think that is normal when you first connect to JRS.

There were also 2 SPARQL syntax errors trying to update a data source,

com.hp.hpl.jena.query.QueryParseException: Encountered " <string_literal2> "\"false\" "" at line 43, column 121.

but when I examined the stack trace this looks like the request was from the UI and not the import mechanism. I did not see any other errors in the log contents that would indicate an error during import of the OOTB reports.

As for building a new report, when you open the “Build” page and select a data source, the section where you select the data source should also list all of the types (work Items, test cases, requirements, etc.) available for that data source. You have to select one type before the Continue button is enabled.

If none of the types are shown for a data warehouse, then there was a problem during initialization of that data source. Do the following:

1) Shutdown the JRS server

2) Delete the JRS log file (.../server/logs/rs.log if using Tomcat)

3) Restart JRS and try to Build the report again.

4) If no types are shown, go to the data sources page and select the data warehouse link to edit that data source.

5) Click Save. This will cause the meta-model data to be refreshed, unless an error occurs.

6) If the types still do not show when building a report, copy the rs.log file and attach it to this thread.

So I figured out the SPARQL syntax error exception in the log ... When you specified the database schema and clicked Save, an invalid SPARQL update command was generated internally in JRS when saving the data source resource. I'll fix that but it should not affect you. That database schema field of a data source is not needed unless you are using an old version of an ORACLE database. Some databases did not support separate databases for different applications. So all of the tables and views for a single application (e.g., the CLM data warehouse) had to add a schema prefix to their table names in order to avoid collisions with tables from other applications.

DB2 creates separate databases so a schema prefix must not be defined.

I noticed on the Build Report page, none of the types were listed for the data warehouse. When you defined the connection to the data warehouse you specified a user name and password. In my testing I usually use the DB2 administrator but if you specify a different user, you MUST define the permissions in DB2 so that the user has read access to all of the tables and views. I think this may be your problem.

After you ensure your DB2 user has read permissions, in JRS open the DW data source and simply click Save. This will refresh the metamodel in JRS. On the Build Report page, you should see the types listed for Change Management, Quality Management and Requirements Management.