Data Collection Job Status fails

Hi, Benjamin,

I recently reconfigured our CLM to use Active directory. After I reconfigured data collection jobs, only QM common jobs won't run. What is so special about QM common job? Any hint on where I should look for troubles? Thanks.

I too have had all sorts of issues trying to understand data collection, the licensing and users who run the collection jobs, and authentication settings. Whenever I have gone to the advanced settings, I see that the ADMIN is still the default user used for many of these jobs, even when the user ADMIN has been disabled during the CLM setup process.

This would be a great subject for a library article. Would love someone from the Jazz team to put together a note on what the settings should be and how they work. Things like the user and roles on the server and/or projects, the authentication methods and what they should be, and how this should look when stand alone and with RRDI.

Additionally, I would love the set up process to make any changes necessary - we specify an ETL user account during set up but the disabled ADMIN username is still dotted everywhere in the data collection advanced settings. I can't work out if this is even important or not, or if the data collection jobs are still working.

Yes, they'll run automatically at midnight every night.  You can check the job status some time after midnight to confirm they've executed.  The account that it uses is the one you have set up under Reports -> Data Collection Jobs, which I believe you said is your account for now.  You may want to create a functional user (ie - ETLUSER) and assign it the data collector license as to not interfere with the ETL (ie - you change your password, then the ETL's will start failing). 

Yes, you only need one Data Collector license since you only need one functional ETL user on the server.  These jobs run by default at midnight, so the users should find that reports are updated with the latest data on the following day without you having to run them manually.

You can re-configure the time they run by entering an integer value under Reports -> Data Warehouse Connection -> Data Warehouse Snapshot Time, but midnight (off hours) is best (as it does put some stress on the applications), unless you have some scheduled maintenance that you know will interfere with the job (ie - database goes down at midnight for some maintenance task).

I'm glad the jobs are running now!

You should be able to update the User ID/password on that page to reflect the user who has the Data Collector license.  Are you not able to modify the values?

I'm using 4.0 and the screenshot I showed is the default.  Is your XDC Authentication type set to "oauth" instead of "FORM"?  You can check under Reports -> Data Warehouse Connection -> XDC Authentication, or under jts/admin -> Server -> Advanced Properties -> XDC Authentication.  I'd try changing it to FORM and specifying the username/password for your ETL user, as using a consumer key/secret is not the default configuration. 

Sure, you can email it to me at bsilverm<at>us<dot>ibm<dot>com.  Or I can attach a screenshot of mine here if it helps:

If you go to https://<server>:<port>/jts/admin -> Reports -> Data Collection Jobs, you'll see each job listed for the JTS/RM applications, and there is a "User ID" field that indicates the user configured to run the ETL.  Again, you'll have to update this under each admin page (ie - qm/admin -> Reports -> Data Collection Jobs, ccm/admin -> Reports -> Data Collection Jobs) for the change to be made for each application.

That might be the problem.  The ETL is configured to run with a certain user if you go to https://<server>:<port>/jts/admin -> Reports -> Data Collection Jobs, and check the "User ID" who is running them.  That user is created during jts/setup, so if you've attached the Data Collector license to any other user, you'll need to change the user that runs the ETL to make sure it's the user that has that license.  You'll need to do that for each application. 

Does the user that is configured to run ETL have the "Data Collector" license?  Is that the same exception you see in the jts-etl.log, or is there more info there?  That might explain why only the STAR job works, as this data is collected from the data in the database rather than from the applications,