on 06-22-2010 7:07 AM
Hi all,
I am doing webservice to RFC (Synchronous) interface.
1.coould you please let me khow how many times PI can try to send information to and external system via a web service.
2.In case PI could not connect to the external system after N number of trials and PI sends alert or email informing about the failure, what would happen to the data, would it still be in PI or we will lose the information.
3.What should be done from external system perspective to retrieve the data into itself once it is up and ready to receive the data.
Thanks and Regards
Kishore
> 1.coould you please let me khow how many times PI can try to send information to and external system via a web service.
Just once.
> 2.In case PI could not connect to the external system after N number of trials and PI sends alert or email informing about the failure, what would happen to the data, would it still be in PI or we will lose the information.
No. The sender application of a sync message receives the error information and is responsible for error handling.
> 3.What should be done from external system perspective to retrieve the data into itself once it is up and ready to receive the data.
You can do nothing on receiver side. Just send the same message again from sender application.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Stephen,
Your reply was helpful.
however i need clarification onmy 2nd question.
2.In case PI could not connect to the external system after N number of trials and PI sends alert or email informing about the failure, what would happen to the data, would it still be in PI or we will lose the information.
No. The sender application of a sync message receives the error information and is responsible for error handling.
You mean, we cant get the data from PI and resend the same to external system through webservices?
Edited by: kishore kumar on Jun 22, 2010 10:06 AM
You mean, we cant get the data from PI and resend the same to external system through webservices?
The scenario will go into error since your receiver system was down.....XI/ PI will then and there send back an error to the sender (since SYNC) and the flow will be closed.
In case of error the message has to again be passed from source application.
This happens only when processing goes into error.....when success, PI is able to get data from target and send it back to the source.
Regards,
Abhishek.
Edited by: abhishek salvi on Jun 22, 2010 1:42 PM
Hi Abhishek,
Thanks for your reply. It seems i was wrongly explained my requirement.
It was my mistake,sorry for that.
here receiver is webservice and sender could be any system ( mostly proxy communication ).
1.in this case, how abt data reprocess from PI incase of failures when target webservice is not available.
2.please confirm, data wont be available in PI, to resend from PI to webservice, since this is sync communication.
3.Also please confirm how abt in async communication ( say for ex: proxy to webservice ) to handle data reprocess from PI in case of failures due to target webservice is not available.
> >2.In case PI could not connect to the external system after N number of trials and PI sends alert or email informing about the failure, what would happen to the data, would it still be in PI or we will lose the information.
> >No. The sender application of a sync message receives the error information and is responsible for error handling.
> You mean, we cant get the data from PI and resend the same to external system through webservices?
This is correct.
Edited by: Stefan Grube on Jun 22, 2010 10:24 AM
1.in this case, how abt data reprocess from PI incase of failures when target webservice is not available.
Only the request will be processed (in terms of mapping and sending to target)......then you will get an error which will indicate that something is wrong with target system and the call will close with a red mark in SXMB_MONI.
You have to resend the message from the sender.
2.please confirm, data wont be available in PI, to resend from PI to webservice, since this is sync communication.
It does not happen as the way you have mentioned......PI wont store the data and make a call again in case of error.
3.Also please confirm how abt in async communication ( say for ex: proxy to webservice ) to handle data reprocess from
PI in case of failures due to target webservice is not available.
One is increasing the number of retries of the target channel....this is documented in a blog (probably by Naveen)
Regards,
Abhishek.
Re opening the thread since i need the solution for the same scenario but for asynch case.
Hi Abhishek,
Scneario is Asynchrounous and it is SAP Proxy to webservice.
here in this case data will be persisted incase of any failures to webservice and we can resend the same to the webservice when it is available.
Please correct me if my understanding is correct.
Thanks
Kishore
Edited by: kishore kumar on Jun 25, 2010 11:18 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Kishore,
here in this case data will be persisted incase of any failures to webservice and we can resend the same to the webservice when it is available.
In case the web service is down, PI will try 3 times to post the message. After that, it will go into error. But this failed message can be resent from RWB.
Hope this answers your question.
Regards,
Neetesh
>
> In case the web service is down, PI will try 3 times to post the message. After that, it will go into error. But this failed message can be resent from RWB.
the amount of retries can be customized - /people/shabarish.vijayakumar/blog/2010/03/31/did-you-know--delivery-attempts-customizable-per-communication-channel
in anycase, even if it fails it can always be resend from RWB
also read;
How to ReProcess failed XI Messages Automatically - /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
7 | |
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.