Soap to proxy : sync scenario

Hi
Have a new PI 7.1 system , wanted to do a soap to proxy sync scenario
Do i need to create business system for proxies or if I just create 2 business services: one for sender and other for reciever ,it would suffice?
Is there any advantage / dsiadvantage if I use Business service instead of Business systems?
In SLD if I just create a product /swcv : it should be good if I want to use Business service mechanism instead of Business syste, ? or is creating Technical system and Business system mandatory even if I have to configure scnearios using Business service
Thnx

Business Systems require technical systems/software components and products, from an organisational perspective in PI it might be a good idea to define these things for an external entity (Business System). As far as Im aware business Services do not have that same requirment.
I tend to limit business service usage to one off or simple interaction B2B, as soon as you have more than one adapter interacting with the same external entity a business system with all of "their" adapters will help keep things clear to other people configuring integration scenario's. Whilst smart naming standard will get you around this most of the time, it makes more sense to put them together under the one system.
Hope this helps.

Similar Messages

SOAP to RFC - Sync Scenario. How to find where the response is going to?

Hello All
I have a SOAP to RFC sync scenario.
In SXMB_MONI, i see that both the initial message and the response message are successfully processed.
But, the SOAP sender is not receiving the response message.
How can i trouble shoot this scenario? How can i findout what is going wrong?
Most importantly, How can i find out the web address of the SOAP sender? I do not see it anywhere.
Thanks

Hi Chandra,
Please check this blog.
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
You can by pass your message through a TCPIP gateway , this will help you to see the message contnet and the SOAP header information.
TCPIPGW application is availabel in one of the SAP notes for Monitoring SOAP adapter. and 2 SAP SDN PI blogs are also there on how to use this application...
Regards
Sunil.

SOAP to Proxy synchronous scenario

Hi,
Hope you are all doing well.
I have a SOAP to Proxy synchronous scenario. As part of this scenario, the data structure of the response sent by SAP is different from the response sent back to the SOAP requester. Hence I have used request message mapping between the SOAP request sent by requester and the one passed on to SAP and response message mapping between the response sent by SAP and the one passed on to the requester. Both the message mappings are incorporated in a single Interface mapping.
The problem is that the interface is behaving like a asynchronous one, i.e., request is passing over to SAP but though the proxy is giving a response back, the same is not coming over to XI.
It would be really helpful if you can let me know what might have gone wrong.
regards
Debansu

Hi,
you should have that:
1. Two Message Mapping:
1.1. a Message Mapping for request    (called MM_request)    , from MT_SOAP_request     to   MT_Proxy_request.
1.2. a Message Mapping for response (called MM_response) , from MT_Proxy_response   to   MT_SOAP_response.
2. One Operation Mapping (in PI 7.1) or Interface Mapping (in PI 7.0) from SI_SOAP to SI_ Proxy with:
2.1 in the tab "request", so from MT_SOAP_request     to   MT_Proxy_request    , give your Message Mapping "MM_request".
2.2 in tab "response"   , so from MT_Proxy_response   to   MT_SOAP_response, give your Message Mapping "MM_response".
3. In you Directory, you define a flow like that:
from SI_SOAP to SI_ Proxy by using your Operation Mapping.
If I missed nothing, that's all.
MT = Message Type
MM = Message Mapping
SI =Service Interface in PI 7.1 or Message Interface in PI 7.0.
regards.
Mickael
Edited by: Mickael Huchet on Oct 19, 2011 4:07 PM

SOAP - XI- PROXY synchronous scenario

Hi Experts,
I have a
SOAP -
XI -
PROXY Synchronous Scenario
I have done the following things ESR and ID
ESR:
1. Created DT and respective MT for Request and Response.
2. Created Service Interfaces with Synchronous mode with respective MT's.
3. Created Two separate MM with respective Request and Response MT's.
4. Created Operation Mapping and call both Request and Response Mappings in it.
Integration Directory (ID):
1. Configured considering Sender SOAP and Receiver ECC Services.
2. Configured CC with required parameters in Sender SOAP CC and Receiver XI CC.
3. Generate wsdl from Sender agreement and save it as a local file.
I am getting error in receiver agreement. Do I need to specify any Module parameters in Module TAB for Sender CC or Receiver CC to synchronous scenario.
Please hep me out.
Thanks

Hi Ram,
I am getting error in receiver agreement. Do I need to specify any Module parameters in Module TAB for Sender CC or Receiver CC to synchronous scenario.
It looks like you did not create a receiver agreement, or if you did, it did not match the interface that is given or configured in Interface Determination. Can you recheck your configuration?
Regards,
Mark

SOAP to RFC sync scenario

Hello members:
we have a business scenario: SOAP to RFC sync
an external system (ABC) sends documentrequest thru XI SOAP adapter and makes an RFC call to a BAPI and gets back the resposne to the ABC system.we are handling 4 mappings. 1. request msg to a common msg 2. common msg to BAPI request3.bapi response to common msg 4. common msg to response msg(which is same as the req msg)
i have the request msg and common msg as external definitions. I did the following steps and wanted to
know if i am right.
1. there are no data type & msg type needed for this
2. 4 msg interfaces
i) document o/b sysnc
ii) document i/b sync
iii)common o/b sync
iiii) common i/b sync
3) 4 mappings
i) document to common
ii) common to bapi req
iii) bapi resp to common
iiii) common to req/response
4) 3 intf mappings
source intf**********               target intf
i)document o/b               common o/b uses mapping #1
ii)request :common i/b         bapi i/b uses mapping #2
   resposne:bapi i/b           common i/b uses mapping #3
iii) common i/b             document i/b uses mapping # 4
pls provide your inputs if my approach is rite? do i need to have 4 msg intefaces?has any made mappings where 4 mappings are involved ( without BPM)
Thanks in advance

Hi,
I think you will have only 2 interfaces.
1. Sync Outbound interface (SOAP Structure)
    Two message types Req and Res
2. Sync Inbound interface (RFC Structure)
    Two message types Req and Res
Then two message mapping
1. SOAP Request to RFC Request
2. RFC Response to SOAP Response
and finally one Interface mapping.
Thanks,
Prakash

ABAP Proxy Sync scenario with error No Implementing class registered error

I am working in a ABAP proxy to Proxy scenario. The connectivity is between SEM and PI systems(SEM->PI->SEM). Outbound synchronus interface is used to create proxy (Client Proxy) its a SAP standard interface. This scenario is configured as below,
1) Sender and receiver business system is the same for SEM with same client.
2) No Message and Interface mapping is used.
Please let me know, if the configuration is correct. if then, how to solve this error?
Regards,
User PI.

>>The connectivity is between SEM and PI systems(SEM->PI->SEM).
SEM->PI->SEM makes no sense. Why do you need PI here?
Any way, the error message implies the server proxy is not implemented (or activated) correctly.

IDOC to Soap Webservice (Async/Sync scenario)

is any can provide somesteps please

Refer this thread
Synchronous IDoc -> SOAP scenario
Regards
Aashish Sinha
PS : reward points if helpful

Dynamic receiver Determination for Sync Scenario??

Hello Experts,
I have a SOAP -> Xi -> R3 sync scenario i,e, R3 to send back response to SOAP client.
Also I need the Dynamic receiver determination.
When I try to create the Interface Mapping, I get the error:
"Interface modi are different. "
Source interface MI_My_sync_iface is synchronous.
Target interface ReceiverDetermination | http://sap.com/xi/XI/System is asynchronous
I coud find few threads on forum related to this but i think there is no clear solution provided.
I do not wanna use BPM.
Please suggest.
Thanks in Advance!
Appropriate point will be awarded.

> So when I try to define a interface Mapping using a Sync interface as Source and Async interface as target, XI does not allow me to do so.
You are getting this error because in Interface mapping when you use sync source then it generates request and response tab so if at target side if you put anync interface then definetly it will go into error. You have to make both the interfaces as sync.
BTW, after getting the message in R3, how are processing the message? Are you using sync proxy??
You can solve the problem by creating one additional message interface of type inbound-asyn. Use this additional Message interfce in your Interface Determination. And create additional Receiver Agreement to deliver the message to it's destination.
Note: When you careate additional Interface Determination then you have to chose the response message interface (Sync message interface which returns the response from R3) as a source.
Regards,
Sarvesh

SOAP to Proxy error PI 7.1

Hi Experts
Working on the SOAP to Proxy scenario, XML message is coming, I am transforming the message from xml into HTML by using the XSLT mapping
I receive the following errror while testing, Can anyone tell how to trace the error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Thanks
PR

Hi,
Please have a look at the following links and see if it helps
Exception handling Proxy to SOAP
SOAP to Proxy test scenario 7.1 PI
How To Debug XML Serialization Error With Deployable Proxy
Best Regards

No mapping logic : soap to proxy scenario

Hi,
I have a soap to proxy scneario with no mapping logic.wanted to confirm certain things.
Wanted to confirm certain things.
1) So i can exclude mapping and interface mapping step since i just need to pass value to proxy ?
2) in interface determination ,what i need to provide for interface mapping ?
3) sync proxy will be generated from one outbound message interface "( there will be only one outbound message interface which will be synchronous : which will be synchronous ?
4) in receiver business system , i need not put any message interface since we only have one outbound sync message interface
Thnx

how many message interfaces wil be needed for synchronous scneario without mapping ?
Two....one for Sender (Outbound) and one for receiver (Inbound)
in case ur answer is 2 for above ? proxy needs to be generated from outbound or inbound interface?
For your SOAP --> XI/ PI --> PROXY, scenario the proxy should be generated for the inbound interface
1) So i can exclude mapping and interface mapping step since i just need to pass value to proxy ?
If both the source and target structures are the same , then you do not need to perform mapping....do not create message and Interface mapping .....you should however create Interface Determination with appropriate Source and Target interfaces.
2) in interface determination ,what i need to provide for interface mapping ?
Nothing.....including a mapping is not mandatory.
4) in receiver business system , i need not put any message interface since we only have one outbound sync message
interface
The message interface needs to be associated with the Business System.....it will be the inbound interface for SOAP --> XI --> PROXY scenario.
Regards,
Abhishek.

SOAP to Proxy scenario communication error

Hi Friends,
 Now i am developing SOAP to Proxy scenario, i am testing WSDL file using SOAP UI software and i am getting an error in SOAP UI tool.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Error Report</title>
<style>
td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;}
A:link {color : #0059AA;}
A:visited {color : #999999;}
A:active {color : #999999;}
</style>
</head>
<body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0">
<table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75">
<tr bgcolor="#FFFFFF">
<td align="left" colspan="2" height="48"> 403 Forbidden</td>
</tr>
<tr bgcolor="#3F73A3">
<td height="23" width="84"><img width=1 height=1 border=0 alt=""></td>
<td height="23"><img width=1 height=1 border=0 alt=""></td>
<td align="right" height="23">SAP NetWeaver Application Server </td>
</tr>
<tr bgcolor="#9DCDFD">
<td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td>
</tr>
</table>
 
 Error: You are not authorized to view the requested resource.
 <a href="https://wiki.sdn.sap.com/wiki/x/wIN3Cw">SAP Technology Troubleshooting Guide</a>
<table>
<tr>
<td valign="top"> Details:</td>
<td valign="top"><PRE>No details available.</PRE></td>
</tr>
</table>
</body>
</html>
I have tried with the same WSDL earlier it was working fine, now its not working and throwing the above error.
Kindly suggest me to overcome from this issue.
Regards,
Senthil.

Hi Senthil,
Try with the authentication preemtive. Also, check your URL because that error seems that you are accessing to wrong PI section or your user has not the enough credentials, try with PIAPPLUSER or with the same roles that this user.
Regards.

Soap to proxy scenario Getting exception caught with cause error

Hi Experts,
MY scenario is soap to proxy i am getting below exception message in advanced engine configuration in ICO.
OAP: request message entering the adapter with user J2EE_GUEST
09/10/2014 11: 06: 03 346 XI Information Packaging (Bulk Mode) is not Enabled, Proceeding to the Normal Processing.
09/10/2014 11: 06: 03 346 XISOAP Information: Received an XI message for processing
09/10/2014 11: 06: 03 598 Error SOAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)
09/10/2014 11: 06: 03 598 Information SOAP: completed the processing
OAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)
09/10/2014 11: 06: 03 598 Information SOAP: completed the processing
09/10/2014 11: 06: 03 598 Information SOAP: response message to continuing 7477aafa-38da-11e4-beed-00000028af0a
09/10/2014 11: 06: 03 599 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)
09/10/2014 11: 06: 03 599 Error SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)
payload is contains some special charters in which is in protiguse language
example.
• AWPJ SERV DE TERCERIZ and
dot is the special char
same payload while testing using sproxy tcode dot "•" is converting in " # "symbol and with out error its successfully updating the database in ECC.
while testing using the same payload using soap ui removing the dot symbol from the field its successfully processing and updating the database.
is this interface is failing in PI level ? or ECC i am not getting dump in ecc.
is there any special character conversation in sap pi level.
where this message exactly failing is in PI level or in ECC level?
Help us find the solution.

Hi Ravinder,
When you mark the option Do not use SOAP envelope the adapter will not generate the SOAP envelope therefore you need to set an extra mapping in the Request to wrap the SOAP envelope. For example with XSL:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml"/>
 <xsl:template match="/">
 <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Header/>
 <SOAP:Body>
 <xsl:copy-of select="/"/>
 </SOAP:Body>
 </SOAP:Envelope>
 </xsl:template>
</xsl:stylesheet>
Later in the response you will have the SOAP envelope tags. (You can do a first try without java mapping only to see in the monitoring the response with the junk character).
When you determine the junk character you can try to use and to modify the next java mapping SAP PI - Deciphering apostrophes in XML - Process Integration - SCN Wiki to deal with your problem.
Hope this helps.
Regards.

Acknowledgement for AsynThird-party-- SOAP-- PI-- ABAP proxy-- ECC scenario

Can someone please provide me a step-by-step for Third-party>SOAP>PI>ABAP proxy>ECC scenario.
Third-part system is sending an Asynchronous HTTPS message to PI which is then routed to the ECC system to do some processing. I have read many blong and all SAP Docu available on this subject, but i am still confused.
I understand that ABAP Proxies supports acknowledgement, but what needs to be done in the third-party system to be able to receive acknowledgements. Is there any special config. that needs to be done in Sender SOAP adapter?
What diff. needs to be done in ABAP proxy to be able to send acknowledgement messages, any config. in XI receiver adapter?
I will appreciate any guidance.
Thanks,
Saurabh

HI
Third party application need to have the synchronus communication enabled. If not then you need to get a wrapper develop for this kind of communication
For proxy development
Just go through these links:
How to create proxy.
http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm
ABAP Server Proxies (Inbound Proxy)
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
OutBound Proxy (Client Proxy)
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
Outbound Proxy (Client Proxy)
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
How to Activate Proxy.
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
File to R/3 via ABAP Proxy with good example
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
Synchronous Proxies:
Outbound Synchronous Proxy
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2boutbound%2bprogram%2b-%2bpurchase%2border%2bsend
Inbound Synchronous Proxy
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2binbound%2bprogram%2b-%2bsales%2border%2bcreation

Synchronous scenario for SOAP to PROXY

Dear Experts,
    I will be working on the following scenarios.
XI will expose the Outbound Interfaces as a Web Service Interface. Web Service Description (WSDL File) will be generated for the Interfaces in Integration directory. DSS (decision support system) will use this WSDL file to define the data types and develop the Web Application. The Web Application sender sends the request message (Start Date, End Date and Table name) synchronously to XI using SOAP Adapter as communication channel. XI sends the message to SAP R/3 via ABAP Proxy. The ABAP Proxy extracts the data from SAP R/3 and sends the data back to XI . XI further passes on the data to DSS.
Request
Sender Application:     DSS
Target Application:     SAP R/3
Sender XI Adapter:     SOAP
Receiver XI Adapter:     XI
Response
Sender Application:     SAP R/3
Target Application:     DSS
Sender XI Adapter:     XI
Receiver XI Adapter:     SOAP
It's a synchronous interface. Please help me out right from the SLD design. I just want an idea how to proceed with this.
How many mapping will have to do? also very important point , can any one help me out, how to write an ABAP proxy for the same. I will have rewards for every answer as time is very very less and work is more.
Thanks
Veeru

Viru ,
So the Business systems will Web as ABAP for ECC and other will be third party. I am right.
Yes
Can u suggest me how to proceed with the mapping. Any snap shots for this scenario?
Mapping will be simple using Mapping editor in IR .
If u have please provide me.
for your refernce :
Few proxy based scenarios :
http://help.sap.com/saphelp_nw04/helpdata/en/2b/f49b21674e8c44940bb3beafd83d5c/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/85/78af1bf407434796aaf8dbd6d4e7b7/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/a5/1b5342d8a7be30e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/a5/1b5342d8a7be30e10000000a155106/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
/people/prasad.ulagappan2/blog/2005/06/27/asynchronous-inbound-java-proxy
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7d4db211-0d01-0010-1e8e-9b07fc2113ab
http://help.sap.com/saphelp_bw30b/helpdata/en/64/30063c66171b3de10000000a11402f/content.htm
I am working on XI 3.0 for this scenario. how to handle the webservices here.
for Web service based scenarios :
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
Regards ,

SET_PAYLOAD_FAILED error in SOAP to Proxy scenario

Hi PI Experts,
We have an inbound syncronus interface (Non sap system to SAP) using the SOAP to Proxy scenario.
When we test the interface using any soap tool like soapui it is working fine but when the interface is triggered end to end from source system then the below error is getting dispalyed on source system.
500 Internal Server Error
In XI below is the error message -
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">SET_PAYLOAD_FAILED</SAP:Code>
<SAP:P1>IN</SAP:P1>
<SAP:P2>REQUEST</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Internal error when completing the message object (setting the payload, direction: IN message: REQUEST)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can any please let me know what is the issue here?
Appreciate your help.
Regards,
Jitender

We had a similar issue with a Synchronous Interface
The interface worked perfectly when sending the request directly to the integration server, but when sending it using SOAP the issue appeared.
It was very tricky to solve it because we had similar interfaces that worked without any issues.
SOLUTION: Create a new Service interface with a new name different from the one failing. And make sure The Message Types are in the same namespace as the service interface.
Why?:
The issue turned out to be in the sender agreement, and name-spacing issues.
Our Outbound Service Interface belonged to one SWCV and ns, We will call it "ns1:SI_A_OUT".
In PI 7.3, and I believe 7.11 also, the you no longer assign a default interface in the to the SOAP communication channel sender agreement pair.
Therefore the SOAP adapter determines the soap method from the payload. If The internal message type in the soap message belong to different namespace, the the java method getMessage() does not find the correct XML node, therefore does not find the payload.
<"ns1:SI_A_OUT">
...<ns2:MT_element>
getMessage( ns1:MT_element)
We are not sure if the issue is the implementation of the SOAP protocol or in the WSDL generation. But this issues seem to create orphan object during runtime, and even if you re-implement the complete interface, the sender agreement seems to be corrupt.
Therefore the only was we could solve this, was to move our MT to the same namespace as the service interface and rename the interface "ns1:SI_A2_OUT"
Hope this helps someone.
Juan Francisco Zurita Duque
NNIT A/S

Soap to proxy : sync scenario

Similar Messages

Maybe you are looking for