Header autentication Receiver HTTP (soap-axis)

hi,
I need to place the authentication in the header to the SOAP receiver channel is for soap-http axis.
Place the authentication module, but the monitor shows pi invalid username and password.
Was entered in the module, but does not work
ParameterName Module Key Parameter Value
wssec UsernameToken action
wssec Handler.Type java: com.sap.aii.adapter.axis.ra.handlers.security.WSDoAllSender
wssec passwordType PasswordText
wssec pwd.password <enter password> = <enter password>
wssec user <enter username>
How rare header from soapUI putting in username and password works, but since IP does not work, it no longer occurs to me that may be happening.
We spent a WSDL with soap12, you can from an XSL add the user and password or may be going ?.
Greetings.

Hi Diego
Check this links
SOAP Header Authentication
https://websmp230.sap-ag.de/sap/support/notes/1039369
Regards
Osman

Similar Messages

How to configure message header in receiver http adapter?

Hi all
I need the outgoing message payload from receiver http adapter to backend system with below form.
POST http://222.222.33.22 /HTTP1.0
content-type:application/x-www-form-urlencoded
USERID=xxxxxx&PASSWORD=xxxx&SRCID=10&CDDATE=20070601...........................................................................
×POST http://222.222.33.22 /HTTP1.0
○content-type:application/x-www-form-urlencoded
○USERID=xxxxxx&PASSWORD=xxxx&SRCID=10&CDDATE=20070601...........................................................................
Is there a parameter to enable POST method as a part of message header outputing?
thanks in advance.

The parameters available in HTTP adapter for message header are:
HeaderFieldFive     http://sap.com/xi/XI/System/HTTP
HeaderFieldFour     http://sap.com/xi/XI/System/HTTP
HeaderFieldOne     http://sap.com/xi/XI/System/HTTP
HeaderFieldSix     http://sap.com/xi/XI/System/HTTP
HeaderFieldThree     http://sap.com/xi/XI/System/HTTP
HeaderFieldTwo     http://sap.com/xi/XI/System/HTTP
HTTPDest     http://sap.com/xi/XI/System/HTTP
TargetURL     http://sap.com/xi/XI/System/HTTP
URLParamFive     http://sap.com/xi/XI/System/HTTP
URLParamFour     http://sap.com/xi/XI/System/HTTP
URLParamOne     http://sap.com/xi/XI/System/HTTP
URLParamSix     http://sap.com/xi/XI/System/HTTP
URLParamThree     http://sap.com/xi/XI/System/HTTP
URLParamTwo     http://sap.com/xi/XI/System/HTTP

PI 7.11 Receiver SOAP (Axis) Adapter with MTOM (Attachments)

Hello,
Iu2019m trying to configure the Receiver SOAP (Axis) adapter for sending SOAP attachments via MTOM to a third-party webservice, but I'm not getting that PI transform the binary encode64 data in an payload element into a MTOM attachment (xop:include).
The configuration looks like this:
Transport Protocol: HTTP (Axis)
SOAP Version: 1.2
Encapsulation Format: MTOM
Keep Attchments: enabled
Payload Extraction: SOAP Body Child
First of all, could you confirm if this is supported?
Or Axis only supports MTOM for the transport protocol 'File (Axis)' like it seems refered in [Configuring the Receiver Axis SOAP Adapter|http://help.sap.com/saphelp_nwpi711/helpdata/en/45/a3c48c87cd0039e10000000a11466f/frameset.htm]
Can you please provide me some guidance here?
Thanks in advance!
Kind Regards,
Alexandre

Hello,
I am facing the exact same issue.
I can't seem to set the cookie in the http header after following the guide.
Cookie: WSL-credential=MyOwnCookie
I managed to set the SOAPAction though.
Anyone has any ideas?

SOAP Axis receiver: host parameter is null

Hello,
we are on a PI 7.11 (SP06) system & we are trying to setup a scenario SOAP - SOAP (Axis) where we initiate a third party webservice. To connect to this service we are obliged to go through our proxy, which we defined in our JVM parameters:
http.nonProxyHosts: [*.ont.local|*.val.local|*.mon.local]
http.proxyHost: [proxypac.mon.local]
http.proxyPort: [8080]
http.proxySet: true
When we execute our scenario via soapUI we get following error:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException:
java.lang.IllegalArgumentException: host parameter is null
We already tried with http://proxypac.mon.local as parameter as well but still we get this error.
Furthermore we are able to make a connection to the service via a SM59 connection.
Axis details:
Adapter Common Library Version: 1.7.1106.20110202095400.0000, NW711_06_REL
Adapter Application Version: 1.7.1106.20110202095400.0000, NW711_06_REL
Axis Version: Apache Axis version: 1.4 Built on Apr 22, 2006 (06:55:48 PDT)
Many thanks in advance for your help,
Frédéric.

Hello Mark,
we get this last error when connecting with SOAP receiver instead of Axis receiver.
We are sending different headers (wsa & wsse) in our soapUI request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:klip="http://ws.agiv.be/klipws" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header>
<wsa:Action xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://ws.agiv.be/klipws/ListKLB</wsa:Action>
<wsa:MessageID>urn:uuid:2a46571e-d5a7-4b33-a4a1-a174330cd36c</wsa:MessageID>
<wsa:ReplyTo> <wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address></wsa:ReplyTo>
<wsa:To>http://wsklip.beta.agiv.be/**********.asmx</wsa:To>
<wsse:Security soapenv:mustUnderstand="1" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:klip="http://ws.agiv.be/klipws" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
<wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsu:Created>2011-09-27T10:00:31Z</wsu:Created>
<wsu:Expires>2011-09-30T18:01:31Z</wsu:Expires>
</wsu:Timestamp>
<wsse:UsernameToken>
<wsse:Username>*********</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest">***************************************wsse:Password>
<wsse:Nonce>****************************************</wsse:Nonce>
<wsu:Created xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">2011-09-12T14:01:31Z</wsu:Created>
</wsse:UsernameToken>
</wsse:Security>
</soapenv:Header>
<soapenv:Body> <klip:ListKLB xmlns="http://ws.agiv.be/klipws"/>
</soapenv:Body>
</soapenv:Envelope>
For the Axis receiver it looks like one of the handlers can't get the value of our host parameter.
Any help or tips would be really appreciated!
Regards,
Frédéric.

SOAP receiver adapter for Axis

Hi,
I used SOAP receiver adapter for Axis like below:
Transport Prorocol : HTTP
Message Protocol : Axis
Url: http://<IP>:<Port>/xxx/WebService/services/Head/yyy
Authentication : Basic
User: <user>
Password: <password>
SOAP Version : 1.1
SOAP Action: : <method>
Encapsulation Format : MIME
Payload Extraction : SOAP Body
When i drive PI message it generates error below.
What must i do to solve this problem?
Thanks.
Error message
com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.ejb.EJBException: Exception in getMethodReady() for stateless bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: com.sap.engine.services.ejb3.util.pool.PoolException: javax.ejb.EJBException: Exception raised from invocation of public void com.sap.aii.adapter.axis.modules.AFAdapterBean.ejbCreate() throws javax.ejb.CreateException method on bean instance com.sap.aii.adapter.axis.modules.AFAdapterBean@20715646 for bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: javax.ejb.CreateException: java.lang.NoClassDefFoundError: org/apache/axis/types/URI$MalformedURIException

*Url:* http://172.28.6.194:8080/AssetManagerWebService/services/Head/SapTest
When i use Url with *?wsdl* it generates below (it'is very long. I give part of it)
wsdl
<?xml version="1.0" encoding="UTF-8" ?>
- <wsdl:definitions targetNamespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:intf="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:tns1="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Types" xmlns:tns2="http://schemas.hp.com/AssetManager/R51/ACMetaData" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- 
- <wsdl:types>
- <schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:AdministrationTypes="http://schemas.hp.com/AssetManager/Custom/Head/Administration/Types" xmlns:CableTypes="http://schemas.hp.com/AssetManager/Custom/Head/Cable/Types" xmlns:CatalogTypes="http://schemas.hp.com/AssetManager/Custom/Head/Catalog/Types" xmlns:ChargebackTypes="http://schemas.hp.com/AssetManager/Custom/Head/Chargeback/Types"
<import namespace="http://schemas.hp.com/AssetManager/R51/ACMetaData" />
<import namespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Types" />
- <annotation>
<documentation>Auto-generated schema for AssetCenter web services for Head/SapTest Implementation</documentation>
</annotation>
<import namespace="http://schemas.hp.com/AssetManager/Custom/Head/SAM/Types" schemaLocation="../../schema/Head/SAM/SAMTypes.xsd" />
<import namespace="http://schemas.hp.com/AssetManager/R51/ACMetaData" ......
<wsdl:operation name="retrieveAllBusinessAPIListByName">
<wsdlsoap:operation soapAction="retrieveAllBusinessAPIListByName" />
<wsdl:input name="retrieveAllBusinessAPIListByNameRequest">
<wsdlsoap:body use="literal" />
</wsdl:input>
<wsdl:output name="retrieveAllBusinessAPIListByNameResponse">
<wsdlsoap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SapTestService">
<wsdl:port binding="impl:SapTestSoapBinding" name="SapTest">
<wsdlsoap:address location="http://172.28.6.194:8080/AssetManagerWebService/services/Head/SapTest" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

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..

Frequency of Message Sending for HTTP/SOAP Receiver

hi,
is there a way to schedule a message for a particular time/situation until we get the response from the receiver?
Say i am connecting to a https://test.com/OrderReceive, for some reason the receiver has failed to receive the message.
Is there a way for HTTPS/SOAP like how we have for a FILE adapter to poll the message at a regular interval until we get a success response?
Thanks,
Tirumal

Hi Tirumal,
you can build a business process with a synchronous sendstep. In case of error you jump into an exception branch. There is an endless loop with a wait step and the same send step. In case of success you raise another exception which can end the process.
Sounds more complex than it is
Regards,
Udo

Problem with Dynamic Configuration in SOAP-AXIS adapter..!!!

Hi ,
Idoc> XI>SOAP-AXIS
I am doing a scenario where I need to pass the URL dynamically in SOAP-AXIS adapter by taking the SNDPRN of Idoc.
If SNDPRN = 100 , message has to go to http://10.190.25.16:8210/file/receiver
   SNDPRN = 200 , message has to go to http://20.180.26.16:8210/file/receiver
It is working correctly when I tried for single receiver. When I' tried to use DynamicConfiguration, it is coming in SOAP document but it is not working and not passing to correct channel. According to this note 1039369, I mentioned the following modules.
AF_Adapters/axis/AFAdapterBean --->                 afreq
AF_Adapters/axis/HandlerBean      --->                  xireq
AF_Adapters/axis/HandlerBean      --->                  dc
AF_Adapters/axis/HandlerBean       --->                 remover
AF_Adapters/axis/HandlerBean       --->                 trp
AF_Adapters/axis/HandlerBean        --->                xires
AF_Adapters/axis/AFAdapterBean    --->               afres
xireq -> handler.type-> java:com.sap.aii.axis.xi.XI30OutboundHandler
dc    -> handler.type-> javasap.aii.axis.xi.XI30DynamicConfigurationHandler
dc   --->   key.1 --->      write http://sap.com/xi/XI/System/SOAP TServerLocation
dc    --->          location.1 --->         context
dc     --->         value.1      --->        transport.url
remover    ---> handler.type    --->   java:com.sap.aii.axis.soap.HeaderRemovalHandler
remover     ---> namespace    --->      http://sap.com/xi/XI/Message/30
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
and I am getting the below error in SOAP-AXIS channel
Error Axis:    error in invocation: java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Error MP:     Exception caught with cause java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Error           Exception caught by adapter framework: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Error 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: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage: java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Kindly let me know if anyone has any idea what might be wrong?
Thanks
Deepthi

I have a similar problem. I also like to add some header fields to my message und that's way I'm trying to use the AXIS adapter. (Axis adapter FAQ question 30) Unfortunately I'm getting exactly the same error message:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Deepthi, you wrote that you have missed one jar file. Can you remember which file it was?

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.

Error while passing URL Dynamically in SOAP AXIS adapter..!!

Hi ,
Idoc> XI>SOAP-AXIS
I am doing a scenario where I need to pass the URL dynamically in SOAP-AXIS adapter by taking the RCVPRN of Idoc.
If
RCVPRN = 100 , message has to go to http://10.190.25.16:8210/file/receiver
RCVPRN = 200 , message has to go to http://10.190.25.16:8210/file/receiver2
RCVPRN = 300 , message has to go to http://10.190.25.16:8210/file/receiver3
I used the below UDF and it is working correctly and generating the URL dynamically .
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey keyHeader1 = DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/SOAP", "TServerLocation");
conf.put(keyHeader1, a);
return "";
The value is coming in SOAP document as expected like below.
<sap:DynamicConfiguration xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:Record namespace="http://sap.com/xi/XI/System/SOAP" name="TServerLocation">http://10.190.25.16:8210/file/receiver3</sap:Record>
</sap:DynamicConfiguration>
I used the below Configuration modules in receiver SOAP-AXIS adapter as suggested in Note 1028961.
AF_Adapters/axis/AFAdapterBean ---> afreq
AF_Adapters/axis/HandlerBean ---> xireq
AF_Adapters/axis/HandlerBean ---> dc
AF_Adapters/axis/HandlerBean ---> remover
AF_Adapters/axis/HandlerBean ---> trp
AF_Adapters/axis/HandlerBean ---> xires
AF_Adapters/axis/AFAdapterBean ---> afres
xireq -> handler.type-> java:com.sap.aii.axis.xi.XI30OutboundHandler
dc -> handler.type-> javasap.aii.axis.xi.XI30DynamicConfigurationHandler
dc ---> key.1 ---> write http://sap.com/xi/XI/System/SOAP TServerLocation
dc ---> location.1 ---> context
dc ---> value.1 ---> transport.url
remover ---> handler.type ---> java:com.sap.aii.axis.soap.HeaderRemovalHandler
remover ---> namespace ---> http://sap.com/xi/XI/Message/30
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
and I am getting the below error in SOAP-AXIS channel at the point java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender.
2009-03-02 15:23:44 Success Axis: getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
2009-03-02 15:23:45 Error Axis: error in invocation: (500)internal server error
2009-03-02 15:23:45 Error MP: Exception caught with cause (500)internal server error
2009-03-02 15:23:45 Error Exception caught by adapter framework: (500)internal server error
2009-03-02 15:23:46 Error 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: (500)internal server error: (500)internal server error.
2009-03-02 15:23:46 Error The message status set to NDLV.
Kindly let me know if anyone has any idea what might be wrong?
Note : The given URL is correct one because I cross checked by passing them normally by giving directly in adapter and they are all working and the message is going to receiver.
Thanks
Deepthi

Hi Stefan,
>> dc -> handler.type-> javasap.aii.axis.xi.XI30DynamicConfigurationHandler
>> dc ---> key.1 ---> write http://sap.com/xi/XI/System/SOAP TServerLocation
>> dc ---> location.1 ---> context
>> dc ---> value.1 ---> transport.url
>> Try read instead of write
When I tried with this, I am getting the below error "Connection refused ".
Success Axis: entering HandlerBean
Success Axis: getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
Error Axis: error in invocation: java.net.ConnectException: Connection refused
Error MP: Exception caught with cause java.net.ConnectException: Connection refused
Error Exception caught by adapter framework: ; nested exception is: java.net.ConnectException: Connection refused
Error 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: ; nested exception is: java.net.ConnectException: Connection refused: java.net.ConnectException: Connection refused.
Success The message status set to WAIT.
It is going successfully when I tried sending directly. Looks like Dynamic Configuration is not working for SOAP-AXIS.
Any Suggestion?
Thanks
Deepthi.

Received HTTP response code 500 : Error during conversion of XI message

hi
Facing the error , "Received HTTP response code 500 : Error during conversion of XI message"
This is the fist time i am configuring the sender soap ( Axis Framework in the SOAP Adapter) (Quality of service Best effort) communication channel and i am getting the above error did any body face this error.
01.09.2011 12:02:32     Information     The message status was set to DLNG.
01.09.2011 12:02:32     Error     SOAPFault received from Integration Server. ErrorCode/Category: XIServer/ATTRIBUTE_INITIAL; Params: Manifest cid:6D90482BF678436D75928FC8B9930519; AdditionalText: null; ApplicationFaultMessage: null; ErrorStack: Attribute Manifest cid:6D90482BF678436D75928FC8B9930519 is initial
01.09.2011 12:02:32     Error     Transmitting the message using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Error during conversion of XI message.
regards
sandeep
Edited by: pendyalas on Sep 1, 2011 12:20 PM

I found a link with respect to similar error , sap note 1522630 has been used to resolve this error.
i will try and see if it works.
AXIS Sender Adapter Failure after upgrade to PI 7.11 SP06
regards
sandeep

HTTP - SOAP

Hi gurus,
We want to create the following scenario:
HTTP - XI - SOAP
We have test with several combinations of the parameters of the HTTP Adapter Sender and the SOAP Adapter Receiver and we obtain:
java.io.IOException: invalid content type for SOAP: APPLICATION/OCTET-STREAM
at com.sap.aii.messaging.net.MIMEInputSource.readBody(MIMEInputSource.java:363)
at com.sap.aii.messaging.net.MIMEServletInputSource.parse(MIMEServletInputSource.java:58)
at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:359)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
or
XIServerUNKNOWN.DeliveryException
com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:CANNOT_READ_PAYLOAD:
at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:451)
at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:125)
at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:831)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Also we have proven with several modules and parameters in the SOAP Adapter.
The HTTP Service is run (sicf) and SOAP too.
They do not exist mappings, both structures are identical. We test the operation by means of a page HTML with the method post.
In the HTTP Adapter we have checked Apply URL Parameters and added the names of the parameters that we will send in the Post.
What can be happening?
Thanks

I attempt to explain better:
I use a page .html (POST) in order to invoke a one Web Service.
HTTP Adapter Sync--> Web Service (SOAP)
I configure HTTP Adapter Sender:
<a href="http://es.geocities.com/jsahagung/SDN/HTTPSender.JPG">HTTP Adapter Sender Configuration</a>
I configure SOAP Adapter Receiver:
<a href="http://es.geocities.com/jsahagung/SDN/SOAPReceiver.JPG">SOAP Adapter Receiver Configuration</a>
and
<a href="http://es.geocities.com/jsahagung/SDN/SOAPReceiver-Module.JPG">SOAP Adapter Receiver Configuration</a>
The code of HTML:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<TITLE>Test HTTP Adapter</TITLE>
</HEAD>
<BODY>
<FORM METHOD=POST ACTION="http://host:ABAPPort/sap/xi/adapter_plain?namespace=http%3A//calculadora.es
&interface=MI_OUT&service=BS_Sender&QOS=BEhttpclient&sap-user=XXXXXXXXXX
&sap-password=XXXXXXXX&sap-client=XXX">
OPER1: <INPUT TYPE="text" NAME="OPER1"><BR>
OPER2: <INPUT TYPE="text" NAME="OPER2"><BR>
OPERATOR: <INPUT TYPE="text" NAME="OPERATOR"><BR><BR>
<INPUT TYPE="submit">
</FORM>
</BODY>
</HTML>
Well, with this configuration, the error that shows is: CANNOT_READ_PAYLOAD.
If I delete module "localejbs/AF_Modules/MessageTransformationBean" and checked "Do not Use SOAP Envelope" the error that shows is: "invalid content type for SOAP: APPLICATION/OCTET-STREAM".
I don't mapping.
The content-type of request is application/x-www-form-urlencoded (SXMB_MONI)
My questions are:
1 - What is wrong?
2 - How I must to configurate communication channel so that the scenario works?
3 - Is Message Mapping with Java mapping necesary?
4 - Are there any blog with this scenario?
5 - The HTTP Adapter automatically doesn't transform request HTTP into XML/XI?

Want to send information in Header dynamically using HTTP adapter using post method

Hi ,
I have a requirement to send below information in http Adapter header dynamically using post method. which will be authenticated by third party system.
Authorization : WSSE realm="SDP", profile="UsernameToken", type="AppKey" X-WSSE : UsernameToken Username="XXXX", PasswordDigest="Qd0QnQn0eaAHpOiuk/0QhV+Bzdc=", Nonce="eUZZZXpSczFycXJCNVhCWU1mS3ZScldOYg==", Created="2013-09-05T02:12:21Z"
I have followed below link to create UDF
http://scn.sap.com/thread/3241568
As if now my third party system is not available while sending request I am getting 504 gateway error. is there any approach I can validate my request is working fine?
Regards,

Hi Abhay,
Correct me if I'm wrong but I think WSSE requires a SOAP Envelope. If that is the case, there are two approaches: the first one is to use SOAP Axis and the second one is just to build SOAP Envelope via Java mapping.
You also need to test it successfully externally, capture the request and replicate it in XI.
Hope this helps,
Mark

Receive complete SOAP Envelope as message

Dear all
I have a web service that I have to consume which has a signature value in the SOAP header. In order that I can validate the signature with the message I would like to receive the complete SOAP envelope as (XML) message (<envelope>...<soap-env:header>...</soap-env:header>...<soap-env:body></soap-env:body></envelope>).
I couldn't find a solution for this.
Currently I use the WCF-Custom adapter to receive the multi part message (xml schemas created with svcutil) and receive the body as XML file. I also know how to access the SOAP header in the message but I would like to know if its possible to receive the
complete envelope as message.
Best regards
Jerome

Orchestration subscription includes value for BTS.MessageType context property, this mean you can't start orchestration with the soap envelope message type because the XmlDisassembler Component will discard the soap:Envelope content and the messaging engine
will only get the soap:Body content – so at the end of the process, BTS.MessageType context property will be set to the actual message type of content under soap:Body section and the orchestration will never start with the type soap:Envelope.
In case you need to process the entire soap:Envelope inside orchestration:
Use PassThruReceive pipeline.
Define message of type BTS.soap_envelope_1__1 message inside the orchestration (Message Type > schemas > from referenced assembly > Microsoft.BizTalk.GlobalPropertySchemas).
Use Xml Document as the incoming message.
Assign the incoming Xml Document message to the BTS.soap_envelope_1__1 message.
Reference :
http://pinhask.blogspot.in/2008/06/processing-soap-envelope-within-biztalk.html
Thanks
Abhishek

Convert XML payload to HTML form data in Receiver HTTP Adapter

Hi,
I want to make a HTTP request ( Receiver HTTP Adapter ) to a servlet where I need to send the payload in HTML form format ( name=value ). As per the help document:
A typical HTML form comprises named fields. When transferring a completed form to the server or a CGI program, the data must be transferred in such a way that the CGI script can recognize the fields that make up the form, and which data was entered in which field.
The plain HTTP adapter constructs this format using a prolog and an epilog
Has anyone done this before? I looked through all help documents and forums but in vain. I can resort to Java Mapping to do this but I do not want to re-invent the wheel if I can do it easily using HTTP Adapter Configuration. Please help.

The parameters available in HTTP adapter for message header are:
HeaderFieldFive     http://sap.com/xi/XI/System/HTTP
HeaderFieldFour     http://sap.com/xi/XI/System/HTTP
HeaderFieldOne     http://sap.com/xi/XI/System/HTTP
HeaderFieldSix     http://sap.com/xi/XI/System/HTTP
HeaderFieldThree     http://sap.com/xi/XI/System/HTTP
HeaderFieldTwo     http://sap.com/xi/XI/System/HTTP
HTTPDest     http://sap.com/xi/XI/System/HTTP
TargetURL     http://sap.com/xi/XI/System/HTTP
URLParamFive     http://sap.com/xi/XI/System/HTTP
URLParamFour     http://sap.com/xi/XI/System/HTTP
URLParamOne     http://sap.com/xi/XI/System/HTTP
URLParamSix     http://sap.com/xi/XI/System/HTTP
URLParamThree     http://sap.com/xi/XI/System/HTTP
URLParamTwo     http://sap.com/xi/XI/System/HTTP

Header autentication Receiver HTTP (soap-axis)

Similar Messages

Maybe you are looking for