COMMIT WORK AND WAIT handling within Gateway changesets

[woutdejong]

method /IWBEP/IF_MGW_APPL_SRV_RUNTIME~CHANGESET_END.

     commit work and wait. 
"wait required because of no tolerance of delay in update task

  endmethod.

Experts,

Can we somewhere configure or customize in SAP NW Gateway the behavior of COMMITs (transaction handling)?

We have a requirement that we MUST wait for the update task to release the locks on SAP objects. We now have implemented the CHANGESET_END method (see above), but wondered if there is a generic switch or piece of customizing that deals with this.

[woutdejong]

Sorry Andre for taking 2 months to respond... Still, thank you anyway.

Indeed we are required to wait for as long as it takes to commit the changes to the db (and also release the locks). Just that I generally regard explicit COMMITs as smelly code, especially if an encapsulating framework (like GW, or the soap runtime) takes care of this.

BTW, we now always put the COMMIT WORK AND WAIT in the CHANGESET_END method, as we have seen too many times that UI5 (1.38) issues a MERGE entity and GET entity request in 1 $batch (fortunately in that order) that resulted in the old, previous value being returned instead of the updated value from the MERGE.

Cheers, Wout

[srg]

This UI5 behavior is the consequence of the ODataModel configuration in UI5.
It is easy to change this.

Regards,

Stefan