Data collection job fails for requirements
We ae using CLM 4.0.4, RRDI 2.0.4 and WAS 8.0.0.3 Data collection job for CCM and QM works fine without any issues, but it fails everytime for RM.
================================================================ Kindly advice |
4 answers
Hello Amit,
to start troubleshooting the issue I would look for errors in the jts-etl.log log file. Best Regards, Francesco Chiossi |
Hello Amit,
HTTP 401, usually indicates that there's a problem with the user configured to run the data collection jobs. If you look at JTS Admin > Reports > Are these the same credentials that are used in the other applications that works fine (CCM/QM)? Best Regards, Francesco Chiossi Comments
Amit Garg
commented Mar 19 '14, 6:32 a.m.
Hi Fancesco, In JTS Admin > Reports > Data Collection Jobs, I see Oauth key and the password. CCM/QM are using different set of Oauth key and password which are not listed anywhere (not even in consumer inbound). When I compared the oauth key for jts with the keys in the consumer (inbound) section, it was using "Jazz reporting" oauth key and secret. So I removed this Jazz reporting entry, recreated it and provided etl_user as the functional user. Used the new key and secret with jts and now I'm able to run the jobs successfully. However I want to know, should it be a user ID and password instead of oauth key or vice-versa? |
Hello Amit,
both approaches are good. By default when you run the Setup, you get and user id and password if you specify the credentials for the data collector user, or otherwise an OAuth Key if you leave it blank. You can switch between one and the other by changing the following parameter: JTS Admin > Reports >
Best Regards, Francesco Chiossi |
I had the same issue with CCM and QM. I used "repotools-ccm -clean -addTables" and "repotools-qm -clean -addTables" commands and some missible columns etc were created. I used this aaproach with the help of IBM Support.
You might wanna try "repotools-jts -clean -addTables" command. That would help you. There's no side effect etc... |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Error we found in jts-etl.log file:
CRRRE1417E: The HTTP status '401' and the message is 'Unauthorized