Why SOAP Adapter Type is missing ?

Hi all, I'm following the WebLog Invoke Webservices using SAPXI (/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi) and I'm not able to use a SOAP Adapter.
In particular, when I try to select the Adapter Type I obtain the following list:
File
HTTP
IDoc
JDBC
JMS
Marketplace
RFC
RNIF
XI
Why SOAP Adapter Metadata is missing ?
Thanks in advance for your collaboration
Best regards
Gianfranco Bello

Hi, we're reimporting the SAP BASIS software component (XI3_0_SAP_BASIS_6.40_00_00.tpz).
The present our situation is:
SAP_JTECHF 6.40 SP11 (1000.6.40.11.0.20050221011822) SAP AG 20050425182200
sap.com SAP-JEECOR 6.40 SP11 (1000.6.40.11.0.20050221011406) SAP AG 20050425182155
sap.com SAP-JEE 6.40 SP11 (1000.6.40.11.0.20050221011617) SAP AG 20050425182238
sap.com SAP_JTECHS 6.40 SP11 (1000.6.40.11.0.20050221012022) SAP AG 20050425182237
sap.com LM-SERVICE 6.40 SP11 (1000.6.40.11.0.20050221012100) SAP AG 20050425182231
sap.com SAP-XIAFC 3.0 SP11 (1000.3.0.11.2.20050407085022) SAP AG 20050425212631
sap.com SAP_XIAF 3.0 SP11 (1000.3.0.11.1.20050324062550) SAP AG 20050425220610
sap.com SAP_XITOOL 3.0 SP11 (1000.3.0.11.3.20050405055844) SAP AG 20050425222949
But the SOAP Adatper still missing.
Is there a newly version to install ?
Regards
Gianfranco

Similar Messages

SOAP Adapter Metadata Missing

Hello,
The SOAP adapter metadata is missing from the http://sap.com/xi/XI/System namespace. All the others are present. How can we get the adapter ?
Does it come as part of some patch.
Regards,
Durga

Hi, we're reimporting the SAP BASIS software component (XI3_0_SAP_BASIS_6.40_00_00.tpz).
The present our situation is:
SAP_JTECHF 6.40 SP11 (1000.6.40.11.0.20050221011822) SAP AG 20050425182200
sap.com SAP-JEECOR 6.40 SP11 (1000.6.40.11.0.20050221011406) SAP AG 20050425182155
sap.com SAP-JEE 6.40 SP11 (1000.6.40.11.0.20050221011617) SAP AG 20050425182238
sap.com SAP_JTECHS 6.40 SP11 (1000.6.40.11.0.20050221012022) SAP AG 20050425182237
sap.com LM-SERVICE 6.40 SP11 (1000.6.40.11.0.20050221012100) SAP AG 20050425182231
sap.com SAP-XIAFC 3.0 SP11 (1000.3.0.11.2.20050407085022) SAP AG 20050425212631
sap.com SAP_XIAF 3.0 SP11 (1000.3.0.11.1.20050324062550) SAP AG 20050425220610
sap.com SAP_XITOOL 3.0 SP11 (1000.3.0.11.3.20050405055844) SAP AG 20050425222949
But the SOAP Adatper still missing.
Is there a newly version to install ?
Regards
Gianfranco

HTTP 415 Unsupported Media Type with SOAP adapter trying to put SOAP header

Hello,
I am trying to put data into soap header using soap receiver adapter. Seems like building the complete soap message is the right way to go. Thus I wrote a java program to build the complete soap message (soap envelop, soap header and soap body which contains the message PI received from the sender). Mapping program works well. However when I ran the scenario, I got Error "SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Unsupported Media Type" when calling the receiver's web service (the SOAP receiver adapter CC have the "Do Not use SOAP Envelop" checked). Anyone knows why I got this error? From google, seems like this error is because the http's content-type is set to other type, rather than "text/xml". However in soap CC there is no option to control this.
The message sent to the receiver is (after mapping);
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header>
<SOAP-SEC:Signature xmlns:SOAP-SEC="http://schemas.xmlsoap.org/soap/security/2000-12" MyAttr="value">My Test Value</SOAP-SEC:Signature>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<ns1:UpdateEquipment xmlns:ns1="http://mycomp.com/mywebservice">
<ns1:EquipmentNumber>000000012345</ns1:EquipmentNumber>
<ns1:LicensePlate>654321</ns1:LicensePlate>
</ns1:UpdateEquipment>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Anyone can help?
Thanks

When you check "Do Not use SOAP Envelop", the SOAP adapter chooses application/xml instead of text/xml.
You can change the content type with help of the MessageTransformBean. You put the bean in the module chain of the receiver channel and add the parameter Transform.ContentType = text/xml
See
http://help.sap.com/saphelp_nwpi71/helpdata/EN/57/0b2c4142aef623e10000000a155106/frameset.htm

SOAP Adapter missing payload on receiving web service

Hi there,
I'm having a problem with a File to (asynchronous) SOAP Adapter scenario that is currently baffling me.
I wonder if anyone out there has any troubleshooting ideas for this one?
The source message is being picked up OK and I can see from Communication Channel Monitoring on the Runtime Workbench that it is allegedly being delivered to the Web Service OK.
All the entries in the audit log point to a successful scenario and I can view the payload in the Message Content "payload" area.
However on the web service / server side the message is completely blank. Somewhere along the line the payload has gone missing.
I can copy and paste the payload manually into the web service test area and this is fine.
Any ideas/suggestions as to what could be happening with this or how I might go about troubleshooting it?
Many thanks
Ian

Thanks Bruno,
It looks like you were right...
In the end we used Wireshark - a packet sniffing application - to check what was actually hitting the destination server. We found that the content was arriving at the server but the web service wasn't accepting the format. The creators of the web service are now investigating why and will hopefully will advide me of the format error in the message. But at least I was able to prove that the message was getting there which was the focus of this query.
Regards
Ian

SOAPException: faultCode=SOAP-ENV:Protocol; msg=Missing content type

I have a WSDL file for which I have created a Web Service stub/skeleton through jdeveloper(version 10.1.2.3.0). Below is the complete code which has been generated by developer. Now whenever i try to run this file in jdeveloper I get the following exception. Please let me know how to resolve this issue.
Also error message is received at the following line of code:
*msg.send(endpointURL, ""<<some URL>>", requestEnv);*
{code}
*Exception Message*
{code}
[SOAPException: faultCode=SOAP-ENV:Protocol; msg=Missing content type.]
at org.apache.soap.transport.TransportMessage.read(TransportMessage.java:249)
at oracle.soap.transport.http.OracleSOAPHTTPConnection.post(OracleSOAPHTTPConnection.java:973)
at oracle.soap.transport.http.OracleSOAPHTTPConnection.send(OracleSOAPHTTPConnection.java:722)
at org.apache.soap.messaging.Message.send(Message.java:125)
at mypackage.NPVNSDLStub.PANDetails(NPVNSDLStub.java:88)
at mypackage.NPVNSDLStub.main(NPVNSDLStub.java:41)
{code}
*Code generated by Jdeveloper*
{code}
package mypackage;
import oracle.soap.transport.http.OracleSOAPHTTPConnection;
import org.apache.soap.encoding.SOAPMappingRegistry;
import org.w3c.dom.Element;
import java.util.Vector;
import oracle.jdeveloper.webservices.runtime.WrappedDocLiteralStub;
import java.net.URL;
import org.apache.soap.Envelope;
import org.apache.soap.Body;
import org.apache.soap.messaging.Message;
import java.util.Properties;
* Generated by the Oracle JDeveloper 10g Web Services Stub/Skeleton Generator.
* Date Created: Wed Feb 29 18:39:33 IST 2012
* WSDL URL: file:/C:/WS/sample.wsdl
public class NPVNSDLStub extends WrappedDocLiteralStub
public NPVNSDLStub()
m_httpConnection = new OracleSOAPHTTPConnection();
public static void main(String[] args)
try
NPVNSDLStub stub = new NPVNSDLStub();
stub.PANDetails("aaaaa8888a");
catch(Exception ex)
ex.printStackTrace();
private String _endpoint = "<<some URL>>";
public String getEndpoint()
return _endpoint;
public void setEndpoint(String endpoint)
_endpoint = endpoint;
private OracleSOAPHTTPConnection m_httpConnection = null;
private SOAPMappingRegistry m_smr = null;
public String PANDetails(String Request) throws Exception
URL endpointURL = new URL(_endpoint);
Envelope requestEnv = new Envelope();
Body requestBody = new Body();
Vector requestBodyEntries = new Vector();
String wrappingName = "PANValidationRequest";
String targetNamespace = "<<namespace url>>";
Vector requestData = new Vector();
requestData.add(new Object[] {"Request", Request});
requestBodyEntries.addElement(toElement(wrappingName, targetNamespace, requestData, false));
requestBody.setBodyEntries(requestBodyEntries);
requestEnv.setBody(requestBody);
Message msg = new Message();
msg.setSOAPTransport(m_httpConnection);
*msg.send(endpointURL, "<<some URL>>", requestEnv);*
Envelope responseEnv = msg.receiveEnvelope();
Body responseBody = responseEnv.getBody();
Vector responseData = responseBody.getBodyEntries();
return (String)fromElement((Element)responseData.elementAt(0), java.lang.String.class);
{code}
Edited by: EJP on 2/03/2012 17:22: added code tags, but your indentation needs fixing

Kishore,
See the links referenced in these threads.
Web Services and R12
Re: Web Services and R12
Integrated SOA Gateway
Re: Integrated SOA Gateway
Regards,
Hussein

SOAP adapter Using XI 3.0 error: invalid content type for SOAP: TEXT/HTML

Hi All,
I have the scenario to send a message to proxy via SOAP adapter . My PI server is 7.3 and my BI application server also 7.3. I have created service interface in the ESR and created the ABAP proxy in the Application server. Im using the receiver SOAP adapter with message protocol as XI 3.0. Am running this scenario in the central adapter engine. (That is i didnt create integrated configuration). I am facing the issue in the receiver SOAP channel as 'invalid content type for SOAP: TEXT/HTML: 401 Unauthorized'. But i can able to login into the URL which is given in the channel using the username and password used in the channel.
Can you please let me know if any addtional settings need to be done in PI side.
Regards,
Ramalakshmi.G

Hi,
Thanks for your reply. I have done my scenario with the integration configuration. Still i am facing the same issue " SOAP: TEXT/HTML; HTTP 401 Unauthorized". I have given the correct URL, username and password. Is this enough to connect to the receiver integration server from AE. Any settings need to be do in the receiver ABAP system and PI system. If so please share the corressponding note for the same. What should be the role is assigned to the userid given in the channel.
I have used sproxy to create the proxy in the receiver ABAP system. In PI i am using the SOAP adapter with XI 3.0 ,message protocol to call to this proxy. I have not done any settings in any of the servers. Do i need to do any settings.
Regards,
Ramalakshmi.G

Why i get different Adapter type in my alert

HI,
I've configured an alert for XML validation at Adapter engine level in PI 7.1. My scenario is Soap to JDBC.
When i seen my Alert in my inbox, the Adapter type i got it as : XIAdapter and it is supposed to SOAP Adapter.
Can you guys have any guess....?
Thanks
Prabhakar

any guess?

HTTP 415 Unsupported Media Type with SOAP adapter ?

Hello All,
Iam getting HTTP 415 Unsupported Media Type with SOAP adapter error while executing the scenario.
i got one thread which have the solution. iam not getting exactly how to write message transform Bean.
HTTP 415 Unsupported Media Type with SOAP adapter trying to put SOAP header
Please tell me where i need to write the MessageTransformBean at sender adapter or receiver file adapter.
Thanks and regards,
chinna

Hi Chinna,
Have you checked this
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
Regards
Ramesh

SOAP Adapter: Content Type Issue in WebServices via HTTP

Hi,
I have configured a Receiver SOAP adapter. When i had to test the message i had an HTTP 415 error.
i found that the sender SOAP adpater that received this message is not capable of handling Content-Type: Application/XML i.e. which is being transmitted by the Receiver SOAP Adapter.
Please let me know how to configure in the Receiver SOAP adapter so that the HTTP Content-Type would be TEXT/XML instead of Application/XML .
Thanks in Advance,
Venkatesh

Hi Michal,
I have created a Web service for a RFC function Module. The webservice is available in SOAMANAGER.
It got activated also . But whenever I tried to test, I am getting the below error,
"Message Envelope not found. Probably Empty SOAP message"
 Request:
 POST /sap/bc/srt/rfc/sap/yotci_i015_linkp8sap/100/yotci_i015_linkp8sap/yotci_i015_linkp8sap HTTP/1.1
Host: sapkrftewd01.krft.net:8030
Content-Type: text/xml; charset=UTF-8
Connection: close
Authorization: <value is hidden>
Content-Length: 657
SOAPAction: ""
<?xml version="1.0" encoding="UTF-8" ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Header><sapsess:Session xmlns:sapsess="http://www.sap.com/webas/630/soap/features/session/"><enableSession>true</enableSession></sapsess:Session></SOAP-ENV:Header><SOAP-ENV:Body><ns1:YotciI015Linkp8sap xmlns:ns1='urn:sap-com:document:sap:soap:functions:mc-style'><IvParam1>POD</IvParam1><IvParam2>00006095</IvParam2><IvParam3>01/14/2009</IvParam3><IvParam4>PDF</IvParam4></ns1:YotciI015Linkp8sap></SOAP-ENV:Body></SOAP-ENV:Envelope>
 Response:
 HTTP/1.1 500 Message E 1S 406 cannot be processed in plugin mode HTTP
content-type: text/xml; charset=utf-8
content-length: 0
accept: text/xml
sap-srt_id: 20090224/141936/v1.00_final_6.40/49A4677A2D0736EDE10000000A3597E9
server: SAP Web Application Server (1.0;700)
Is this because of "do not use SOAP envelope" check?
I didn't check this check box.
If that is the error could you please tell me how to see the "do not use SOAP envelope"?
Where can I find SOAP channel?
I am very new to SOAP concept.
One JAVA application is going to invoke this Webservice from SAP.
Please help me.
Thanks,
Bala.

IOException: invalid content type for SOAP: TEXT/ using Sender SOAP adapter

Hi all,
When I am using Sender SOAP adapter, i am getting (MessagingException: Could not parse XMBMessage. Reason: java.io.IOException: invalid content type for SOAP: TEXT/HTML using connection SOAP_http://sap.com/xi/XI/System) exception.
From my RWB I can see:
2009-05-25 16:18:39 Information The message was successfully retrieved from the call queue.
2009-05-25 16:18:39 Information The message status was set to DLNG.
2009-05-25 16:18:39 Error Failed to parse the XI system response.
2009-05-25 16:18:39 Error The message was successfully transmitted to endpoint com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIMessage creation failed (inbound). Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not parse XMBMessage. Reason: java.io.IOException: invalid content type for SOAP: TEXT/HTML using connection SOAP_http://sap.com/xi/XI/System.
2009-05-25 16:18:39 Error The message status was set to FAIL.
2009-05-25 16:18:39 Error Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIMessage creation failed (inbound). Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not parse XMBMessage. Reason: java.io.IOException: invalid content type for SOAP: TEXT/HTML
Please help if possible! Thanks!
Mayank

Hi,
Check in SLD your integration engine business system have the following
pipeline url : http://server:httpport/sap/xi/engine?type=entry
check Http port also
After that go to TCODE - SXMB_ADM - integrationn engine configuration and check if your server is configured as HUB with the same url or not.
Thanks
Kasturika Phukan

Why we do not need sender agreement for Mail and SOAP adapter

Hi SDN,
I know, we do not need sender agreement for IDOC ,HTTP,XI adapters. As these three adapters will run in Integration engine of the abap stack.
In our scenario if sender is other than IDOC or HTTP or XI .
By Refering Sivamni's blog.
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
message will be pickedup by communication channel with the help of sender agreement and prepare XI message header by performing cpa cache lookup. then message will go to module processor etc.
In our scenario if sender is IDOC or HTTP or XI .
As these 3 adapters are run in Integration engine.
Doubt 1:
how the integration engine will create the xi message header like sender interface sender system name etc...
Doubt 2:
I believe SOAP and mail adapter will run in adapter engine.but i came to know that we do not need sender agreement and sender comm channel for these two adapters too...then how the XI message header will create...
Please do correct me if i am wrong
and throw some light on the same..
Appreciate your help....
Regards,
Reehan.

Reehan,
Thanks for pointing me to that link. Guess I was wrong .,But,let me try to put to you why you need a sender agreement for a Sender SOAP Adapter,
1. In the sender SOAP adapter , the Sender Interface and the Interface Namespace as provided in the fields Default Interface Name and InterfaceNamespace. The Name of the Sender Service is provided in the WSDL when you ceate the WSDL in the Integration Directory. So, as all details are available in either the Sender SOAP adapter or in the WSDL url you do not need a Sender Agreement. It is not obligatory but you can always create the Sender Agreement.
2. For the mail adapter , if you select the option XIPAYLOAD, you will have the option to mention the Interface Name and Interface Namespace under XI Parameters and so in this case as once again the details provided in the sender agreement are available in the Sender Adapter itself the sender agreement is not needed for the mail adapter when you have select option XIPAYLOAD.
If you have selected XIALL then you need a sender agreement.
Regards
Bhavesh

SOAP adapter error: invalid content type for SOAP: TEXT/HTML.

Dear SAP experts,
Need your help again here.
Currently, i am getting this specific error in my RWB logs.
The connection is from SAP XI going to Trading Partner via SOAP adapter.
The specific error is:
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: invalid content type for SOAP: TEXT/HTML.
I've already searched on what is causing the issue and it seems majority of the information is that, the error might be due to incorrect/wrong URL that was set in the configurations in the SAP XI communication channel.
Can you confirm this one?
DO you have any thoughts on this error?
Please help.
Thank you very much!
Fred

Hi Freddiesan,
First of all, test your URL acessing it from SAP PI server's local browser to check firewall and router settings.
If it works, check these blogs:
Regards,
Rogério
Edited by: Rogério Tambellini on Jul 3, 2009 12:52 PM

Selected communication channel IDoc_AAE_In is assigned to the wrong adapter type IDoc_AAE Supported adapter types: HTTP, SOAP, XI, WS.

Hi Team,
I have a problem.
I have a scenario using the the Sender Adapter. HTTP_AAE
When I am trying to use the function "Display WSDL" I am receiving the following.
Error:
Selected communication channel HTTP_AAE_In_SAPII is assigned to the wrong adapter type HTTP_AAE Supported adapter types: HTTP, SOAP, XI, WS.
Somebody knows this problem?
Thanks

Hi,
am also getting same error.
think that feature is not supported.
have look on Configuring the Java HTTP Adapter on the Sender Channel - Advanced Adapter Engine - SAP Library for sending a message.
reg,avinash M

SOAP Adapter Content-Type

Hi,
we move a Interface from BC to XI and now the problem come up that the content type isn't correct anymore.
With BC we Post a request with Content Type application/x-sap.idoc to a specific url.
With XI i use the SOAP Adapter for sending the Idoc structure but now in the header the Content-Type is application/xml is there any possibility to change this in the SOAP Adapter.
Or do i have to use another adapter? Somebody has experience with that?
Regards,
Robin

I don't know a standard way to modify the Content-Type.
You can write a custom adapter module that make this:
From http://help.sap.com/saphelp_nw04/helpdata/en/cd/5af7c0c994e24fb0d0088443513de2/content.htm
"In the receiver adapter, if you want to add your own modules to process the request message, you add them before the module specified below; if you want to add your own modules to process the response message, you add them after the following module:
sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean"
Or you may try to use the HTTP adapter, there you have the control on content-type
Regards,
Sandro

Adapter Type Missing

Hi All,
Can anyone say me why I can't select adapter type in a communication channel???
Thanks a lot

Hi Albert.
Trye reimporting your SWCV SAP BASIS 6.40 if netweaver 2004 or SAP BASIS 7.00 if netweaver 2004s.
If doing this, you don't have the adapters, is because *.tpz files that contain definitions and SAP demos is not availbale. Ask your BASIS team to put the necessary files into correct folders so you can import them and have adapters.
Regards,
Inigo.
Hola Albert.
No tienes los adaptadores porque es posible que falten unos ficheros *.tpz en los servidores que contienen las definiciones. Para comprobar esto, reimporta los SWCV SAP BASIS 6.40 o SAP BASIS 7.00 si estas en NW 2004 o 2004s.
Si despues de hacer esto sigues sin ver los adaptadores, es definitivamente porque faltan los ficheros. Diles a los de sistemas que busquen la nota OSS donde les explica bien clarito qué hacer.
Ahora te busco la nota y me das los puntitos, jejje
Saludos,
Inigo

Why SOAP Adapter Type is missing ?

Similar Messages

Maybe you are looking for