Missing soap action in the soap axis receiver adapter ?

Hi Guys,
I could not find the soap action field in the soap receiver adapter and i followed the OSS note
Note 1054986 - SOAP (Axis) receiver adapter's SOAPAction field missing
Please apply the following patch and use the handler parameter defaultSOAPAction for the XI30OutboundHandler handler in the request chain. This handler parameter can be configured as a module parameter for the HandlerBean module associated with this handler. It is noted that this module parameter takes precedence over the channel parameter for SOAPAction if this field is available.
For SP12
XI ADAPTER FRAMEWORK CORE 7.0
Support Package 12, Patch Level 1 (SAPXIAFC12P_1.SCA)
we are on SP15 so i think the option should be available ?
Do i need to add this parameter in the Module Configuration ?
Moduel Key : ?
Parameter Name: handler.type ---> is this right
Parameter Value ---> ?
we need to validate the user id and pw on IIS for NTLM authentication. Any help regarding developong the handlers would be great
any help would be appreciated.
Thanks,
Srini

Srinivas,
You are on the right path...........yes that is the right note for this issue.
The problem is this is not a general fix that comes with all service packs as the axis adapter is not used a lot, that being said.if you dont see it with sp15..i would safely go apply this fix and see if it works..else you might have to open an oss note for the same...
Hope that helps..
Regards
Ravi Raman
P.S: On my home system..i did apply the fix and i was on a much higher sp level ..i saw some errors..in the logs but nothing a restart couldent fix..

Similar Messages

Axis receiver adapter error

Hi,
I am getting the following error when i check the MDT for the Axis Receiver Adapter.
com.sap.aii.utilxi.misc.api.UnexpectedException: Internal Error: An unexpected error occurred (java.lang.NoSuchMethodException: com.sap.aii.mdt.server.integrationengine.IntegrationEngineDataImpl.getDuration())
The Stack trace is as follows
Stack trace for the above error message is:
com.sap.aii.utilxi.misc.api.UnexpectedException: Internal Error: An unexpected error occurred (java.lang.NoSuchMethodException: com.sap.aii.mdt.server.integrationengine.IntegrationEngineDataImpl.getDuration())
     at com.sap.aii.mdt.api.data.Attribute.getDisplayFieldValue(Attribute.java:463)
     at JEE_jsp_monitor_monitor2_113430051_1317630683360_1323173672867._jspService(JEE_jsp_monitor_monitor2_113430051_1317630683360_1323173672867.java:573)
     at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102)
     at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:428)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:147)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
     at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
     at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
     at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
     at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: java.lang.NoSuchMethodException: com.sap.aii.mdt.server.integrationengine.IntegrationEngineDataImpl.getDuration()
     at java.lang.Class.getMethod(Class.java:1605)
     at com.sap.aii.mdt.api.data.Attribute.getDisplayFieldValue(Attribute.java:429)
     ... 45 more

Hi Srinivas,
Post last line when you received this error.
regards
Ramesh

Query reg adding custom tags in SOAP Header - AXIS Receiver Adapter

Hi All,
I need to send custom tags as mentioned below to my traget webservice application. I think I can do this with Receiver AXIS adapter but not sure how it can be done. Can any of you suggest?
                                              <WSContext>
               <FromAppId>ABC</FromAppId>
               <ToAppId>XYZ</ToAppId>
          </WSContext>
Thanks,

If you want to add custom tags in the soap header, one possible solution is use XSLT mapping or Java mapping to create header first then do message mapping for mapping the payload structure between your source and target as usual.
So in operation mapping you sequence mapping like this... first XSLT mapping for custom tags for the SOAP Header followed by payload mapping.
Hope that helps.
Search SDN for XSLT Mapping for soap header. Already we have handled these issues.

Can Soap Action be dynamically substituted in receiver side soap Action ?

Hi all
I am trying to place Action in Soap Receiver adapter.
I could see the THeaderSoapAction and the action I have specified in Dynamic Configuration and that action is not getting triggered
I was going through previous posts and Raj was mentioning that there was some problem with Soap Receiver adapter while dynamically placing Soap Action.
Is it so? Has anyone dynamically passed Soap Action using Adapter specific parameters?
If its cannot be achieved with ASP, What is the best alternate to this ?
Thanks and Regards,
Nikhil.

Have not tried this option, but theoretically it should work using the Adapter Specific message attributes
http://help.sap.com/saphelp_nw2004s/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
Regards,
Prateek

Missing namespace prefix in the soap body

Hello
The soap body that is produced along with soap header for my webservice. I
am the client talking to a server. The first piece in RED color is what
weblogic generates to send to the client but does NOT work. The one below
though works fine which is what I manipulated by hand to send to the
server. I have no idea why weblogic drops the namespace prefix in the
BODY.
-Narahari
The message is as shown below
POST /FS HTTP/1.1
Host: asgappsrv10:6211
Content-Type: text/xml; charset=utf-8
Connection: close
SOAPAction: "ListDomains"
<?xml version="1.0" encoding="utf-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header>
<n1:Credentials xmlns:n1="urn:criticalpath:fs:api:1.0"
xsi:type="n1:Credentials">
<Username xsi:type="xsd:string">admin@default</Username>
<Password xsi:type="xsd:string">password</Password>
<SessionId xsi:nil="true"/>
</n1:Credentials>
</env:Header>
<env:Body
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<Fulfill xmlns:n2="urn:criticalpath:fs:api:1.0"
xsi:type="n2:Fulfill">
<Request xsi:type="xsd:string">ListDomains</Request>
<RequestAttributes soapenc:arrayType="n2:Attribute[0]"/>
<Async xsi:type="xsd:boolean">false</Async>
</Fulfill>
</env:Body>
</env:Envelope>
When you see the data carefully, the env:Body has the Fulfill element. But
it does have a namespace prefix on it. This causes the call to fail. If I
change the above segment manally to look like
POST /FS HTTP/1.1
Host: asgappsrv10:6211
Content-Type: text/xml; charset=utf-8
Connection: close
SOAPAction: "ListDomains"
<?xml version="1.0" encoding="utf-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header>
<n1:Credentials xmlns:n1="urn:criticalpath:fs:api:1.0"
xsi:type="n1:Credentials">
<Username xsi:type="xsd:string">admin@default</Username>
<Password xsi:type="xsd:string">password</Password>
<SessionId xsi:nil="true"/>
</n1:Credentials>
</env:Header>
<env:Body
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<n2:Fulfill xmlns:n2="urn:criticalpath:fs:api:1.0"
xsi:type="n2:Fulfill">
<Request xsi:type="xsd:string">ListDomains</Request>
<RequestAttributes soapenc:arrayType="n2:Attribute[0]"/>
<Async xsi:type="xsd:boolean">false</Async>
</n2:Fulfill>
</env:Body>
</env:Envelope>

Hi All,
we are also facing the same issue, Please provide the solution if anyone knows. We are also using the SOA Suite 11g Version.

PI 7.1 SOAP Action parameters in SOAP request?

Hi all,
I have to implement an IDOC->PI->XML interface to transfer some master data. After performing the mapping, the mapped data needs to be sent to the target system using a SOAP request via a webservice.
On PI, I specified the URL for the WS in a SOAP-oriented Communication Channel. In the parameter "SOAP Action" of this CC, I entered the relevant method name to be used to transfer the mapped data. However, this method requires 2 parameters:
- applicationName: this is the name of the target structure used in the Message Mapping
- xmlMessage: this is the actual mapped message string
So my question is: how can I bind these 2 parameters in my PI design and configuration?
Thanks for your help,
Eric

there can be one WS having many actions....which means one WS can be used in multiple interfaces.
However, this method requires 2 parameters:
- applicationName: this is the name of the target structure used in the Message Mapping
- xmlMessage: this is the actual mapped message string
If I get it correctly, you have to actually set the SOAP action before you send the message to the WS....and you want to do it in SAP PI?
so your action is something like http://something.abcd/applicationName/xmlMessage and you have to set the things here?
If yes, then you can use the Dynamic Configuration (adapter specific message attributes...ASMA) in SOAP channel (UDF in mapping) and set this ASMA THeaderSOAPACTION
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get
(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","THeaderSOAPACTION");
String a = http://something.abcd/applicationName/xmlMessage //set the value of actual action here
conf.put(key, a);
return "";
Regards,
Abhishek.

HTTP (Axis) Receiver Adapter error: The security context token is expired or is not valid

Hi Experts,
We are required to send a message through PI 7.31 (single stack) in a Soap-to-Soap scenario connecting to a Soap 1.2 Web Service.
We are getting a Security Context Token expired or Invalid error.
Please help us resolving this error.
Thanks in advance!
The Channel Configurations are as follows:
Processing sequence:
Module configurations:
1.
2.
3.
4.
Best Regards
Vikram

Hi all !
First of all, thanks for your answers..
Stefan Grube:
Itu2019s not a Adapter Module.
The module tab following configuration
Processing Sequence:
AF_Adapters/axis/AFAdapterBean     Local Enterprise Bean     afreq
AF_Adapters/axis/HandlerBean                     Local Enterprise Bean     xireq
AF_Adapters/axis/HandlerBean                     Local Enterprise Bean     trp
AF_Adapters/axis/HandlerBean                     Local Enterprise Bean     dcres
AF_Adapters/axis/HandlerBean                     Local Enterprise Bean     xires
AF_Adapters/axis/AFAdapterBean     Local Enterprise Bean     afres
Module Configuration
xireq          handler.type     java:com.sap.aii.axis.xi.XI30OutboundHandler
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
How can i know if those values are correct ?
Srinivas Reddy:
Thanks for the documentation
I have applied SAP Note 11016021 and the error changed, now it says:
Axis: fatal error in invocation: java.lang.NoSuchMethodError: com/sap/aii/axis/xi/XIUtils.setOperation(Ljava/lang/String;Lorg/apache/axis/MessageContext;)V
Message processing failed. Cause: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
Edited by: Antonio Guzman on Jul 9, 2008 5:29 PM

New to SOAP - How to create SOAP message for the SOAP described

Hi Friends,
Im bit new to SOAP-JAVA interactions.
I have an SOAP describing
POST /abc/WebSrevices/MyService.asmx HTTP/1.1
Host: 127.0.0.1
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "http://tempuri.org/BillingAddressValidation"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<BillingAddressValidation xmlns="http://tempuri.org/">
<inXml>string</inXml>
</BillingAddressValidation>
</soap:Body>
</soap:Envelope>
My question is How can I construct an equivalent JAVA message using SAAJ
I wrote like the following
public void performSOAPReadWrite(String transaction){
try{
SOAPConnectionFactory scf = SOAPConnectionFactory. newInstance();
SOAPConnection con = scf.createConnection();
MessageFactory mf =
MessageFactory.newInstance();
SOAPMessage msg = mf.createMessage();
SOAPPart sp = msg.getSOAPPart();
SOAPEnvelope envelope = sp.getEnvelope();
//Adding Content to the Header
envelope.getHeader().detachNode();
SOAPBody body = envelope.getBody();
SOAPElement billingAddressValidation =
body.addChildElement("BillingAddressValidation","http://tempuri.org/");
SOAPElement inXml =
billingAddressValidation.addChildElement("inXml");
inXml.addTextNode(transaction);
URL urlEndpoint = new URL(DEFAULT_SERVER);
// 127.0.0.1/abc/WebSrevices/MyService.asmx
System.out.println("Sending Message");
SOAPMessage reply = con.call(msg,
urlEndpoint);
System.out.println("Reply is "+reply);
}catch (Exception e) {
e.printStackTrace();
// TODO: handle exception
Can any one let me know whats wrong in this ?
Thanx in advance
Im waiting for ur reply
Mahesh Raja Vandyala
Senior Analyst

Hi,
When im running the program I am getting a
javax.xml.soap.SOAPException: Failed to send message:java.io.IOException: The server at http://127.0.0.1/abc/WebSrevices/MyService.asmx returned a 500 error code ( Internal Server Error )
Please ensure that ur URL is correct and the Web service has deployed
This is web service is provided by .net team and im required to take the services of that web service to retrieve some information provided by that.
I can launch the webservice definition thru IE....their they have provide a text box with a Invoke button.
The same data that im sending thru code if invoked thru IE is working fine.
I suspect that the way Im construcint the SOP message is wrong.
Any help in finding out the correctness of the Message in the java code ?
Thanx
Mahesh

How to XI error message will mapped to the SOAP faul message-SOAP(Axis)

Hi,
Receiver end I am using SOAP (Axis) adapter and I am getting the system error and I am not getting the payload in SXMB_MONI.
What ever the error message how do MAP as a SOAP Fault message in SXMB_MONI.
I found the Solution from OSS note 1039369 but did not explain where to set what parameter and what modules...
SOAP Fault code
If parameter Category is XIAdaptger, Area SOAP, Code FAULT
In this case, parameters P1 and P2 may be set to the fault namespace and fault name. If these parameters are set, the SOAP fault code is set to namespace P1 and name P2. Otherwise, it is set as in other cases.
For all other cases
In this case, the SOAP fault code is set to namespace "http://sap.com/xi/XI/Message/30" and name category.area.code, where category, area, code represent the XI error category, area, and code values, respectively.
SOAP detail
If parameter ApplicationFault is set
The SOAP detail child is set to the XI application payload. If, however, the payload extraction mode is set to Envelope, the application payload is taken as the SOAP envelope and the SOAP detail content is set to its body content. Similarly, if the extraction mode is set to Body, the application payload is taken as the SOAP body and the SOAP detail content is set to its content.
Otherwise
No SOAP detail content is set in this case.
Examples
XI error element
<sap:Error ...>
<sap:Category>XIAdapterFramework</sap:Category>
<sap:Code area="MESSAGE">GENERAL</sap:Code>
<sap:AdditionalText>Failed to determine a receiver agreement for the given message.</sap:AdditionalText>
</sap:Error>
SOAP fault element
<soapenv:Fault>
<faultcode xmlns:ns1="http://sap.com/xi/XI/Message/30">ns1:XIAdapterFramework.MESSAGE.GENERAL</faultcode>
<faultstring>Failed to determine a receiver agreement for the given message.</faultstring>
<detail/>
</soapenv:Fault>
Help appriciated
Regards,
Venu.
Edited by: Venugopalarao Immadisetty on Sep 24, 2009 3:39 PM

Using Receiver SOAP Axis adapter and I am getting the below exception
XI error element
<sap:Error ...>
<sap:Category>XIAdapterFramework</sap:Category>
<sap:Code area="MESSAGE">GENERAL</sap:Code>
<sap:AdditionalText>Failed to determine a receiver agreement for the given message.</sap:AdditionalText>
</sap:Error>
and above exception how do I convert as a SOAP Fault message..
SOAP fault element
<soapenv:Fault>
<faultcode xmlns:ns1="http://sap.com/xi/XI/Message/30">ns1:XIAdapterFramework.MESSAGE.GENERAL</faultcode>
<faultstring>Failed to determine a receiver agreement for the given message.</faultstring>
<detail/>
</soapenv:Fault>
Any idea what modules need to add in Receiver SOAP Axis adapter.

What is the use of soap action?

Hi experts,
what is the functionality of soap action in receiver soap adapter?
Thanks & Regards
E.Ravi Chandra Reddy

Hi Ravi,
This “SOAP action” tells the web service to perform a particular action. It will call the related method in the WSDL and perform that action and that WSDL may contain different functionalities/Methods and the action we will give in the channel will call the particular method
I have attched the screen of a WSDl containing different methods (WSMethods)
Channel for more reference

Receiver Adapter - Target URL/SOAP Action

Hi,
Can I just confirm the following 2 values required on a SOAP Receiver adapter:
Target URL : Location within SOAP:Address tag of WSDL
SOAP Action: SoapAction within SOAP:Operation for relevant Web Service method within WSDL
Cheers,
PaulC.

> Target URL : Value of SOAP:Address tag from web service WSDL
right, it is attribute "soapAction"
> SOAP Action: Value of SOAP:Operation for relevant Web Service method within web service WSDL
right. attribute "location"
check this guide:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4

How can I check the called SOAP-action

Hi,
our scenario is IDOC - XI - SOAP (based on a wsdl). I've imported the wsdl as external definitions. The I implement all necessary interfaces, mappings, .... When I'm sending any IDOCs, I see the right interface, but I can't check the right SOAP-Action. The Receiver firm means, that the wrong function will be called.
Have you any ideas?
Thanks
Matthias

Hi Matthias,
the only way to check the SOAP Action is using an HTTP sniffer. Or you write a simple Java program that listens to a port and writes incoming data to a file.
But I have never heard about the problem, that the SOAP action is not correct. Make sure, that the correct receiver channel is used, the channel is activated and the cache refreshed.
Regards
Stefan

No Payload in the soap receiver call adapter ?

Hi Guys,
configured Proxy-SOAP Asynchronus process and in the sxmb_moni, i am unable to see the payload under call adapter in sxmb_moni, but i am able to see the payload under RWB in MDT. The message is checked successful in monitor.
I am not understanding why i am unable to see the payload under call adapter in sxmb_moni. I am not getting the data into my receiver system.
Do i need to mention the QOS as EO in the soap url in the soap receiver adapter configuration ?
any help would be really appreciated
Thanks,
srini

Hi,
You can only see the Payload(both with and without transformation) in MONI. message that is handling by adapter can only seen in Adapter Framework using RWB-Message Monitoring or using Communication Channel Monitoring.
Regards,
Farooq.
<b>
Rewards points if you find it usefull.</b>

Unable to open PWA in browser and MSP on application server in project server 2007. ERROR: Sending the Soap message failed or no recognizable response was received.

Hi All,
I am using project server 2007 and WSS 3.0.
I have been facing a strange issue for couple of days. I am unable to open PWA in browser and MS Project Pro on application server.
Everything is correct whether it is URL or MS Project profile account on MSP. This is strange because i can open same PWA/MSP from other computers (Database server / Client PCs) but not locally on server.
When i try to connect to MSP on App server, i get the following errors in event viewer.
Event Type: Error
Event Source: MSSOAP
Event ID: 16
User: N/A
Computer: APP-Server-Name
Description:
Soap error: Connection time out..
Event Type: Error
Event Source: MSSOAP
Event Category: Client
Event ID: 16
User: N/A
Computer: APP-Server-Name
Description:
Soap error: An unanticipated error occurred during the processing of this request..
Event Type: Error
Event Source: MSSOAP
Event Category: Client
Event ID: 16
User: N/A
Computer: APP-Server-Name
Description: Soap error: Sending the Soap message failed or no recognizable response was received.
Event Type: Error
Event Source: MSSOAP
Event Category: Client
Event ID: 16
User: N/A
Computer: APP-Server-Name
Description:
Soap error: Unspecified client error..
One more issue i am facing and i guess that is related to above issue. The Issue is, when i am creating a new project, It's workspace gets created but doesn't get linked to the project and i can't link it manually because it already exists for the project.
sandeep

Hi Paul ,
Thanks for reply. The project server URL was already added to the Trusted
Sites/Local Intranet areas in IE.
sandeep

Modify the payload in a soap receiver adapter module

Hi all,
I have an scenario where I should modify the soap_body tag (adding a head and a tail).
I have implemented it using an adapter module, since the mapping is for business stuff and this head and tail is just a technical requirement of the third party web service
It works fine when I use a file channel for testing, but when added to the soap channel, then leaves the soap body empty.
Is there any difference between using the Adapter module on a file channel and a soap channel?
regards,
David R.

David,
Is your requirement that you need to create the SOAP enevlope with some custom fields when sending the data to the SOAP adapter?
if yes, this is what you need to do,
1. In your mapping ( using XSL or Java ) create the Entire SOAP envelope including the SOAP header and the SOAP Body.
2. In the receiver SOAP adapter, select option "Do not use SOAP Envelope".
By default, the SOAP adapter creates the SOAP Envelope for the message and strips out the SOAP content for the response. If you need to add custom fields etc in the SOAP header you need to manually create the SOAP header and body and then select the above option.
Regards
Bhavesh

Missing soap action in the soap axis receiver adapter ?

Similar Messages

Maybe you are looking for