SOAP adapter redirecting 50000 port posts to 50001 automatically

Hi,
We have the SSL provider activated because we do encrypted messaging with external partner, but we also have internal systems posting via the SOAP adapter without SSL. They are trying to do this via port 50000, but since SSL is active, the message is redirected to 50001. This normally would not be an issue, except, they do not have port 50001 open on the firewall of the internal system sending the message and it is blocked, is there a config setting to NOT automatically redirect messages to 50001?
But acept them via 50000 and 50001.
Thanks,
Chris

Its technically possible to use same port but it may give usability issues in long run. It would be better if you could opt for different ports. During https enabling, the SSL port is identified and the traffic will always use that port. You Might need to disable and re-enable the settings.
Regards,
Prateek

Similar Messages

SOAP adapter: WSDL issue

Hi Experts,
I am working on File-XI-->Mail scenrio using SOAP adapter. My file contains only one line fields say:
TATA 407
I have configered File adapter perfectly and CC of it is showing perferctly green (Data is coming in MONI). On the counter SOAP side, I would like to send this file to the Gmail. But I am not able to do this due to the fact that I am not understanding the WSDL ? I have read several doucments but not one is giving the perfect idea about it.
Please tell me how to accomplish it. Please avoid to send the links. Please help ASAP.
-=Soniya=-

Hi Soniya,
>>I do agree that Mail adapter can be used in place of SOAP
No, it's not that.
SOAP and Mail adapter are two different things. SOAP adapter is used to exchange SOAP messages (do not confuse "message" with "email message") between applications (XI/PI to third pary OR third-party application to XI/PI) using SOAP/HTTP protocol. Whereas Mail adapter is used to send email using IMAP/POP3 protocol.
>>Somebody is saying that Webservices are the one, where you send your messages either side people are saying.
Correct. You can configure SOAP adapter as sender in PI and receive SOAP messages in PI sent by some third-party application. OR you can configure SOAP adapter as receiver and post the message form PI to some third-party provided URL.
For exposing webservice from PI all you need to do is to go to Integration directory. Select the sender aggrement you want to puslish as web service. From TOOLS menu say display WSDL. Save this WSDL and provide it to client/third-party application. They will have to generate the client proxy class and post the message from there to PI.
For cosuming webservice in PI (posting message from PI), third-party application has to provide you with a URL which you will enter into SOAP receiver type adapter.
Regards.

Question: SOAP Adapter

Hello friends,
I have a question on soap adapter.
I am trying to convert an IDoc into an XML and then using SOAP adapter i want to post that XML into a web service.
I searched many threads but without much help.
Can anyone of you guide me as to how to go about this problem?
Thanks,
Lakshmi

Hello lakshmi,
Although i don' have a link to Blog, but here are the steps.
1. Import the source idoc in to the external defintions from the source system.
2. Import targer Webservice WSDL
3. Create target message interface using Message Type from WSDL. You don't need to create sorce message interface as this will be the IDOC interface itself.
4. Create message mapping and Interface mapping as needed beteen source and target. remeber that you will be calling webserice asynchronously.
5. In the ID, create Interface determination, receiver determination. You will not need any sender agreement. Ask Basis guys to include a new partner profile in source system sending IDOC for Your XI system.
These are just basic steps.
Let me know if you need any elaboration.
SOAP adapter configuration link:-
http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
Thanks
-Kulwant
Assign Score if useful
Edited by: Kulwant Bhatia on Dec 23, 2008 4:23 PM

SOAP adapter: port, logging/tracing, http/https

Hi,
several questions concerning SOAP adapter:
SAP XI 3.0 SP19 used.
Scenario 1:
SOAP request adressing J2EE port
http://host:8000/XISOAPAdapter/MessageServlet?channel=Partner:Service:SOAPSenderChannel
Scenario 2:
SOAP request adressing ABAP port
http://host:50000/XISOAPAdapter/MessageServlet?channel=Partner:Service:SOAPSenderChannel
Question 1:
What happens with a SOAP request adressed to the ABAP port?
Obviously it is forwarded to the J2EE port but where is this forwarding function documented
and is it allowed in every case to send SOAP messages to ABAP port?
Question 2:
What logging and tracing functionalities do i have in both scenarios before the message enters (before RWB)?
E.g. where can i see unsuccessful requests (e.g. if there is mistyping in SenderChannel).
Then it not visible in Runtime Workbench but whereelse?
If the ABAP port is adressed i see something in SMICM trace file, but very cryptic and not conclusive.
Do you know further trace/log files for both scenarios (Visual Admin?) ?
Question 3:
What is the difference if https is used concerning logs and traces?
Do i have more or less possibilities?
Thank you very much in advance for comments.
Michael

Hi
The URL sent to the ABAP port and the J2EE port are different.
The URL to the ABAP port is documented in this blog by Stefan,
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
http://<server>:<ABAP-port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface>
Answering question 1 --> As the URL are different, the Request in case of the ABAP stack hits the Integration Engine directly - into the pipeline of XI and bypassed the Adapter Engine competely.
As stefan's blog states - you cannot post multipart SOAP request to the IE directly.
Question 2 - If the URL is incorrect, if the request hits XI then you will have the log in XI ( in MONI in case of ABAP port ) and in RWB -Message Monitroing ( in case of J2EE port)
Regards
Bhavesh

Exception while posting a message using SOAP adapter

Hi
We are getting the following message while posting a SOAP request through SOAP adapter through Http Client. The error message is
<SAP:Error>
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code>MESSAGE.GENERAL</SAP:Code>
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML</SAP:AdditionalText>
</SAP:Error>
Please help in this regard.
Regards
Ramesh

Dear Gopal,
I am trying from HTTP->WEB SERvice (R/3 system)
I have created a webservice from RFC.
Receiver Adapter type : SOAP
USer authentification provided
URL provided. i picked from wsdl file
i am getting this error
com.sap.aii.af.ra.ms.api.DeliveryException : invalid content text/html.
I hope u trouble shooted this kind of error.
can u provide me some clues.
regards
chandra
Message was edited by:
chandra shekar dasari

HTTPS Port for SOAP Adapter PI 7.1 (XI)

Hello Colleagues,
we plan to configure an Sender SOAP Adapter (without SOAP envelope) as HTTPS message receiver with HTTP Security Level "HTTPS with Client Authentication".
Does anyone know if this works and which port will be used. For my understanding it must be 443.
If not, it's possible to change the port to 443?
Regards,
Jochen

Hi Prateek,
many thanks!
Where can i do the port change?
Many thanks in advance!
Regards,
Jochen

SOAP Adapter (Ports and Interfaces)

Is it true that for every single interface, a new soap adapter needs to be configured? Can one soap adapter handle many interfaces?
Do I need one port for each interface or can I use one port for multiple interfaces. (note, I am using Soap Adapter)
Thanks in advance for your responses

When you are talking about "ports", I assume, that you are using the J2SE Adapter Framework.
Yes, you need a seperate Soap Adapter module (or in XI 3.0 J2EE Adapter Framework a seperate channel) for each interface and for each SOAP Adapter Module you need a different port.
Regards
Stefan

Redirect from port 80 to 50000

Can someone point me at some sample code or documentation to show how calls on Port 80 (internet) can be redirected to port (port 50000) without problems in things like dynamic menu. Assume portal EP6 stack 09.
Thanks

Run the Web Dispatcher. This URL can help you out.
http://help.sap.com/saphelp_nw04/helpdata/en/f5/51c7d170bc4a98b1b5a0339213af57/frameset.htm
The easiest way to config the Web Dispatcher is to run sapwebdisp -bootstrap at which point it will ask the following:
Message server hostname
HTTP Port of the message server: Which is 81 system number of the SCS
System Number for the Web Dispatcher: Pick a number your not using
HTTP Port of the Web Dispatcher: You would want port 80 but you can set it to anything.
I have been using this for EP 6.0 SR1 and I have not had a problem.

SOAP Adapter in XI 3.0 (Central Engine, not J2SE Adapter)

Hello,
I am trying to get the demo (flight availablity check) work via SOAP, so that it can be called from .NET. I created a communication channel with sender SOAP adapter (and adapter engine as Integration server, http://sap.com/xi/XI/Demo/Agency as interface namespace and FlightSeatAvailabilityQuery_Out as interface name)
When I post it to XI
http://xxxxxx:8000/sap/xi/engine?type=entry&version=3.0&Sender.Service=XX1_205&Interface=com.sap^FlightSeatAvailabilityQuery_Out&QualityOfService=BestEffort&ProcessingMode=p&MessageClass=RQ
with soapaction http://sap.com/xi/WebService/soap1.1
and
<?xml version="1.0" encoding="utf-8" ?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<FlightSeatAvailabilityQuery xmlns="http://sap.com/sapexamples">
<FlightID xmlns="">
<AirlineID>LH</AirlineID>
<FlightDate>2004-12-01</FlightDate>
</FlightID>
</FlightSeatAvailabilityQuery>
</soap:Body>
</soap:Envelope>
I get just
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
</SOAP:Body>
</SOAP:Envelope>
Any idea why this does not work. The plain HTTP adapter (to /sap/xi/adapter_plain) works ok.
Thanks
siva

Post your message to following URL:
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
port is the J2EE port 50000 in your example.
Check the newest manual for further details.
Regards
Stefan

Error in Receiver Soap Adapter for Google API

Hi,
I am working on HTTP-XI-Soap scenario which on the receiver side calls google API for spell check.
I get the following error : No Deserializer found to deserialize a ':key' using encoding style 'http://schemas.xmlsoap.org/soap/encoding/'.
However if I try calling the webservice individually using SOAP Client it works fine and do get desired response.The soap message that is sent by the client to the target URL is :
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:GoogleSearch" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Body>
 <urn:doSpellingSuggestion soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
 <key xsi:type="xsd:string">qXWD4x1QFHIo/dePqlYOLwT7kMmkv80E</key>
 <phrase xsi:type="xsd:string">Bratney</phrase>
 </urn:doSpellingSuggestion>
 </soapenv:Body>
</soapenv:Envelope>
However if i remove the "xsi:type="xsd:string" part from the element 'phrase' and 'key' it returns the same error as it does while using with XI.
Hence I am assuming that that the outgoing soap message elements need to have the above highlighed attribute.
Now I want to have this attribute(xsi:type="xsd:string) in the soap message that is sent from XI.
My question is , Is there any setting using which I can add the attributes in the above form to the outgoing message from XI.I do not want to use a adapter Module.
Thanks & Regards,
Sidharth

Hi Sidharth,
You post here the soap message that is sent by the client to the target URL, but did you look to the soap message that is sent by XI?
Try the AF monitor http://<host>:<j2ee-port>//MessagingSystem/monitor/monitor.jsp?
Because XI soap adapter doesn't support all tags of wsdl rpc-based, we need to adjust them...
Look to the SOAP FAQ (SAP note number 856597) under question "Can I convert an RPC styled WSDL to a document styled WSDL?"... Look at last but one paragraph ;o)
So, you need to change this attribute to one that it is compatible...
Go to http://service.sap.com/xi > Media Library > Documentation and there you will find this xls document -> SAP XI 3.0 (SP11) - Supported XML Schema and WSDL (EN) in this document you have all the compatible elements of wsdl for XI.
One more thing, you can adjust your soap request and change or add the required tags You can do it with xslt-mapping or create your won data types in XI without import the WSDL generated by google.
Hope it helps,
Ricardo.
Message was edited by: Ricardo Quintino

SOAP adapter in PI 7.1

Hello, expert,
I have made SOAP adpeter work in PI 7.0, however after upgrading to PI 7.1, I have issue with a test scenario as following.
I've defined DT, MT and SI (Service Interface) in ESR (no mapping needed)
In ID, I configured a scenario SOAP --> PI --> File.
I tested the scenario in RWB using the test tool for adapter engine using URL:
http://host:port/XISOAPAdapter/MessageServlet?channel=:BC_comp:CC_Notification_SOAP_Sender
the message is attached in the end of this post.
The message was successfully send to PI and saved to file, however the message going into IE pipeline and finally saved to the file is not the one I sent.
Message sent to SOAP adapter:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Notification xmlns:ns0="http://mynamespace/xi">
 <Notification>
 <Number>12345</Number>
 <Type>abc</Type>
 <Status/>
 <OrderNo/>
 <FunctionalLocation>qaz</FunctionalLocation>
 <StartDate/>
 <EndDate/>
 </Notification>
</ns0:MT_Notification>
Message going into IE pipeline and further saved to file:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<sap:Manifest xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink">
<sap:Payload xlink:type="simple" xlink:href="cid:payload-29092409f6d11ddc4d982a0c41f100csap.com">
<sap:Name>PayloadName</sap:Name>
<sap:Description>PayloadDescription</sap:Description>
<sap:Type>Application</sap:Type>
</sap:Payload>
</sap:Manifest>
Also in sxmb_moni, there is a acknowledgement which do not expect.
Does anybody have an idea how this happens?
Thank you
Jayson

Hi!
I want to answer this thread as 2 parts:
1. First check all of your configuration whether you have done...correctly or not later please activate all of your objects...
then try your Scenario once..if not do one thing..
2:
I my sugestion is Why don't you try yourr scenario by using either SOAP CLient Tool or else ALTOVA XML SPY TOOL...
Here I am provding the Steps to be followed to use ALTOVA XML SPY Tool
please make sure even though you have done correctly..
Steps for Testing via ALTOVA>>
1. Go to ID-> TOOLS-> Define Web Service
2. Give following URL in following window
For without Party:
note: http://<HOST name:5<Port>00/XISOAPAdapter/MessageServlet?channel=:<Channel Name>:<Adapter Name>
3. Give Message Interface Name of Scenario
4. Give following details in following screens Service Name, Message Interface Name, Namespace
5. Finish & Save the WSDL in local folder to give to web-services
(Generated WSDLu2019s attached in Technical Design Document)
NOTE: AFter generating you can observe the above SOAP URL with your objects name...
6.Once the WSDL file is created. Use a SOAP client tool or else aither ALTOVA XML SPY Tool to create the SOAP request.
You can create SOAP Request from WSDL using the following tool
Once you have created the SOAP request, use the same as the payload and test the scenario.
7. Select the option in the SEND SOAP REQuest in the MENU present in the top list of ALTOVA XML SPy Tool and give inputs i.e., SOAP URL and also give server details and it will ask authentification details
8. Now by giving Authentification details you can send successfully....
9. Now Got SXMB_MONI and now check your scenario is success or not..
10. IF not go to MEssage monitoring in RWB and check at both the INtegration Server Level and ADAter engine level and then Check the AUDIT LOG
11. ALso you can check Audit log in COmmunication channel monitoring
12. If your SOAP Channel is in Red check Errors and then stop that channel manually and start once again and try the scenario once again...
http://help.sap.com/saphelp_erp2004/helpdata/en/ae/d03341771b4c0de10000000a1550b0/frameset.htm
I hope it will be useful to you in final case...Suppose if it is useful to you please close this and award points to the repective contributors if it is useful to you..
Regards:
Amar Srinivas ELi

SMIME in sender soap adapter

Hi,
I'd like to know the proper format of the POST request to a sender soap adapter with SMIME activated. I've found almost no documentation about it.
I'm trying to send a document ciphered to PI via soap adapter (HTTP POST). I've done the following steps
1. I activate SMIME in the sender soap adapter, and I specify "Decrypt" as the security procedure in the sender agreement. I also incorporate the private key in the keystore DEFAULT and reference to it in the sender agreement.
2. I use OpenSSL to cipher an xml document like this (I use the public certificate associated to the previous private key) :
--> openssl smime -encrypt -in fich.txt -out fich_encrypted.txt certTesting.pem
What I get is:
MIME-Version: 1.0
Content-Disposition: attachment; filename="smime.p7m"
Content-Type: application/x-pkcs7-mime; smime-type=enveloped-data; name="smime.p7m"
Content-Transfer-Encoding: base64
MIIC....[base64 content of the file encrypted]
3. I use CURL to send the HTTP POST request to PI. Previously I get the binary file from the base64 content.
> POST /XISOAPAdapter/MessageServlet?senderParty=&senderService=BC_1[...]
> Authorization: Basic c2U[...]
> Host: pi.[...].com:50000
> Accept: /
> Content-Type: application/pkcs7-mime; smime-type=enveloped-data; name=fich_encrypted.der
> User-Agent: Jakarta Commons-HttpClient/3.1
> Accept-Encoding: text/xml
> Content-Disposition: attachment; filename=fich_encrypted.der
> Content-Length: 620
> Expect: 100-continue
but I get this error from the SOAP Adapter:
--> java.io.IOException: invalid content type for SOAP: APPLICATION/PKCS7-MIME.
I also get the same error if I remove the header Content-Disposition.
4. If I send the xml file without ciphering (header Content-Type: text/xml;charset=UTF-8) I get the error:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: call failed: java.lang.SecurityException: Exception in Method: VerifySMIME.run(). LocalizedMessage: SecurityException in method: verifySMIME( MessageContext, CPALookupObject ). Message: IllegalArgumentException in method: verifyEnvelopedData( ISsfProfile ). Wrong Content-Type: text/xml;charset=UTF-8. *Expected Content-Type: application/pkcs7-mime or application/x-pkcs7-mime*. Please verify your configuration and partner agreement
PROBLEM --> I really don't know what the SOAP sender channel is expecting when SMIME is activated. I've tried to send the binary file encripted as an attachment and also directly, but the soap adapter complains.
Thanks

HI,
for XI EP
Please see the below links so that you can have clear Idea..
/people/saravanakumar.kuppusamy2/blog/2005/02/07/interfacing-to-xi-from-webdynpro
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/java/integrating%20web%20dynpro%20and%20sap%20xi%20using%20jaxb%20part%20ii.article
Consuming XI Web Services using Web Dynpro Part II-/people/riyaz.sayyad/blog/2006/05/08/consuming-xi-web-services-using-web-dynpro-150-part-ii
Consuming XI Web Services using Web Dynpro Part I -/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
/people/sap.user72/blog/2005/09/15/creating-a-web-service-and-consuming-it-in-web-dynpro
/people/sap.user72/blog/2005/09/15/connecting-to-xi-server-from-web-dynpro
Regards
Chilla..

Error in Sender SOAP Adapter on XI 3.0 SP13

Hi All.
I have an application that sends a SOAP message to XI SOAP Adapter, to reach a synchronous interface. I've generated the .wsdl file from the Integration Directory, within the URL:
http://sapbox:59800/XISOAPAdapter/MessageServlet?channel=:BS_PORTAL:CC_S_SOAP_CREDITO
When I try to reach this URL, I get the successful response:
Message Servlet is in Status OK
I've also created the sender SOAP communication channel, fullfilling the default namespace and default interface correctly.
However, when I use wsnavigator client provided by SAP to prove the scenario, the SOAP message doesn't achieve XI, as the XISOAPAdapter EJB throws some exceptions:
HTTP/1.1 500 Internal Server Error
Connection: close
Server: SAP J2EE Engine/6.40
Content-Type: text/xml; charset=utf-8
Date: Sat, 17 Sep 2005 02:59:12 GMT
<?xml version='1.0'?>

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
 <context>XIAdapter</context>
 <code>BaseEJBException</code>
 <text><![CDATA[
com.sap.aii.af.mp.processor.ModuleProcessorException
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:278)
 at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
 at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:162)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:508)
 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:159)
Caused by: com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method process.
 at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:121)
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:227)
 ... 19 more
Caused by: java.lang.NoSuchMethodError: com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.setDynamicConfigurationMode(I)V
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.createXMBWSBubble(XISOAPAdapterBean.java:1129)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.setup(XISOAPAdapterBean.java:265)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:562)
 at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
 ... 20 more
 ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
I've already done something really similar on SP 9. Can it be a new problem from SP13? Does anyone has any idea?
Thanks in advance.
Deise Lima.

Hi Naveen,
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_WEBSERVICE:CC_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 or Altova XML Spy we are getting a 500 internal server error.
Am not sure what causes the error

How to use Basis Authentication in Sender SOAP Adapter

We implemented one Sender SOAP Adapter and we had to implement the modified WEB.XML method to remove the security specification. We have now asked the developer to correct this situation so we can remove this modification. The Interface developer would like to use Basic Authentication. If you have an automated interface sending in a SOAP Message, how do you do Basic Authentication?
I've tried using:
http://host:port/XISOAPAdapter/MessageServlet?channel=:<Service>:<Channel>&sap-user=xiappluser&sap-password=<Password>&sap-language=EN&sap-client=<Client>
When I do this, I still get the Authentication Pop-Up Window.
How does the Sending Interface either supply the ID and Password on the incoming SOAP Message or respond to the Authentication Pop-Up?
Thanks,
Anne

By Defualt the web service exposed by you will use Basic Authentication mode only.
But the way you do Basic Authentication in the web client is platfrom dependent.
This is not the way to do Basic authentication
http://host:port/XISOAPAdapter/MessageServlet?channel=:<Service>:<Channel>&sap-user=xiappluser&sap-password=<Password>&sap-language=EN&sap-client=<Client>
I am providing you a code snippet on how to Basic Authentication in Java when making the Web Service Call.
If the client is on some other platform just look for the corresponding api.
Please award points if you find this answer useful.
Code Snippet
URL url = new URL(URL);
URLConnection connection = url.openConnection();
if( connection instanceof HttpURLConnection )
((HttpURLConnection)connection).setRequestMethod("POST");
 //connection.setRequestProperty("Content-Length",Integer.toString(content.length()) );
 connection.setRequestProperty("Content-Type","text/xml");
 connection.setDoOutput(true);
 String password = User + ":" + Password ;
 //Where con is a URLConnection
 connection.setRequestProperty ("Authorization", "Basic " + encode(User + ":"+ Password));
 connection.connect();
Encode Method
public static String encode (String source) {
BASE64Encoder enc = new sun.misc.BASE64Encoder();
return(enc.encode(source.getBytes()));

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

SOAP adapter redirecting 50000 port posts to 50001 automatically

Similar Messages

Maybe you are looking for