cancel
Showing results for 
Search instead for 
Did you mean: 

Soap Adapter

Former Member
0 Kudos

Configured sender soap comm. channel.I am trying to test Sender Soap adapter. What are the steps that I need to follow to test if i can receive this message?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

To test you SOAP sender scenario, goto runtime workbench-> component monitoring-> adapter monitoring.

There you can your test message by providing party, Sevice, communication channel, URL to the message servelet and the payload.

One more option is use a SOAP request builder tool. Seach the internet and get an available tool for SOAP request builder. Then privide the WSDL file and the authorization details( uname and password). The tool creates a SOAP request for you. Enable the SOAP sender channel by activating it.

Cheers,

Ajay

Former Member
0 Kudos

One other question, my Sender soap adapter is inactive in Adapter monitoring, even though I have activated the Sender adapter. When does the Sender Comm. channel show up as active(green) in Adapter monitoring.

former_member187339
Active Contributor
0 Kudos

Hi,

>>my Sender soap adapter is inactive in Adapter monitoring

It will be active only when atleast one message is passed thru it.

Regards

Suraj

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi,

For the authorization error you have to change the proxy settings in the SOAP client taken from SDN.

This can be done using the "setting" menu in the SOAP client. Set according to the proxy used in your Internet Explorer.

may be this will solve your problem.

regards,

P.Venkat

Former Member
0 Kudos

Hi,

Your message not reaching XI becasue the SOAP request send must be having the encoding type UTF (Unicode Transformation Formats) as UTF-16. Change it to UTF - 8.

The best way to test the XML is to open that in internet explorer. If that is working fine your reuqest will hit XI.

Regards,

Ajay.

Former Member
0 Kudos

Hi,

Follow the steps for testing the SOAP Adapter from XI.

Step 1 :- Component Monitoring--> Click Adapter Engine.

Step 2 :- Select the "Test Message" Tab

Step 3 :- Give the send to,interface name, service, namespace

Step 4 :- Payload should be Soap Request. and click send message.

Check the result in SXMB_MONI.

Note : You can create SOAP Request from WSDL using the following tool.

http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=65a1d4ea-0f7a-41bd-8494-e916e...

Former Member
0 Kudos

I tried testing it from RWB. But in SXMB_MONI, my input payload makes no sense,

This is my soap request generated from WSDL.

<?xml version="1.0" encoding="utf-8"?>

<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:Body>

<MT_OUT xmlns="http://xxx.com/test">

<Name xmlns="">test</Name>

</MT_OUT>

</soap:Body>

</soap:Envelope>

While my payload in SXMB_MONI is as follows and does not have any input.. and fails during mapping.

- <sap:Manifest xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink">

- <sap:Payload xlink:type="simple" xlink:href="cid:payload-7c802e91a48211da80ac00110a54ae35@sap.com">

<sap:Name>PayloadName</sap:Name>

<sap:Description>PayloadDescription</sap:Description>

<sap:Type>Application</sap:Type>

</sap:Payload>

</sap:Manifest>

Former Member
0 Kudos

Hi Kris

sorry, it's two years later. I do have the same issue as you, how did you solve your problem?

Thanks

Jayson

Former Member
0 Kudos

1. Generate a wsdl file from Integration Directory (Tools ->Define Web Service) for the sender soap adapter that you configured.

2. You can use any soap test tool to send the soap request message (e.g., soapscope can be downloaded for eval) by importing the wsdl file.

3. After you send the soap message, go to SXMB_MONI to monitor if there is any message that came into the pipeline (in the last 1 minute).

4. If there is no message came in to the pipeline, there are several things you can do:

a). Check the response message from your soap test tool -- this usually tells you enough info what went wrong.

b). Go to Runtime Workbench to monitor the soap adapter status.

Hope that helps (pls reward points if this is useful to you).

Former Member
0 Kudos

Could you please elaborate on the second step? I am using the SOAP client (from SDN), what should I do with the generated WSDL

Former Member
0 Kudos

Sorry what is the SOAP client from SDN -- can you give me a link to it? I have used SOAPscope to import the WSDL file and it can generate SOAP request instance for you. All you need to do is to fill in the input field values in a browser interface.

You can also build your own test harness in NWDS by building a proxy for the web service (deployable or standalone). This is 100% configuration driven by importing the WSDL from XI. The only thing you have to do is to create a servlet to call the proxy (I can send you an example if you are interested).

Another (free) tool that I found useful in SOAP testing is Apache AXIS's tcpmon that can be used to monitor SOAP/HTTP messages on the wire. All you need is the axis.jar file (you can google-search it).

Former Member
0 Kudos

I am using the SAP Soap Client from SDN. When I imported the WSDL file and sent the request, I am getting 401 authorization file.

when I look at the trace file, I am getting "Cannot authenticate the User error"