SOAP - other protocols

When SOAP is being used in any of the scenarios, what are the other protocols that can be thought of in place of SOAP.

Naveen,
XI uses SOAP over HTTP as its transport protocol. I dont thinkthis can be changed in anyways.
Is this what you are looking for?
Regards,
Bhavesh

Similar Messages

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

ACE - x-forwarded-for equivalent for other protocols than HTTP

Hello you guys
Need your help. I have an ACE architecture based on source-nat but I want to have the real source IP info on the destination real server.
For HTTP packets I can set up x-forwarded-for, but is there a way to do the same for other TCP protocols? And, just for the fun of it, UDP also?
Best wishes

Hi,
it is designed specifically for HTTP. ACE cannot insert the same to any other protocol.
Even if you look at the commands it says :
"insert-http x-forward header-value "%is"
which itself indicate that it is desinged for HTTP. This is a process of adding a header to HTTP message.
Hope that helps.
regards,
Ajay Kumar

Using other protocol than HTTP for a Nokia 7650 application

Hello,
I'm developing an java application for a Nokia 7650 that needs to use SIP over UDP.
In an emulator on the PC the communication works fine.
I'm afraid that there will be some problems when I port the application to the real device.
Can I use SIP over UDP communication on a real Nokia 7650?
thanks in advance
Best regards
Hector

I add some code example of my application. SIP uses Datagram protocol, which is supported in CLDC.
// Create a new datagram socket.
DatagramConnection dc =
(DatagramConnection)Connector.open("datagram://:5060");
System.out.println("SYSTEM, datagram server listener:" + "datagram://:5060");
while (! sipStack.toExit) {
Datagram datagram =
dc.newDatagram(MAX_DATAGRAM_SIZE);
System.out.println("SYSTEM, listening!");
dc.receive(datagram);
System.out.println("SYSTEM, packet revceived!");
// Create asynchronous message handler
// for this message
UDPMessageChannel udpMessageChannel =
new UDPMessageChannel
(datagram,sipStack);
} catch (Exception ex) {
ex.printStackTrace();

Send Stream using other protocol

Hello everyone, I have a question I do not know whether we can do the following:
- Suppose I have a application protocol in Java, where sending objects over the network:
SendObject (Object data).
- You can send multimedia data (audio and/or video) through my protocol with JMF, what Object I send, if that were possible.
thanks for your help.

Ok, thanks ... captfoss sending the byte array is fine.
On the other hand,
1.- when I receive this byte array and converts it to buffer should I do next?.
using the example:
[http://java.sun.com/javase/technologies/desktop/media/jmf/2.1.1/solutions/LiveData.html]
// In MyDataSource.java...
public PushBufferStream [] getStreams() {
     if (streams == null) {
         streams = new LiveStream[1];
         stream = streams[0] = new LiveStream();
     return streams;
When I receive the data, converts it to buffer and invoke this function.
This function is new and is to pass the buffer to LiveStream.read (Buffer)
public void setBufferReceived(Buffer buffer){
    stream.read(buffer);
}- But not understanding how modifying function LiveStream.run ().
that performs this code."transferHandler.transferData(this); " ??
public void run() {
          while (started) {
               synchronized (this) {
                    while (transferHandler == null && started) {
                         try {
                              wait(1000);
                         } catch (InterruptedException ie) {
                    } // while
               if (started && transferHandler != null) {
                    transferHandler.transferData(this);
                    try {
                         Thread.currentThread().sleep( 10 );
                    } catch (InterruptedException ise) {
          } // while (started)
     } // run     - Also once you create the MyDataSource:
MyDataSource ds = new MyDataSource ();
This DataSource must be connected (connect ()) and start (start ()) in explicit form?.

How to enable cache on Business service having protocol other than JCA

Hi all,
In my use case I should use cache on my business service which uses Http as its transport protocol.
when I try to use the cache on http business service I am unable to use the cache functionality.
When I try to use the cache on JCA business service I am able to use it. Please help me in finding the
ways in which I can enable cache functionality on the business service which uses the other protocols.
Thanks,
Phanindra.

Caching in Business Service should work fine on HTTP transport as well. What all configurations have you done in your HTTP business service and how are you testing it?

Send/Receive IDOCs (XML) from/to SAP R/3 with XI-SOAP without XI!

Dear SAP specialists,
(BACKGROUND) We are using the Microsoft BizTalk Adapter for SAP 1.0, developed on top of the SAP DCOM Connector (we are using the version 6.20 Patch Nr. 177), with Microsoft BizTalk Server 2002 SP1 in order to send and receive IDOC via the tRFC transport protocol. We are using the Microsoft BizTalk Adapter for SAP 1.0 since February 2002, and today we are exchanging more than 25,000 IDOC/day with this architecture.
When we migrate our SAP R/3 system to the version 4.7 with WAS 6.20, I was very enthusiastic about the possibility of sending the IDOC in XML via the standard HTTP transport protocol, because it would considerably simplify my architecture, i.e. no need of any (expensive) adapter any more! But, I had to realise that the quality of service exactly once will not be there anymore with HTTP as it exists with tRFC. Then, we carry on using the tRFC transport protocol with the adapter.
(QUESTION) But recently, I followed the SAP Course TBIT40 XI Foundations and I learn that:
1. On one hand, the XI-SOAP protocol supports the quality of service exactly once by the usage of a message GUID within the XI-SOAP envelope;
2. On the other hand, all mySAP solutions using WAS 6.20 (or higher) carry a small Integration Engine (with XI-SOAP as the native transport protocol).
Then, my question is: << Is it possible to exchange IDOC (XML) directly with an SAP R/3 4.7 (WAS 6.20) via the XI-SOAP transport protocol using the small Integration Engine embedded into it, with the quality of service exactly once? >>
Many thanks in advance and best regards,
Patrice Krakow

Hello Patrice
We have same issue. Is it possible to use IDoc (XML) directly with SAP 5.0 with SOAP (HTTP) without XI?
Since your que is three years old, I'm sure you must have found some method for this.
We'll highly appreciate your help.
Regards: Gaurave

SOAP receiver adapter digest authentization

Hallo,
I have scenario with SOAP receiver adapter configured as follow:
Adapter Type: SOAP
Transport Protocol: HTTP
Message Protocol: SOAP 1.1
Adapter Engine: Integration Serer
Target URL: http://localhost:8099/webservices/test_v1_1_2
Configure User Authentication
User: ****
Pasword:****
but WS need digest HTTP authentication and SOAP adapter send in header Authentication: Basic.
Hou can I change authentication method for SOAP protocol?
Thx

Hallo,
I solved this problem by using AXIS framework. I hope that this short instruction help to someone.
1. In SOAP receiver CC you have to set up Transport Protocol to HTTP(AXIS) and Message protocol to AXIS
2. Now you can switch Authentication to Digest (NOW adapter will still send Basic!!! Digest Authorization is Supported only by the following handler: com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender)
3. On Module tabs in section Module configuration change type HTTPSender to CommonHTTPSender:
(trp handler.type java:com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender)
4. Save and Activate
Before you start to use AXIS framefork you have to deploy necessary library.
This thread help:
Re: How to install SOAP Axis adapter and where is it available ??
Be carefull, for digest authorization you have to linked Optional library "Jakarta-Commons HttpClient" too.
Good luck.
JK

SOAP Receiver Version Mismatch

Hi Gurus,
I am have a iDoc to SOAP scenario. I have created the receiver communication channel as SOAP 1.1 in XI. I get the following error in communication channel
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Incoming SOAP message protocol is version 1.1, but endpoint is configured for SOAP 1.2. This is not supported.
Please advice..
Regards,
Isuru

Hi Gopal,
Thank you. But remember this is not the namespace created under software component in IR. This is the envelope namespace "http://schemas.xmlsoap.org/soap/envelope". Isn't this a system generated namespace?
Please advice me how to do the mapping.
Thanks in Advance!
Isuru

Presence of multiref tag in soap response message

We are having a problem when we try to call a web service in PI. The web services called is provided by an Axis server.
We tried to use the plain HTTP protocol in the definition of the communication channel as shown here:
Adapter type: SOAP
Transport protocol: HTTP
Message protocol: SOAP 1.1
Adapter engine: Central Adapter Engine
We got the followong error response in SXMB_MONI:
The payload shown in SXNB_MONI is:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<ns1:cedstr_obt_cle_elem_v2_Response xmlns:ns1='urn:CEDSTR' soapenv:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/' xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
<tab_cle soapenc:arrayType='ns1:cedstr_cle_elem_v1[3]' xmlns:soapenc='http://schemas.xmlsoap.org/soap/encoding/' xsi:type='soapenc:Array'>
<item href='#id0'/>
<item href='#id1'/>
<item href='#id2'/>
</tab_cle><nb_cle xsi:type='xsd:int'>3</nb_cle><stat_elem href='#id3'/>
<cdr href='#id4'/>
</ns1:cedstr_obt_cle_elem_v2_Response>
The expected payload is:
<?xml version="1.0" encoding="UTF-8" ?>
- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <soapenv:Body>
- <ns1:cedstr_obt_cle_elem_v2_Response soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:CEDSTR">
- <tab_cle xsi:type="soapenc:Array" soapenc:arrayType="ns1:cedstr_cle_elem_v1[3]" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<item href="#id0" />
<item href="#id1" />
<item href="#id2" />
</tab_cle>
<nb_cle xsi:type="xsd:int">3</nb_cle>
<stat_elem href="#id3" />
<cdr href="#id4" />
</ns1:cedstr_obt_cle_elem_v2_Response>
- <multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">118406</id_structure_det>
<ordinal xsi:type="xsd:int">2648545</ordinal>
<appareil xsi:type="xsd:string">C3D1E</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id1" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns3:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns3="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">984806</id_structure_det>
<ordinal xsi:type="xsd:int">2723425</ordinal>
<appareil xsi:type="xsd:string">O5C3X</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id2" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns4:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns4="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">1163686</id_structure_det>
<ordinal xsi:type="xsd:int">3144641</ordinal>
<appareil xsi:type="xsd:string">Y0A6B</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id3" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns5:cedstr_stat_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns5="urn:CEDSTR">
<tension xsi:type="xsd:string">MT</tension>
<nb_concess xsi:type="xsd:int">0</nb_concess>
<nb_restr xsi:type="xsd:int">0</nb_restr>
<localisation xsi:type="xsd:string">DEVILLERS EST DE BEAUREGARD</localisation>
<remarque xsi:type="xsd:string" />
</multiRef>
- <multiRef id="id4" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns6:utlgen_cdr" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns6="urn:CEDSTR">
<succes xsi:type="xsd:int">1</succes>
<code xsi:type="xsd:int">0</code>
<message xsi:type="xsd:string" />
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
</ns1:cedptr_obt_cle_di_v1_HResponse>
What I can see is that PI seems to ignore the multiref tag in the SOAP response message. Does anybody knows if there is an issue with the mutiref tag in PI ?
Thanks for your help.

The SOAP adapter does not support more than one body child.
If a SOAP message with several body childs arrive, then only the first body child is considered, all other body childs are ignored.
Regards
Stefan

Error using IDOCFlatToXmlConvertor in Axis-SOAP

Dear Members,
I am trying to execute the IDOCFlatToXmlConvertor module in SOAP-Axis adapter (sender) of SAP PI 7.11. Addition of modules is done as per guidelines of SAP Help and Axis_FAQ:
AF_Adapters/axis/HandlerBean
AF_Adapters/axis/AFAdapterBean
SAP_XI_IDOC/IDOCFlatToXmlConvertor
CallSapAdapter
AF_Adapters/axis/AFAdapterBean
AF_Adapters/axis/HandlerBean
Corresponding module parameters (SAPRelease, TargetDestination, SourceJRA) are also mentioned correctly. However when I try to send a flat IDOC through the Axis channel it fails in the channel monitoring with below error:
message not processed: java.lang.ClassCastException: class
org.apache.axis.message.Text:library:com.sap.aii.af.axisproviderlib_at_com.sap.engine.boot.loader.ResourceMultiParentClassLoader_at_32e6e42e_at_alive incompatible with
class
org.apache.axis.message.SOAPBodyElement:library:com.sap.aii.af.axisproviderlib_at_com.sap.engine.boot.loader.ResourceMultiParentClassLoader_at_32e6e42e_at_alive
I have done the below:
1) Ensured that required components for Axis protocol are enabled. Normal SOAP message is processed by the Axis Channel
2) Maintained all the parameters for IDOCFlatToXmlConvertor in NWA and also in the channel
3) The scenario works perfectly fine when used a File_Sender_channel instead of SOAP_Sender_channel
So my question now is, can the IDOCFlatToXmlConvertor module be used with SOAP-Axis protocol (theoritically it should be)? If yes, then where am I making the mistake? Is it because I am using SOAPUI tool for testing?
Thanks,
Abhishek.
P.S. I have replaced the @ symbol with at as SDN does not allow me to post!

Hi Experts,
In my Receiver SOAP adapter module Tab.
As my scenario is synchronous and i required UsernameToken with PasswordDigest security i have added following parameter value in module.(as per SAP Note 1039369 FAQ XI Axis Adapter ).
Processing Sequence.
Module Key
afreq
xireq
wssec
trp
xires
afres
Module configuration
ModuleKey ParameterName   parametervalue
xireq           handler.type         java:com.sap.aii.axis.xi.XI30OutboundHandler
wssec         action                   UsernameToken
wssec        handler.type         java:com.sap.aii.adapter.axis.ra.handlers.security.WSDoAllSender
wssec       passwordType     PasswordDigest
wssec      pwd.password     ********************
wssec      user                       XYZ
trp            handler.type            java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
trp             module.pivot          true
xires       handler.type           java:com.sap.aii.axis.xi.XI30OutboundHandler.
Do we need to do any other configuartion apart from above in parameter value.
While getting response from third party i getting error as WSDoAllReceiver: security processing failed (actions number mismatch)
Do i need to add parameter value for WSDoAllReceiver as well as my scenario is synchronous.
Please help me out on this as i am not able to proceeed further because of the above errro.
Please advice.
regards
Anku Chopra

Axis SOAP adapter

We tried to use the Axis HTTP protocol in the definition of the communication channel as shown here:
Adapter type: SOAP
Transport protocol: HTTP
Message protocol: Axis
Adapter engine: Central Adapter Engine.
When we tried to execute the scenario, we got the below error in SXMB_MONI:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: org.apache.axis.ConfigurationException: adapter is null org.apache.axis.ConfigurationException: adapter is null at com.sap.aii.adapter.axis.modules.HandlerCore.process(HandlerCore.java:54) at com.sap.aii.adapter.axis.modules.HandlerBean.process(HandlerBean.java:75) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2583.process(Unknown Source) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:249) at sun.reflect.GeneratedMethodAccessor352.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy45.process(Unknown Source) at com.sap.aii.af.app.listener.AFWListenerBean.onMessage(AFWListenerBean.java:317) at sun.reflect.GeneratedMethodAccessor886.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy58.onMessage(Unknown Source) at com.sap.engine.messaging.impl.spi.ServicesImpl.deliver(ServicesImpl.java:314) at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1000) at com.sap.engine.messaging.impl.core.queue.consumer.RequestConsumer.onMessage(RequestConsumer.java:73) at com.sap.engine.messaging.impl.core.queue.Queue.run(Queue.java:848) at com.sap.engine.messaging.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56) 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:152) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Has somebody got the same issue? Please help.

The problem is corrected.
For those who are interested, the problem was caused by a missing component in the installation of the Axis adapter in PI: the commons-httpclient.
By verifying the list of modules present in the Module tab of the communication channel defined for the interface, we found an entry specifying 'com.sap.aii.adapter.axis.ra.transport.http.HTTPSender'.
The documentation 'Configuring the Receiver Axis SOAP Adapter ' provided by SAP Help stated that:
"If you are using the handler com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender, the commons-httpclient of Apache Commons HTTP Client must be contained in axisproviderlib."

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.

Soap server connection problem

in jdeveloper 9.0.2 i am trying to develop and deploy webservice. After starting embeded oc4j engine from the command prompt i m unable to get this url http://<hostname>:8888 from the browser .
Also facing the problem while running the new soap server connection wizard. while testing the connection i m getting this error.
Testing connection...
[SOAPException: faultCode=SOAP-ENV:Protocol; msg=Unsupported response content type "text/html", must be: "text/xml". Response was:
<HTML><HEAD>
<TITLE>ERROR: The requested URL could not be retrieved</TITLE>
</HEAD><BODY>
<H2>The requested URL could not be retrieved</H2>
<HR>
<P>
While trying to retrieve the URL:
<A HREF="http://<hostname>:8888/soap/servlet/soaprouter">http://kanti:8888/soap/servlet/soaprouter</A>
<P>
The following error was encountered:
<BLOCKQUOTE>
Unable to determine IP address from host name for
<I>kanti</I>
</BLOCKQUOTE>
<P>
The dnsserver returned:
<BLOCKQUOTE>
Name Error: The domain name does not exist.
</BLOCKQUOTE>
<P>
This means that:
<PRE>
The cache was not able to resolve the hostname presented in the URL.
Check if the address is correct.
</PRE>
<P>Your cache administrator is <A HREF="mailto:root">root</A>.
<br clear="all">
<hr noshade size=1>
Generated Fri, 14 Feb 2003 13:05:51 GMT by firewall (Squid/2.4.STABLE6)
</BODY></HTML>
     java.lang.String org.apache.soap.rpc.Call.getEnvelopeString(org.apache.soap.transport.SOAPTransport)
     org.apache.soap.rpc.Response org.apache.soap.rpc.Call.invoke(java.net.URL, java.lang.String)
     org.apache.soap.rpc.Response oracle.jdevimpl.webservices.util.JDevServiceManager.invokeMethod(java.lang.String, org.apache.soap.rpc.Parameter)
     java.lang.String[] oracle.jdevimpl.webservices.util.JDevServiceManager.list()
     void oracle.jdevimpl.webservices.wizard.connection.TestConnectionPanel$2.run()
Unable to connect to SOAPServerConnection1 (http://<hostname>:8888/soap/servlet/soaprouter)
Connection test failed: unable to connect
right now i m ready to use any web service either
1 > j2ee web service .(or)
2 > soap web service
but both are not working .
Pls help me on this issue.
regards mangesh

If you use HttpsURLConnection for this, it will work on java 1.4.1, but not on prior releases. It will (as far as I can tell from experiment) use the time that the server provides for Keep-Alive.

SOAP response XI - SAP Business Connector

Hi all,
I'm working on a project using SOAP messaging between SAP BC and XI.
I'm sending a soap message from XI to BC.
I configured the communication channel:
Adapter Type     - SOAP
Transport Protocol     - HTTP
Message Protocol     - SOAP 1.1
ecc...
and in BC flow I've defined a record with response-message parameters (acknowledgment).
When I try the flow, the response message was create (I use service savepipelinetofile in BC and i read out data), but in xml monitoring inside XI (trans. SXMB_MONI) i cannot read my response parameters.
In effect in Ack. Status i find icon "Acknowledgment not possible".
Can I create correspondence between "soapresponsedata" in BC and response message in XI xml monitor?
Thanks
Alex

hi,
I suppose you need to create a communication channel to push the data from BC to XI. For this you may require to configure XI's BC adapter(as sender).
From BC side you should define a routing rule. Refer to http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Hope this helps,
Regards,
Siva Maranani.

SOAP - other protocols

Similar Messages

Maybe you are looking for