| Author |
Message
|
| pc.verhey |
 Posted: Tue Sep 13, 2005 11:56 pm Post subject: recovery message when mysap adapter fails |
 |
|
Newbie
Joined: 13 Sep 2005
Posts: 6
|
In our company we build an interface where
1. The broker sends a message, and the adapter makes an IDOC
of it.
2. The broker sends a message, and the adapter makes an BAPI of it
3. SAP sends an IDOC
We have all that working, but what happens when a message goes
wrong in the adapter, can we recover it.
In a ideal world we want to take the message that went wrong and put it a second time on an input queue of thee adapter.
This is important for us, because it is forbidden to louse messages.
So does somenone knows the answer? |
|
| Back to top |
|
 |
| djeripo |
| Posted: Wed Sep 14, 2005 7:30 am Post subject: |
|
|
Master
Joined: 25 Jan 2004
Posts: 225
|
What do you mean by 'Message went wrong'? Could you elaborate.
If at all your event did not pass through the flow,You can always re-submit the same event using 'Flow Manager'. |
|
| Back to top |
|
|
| pc.verhey |
| Posted: Thu Sep 15, 2005 1:12 am Post subject: |
|
|
Newbie
Joined: 13 Sep 2005
Posts: 6
|
I make a litle design
mes means message
customer-->mes-->broker--->mes--->adapter---IDOC/BAPI---SAP
Someone makes a mistake and the the adapter says I don't like
the mesage (for instance no XSD files) so the 'error' is in the adapter.
How can I recover it when the customer says I can't sent the message a second time. |
|
| Back to top |
|
|
| djeripo |
| Posted: Mon Sep 19, 2005 1:36 pm Post subject: |
|
|
Master
Joined: 25 Jan 2004
Posts: 225
|
I am not sure How SAP Adapter works.I am sure it would be pretty much similar to JDBC/JText where you have Archive,Output and Event tables/Directories.
If for some reason , JText connector picks up a bad message from the Event directory,It archives in the archive directory with .fail extension.
Broker failed to process message because ,There was a problem with the message.In the middleware terms,Adapter should not re-work on the bad message and convert it into the good message so that it would be picked again.Its the responsibilty of the sending application(customer) to send a good message. |
|
| Back to top |
|
|
| recallsunny |
| Posted: Wed Sep 21, 2005 12:17 pm Post subject: |
|
|
Disciple
Joined: 15 Jun 2005
Posts: 163
Location: Massachusetts
|
The one good thing about Adapters is they use a common framework, hence what is true for one adapter behaviour applies to the rest...
Since you've configured your adapter with BrokerType as WMQI, it forces the DeliveryType to JMS... which is good!!
| Quote: |
| If connector framework cannot deliver the business object to the WebSphere InterChange Server-integration broker, then the object is placed on a FaultQueue. |
This is the default behaviour if a JMS delivery transport is used, and applies for SAP adapter too.
The rest is simple, either you can have a message flow pick up these fault BO's and log them or have a triggering setup for FaultQueue, to call a batch script to handle this...  |
|
| Back to top |
|
|
| pc.verhey |
| Posted: Fri Sep 23, 2005 3:50 am Post subject: |
|
|
Newbie
Joined: 13 Sep 2005
Posts: 6
|
If connector framework cannot deliver the business object to the WebSphere InterChange Server-integration broker, then the object is placed on a FaultQueue.
oke that is the way from the framework to the adapter. But what happens
the other way around?
If the broker delivers a message to the framework, and the framework cannot deliver the business object to the applicaton then the object is placed on............
somthing like this happens for instance when someone make a mistake
with the configuration of the framework and the framework doesn´t recognize the message. You can of course say the businessystem should send the message again but that is not always posible. |
|
| Back to top |
|
|
|
|
