Skip to Content
avatar image
Former Member

Performance improvement of ccBPM process

Hi guys,

I have developed a BPM process which involves 6 systems and has circa 80 steps including 12 sync calls, some of them are in block repeated more times, so it is very complex. Unfortunately, it seems, when the sender system (BPM start message) sends many messages, the system goes down. Is there any way, how to improve the BPM?

I thought, that all the requests are queued and PI can never go down.

Is there any way how to reject sent message, when the system is overloaded?

Thanks in advance for help, Andrzej

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Jun 07, 2011 at 08:54 AM
    Add comment
    10|10000 characters needed characters exceeded

  • Jun 07, 2011 at 08:58 AM

    Hi,

    Perfroming 12 snc in one BPM (oh my god) not a good practice, the solution is you can divide your requirement in to multiple scenarios and try your luck.

    if spliting not possible then check below points

    1)Avoid using transfomation step in BPM and execute your operation mappings in interface determination step.

    2)Implement message packaging for your scenario.

    3)Define scope of container variables alsways within block (if you dont required them other block).

    Regards,

    Raj

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 07, 2011 at 10:40 AM
    I have developed a BPM process which involves 6 systems and has circa 80 steps including 12 sync calls, some of 
    them are in block repeated more times, so it is very complex.

    My first suggestion would be split the scenario....even with a good quality backend resources in PI the above BPM design will cause performance issues.

    Unfortunately, it seems, when the sender system (BPM start message) sends many messages, the system goes down. 
    Is there any way, how to improve the BPM?

    This probably means that multiple instances of BPM are created in PI and hence increase in load....Looking at your BPM steps there is only one solution.....ask the sender system to send messages after some gap of time....even if you implement standard procedures the system is bound to go down with such a heavy load.

    Add comment
    10|10000 characters needed characters exceeded

  • Jun 07, 2011 at 02:10 PM

    In addition to above suggestions, If you have single sender system with multiple messages arriving in a period of time, consider doing correlation pattern to avoid creating multiple instance of the process. This might help avoid system shut down during sending messages. But still your design is so complex to accomodate many things in one scenario which we dont recommend in CCBPM.

    Add comment
    10|10000 characters needed characters exceeded