Testing the Web service

[Former Member]

Hi Experts,

I have exposed the RFC as webservice, but could'nt able to test it, as we don't have a Java stack installed.

please can you suggest on how to generate WSDL and test the webservice.

Thanks in advance,

MK

[amit_khare]

Are you looking for [This|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1135] [original link is broken] [original link is broken] [original link is broken];?

[GrahamRobbo]

Hi Mickey,

You can write a simple test harness in ABAP. Lots of blogs on how to do this. Just search for "consuming web services from abap".

There are also lots of tools around for testing web services.

I user XMLSpy from Altova and find it very good. You can download a 30-day trial from their website.

Cheers

Graham Robbo

[Former Member]

Thanks Amit and Graham.

but as we require WSDL to test webservices in tools like XML spy, please suggest on how to produce it from ABAP.

[GrahamRobbo]

Hi Mickey,

the SOAMANAGER transaction provides the URL for the WSDL of a published web service. You can also find it in the web service definition using SE80 I think.

Cheers

Graham Robbo

[Former Member]

Thanks Graham,

we are using ECC 6.0, and it says Transaction SOAMANAGER does not exist

and also looked at webservice definition in SE80, could'nt able to find the URL.

[GrahamRobbo]

Hi Mickey,

the pre-cursor transactions to SOAMANAGER were WSADMIN and WSCONFIG. Try them. Certainly SOAMANAGER exists on all the ECC6 systems I have access to. I think it appeared around SP12.

In my systems, ECC6.0 SP14, if you navigate to the web service definition using SE80, double-click on it, and select the WSDL tab you will find the WSDL itself and the URL to access it from external tools.

Cheers

Graham Robbo

[Former Member]

Thanks Graham,

But on our system I can only see three tabs Properties, Interface and Variants after double clicking the WSD in se80.

We have recently got upgraded to ECC 6.0, can you please suggest on how to check the service pack we are on.

[GrahamRobbo]

Hi mickey,

System->Status will tell you that - but clearly you are not on the later service packs or the SOAMANAGER transaction would be available.

As mentioned previously look for transactions WSADMIN and WSCONFIG.

Cheers

Graham Robbo

[Former Member]

Hi Graham,

At system--> status I can see the below

Software component   Release     level
SAP_ABA	                 700	  0013	Cross-Application Component

Is that means we are on SP13 ?

Thanks,

MK

[GrahamRobbo]

Hi Mickey,

yep that's SP13. Have you tried the transaction codes I already mentioned?

Cheers

Graham Robbo

[mvoros]

Hi,

yes, you are on level 13 and you missed just by one SP. SOAMANAGER was introduced in SP14. You will have to use WSADMIN and WSCONFIG as Graham already mentioned.

The following blog may be useful for you.

/people/thomas.jung3/blog/2005/05/09/abap-webservices-logon-language-processing

[Former Member]

Thanks Graham and Martin,

The transactions WSADMIN and WSCONFIG does not display the complete Url, and as the J2EE instance is not installed what values can we pass for J2ee server host and port.

<http(s)>://<JavaServerHost>:<JavaServerPort>

[GrahamRobbo]

Hi Mickey,

You do not need a J2EE instance - and I seem to recall from earlier posts you don't have one anyway.

Suggest you read up on the documentation and check with your system admin people of things still don't work.

Cheers

Graham Robbo

[Former Member]

Hi,

To generate WSDL follow this link.

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30f1b585-0a01-0010-3d96-ad0ea291...

and to test the webservice

http://www.sap-press.de/katalog/buecher/htmlleseproben/gp/htmlprobID-59

Hope this will help you.

Regards:

Alok

[Former Member]

Thanks for the replies.

But the issue is to produce the WSDL without the J2EE instance.

please suggest to resolve the issue.