on 07-02-2008 8:11 AM
The project scenario is like this
SAP needs to send XML file output to 3rd party system through Web services.
SAP to SAP XI is IDOC adapter.
SAP XI to 3rd party system is SOAP adapter.
Please let me know what all settings need to require for sending XML output file to 3rd party by web services using SOAP adapter in XI.
Do we need WSDL file from 3rd party or what details r needed !
Points will be rewarded !!
Edited by: ViJaYaNt JhA on Jul 2, 2008 9:12 AM
Hi Vijayant,
Your scenario is basicallty SAPR/3(IDOC)-SAPXI-3RD PARTY(WEBSERVICES).
In your scenario, you have to do the following steps:
1. Configure the ALE seetings between SAP R/3 to SAP XI such as
- creation of logical system-t-code SALE
- creation of RFC in sm 59 pointing to SAP XI
- creation of port and using the RFC pointing to SAP XI
- creation of Partner profile for outbound parameter
2. Ask the webservices team to provide you the wsdl file for the 3rd party system
3. Do the SLD configuration for respective software product, software component
4. Configure Integration repository , use the wsdl file as an external definition so no need to create data type n message type for your scenarios.Create message Interface as Inbound & select the message type from external defintion of wsdl file for output. Import the IDOC and do the mapping and Inteface mapping.
5. Create the Business Service as your 3rd party system is webservice
the configure your soap receiver adapter communication channel and mention the address location URL which is there in wsdl file , mention the user authentication parameters if required , mention the soap action which is there in wsdl.
No need to create IDOC Sender adapter.
Create receiver determination , Interface determination , receiver agreement. No need to create sender agreement ad no sender communication channel required in your case.
6. Now the configuration is over and download SOAP UI tool and test the wsdl file connectivity.Once it is o.k
7. start triggering your IDOC and and it will be sent to reciving 3rd party system via SOAP adapter.
Hope it helps you.
Thanks & Regards
Prabhat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please refer following links
Regards
Aashish Sinha
PS : reward points if helpful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Idoc --- Xi -
webservice
1. Hope you have done at sender side i.e from R/3 to XI .
2. For receiver side you need to do below steps
2.1 . Get the WSDL of webservice , and import it into XI
Under External Definition in IR .
2.2 Create Message Interface for one of the messages
( methods ) of wsdl you have imported.
2.3 Now you do rest of things as usual in IR.
3. Configure Soap receiver adapter
3.1 Need to give URL of webservice you are calling .
3.2 all others are optional .
let me know if you struck anywhere .
- Satish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vijayanath,
Before u need to use the IDOC , create the basic setting in R/3 & XI end.
I think there is no need to create basic settings create the SOAP Adapter.
Once u configured in ID. U need to go TOOLS option, Under that create the WEB SERVICES'
Once u can select there is asking some default setting like URL , Namespace like that..
Once u can create SOAP Adapter. U can check the request for ALTOVA XML SPY...
Regards,
Skumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vijayant,
Chk out the link below to configure your receivevr SOAP adapter.
U just need to configure it for your requirement and test your scenario.
http://help.sap.com/saphelp_nw70/helpdata/EN/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
kanan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi
for The 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 that you define yourself.
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 externaldefinitions:
After importing the WSDL file, you can view the included messages on the Messages tab.
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 Webservice.
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 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 theconfiguration are Target URL and SOAP action. You get the values you have to enterhere from the WSDL file.You find the target URL at the tag soap:address and the SOAP action at the tag soap:operation:
page:
REGARDS
kummari
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.