Skip to Content
0
Nov 15, 2012 at 02:57 PM

ccBPM questions

57 Views

Hi,

i wanted to mitigate some particular doubt i have regading to ccBPM in PI 7.11
  • User desicion step: is there any SAP recommendation regarding the use if this step (performance,warning, etc), my doubt is because the availability of this step breaks the objective of ccBPM (system-centric)? --> any link/documentation?



  • BPE: lets assume a ccBPM that take about 3 hours to execute how does the engine acts? persist the process in memory and consuming work item so in the worst all work item will be taken or buffer the workflow (hibernate) ar DB without consuming resourcing of the server and wake it up when an event occurs for example the spected messege reachs? --> doc/link?



  • Parallelization of process execution: When is recommended to set it up,for ccBPM where correlation of message is not needed? where it must be configurated SWF_INB_CONF?



  • its not clear for me the concept of TRANSACTION BOUNDARIES, can anyone explain it with his own words?:

"You can specify for a block whether the block start or block end form transaction

boundaries:

• You can specify for the block start that the system starts a new transaction.

• For the block end you can specify that the system ends the currently started

transaction (COMMIT WORK). The system ends the transaction open at the current time, regardless of where it was started. If, for example, no new

  • Transaction Handling:

"A transaction is a sequence of processing steps that is either executed completely

or not at all. If a transaction cannot be executed completely, the system undoes

all processing steps within the transaction. This means that the condition before

the start of the transaction is restored."

is it traying to explain that if a IP fails at any step, the IP ROLLS BACK all the previous operation performed before the error? What about when the IP creates a flat file or perform a create/ update operation in a DB, etc??

Best Regards.

Rodrigo Pertierra

transaction was started at the start of the block, the last started transaction before this is continued.

With suitable settings for the start and end of a block you can expand the scope of transactions. This reduces the number of write accesses to the database, enabling you to improve performance."