Service Registry configuration issue

[vijay_kumar133]

Hi ,

after fresh instalations of pi7.11 we are in process of service registry configuraitons here we got issue.

i am following the link as below.

http://help.sap.com/saphelp_nwpi711/helpdata/en/48/2be46efcc531cbe10000000a42189d/frameset.htm

after this i tried to publish a sender agreement to sr i am getting error as

Fatal Internal Error

Services registry is not available; for more information, see the log

while i try to configure using this link i need input on

http://help.sap.com/saphelp_nwpi711/helpdata/en/48/2be46efcc531cbe10000000a42189d/frameset.htm

in discover url host name what value i need to enter

and in own node id and in policy tab what we need to chanege the settings .

sugest me what all steps that else need to be done afte this is there any sequence to be done... in order to solve this issue..

regards

vijay g

Edited by: vijay Kumar on Jun 1, 2010 12:37 PM

Edited by: vijay Kumar on Jun 1, 2010 12:44 PM

[Former Member]

Well that URL should work if your configuration is correct. That Consumer proxy with the port is the gateway to Services Registry including Integration Builder. Or restart J2EE as the last resort if you feel SiPort has been configured correctly for your installation version. It always does magic. You can check from WS navigator if thar proxy is working..just like you would test a proxy you built yoursefl. Try Opearations that are queries.

[Former Member]

I had the same problem and found that the issue was related to the user setup. I created a comms user in the backend that was replicated to the java side. The java side was complaining I needed to reset the pasword, even though it is a comms user. See note 0001387197 - Server returned code (500) content type texthtml .

Good luck and hopefully this works for you although this message is quite old now

[Former Member]

Publish button appears only for inbound interfaces under the WSDL tab. Are you saying it is disabled even for inbound service interfaces?

And for Services Registry, while configuring ServicesRegistrySiPort and creating the UDDI_Destination and Classification_Services, you have to use basic http authentication. And the user you use there should have UDDI_Admin and SERVICES_REGISTRY_READ_WRITE roles assigned on J2EE. You can check this on Identity Management from /nwa if you have admin-level access. If you are already using a user with these roles for the above configuration check if the following links are working for you to ensure you config is correct. They should return the corresponding WSDLs.

http://<host>:<port>/uddi/wsdl/uddi_v3_service.wsdl

http://<host>:<port>/ClassificationService/CS?wsdl

http://<host>:<port>/ServicesRegistrySiService/ServicesRegistrySiPort?wsdl

Then check if you can access Services Registry from WS Navigator by selecting the radio button for Services Registry and click 'Go'.

If all these checks pass, you should be able to publish from Integration Builder by an user who has SERVICES_REGISTRY_READ_WRITE and UDDI_TierN roles.

[vijay_kumar133]

Hi

i have checked and i have configured service registry with user who has authorizations has explained.

there are no deviations in that configurations.

now while testing the wsdl links which u have given

first two are working fine and last one is throwing error as

http://host:port/ServicesRegistrySiService/ServicesRegistrySiPort?wsdl

as

Error: No Service is found using request url /ServicesRegistrySiService/ServicesRegistrySiPort.

this is only one which i am facing problem.

kindly suggest me what else configuraiton i am left with. so that i can publish from sender aggrement into service registry.

Reagrds

Vijay G

[Former Member]

Also, I see that you wanted to know the values for 'UDDI host for discovery url' and 'own node id'. You need not maintain these values. They are not mandatory. The host will be where j2ee engine resides no matter what. Because thats where your UDDI registry will also physically reside. The discovery url for SR will always be http://<host>:<port>/sr. That is why this value is blank by default. You can give any value there and save it but will not make any difference.

Coming to the 'Own Node Id', this is analogous to the instance of one set of SR entries. You can name the node id as anything and SR/UDDI Registry will run with it. But if you change it, it will reassign the entires associated with the previous id to the new node id. This can take a while especially if SR has significant content. The default node id (uddi:uddi.mycompany.com:betanode) is just a suggestion to have decipherable name. So just replace 'mycompany' with either 'host' name or 'host.companyurl' after installation and you need not change it again. Sometimes changing and saving can take forever and time out as well depending on the transport settings for UDDI and Classification destinations. It is better to restart J2EE engine instead if you ever change 'Own Node Id' and keep getting time-out error.

[vijay_kumar133]

Hi

Thanks a lot even i have raised the issue to sap but still no proper response.

Even i am looking for how to publish into Service registry if i found any solution i will post.

and i can notice that in ESR the service interface the publish button is disable in my case.

and if you find any solution kindly post.

Regards

Vijay

[Former Member]

Hi,

I am having the same issue. Trying to get help from SAP support. Even they seem to have no clue unfortunately. The symptoms are exactly as you are facing. And by the way, you do not need ServicesRegistrySi in Service Definition. Only in Consumer Proxies. To check if the inputs you gave are correct: try this URL in a browser

http://<host>:<port>/ServicesRegistrySiService/ServicesRegistrySiPort?wsdl

If you figure out how to publish directly from Integration Builder, please update us! Thank you.

[former_member4985]

Hi Vijay,

Please check note:

#1267817 - Configure Services Registry proxy (ServicesRegistrySi)

Also refer to:

/people/robin.schroeder/blog/2007/08/08/publish-your-services-to-es-registry

and

/people/community.user/blog/2008/10/23/new-features-of-service-registry-in-ehp1-ce

Regards,

Caio Cagnani

[vijay_kumar133]

Hi Caio Cagnani,

I am doing the service registry configuration in PI 7.1 EHP1.

I have followd the note and complete that configuration and then by following the blog i have created the destinations in

as per note i have created ServicesRegistrySi Service Definition at

SOAmanagement-Application and Scenario Communication-Single Service Administration: Service Definitions

SOAmanagent-technical configuration -Destination Template Management: Destination Templates

i have created 2 destinations UDDI_DESTINATION ,CLASSIFICATION_DESTINATION

i have done this 2 steps still i am getting error while publishing the service to registry as

Services registry is not available; for more information, see the log 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:435) at com.sap.aii.ibdir.server.wsquery.WSQUDDIPSPublishTB.execute(WSQUDDIPSPublishTB.java:91) at com.sap.aii.ibdir.core.simulation.DefaultTaskBroker.execute(DefaultTaskBroker.java:172) at com.sap.aii.ibdir.server.simulation.TaskQueryService.specialQuery(TaskQueryService.java:31) 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.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at

any more steps i need to do or need to check any connections kindly suggest.

Regards

Vijay g

[rajasekhar_reddy14]

Hi Vijay,

What about PI7.1 EHP1 is it newly installed system?? the error looks installtion not done propley,i think UDDI server missing,why dont you post the link in SAP NetWeaver Administrator forums,there you will get basis experts inputs.

Regards,

raj

[vijay_kumar133]

hi raja,

yup its newly installed system,

Can we check uddi server is installed or not if not how to install it or configure it

even i have posted the same in netweaver admin forum too but no response.

Regards

Vijay

[former_member4985]

Hi Mr. Kumar,

Check the following links taht may aid you with the issue:

http://help.sap.com/saphelp_nwpi71/helpdata/en/46/94dd02c7b915ebe1000000

0a114a6b/frameset.htm

and

http://help.sap.com/saphelp_nwpi71/helpdata/EN/44/cc8fd368c873dfe1000000

0a11466f/frameset.htm

Also check if the user has missing UDDI role. To use Services Registry the

user have to have UDDI permissions. Please assign to the PIUSER

UDDI_Admin role.

Additional information how to configure Services Registry can be found

here:

http://help.sap.com/saphelp_nwce711/helpdata/en/48/2be46efcc531cbe100000

00a42189d/frameset.htm

You can also check:

#1319742 - Services Registry Publication

With regards,

Caio Cagnani

[vijay_kumar133]

Hi Caio Cagnani,

Thanks a lot i have checked all the steps by following the note 1319742 - Services Registry Publication

all the steps are working fine

1.http://host:port/sr

2.http://<javahost>:<javaport> /ESRegistryWS/BasicAuthConfig?wsdl=service&style=document

3. http://<javahost>:<javaport>; /ServicesRegistryFlatSiService/ServicesRegistryFlatSiPort?wsdl

4.http://<uddihost>:<uddiport> /uddi/wsdl/uddi_v3_service.wsdl

I have created a user with roles as mentioned UDDI_Admin

SERVICES_REGISTRY_READ_WRITE

and even type of user as technical user.

all this checks are passed as per note.

Still i am getting the same issue.

i have one doubt in

http://host:port/nwa

SOA Management-Technical Configuration-Services Registry Management: UDDI Server Configuration

here in Discovery URL HOst name has to be filled with default value but in my case its blank

and in Own Node Id the value is uddi:uddi.mycompany.com:betanode

did i need to change this values manulay if so what the url and node i need to enter.

is this might me one of the cause for the issue.

Regards

Vijay

[vijay_kumar133]

Hi Caio Cagnani,

Thanks a lot i have checked all the steps by following the note 1319742 - Services Registry Publication

all the steps are working fine

1.http://host:port/sr

2.http://<javahost>:<javaport> /ESRegistryWS/BasicAuthConfig?wsdl=service&style=document

3. http://<javahost>:<javaport> /ServicesRegistryFlatSiService/ServicesRegistryFlatSiPort?wsdl

4.http://<uddihost>:<uddiport> /uddi/wsdl/uddi_v3_service.wsdl

I have created a user with roles as mentioned UDDI_Admin

SERVICES_REGISTRY_READ_WRITE

and even type of user as technical user.

all this checks are passed as per note.

Still i am getting the same issue.

i have one doubt in

http://host:port/nwa

SOA Management-Technical Configuration-Services Registry Management: UDDI Server Configuration

here in Discovery URL HOst name has to be filled with default value but in my case its blank

and in Own Node Id the value is uddi:uddi.mycompany.com:betanode

did i need to change this values manulay if so what the url and node i need to enter.

is this might me one of the cause for the issue.

and in

And in the nwa

SOA Management-Application and Scenario Communication-Single Service Administration: Service Definitions

Here I have searched for ServicesRegistrySi service definitions and created ServicesRegistrySiPort Service Endpoint in both tabs

Service definitions and consumer proxies also.

I have done this configuration in both the places

i hope i need to rectify in service definitons configuration here suggest me what need to be done

and when i checked the endponit of the consumer proxies of serviceregistysi service

http://host:50700/ServicesRegistrySiService/ServicesRegistrySiPort

i am getting as 404 Not Found

Error: Web Service Endpoint URI expected. Not found endpoint with URI /ServicesRegistrySiService.

Troubleshooting Guide https://sdn.sap.com/irj/sdn/wiki?path=/display/jsts/home

even this might help you for analysis.

Regards

Vijay

Edited by: vijay Kumar on Jun 4, 2010 9:25 AM

[former_member4985]

Hi Vijay!

Check the problem described on OSS Note:

#1340480 - UDDI Invalid Response code (404) uddinull

If it's the case, look for a user with a "random" name existing in the

UME database, if you find it, delete all of them and see if works.

May there are a lot of "random" users, but you can remove them

since they can cause this kind of problem for the Services Registry.

With regards,

Caio Cagnani

[vijay_kumar133]

Hi Caio Cagnani,

I have checked the default Trace in which i din't find any exception as mentioned in note Note 1340480 - UDDI Invalid Response code (404) uddinull

But while investigating i found in default trace an error as and same as well as

the same error i can see in

SOA Management-Application and Scenario Communication-Single Service Administration: Service Definitions-

consumer proxies and search for ServicesRegistrySi and the logs and traces

in the records as

#2.0 #2010 06 05 12:08:44:919#+0530#Error#com.sap.engine.services.ejb3.runtime#

#BC-JAS-EJB#ejb#0021286C81C00011000000140000180A#76976850000197976##com.sap.engine.services.ejb3.runtime####74B6B2F16E0011DFC30E0021286C81C0#74b6b2f16e0011dfc30e0021286c81c0#74b6b2f16e0011dfc30e0021286c81c0#0#Timeout Event Processor, id [4], invocation [73]#Java##

System exception

[EXCEPTION]

#1#javax.ejb.EJBException: (Failed in component: sap.com/tc_esiuddi_srproxy_{ear, BC-ESI-UDDI) Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.getPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.GetPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySigetPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySigetPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySigetPhysicalSystemsFault12 method on bean instance com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade@5de75dd9 for bean sap.com/tc}esi_uddisr_proxyearannotation|tc_esiuddi_srproxy~ejbm.jarannotation|ServicesRegistryProxyFacade in application sap.com/tc_esiuddi_srproxy~ear.; nested exception is: javax.xml.ws.WebServiceException: Invalid Response code (404). Server <http://relmetrodev:50700/ServicesRegistrySiService/ServicesRegistrySiPort> returned message <Not Found>.

javax.xml.ws.WebServiceException: Invalid Response code (404). Server <http://relmetrodev:50700/ServicesRegistrySiService/ServicesRegistrySiPort> returned message <Not Found>.

at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:173)

at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:120)

at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:83)

at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:64)

at $Proxy3032.getPhysicalSystems(Unknown Source)

at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.getPhysicalSystems(ServicesRegistryProxyFacade.java:277)

at sun.reflect.GeneratedMethodAccessor630.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)

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 $Proxy203.getPhysicalSystems(Unknown Source)

at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.getPS(SOACentralSRPublisherImpl.java:2348)

at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.isCurrentPhysicalSystemPublished(SOACentralSRPublisherImpl.java:586)

at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.getLocal(SOACentralSRPublisherImpl.java:136)

at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.publishServiceDefinitions(SOACentralSRPublisherImpl.java:985)

at com.sap.esi.esp.service.server.mass.PublishRulesHandler.publishServiceDefinitions(PublishRulesHandler.java:514)

at com.sap.esi.esp.service.server.mass.PublishRulesHandler.process(PublishRulesHandler.java:464)

at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.process(SOATimeoutListenerImpl.java:550)

at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.run(SOATimeoutListenerImpl.java:383)

at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.timeout(SOATimeoutListenerImpl.java:170)

at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:74)

at com.sap.engine.frame.core.thread.Task.run(Task.java:73)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)

Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (404). Server <http://relmetrodev:50700/ServicesRegistrySiService/ServicesRegistrySiPort> returned message <Not Found>.

at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:581)

at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1134)

at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:818)

at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:759)

at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:167)

Regards

Vijay G

Edited by: vijay Kumar on Jun 5, 2010 12:08 PM