| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Error handling framework |
« View previous topic :: View next topic » |
| Author |
Message
|
| hongabonga |
 Posted: Wed Jan 11, 2012 11:55 pm Post subject: Error handling framework |
 |
|
Novice
Joined: 15 Feb 2011
Posts: 24
|
Hi Friends,
I did a quick search and did not find anything on this topic. So if you think it relates to some other posting already available, we can stop here and you can redirect me to the original post.
So my question is:
I have n number of legacy systems, which I want to integrate with SAP on the other end. I have chosen WMB to do it. So what could be a good approach to come up with a error handling framework in this situation.
One of my aquentances asked me this question couple of weeks back where my answer was somewhat like this:
I will have mapping table for errors with code, type, description, queue name. When I face an error condition, I will put the error message in a designated queue from where the error handling flow will pick up the message. It will look up the mapping table to find what to do with this error and route it accordingly. It can send mail or put it to some other queue or call a web service etc etc.
I am not sure if my answer was good enough becuase I found similar solution in my previous experience where one side had web app or mainframe and the other side had web service. This senario is different.
So I am posting it here with the hope that we can have a good discussion. So, friends, please join in.
 |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Thu Jan 12, 2012 12:15 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
There are a huge number of different error handling systems being used with Broker. Most are designed to fit in with the requirements of the given site/customer.
There is no general panacea when it comes to Error Handling.
The one you describe sounds pretty good for your site.
However you might need to look at how SAP returns the errors to Broker.
If you are using SAP via BAPI's then you need to interrogate the TReturn structures. Yes, they can be multiple TReturn structures.
If the bapi you call calls other bapi's internally, they will in my experience result in multiple TReturn structures being passed back to Broker.
you may need to filter the results based up the whole set of return values.
Then there is the case that SAP can lie to you about it actually being finished with the request you have made. If it says 'I'm done', it might not be. The 'I'm done' message might be saying that it has put your request on a queue/worklist internally. Then if the next update is also for the same order/customer/whatever you could get back an 'I'm busy' even though it has told you that it was done just moments earlier.
What I'm trying to say is, that by all meas use what you have got but you may have to add something to the error detection that is very SAP specific and which will allow the SAP stuff to work with the existing error handling system nicely.
Take your time. Don't rush. Do lots of experimentation and testing before your decide upon your solution. If you rush this, people running the system after you have moved onto pasteures new will curse you loudly!
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
