WS to WS scenario - SOAP Action error

[Former Member]

Hi,

I am working on a WebService to WebService Scenario and stuck with an error. The error message at CALL RECEIVER ADAPTER stage is as below.

"soap fault: Action cannot be processed at the receiver. Check the Payload and Action to ensure you are using the proper attributes specified in the TLI. The error raised was System.NullReferenceException: Object reference not set to an instance of an object. at MohawkCollege.EHR.HIAL.Communications.LRSCommunicator.InvokeHttp(String url, String responseAction, Message request, Boolean newOid)"

Can anybody help. The URL and the SOAP action

[Former Member]

Check the soap action.

Come soap actions will have namespace/soapaction ( Check weather it is declared like that in wsdl file)

eg : http://.........../soapaction

U need to place http//.......//soapaction on soap action field in receiver adapter...

Regards,

Jayasimha JAngam

[Former Member]

hi,

while defining the theSOAP CC you need to specify 2 things,

1) SOAP URL

2)SOAP action

you need to copy these 2 parameter from the WSDL file provided.

please also check the message tab while consuming the WS , there must be 2 message type like soapIn and soap out.

create the interface as inbound synchronous and specify these message as sender and receiver.

please do the necessary mapping.

regards,

navneet

[Former Member]

Hi,

1) towards the reciver adapter check if there is any proxy server ip address you need to mention.

2) The URL extracted from SAP XI should be in the form of

http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?

channel=<party>:<service>:<channel>

Hope this is useful info

[former_member183906]

check the below link for

Handling Web Service SOAP Fault Responses in SAP NetWeaver XI

check it

The fault message structure are useful only when you want to pass them to the sender system via XI. IF you want to push them to a Z table in ECC itself, you need not have to define them. In the proxy code, use Try Catch blocks to catch the exceptions and write them to Z tables.

regards

[Former Member]

check:

1) URL and SOAP action in WSDL file.

2) Test the WSDL file using XML spy

3) Check the configuration of SOAP adapters.

chirag