Publishing Service in Service Registry from SOAMANAGER/WSPUBLISH

Hi,
When I am trying to publish services from SOAMANAGER to SERVICE REGISTRY all the services are published successfully
I am able see a message in display log.But when i check the services in service regisrty i am not able see any service ...what could be the problem?where i can check the log?
Thanks
Swathi

Hi Chanakya,
Please find this help.sap.com link which gives the standard procedure for publishing services.
[Publishing a Service|http://help.sap.com/saphelp_nw70/helpdata/EN/44/b7f7e1354135e7e10000000a1553f7/frameset.htm]
Even this indicates use of WSPUBLISH Transaction.
I'll update if any new information is found.
Regards,
Alka.

Similar Messages

Publish an Enterprise Service in Service Registry from SOAMANAGER

Dear All,
Can anyone please helpme with the procedure or step-by-step guide to Publish an Enterprise Serive in Service Registry from SOAMANAGER?
Thanks a lot.
Regards

Hi Chanakya,
Please find this help.sap.com link which gives the standard procedure for publishing services.
[Publishing a Service|http://help.sap.com/saphelp_nw70/helpdata/EN/44/b7f7e1354135e7e10000000a1553f7/frameset.htm]
Even this indicates use of WSPUBLISH Transaction.
I'll update if any new information is found.
Regards,
Alka.

Can't publish service from soamanager

Hi all,
I want to publish a service from soamanager.
Found Calls
Status Timestamp Interface Name Location Is Prescheduled Communication Pattern Call ID
Error 2009-05-11 09:42:21 CO_ESREGISTRY_WSSI Consumer X Method:getVersionInfo 4A039102F16800B5E1008000C0A81213
Error 2009-05-11 09:47:15 CO_ESREGISTRY_WSSI Consumer X Method:getVersionInfo 4A03919EF16800B5E1008000C0A81213
Error 2009-05-11 09:53:18 CO_ESREGISTRY_WSSI Consumer X Method:getVersionInfo 499DCF8A910F0063E1008000C0A81213
Error 2009-05-11 09:53:18 CO_ESREGISTRY_WSSI Consumer X Method:getPhysicalSystem 499DCF8D910F0063E1008000C0A81213
Error 2009-05-11 09:53:18 CO_ESREGISTRY_WSSI Consumer X Method:publishPhysicalSystem 499DCF90910F0063E1008000C0A81213
Error Error CL_SOAP_RUNTIME_CLIENT EXEC_PROCESSING SOAP Runtime SOAP Fault Exception caught: : Cannot create implementation instance. Nested message: An exception occurred while obtaining UDDI Logical Ports. Please, check your configuration settings (UDDI Endpoint or UDDI wsdl file)[_DestinationServiceImpl7000] Application or service service:tcesiesp~srv tried to access destination UDDI_DESTINATION of type WSDestinationTemplate which does not currently exist in the destination service. You can create destinations in the NWA under Configuration Management->Infrastructure->Destinations..
What do I have to configure that it is working?
Please don't refer to documentation about the transaction WSPUBLISH!!!!
regards

Hi Poonam,
I followed your steps and I am not able to publish it. Ok, let me give my landscape.
I am using Netweaver CE 7.1 Trial Version and EHP1 for SAP Netweaver 7.0 Trial Version.
I created a simple calculator example in Enterprise Service Builder where in it takes 2 inputs and will give 1 output (simple addition).
I did save and activate the objects in ESB.
Now in SE80, I did see this Service Interface and created a proxy object and activated. I noticed that the "State" of the service is "Not released". How would we release this??
In SOAMANAGER transaction, I did create the endpoints. Also, I did notice that under Classification, the lifecycle status is "Not Released".
I cannot find this service in the "Service Registry" page.
I followed your steps as mentioned.
Q) Confirm that your Service Registry is configured properly?
In TXN SOAMANAGER, I went to Technical Configuration->Publication Administration->Services Registry. In here there is a entry:
Registry = SR_UDDI
Proxy Class = LP_WORKPLACE
Logical Port = CE1LOGICALPORT
Primary = X
Q) Do you have SR_UDDI_REG authorization object ?
There is a role called SAP_BC_WEBSERVICE_ADMIN which contains it . Assign this role to the user.
and check.
Yes, the role has been assigned to my userid in SU01 transaction
Q) Also Follow the below steps if not followed.:
Configuring your WS via SOAMANAGER or WSCONFIG/ WSADMIN is not all. After you do the config, you need to publish it.
In order to publish:
Go to Txn SM59 and create two TYPE G destinations for:
1. UDDI INQUIRY and
2.UDDI Publish
I did create 2 destinations with type "G" in SM59
RFC Destination = UDDI INQUIRY & UDDI PUBLISH
Target Host = localhost
Service No = 50000
path prefix = /sr/uddi
Q) Make sure you have OLD_UDDI attached to your user profile.
Then go to txn: SUDDIREG to register your destinations.
How do I check OLD_UDDI Profile ???
The Txn SUDDIREG doesn't contain anything. It's blank.
Open your WS in SE80 and go to variants tab.
on the UDDI node right click and publish to the UDDI registry you menytioned in SUDDIREG.
I did select my "Service Interface" in SE80 but couldn't find variants tab.
Your help is much appreciated.
Thanks,
Sathya

No service endpoint after publishing (SOAMANAGER & WSPUBLISH)

Hello,
When I am publishing an Enterprise Service, even if I select the option for publish "service definition & endpoints",the service is published succesfully but no endpoint is generated. This happen after executing the transaction in SOAMANAGER or WSPUBLISH.
Please, someone knows why?
Thanks
Regards
SU
Edited by: soauniverse on Jan 14, 2010 9:17 PM

Not Answered.

BPM Error in publishing webservice in service registry

hi,
i am getting following error when i try to publish webservice wsdl file in service registry.
please let me know do i need to do any settings in nwa
com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail message: com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.ValidationException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='WSDL_WSDL_EXCEPTION', Arguments: ['IO Exception occurred while parsing file:Invalid Response Code: (500) Internal Server Error. The requested URL was:"http://sapsbx11:50000/PurchaseOrderCreateRequestConfirmationInService/PurchaseOrderCreateRequestConfirmation?wsdl"', 'http://sapsbx11:50000/PurchaseOrderCreateRequestConfirmationInService/PurchaseOrderCreateRequestConfirmation?wsdl']> : 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.ValidationException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='WSDL_WSDL_EXCEPTION', Arguments: ['IO Exception occurred while parsing file:Invalid Response Code: (500) Internal Server Error. The requested URL was:"http://sapsbx11:50000/PurchaseOrderCreateRequestConfirmationInService/PurchaseOrderCreateRequestConfirmation?wsdl"', 'http://sapsbx11:50000/PurchaseOrderCreateRequestConfirmationInService/PurchaseOrderCreateRequestConfirmation?wsdl']> : 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.ValidationMessage: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='WSDL_WSDL_EXCEPTION', Arguments: ['IO Exception occurred while parsing file:Invalid Response Code: (500) Internal Server Error. The requested URL was:"http://sapsbx11:50000/PurchaseOrderCreateRequestConfirmationInService/PurchaseOrderCreateRequestConfirmation?wsdl"', 'http://sapsbx11:50000/PurchaseOrderCreateRequestConfirmationInService/PurchaseOrderCreateRequestConfirmation?wsdl']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en

Hi,
In CE 7.1 Ehp1 we need not publish the web service directly to the service registry. We can publish all the webservices using NetweaverAdministrator.
Please go through this link to know how to publish the webservice to the Service Registry using NWA.
[Publishing WebServices from the Netweaver Administrator|http://help.sap.com/saphelp_nwce711/helpdata/en/48/56855c708131c3e10000000a42189d/content.htm]
Regards,
Gayathri

Using the local service registry from other applications (VC, GP)

Hi all,
I am not sure if this is the appropriate forum, but my problem is the service registry I think.
I am facing the problem of using services that I publish to my local service registry from VC and GP.
The problem is as follows:
I publish the services via the "publish" tab on the http://localhost:50000/sr page. The process is executed successfully according to the message.
Then on the Service Definitions Tab of http://localhost:50000/sr I can find and test the service, though on the System Details Tab All parameters are set to "No data available".
When I then try to search the service from the VC (searching in a Ws of type service registry, which I have previously configured through destination templates), I get "no services found".
In the GP I see the published services, but when I try to use them as callable objects, I get the following error message:
"WS-Interface initialization problem of GenericServiceFactory..., Local_Service_Registry - ServiceName not found. possible changes in the WSDL"?
I also tried publishing the web services through the ws restrictions, but they dont get published.
I have adjusted the UDDI_DESTINATION and CLASSIFICATION_DESTINATION properties according to the help page for the localhost system. I also use a Local_Service_Registry destination of type service registry as I thought I need it in oder to use the service registry.
Has somebody experienced this problem before?
Thanks in advance!
Best regards,
Vera

Hi,
the exact error trace is as follows:
#1#javax.ejb.EJBException: Exception raised from invocation of public com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesResponseType com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishClassificationSystemValues(com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesType) throws com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishClassificationSystemValuesFault method on bean instance [email protected]8 for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxy~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: connect)
javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused: connect)*
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:158)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:117)
     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 $Proxy56_10002.publishClassificationSystemValues(Unknown Source)
     at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishClassificationSystemValues(ServicesRegistryProxyFacade.java:302)
     at sun.reflect.GeneratedMethodAccessor810_10002.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: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 $Proxy34_10002.publishClassificationSystemValues(Unknown Source)
     at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.createUDDIClassifications(SOACentralSRPublisherImpl.java:742)
     at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.publishServiceDefinitions(SOACentralSRPublisherImpl.java:435)
     at com.sap.esi.esp.service.server.mass.PublishRulesHandler.publish(PublishRulesHandler.java:282)
     at com.sap.esi.esp.service.server.mass.PublishRulesHandler.process(PublishRulesHandler.java:248)
     at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.process(SOATimeoutListenerImpl.java:128)
     at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.timeout(SOATimeoutListenerImpl.java:51)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:72)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:144)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:242)
Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused: connect)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:340)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:961)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:700)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:673)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:152)
     ... 37 more
Caused by: java.io.IOException: Unable to connect to localhost:50100 - Connection refused: connect
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:666)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:658)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:621)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:499)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:450)
     at com.sap.engine.services.webservices.espbase.client.bindings.ClientHTTPTransport.getRequestStream(ClientHTTPTransport.java:481)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:298)
     ... 41 more
javax.ejb.EJBException: Exception raised from invocation of public com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesResponseType com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishClassificationSystemValues(com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesType) throws com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishClassificationSystemValuesFault method on bean instance [email protected]8 for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.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: connect)
     at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72)
     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 $Proxy34_10002.publishClassificationSystemValues(Unknown Source)
     at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.createUDDIClassifications(SOACentralSRPublisherImpl.java:742)
     at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.publishServiceDefinitions(SOACentralSRPublisherImpl.java:435)
     at com.sap.esi.esp.service.server.mass.PublishRulesHandler.publish(PublishRulesHandler.java:282)
     at com.sap.esi.esp.service.server.mass.PublishRulesHandler.process(PublishRulesHandler.java:248)
     at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.process(SOATimeoutListenerImpl.java:128)
     at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.timeout(SOATimeoutListenerImpl.java:51)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:72)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:144)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:242)
Caused by: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused: connect)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:158)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:117)
     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 $Proxy56_10002.publishClassificationSystemValues(Unknown Source)
     at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishClassificationSystemValues(ServicesRegistryProxyFacade.java:302)
     at sun.reflect.GeneratedMethodAccessor810_10002.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:43)
     ... 28 more
Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused: connect)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:340)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:961)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:700)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:673)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:152)
     ... 37 more
Caused by: java.io.IOException: Unable to connect to localhost:50100 - Connection refused: connect
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:666)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:658)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:621)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:499)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:450)
     at com.sap.engine.services.webservices.espbase.client.bindings.ClientHTTPTransport.getRequestStream(ClientHTTPTransport.java:481)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:298)
     ... 41 more

I can not publish and query services in Registry Server?Help please!

I want to use Registry Server in Jwsdp1.5 to publish and query services,but there is some problems:
2006-4-26 10:05:26 com.sun.registry_server.server.RegistryServerServlet init
��: NamingException: javax.naming.NameNotFoundException: Name org.xml.sax.driver is not bound in this Context
2006-4-26 10:05:27 com.sun.xml.messaging.saaj.soap.MessageImpl identifyContentType
��: SAAJ0537: �� SOAP ��
2006-4-26 10:05:27 com.sun.xml.messaging.saaj.soap.MessageImpl <init>
��: SAAJ0535: ��
javax.xml.registry.JAXRException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message
     at com.sun.xml.registry.uddi.RegistryServiceImpl.jaxmSend(Unknown Source)
     at com.sun.xml.registry.uddi.RegistryServiceImpl.send(Unknown Source)
     at com.sun.xml.registry.uddi.Processor.processRequestJAXB(Unknown Source)
     at com.sun.xml.registry.uddi.UDDIMapper.findOrganizations(Unknown Source)
     at com.sun.xml.registry.uddi.BusinessQueryManagerImpl.findOrganizations(Unknown Source)
     at QueryByName.doPost(QueryByName.java:63)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:535)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:790)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:709)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:572)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:644)
     at java.lang.Thread.run(Thread.java:595)
Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message
     at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:127)
     ... 34 more
Caused by: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:121)
     ... 34 more
Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message
     at com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:231)
     at com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl.<init>(Message1_1Impl.java:43)
     at com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl.createMessage(SOAPMessageFactory1_1Impl.java:32)
     at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:354)
     at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:150)
     ... 36 more
Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Invalid Content-Type:text/html. Is this an error message instead of a SOAP response?
     at com.sun.xml.messaging.saaj.soap.MessageImpl.identifyContentType(MessageImpl.java:295)
     at com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:146)
     ... 40 more
can you help me?expectiong your advise!thank you

I have created my own private registry, I hava installed JWSDP1.5.
I use a .jsp file and a servlet to publish services,the servlet is:
import javax.xml.registry.*;
import javax.xml.registry.infomodel.*;
import java.net.*;
import java.security.*;
import javax.servlet.*;
import javax.servlet.http.*;
import java.io.*;
import java.util.*;
public class Publish extends HttpServlet{
     public void doGet(HttpServletRequest request,HttpServletResponse response)
     throws ServletException,IOException{
          doPost(request,response);
     public void doPost(HttpServletRequest request,HttpServletResponse response)throws ServletException,IOException{
     String userName=request.getParameter("username");
     String authPassword=request.getParameter("password");
     Connection connection = null;
RegistryService rs=null;
BusinessLifeCycleManager blcm=null;
BusinessQueryManager bqm = null;
     Properties props=new Properties();
props.setProperty("javax.xml.registry.queryManagerURL","http://localhost:8080/RegistryServer");
props.setProperty("javax.xml.registry.lifeCycleManagerURL","http://localhost:8080/RegistryServer");
props.setProperty("javax.xml.registry.factoryClass","com.sun.xml.registry.uddi.ConnectionFactoryImpl");
//props.setProperty("com.sun.xml.registry.http.proxyHost",httpHost);
//props.setProperty("com.sun.xml.registry.http.proxyPort",httpPort);
// props.setProperty("com.sun.xml.registry.https.proxyHost",httpsHost);
// props.setProperty("com.sun.xml.registry.https.proxyPort",httpsPort);
try{
// Create the connection, passing it the
// configuration properties
ConnectionFactory factory =
ConnectionFactory.newInstance();
factory.setProperties(props);
connection=factory.createConnection();
PrintWriter out=response.getWriter();
out.println("<a href=\"/publishapp/publish.jsp\">You can click here to be Back </a>");
out.println("<H3>Created connection to registry</H3>");
rs=connection.getRegistryService();
blcm = rs.getBusinessLifeCycleManager();
bqm = rs.getBusinessQueryManager();
//out.println("Got registry service, query " +"manager, and life cycle manager");
// Get authorization from the registry
PasswordAuthentication passwdAuth =
new PasswordAuthentication(userName,authPassword.toCharArray());
Set creds = new HashSet();
creds.add(passwdAuth);
connection.setCredentials(creds);
out.println("<br>");
out.println("<H3>Established security credentials</H3>");
//receive organization name and description
String orgName=request.getParameter("orgname");
String orgDescription=request.getParameter("orgdescription");
// Create organization name and description
Organization org =
blcm.createOrganization(orgName);
InternationalString s =
blcm.createInternationalString(orgDescription);
org.setDescription(s);
//receive contactor name phone and Email
String contactName=request.getParameter("contactname");
String contactPhone=request.getParameter("contactphone");
String contactEmail=request.getParameter("contactemail");
// Create primary contact, set name
User primaryContact = blcm.createUser();
PersonName pName =
blcm.createPersonName(contactName);
primaryContact.setPersonName(pName);
// Set primary contact phone number
TelephoneNumber tNum = blcm.createTelephoneNumber();
tNum.setNumber(contactPhone);
Collection phoneNums = new ArrayList();
phoneNums.add(tNum);
primaryContact.setTelephoneNumbers(phoneNums);
// Set primary contact email address
EmailAddress emailAddress =blcm.createEmailAddress(contactEmail);
Collection emailAddresses = new ArrayList();
emailAddresses.add(emailAddress);
primaryContact.setEmailAddresses(emailAddresses);
// Set primary contact for organization
org.setPrimaryContact(primaryContact);
String serviceName=request.getParameter("servicename");
String serviceDescription=request.getParameter("servicedescription");
String serviceURL=request.getParameter("serviceurl");
String svcbindDescription=request.getParameter("svcbinddescription");
// Create services and service
Collection services = new ArrayList();
Service service =
blcm.createService(serviceName);
InternationalString is =
blcm.createInternationalString(serviceDescription);
service.setDescription(is);
// Create service bindings
Collection serviceBindings = new ArrayList();
ServiceBinding binding = blcm.createServiceBinding();
is = blcm.createInternationalString(svcbindDescription);
binding.setDescription(is);
// allow us to publish a fictitious URL without an error
binding.setValidateURI(false);
binding.setAccessURI(serviceURL);
serviceBindings.add(binding);
// Add service bindings to service
service.addServiceBindings(serviceBindings);
// Add service to services, then add services to organization
services.add(service);
org.addServices(services);
//receive Classification scheme name and value
String classificationScheme=request.getParameter("classificationscheme");
String classificationName=request.getParameter("classificationname");
String classificationValue=request.getParameter("classificationvalue");
// Set classification scheme to NAICS
ClassificationScheme cScheme =
bqm.findClassificationSchemeByName(null, classificationScheme);
// Create and add classification
Classification classification = blcm.createClassification(cScheme,
classificationName,classificationValue);
Collection classifications = new ArrayList();
classifications.add(classification);
org.addClassifications(classifications);
// Add organization and submit to registry
// Retrieve key if successful
Collection orgs = new ArrayList();
orgs.add(org);
BulkResponse response1 = blcm.saveOrganizations(orgs);
Collection exceptions = response1.getExceptions();
if (exceptions == null) {
out.println("<br>");
out.println("<H3>Service Registering is Sucessful!</H3>");
out.println("<br>");
out.println("<H3>service information saved is</H3>");
out.println("<H3>");
out.println(orgName);
out.println("</H3>");
Collection keys = response1.getCollection();
Iterator keyIter = keys.iterator();
if (keyIter.hasNext()) {
javax.xml.registry.infomodel.Key orgKey =
(javax.xml.registry.infomodel.Key) keyIter.next();
String id = orgKey.getId();
out.println("<H3>service key is </H3>");
out.println("<H3>");
out.println(id);
out.println("</H3>");
} else {
Iterator excIter = exceptions.iterator();
Exception exception = null;
while (excIter.hasNext()) {
exception = (Exception) excIter.next();
System.err.println("Exception on save: " +
exception.toString());
} catch (Exception e) {
e.printStackTrace();}
the exception in the tomcat50-jwsdp/logs:
javax.xml.registry.JAXRException: javax.xml.bind.JAXBException
- with linked exception:
[javax.xml.soap.SOAPException: Unable to create message factory for SOAP: Provider com.sun.xml.messaging.saaj.soap.MessageImpl could not be instantiated: java.lang.IllegalAccessException: Class javax.xml.soap.FactoryFinder can not access a member of class com.sun.xml.messaging.saaj.soap.MessageImpl with modifiers "protected"]
     at com.sun.xml.registry.uddi.Processor.processRequestJAXB(Unknown Source)
     at com.sun.xml.registry.uddi.UDDIMapper.getAuthorizationToken(Unknown Source)
     at com.sun.xml.registry.uddi.ConnectionImpl.setCredentials(Unknown Source)
     at Publish.doPost(Publish.java:66)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:535)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:790)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:709)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:572)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:644)
     at java.lang.Thread.run(Thread.java:595)
Caused by: javax.xml.bind.JAXBException
- with linked exception:
[javax.xml.soap.SOAPException: Unable to create message factory for SOAP: Provider com.sun.xml.messaging.saaj.soap.MessageImpl could not be instantiated: java.lang.IllegalAccessException: Class javax.xml.soap.FactoryFinder can not access a member of class com.sun.xml.messaging.saaj.soap.MessageImpl with modifiers "protected"]
     at com.sun.xml.registry.common.util.MarshallerUtil.jaxbMarshalObject(Unknown Source)
     ... 32 more
expecting yours advise, thanks!!

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

Test published web service in Service Registry

I have published a web service to the Service Registry and what to see if I can test this web service in Service Registry directly.
When I go to the 'EndPoint' tab and click on Test Button, I got to WSNavigator page and my web service's WSDL URL is correctly displayed in the WSDL URL field, however, I got the following error:
Invalid Response Code: (502) Bad Gateway. The requested URL was:"http://<hostname>:<port>/sap/bc/srt/wsdl/bndg_491D31E0A67A1FD0E100000022E2EA08/wsdl11/binding/ws_policy/document?sap-client=<xxx>"
Did I miss some configuration step?

Not answered

Deploying to Oracle Services Registry from Oracle Workshop (10.3.1)

Hi folks,
In our project, we are using Oracle Services Bus (version 10.3.1) and we want to interact with an UDDI registry (Oracle Service Registry). We used the following process :
1/ Creation of a UDDI file correctly configure in our OSB project from Oracle Workshop. The validation test works like a charm
2/ Importing a Service from UDDI in Oracle Workshop correctly works too.
The problem : We cannot find a way to export our services (Proxy services) from Oracle Workshop into the UDDI. Is it possible ? What do we do wrong and how can we do that ?
Thanks in advance for your answer,
Cheers

This is a blocker issue for us. Any hints ? At least, we need to know if it's possible to do so and if somebody faces the same issue.
Thanks,
Cheers,

Connection to "Central" Services Registry from Visual composer not working

Hi Folks,
We are having issues connecting to the Services registry from the Visual Composer. The search on services in the services registry does not yield any results.
We have configured the NWA page as mentioned on the "Configuring the Services Registry" http://help.sap.com/saphelp_nwce10/helpdata/en/46/94dd02c7b915ebe10000000a114a6b/frameset.htm
Any ideas to help will be highly appreciated.
Thanks
Z.

Hi ZM
I had the same problem with my service registry. In Web Visual Composer, i didn't find any service in SR.
I resolve in two ways.
Configure the service registry in NWDS, there works fine, but i have problem with DC in VC in NWDS.
I use destination WSIL, with this destination i have found all the services
Regards
Marcos

Accessing JAXR registry from within web service

Hi I'm having trouble accessing the registry from within a web service running in the tomcat server.
The service should register with the registry at startup, but in the logs from the tomcat server I can see that a JAXRException is thrown:
javax.xml.registry.JAXRException: Unable to create ConnectionFactory: Provider com.sun.xml.registry.common.ConnectionFactoryImpl not found
at javax.xml.registry.ConnectionFactory.newInstance(Unknown Source)
If I run the program from outside the tomcat server as a standalone program, it registers perfectly.
I believe the problem is that it is missing one or more jars.
I have tried to put the jaxr-jars under shared/libs but that hasn't solved the problem.
Has anyone an idea of what I'm doing wrong?
Help is greatly appreciated!
/ Bo

Hi swatdba
I know that the build file states alle the packages that I need, and as I said, if I run my program like the regular JAXR examples, it works fine.
The thing is, the JAXR examples are not web services on their own. They are merely Java programs that access the registry.
In my case I am building a web service that should run in the tomcat server. When it initialises, it should register with the register, and also be able to search for other web services.
I thought this would be possible per default, ie. the jars that the web service needs should already be available in the tomcat server, but it doesn't work. I have tried to put the jars that I've found in the build script in the folder C:\jwsdp-1.3\shared\lib, which according to the tomcat manual should be used to put jars that you want to share between your web services.

Regarding How to Register a service in Service Registry ....?

Hi All ,
i have a doubt , hope i may get some answers form the Expert...!
1) Is there any diffrence between registering a Service in SR and Publishing a Service in SR (SAP PI 7.1)?
2) If yes, then can some one pls provide with some more info or links where i can search ?
Thank you in advance,
Regards,
Aziz khan...!

Hi Aziz,
ServiceRegistry: The Services Registry is a registry for Web services. Located centrally within an SOA landscape, it contains entries for all services and service definitions in that landscape,with references to the servicesu2019 relevant WSDL metadata and to the locations of the callable service endpoints.
Publishing: By entering the endpoint WSDL of a service definition that provides a valid URL you can publish service definitions to the Services Registry.
From the above definitins i dont think there is any difference between Registering and Publishing.Because Registering in UDDI (service registry ) means giving Acess points to a particular service developed and this process of giving acess to webservices in UDDI is nothing but Publishing.who want to consume then they have to acess those endpoints(action points) through webservices URL
FYI i have not worked on services on PI7.1 but trying to answer your qurey with little conceptual knolwdge on Webservices in PI7.1.As far as registering the services are concerned please refer the following link and let me see wether its useful in any way ....navigate .
http://help.sap.com/saphelp_nwpi71/helpdata/en/45/b4ca147d2952f5e10000000a1553f7/frameset.htm
Serviceregistry----> Tasks---->with references to the servicesu2019 relevant WSDL metadata and to the locations of the callable service endpoints
Thanks,
Ram.

XML Publisher with Service Module - Service Request Reports -- URGENT

Hi all ... any pointers/help/guidance with the problem listed below would be much appreciated.
I'm working in the context of the Oracle Service Module & Service Request Reports.
I'm required to configure the XML Publisher Responsibility seeded functionality with the service module reports.
Listed below are the two reporting requirements that I'm considering , corresponding to the following seeded XMLP Responsibility seeded components:
(I'm quoting an extract from the Oracle TeleService Implementation & User Guide here).
Detailed Report
Data Definition: Service Request Detail Definition (CS_SR_DETAIL_DEF)
Corresponding Template: Service Request Detail Report Template (CS_SR_DETAIL_TMP.en)
Template Description: Includes all of the available service request attributes including charges, the two descriptive flexfields, and extensible attributes.
Summary Report
Data Definition: Service Request Summary Definition (CS_SR_SUMMARY_DEF)
Corresponding Template: Service Request Summary Report Template (CS_SR_SUMMARY_TMP_en)
Template Description: Includes a subset of the detailed report attributes including the same charges information as the detailed report.
When I log into the EBS >> XML Publisher Administrator Responsibility >> Service Application ... I find these seeded XMLP components, together with the preview data, downloadable templates & sample output.
The question is:
Where (responsibility/application/navigation/etc.) do I find the seeded EBS Service Reports to provide the expected XML input to the seeded XMLP Service Request Data Definitions & Templates????
Notes ...
I have found the following two reports, under the Service Application in EBS, set their output type to XML and viewed the output of the submitted request:
- Service Request Detail Report
- Service Request Summary Report
... but each of these two reports produce XML output of a different data model/structure to that expected by each of the corresponding seeded XMLP data-definitions/templates.
Additionally, I cannot find any corresponding concurrent program definitions on the system with the same SHORT-NAME/CODE as the seeded XMLP data definitions themselves i.e. CS_SR_DETAIL_DEF and CS_SR_SUMMARY_DEF.
Are the necessary reports not actually seeded within EBS? Do the seeded XMLP data definitions & templates require development of new Concurrent Programs from scratch to access the database tables and provide the necessary data/input, or am I missing something here??

I am sure you found a solution to your problem. If not, to give a pointer to this issue, I guess these reports are gererated right from the service request screen and this definition is used there.This report can be generated from several places based on where you are within SR scree.
Thanks
Nagamohan

Error while trying to publish a web service in UDDI client

hi
i m getting this error when trying to publish my web service in UDDI client.I have
configured my uddi client using Visual Administrator.I created a local test registry.The name of my registry is QuickCarRentalRegistry_Local.I created this at admin level.I also tried at level 1 Tier.But it was giving the same error.
The error is "<b> Internet Explorer Script Error</b>".my ie version is 7.0
In my alert window it displays error: 'ur_txt' is undefined.
Regards
mythri.

Hi mythri.
Did you find a way out of this error? Could you share the solution with me? Because I am facing a problem that looks just like the one you had.
Thanks in advance.
Renan

Publishing Service in Service Registry from SOAMANAGER/WSPUBLISH

Similar Messages

Maybe you are looking for