Enabling event queue to avoid system load problems

[Former Member]

Hi,

We are having issues with the system load and as a result all trasnactions are running very slow in  the system after a acertain pint of time.

We were asked to “Switch on event queue” under Activation tab in T-code SWEQADM . and also set the parameters under the tab "Background Job ":

Currently I see the below values for the parameters in the system:

Operation Mode of Background Job -->Depending on load

Number of events per read access -->20

Time interval between two read accesses -->1  minutes

Interval until event queue next checked -->5 minutes

Can someone please recommend what values I need to change?

Also what are the diasvnatgages of enabling EVENT QUEUE?

[Jocelyn_Dart]

Hi,

Just remember that the Event Queue will only apply to event linkages that have been specifically enabled for the event queue (e.g. in transaction SWE2) regardless of whether the job is scheduled or not.

Regards,

Jocelyn

[anjan_paul]

Hi, 

Its depend on how many events raise within a specific time.

Whatever you mention is ok to me.

only I refer Time interval between two read accesses -->2  minutes.

[Former Member]

Thanks all for the inputs.

I was able to schedule the background job SWEQSRV via SWEQADM but now when I check in SM37,I see only one entry for this job with status FINISHED instead of all entries for the previous times the job has been executed in the system.

[former_member185167]

Hello,

Make sure you have selected all possible 'Job status' values in SM37.

Are you sure you need this? How many workflows are started per hour?

regards

Rick Bakker

[Former Member]

Yes,I have selected all status in SM37.

My problem is I see only one entry for the job in SM37 and not multiple instances like we see for any periodic job scheudled via SM36,

Not sure if this is because the job was started via SWEQADM.

[former_member185167]

Hello,

You could always do it yourself via SM36, run it as often as you want.

regards

Rick

[anjan_paul]

Hi,

  You can directly check the job from 'DISPLAY BACKGROUND JOB' button in background job in SWEQADM

[Former Member]

Thanks Anjan.

My query is why dont I see multiple entries for the job run in SM37 irrespective of how I go to see the job details?

Generally when we check the details for any backgorund job in SM36,for each run  of the job,there isa seperate entry in SM37 with the time when the job ran.

But for this particular job,in SM37,there is always only one record which updated with the last tiem when the job ran.

[anjan_paul]

Hi,

may be the multiple entry deleted by event queue program

[former_member583013]

The SWEQADM functionality actually only keeps one job and overwrites that one once the next instance is generated. It's not normal in terms of job scheduling but it's the way the event queue operates....

[suresh_subramanian2]

Hello !

       When large number of events are raised over a long period of time, it could cause high system load which in turn affect the system response time and performance.

      To prevent the system overload, event queue can be activated. But, doing so can delay the event delivery.

      You can have additional details at the second-half screen of "Activation" tab in SWEQADM transaction.

Regards,

S.Suresh     

[former_member185167]

Hello,

How many workflows are started per minute or hour at your site? You would need a very high volume for the event queue to be considered.

regards

Rick Bakker / hanabi technology

[Matheus_1994]

Hello,
Could you please give a feedback if the problem was solved and what did you do?

I'm facing the same problem, my parameters in SWEQADM are the same as yours.

Best Regards
Matheus

[Matheus_1994]

Hello,
Could you please give a feedback if the problem was solved and what did you do?

I'm facing the same problem, my parameters in SWEQADM are the same as yours.

Best Regards
Matheus