Is it mandatory to Publish a service in Service Registry to consume it?

Hi Experts,
We have developed a Service interface with two service operations in the ESR.
In the backend ERP system, we have generated the proxy for the interfaces and implemented it.
Using SOAMANGER, we have generated the WSDL.
But when we try to Open WSDL document for selected binding, We get an error Forbidden 403.
What I thought is that we would be promted to enter the user id and pwd of the backend system.
so, i have the following questions.
1) Is it mandatory to Publish a service in the SR to generate the WSDL and consume it?
2) Do we need to some additional steps?
I have used the steps described here:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60cb2b4c-af72-2b10-a3a2-a2f718d2a565
Regards,
Ravi Kanth Talagana

Let me rephrase my question.
1) We have developed the service interface in the ESR.
2) In the backend system, we have generated the PROXY for the interfaces in SPROXY transaction.
3) Implemented the abap code in the class-methods.
4) Launched SOAMANAGER transaction.
5) Created the service and the binding.
(As described here: https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60cb2b4c-af72-2b10-a3a2-a2f718d2a565)
6) when I click on the Open WSDL document for selected binding link, I get the following error.
Service cannot be reached
What has happened?
URL http://njsapnet1.us.intelligroup.com:8000/sap/bc/srt/wsdl/bndg_DDB660678B8DB6F1934200142220669B/wsdl11/allinone/ws_policy/document call was terminated because the corresponding service is not available.
Note
The termination occurred in system E6I with error code 403 and for the reason Forbidden.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:NJSAPNET1_E6I_00-v:0-s:403-r:Forbidden
HTTP 403 - Forbidden
Your SAP Internet Communication Framework Team
Can some one help??
Thanks,
Ravi

Similar Messages

UDDI Exception : publishing the service registry

Hi,
have anybody faced the error below :
com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail message: com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.UDDIServerRemoteException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='REMOTE_EXCEPTION_UDDI_SERVER', Arguments: ['http://dvjcen00:*****/uddi/api/inquiry/', 'http://dvjcen00:*****/uddi/api/publish/']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en->com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.UDDIServerRemoteException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='REMOTE_EXCEPTION_UDDI_SERVER', Arguments: ['http://dvjcen00:*****/uddi/api/inquiry/', 'http://dvjcen00:******/uddi/api/publish/']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en->com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server <http://dvjcen00:******/uddi/api/publish/> returned message <Unauthorized
Can anybody suggest on that . At the time of Publish the service registry it comes.
Rgds,
Deep

Hello Deep,
Have you tried to assign the SERVICES_REGISTRY_READ_WRITE role to the user that is trying to publish?
Thanks & Regards
SU

Endpoints not published in Service Registry

Hi all,
I have published all the Enterprise services from the Discovery system(ECC) and they are available within the service registry.
But somehow the endpoints are not published to the Service Registry because of which I am not able to consume the services for UI development in VC.
I have the following concerns :
1) The ES are being tested successfully but not being sure why the endpoints were not published when the Services were published from the Discovery System.
2) Can we forcefully create the endpoints in the Service Registry. If so, plz let me know the procedure.
3) SP13 is applied on Discovery System, so I am not able to execute TCode SOAMANAGER to create Endpoints, so is there any other alternative, other than upgrading ECC to SP14.
Points will be rewarded for any help
Regards Brian

Hi Brian,
Maybe the issue is wrt the Service Registry destination definition. The correct system name should be picked from the SLD system name (under http://host:port/sld) definition (I think it CE1 by default). You can also refer other issues I faced in a similar situation that i documented in thread [Endpoints not published in Service Registry;
I take my earlier comment about using the Publish function in Service Registry. I learn it should be not be used.
As regards the ServicesRegistrySi(Proxy Definition) URL, I guess you can use http://localhost:port/ServicesRegistrySiService/ServicesRegistrySiPort?wsdl&mode=sap_wsdl
Regads
Suresh

Error while publishing thru Service registry

Hi friends
While publishing service thru service registry, I am getting this error message.
Any Solution?
Thanks
-Mitesh
com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail message: com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.ValidationException: Cannot load WSDL due to "Invalid Response Code: (401) Unauthorized. The requested URL was:"http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1"". Check that the specified WSDL URL "http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1" points to WS-I Basic Profile 1.1 compliant WSDL Definitions file->com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.ValidationException: Cannot load WSDL due to "Invalid Response Code: (401) Unauthorized. The requested URL was:"http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1"". Check that the specified WSDL URL "http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1" points to WS-I Basic Profile 1.1 compliant WSDL Definitions file->com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.ValidationMessage: Cannot load WSDL due to "Invalid Response Code: (401) Unauthorized. The requested URL was:"http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1"". Check that the specified WSDL URL "http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1" points to WS-I Basic Profile 1.1 compliant WSDL Definitions file

Hello Mitesh
Would this forum question be interesting for you?
[ESR post-installation tasks are missing|ESR post-installation tasks are missing]
regards
Rathish

RFC WSDL need to publish in Service Registry or not?

Hi,
I have created a webservice(WSDL) using SOAMANAGER for Remote Function Call(RFC) developed in R/3 System. This WSDL will be used in Enterprise Portal for our Web Application. Is it required to publish the Webservice in Service Registry? What is the importance of publishing webservice in Registry? If it is required, who will be responsible for publishing it(ABAP Technical person or Basis or Enterprise Portal person)?
Thanks and Regards,
Vimala P

Hi Nidhi,
>My Scenario is I need to publish one RFC as a webservice in PI 7.1 and provide an endpoint URL to user to use.
As per my understanding, you are trying to expose an RFC as webservice. If yes, have a look at this [link|http://help.sap.com/saphelp_nw04/Helpdata/EN/e9/ae1b9a5d2cef4ea4b579f19d902871/frameset.htm] to ensure you have done it properly.
> I have done the configuration but when I try this option Tools-> display WSDL it gives me following error-- ``Object Service Interface Z_QMNC_SAVE_CORRECTIONS | urn:sap-com:document:sap:rfc:functions not found in Enterprise Services Repository``
I am not clear with configuration you have done. Can you describe a bit more?
Regards,
Sunil Chandra

BizTalk Published Web Service unable to consume, Token-Based Server access validation error

Hi, We have developed a BizTalk application and we have published as web service, but when we are trying to consume the application we are getting the an error and its logged
in event log.
While deploying we have allowed Anonymous user access for the web services as well.
Following are the errror details -
"Login failed for user 'IIS APPPOOL\ASP.NET v4.0 Classic'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]"
I tried to change it other App pool as well. It seems an issue with permissions related to BizTalk user's/Group,
Please suggest which app pool should we select or should we give permissions to App Pools.

The User of App Pool should be part of "BizTalk Isolated Host Users Group".
In your case user is "IIS APPPOOL\ASP.NET v4.0 Classic", so either you add this user to BizTalk Isolated Host Users
Group or create a new App Pool with new user. I would suggest to go for new user specific to BizTalk.
This permission is required because IIS(App Pool(w3wp.exe)) will be publishing new messages to BizTalk Databases. So they should have required permissions to do that and in BizTalk we have a default group for the same, as suggested by Shankycheil.
BizTalk Isolated Host Users
The default name of the first Isolated BizTalk Host Group created by Configuration Manager. Isolated BizTalk hosts not running on BizTalk Server, such as HTTP and SOAP.
Use one BizTalk Isolated Host Group for each Isolated Host in your environment.
Contains service accounts for the BizTalk Isolated host instance in the host that the Isolated BizTalk Host Group is designated for.
BTS_HOST_USERS SQL Server Database Role in the following databases:
BizTalkMgmtDb
BizTalkMsgBoxDb
BizTalkRuleEngineDb
BizTalkDTADb
BAMPrimaryImport
Thanks,
Prashant
Please mark this post accordingly if it answers your query or is helpful.

Error in publishing endpoint in service registry

Hey,
I am gettin the following error while publishing the service registry.
10160A save request exceeded the quantitylimits for a given structure type. #Number of Business Entities exceeds your limit 1(2).
This is with respect to the endpoint. The endpoint is also not published when I checked it in the service registry of PI.
regards,
Milan.

Hi Milan,
Open your UDDI client->Select Publish->Select Retrieve My Business
check if you are able to add more than one Business entity.
You find out all the Business entities present in the UDDI, Take their keys (UDDI Keys)
then go to Publish->Select Retrieve My Business
create business entity with the key you have obtained before and then delete that, It will delete the the business entity and then try to publish the your service with end point.
Thanks,
Sunil Singh

Failed to test a SAP PI Published web service on SOAPUI

Hi All,
I have developed the RFC to Web service through SAP PI 7.1 . Web service published on 'Services Registry' and test on it. It accepts the my request and respond from SAP R3. All the message was successfully recorded on SXMB_MONI.
In Integration Directory, i could view the web service URL . I navigated to the Sender Agreement -> Display WSDL and i could see the "WSDL URL' and wsdl content on large text box.
I access the WSDL URL from SOAPUI tool and set the preference -> proxy setting also. it populated the request message successfully but respond gives the '400 Bad HTTP request' and Detail: -> illegal path specified . No SOAPUI request recorded on SXMB_moni.
i try the same following way also . i saved the WSDL on xml file and access it through the SOAPUI -> import project. that also failed on SOAPUI.
Can you please help to solve the issue ?
Thanks,
Rehan

Hi Rehan
Please check the below blog, it might help
Publish services from PI 7.1 to the Service Registry
Consuming SAP PI published Web Service
regards,
Harish

Service Registry SDLC import export of services

hi ,
I am intrested to know how is the SDLC process work in service registry?? I have a service in my test environment and is published to service registry test environment. Now I wanted to promote the service to production enviornment and publish it to production service registry env. How can I achieve this.
appreciate your help.
thanks
Srini

Hello Gourav,
Thank you for this information; it is very helpful.
However - the export appears to only include the entries in the namespace http://uddi.sap.com/classification. Since that is a protected namespace I am not able to create my custom classification values there. (I'm also going to assume that this namespace gets overwritten during system upgrades, so I would not want my custom values in it anyway.) Subsequently my custom values are in a separate namespace that does not seem to be included in the export process.
Is there a way to configure this export utility so that it retrieves the data from my namespace, rather than (or in addition to) the standard SAP namespace?
Thanks again,
-- Chris

Service Registry configuration

Hi,
I am getting below error while publishing in service registry ""could not establish connection to service registry, configure connection to service registry in SAP netweaver and try again
Thanks

Note 1267817 - Configure Services Registry proxy (ServicesRegistrySi) for this configuration
Thanks

Regarding the Service Registry in SAP PI 7.1 and non SAP System ....!

Hi All ,
I need to know answers for the below Question ...hope to get some answers frm Experts ....
1) How to publish service from non-SAP systems?
2) How to use discovered service in the Service Registry for consumer/provider scenario? With some examples.
Thanks in Advace ...!
Regards ,
Aziz khan .
Edited by: Aziz khan on Sep 16, 2009 11:43 AM

Hi,
1) How to publish service from non-SAP systems?
Publish Service is nothing but making WSDL of that service available. For that you need to Publish the WSDL of the web Service to UDDI. For Non SAP system, Lik .net , Java they have there oun APIs to do so. U can search on net to get it.
For Ex. below link.
http://www.startvbdotnet.com/web/publish.aspx
2) How to use discovered service in the Service Registry for consumer/provider scenario? With some examples.
Once you discover the services, you get the WSDL of that Service. Then You can import this WSDL in IR and you it.
See the below links.
http://help.sap.com/saphelp_nw04/helpdata/en/43/ce993b45cb0a85e10000000a1553f6/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/EN/26/9e97b0f525d743882936c2d6f375c7/frameset.htm
Shweta

Importance of TREX server and services for Services registry

Hello All
Is a TREX Server and TREX services mandatory to be able to connect to the services registry??
Because I have no trex server and when i browse the services registry , no results are yielded..
Need information on the TREX and relation with the registry.
Thanks
Vijay

TREX is not mandatory to connect to Service Registry. But to Search a service in the registry, TREX is used in the backend.
Regards,
Prateek

OWSM Integration with Service Registry- Failing

Hi All,
I am trying to import a service published on service registry in OWSM and then trying to test the gateway from OWSM->Tool->TestPage. But I am getting the following error after running the test which is as follows:-
ORABPEL-08021 Cannot find partner wsdl. parnterLink "ManageInventoryService" is not found in process "ManageInventoryService" (revision "1.0") Please check the deployment descriptor of the process to find the correct partnerLink name.
I am also pasting the original service wsdl code below:-
<definitions
name="ManageInventoryService"
targetNamespace="http://www.cognizant.com/ManageInventoryService"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:ns1="http://schemas.oracle.com/bpel/extension"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:client="http://www.cognizant.com/ManageInventoryService"
>
<import namespace="http://schemas.oracle.com/bpel/extension" location="RuntimeFault.wsdl"/>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://www.cognizant.com/ManageInventoryService" schemaLocation="ManageInventoryService.xsd"/>
</schema>
</types>
<message name="ManageInventoryServiceRequestMessage">
<part name="payload" element="client:ManageInventoryServiceProcessRequest"/>
</message>
<message name="ManageInventoryServiceResponseMessage">
<part name="payload" element="client:ManageInventoryServiceProcessResponse"/>
</message>
<portType name="ManageInventoryService">
<operation name="initiate">
<input message="client:ManageInventoryServiceRequestMessage"/>
</operation>
</portType>
<portType name="ManageInventoryServiceCallback">
<operation name="onResult">
<input message="client:ManageInventoryServiceResponseMessage"/>
</operation>
</portType>
<plnk:partnerLinkType name="ManageInventoryService">
<plnk:role name="ManageInventoryServiceProvider">
<plnk:portType name="client:ManageInventoryService"/>
</plnk:role>
<plnk:role name="ManageInventoryServiceRequester">
<plnk:portType name="client:ManageInventoryServiceCallback"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
However when I am trying a dynamic look-up from BPEL on the above service published on service registry it's working fine and returning the expected response.
Please let me know where am I going wrong?It's little urgent and any help will be appreciated.
Thanks.

Thanks Chintan, I think the problem is the needed patch 6133448. I have MLR#9 deployed but I think it does not include 6133448 and I can't install 6133448 as it conflict with MLR#9.
I will check with Oracle.
Thanks
Kish

Publish of a Service over Service Registry - com.sap.esi.uddi.sr.api.exce

Hello
I try to publish a Service over the Service Registry UI but this results in a com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail message: java.lang.NullPointerException->java.lang.NullPointerException
Is the problem the schema import or the two address locations ?
We use ESR CE 7.1 SP3
Kind regards
Gerald Eder
The WSDL looks like :
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://test.com/soa/" xmlns:i0="http://test.com/soa" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://test.com/soa/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:import namespace="http://test.com/soa" location="http://pwwdev.test.com/Appl/Corp/Services/SOA/SOAServer/customerid.asmx?wsdl=wsdl1" />
- <wsdl:types>
- <s:schema targetNamespace="http://test.com/soa/">
<s:import schemaLocation="http://pwwdev.test.com/Appl/Corp/Services/SOA/SOAServer/customerid.asmx?schema=schema1" namespace="http://test.com/soa" />
</s:schema>
</wsdl:types>
- <wsdl:service name="CustomerID">
- <wsdl:port name="CustomerIDBinding" binding="i0:CustomerIDBinding">
<soap:address location="http://pwwdev.test.com/Appl/Corp/Services/SOA/SOAServer/customerid.asmx" />
</wsdl:port>
- <wsdl:port name="CustomerIDBinding1" binding="i0:CustomerIDBinding1">
<soap12:address location="http://pwwdev.test.com/Appl/Corp/Services/SOA/SOAServer/customerid.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:de

Hi Rajesh,
Many thanks for your prompt reply, however this note 1267817 was already applied before posting message.
B/W I have observed that in spite of the error the service published multiple times in the registry (perhaps each try to publish resulted a entry in SR).
Really crazy error, any other suggestion??
Regards, Immy.

Error publishing service in Service Registry

Hi experts.
I've configured Service Registry in a SAP PI 7.11. Everything seems to work correctly but I can't publish services there. When I try to publish from Directory or directly in Service Registry by wsdl I'm getting this error:
com.sap.aii.ib.core.uddi.RegistryClientException: Services registry is not available; for more information, see the log
     at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:440)
     at com.sap.aii.ibdir.server.wsquery.WSQUDDIPSPublishTB.execute(WSQUDDIPSPublishTB.java:91)
     at com.sap.aii.ibdir.core.simulation.DefaultTaskBroker.execute(DefaultTaskBroker.java:171)
     at com.sap.aii.ibdir.server.simulation.TaskQueryService.specialQuery(TaskQueryService.java:33)
     at com.sap.aii.ib.server.query.SpecialQueryServiceProvider$SpecialQueryServiceImpl.specialQuery(SpecialQueryServiceProvider.java:63)
     at com.sap.aii.ib.server.query.QueryServiceImpl.specialQuery(QueryServiceImpl.java:443)
     at com.sap.aii.ib.server.query.QueryServiceBean.specialQuery(QueryServiceBean.java:112)
     at sun.reflect.GeneratedMethodAccessor762.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:592)
     at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
     at $Proxy1646.specialQuery(Unknown Source)
     at sun.reflect.GeneratedMethodAccessor761.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:592)
     at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:362)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:977)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
I think is a authorization problem but I have role to read and write in service registry. I can see this error in Service Registry Trace
Invalid Response code (401). Server [http://xxxxxx:50000/uddi/api/publish/] returned message [Unauthorized].
Any idea? Maybe the user you have to fill in Service Registry Configuration Wizard?
Regards
Edited by: Christian Abad Chico on Feb 20, 2012 1:00 PM

Hi,
It looks like you are missing some Services Registry preconfiguration. Please find a description how to configure the Services Registry under the SAP Help document below:
http://help.sap.com/saphelp_nwce711/helpdata/en/47/d391d7b8fc3c83e10000000a42189c/frameset.htm
There is also a wizard that you can use for this purpose:
http://help.sap.com/saphelp_nwce711/helpdata/en/f7/6182bd68434595ba5105a0a346efcc/frameset.htm
Hope this helps,
Greg

Is it mandatory to Publish a service in Service Registry to consume it?

Similar Messages

Maybe you are looking for