Maintaining Tab Page Event Deliveries
Use
On this tab page you maintain how the event receivers are to be started.
A defined number of events is delivered by the background job in each cycle. These events can be processed sequentially or in parallel (with aRFC).
The receivers can be started synchronously (with RFC) or asynchronously (with tRFC).
Integration
This tab page is maintained within administration of the event queue.
Features
Features
Processing of events
Sequential
Events are delivered from the event queue in defined units (for example 5 events per read access). Sequential processing means that these events are processed in succession.
Parallel on server group
Events are delivered from the event queue in defined units (for example 5 events per read access). Parallel processing means that the events are processed at the same time in separate processes. These parallel processes can run using a defined server group.
Start of receivers
Synchronous
Various receivers (for example workflows) can be started for an event. Synchronous start of receivers means that they are started using a remote function call (RFC). The processing waits until the receiver call is complete.
Asynchronous
Various receivers (for example workflows) can be started for an event. Asynchronous start of receivers means that they are started using a transactional remote function call (tRFC). The processing does not wait until the receiver call is complete, but is continued immediately instead. The receivers are started asynchronously.
Activities
You can access administration of the event queue by choosing .

