Skip to Content
0
Former Member
Feb 16, 2009 at 10:52 PM

WSADMIN Obsolete....now what?

499 Views

Webservices worked fine in SAP:

SE37 -> Create Service -> WSADMIN - > WSDL.

Now SAP invented this thing called SOAMANAGER. Maybe it's an architectural wonder. Maybe it makes sense. Maybe it follows every standard in the book. Too bad I just want things to actually work.

After SP14, I can't get Visual Studio 2008 to read the new WSDLs ("legacy" WSADMIN WSDLs are read just fine). Now I have a service wizard that tells me I need to run WSADMIN2. Too bad I don't have a J2EE and I don't want a J2EE server. I hate SAP Java, I think it's a piece of utter rubbish and waste of disk space.

How can I actually use webservices in SAP post SP14 in pure ABAP world? I repeat, I didn't need a J2EE server before, and I makes little sense to need one after a simple SP (not version on enhancement package upgrade). A SP should fix bugs and leave basic functionality alone. This policy of SPs containing tons of changes is ridiculous and goes against the very concept of SP.