Too many messages in monitoring

[Former Member]

My scenario is

FileSender -> BPM -> FileRecever && JDBCRecever

In Integration Engine monitoring I see 9 rows for 1 message!

1. FileSender -> BPM

2. FileSender -> BPM

3. BPM (Branched)

4. BPM -> FileRecever

5. BPM -> JDBCRecever

6. BPM -> FileSender (Acknowledgment)

7. FileRecever (no receiver)

8. JDBCRecever (no receiver)

9. FileRecever (no receiver)

Could you explain why are there 2 senders ( rows 1,2)

2 senders (rows 7,9) ?

Could you explain the existence of rows 7,8,9 without recever ?

[Former Member]

Hi Sergey,

<i>

> 1. FileSender -> BPM

> 2. FileSender -> BPM

> 3. BPM (Branched)</i>

You are using fork step rite???

As i understand your scenario is sending the same message to a file and database.Please correct me if am wrong.

In such a case, the message format should be different even if the same msg is gonna be send.Revert back for clarifications.

regards

Priyanka

[Former Member]

> You are using fork step rite???

I am not using fork. It is a simple BPM with only receiver and send step.

> As i understand your scenario is sending the same message to a file and database

Yes. I understand a branching. But Why are there 2 pair of senders(1,2 and 7,9) ?

[Former Member]

Maybe the problem is in correlation? Do I need a correlation for this BPM?