Overriding Soap Header using Axis(SOAP) Receiver

Hi Experts,
I am having a problem in including the SOAP Header in the XML using the SOAP Axis Receiver Adapter. Well I am not sure on how to place this structure in the header:
<SoapHeader>
    <Header1>
        <child1>
        <child2>
    </Header1>
    <Header2>
        <child1>
        <child2>
    </Header2>
</SoapHeader
I have already tried overriding the SOAP Header via Java Mapping but it is not working when I send it to the third-party. I believe this header should be directly encoded using the axis module, but I can only find examples for simple headers and not nested ones...
Please help.
Edited by: Mark Dihiansan on Sep 7, 2010 5:15 PM

Hi,
you simply place your header template in the handler configuration. If you need to set some values of the header dynamically, you can pass each value in the dynamic configuration header. The axis handler will fill the header with the supplied values.
The Axis Note 1039369 describes a few header insertion examples that you should look at.
regards, yza

Similar Messages

Handling SOAP HEADER using SOAP Receiver Adapter

Hi Experts,
I need to implement SOAP Receiver Scenario and passing ( Header fields User, Password and token) I have seen a lot of scenario using a XSLT Mapping, to handling the SOAP Header. So need to help to understand some details:
Suppose I need to implement the SOAP Header below? In this case I need add only the fields u201CUsername, Password and AuthenticationTokenu201D. I created the XSLT Transform, the source XML? Where I put it? Or can create it into Message Interface?
Is it possible to do this in Java Mapping?
Thanks!
Best Regards
Fábio Ferri
<soap:Header>
      <v1:ExecutionHintHeader>
         <v1:Name></v1:Name>
         <!Optional:>
         <v1:Arguments>
            <!1 or more repetitions:>
            <v1:Argument Name="?" Value="?"/>
         </v1:Arguments>
      </v1:ExecutionHintHeader>
      <v1:CredentialsHeader>
         <!Optional:>
         <v1:Username>pi</v1:Username>
         <!Optional:>
         <v1:Password>jhjhjjhjhjius</v1:Password>
         <!Optional:>
         <v1:AuthenticationToken></v1:AuthenticationToken>
      </v1:CredentialsHeader>
   </soap:Header>

You need to put XSLT mapping in 2° step mapping in request.
SourceMessageRequest -> Message Mapping -> XSLT Mapping -> DestinationMessageRequest
If you test mapping program, this should be working fine.
In adapter module, put localejbs/AF_Modules/MessageTransformBean with parameter value text/xml; charset=utf-8 and correctly set Conversion Parameter "Do not use Soap Envelop"
XSLT Request Mapping
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Header>
<ServiceAuthHeader xmlns="http://WIND.WEBSERVICES.DMS/">
<Username>USER</Username>
<Password>PASSWORD</Password>
</ServiceAuthHeader>
</soap:Header>
<soap:Body>
<xsl:copy-of select="*"/>
</soap:Body></soap:Envelope>
</xsl:template>
</xsl:stylesheet>

SOAP Receiver adapter : SOAPAction Header appears 2 times using ASMA param

Hi,
I'm using a PI7.1 SOAP receiver channel that uses the ASMA variable THeaderSOAPAction to dynamically add the SOAP action during the mapping. All works fine except that apparently also the 'standard' SOAP action field from the adapter still appears in the request.
( regardless of whether its empty or not )
e.g. the headers from my message look like this
Content-Type: text/xml; charset=utf-8
Content-Length: 863
SOAPACTION: "test"
SOAPACTION: "SetFromASMA"
I'm using conf.put to set the variable in the map. Should I use other method to 'replace' the existing ?
Did somebody experience this as well ? Any suggestions ?
rgds
Dirk

Hi Michael,
Yes, I did see this but :
1) The 'replace' command here is just a java string replace command to manipulate the content before setting the dynamic variable ( nothing to do with replacing an existing dynamic variable in the HTTP headers )
2) I did add first a 'get' to my code after seeing this but that did not work neither ( it even seems that at the time of mappnig execute the static value from the channel is not yet known as the 'get' returns a blank value for the key. ( but then again this is normal because we are only at the mapping step )
It seems that the adapter does not check upfront ig a SOAPACTION was already present or not
( I think this worked in PI 7.0 )
I will submit an oss,
rgds
dirk

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>

SOAP Receiver - HTTP header problem

Hi,
Scenario: IDOC - - XI - - SOAP(webservice).
Third party is asking for missing "/" (path?) in header after "POST". Following is the message received by third party. How to override this header to put "/" after POST? Please help.
POST HTTP/1.0
Accept: /
Host: 100.10.2.5:9092
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
Authorization: Basic Z2hydHNvYXA6bm92ZWxs
content-id: <soap-48E034BD9F5B3308E1000000876CF529@sapcom>
Content-Type: text/xml; charset=utf-8
Content-Length: 313
SOAPACTION: "#batchRequest"
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
    <SOAP:Header/>
    <SOAP:Body>
        <ns0:cvgtransaction xmlns:ns0='http://abc.com/xi/Novell' event='modify' workforceID='1' type='employee'>
            <attribute name='WWID' operation='replace'>1234567</attribute>
        </ns0:cvgtransaction>
    </SOAP:Body>
</SOAP:Envelope>

Hi!
with XI standard tools you have no chance to manipulate the soap envelope created by the XI. You have to configure your soap receiver communication channel to not create a soap envelope "Do not use SOAP envelope") and then you use e.g. a XSLT mapping to create a soap envelope by yourself.
Regards,
Volker

SOAP Receiver Adapter - Read Header data on Synchronous Response

I have a scenario - flat file to SOAP. The web service provider sends a response that contains data in the Header that I need to access. I have tried to use the "Do Not Use SOAP envelope" option on my receiver SOAP adapter, and I have configured my request message type to include the soap envelope elements. However I'm getting the following error from the web service
com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Cannot process the message because the content type 'application/xml' was not the expected type 'text/xml; charset=utf-8'.
I've read some inputs on this error that say to use the Transform bean to adjust the content to text/xml. However I'm not sure how to do that. If that is the correct resolution to my problem, can someone provide detailed steps on how to add the Transform bean to the adapter module. I have no experience with adding items to the module tab.
If there are other ways to tackle this scenario to get access to the SOAP Header from the SOAP receiver adapter, please share those as well.
Thanks in advance.
Chris

Resolved with the following blog
/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi

SOAP Header in SOAP Receiver adapter

Hi All,
I am doing a Proxy to Webservice scenario where webservice requires the SOAP request as below.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header>
        <mh:CustomHeader xmlns:mh="http://schemas.test.com/customHeader">
            <mh:MessageData>
                <mh:MessageId>12345</mh:MessageId>
                <mh:Timestamp>2004-06-09T14:41:44Z</mh:Timestamp>
            </mh:MessageData>
        </mh:CustomHeader>
        <wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/04/secext">
            <wsse:UsernameToken>
                <wsse:Username>test</wsse:Username>
                <wsse:Password>test123</wsse:Password>
            </wsse:UsernameToken>
        </wsse:Security>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
    </SOAP-ENV:Body>
Need your help to understand how can we achieve this using Standard SOAP adapter to customize the Header part as it requires to include "<mh:CustomHeader " & "UsernameToken".
Or Do i need to go for adapter module development to create this SOAP request.
Please provide your suggestion to achieve this scenario.
Thanks & regards
Ashwin
Edited by: ashwin dhakne on May 17, 2010 5:32 PM

Hi all,
Created a below target payload in a message mapping with SOAP Header & Body part as per the requirement.
In SOAP receiver communication channel, checked the option " Do Not Use SOAP Envelope".
But while executing an sceanrio, i am facing an error in SOAP receiver channel as Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
And if i don't check the option " Do Not Use SOAP Envelope" it gives an error as
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Unable to obtain service binding,error=Payload Envelope is not a known message for TestWebserviceService.
Please provide your suggestions to handle this issue.
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:Envelope xmlns:ns1="http://schemas.test.com/CustomrHeader">
<ns1:Header>
<ns1:CustomrHeader>
<ns1:MessageData>
<ns1:MessageId>Constant</ns1:MessageId>
<ns1:Timestamp>Constant</ns1:Timestamp>
</ns1:MessageData>
<ns1:Security>
<ns1:UsernameToken>
<ns1:Username>Constant</ns1:Username>
<ns1:Password>Constant</ns1:Password>
</ns1:UsernameToken>
</ns1:Security>
</ns1:CustomrHeader>
</ns1:Header>
<ns1:Body>
<ns1:Details>
<ns1:Information>
<ns1:Title>Test</ns1:JobTitle>
</ns1:Information>
<ns1:Contacts>
<ns1:Street>Test Drive</ns1:Street />
</ns1:Contacts>
</ns1:Details>
</ns1:Body>
</ns1:Envelope>
Thanks
Ashwin
Edited by: ashwin dhakne on May 18, 2010 5:47 PM
Edited by: ashwin dhakne on May 18, 2010 5:48 PM
Edited by: ashwin dhakne on May 18, 2010 5:48 PM

Any one knows how to use Axis Framework in the SOAP Adapter Modules

How to use Axis Framework in the SOAP Adapter?
How to add custom handler modules?
http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/frameset.htm
I went through the above link on help.sap.com. But still could not create a working example.
I have created a wc on some 3ed party app server using apaches axis. I am trying to call that web service from XI using SOAP receiver? I need to add some security related headers to the soap message, SO I am trying to use a handler. I want to know how to configure this handler in SOAP axis adapter module.
Thank you
Moni

Ravi ,
I am trying exactly the same. Hers is the scenario.
ABAP Proxy --> PI (7.0) SP 12 ---> WebService.
Since This is service is secured, means it is using OASIS web servie securyty user name token,
I am trying to use AXIS adapter. and I want to configure HandlerBean in which I want to use apache wss4j api to add the userNameToken. I am looking for some documentation on this.
I need to add SOAP action element too as I can not configure this one on the communication channel.
Thanks for any inputs in this regard.
Moni

"Do Not Use Envelope" feature: WS Receiver vs Soap Receiver

I have a scenario that I need to call web service on receive side.
When I use Soap adapter, need to use mapping program to compose SOAP message mannully:
Envelope
   + Header
     ++MessageID
     ++Action
   +Body
     ++FistName
     ++FistName
In SOAP receiver adapter, I do not use PI envlope, so I have to choose "Do Not Use Soap Envelope" option.
When I use WS receiver adapter to call the same web service, I could not find the way the Soap adapter does.
Anyone tried to use same feature in WS adapter ?
Thanks
Liang
Edited by: Liang Ji on Oct 27, 2011 4:33 PM

>Anyone tried to use same feature in WS adapter ?
IMO, WS adapter does not provide "Do Not USe Envelope option" in 7.1 as well in above versions.   You might want to see other experts opinion.

Creating SOAP Receiver comm.channel for axis web service

Hi,
I created Soap Receiver comm. channel fro Axis web service like below:
*Target URL* : http://<IP>:<Port>/<x>/service
*User:* <user>
*Password :* <password>
*SOAP Action:* <target namespace>/method
when i drive PI Message that use Soap Receiver it get error below
I do same method for .Net web service, it runs properly.
How can i solve this problem?
Error
<?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>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID B3004965647F340C997B5F2CC9EA7E22 Software Component 4CF44F80503211DEB2A0D3F40A194B29</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID B3004965647F340C997B5F2CC9EA7E22 Software Component 4CF44F80503211DEB2A0D3F40A194B29</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hi,
I did all but nothing changed?
I have doubt about axis side. Because respose like below.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
May be Soap Receiver setting for axis web service must be different.
Thanks.

Soap receiver - owerwrite default http header fields

Hi,
I'm using the soap receiver adapter in nosoap mode.
How can I owerwrite the default settings for the header fields in the http request?
The soap adapter will automatically set content-type = application/xml.
I would like for example set "text/xml".
Thanks,
Bela

Dear Mohan,
I tryed with the keep headers option but it didn't change anything to the HTTP header fields.
In the documentation we have the following : Keep Headers
If you want to include the header of the XI message in the Web service message, set the indicator.
Does it mean that I have to create a HTTP header section in the XI message??? Do you have an example?
Best regards,
Bela

Error on SOAP Receiver for Axis

Hi all,
Is there anybody to help for solution?
Thanks.
Error on SOAP Receiver for axis
Error Message
<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: 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@3ff5ea5d 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</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

We deployed com.sap.aii.af.axisproviderlib.sda to use SOAP for axis.
We sent data from SAP to Axis, error below ocured?
What must we do to solve problem?
Thanks.
Error
<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: handler is not instantiated org.apache.axis.ConfigurationException: handler is not instantiated at com.sap.aii.adapter.axis.modules.HandlerCore.process(HandlerCore.java:73) at com.sap.aii.adapter.axis.modules.HandlerBean.process(HandlerBean.java:75) at sun.reflect.GeneratedMethodAccessor360_10000.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 $Proxy2634_10000.process(Unknown Source) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:275) 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 $Proxy1431_10000.process(Unknown Source) at com.sap.aii.af.app.listener.AFWListenerBean.onMessage(AFWListenerBean.java:332) 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 $Proxy1479_10000.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:921) 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>

SOAP Receiver Adapter using SSL - PI 7.0

Hi all,
i am currently faced with a .net WCF webservice integration using https via SOAP Receiver Adapter in PI 7.0.
Can anybody tell me into which Visual Administrator view i have to import my certificate in order to get https working ?
Thanks in advance,
Martin

It must be the View you have created for your partners. There is usually a Trusted view where you have your own certificate. And there are other views where partners cerificates are stored. There you have to store the certificate.
Regards,
Prateek

Problem in testing SOAP receiver adapter using SOAP UI

Dear Experts,
I'm trying to test my SOAP receiver adapter as mentioned in the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/21844. [original link is broken] [original link is broken] [original link is broken] But, my request from ECC proxy keeps failing in XI communcation channel monitor. I've configured my receiver adapter http://ip:8080/mockSoapHTTPBinding and kept the authentication as NONE. Can any of you suggest?
ip - is my system ip shown in ipconfig.
mockSoapHTTPBinding - is the path.
Thanks.

What is the error of the messages? Are the messages leaving the SOAP adapter?
Please try both:
1. Go to Runtime Workbench -> Component Monitoring -> Adapter Engine -> Test message. Then, execute the message directly without the intermediate of the Proxy sender. This will allow you to check only the receiver SOAP.
2. Please use the TCPGateway tool attached from the note below. It will be a "man-in-the-middle" between the target WS and the Receiver SOAP channel, tracking the whole HTTP/SOAP message. Check if the message is well-formed.
[Note 856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=856597]
under question "Q: How can I trace the whole message?"

SOAP Receiver to use operations and methods

Hi.
I have got a WSDL with 3 methods and I have to call one of them.
However, the SOAP Receiver adapter only has a Action section which can be maintained.
How can this be attained?
The WSDL I am using is as follows:
<?xml version="1.0" encoding="ISO-8859-1"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:tns="urn:uniface:applic:services:CSYV1000" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" targetNamespace="urn:uniface:applic:services:CSYV1000" name="CSYV1000">
     <wsdl:types />
     <wsdl:message name="EXTERNALRequest">
          <wsdl:part name="REQUEST" type="s:string" />
          <wsdl:part name="REQUESTDATA" type="s:string" />
     </wsdl:message>
     <wsdl:message name="LOGOFFRequest">
          <wsdl:part name="REQUEST" type="s:string" />
     </wsdl:message>
     <wsdl:message name="LOGONRequest">
          <wsdl:part name="REQUEST" type="s:string" />
     </wsdl:message>
     <wsdl:message name="EXTERNALResponse">
          <wsdl:part name="return" type="s:int" />
          <wsdl:part name="RESPONSE" type="s:string" />
          <wsdl:part name="RESPONSEDATA" type="s:string" />
          <wsdl:part name="RESPONSEERROR" type="s:string" />
     </wsdl:message>
     <wsdl:message name="LOGOFFResponse">
          <wsdl:part name="return" type="s:int" />
          <wsdl:part name="RESPONSE" type="s:string" />
          <wsdl:part name="RESPONSEERROR" type="s:string" />
     </wsdl:message>
     <wsdl:message name="LOGONResponse">
          <wsdl:part name="return" type="s:int" />
          <wsdl:part name="RESPONSE" type="s:string" />
          <wsdl:part name="RESPONSEERROR" type="s:string" />
     </wsdl:message>
     <wsdl:portType name="CSYV1000PortType">
          <wsdl:operation name="EXTERNAL" parameterOrder="REQUEST REQUESTDATA RESPONSE RESPONSEDATA RESPONSEERROR">
               <wsdl:input message="tns:EXTERNALRequest" />
               <wsdl:output message="tns:EXTERNALResponse" />
          </wsdl:operation>
          <wsdl:operation name="LOGOFF" parameterOrder="REQUEST RESPONSE RESPONSEERROR">
               <wsdl:input message="tns:LOGOFFRequest" />
               <wsdl:output message="tns:LOGOFFResponse" />
          </wsdl:operation>
          <wsdl:operation name="LOGON" parameterOrder="REQUEST RESPONSE RESPONSEERROR">
               <wsdl:input message="tns:LOGONRequest" />
               <wsdl:output message="tns:LOGONResponse" />
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:binding name="CSYV1000Binding" type="tns:CSYV1000PortType">
          <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc" />
          <wsdl:operation name="EXTERNAL">
               <soap:operation soapAction="" />
               <wsdl:input>
                    <soap:body use="encoded" namespace="urn:uniface:applic:services:CSYV1000" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
               </wsdl:input>
               <wsdl:output>
                    <soap:body use="encoded" namespace="urn:uniface:applic:services:CSYV1000" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
               </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="LOGOFF">
               <soap:operation soapAction="" />
               <wsdl:input>
                    <soap:body use="encoded" namespace="urn:uniface:applic:services:CSYV1000" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
               </wsdl:input>
               <wsdl:output>
                    <soap:body use="encoded" namespace="urn:uniface:applic:services:CSYV1000" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
               </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="LOGON">
               <soap:operation soapAction="" />
               <wsdl:input>
                    <soap:body use="encoded" namespace="urn:uniface:applic:services:CSYV1000" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
               </wsdl:input>
               <wsdl:output>
                    <soap:body use="encoded" namespace="urn:uniface:applic:services:CSYV1000" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:service name="CSYV1000Service">
          <wsdl:port name="CSYV1000" binding="tns:CSYV1000Binding">
               <soap:address location="http://localhost/pathway/environment.pathway" />
          </wsdl:port>
     </wsdl:service>
</wsdl:definitions>
Your help is appreciated.
Regards,
Reenal

Hi, Amit.
The problem arises when I send a logon messages from XI, it fails.
The request which works is:
<?xml version="1.0" encoding="utf-16"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="urn:uniface:applic:services:CSYV1000" xmlns:types="urn:uniface:applic:services:CSYV1000/encodedTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <tns:LOGON>
      <ns0:REQUEST xmlns:ns0="urn:aucklandcity-govt-nz:filenet:property_search"><service>CSYV1000</service><trace/><groupId/><product>SAP XI</product><processId/><threadId/><nodeId/><ipAddress/><sourceUserId/><sourceOSUserId/><uiForm>CMNQ1030</uiForm><groupIdPrevious/><userId>albadryh</userId><password>husain</password><osUserId></osUserId></ns0:REQUEST>
    </tns:LOGON>
</soap:Body>
</soap:Envelope>
The problem is that XI is not adding the <tns:LOGON> tags.
Regards,
Reenal

Overriding Soap Header using Axis(SOAP) Receiver

Similar Messages

Maybe you are looking for