This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Only one execution slot is used by the SAP queue

hello,

even there are 10 slots defined for the SAP queue on the job server, SAP provisioning tasks are only using one single slot, preventing to run in parallel several SAP provisioning tasks.

We don't face the issue with either AD, Exchange or LDAP queues.

Any idea why we face this behavior and how to improve?

Regards,

Parents Reply
  • To avoid potential locking issues during the provisioning to SAP,  that could arise if two operations have to be executed against the same object in SAP (for example update operations against SAP user objects and SAP user parameter assignments lead to an update of the same SAP user object in SAP), many SAP provisioning steps are set to the task AdHocProjectionSingle. This leads to the described behavior.

    We are going to optimize the behavior in the next version of OneIM so that many of the provisioning tasks are able use the AdHocProjection task again.

Children
No Data