Problem sending to XI soap adapter

Hi
I have a webservice in XI, a third party application (built in .Net) is sending data to this webservice. My problem is that when trying to send I get this error message in the .Net program System.Web.Services.Protocols.SoapException : Server Error
I can not find any traces in the RWB or SXBM_MONI.
How can I find a more detailed log?
Best Regards
Morten

Hi,
For your Previous Thread :401 with the Unauthorized
1) This might cause due to wrong permissions.
2)Try with this Login XIISUSER
3)Tcode SICF -> Default_host -> sap -> xi
( Check right password for the user id )
Regards
Agasthuri Doss

Similar Messages

Problems using access control in sender agreement for SOAP adapter 7.1

I am trying to use Access Control Lists to restrict user access to web services/interfaces which are exposed via PI. This can be configured via the Integration Builder Directory using the u201CAssigned Usersu201D tab of both Communication Components (Business System) and Sender Agreements.
The configuration is via the above mentioned components. However, I understand that itu2019s the adapters which at runtime are responsible for actually applying these checks.
I have been having problems getting the access control to work using a setup involving a SOAP adapter of type SAP BASIS 7.10.
The symptom of the problem is that although the access control works as expected at the Business System level, any settings at the Sender Agreement level appear to have absolutely no effect whatsoever.
I have confirmed that I have no problems if I use an adapter of type SAP BASIS 7.00. However, I really need to get this working on 7.1.
I have looked on the SAP support portal but can not find any notes that relate to this.
Has anyone else had a similar problem? And have you found a fix for it?
Any suggestions would be welcome.
Edited by: Malcolm Dingle on Jun 17, 2009 1:08 PM

Hi Shai,
Please have a look at the following link and see if it helps you .
It deals with SOAP adapter installation and activation
Re: SOAP adapter installation and activation
Best Regards
Edited by: Prakash Bhatia on May 8, 2009 11:51 AM

WSDL url for sender and receiver SOAP adapter

Dear Experts,
I am working on SOAP --> SAP PI --> SAP ECC synchronous scenario. That means I have to create 2 Cc for SOAP i.e. Sender as well as Receiver adapter. I am responsible for creating the Request as well as Response structure in SAP PI. The sender application team is dependent on me to get the WSDL file.
Please provide the suggestions on the below.
Sender SOAP adapter.
1. I will create the WSDL from Sender Aggreement. How to get the url and what is the navigation step? Should I provide the same url to sender application team to call the service.
Receiver SOAP adapter:
2. In the receiver SOAP adapter , Should I have to get the web service parameter of the sender application. As mentioned , I am creating the response structure as well. That means I can not import the WSDL from the sender application. How to get target url in the receiver SOAP Cc.
I refered to the forum SOAP SENDER - test in soapui but its not clear.
Regards
Alice Rebecca
Edited by: Alice@xi on Dec 20, 2011 5:48 PM

Dear Bhaskar,
For synchronous scenario
 Request
MS Application (SOAP)<--> SAP-PI <--
> SAP ECC.
 Response
I am creating the Request as well as Response structure in SAP-PI and its agrreement for both
the ways.
So for the MS appl team, I will give the WSDL url from the sender agreement to make the request to SAP-ECC.
Now for receiving the response from SAP ECC, from where I should find the value to enter in the target url of SOAP
receiver channel.
1.Should I take the target url value from the MS Application team?
2.How to know whether the MS Application or SAP ECC is hosting the web service?
Regards
Alice

How to send images using SOAP adapter

hi All,
I want to send images using the SOAP adapter . ( Sender and Receiver )
Can anybody help out with this requirement
Regards,
Loveena

Hi,
Following links may help U
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
http://help.sap.com/saphelp_nw04/helpdata/en/3c/b4a6490a08cd41a8c91759c3d2f401/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/frameset.htm
to know the basics about soap adapter u cn check out this link
/people/padmankumar.sahoo/blog/2005/02/15/an-overview-of-soap
to get in detail about the attachments chk out this link
hi i am unable to attach an attachment in File to mail scenario
Regards
Pullarao

Problems when calling the SOAP adapter from a Webdynpro

Hi,
An error occurs in the SOAP adapter when sending a message from a Webdynpro client. I have downloaded the SAP Soap Client and made the same test and that works fine.
I had to do some debugging to finally find the stack trace found below.
Does anybody have an idea of why the call doesn't work from Webdynpro?
<text>com.sap.aii.af.service.cpa.CPAException: invalid channel (party:service:channel) = <null>
 at com.sap.aii.af.mp.soap.web.MessageServlet.getChannelID(MessageServlet.java:415)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:377)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)</text>
</s:SystemError>
Thanks for help,
Hans

Hi Suraj
First I should mention that I have imported a generated WSDL from XI to create the Model and thus the port configuration. The URL looks like this:
http://<host>:<port>/XISOAPAdapter/MessageServlet?Version=3.0&Channel=:Telia_Kundservice_portal:Sender_SOAP&version=3.0&Sender.Service=Telia_Kundservice_portal&Interface=urn%3Aacandofrontec.se%2FTelia%2Ffaktura%5ETelia_faktura_4
Service = Telia_Kundservice_portal
Channel = Sender_SOAP
I've also tried with a modified shorter version which is also the one I'm using from the SAP SOAP client.
http://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:Telia_Kundservice_portal:Sender_SOAP
The actual call is a typical one:
wdContext.currentRequest_Faktura().modelObject().execute();
Before this call the Basic authentication (user/passw) is set.
Regards,
Hans

Sending Attachments via SOAP Adapter

Hi Everyone,
We have the requirement to send the text files as attachement using SOAP Adapter. Can anyone help me how to do it in XI and the structure of WSDL. Or any document which can help me getting this done.
Any help appreciated.
Thanks in advance
Laks

I understand i need to add teh WSDL file in the repository .
Yes, it would be like any other soap receiver scenario wherein you need to import the wsdl under external definitions.
Like it should be cabable of receiving as attachments ?
Yes, it should be. This will help in creating one.
/people/baris.buyuktanir2/blog/2007/03/06/how-to-create-a-web-service-with-attachments-soap-with-attachments
Is there anything i need to do in Repository part ? If your sender sends the file as attachment using the option "Addition files", then the message will be forwarded directly with attachment to soap receiver. There would be no need for any additional setting in repository.
Regards,
Prateek

Problem with SOAP Adapter receiver not receiving the proper string

Hi friends
I have a very simple scenario as follows using SOAP Syncronous Call
SENDING SCENARIO
================
ExternalClient --> SOAP ADAPTER --> XI -> RFC ADAPTER --> ZBAPI
RECEIVING SCENARIO
==================
ZBAPI --> RFC ADAPTER --> XI --> SOAP ADAPTER --> ExternalClient
Here External Client is sending a search ID and ZBAPI searches for that record and send the FirstName and LastName.
I am using external Definitions in XSD format as follows.
INPUT XSD is
=========================================
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://cincom.com/xi/socrates/customerSearch" targetNamespace="http://cincom.com/xi/socrates/customerSearch">
 <xsd:element name="ZBAPI_GET_NAME">
 <xsd:complexType>
 <xsd:all>
 <xsd:element name="ID" type="xsd:integer" minOccurs="0" />
 </xsd:all>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>
===========================================
Reciving XSD file has
==============================================
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:socrates.cincom.com" targetNamespace="urn:socrates.cincom.com">
 <xsd:element name="ZBAPI_GET_NAME_RESPONSE">
 <xsd:complexType>
 <xsd:all>
 <xsd:element name="ADDRESSDATA" minOccurs="0">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="FNAME" minOccurs="0">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="20" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="LNAME" minOccurs="0">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="20" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 </xsd:all>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>
=========================================================
I HAVE TESTED THE ZBAPI AND IT WORKS WELL ON ITS OWN. ALSO I HAVE TESTED THAT THE MESSAGE SENT FROM OUTSIDE CLIENT IS REACHING BAPI. HOWEVER WHEN I GOTO 'SXMB_MONI' AND CHECK THE
XML STRING THAT THE RECIEVER IS GETTING, I SEE JUST THE FOLLOWING TWO LINES
===================================
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:ZBAPI_GET_NAME_RESPONSE xmlns:ns1="urn:socrates.cincom.com" />
======================================
IF YOU NEED ANY FURTHER INFO, PLEASE LET ME KNOW.
HOPE SOME ONE CAN GUIDE ME WITH THIS PROBLEM.
THANKS IN ADVANCE
RAM

Ram
Can you pls. confirm whether the mapping of your XSD fields & BAPI fields are in same sequence. I mean hierarchy is same or not.
Just to verify, as you said you are using Sync scenario that means you are using ONE Sender Soap & ONE Reciever RFC adapter.
Regards
Lalit

Sender SOAP Adapter Security Issue

Hi All,
We are building a SOAP to proxy scenario. The sender is a SOAP Adapter and the receiver is Proxy. The SOAP WSDL and URL is provided to the legacy system. When the legacy system is trying to send the data using the WSDL and the URL provided, they are receiving a dialog box to enter the user name and password. We can create a system user and provide those credentials to the legacy system. However, the legacy folks are not interested in including this in their web service.
Could you please suggest, if there is a way to create the web service such that it wouldn't request for user credentials? Something like no authorizations in the web service?
Thanks,
Manohar Dubbaka.

Hi Preeti,
Thanks for the response. Since we are on PI 7.0, I believe the setting that you are referring to should be on Visual Admin. Could you please let us know the parameter or the setting that needs to be changed in VA?
I am not sure, how we can make use of SSO to prevent them from entering the user credentials. Your help in this regard would be much appreciated.
Thanks,
Manohar Dubbaka.

Soap Adapter - XI_J2EE_ADAPTER_XI_HANDLER Error

Hello,
we have a very informative error here for
SOAP outbound adapter:
Sending to the SOAP-Adapter address ..../SOAP_Adapter/MessageServlet.... with the test tool in RWB we have this error:
Error category: XI_J2EE_ADAPTER_XI_HANDLER
Error code: GENERAL_ERROR
No entries in SXMB_MONI (of course!)
No idea, what has gone wrong!
Scenario is completed in ID!
What could be possible problems related to this fantastic error message?
We are on SP17,
Comm.channel monitoring shows no errors! (green light)
Best regards
Dirk

Hi Dirk,
can u see any messges in Message monitor on the RWB.
If yes, can u check the audit log and see what the problem is?
Regards
Sunita

Soap adapter: string transformations issues

I have a difficult issue:
I want to send a SOAP message to a thirdparty environment ,this environment requieres a special format of the message XML to String; iu2019ll put a sample:
< SOAP:Body >
< ns0:application xmlns:ns0=u201Dhttp://xxxxxx/yyyyyyy.com/zzzzu201D >
< in0>
< inputMessage >
< request>name </request >
< versionMsg>x.0
u2026u2026u2026u2026..
< /parameters >
< /inputMessage>
This is the meesage that i process with PI. Then when it arrives to the other environment should be as this one, i'll write wrong the chars because the web change it in code...:
u201C< SOAP:Body >
< ns0:application xmlns:ns0=u201Dhttp://xxxxxx/yyyyyyy.com/zzzzu201D>
< in0>
& lt inputMessage& gt
& lt request & gt name& lt /request& gt
& lt versionMsg& gt x.0& lt /versionMsg& gt
etc etc etcu2026u2026.u201D
I have changed it in the mapping, it's something easy to map a source structure ot a target whit a string field and mark Return as XML in the source field. that's ok.
But now is the problem: The SOAP adapter changes all the '&' in differents chars as:&|#|34 (i separate whit |in this sample) or the tag > or < in other ascii chars.
Some one knows what can i do? i have tried too whit the last post, the module config for SOAP adapter: strictXML2PlainBean but it doesn't work.
Any help will be appreciated.
Best regards and thanks in advance.
Thanks in advance and best regards.

No, the problem is that the SOAP adapter does the escaping of these chars, so i can't control it. I am trying to deploy a EAR in the server, but i guess that an easiest way should exist for this case.
The main problem is that the thirdparty system has an filter and this kind of chars are not allowed, this system only understand & lt and & gt in the string field.
Thanks anyway
Edited by: Cantabria on Mar 18, 2010 3:07 PM

Is there a way to see the string returned by SOAP adapter at the Reciever

Hello Friends
I have a scenario as follows
Sender:        Outside Client   -
>> Soap Adapter   -
>XI   --->   RFC Adapter   ---> ZBAPI.
The outside client sends an id to search through XI using SOAP adapter which inturn calls a ZBAPI
to look for the record in the table and sends the found record back to XI and from there to the outside client via SOAP adapter.
I have made sure that the ZBAPI is being contacted successfully.
However, the return data is not coming to the client.
Is there a way to findout what xml string is being received at the receiver SOAP adapter.
I have checked the zbapi, mapping etc., and everything is ok.
Any suggestion or feedback will be highly appreciated.
Thanks
Ram

You should be able to see the Request and the response in SXMB_MONI.
Just make sure that synch logging is turned on in MONI. Add the entry LOGGING_SYNC with value as 1 in SXMB_ADM --> Integartion Engine Configuration.
Regards
Bhavesh

Login Module configuration for soap adapter ?

Hi Guys,
I have configured XISOAPAdapter for client certificate Authentication and i have created 1443 as the HTTPS port on the ABAP stack and defined this port in the instance profile.
Under SSL provider i have selected 50101 as the HTTPS port and the user mapping to the certificate works fine and i was able to login directly.
https://host:50101/XISOAPAdapter/MessageServlet - I was able to login with the user mapping to certifcate.
but when i try https://host:1443/XISOAPAdapter/MessageServlet - it is asking for the basic password authentication and the automatic login with the certifcate is not working. Our customer will be using this url to send messages to soap adapter.
under policy configurations for XISOAPAdapter, i have defined only clientcertificateloginmodule and define the rule as Rule1.getUserFrom=wholecert.
any help or suggestions would be appreciated.
Thanks,
Srini

Hi,
We also experienced that limitation when a vendor is connecting to our XI SOAP Sender Adapter. It is asking for basic username/password. What we did was to create a Generic XI user with a password on it and use SSL authentication at the same time. Our Scenario was PI --> XI --> SAP R3, with the PI system using an HTTP RFC destination with a Basic Logon and Active SSL option to connect to the same system as yours https://host:portnumber/XISOAPAdapter/MessageServlet
Let me know if this helped...
Regards,

XI / PI SOAP Adapter - MessageServlet not found / not responding

I am in trouble with XI SOAP Adapter. When I try to reach the MessageServlet ( http://host:port/XISOAPAdapter/MessageServlet ) I get the response that document dont exists. Why MessageServlet do not respond? Anyone can help me?
In my Adapter Monitor ( http://host:port/mdt/amtServlet ) I see about the SOAP adapter a grey status and the information: "SOAP Adapter Monitoring is now part of Channel Monitoring". This is not a problem, according to Suraj: "SOAP Adapter will become active only when you sent a message through that for atleast one time.")
See also these topics:
SOAP adapter installation and activation
Adapter monitoring: SOAP is grey although it is used?
how can i enable SOAP Adapter?
https://websmp208.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012003146900000286382005 (SAP Note 856597)
 I have readed these topics (and others), but my problem seems to be a little different.

My XI runtime cache contents (SXI_CACHE) are up-to-date.
Information of some of my XI components:
Software Components
Vendor Name Version Location Applied
sap.com SAP-JEE 6.40 SP17 (1000.6.40.17.0.20060516064307) SAP AG 20060612185606
sap.com SAP-JEECOR 6.40 SP17 (1000.6.40.17.0.20060516064111) SAP AG 20060612185559
sap.com NWMADMIN 6.40 SP17 (1000.6.40.17.0.20060515153837) MAIN_APPL63VA_C 20060612185601
sap.com SAP_XITOOL 3.0 SP17 (1000.3.0.17.0.20060504222004) SAP AG 20060613105756
sap.com SAP_XIPCK 3.0 SP16 (1000.3.0.16.0.20060220233019) SAP AG 20060612185556
sap.com LM-TOOLS 6.40 SP17 (1000.6.40.17.0.20060417111655) MAIN_APPL63VA_C 20060612185603
sap.com SAP-XICONS 3.0 SP16 (1000.3.0.16.0.20060220232901) SAP AG 20060612185600
sap.com SAP-XIAFC 3.0 SP12 (1000.3.0.12.5.20050712085155) SAP AG 20060612185555
sap.com SAP_XIAF 3.0 SP17 (1000.3.0.17.0.20060522230043) SAP AG 20060613103623
sap.com SAP_JTECHF 6.40 SP17 (1000.6.40.17.0.20060516064445) SAP AG 20060612185559
sap.com SAP_JTECHS 6.40 SP17 (1000.6.40.17.0.20060516064629) SAP AG 20060612185606
sap.com com.sap.aii.af.mp 3.0 (3.0.1720060522104934.0000) SAP AG 20060613102037 sap.com/SAP-XIAFC 
sap.com com.sap.aii.af.soapadapter 3.0 (3.0.1720060522104934.0000) SAP AG 20060613103506 sap.com/SAP_XIAF
Thanks a lot! If you need other information, please, let me know.
Ivan, from Brazil

"https://websmp208.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012003146900000286382005 (SAP Note 856597)
I have readed these topics (and others), but my problem seems to be a little different."

SOAP adapter using HTTPS

We need to using SSL over HTTP for our web service defined in PI, basically using HTTPS in our SOAP adatper. I did a lot of research on this, seems like it's not an easy job to enable SSL. However I am only interested in making it work from an application developer point of view, enabling SSL, generating/installing certificate is a job for basis people.
So I created an sender CC with SOAP adapter with HTTPS with client authentication. (BTW, what is HTTPS without client authentication, does it mean HTTPs with server authentication where the server certificate is to be installed at the client side?), to my understanding, the client certificate should be installed in NWA (We have PI 7.1, not 7.0 -) and somewhere in ID (like sender agreement) we need to specify which client certificate should be used to authenticate the client who calls our service. However nowhere in ID I can specify which client certificate should be used for the defined sender CC. So how would it work in runtime? When my web service is called, which client certificate does PI use to authenticate the client?
It'd very much appreciated if you could give more information about how HTTPS for SOAP adapter works? I've done lot of research on this, but still confused.
Thanks

Hi,
for transport level security you should assign the HTTPS connection created in SM59 to the SOAP communication channel.
The HTTPS connection should use the certificates imported in t-code STRUST.
1. You have to dounload the SAP cryoptographic librariers.
2. Set the specific paramerts in RZ10
3. Maintain the enviornmental variables & you need to keep the logon tickets too in some specific directory.
4. Import the client & server certificates into STRUST.
You can find some documents on ABAP ssl configuration from the SDN library .... I don't have a link now
Regards
Sunil.

PI 7.1 problems publishing a WSDL of a sender soap adapter

We have upgraded our dev system from XI 3.0 to PI 7.1 and now I'm facing a problem with SOAP adapter. I have searched for answers here for a while but couldnu2019t find them. That why I start an own thread.
I thought with PI 7.1 it is very easy to publish the WSDL of SOAP adapter respectively a sender agreement. All you have to do is to choose your sender agreement and select the menu item "display WSDL" There you can get the WSDL and a WSDL URL. So it would be possible to deliver this URL to my partners. But while checking this URL respectively the delivered WSDL I've found a problem.
First of all the the WSDL URL doesn't look really good:
http://<server>:<port>/dir/wsdl?p=1_1ce2e954fe9632818bfff6c32f370748_portTypeBindingService
But it works. If I call this URL with a browser or with XML Spy I get the correct WSDL. Any chance to get a better readable URL?
The next thing is the proposed soap:address location in the WSDL. It has the following form:
http://<server>:<port>/XISOAPAdapter/MessageServlet?senderParty=&senderService=MYSERVICE&receiverParty=&receiverService=&interface=MYINTERFACE&interfaceNamespace=MYNAMESPACE"
If I compare it with the documentation i can see that the URL is completely different.
http://help.sap.com/saphelp_nwpi71/helpdata/en/43/951aceb1146353e10000000a11466f/frameset.htm
But again if it works all is fine but it doesn't work at least it doesnt work with XML Spy. The reason is the use of "& a m p ;" instead of only "&".
If I create a SOAP request with XML Spy an sent it to the XI I get the following error message: " Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=null;TS=null;AN=null;ANS=null;"
But if I change the SOAP request parameters replacing all the "& a m p ;" with "&" then it works.
Any chance to manage this? If I provide a WSDL on this way I want that my partners can use this "out of the box"

Kulwant
Yes of course I can change that manually but therefore I have to save the WSDL to my local hard disc, change the WSDL and send it to my partner via mail. This is exactly the way I've done this till now. But with PI 7.1 I like to use the new opportunities.
Bhavesh
I have also no Service Repository till now. That's the reason why I want to use the way described in my initial post.
In PI 7.1 you can open the corresponding sender agreement of you SOAP adapter. There you find a menu item "display WSDL". If you choose this you get a window which displays the correct WSDL and an URL where you can find the WSDL too. If you copy this URL to a browser you get the same WSDL too.
http://help.sap.com/saphelp_nwpi71/helpdata/en/31/daa0404dd52b54e10000000a1550b0/content.htm
First part of my question is regarding to this URL. The URL has a strange format.
The second part is regarding to the form of soap:address in this generated WSDL. Here I have problems with the use of this "& a m p ;" string. But I have no influence on it. If I deliver my partners the obove mentioned URL to the WSDL and the WSDL contains this soap:address URL my partner will probably have the same problem like I with my XML Spy.
Gaurav
I don't understand you answer. I know the correct soap address but the IB tool generates it with this "& a m p ;" string instead of only "&". Thatu2019s the point. No idea if and how I can handle this.
But thank you for the note number. Was helpful. The number is in the online documentation too but I've read over it.
To bad that the online documentation isn't correct regarding to the soap address. But believe me the German version is even worse. There you can find the two soap adapter settings (XI parameter: interface namespace, interface) that are no longer existed in PI 7.1
Now I will test if a .NET application can handle this soap address correctly.
Edited by: Gil Ritter on Nov 14, 2008 11:25 AM

Problem sending to XI soap adapter

Similar Messages

Maybe you are looking for