BPM outbound status?

[Former Member]

Hi all,

I am building on a simple scenario using BPM (S/A bridge). At first it was working fine, but after some test cases (also wrong), I canu2019t make it work again.

I always get the initial message stuck in queue XBQO$PE_WS90000001 with error u201CPermanent error in BPE inbound processingu201D. I delete then these queues manually. In SXMB_MONI I see error "Timeout condition of pipeline reached", and a lot of messages that have a green or red flag under Outbound status.

My questions are:

What exactly means the outbound status in BMP?

How to get rid of this green/red flags? Or they can stay there with no harm for next messages, but what else can be the reason for errors?

Thanx, Janos

[Former Member · Accepted solution]

Hi guys,

I have deleted all items with ERROR, READY and STARTED status from SWWL. Now it is working again,

Thanks a lot for the answers.

Anyway I can still see some old green outbound statuses in sxmb_moni.. so I suppose these flags are not problematic.

But I have one more question: In which cases I should go to SWWL to solve problems? I mean, is this a standard way, or it is a u201Cdirty wayu201D to be used only in emergency? (I donu2019t have any error handling implemented.)

Thanks, Janos

[former_member200962 · Accepted solution]

But I have one more question: In which cases I should go to SWWL to solve problems? I mean, is this a standard way, or 
it is a u201Cdirty wayu201D to be used only in emergency? (I donu2019t have any error handling implemented.)

It is the dirty way

Having an error handling is always beneficial...just think how much time consumption will be there in actual Production environment if such a thing happens

With error handling not only the BPM will remain unstuck but also the Support folks will come to know why and where the error occured.....my personal opinion and experience

Update:

You just need to delete the Error instance of the BPM from SWWL

Regards,

Abhishek.

Edited by: abhishek salvi on Jul 31, 2009 1:55 PM

[Former Member · Accepted solution]

Hi All

Even i had the same question ...This solution is feasible as long as we are in deveopment or testing environment...What if its in production and you get a error...

Lemme know if you find any way out ...

Cheers!!!

[prateek · Accepted solution]

Anyway I can still see some old green outbound statuses in sxmb_moni.. so I suppose these flags are not problematic.

That's may be because you still have some entries in smq2. Even if you couldn't find it, it won't interfere with the processing now.

+In which cases I should go to SWWL to solve problems? I mean, is this a standard way, or it is a u201Cdirty wayu201D to be used only in emergency?

It is neither of two. It cannot be said standard because deleting something manually could not be the ideal procedure for error resolution. It cannot be called as a dirty procedure as this is the only procedure to solve such situations.

Regards,

Prateek

[former_member200962]

At first it was working fine, but after some test cases (also wrong)

Does this mean:

1) You changed the BPM....then check the return code in SXI_CACHE

2) You used wrong test data to test the scenario....then if proper error handling is not implemented you will always get error in BPM processing....

Or they can stay there with no harm for next messages, but what else can be the reason for errors? 

The Queue will be blocked and the next messages will also get stuck in the Queue...you have to clear the queue before processing next set of messages

Reasons can be any one of the above mentioned

Regards,

Abhishek.

[prateek]

Outbound status for BPM here refers to the status of message after entering the Integration process.

You need to perform 2 things:

1. Delete all error entries from transaction SWWL.

2. Delete all stuck queues entries from smq2.

Then you need to run your scenarion again.

Regards,

Prateek

[former_member187339]

Hi,

Go to SWWL and delte the errored instance of the workflow and retest your interface.

Regards

Suraj