on 03-07-2010 4:27 PM
Hi,
Could someone throw more light on this statement from [Transactional Behavior of an Integration Process|http://help.sap.com/saphelp_nwpi71/helpdata/en/45/058023846b2460e10000000a1553f7/frameset.htm] -
> A transaction is a sequence of processing steps that are either fully executed, or not executed at all. If the system cannot fully execute a transaction, it rolls back all processing steps within the transaction. This means that the system can return to the state before the transaction was begun.
How is it relevant while designing a BPM scenario ?
Regards,
Sunil Chandra
Hi Sunil,
For example suppose you have a design in hand to create a sequential processing BPM for Material Master Creation in SAP and this process got some multiple steps.like.. Material Creation, Classification creation , Updating characterisitcs etc...
In real time ... suppose the BPM fails in the second step and the design ask you to have a restart from the the step where you BPM falied.Transactional Behavior of the BPM will help you to acheive this design.
Each process step can be represented by a block( logical seperation ) with Transactional Behavior checked.
Regards
Sunil.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Transactional Behavior of an Integration Process this is related to the availability of the Create New Transaction option in the respectives steps of the BPM....when you want to have a good performance out of your BPM avoid using this option.....some more information can be found in this document: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/200a4efc-f547-2a10-02bf-ada1d207d...
In the help link which you gave, if you check the sub-links (Send message Async/ Synchronously etc you will find what this option does).
Regards,
Abhishek.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Abhishek, but I already have gone through this link and some blogs on sdn. It is all about the transactional property of steps involved. I guess it is not directly relevant to the definition of transaction which discuss about roll back.
Regards,
Sunil Chandra
Edited by: sunil chandra on Mar 8, 2010 2:39 PM
Hi,
The concept is same as the commit and rollback strategy of the data base system.
The transaction says when we specify a bunch of activities say a block in BPM with a new transaction it should complete the whole process to commit or if there is any fail in between it shoul roll back to its previous state i.e until it had previously executed before the transaction started.
It has also something to do with memory allocation also.When a new transaction is assigned to a particular task or bunch of tasks, a chunk of memory is allocated for that transaction and it gets released once the transaction is over.
Its is very useful in case of critical steps and it guarantees consistency.
cheers,
Abhishek.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.