Documentation of services in the service registry

Hi all,
in the service registry i can publish a documentation url for enterprise services.
How can i make a documenation for NON-Enterprise Services?
Can i publish a URL for normal web services?
How can i document a normal web service?
regards

Not possible yet.

Similar Messages

  • Documentation URL in Services Registry.

    Hi,
    We are trying to use the Services Registry of SAP (in PI 7.1) for registering Services, however find a major challenge in terms of updating the documentation URL.
    For Non SAP services we can update the same in the provider system and thus while registering the service the URL appears. However could not find a way to do the same for SAP services (custom as well as Enterprise Services). there was some help provided in note 1319742 which is not visible in SOAMANAGER for the ECC system that we have (6.0 EhP4), also the transaction 'WSDOCU_SERVER' did not help (service published without the documentation URL even after maintaing a URL).
    Any help on this will be appreciated.
    Regards,
    Avishek.

    check for this sap note 1120842 - Publish WS Documentation Link during Service Publication.
    - julius

  • Service Registry - Services without documentation

    Hi all,
    how can i add a documentation to my services in the service registry?
    Documentation URL: There is no documentation URL available
    regards

    check for this sap note 1120842 - Publish WS Documentation Link during Service Publication.
    - julius

  • Service Registry documentation URL and deleting published services?

    Hello,
    We are using SAP NetWeaver PI 7.1 SP 7. Do anyone know how you can control the published Documentation URL for published Service Interfaces in the Service Registry when you publish service interfaces directly from the ESR (from the WSDL tab on a Service Interface)?
    Do anyone know if you can delete published service interfaces in the Service Registry if a service interface have been deactivated/deleted/is not used any more?
    Regards,
    Markus Johansson

    Hi Markus,
    There is anothre approach to delete services using API's.
    Determine the WSDL Url of your Services Registry.
    - Open SAP NetWeaver Administrator and choose SOA Management Application and Scenario Communication Single Service Administration .
    - Search for ServicesRegistrySi and copy the Services Registry WSDL.
    Open WS Navigator.
    - In the WSDL Url field, enter the Services Registry WSDL and choose Next.
    - All Services Registry API operations are displayed.
    - Select operation hideServiceDefinitions and choose Next.
    - Enter either the UDDI key or the logical key of the service definition you want to delete and choose Execute.
    Both keys are displayed on the General tab in the Services Registry.
    In case SR shows you as having no logical key for the service you are interested in removing.
    There is another operation, findServiceDefintions, that can be used to search a name that will return the UDDI key. Take that value and plug it into the hideServiceDefintions uddiKey value.
    Regards,
    Jitender

  • Error while testing the endpoints in Service Registry

    Hi,
    I am getting the following error while testing the endpoint in the Service Registry
    Invalid Response Code: (404) Not Found. The request URL was:"http://<server>:8000/sap/bc/srt/wsdl/bndg_DD73518A3AD471F18558001D0910D3CA/wsdl11/binding/ws_policy/document?sap-client=800". Check, whether the URL is correct, and the Web Service that you are requesting is up and running.
    I have created an Enterprise Service at the backend and have published to the Service Registry of the CE server , but while testing the endpoint in service registry i am getting error.
    Can any one please help me to solve this issue.
    Thanks & Regards,
    Hamsa Shree

    Hi hamsa,
    Have you tested the service? If It works, maybe there's something wrong with your destination configuration.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/705459a3-bf1c-2b10-8a9d-d300ada5f0fc
    You may find a solution in the above article.
    Good luck!
    Wenhao

  • 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

  • Error the port of the service registry

    Dear everyone,
    please help me, i got the error message as below:
    Information for this WSDL portType has not been obtained successfully. Some errors have occured.
    (E.g. some of the parent entities might be corrupted or unpublished.)
    Error message:
    WSDLException: faultCode=INVALID_WSDL: java.io.IOException: Connection to localhost:7201 refused
    Actually, my registry is run on port: 7301: http://localhost:7301/registry/uddi/web
    but I don't know why when I log to oracle enterprise manager, registry control and click on find_tmodel, then click to obtain the list of service in this tmodel; i get the error message above.
    Can anyone tell me how can I change the port value?
    Many thanks in advance,
    sophea

    Now it is ok, i can use registry console to change the port.
    registry console -> manage ->registry management - > replace url

  • Service Registry: Publish the same service for two different business syst.

    Hello all,
    i am trying to publish a webservice in the Service Registry of a PI 7.1 EHP1 and i'm facing a problem. I have configured two Business Systems that use the same Service Interface, let's say Dev and Qua systems. So, this two business systems can be senders of the webservice. I have been able to publish the first Sender Agreement properly, but when i try to publish the second Sender Agreement as the service is already publish i get the following error:
    One service definition with the same name 'SI_I015_EneGISDeviceLocationServicesInternalMessage_In(urn:enemalta.com.mt:iubs:integrations)' found; do you want to delete this object from the Services Registry and continue publishing?
    I've been told that this error might be a permission problem but the user i am using has all the permissions required. Does anyone know how to solve this issue?
    Thank you very much in advance!
    Roger Allué i Vall

    Hi Roger,
    Is that problem solved for you?
    I am looking for inputs on a similar issue here. I need to have a single service but with two different endpoints (for two sender business systems) published in SR.
    Thanks,
    Marz

  • What is the difference of  3 endpoints of ES in Service Registry

    When I search the enterprise service in service registry of PI in the discovery system,  I found the enterprise service and select the endpoint view, there are 3 endpoints, such as Binding_T_HTTP_A_HTTP... , and Binding_T_HTTPS_A_HTTPS..., and MaterialBasicDataByIDQueryResponse_inSOAPBindings.
    What is the diffrence of 3 endpoints?
    When I select enterprise service in SR as a WebDynpro web service model, which one should I choose?
    When I select enterprise service in SR as a automated activity in BPM, which one should I choose?

    Hi Takako,
    When your basis team made the configuration in mass of those enterprise services endpoints probably they did something wrong. Normally you should have just one endpoint - no problem to have more than one, just is more information to keep updated. You have different endpoints specially when you need to keep two versions of the same service running together.
    My suggestion, test the last endpoint you wrote in this message (it is more meaningful). If it works, use it.
    Regards.
    roberti

  • 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

  • PI 7.1 How to delete a published service from the service registry?

    Hello,
    I have the same problem in the pi 7.1, like Rahul in CE (Composition Environment) with the deleting of published services.
    How to delete a published service from the service registry?
    In the WS navigator I found only this operation:
    deleteClassificationSystemValues and deleteClassificationSystem
    I miss the operation deleteService.
    Have you an idea?
    Bye
    Stefan

    Hi all,
    I have opened an oss message and now I have an answer:
    Use this Service: ServicesRegistrySiService and the operation deleteServices with the logical key of the service as parameter.
    The logical key can be seen from the SR UI in the details of the endpoints.
    Bye
    Stefan

  • Exchange BPA Errors (Exchange server is a virtual machine but the additional tools are not installed and The 'Services' string type value located in 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\Setup\Services' registry key is missing)

    Hi,
    I am running BPA on My Exchange 2010 VM (Server 2008 R2 VM on Hyper-V) and get the following errors:
    The 'Services' string type value located in 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\Setup\Services' registry key is missing or inaccessible. The Microsoft Exchange Information Store service won't start. As a result, all services that depend
    on this service won't be able to start
    Exchange server [Exchange Server FQDN] is a virtual machine but the additional tools are not installed. This configuration is not supported. Install Virtual Machine Additions for this guest.
    Problem is that, for the first, that Key exists and the service is actually running fine. And for the second my VM tools are already installed.
    Hopefully someone out there has had the same issue and can assist.
    Pete

    Hi Pete,
    For the first error message, please try the following steps:
    Make sure the Information Store service is in Starting status,
    Automatic startup type and works well, as a test we can try to
    restart the Infroamtion Store service and verify the service works well.
    Start
    Registry Editor, find the registry key “Services” under “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\Setup”, its value is “C:\Program
    files\Microsoft\Exchange Server\v14”(default install location), please check your registry, make sure the key “Services” exist and value is the Exchange Server install location and the
    location is accessible;
    Start
    Registry Editor, and locate the following registry key:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\Setup
    Use the
    Permission option under the Security tab to check the permission setting on this key. Make sure
    System is in the list with Full Control permissions if the service account is Local System. If you are not using Local System as the service account, check the existence of the corresponding account in the list and ensure that
    it has Full Control permissions. Please refer to this article:
    Title: Exchange Store Does Not Start: Errors 7024, 1026, 9542, and 5000
    Link:
    http://support.microsoft.com/kb/285116
    Start
    ADSI Edit, and then browse to the following location:
    Domain.com/Configuration/Services/Microsoft Exchange/Org/Administrative Groups/AdminGroup/Servers/Server Name
    Right-click the
    server name, and then click Properties.
    Click the
    Security tab, make sure this own server’s server object have
    full control permission on its own server.
    If not or the object is missing, please modify the permission or click
    Add, locate the computer account for the Exchange Server computer, add it to the Permissions list with full control.
    Click OK, and then close ADSI Edit.
    Use
    Active Directory Users and Computers to add the current affected
    Exchange Server computer account to the Exchange Servers(previous version should be “Exchange Domain Servers”) group in the
    Microsoft Exchange Security Groups( or Users) OU. Refer to this article:
    http://support.microsoft.com/kb/297295.
    Restart the Exchange Server computer, then rerun the ExBPA.
    For the second error message, Microsoft don’t recommend to install Exchange Server on virtual machine without additional tools, so the error message occurs. We can just ignore
    this message, it will not affect the Exchange servers.
    Regards, Eric Zou

  • Problem with the Browsing of Services Registry in Visual Composer

    Hi,
    I have tried to connect Visula Composer of CE 7.1 to the Services Registry for ES Workplace by configuring 3 Web Service destination on my local server:
    1. UDDI_DESTINATION
    2. CLASSIFICATION_DESTINATION
    3. Backend destination "HU2"
    as stated in the tutorial "How to Browse an Enterprise Services Registry in Visual Composer" (https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/605303db-9d5f-2a10-e0a2-c0e1c8af9e96&overridelayout=true).
    After the configuration, I opened up the "Search" dialog in Visual Composer and selected "Service Registry" for the "Search in" drop down list and then clicked on the link "Advanced Search". An error message "XMSG_COULD_NOT_LOAD_CLASSIFICATIONS" was then displayed. I have tried to google the error message but to my surprise there wasn't even a single result for that.
    Could anyone please help me on this?
    Thanks in advance.
    Regards,
    Joon Meng

    Hi Mike,
    Thanks for your reply. It is actually my intention to try out with the Services Registry for ES Workplace. The thing is, I was able to connect my NWDS to the SR, but not in Visual Composer.
    Below are the URLs for both destination.
    1. UDDI_DESTINATION: http://sr.esworkplace.sap.com/uddi/wsdl/uddi_v3_service.wsdl
    2. CLASSIFICATION_DESTINATION: http://sr.esworkplace.sap.com/ClassificationService/CS?wsdl
    I tried to open the first URL in my browser and a WSDL document was displayed, but for the second URL an error message "503 Service Unavailable" was returned.
    Does this mean that the second URL "http://sr.esworkplace.sap.com/ClassificationService/CS?wsdl" might be the cause of the problem?
    Regards,
    Joon Meng

  • 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

  • How to use the XSD that is registered in Oracle Service Registry.

    Hi,
    I got a requirement to publish a XSD in Oracle Service Registry and there after use the XSD from Service registry.
    I have done the following.
    --> Published the XSD in Oracle Service Registry.
    But do not know how to access the XSD, that is published in Oracle Service Registry.
    Pls someone throw some light on this.
    Regards
    Jude.

    Hello Shaveta,
    Thanks for the reply.
    I tried to find 'UDDI version 3 format’ tmodel key, but couldn't able to find it. Pls. provide any sample 'UDDI version 3 format’ tmodel key.
    I just tried with the existing tmodel key. Below is the modified WSDL. Here, I have modified schema location with the tmodel key. Pls note me, if I have gone wrong at any place or provide a sample WSDL.
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions name="AccessingRegistryXSD"
    targetNamespace="http://xmlns.oracle.com/AccessingRegistryXSD"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:client="http://xmlns.oracle.com/AccessingRegistryXSD"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
         <types>
              <schema xmlns="http://www.w3.org/2001/XMLSchema">
                   <import namespace="http://xmlns.oracle.com/AccessingRegistryXSD" schemaLocation="uddi:8d6511a0-cd6e-11dc-b81e-0f5150e1b81c" />
              </schema>
         </types>
    In BPEL, when tried to create copy operation for the input variables, it shows an exception "Exception - Bad URL encountered". Understood, gone wrong at some place. pls help.
    Regards
    Jude.

Maybe you are looking for