Background Jobs in IFS Cloud with IFS Admin

  • 23 August 2021
  • 2 replies
  • 102 views
Technical Toby
Rank
Userlevel 5
Badge +14

It is not possible to use IFSADMIN as a User for setting up the Background processing when it comes to certain jobs. 


Missing rights are somewhat troublesome.

 

As you can see, it is not possible to switch a _SYS job to another queue if desired.

Missing _SYS functionality

Within IFS Germany, we have always setup a Queue for all types of Foundation Tasks to prevent them from blocking the default queue.

Now, this is no longer possible with only the IFSADMIN.

Either there should be a change of grants on this one or we have to live with it.

What do you think?

Never be afraid to ask!
This topic has been closed for comments

2 replies

durette
Rank
Userlevel 7
Badge +18

Are either of these work-arounds acceptable?

  • Create a new queue, then move your critical jobs to it that you don’t want blocked.
  • Increase the parallel degree for your default queue.
If you find this forum useful, please consider paying back to the community in your own areas of expertise. -- Kevin Durette - https://www.linkedin.com/in/kevindurette
Technical Toby
Rank
Userlevel 5
Badge +14

Hi @durette 

There is just no access for the IFSADMIN to the SYS objects and that makes it hard to handle the background processing properly without having the IFSAPP User.

 

And it does apply for a new queue as well. As the access for the objects themselves is not given.
Adding, that sometimes it makes sense to move background jobs from one queue to another or a new one. Not only increasing the processes for one queue.

Kind regards,
Tobias

Never be afraid to ask!
Terms & ConditionsCookie settings