clm2012 - RRDI setup / Load Cognos Archive issue
After downloading the archives files from JTS and CLM App (into installdir/cognos/deployment) and running the setup (https://localhost:10443/rrdi/setup) "Load Cognos Archive" the folder (Report Template, Reporting Data Models and Sample Report Definitions) are visibles in the public foders tab (Cognos).... but unfortunately they are empty.
Any help or idea would be greatly appreciated.
(Test environment : single server topology / Windows / DB2 / Tomcat for CCM-RM-QM / WAS 8.0 for RRDI) - CLM 4.0 RC5
Thanks
Any help or idea would be greatly appreciated.
(Test environment : single server topology / Windows / DB2 / Tomcat for CCM-RM-QM / WAS 8.0 for RRDI) - CLM 4.0 RC5
Thanks
3 answers
Where there any errors shown on the Setup page or in the log (C:\Program Files\IBM\RRDI\setup\logs\rrdi_setup.log)?
When you clicked the "Get Available Archives" button on the Load Archives page, did you see the right archives listed? There should have been one for the data model, and one for each CLM app that you downloaded.
Mike Fox
When you clicked the "Get Available Archives" button on the Load Archives page, did you see the right archives listed? There should have been one for the data model, and one for each CLM app that you downloaded.
Mike Fox
There was no error related to the loading in the log file. Just errors related to the connection to the JTS from previous initialization steps. It is the reason why I decided to rerun the setup from scratch.
I have submitted a defect, because when I start and stop the server the file jazzns_config is not updated correctly. I have to update this file manually. The oauth-key is wrong... (Nx32char) instead of 32. Maybe it is somewhere connected. I don't know....
I'm working on a test environment with a Window 7 64bits computer (OS not supported) and I use DB2 V10.1 which is not supported either but seems to work pretty well.
Thanks
I have submitted a defect, because when I start and stop the server the file jazzns_config is not updated correctly. I have to update this file manually. The oauth-key is wrong... (Nx32char) instead of 32. Maybe it is somewhere connected. I don't know....
I'm working on a test environment with a Window 7 64bits computer (OS not supported) and I use DB2 V10.1 which is not supported either but seems to work pretty well.
Thanks