on 08-05-2009 7:23 AM
Hi,
I have a "Proxy -> BPM -> File" scenario and have configured acknowledgment. When the data is sent from proxy and written to file without errors I get the correct acknowledgment back to the R3 system. But when the file can't be written (FTP cant be reached) then I get an error in the BPM step but get an Wait step in R3. "Still awaiting acknowledgment"
sxmb_moni in PI:
Processed successfully@ @Still awaiting acknowledgment @ 04.08.2009 14:47:18 14:47:18 @R3System
Processed successfully@ @Acknowledgment contains system errors @ 04.08.2009 14:47:19 14:47:19 @Integration Process
In SWWL I see this status:
Waiting for event 'SEND_OK_TRANSPORT' of object type 'CL_SWF_XI_MESSAGE'
Maybe it has something to do with the "Guaranteed delivery". It retries 4 times and maybe it is waiting for an retry limit or something. I am not sure.
Any ideas on this one?
HI,
File Adapter tries to connect to FTP 3 times and after that it declare the message as System Error and which in turn should send negative acknowledgement , if BPM is configured properly for Acknowledgement in Send Step ( use Transport Acknowledgement) . And don't forget to define a Deadline branch apart from Exception Handling which will terminate the BPM running on server after limited retries.
I hope it helps you to some extent.
Regards,
Anurag Garg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Shouldn't this be a "Acknowledgment contains system errors" ?
Are you implementing any logic once the deadline is met?
To send the NACK to R3 you need to have a Send step in your Exception/ deadline branch which will send the required message to R3.
A similar approach is shown here: /people/michal.krawczyk2/blog/2006/06/22/xi-playing-with-the-file-adapters-acknowledgments
Instead of the Control Step you need to have a Send Step.
Update:
Please note that any acknowledgement from AE will come into the BPM and will not go directly/ automatically to R3. The meaning of acknowledgement coming back to the Sender Application means ACK/ NACK to the BPM and not any other system.
Regards,
Abhishek.
Edited by: abhishek salvi on Aug 5, 2009 2:48 PM
Hi,
How should I design the BPM. My bpm is like this:
Receive step -> Block (starts, Exceptions=SendError) -> SendStep (acknowledgment=transport) -> Deadlinebranch (reference=creating new step, inside is a control step - action=Throw Exception, Exception=SendError) -> Exception Branch (exception handler=SendError) -> Block (ends) -> Stop
Now in deadline I said 1 minute. after that the process is cancelled and I get a Positive Ack. back to R3. But I need a negative one.
By Default your receiver CC will try for 3 times at an interval of 5 mins each
So a deadline of 1 min may not help.....just think what you will do if the retry succeeds in the third attempt i.e. after 10 mins...or does not succeed at all
Have an Exception branch and then in that branch include a Send Step....this Send step should contain the failure message.
You can check the approach as mentioned in the blog which I gave in previous reply.
after that the process is cancelled and I get a Positive Ack
Yes you will get a Positive ACK only...since the process has completed and has not gone into an error state.
Regards,
Abhishek.
configure exception handling / deadline in BPM and send related error message back as ack.
Edited by: NetWeaver Expert on Aug 5, 2009 8:47 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.