cancel
Showing results for 
Search instead for 
Did you mean: 

Proxy to SOAP scenario

Former Member
0 Kudos

Hi Experts,

My scenarios is ABAP proxy to SOAP, it is synchronous scenario. we are sending 2 fields to the target system and we are getting the status field (value either 1 or 0).

In the SOAP we are configuring the webservice path,if suppose an error occur in between PI and webservice then we have to handle that error, how to handle? for this purpose we configure the fault message type. Here My question is is there any settings need for getting this fault message from the web service to PI ? (in PI we are giving the web service URL like that we have to give any thing)

To handle this only fault message or is there any alternative solution?

My second question is when we are getting the response at that time suppose some problem occur (Connection failure / ....) in between the PI and R/3, then we have to handle that error/exception and send that error to R/3 side guys, how to handle that?

Thanks & Regards

Ramesh

Accepted Solutions (1)

Accepted Solutions (1)

prateek
Active Contributor
0 Kudos

Talking specifically in terms of connection related alerts, you may raise them for all Adapter engine related errors. It is most of the time related to connection problems. This will give you some detail level alerts.

As Aamir said, CCMS is also not at all a bad option. But specifically for connection both could be used.

Regards,

Prateek

Former Member
0 Kudos

Thank you all,

According to the client requirement we can't use the CCBPM.

What are the possible errors we can expect in between the PI and R/3 systems (connection, messages struck in the queue,.........like that) and how to handle all those errors/exceptions. we have to send that error message to some members.

Ramesh

Former Member
0 Kudos

>>According to the client requirement we can't use the CCBPM

No body is asking you to use ccBPM:)

CCMS is used for monitoring and is able to cover all kinds of errors in SAP Landscape,you can specify receiver mail ID's in it who are notified in case of any error.

Thanks

Aamir

Answers (4)

Answers (4)

Former Member
0 Kudos

Thank you all

former_member200962
Active Contributor
0 Kudos
My scenarios is ABAP proxy to SOAP, it is synchronous scenario.

Since it is a Synchronous Scenario there is no need to go for a BPM........if there is an error you will get the notification then and there itself....let it be error in mapipng or an error in connecting with the End System......just configure an alert category in ALRTCATDEF....and add the recipients.....once done go to RWB and setup the Alert Definition in Alert Configuration.....give the sender NameSpace and other details if you want the alert configured for a particluar scenario....select if you want the alert for Inetgration Engine (mapping error etc) of for Adapter Engine (connection problem with end system)....and you are done...once the error occurs you will get the alert......one thing for sure no need of BPM...as you need....

Regards,

Abhishek.

Shabarish_Nair
Active Contributor
0 Kudos

>

> Hi Experts,

>

> My scenarios is ABAP proxy to SOAP, it is synchronous scenario. we are sending 2 fields to the target system and we are getting the status field (value either 1 or 0).

> In the SOAP we are configuring the webservice path,if suppose an error occur in between PI and webservice then we have to handle that error, how to handle? for this purpose we configure the fault message type. Here My question is is there any settings need for getting this fault message from the web service to PI ? (in PI we are giving the web service URL like that we have to give any thing)

> To handle this only fault message or is there any alternative solution?

>

fault messages is the right way to go

/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi

> My second question is when we are getting the response at that time suppose some problem occur (Connection failure / ....) in between the PI and R/3, then we have to handle that error/exception and send that error to R/3 side guys, how to handle that?

>

>

> Thanks & Regards

> Ramesh

configure alerts - /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step

The documentation-

http://help.sap.com/saphelp_nw04/helpdata/en/56/b46c3c8bb3d73ee10000000a114084/frameset.htm

Former Member
0 Kudos

Thank you prateek and vijay,

Suppose some problem (either connection / ...) occur in between the PI and R/3 system (at the time of getting the response) then we have to send mail to some people (means email alerts) about that error, how to handle means what is the alert category and how to configure that alerts.

Regards

Ramesh

Shabarish_Nair
Active Contributor
0 Kudos
http://help.sap.com/saphelp_nw04/helpdata/en/82/f1b14000eef20fe10000000a1550b0/content.htm

You can personalize the way in which you receive alerts.

Simply choose Personalization to make individual settings for your alert inbox. You can determine a substitute who will then receive the alerts. In addition, you can choose whether alerts are sent to you time-independently or time-dependently. The default setting is that alerts are sent time-independently to your alert inbox and via e-mail when they occur. You can additionally select the communication methods FAX and SMS for time-independent alert notification.

If you want to receive alerts only on certain days for a certain time, simply select the option for time-dependent sending of alerts and choose Create to create a new table entry. You can then choose the corresponding factory calendar, the time interval, and communication channel. Alerts that arise during this time frame will be sent in any case to your alert inbox. If you have also selected other communication channels, the alerts are additionally sent to you using these other channels.

Email is also a valid option when you configure alerts

some reference are:

/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide

/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step

Former Member
0 Kudos

Hey

Its better to configure CCMS here,

sometimes its possible that message get stuck in queue due to connectivity issues between XI and R/3 when you are using IDOC or Proxy.

since ALRTCATDEF can't handle errors in queue,you can configure CCMS to monitor the whole process.

Just search in SDN for blogs as to how to configure CCMS.

Thanks

Aamir

prateek
Active Contributor
0 Kudos

This should be of your interest.

/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi

To handle this only fault message or is there any alternative solution?

No other way except BPM.

when we are getting the response at that time suppose some problem occur (Connection failure / ....) in between the PI and R/3,

At that time error would be seen at R3 and not PI. R3 team should be able to notify further.

Regards,

Prateek