SOAP Sender System in SLD

Hi
Im doing a SOAP-XI-JDBC scenario
Im getting request from a 3rd part system to XI through Webservice provided by WSDL file
Now i have to create a sender SOAP adapter . For this do i need to make an entry of the sending system in my SLD..
Do i need to create a Business system or Business Service
If so what would be the details
Thanks
Keerthi

To add more points to Rajesh
<soap:address location="http://yhsapi01:50000/XISOAPAdapter/MessageServlet?channel=:BS_FILE_SENDER:CCT_WebService_2_WebService_Sender_H1309&version=3.0&Sender.Service=BS_FILE_SENDER&Interface=http%3A%2F%2Fyash.com%2Fh1309%2FWebService_2_WebService%5EMI_A_OUT_+SendSMSToIndia_H1309" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
In the above sample example soap:address element specify the address to access the XI. test tool like soapUI read the wsdl and try to connect to the WebService provider(here XI) using the address specified in the soap:address element and soap:action attribute in soap:operation because soap:action identifies the specific operation in the webservice.

Similar Messages

SOAP sender configuration

Hello,
I am trying to configure SOAP sender in my XI system. My SOAP sender system is AS Java System. I am trying to add this to SLD. Can i add AS java system for Visual admin also. What is difference if i add from SLD and Visual admin thorugh SLD data supplier.
In SLD i have given Message port : 3900 and Message HTTP port as 8001.
Is it correct.
Also, i would like to know, In outbound interface, I suppose to enter WSDL. to accept the request.
How to test it.
Thanks in advance,
Srinivas

>>Also, i would like to know, In outbound interface, I suppose to enter WSDL. to accept the request.
How to test it.
To test your scenario you need some SOAP client(Altova XML spy etc).once the test is done you can ask the actual system to send the data so that you can test the complete scenario
Thanx
Aamir

Stuck with logical system name for JDBC Sender system!!!!!!!!!!!!!

Hi All,
I'm doing a scenario as JDBC2FILE.
I tried to add my jdbc sender system to SLD. So i created the technical system
now i'm creating business system...what should i give at logical system name tab? I've created tech system and business system as third party.
do we need logical system name in this scenario where we are not interacting with any R/3???
can anyone suggest the way to achieve this scenario?
Thanks in advance.....
Santhosh.

Hi Santhosh,
I just want to add ons..few more information which it might help you.
You no need to give logical system when you are using Thirdpaty.
Please check the below blog you will get more idea how to proceed to achieve the JDBC Scenario.
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
If you have any doubts while proceeding with your scenario plesae let me know..I will try my level best.
Thanks and Regards,
Chandu

Soap sender adapter show invalid content type

Hi dear mates,
I have a SOAP-JMS scenario working succesfully on 7.3.1. But in 30 min after ICM restart (usin SMICM) something wrong happend because all Soap sender adapter fails showing that error.
<text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not parse XMBMessage due to invalid content type for SOAP: TEXT/HTML
If I restart manually ICM still working fine until next 30 min more or less.
I have added MP transform bean to ensure that I am sending UTF-8 propertly. But it doens't work.
Does anybody know a clue why occurs this strange behavior?
Thanks in advance and regards.
José Antonio.

Thanks Vladimir,
This is exactly the behavior. And yesterday we have to increase the memory because it has 32gb shared in two PI instances, 16gb(DEV) and 16gb(TEST). And the memory was always full.
Recently I found the trouble. Doing SLDCHECK have this trouble also. SLDCHECK error-Check and maintain the SLD content for the current client
So, I re-register once again the system in rz70 and review related Bussiness System. And BS pipeline URL was wrong :S because it hasn't be wrote with path /sap/xi/engine?type=entry.
After restart SLD I do sldcheck and it looks perfect.
Thanks to all.
I hope this stupid error do not disturb any other consultants.
Best Regards.
Jose.

Error while posting messages to SOAP sender adapter SP 13

Hi Friends,
I have configured a SOAP sender adapter in XI 3.0 and is using the URL
http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to post the messages. When I open the URL in the browser I am getting the error.
Message Servlet is in Status ERROR
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal not instantiated
ModuleProcessorRemote not instantiated
But when I test the URL http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to check the communication channel I am getting the right response as below.
<?xml version="1.0" ?>
<http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_EBTR_WEBSERVICE:CC_EBTR_WEBSERVICE_SOAP> <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>e7ac884596ea3d088cbfd8b434f942f2</channelID>
<name>CC_WEBSERVICE_SOAP</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party />
<service>BS_WEBSERVICE</service>
</s:ChannelInfo
I used the http capture to debug, In the 1st case though I am getting "Message Servlet in status error" I am seeing a 200 OK code in the http capture tool. When the message is posted from .net client proxy we are getting a 500 internal server error.
Am not sure what causes the error ? I saw two notes in SDN related to SOAP - J2EE SP13. We are in SP13. Is this the issue ? Wanted to know your opinion before applying the notes.
Thanks & Regards,
Mathew

ABAP & Java stack was on different SP levels.

Logical Sys Name for Business system in SLD for Third Party

Hi !!
I have little doubt what will be the logical system name for creating Business systems in SLD for third party?
thanks
Gowri

Hi Gowri,
sorry, i dont agree with the other answers. The logical system name is required for ALE partner finding. If you dont want to communicate with IDocs you dont need it. If you want to send messages from third party system to R/3 via IDoc adapter, then you should (can) give a name. It can be configured in IB directory as well (adapter specific identifiers). Choose any name, this name will be used for the partner agreement in R/3.
Regards,
Udo

Variable Transport Binding - Soap Sender

Hello all,
I'm trying to retrieve a parameter from the HTTP header of a SOAP request.
I have created a SOAP sender communication channel, checked "Set Adapter-Specific Message Attributes" and "Variable Transport Binding", and entered the name of the parameter in Variable Header (XHeaderName1).
When I send the SOAP request, DynamicConfiguration exists with all standard parameters, but there is no XHeaderName1...
If I try the same with sender HTTP adapter, it works fine.
In the other way, if the dynamic configuration parameter XHeaderName1 already exists, and I try to add it in a HTTP header parameter in a receiver SOAP CC, that works.
Does somebody know why this doesn't work in the sender one?
Thanks,
Greg
PS: I'm using PI7.0 SP14

Hello,
I can see in dynamic configuration, with the namespace http://sap.com/xi/XI/System/SOAP, the standard HTTP parameters like SServerHost, SRemoteUser, etc...
But if I add a HTTP header parameter in the SOAP request, and I try to retrieve it with the SOAP sender CC, the parameter is not added in the dynamic configuration. If the name of the added HTTP header parameter is "TestParam", I put "TestParam" in the XHeaderName1 field of the sender CC, but the value is not added in the dynamic configuration. This is my problem.
Thanks,
Greg

Variable Transport binding - SOAP Sender Adapter

Hi All
have a scenarion where Sender System is sending Custom SOAP Header as below into P through SOAP Sender ChannelI.
And the requirement is to access the values coming in Header fields, example within Message Mapping need to Map Headername1 value to Outgoing structure.
<soapenv:Header>
 <Header1>S1</Header1>
 <Header2>S2</Header2>
 <Header3>S3</Header3>
</soapenv:Header>
 <soapenv:Body>
 u2026..
 </soapenv:Body>
Have checked the Paramter KEEP Headers in SOAP Adapter and in Adapter Specific Message Attributes have defined the following
Variable Header (XHeaderName1) = Header1
Variable Header (XHeaderName2) = Header2
Variable Header (XHeaderName1) = Header3
Now need to know what should be mentioned in the UDF in the Message Mapping for accessing Dynamic Configuration. Will these headers mentioned will be a part of Dynamic Configuration or not ?
Using the below UDF and its failing in Message Mapping - kindly suggest the corect way of achieving the same
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key1 = DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/SOAP", "XHeaderName1");
String value = conf.get(key1);
return value ;
Appreciate response in this regard
//Swetank

Hi Abhishek
Its failing at runtime at Message Mapping stage. The real problem is that I can't see the Header1 in my Dynamic Configuration header - it has all the other fields like SServerHost, SRemoteUser, but not my Header1 (S1) field. Thus either the UDF is wrong or any configuration in SOAP Sender Channel needs to be adjusted.
Further I am not sure whether Custom SOAP Header fields can be a part of Dynamic Configuration or they only show fields which are part of HTTP header.
//Swetank

SAP PI 7.1 SOAP sender 500 internal server error

Hello!
We would like to receive messages from our business partner. As the partner sends EDIFACT we have to use the conversion from EDIFACT-text to EDIFACT-xml. That's why we have to use SOAP instead of plain HTTP.
As the partner already sent messages over X.400 we just added a SOAP communication channel and used this channel in the sender agreement instead of the X.400 communication channel.
We sent the following link to the customer:
http://<server>:<j2ee port>/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<SOAP sender communication channel>
One question: is the <service> the communication component used for the partner?
At the moment the partner receives a 500 error message. Due to our network partner the message reaches the PI system.
Due to the information I found that also a message parsing error can cause a 500 error message I would like to add the processing sequence:
Does anyone have an idea how to solve this problem?
Thanks a lot!
Regards
Christian

Hi Christian
You can refer to the following SAP Library link on how to configure the SOAP sender.
Configuring the Sender SOAP Adapter - Configuring the SOAP Adapter in the Integration Directory/PCK - SAP Library
For the URL, the <service> is the Communication Component that the SOAP channel belongs to.
Using the example below, the value would be P_B2B_:BC_:CC_S_SOAP_
Actually SAP recommends a new alternative for the URL. If you scroll right to the end of the library link above.
You have configured the sender SOAP adapter. You can trigger a call to the sender SOAP adapter using either of the following URLs. However, SAP recommends you to use the second option.
http://hostname:portname/XISOAPAdapter/MessageServlet?channel=partyname:service name:channelnameIf you have not created a party, enter channel=servicename:channelname.
http://hostname:port name/XISOAPAdapter/MessageServlet?senderParty=name of the sender party<&senderService>=name of the sender service<&interface>=name of the interface<&receiverParty>=name of the receiver party<&receiverService>=name of the receiver service<&interfaceNamespace>=name of the interface namespace
You can get this by generating the WSDL from the Sender Agreement object (Sender Agreement -> Display WSDL). The generated URL will be at the last section of the WSDL.
Also, please note that modules cannot be added to the SOAP sender adapter, also mentioned in the link.
You cannot add your own modules to this adapter.
An alternative would be to receive the EDIFACT Flat file as it is, and write it to at temporary File/FTP location. Then have a second channel pick it up, you can configure the second channel with module to convert it to EDIFACT XML.
Lastly, regarding the issue about the partner getting HTTP 500 error. Please check if you are able to see any error logs in the communication channel. It might give you some pointers as to what might be wrong - invalid sender agreement, etc, etc.
Rgds
Eng Swee

SOAP sender adapter and XI adapter reusablity

Hi,
We are having good amount of interfaces using SOAP sender and XI Adapters (WS to Proxy scenarios).
My question is :
we can make reuse of Sender SOAP and Rcvr XI adapters in all scenarios.
If we reuse these adapters in all our interfaces what are the limitations and any problems we may face in future?
Replies will be highly helpful.
Thanks
Kishore
Edited by: kishore kumar on Jan 21, 2010 7:23 PM

SOAP sender depends on the Sender Message Interface and Namespace (in versions lower than SAP PI7.1) so if your scenarios satisfy these parameters then you can (rather should) re-use the channels.
Similarly for the PROXY receiver channel....if the proxy is being hosted on one particular receiver SAP ECC system then the details in all the channels that you create will be the same and wont be recommended....hence even this can be re-used.
There is no issue in re-using the channels....just that you should closely monitor these channels to ensure that they do not stop/ fail causing all the involved interfaces to stuck.
Regards,
Abhishek.

IDOC sender system settings

Hi,
I am trying to do the settings for the idoc sender system the steps i have completed are..
1) sm59..maintain a rfc destination from idoc sender to the integration server.
2) we21..created a tRfc port with the rfc dest from step1.
step 3 is where i am stuck...
3) we20....to maintain the partner profile and partner number...there isint enough info in the xi config guide..
any pointers..would be appreciated.
Regards
Ravi

ALE settings.
SAP XI1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP XI towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.

Registration of 4.6B systems in SLD

Hi,
Some of the systems in my landscape are still in version 4.6B and I would like to register them in SLD.
According to SLD doc I can add them manually, but I don't want to perform manual update of system data every time when something changes.
I heard that there is an agent that can run on older than 6.20 systems and send data to SLD, but I can't find any information regarding this topic. Could you please confirm if such an agent exists or maybe there is a different way to make it automatic?
Thanks in advance.
Jola

Hi Jola,
This is what is meant in the Note:
>Solution
>The manual entry of data in the System Landscape Directory is replaced
>by an "instrumentation" of the SAP system. The instrumentation for the
>automatic information transfer is carried out by the configuration of
>"SLD agents". The relevant software is imported with the latest SAP
>Support Package.
Best Regards,
Matt

Need to include the R/3 Business system in SLD.

Now i need to include the R/3 Business system in SLD.
To do that i have to establish an RFC connection, could anyone guid me what type of RFC connection i need to use like HTTP connection or else other..... Get me the details.

The distribution, participation in distributing or otherwise sending of this material is against the law. The material you are requesting is copyrighted material and available ONLY to customers of SAP. If you need such documents from the SAP Service Marketplace then you must have "S" user ID and login yourself to retrieve this material. If you do not have a "S" user ID then you should contact your own internal company groups responsible and request one or request them to retrieve the document for you.
By participating and sending such documents you are at risk for legal action and a removal of your account here on SDN and BPX.
DO NOT send material via email such as this! Further actions will result in officials within your company and your SAP Sales Account being notified and could result in legal action against you as an individual.

Help Need on SOAP (Sender) to RFC Scenario(Synchronous Communication)

Hi All
I have a requirement of SOAP(Sender) to RFC scenario(Syncronous Communication). The scenaio goes like this........
I have a web service through which I have to create a SAP Notification in SAP system and the Notification ID created and other details have to be returned back to the webservice from the BAPI. I have identified the relevant BAPI for the scenario.
I have a wsdl file which I have uploaded it. What are the next steps to be done?
Please let me know what all(e.g., Data types, Message Types, Message Interface) I have to create in Integration Repository and what all configurations I have to make in Integraion Directory.
FYI, I have a gone through a list of Blogs, but didn't get enough info.
Please help me out in providing your valuable answers.
Thanks,
Vijay
P.S. Rewards points are sure .....

Hi Vijay,
 If at all you have uploded wsdl file for the webservice you no need to create data types for the same even for the same as RFC also.
 Create message mapping and drag the wsdl file which you have imported as External Definiations and there you will be having request and response parameters..Do the mapping accordingly(according to your requirement).
Mapping like:
 Wsdl(Request)---->RFC (Input parametrs)
 RFC (out parameters)------>wsdl(Response)
Create message interface with Synchronous for outbound
 No need of DT,MT if at all if you import the wsdl file.
 Hope i am clear.
Please let me know if you have any queries..!
Thanks and Regards,
Chandu.
null
null

SOAP Sender to RFC Scenario WSDL File

Hi,
I am working on SOAP -> PI -> RFC Scenario. I generated WSDL from sender agreement and gave to the client that can consumed by the third party system. But client is not ready to consume the WSDL. He provided WSDL and asking me to use that. Could you please suggest whether WSDL given by the client can be used in SOAP -> PI -> RFC Scenario. If it is possible, could you please provide steps how it can be done?
Thank you.
Regards,
Cdr.

Thank you Hareesh & Divya,
When we generate WSDL from PI, it gives soap action and soap address location based on the interface we use for SOAP -> PI -> RFC.
When we import WSDL given by the client as external definition, we get messages(Structures). But where do we pass the soap action or address location. I do not see any option in the soap sender communication channel. I am not visualize the link.
Can somebody share their knowledge if they have done in this way.
Thank you.
Regards,
Cdr.

SOAP Sender System in SLD

Similar Messages

Maybe you are looking for