Soap to Soap scenario(need suggestions)

Hi All,
I have a scenario to be developed. Its a soap to soap scenario. We need to send a request with target site name and list name in the URL.
As there are 4 different sites each has different list with different columns. We need to retrieve these data in a single structure and send it back to the source system( as response). Now I am stuck in the response structure creation. Anybody has any idea? Please suggest.

Hello,
I would suggest you to check below blog and using this create ur target URL (or action) dynamically to retrieve data from different sites.
Dynamically providing URL and action values to receiver SOAP communication channel
Now for the response, i would suggest you to use JM. So, in java code parse (whatever) response which is coming from WS, send the same to ur sender system - By this way u don't have to worry abt creating response structures in PI for each site.
Hope i understood ur question correctly and if not then do correct me.
Thanks
Amit Srivastava

Similar Messages

Soap - XI - File Scenario

Hi experts,
I need your help on this.
XI will receive a synch soap request with the following input parameters: date and supplierNo. With that input parameters XI has to find and retrieve (from a File Server) all the documents of that supplierNo for that specific date.
Do you know how to develop such scenario?
Thanks in advance
Pedro Leal
Edited by: Pedro Leal on Feb 13, 2008 6:17 PM

Hi Pedro !!
Based on your scenario description, maybe the best solution is to create a SOAP<->XI<->Proxy scenario where the Proxy could be ABAP or Java. I suggest a Proxy, because the receiver file adapter only writes files and the sender only picks files up based on a time interval and not on demand.
For example, the Java Proxy server could receive the request from XI, search the files and send them back as response. You need to check file sizes and if files content is XML or binary and maybe other details to see if this scenario only will we enough, or if you may need a BPM or more than one scenario, one for "prepare the files" and one that takes the "prepared" files and thru XI sends them back to the target as a response in a synch or async manner.
Regards,
Matias.
ps: please award points if helpful.

File to Web service (SOAP) to File scenario with out BPM in PI 7.1

Hi All,
I have scenario File to Web service (SOAP) to File scenario with out BPM.i am getting the below error:
1) Error MP: unexpected exception caught com.sap.aii.af.service.cpa.impl.exception.CPAObjectKeyException: Value of key must not be null: ObjectId
2) Error ROB: error during processing: com.sap.aii.af.lib.mp.processor.ModuleProcessorException: Processing Error
PI server is 7.1 with SP:8
I have configured the scenario like this
1) 2 File channels - Sender & Receiver ,1 RFC channel - Receiver. We need to note that, the additional Module parameters need to be added only for sender File channel
2) Created Sender Agreement
3)Created Receiver Determination
4)Created Interface Determination
5)Created Receiver Agreement
Regards,
Ramesh

Hi,
Thanks for your reply!!
My Scenario is File to SOAP to File.
Configred modules in Sender channal below:
Prcessing sequence:
Number       Module Name                                        Module Key
1..........       AF_Modules/RequestResponseBean.......1
2..........       CallSapAdapter..........................................2
3..........       AF_Modules/ResponseOnewayBean.......3
Module Configuration:
Module Key                                       Parameter Name                                       ParameterValue
1                                                        passThrough                                            true
3                                                        receiverChannel                                       receiverChannel name
3                                                        receiverService                                        receiverService name
please tell any more confiration requered.
Regards,
Ramesh

SOAP TO JDBC scenario: calling stored procedure which will return the value

Hi
I have Soap To Jdbc scenario in which I am going to call the Stored Procedure at target side which will be executed and it is going to return the result set .
Result contains following values.
return code as ( 0 Or 1) and also specific exception message if its return code as 1.
Could you suggest me the way by which I can handled this return code and send it back to the Sap PI system then the same thing is directed the to SMTP server for sending mail to consern person.
Regards
Kumar

The OUT parameters of stored procedure will be returned as response. Where exactly are you facing the proble? Here is a complete walkthourgh
/people/luis.melgar/blog/2008/05/13/synchronous-soap-to-jdbc--end-to-end-walkthrough
In your case, you don't want response at sender. Instead you want to mail it. For this you may use BPM to design your scenario with following steps
Receive (to receive data from sender)
Send Sync (to stored procedure and get response)
Send Async (to mail receiver)
Regards,
Prateek

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:Fault" in scenario with ABAP proxy client

Hello,
I realized the scenario CRM40_Basis620(ABAP proxy client)->XI->File.
XI:
The sender communication channel is a XI adapter (Parameters: HTTP 1.0, XI 3.0, Integration Server, Security profile unchecked, Security level - HTTP).
CRM:
The proxy generation is ok.
SLDCHECK is ok.
All RFC destinations are ok.
APPINT_200_620 for CRM was installed and configured well (I think so, but...).
When I ran the ABAP proxy client on CRM, sxmb_moni(CRM) returned the text for the XML Message (Display-CallIntegrationServer-Payloads-TraceDocument):
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = EST</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = BABKIN_RA</Trace>
<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = DC4424A659314CF18F500002A541D0E7</Trace>
<Trace level="1" type="T">PLNAME = SENDER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTS0004</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline SENDER</Trace>
<Trace level="1" type="T">system-ID = EST</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = BABKIN_RA</Trace>
<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<Trace level="1" type="T">Get definition of pipeline PID= SENDER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
- <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV">
<Trace level="1" type="T">URL for integration server read from global configuration</Trace>
<Trace level="1" type="T">URL= http://SRMDEV.oao.sng:8011/sap/xi/engine?type=entry</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY" />
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="1" type="System_Error">HTTP-client: error response= <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Header> </SOAP:Header> <SOAP:Body> <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during conversion of XI message</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIServer</SAP:Category><SAP:Code area="SECURITY">INBOUND_SECURE_LEVEL</SAP:Code><SAP:P1>DC4424A659314CF18F500002A541D0E7</SAP:P1><SAP:P2/><SAP:P3>HTTP</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Message DC4424A659314CF18F500002A541D0E7 was sent with ''. Channel configuration, however, requires 'HTTP' </SAP:Stack></SAP:Error></detail></SOAP:Fault> </SOAP:Body> </SOAP:Envelope></Trace>
</Trace>
<Trace level="1" type="System_Error">Exit XMB because of system error!</Trace>
<Trace level="1" type="System_Error">System-Error: HTTP.HTTP_STATUS_CODE_NEQ_OK</Trace>
<Trace level="1" type="System_Error">HTTP status code 500 : Error during conversion of XI message</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
</SAP:TraceHeader>
I think the main problem is the parameter "HTTP Security level" for the channel, but not sure.
Does anybody know where to find a solution?
Regards,
Roman

Hi Roman
There is no need for an XI adapter for client proxy.... we only use that for server proxies.
Vaibhav

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.

SOAP to RFC scenario prolem

Hello Guru's
 Im trying the basic SOAP TO RFC scenario, in which RFC is SXIDEMO_AIRL_FLIGHT_CHECKAVAIL
and the out bound interface consists of only basic feilds i.e.
REQUEST MESSAGE TYPE : AirlineID
 ConnID
 Fldate
RESPONSE MESSAGE TYPE : Ecnofree
 Bussfree
 Firstfree
and no fault message type.
i created the scenario with out any errors, and i defined webservies in ID with the following URL
http://starxi:50000/XISOAPAdapter/MessageServlet?Channel=:SXI_BS_SOAPRFC_SENDER:SOAP_RFCSENDER
it is according to the following syntax
htt://<xi server>:<J2EE Port>/XISOAPAdapter/MessageServlet?channel=:<sender business system>:communication channel.
But im not able to post SOAP request to the xi server. it is saying following error
"SOAP Request cannot be posted <with url > 403"
403 is the error code.
please can anyone help me in overcoming the above problem. and where iam wrong.
Thanks in advance
arjun

Hi!
Please check once again reg SOAP URL while generating the WSDL.
[http://<HOST name:5<Port>00/XISOAPAdapter/MessageServlet?channel=:<Channel Name>:<Adapter Name>]
[Re: Using SOAP Sender adapter in PI 7.1]
1. Check whether your SOAP URL s correct or not which you are giving in the receiver SOAP adapter
2. Also check you are giving the SOAP action in the receiver SOAP adatper correctly or not.
3. Finally check the SOAP service is activei or not in SAP>BC>XI-->SOAP in ABAP stack
4. Since FIle is only for ASYN comm and while using FILE for sync interface you need to pass module paramters in the Sender File CC
ERROR 403 means::
This error will be comming mostly in the synch scenarios like SOAP to RFC - SOAP and FIle to RFC--FILE
when the target system is down or service is inactive.
Error: HTTP 403 Forbidden
Description: The server understood the request, but is refusing to fulfill it
Possible Tips:
Path sap/xi/engine not active
u2022 HTTP 403 during cache refresh of the adapter framework - Refer SAP Note -751856
u2022 Because of Inactive Services in ICF u2013Go to SICF transaction and activate the services. Refer SAP Note -517484
u2022 Error in RWB/Message Monitoring- because of J2EE roles u2013 Refer SAP Note -796726
u2022 Error in SOAP Adapter - "403 Forbidden" from the adapter's servlet. u2013Because of the URL is incorrect or the adapter is not correctly deployed.
Regards::
Amar Srinivas Eli

Response from PI in SOAP to SOAP Scenario

Hi,
My scenario is Soap to SOAP sending purchase orders. they want acknowledgement from PI whether PI received the message or not in the form of SOAP response.
sender system not expecting the response after the message processing in receiver system, they are expecting the response when PI receives message from them.
As any way they receive HTTP200 OK acknowledgement is it necessary that to send the SOAP response from PI by developing BPM?
Is it a good way of doing it?
Is any other way of doing it?
Your suggestions will be helpful to me.
Thank you.
Santhi.

Hi Santhi,
Please refer to SAP Note 856597 - SOAP Adapter FAQ Question number 2
2. Sender Asynchronous Calls
o Q: What are the correct sender options for asynchronous calls?
When the client sends a SOAP message and checks if the response is
an HTTP 200 response message with an empty soap envelope or an HTTP
202 response message with no content, the quality of service with
AtLeastOnce can be realized. In this case, the client must resend
the message until such a successful response is returned. When the
message successfully accepted by the adapter, an HTTP 200 response
with an empty SOAP envelope or an HTTP 202 response message with no
content is returned.
You don't have to do anything. When an async message is sent, PI will either reply with a 200 with an empty SOAP Envelope or an HTTP 202 with no content . That will serve as your acknowledgement.
Regards,
Mark

Business systems for Soap to file scenario

Hi Experts,
I am working on a soap to file scenario.Which type of business systems shall i create i.e Third party,As ABAP,As Java etc.Please suggest.
Thanks
Veeru

Hi,
Normally Business systems are created in SLD when you are provided with relevant system details. A business service is used in case of the system being an abstract unit.
In your case, it is better to go for Business service because you generally don't have such details for third party system.
Just go through this link for more understanding...
Difference between Business System and Business Service
Regards,
Chandra

Doubt Regarding SOAP to File Scenario

Hi All,
I am trying to create a SOAP to File scenario .These are the following things I have done so far :
IR - 2 datatypes ( 1 for soap message and 1 for file message )
       2 message types for the corresponding messages
      2 Message interfaces, both are asynchronous
      1 message mapping
      1 interface mapping
ID- 2 business systems (1 to send soap, 1 to recieve file )
    2 communiccation channel (soap sender, file receiver )
soap sender adapter parameters - Interface Name - Message interface for soap message
                                                  interface namespace - scenario namespace
Then, i generated a wsdl file to expose the outbound message interface for soap message as a web service, url for message interface : http://host:port.XISOAPAdapter/MessageServlet?:service:channel.
After generating the wsdl file, i imported it in external definition
Could anyone plz. tell me, is this the right approach to creat this scenario ? how can I test this scenario?using altova spy ?

Hi,
The URL you have mentioned to genarate WSDL is not a valid one
http://host:port.XISOAPAdapter/MessageServlet?:service:channel.
Check the below valid URL
http://host:port/XISOAPAdapter/MessageServlet?channel=:service:channel.
You no need to import this to the Eexternal Definition as you already have DT,MT and MI, Any way this dosn't make any difference.
You can use SOAPGUI Tool to test:
->Create New Project -> provide WSDL you have genarated.
->Select Request and provide username and password and click the green button on top(Submit request to end URL).
Using altova spy:
Select SOAP Menu->Create New SOAP Request and provide your WSDL file and
SOAPMenu->Send Request To Server
Then you will get response..
Regards,
Prasanna

Testing of SOAP to FILE Scenario

Hi all
I have done with SOAP to FILE scenario.
--> while defining web service what we need to give in the URL????
--> How to test this SOAP to FILE scenario to see wheather it is working fine or not, what are the all options
Thanks
Dheeraj

Hi Dheeraj,
Definitely you can test it through the microsoft infopath tool.
steps to follow:
Executing wsdl File Using Microsoft Info Path
1.>Click on the design a from template
2.>Select the Web service icon and click ok
3.>Select the radio button u2018receive and submit datau2019 and click on next.
4.>Enter the path of the generated wsdl which u have saved and click next.
5.>Select the interface and click next
6.>Select the interface and click next.
7.>Double click on parameters.
8.>Double click on the parameter (which you want to send as request). Then click on the query field and click ok.
9.>Click next. And click Finish
10.>Now drag the query fields on the data fields to the left side. And click preview.
Please follow these steps I hope you will be able to test it.
Thanks and regards,
Nutan

Help SOAP to RFC Scenario using BPM (Synchronous communication)

Hi,
I am doing a scenario from SOAP to RFC scenario(Synchronous communication). Here I am creating a PM Notification in the SAP system through a webservice.
I am using three BAPI'S here,
1. BAPI_ALM_NOTIF_CREATE
2. BAPI_ALM_NOTIF_SAVE
3. BAPI_TRANSACTION_COMMIT
I am successful in calling the first BAPI from the Web Service. For this I have not used BPM. But to commit the transaction(PM notification in this case), I have to execute the other two BAPI's as well. I have to pass the output of first BAPI to the second BAPI and then execute the 2nd BAPI. And finally have to execute the 3rd BAPI. FYI, 3rd BAPI is not dependent on any output. It has to be executed independently after execution of the first two BAPI's.
How can I execute this scenario? Do I have to use BPM? If yes please let me know the steps in detail. I have not done any BPM scenario till now. So please answer me in detail.
Thanks in Advance,
Vijay
p.s. reward points are must

Hi Vijay,
Yes, You will indeed need a BPM in this case...
Based on my understanding of the Scenario u have explained, here are the steps that would be needed.
1. Receive With the Sync-Async Bridge open.
2. Transformation Step (Between the source Request and The BAPI_ALM_NOTIF_CREATE Request)
3. Send Synchronous
4. Fork
5. In one Branch of the fork - Transformation (Between the BAPI_ALM_NOTIF_CREATE Response and API_ALM_NOTIF_SAVE Request)
6. In the other branch of the fork - Transformation (Between a Dummy Source and the BAPI_TRANSACTION_COMMIT Request)
7. Send Synchronous (to make the 2nd BAPI Call)
6. Transformation ( BAPI_ALM_NOTIF_SAVE Response and the source Response)
7. Send Asynchronous (to make the 3rd BAPI call)
8. Send the Source Response and close the Sync-Async Bridge.
There might be alternative ways also of doing it...
Also a better design would be to take care of the 2nd and the 3rd BAPI call within the code of the 1st RFC Function Module.
Regards,
Abhy Thomas

SOAP to SOAP scenario

Hi Experts,
Could you please tell me, how to do SOAP to SOAP scenario?
Mainly need info for Receiver SOAP Adapter...
Any document for the same?
Regards
Sara

Hi,
Receiver SOAP Adapter
The receiver SOAP adapter connects XI with an external Web service. To call the Web
service, you need to define a message interface that represents the structure of the
request and response of the Web service. You can create this message interface easily
with the help of a WSDL file that represents the Web service. If this is not possible, you must create the message interface based on data types.
- Uploading the WSDL
Since the WSDL describes the message interface, you upload the WSDL into the
Integration Repository. Go to your Software Component Version and open the required
Namespace. Create an External Definition.
In the external definition object, choose Category wsdl and click Import external
definitions.After importing the WSDL file, you can view the included messages on the Messages tab page:
The namespaces of the messages are part of the WSDL description and can
differ from the namespace of the external definition object.
Now you can create a message interface corresponding to the message types from the external definition. You need the message interface for routing the message to the Web service.
In the message interface object, select the message types of the external definition
object by using the input help.
After assigning the output and input message, save and activate your work. Now you can use the message interface for routing and mapping.
Creating a Message Interface Without WSDL
For some scenarios it is not possible to provide a WSDL file. In this case you need to create a message interface according to the message structure of the server. The best way to achieve this is by using an example SOAP message for the request and the response message.
Since the SOAP adapter creates the SOAP envelope you have to extract the SOAP
body. Usually, Web services ignore declarative attributes (xsi:type), therefore you can delete them. The namespace declaration of the root tag must be applied. The XI
message payload should be the following message.
Create a data type, message type, and message interface according to this structure. In the message type, apply the correct name and namespace of the message.
Creating a SOAP Receiver Channel
To call the Web service, you create a communication channel with type SOAP and
direction receiver in the Integration Directory. The obligatory parameters in the
configuration are Target URL and SOAP action. You get the values you have to enter
here from the WSDL file.
You find the target URL at the tag soap:address and the SOAP action at the tag
soap:operation.
If more than one message type is described in the WSDL, several SOAP actions
might also be defined. Check for the correct operation name. If no SOAP action is
defined in the WSDL, you can leave the parameter in the receiver channel empty.
For the receiver SOAP adapter you need at least the following parameters.
If the Web service is outside your system landscape and you need to address a proxy server, select the Configure Proxy checkbox and fill in the corresponding fields.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful

SOAP to SOAP (ECC) Synchronous Scenario

Hi,
 I am configuring SOAP to SOAP scenario. Source systems is take an SOAP UI and Destination system as SAP ECC system. I configured as follows in PI 7.11
1. Created Two Data type for Source System( one for Request and Second one is for Response)
2. Imported WSDL which was created in ECC.
3. Two Service Interface( Both are Synchronous)
4. Two Message Mappings( Source Message Type to SOAP Request & SOAP Responce to Sencer system Response message)
5. Operatino Mapping ( Request and Response)
ID
6. Once Business Component for both Sender and Receiver
7. Two SOAP Communicatino Channels ( Target Channel i given Target url and authentication Details)
8. Receiver Determination
9. Interface Determination
10. Sender Agreement
11. Recever Agreement
 I am executing the scenarion now i am getting the "http 404 not found error".
My doubt is do we need to do any Configuratin in ECC System? I did not do any configuration in ECC System. If i am accessing that WSDL through IE then i am getting response back. Please lte me know the solution.
Regards,
Dev

Hi Deevan,
 Check if the Target URL that you have mentioned is correct.
The target URL should be like this,
http://server:port/sap/xi/adapter_plain?namespace=<xxx>&interface=<xxx>&service=<xxx>&sap-user=<xxx>&sap-password=<xxx>&sap-client=<xxx>&sap-language=<xx> .
Copy ur target url on to the browser and check what happens??
Regards
Deepthi Premnath

Soap to Soap scenario(need suggestions)

Similar Messages

Maybe you are looking for