SERVICE_REGISTRY_NOT_AVAILABLE

[sriram_devarapalli]

Hi Team,

we had a scenario where we need to send data from SOAP to R3 system using Proxy in synchronous way.

since our PI is 7.1 & ECC is 6.0 EHP1, we had followed the PDF "Service Enabling with SAP PI 7.1"; which is posted in SDN.

we had implimented the PROXY in ECC system.

Now where do we need to create the Service & End point?

in ECC we do not have SOAMANAGER, so we created the service in ECC using Wizard, then when we tried to publish the Service Interface WSDL from PI we are getting Error " SERVICE_REGISTRY_NOT_AVAILABLE" .

is there any other way to do this scenario.

Thanks in Advance,

Sriram

[Former Member]

Hi,

I make out that your scenarios is as follows:

Application > SOAP Channel > PI > Proxy > ECC.

Publishing Web Service url is not mandatory. You can just share the Web Service URL with the SOAP Application.

Please right click on Sender agreement to view WSDL URL and wsdl itself.

Also, you dont need to publish end point if you are using XI 3.0 protocol with PI. Its is required only when you use WS-RM or want to use web service without PI.

Regards,

Vikas

Edited by: Vikas Aggarwal on Oct 5, 2009 6:05 PM

[former_member200962]

 SERVICE_REGISTRY_NOT_AVAILABLE

Check this related discussion:

Regards,

Abhishek.

[Former Member]

hi,

If SOAMANAGER not available then use following transactions:

WSCONFIG and WSADMIN

Read documentation on SAP help: http://help.sap.com/saphelp_nw70/helpdata/en/47/3431de6c720aa7e10000000a114a6b/content.htm

Regards,

Gourav

[Former Member]

Hi,

Check following note for configuring services registry, 1267817.

Regards,

Siddhesh S.Tawate

[sriram_devarapalli]

HI Team,

We followed the Note "1267817" and we are getting the same error.

The Erro Log

====================================================================

= Root Exception ===================================================

====================================================================

Thrown:

com.sap.aii.ib.core.uddi.RegistryClientException: The Service Interface cannot be published. Please view the logs for more details.

at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:435)

at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishPhysicalSystem(ServicesRegistryBean.java:316)

at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:173)

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 com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)

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 $Proxy1611.publishServiceInterface(Unknown Source)

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 com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)

at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)

at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)

at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)

at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)

at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)

at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)

Serialized cause: javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade@63c58ddc for bean sap.com/tc_esiuddi_srproxy_{ear*annotation|tc}esi_uddisr_proxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused); nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade@63c58ddc for bean sap.com/tc_esiuddi_srproxy~earannotation|tc_esiuddi_srproxy~ejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused)

at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$Required.error(TransactionAttributeHandler.java:307)

at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$TransactionAttributeErrorsHandler.error(TransactionAttributeHandler.java:130)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:40)

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 $Proxy405.publishPhysicalSystems(Unknown Source)

at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:417)

... 39 more

Thanks in Advance,

Sriram.

Edited by: Sri Ram Devarapalli on Oct 6, 2009 9:39 AM

[former_member187339]

Hi,

Just check by doing the steps mentioned in note

Note 1319742 - Services Registry Publication

Regards

Suraj

[sriram_devarapalli]

Hi Team,

Since we did not have SOAMANAGER in ECC EHP1 System, we are looking into WSADMIN,WSCONFIG.

Where do we create UDDI Registry?

Thanks in Advance,

Sriram

[sriram_devarapalli]

Hi Team,

For this scenario I am refering the document 'Service Enabling with SAP NetWeaver Process Integration 7.1'.

As our ABAP system is ECC EHP1 transaction SOAMANAGER dose not exists. So, I have created a Web Service for the Proxy Interface using wizard in Tcode SPROXY. And I am publishing this service in PI.

While i am publishing the service i am getting this Error "SERVICE_REGISTRY_NOT_AVAILABLE".

I had also applied Notes 1319742 , 1267817.

After the publish will this scenario work?

Please tell if any one has worked on this.

Thanks in Advance,

Sriram.

[Former Member]

Hi Sai Ram,

As you said, your sender is ECC system so it is not necessary for you to have web service. You can directly communicate through Abap proxy.

If still you want to go for web service, then I guess your approach should be as follows:

1. Do all necessary configuratons in IR. Now for sender message type create web service and publish it in PI.

2. This Web service has to be consumed by you in ECC Abap Proxy.

3. For Service Publishing in PI Service registry, there are certain configurations required to be done from basis side.

4. I guess the note no provided by me earlier in addition to content available on help.sap should be sufficient for step no 3.

Correct me if the above approach suggested by me is wrong.

Regards,

Siddhesh S.Tawate

[sriram_devarapalli]

Hi Siddhesh,

after implemeted the above notes, 1319742 , 1267817 we are getting error '

' Invalid Response code (401). Server <_http://PIserver.domain.com:51100/ServicesRegistrySiService/ServicesRegistrySiPort> returned message <Unauthorized>'.

Thanks in Advance,

Sriram.

Edited by: Sri Ram Devarapalli on Oct 12, 2009 8:21 AM

[Former Member]

Hi,

Please check if the users have necessary authorisations.

http://help.sap.com/saphelp_nwpi71/helpdata/EN/46/8b190fc23e59d9e10000000a1553f6/content.htm

Hope this helps.

Regards,

Siddhesh S.Tawate

[sriram_devarapalli]

Hi Siddhesh,

As given in the Notes and in Link, we added the roles in Java side for CPIC_PIESR & even to my user, but not in ABAP side.

But still we are getting the same Error "Unauthorized".

When we test the service in ECC system from SICF, i am geting the error HTTP 500.

When we test http://eccserver:Port/wsnavigator/jsps/index.jsp the error is

*The termination occurred in system ECC with error code 404 and for the reason Not found.

The selected virtual host was 0 *.

When we test http://pi.server.com:51100/ServicesRegistrySiService/ServicesRegistrySiPort

the error is Web Service Endpoint URI expected. Not found endpoint with URI /ServicesRegistrySiService

We have some queries

1) Our service is not available in SOAMANGER. After publish only will it appear?

2) Since our R/3 is ECC 6.0EHP1 we are not able to know where to do this settings?

3) We just created the Proxy in sproxy and creared the End Point Via Wizard, is it the right way?

4) where can we find the end point for the service ?

Thanks in Advance,

Sriram

[sriram_devarapalli]

Hi Team,

In PI 7.1, please recheck the USER Access & Password and Roles for the User assigned.

Thanks & Regards,

Sriram