SOAP client test tool - Configuration checklist

[Former Member]

Hi,

We are using the SAP supplied SOAP client test tool but are finding that the process hangs when processing a request.

The target URL we are using is as follows:

http://sxd.csc.southwark.gov.uk:50200/XISOAPAdapter/MessageServlet?channel=:iWorld:SOAP_Sender

This URL works fine in a standard browser however does not work in the test tool - it just hangs !

Does anyone have a checklist to use in the configuration of the test tool ? Or provide a alternative to using this tool ?

Thanks in advance.

Colin.

[former_member185751 · Accepted solution]

Hi Colin,

Try using SOAPScope 4.1 from Mindreef (www.mindreef.com) as an alternative to SAP's SOAP client test tool.

They give a 4-day trial license.

Or you can try using XMLSPY or Stylus Studio.

Regards,

Sridhar

[Former Member]

Hi Colin,

Just a question, where can the SAP supplied SOAP client test tool be found ?

Thanks in advance.

Peter

[Former Member]

It can be downloaded from SDN itself.

(Just search using search term 'soap client')

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/sap soap client tool download.abst

[Former Member]

> It can be downloaded from SDN itself.

> (Just search using search term 'soap client')

>

> https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot

> /com.sap.km.cm.docs/documents/a1-8-4/SAP%20SOAP%20Clie

> nt%20Tool%20Download.abst

I would like to use this tool but I get a Web Start Error.

JNLPException[category: Download-Fehler : Exception: java.net.ConnectException: Connection timed out: connect : LaunchDesc: null ]

at com.sun.javaws.cache.DownloadProtocol.doDownload(Unknown Source)

at com.sun.javaws.cache.DownloadProtocol.isLaunchFileUpdateAvailable(Unknown Source)

at com.sun.javaws.LaunchDownload.getUpdatedLaunchDesc(Unknown Source)

at com.sun.javaws.Launcher.downloadResources(Unknown Source)

at com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source)

at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)

at com.sun.javaws.Launcher.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

I assume the reason is the security policy of my company. Is there any other way to get this tool?

Is there any other oportunity for a simple test of my SOAP Adapters?

Thanks.

[Former Member]

I have fixed the problem. Proxy Setting ind Java Web Start.

[Former Member]

Hi,

What is the proxy settings to be done in Java Web start ?

Iam stuck with the same problem.

regards,

Nagarajan.J

[Former Member]

Hi Colin,

You are already a step further then me, if I call my target url in a browser, I get a popup for username and password. Do you know where to make the setting for anonymous logon for the soapadapter?

Cheers,

Frank

[Former Member]

Hi Frank,

Since you are in the browser, it will ask for a username and password. Just enter your XI username and password.

Regards

Manish

[Former Member]

Hi Manish,

If a server is calling my WS, I don't want a popup. So I'm looking for:

- anonymous logon or

- send the Username / password in the URL

In both cases I don't know how to do it.

Cheers,

Frank

[Former Member]

Hi Frank,

XI uses HTTP Basic authentication, e.g. a believe a base64 encrypted string. You would add this to your program, must WS toolkits let you call a method to provide the user id and password and create the required string.

I used HTTP Sniffer on the SOAP Client from SAP, they have an option in the menu to use HTTP basic authentication and you put your user id and password in. The SAP SOAP Client works but is not as comfortable as XMLSPY.

Cheers

Stefan

[Former Member]

Hi Stefan,

The people who are calling a WS on SAP XI are using AXIS and they don't know to provide the user id and password. I tried looking for a way to switch off basic authentication for the SOAP adapter, but I can't find it. Any idea's?

Cheers,

Frank

[Former Member]

Hi Frank,

for AXIS they have to do following:

Run AXIS's wsdl2java tool to generate the service proxy (you need to connect to the service using this proxy). This is available in one of the jars that comes along with AXIS.

Use the generated structure of java interfaces and classes inside your client. Heres wht my client looks like after using the autogenerated AXIS code:

public void doPost(HttpServletRequest request, HttpServletResponse res)

throws IOException, ServletException

{

res.setContentType("text/xml");

PrintWriter out = res.getWriter();

String endpoint = "http://msssapxinw:50000/XISOAPAdapter/MessageServlet?channel=:SOAPClient:JJSSoap";

String supname = request.getParameter("sup-name");

String supnumber = request.getParameter("sup-number");

Supplier_SOAP supplier_soap = new Supplier_SOAP();

supplier_soap.setSupplierName(supname);

supplier_soap.setSupplierNumber(supnumber);

try{

SoapSenderService soapsenderservice = new SoapSenderServiceLocator();

SoapSender soapsender = soapsenderservice.getSoapSenderPort(new java.net.URL(endpoint));

soapsender.soapSender(supplier_soap);

} catch(Exception serex){ serex.printStackTrace();}

}

The only catch here is that you need to modify the autogenerated code with your XI username and password.

This is in the <servicename>BingStub.java file.

Just overwrite the username and password for the call object using AXIS APIs:

_call.setUsername("username");

_call.setPassword("*******");

This is what somebody else did and it works for AXIS. I tried to turn off the password setting too but I did not find the right service in the Visual Admin and then on the other hand it would be great from SAP to let you include the user name and password in the communication channel since the basic auth. is not good.

Stefan

[Former Member]

Hi Stefan,

Thanks, I am going to try if it works.

Cheers,

Frank