A couple of questions on the Cube Monitoring method of Job Execution with ReportWORQ and Planning Analytics

ReportWORQ
1

Hi,
We’re using Cube Monitoring to allow automatic execution of ReportWORQ jobs with PA and this is working successfully. Using ReportWORQ v 5.0.0.78
A couple of questions.
When ReportWORQ has no work to do it when it polls, it generates a record in the log file. Is there anyway to suppress this / is this expected?

We are using ReportWORQ as a piece of middleware with no direct interaction and so the account being used to connect to Planning Analytics is a “service” account with minimal rights. Besides access to the reporting cubes I have also given the account the following rights.

WRITE to the cube }ReportWORQ__Queued Jobs (suspect READ would be fine).
ADMIN to the dimension }ReportWORQ__Queued Job ID (so the job IDs can be deleted)
READ to the dimension }ReportWORQ__Queued Job Details

Everything seems to be working but I just wanted to check if there is a recommendation for other objects on the PA server when using the “Cube Monitoring” method?

TIA
Steve

2

@SteveRoweInfocat

We’ve made an update recently to improve some of the logging around cube monitoring; in our latest release, we’re no longer adding extra records around polling when no queued jobs are found.

Re: access to the }ReportWORQ_ objects, the current access you’ve set up is all that you need.

  • Justin
3

Great, thanks for the response Justin