Services registry in BASIS 700

[Former Member]

Hi all,

could any body guide me on publishing webservices to SERVICE REGISTRY from ABAP workbench or SOAMANAGER.

First of all how do I know If SR is up in my system . When I try url http://hostname:port/sr it is returning 'page not found'.what should i do to configure sr in the system.

please advice.

regards,

sap fan.

[Former Member]

works from all machines when the web service is published

[Former Member]

Hi Gourav,Trevor,

thanks for the replies.

Actually I saw there is a UDDI client in the system and some registries listed in SOAMANAGER. But when i try to publish webservice, it asks for user name and pwd, not sure where to create this user id.

I requirement is to access the webservice from .NET application.Surprisingly, I can access the WSDL from .net application in my machine. But from visual studio in another machine in the same network, it is throwing Discovery error.

thanks.

[Former Member]

Hi,

Point one: you don't need service registry to use webservice in any application, it is just yellopages or directory of service for easy search.

Point two: if you don't have CE 7.1 or PI 7.1 then chances are there is no service registry in your landscape (non sap can exisit).

Point three: Try to replace wsdl url with ip address then hostname or use fully qualified hostname, to access it from another machine with .Net

Regards,

Gourav

[Former Member]

Hi Sap Fan,

Don't confuse SOAMANAGER & Service Registry. They are 2 different things...SOAMANAGER is used for endpoint config & security setup. Service Registry is for broadcasting your webservice to the world.

In your case you just need SOAMANAGER, refer to guide below for a good overall understanding of how things work. Also refer to page 81 for your requirement:

[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60cb2b4c-af72-2b10-a3a2-a2f718d2a565?quicklink=index&overridelayout=true]

Regards, Trevor

[Former Member]

hi all,

yeah i did the mapping of ipaddress also. but i still get the error when I add the wsdl generated in SOA MANAGER to ADD web reference in .net

the link u specified was not much of use

the wsdl is :

http://host::8002/sap/bc/srt/wsdl/bndg_DEEFA40807E3B8F1948E00215E56BC34/wsdl11/allinone/standard/doc...

from another m/c I can see the method name, but it throws DISCOVERY error.I guess the problem is due to the element:

'urn:sap-com:document:sap:soap:functions:mc-style' in xml.

when I try from a m/c with SAP gui installed, i dont have any problem.

pl help.

[Former Member]

here is the error from .net

The document at the url

http://XXXX:8002/sap/bc/srt/wsdl/bndg_DEEFA40807E3B8F1948E00215E56BC34/wsdl11/allinone/standard/docu... was not recognized as a known document type.

The error message from each known type may help you fix the problem:

- Report from 'WSDL Document' is 'There is an error in XML document (1, 500).'.

- 'Element' is an invalid node type. Line 1, position 500.

- Report from 'DISCO Document' is 'Discovery document at the URL http://XXXX::8002/sap/bc/srt/wsdl/bndg_DEEFA40807E3B8F1948E00215E56BC34/wsdl11/allinone/standard/doc... could not be found.'.

- The document format is not recognized.

- Report from 'XML Schema' is 'Expected Schema root. Make sure that the root element is <schema> and the namespace is 'http://www.w3.org/2001/XMLSchema' for an XSD schema or 'urn:schemas-microsoft-com:xml-data' for an XDR schema. An error occurred at , (1, 40).'.

[Former Member]

Hi Sap Fan,

It may be a .NET issue according to the thread below:

[http://bytes.com/topic/asp-net/answers/532488-disco-not-compiling]

But just out of curiousity, did you create an enpoint protocol binding for the service in SOAMANAGER? Where did you extract the WSDL from (on SAP) to use in VB.NET.

After creating the enpoint binding you need to use the WSDL with binding.

Regards, Trevor

[Former Member]

Hi triver,

I have gone thru those posts as well. But if it is .NET issue then i should have ti=his problem in all machines. strangely, i dont have this problem with .net in my m/c.(the other one also has same version of .net)

i got the url from SOAMANGER,.it is same as the url i test from WS navigator and the test works fine.

I see so mamny posts regarding accessing sap webservices from .net, but none of them is working out

dont know where the missing link is.. i tested the wsdl with xml spy, and it says wsdl is valid.

[Former Member]

Hi Sap Fan,

The thing is that it's not an SAP webservice issue...Logically speaking, if the SAP webservice work fine from one machine & not another one in the same network then the issue is that machine experiencing the problem.

Hence I suggested the thread above where the user had to uninstall & re-install the .NET SDK & then things started working, see portion of thread:

"Thanks, Juan, for the suggestion. It worked now.

& thanks for the suggestion to re-install .NET2.0 SDK in my other post

as well. After uninstalling & re-installing the SDK, disco.exe showed

up in C:\Program Files\Microsoft.NET\SDK\v2.0\Bin directory. But the

strange thing is before uninstalling the SDK, the Bin directory had

only 23 files & no folders but after re-installing the SDK, now the Bin

directory houses 66 objects (2 of which are hidden) - 2 directories &

64 files!"

Regards, Trevor

[Former Member]

Hi all,

thanks for ur replies. But the sap PI or CE is not installed in my system. Only SAP BI component is installed. Is it possible to configure service registry or UDDI registry for this system. I have access to SOAMANAGER also but with limited features. I can see UDDI client also.But just the links , I dont see any registries in it.

Regards,

sap fan

[Former Member]

Hi Sap Fan,

SAP Service Registry only comes with PI 7.1 or CE 7.1. Depending on your version of BI you could possibly publish your BI web services to an Exeternal UDDI Server if it's available to you, see example:

[http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1162] [original link is broken] [original link is broken] [original link is broken];

I also came across a UDDI Server buil-in to the J2EE Engine, you might want to check that out:

[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7ffba2ec-0c01-0010-2e81-988e48e3ca43?quicklink=index&overridelayout=true]

I can't comment too much on this cos I haven't used it.

Regards, Trevor

[Former Member]

Hi,

SAP Service Registry only come with CE and PI 7.1, although it is not mandatory to use service registry in a landscape but it is suggested.

If you still want to use service registry then download any open source service registry available on internet and deploy in your landscape.

Regards,

gourav

[Former Member]

Hi Sap Fan,

It looks like your installation & post processing steps wasn't completed as per the guide. You could use the Troubleshooting Guide - SAP NetWeaver PI 7.1 to rectify this now...In Service MarketPlace:

[https://websmp105.sap-ag.de/operationsnwpi71]

Regards, Trevor

[Former Member]

Hi,

Service Registry is available with PI7.1 or CE7.1 system, so if you have PI 7.1 system, then type http://pihost:port/sr

Regards,

Gourav