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

Similar Messages

  • 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

  • BAPI table input parameters for Visual Composer not working?

    I am using a BAPI with table input parameters (2 input fields for the table). I tested the BAPI in ecc function builder (it works as planned).  However, it doesn't work in Visual Composer using the same input values (not getting any error messages).  Is this a bug in VC 7.0?  Any help would be greatly appreciated.
    Edited by: Brent Crabb on Aug 29, 2008 8:12 PM

    Hi,
    The data service at a time  can execute only one input data.
    it will not handle too many inputs at time otherwise all the input ports should have same submit action then it is possible to Execute multiple input forms data .
    When you are mapping the input form and the dataservice ,give the same event like this *submit for both Inputforms
    Thanks,
    Govindu

  • Service Registry XSD dynamic reference not working

    Hi ,
    I have published an employee canonical schema to service registry. I have referenced it in my BPEL in my wsdl file as follows
    <schema xmlns="http://www.w3.org/2001/XMLSchema">
                   <import namespace="http://systinet.com/uddi/demo/employeeList" schemaLocation="employees.xsd" id="uddi:company:HR:EmployeeCanonical" />
              </schema>
    I have deployed the BPEL and is working fine. When I updated the service registry to point to the lastest version of canonical file , the BPEL is not reflecting to the new version. I have bounced both bpel server and reg. service but still no difference.
    please let me know how I can dynamically reference the xsd in service registry.
    appreciate your help.
    thanks
    Srini

    Hi
    I am having trouble making the BPEL and Systinet to work together. I have Systinet and BPEL installed separately on 2 different servers. I deployed my web services and registered them in UDDI. I created a new BPEL process and added a partner link to refer to one of the web service I have registered in UDDI. When I create the partner link, it is forcing me to give the wsdl and it also gives an error message " There are no partner link types defined in current wsdl. Do you want create that will by default create partner link type for you?". If I say "NO' then deployment fails. If I say "Yes", then it creates a new wsdl file on the local server etc and gives "<Faulthttp://schemas.xmlsoap.org/soap/envelope/>
    <faultcode>soapenv:Server.userException</faultcode>
    <faultstring>com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is 75164a0815ea471a:-3be8c246:117cc377894:-537b. Please check the process instance for detail.</faultstring>". Any help is appreciated.

  • Zero Fill and Upper Case in Visual Composer not working

    Hello,
    I am building my first VC application and hit a small wall from get go. When I create input fields and set text formats for one to have "Zero Fill" and for the other one "Upper Case" they do not seem to work properly.
    “Zero Fill” does not work at all. I set this format and also set max length as 10 to be used as input for customer account #. But it does not perform conversion. When I call a BAPI to get customer list, if I enter 0000000100 it works. When I enter 100 it does not work. Thus "Zero Fill" does not take effect.
    "Upper case" works but only after refresh. If I enter ac10 as company code and then click submit it does not work. However if after entering ac10 I press enter and then submit, it work.
    Does anyone have any info on how to deal with this? We are using VC 7.0
    Thanks,
    Alex

    Hi ALex,
    Now I got your problem. I suggest a solution for it.
    Go to the design board of VC.
    I think you have an Input Form that contains the input fields and the Submit button. There will be a link named "submit"between the Input Form & the Data Service(say BAPI). Click on the  submit link, you will get the Input Fields & Assigned values of the Input Form at the bottom right side. Go to the Assigned Value of the particular field & apply a formula like UPPER(@inputfield). So now whatever case you give in the inputfield, it is converted to UPPER case before Submiting the values.Keep the Upper Case option checked at the formatting tab of the Input field properties, this will help to display the value in Upper case.
    For eg, BAPI_BANK_GETLIST, the input fields are BANK_CTRY & MAX_ROWS.
    Make the assigned value of bank_ctry as UPPER(@BANK_CTRY), you can get this with the help of formula. 
    This will solve your problem.
    Regards,
    Shemim

  • Unable to connect to BI System from Visual Composer

    Hie there,
      I am unable to connect to my BI system from Visual Composer
      The error message which I obtain upon clicking on 'Find Data' and selecting one of the many Systems list are as follows :-
      Error - 30014 Search returned an erro Failed to conect to backend system. Check your system defination and user priveleges.
      Please advice how can I add a BI System to this Visual Composer
    p/s: I`m new to portal environment, hence please excuse my rudimentary question

    Hi John,
    you find some information under:
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/de/9b/3ac52d74cf4c43b1cf3a71725c951f/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/de/9b/3ac52d74cf4c43b1cf3a71725c951f/frameset.htm</a>
    I had a similar question as a comment for my blog here:
    <a href="/people/marcel.salein/blog/2007/02/01/visual-composer-and-abap-rfcbapi-a-powerful-combination-part-i:///people/marcel.salein/blog/2007/02/01/visual-composer-and-abap-rfcbapi-a-powerful-combination-part-i
    You should also look in the VC wiki, there is a section for the connectivity
    <a href="https://wiki.sdn.sap.com/wiki/display/VC/Connectivity">https://wiki.sdn.sap.com/wiki/display/VC/Connectivity</a>
    Hope that helps!
    Best Regards,
    Marcel

  • WSPUBLISH to Central Services Registry issue

    Hi Gurus,
    I am trying to publish a web service in the ERP6 backend to our central Services Registry (PI 7.1)
    when I do this in SOAMANAGER the page hangs (hangs on loading step)
    so i try to execute the publish using WSPUBLISH transaction code, and it is successful
    but checking on PI SR the service is not published,
    so i checked the log of the WSPUBLISH execution, and on this step:
    "Physical System was published successfully" i clicked on the display icon and it is showing
    300.SystemName.ERP.SystemNumber.0020600664.SystemHome.<ERP6_HOST>
    shouldn't it be that this should show the PI SR server e.g.   100.SystemName.PIX.SystemNumber.0020600664.SystemHome.<PIX_HOST>
    where PIX = my PI 7.1 server
    I have configured my PI SR as a Central Services Registry from http://help.sap.com/saphelp_nwpi71/helpdata/en/45/c1ea61a1194432e10000000a155369/frameset.htm
    I've already looked at Note 1319742
    Kindly advice

    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

  • Unable to consume Enterprise services from Visual Composer

    Hi,
    We have implemented ECC-SE 603 add-on in our ECC 6.0 system.
    We configured to set up a connection between our J2EE engine and the ES Workplace, to consume the Enterprise services from Visual Composer.
    But, we are unable to see the Enterprise Services in the Visual Composer.
    Kindly, let us know how to resolve this issue.

    Hi,
    please refer the following link
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a160392c-0e01-0010-7784-9cc564d871d2
    Regards
    Manohar

  • Connection Configuration to Central Services Registry in PI7.1

    Hi Freinds,
    while in CE7.1-
      NWA->Configuration Wizard-> I have this set up file Connection Configuration to Central Services Registry to configure the central service registry.
    while on PI7.1 EHP-1
    I dont have this setup file Connection Configuration to Central Services Registry.
    Is this included in Any Configuration service, or with different name?
    Regards
    chandra Dasari

    Hello Chandra
    See the link below.
    Configuring a Central Services Registry 
    http://help.sap.com/saphelp_nwpi71/helpdata/EN/46/bb923d06582710e10000000a11466f/content.htm
    Regards
    Mark

  • Missing "Connection Configuration to Central Services Registry" in Config Wizard in NWA

    Hi,
    When we trying to do the following operation [ by referring the document http://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=5&cad=rja&uact=8&ved=0CD8QFjAE&url=http%3A%2F%2Fdocencia.…]
    Configuration Management > Scenarios >
    Configuration Wizard > Start the Connection Configuration to Central Services Registry task in NWA for setting up the Service Registry, we don't see this task in the list.
    Can someone help me in starting this task ???
    Regards,
    Samba

    Hello Chandra
    See the link below.
    Configuring a Central Services Registry 
    http://help.sap.com/saphelp_nwpi71/helpdata/EN/46/bb923d06582710e10000000a11466f/content.htm
    Regards
    Mark

  • Connecting SAP NetWeaver BI System to Visual Composer via BICS

    Hy, i find on service.sap.com the possibility to connect SAP NetWeaver BI System with Visual Composer by BICS. What's BICS?and how can create this connection?
    Thank's a lot.
    Sincerely yours.
    Andrea Maraviglia

    Hi Neil,
    See https://www.sdn.sap.com/irj/sdn/downloaditem?rid=/library/uuid/6055f523-df6e-2910-f0bf-acccbb0a7d37 (troubleshooting guide): <b>Kernel dump while generating Web Services and Simple Transformation (XSLT) and problems when upgrading the NSP system from SP8 to SP9.</b>
    Download the patch (two files) and overwrite the existing ones with them - that solved the problem for me. This is a direct link to the zipfile:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/business_packages/a1-8-4/bugfixdbdriverfornspsystem.zip
    brgds
    Søren

  • Central service registry in PI 7.1 EHP1

    Hi,
    Like SLD , i think it is recommended to have one central service registry.
    So , we have followed a 2 SLD approach. one for Non prod which resides in DEV PI system and Prod SLD system which resides in Prod PI system.
    QA system connects to DEV SLD.
    Like wise , how do we change the service registry in QA system to point to Dev system ( Non Prod service registry).
    We would like to leave the registry in DEV and Prod to stay local as they serve as Non prod and prod regsitry respectively.
    Thanks,
    Tanuj

    Hi Tanuj,
    You can set this up in Netweaver Administrator of QA. Go to SOA Management, then Service Registry Configuration & then specify the Dev server details for the UDDI config.
    Regards, Trevor

  • 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

  • Creating web service system for Visual Composer

    Hello,
    I seem to have made some changes that made my unable to create web service systems for Visual Composer. 
    The change I made is in NetWeaver Administration > Configuration > Application Resources > WebServicesFactory, I added the Configuration Property "UseCacheByDefault" with Boolean value = true. 
    After this, if I create a web service system in Enterprise Portal, the Connection Tests fail.  In Visual Composer when I define a web service system, the error I am getting is: "Connector Factory not found for value WebServicesFactory".
    I have tried to delete the UseCacheByDefault property I added as well as restart the server but I am still getting the error.
    However when I test my web service using the Web Services Navigator, I am not getting any problems.  So my guess is the problem lies with the connection factory.
    Can anyone help me with this issue?
    Thanks.

    Hello,
    Since creating WS system in the portal resulted with failed connection test, the issue has nothing to do with VC.
    I'm just guessing, but try to configure proxy in the J2EE engine.
    If that doesn't help I suggest you raise this question in the portal forum.
    Best regards,
    Shay

  • 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.

Maybe you are looking for