AXIS SOAP Adapter

[Former Member]

Hi,

Can we use message transformation bean in SOAP adpter with transport protocol as HTTP (Axis).Can anyone please Help on this.

Thanks,

Dinesh

[Former Member · Accepted solution]

Hi Dinesh,

Yes, you can use message transformation bean with the SOAP adapter using the Servlet(Axis) Transport protocol and Axis Message protocol.

In the Module processing sequence call the MessageTransformBean before CallSapAdapter. Other Modules like HandlerBean and AFAdapterBean will be populated automatically as you select the Axis protocol in the communication channel.

0 - AF_Adapters/axis/HandlerBean

1 - AF_Adapters/axis/AFAdapterBean

2 - localejbs/AF_Modules/MessageTransformBean

3 - CallSapAdapter

4 - AF_Adapters/axis/AFAdapterBean

5 - AF_Adapters/axis/HandlerBean

For more information:

Adding modules in Axis SOAP Adapter:

http://help.sap.com/saphelp_nwpi71/helpdata/en/45/a4a36de28552f7e10000000a1553f7/content.htm

Configuring the Receiver Axis SOAP Adapter:

http://help.sap.com/saphelp_nwpi71/helpdata/en/45/a3c48c87cd0039e10000000a11466f/content.htm

Regards,

Aravind

[Former Member · Accepted solution]

Hi Ajnayak,

Thanx for your quick response.

We have configured SOAP Receiver adapter as you mentioned..But getting the error as below.Is it because are we missing any jar files in XI

Message processing failed. Cause: 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@4de787c4 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/AxisFault

Thanks,

Dinesh

[Former Member · Accepted solution]

Hi Dinesh,

Check this thread :

Check SAP Note: 1039369 - FAQ XI Axis Adapter

Thanks,

[Former Member · Accepted solution]

HI Harrenkumar,

we are coming across error has NoClassDefFoundError: org/apache/axis/AxisFault.But the link which you have sent tells about

org/apache/axis/types/URI$MalformedURIException .Can you please suggest on this what went wrong.

Thanks,

Dinesh

[Former Member · Accepted solution]

Hi,

Hope you have done these entries:

Processing Sequence:

0 - AF_Adapters/axis/HandlerBean : xireq

.........

.........

.........

5 - AF_Adapters/axis/HandlerBean : xires

Module Configuration:

xireq : handler.type : java:com.sap.aii.axis.xi.XI30InboundHandler

xires : handler.type : java:com.sap.aii.axis.xi.XI30InboundHandler

Regards,

Aravind

[Former Member · Accepted solution]

Hi Dinesh,

The issue might be with the sequesnce of processing, also please check the WSDL deployed.

Thanks,

[Former Member · Accepted solution]

Hi,

yes..these parameters are coming automatically once we create the channel....

In our channel its coming as

xireq : handler.type : java:com.sap.aii.axis.xi.XI30OutboundHandler

xires : handler.type : java:com.sap.aii.axis.xi.XI30OutboundHandler

i.e OutboundHandler instead of Inbound handler. We are using SOAP receiver channel.

Our WSDL is listed below

<definitions

name="UEBIBrokerInterfaceServiceName"

targetNamespace="UEBIBrokerInterface"

xmlns:tns="UEBIBrokerInterface"

xmlns="http://schemas.xmlsoap.org/wsdl/"

xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/">

<message name="TEBIBrokerInterface_PublishWS">

<part name="aClientId" type="xsd:string"/>

<part name="aUser" type="xsd:string"/>

<part name="aPassword" type="xsd:string"/>

<part name="aDomain" type="xsd:string"/>

<part name="aApplication" type="xsd:string"/>

<part name="aSchema" type="xsd:string"/>

<part name="aDestination" type="xsd:string"/>

<part name="aReference" type="xsd:string"/>

<part name="aMessage" type="xsd:string"/>

<part name="aMessageFormat" type="xsd:int"/>

<part name="aDuplicates" type="xsd:int"/>

</message>

<portType name="UEBIBrokerInterfacePortType">

<operation name="TEBIBrokerInterface_PublishWS">

<input message="tns:TEBIBrokerInterface_PublishWS"/>

<output message="tns:TEBIBrokerInterface_PublishWSResponse"/>

</operation>

</portType>

<binding name="UEBIBrokerInterfaceBinding" type="tns:UEBIBrokerInterfacePortType">

<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>

<operation name="TEBIBrokerInterface_PublishWS">

<soap:operation soapAction="urn:UEBIBrokerInterface#TEBIBrokerInterface_PublishWS" style="rpc"/>

<input>

<soap:body use="literal" namespace="UEBIBrokerInterface" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>

</input>

<output>

<soap:body use="literal" namespace="UEBIBrokerInterface" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>

</output>

</operation>

</binding>

<service name="UEBIBrokerInterfaceService">

<port name="UEBIBrokerInterfacePort" binding="tns:UEBIBrokerInterfaceBinding">

<soap:address location="https://asp26.sedeb2b.com:9020"/>

</port>

</service>

</definitions>

Can you please help on this?

Thanks,

Dinesh

[Former Member · Accepted solution]

Hi Dinesh,

I think some of the Jar files are missing. Try to re-deploy.

Thanks,

[Former Member · Accepted solution]

Thank You for ur Response