Best practice job queue

Hello,

What version are you running?

What do you mean by best practices?  As in, how to use JobQueueInfo?  Or with regards to creation of queues?

Trevor

Version 8.1.5

It's about configuration of queues.

The documentation covers this:

https://support.oneidentity.com/technical-documents/identity-manager/8.1.5/configuration-guide/45#TOPIC-1650991

And there's a KB that goes over this as well:

https://support.oneidentity.com/identity-manager/kb/295972/how-to-configure-job-server-queues

Hope this helps.

Trevor

It gave infos about parameters etc... but unfortunately, it does not give some advices about best practice to configure them following editor's recommandations.

As before, I don't understand what best practices you're looking for.  Sorry.

Trevor

As before, I don't understand what best practices you're looking for.  Sorry.

Trevor

Hi
I'd like to follow up.

Best practice means for example how many queues and how many jobservers makes sense.

In our case, we have created queues with names based on target system. i.e. ADS, AAD, SAP, SMTP, ...
That allows us, to stop specific provisioning or other interactions with outside. As example, we stop the SMPT Queue during upgrades, to be sure, that we don't send any unwanted emails generated by mistakes.
We have 12 Queues, but only 4 Jobservers.

The drawback of that solution is additional administration. Another open question is, what is the best way to deal with updates (dll, ...). So each queue is doning it on it's own which seems somehow to work, even if 4 queues have the same installation directory behind the one jobservice an that server.

Are there other ideas on that topic?
Best Pratices?

For some good info about queue configuration see this video by 1IM legend Herwig Abele
www.youtube.com/watch