Services Registry Endpoints in SLD

Hi,
I am working on CE 7.2 SP03. I have configured SLD, SLD Client and SLD Data Supplier.
Now I am trying to configure Service Registry using Configuration Wizard.
We have a drop down option to select the "Services Registry Endpoints in SLD" in which it shows only below option to select "http://[host]:[port]/ServicesRegistrySiService/ServicesRegistrySiPort" in the place of host and port number, it is supposed to show my host and port but it is not showing. Just it is showing as "http://[host]:[port]/ServicesRegistrySiService/ServicesRegistrySiPort".
Please advice.

Hi Patana,
I believe this question has nothing to do with NWDI, please post this question in
Service-Oriented Architecture (SOA) and SAP
Thank you!
Best Regards,
Ervin

Similar Messages

  • Problem with the cfg-wizard - Service Registry and SLD Client

    Hi,
    I try to complete the initial activity for configuring the Registering Services Registry instance in SLD (http:
    localhost:port\nwa\cfg-wizard)  but when i start the wizard i found this error:
    Error: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
    I don't know what is that error. Anyone can help us?
    regard.

    Hi ,
    I am facing an issue while running  SLD configuration wizard in SAp NW 7.3.
    Find the error message below.
    com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
    Can anyone guide on this issue.
    ~Viswanathan

  • Endpoints not published in Service Registry

    Hi all,
    I have published all the Enterprise services from the Discovery system(ECC) and they are available within the service registry.
    But somehow the endpoints are not published to the Service Registry because of which I am not able to consume the services for UI development in VC.
    I have the following concerns :
       1) The ES are being tested successfully but not being sure why the endpoints were not published when the Services were published from the Discovery System.
       2) Can we forcefully create the endpoints in the Service Registry. If so, plz let me know the procedure.
      3) SP13 is applied on Discovery System, so I am not able to execute TCode SOAMANAGER to create Endpoints, so is there any other alternative, other than upgrading ECC to SP14.
    Points will be rewarded for any help
    Regards Brian

    Hi Brian,
    Maybe the issue is wrt the Service Registry destination definition. The correct system name should be picked from the SLD system name (under http://host:port/sld) definition (I think it CE1 by default). You can also refer other issues I faced in a similar situation that i documented in thread [Endpoints not published in Service Registry;
    I take my earlier comment about using the Publish function in Service Registry. I learn it should be not be used.
    As regards the ServicesRegistrySi(Proxy Definition) URL, I guess you can use http://localhost:port/ServicesRegistrySiService/ServicesRegistrySiPort?wsdl&mode=sap_wsdl
    Regads
    Suresh

  • 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

  • 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

  • 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

  • Service Registry: why do i need two bindings (wsdlDeployment and endPoint)

    based on the technical note of Clemens Utschig "Enabling a Dynamic, Reusable SOA with Oracle BPEL Process Manager and Oracle Service Registry" i have one question:
    why do i need two bindings (wsdlDeployment and endPoint) in my service in the service registry. if i only define the wsdlDeployment if get this messages:
    <2006-12-07 09:39:02,559> <FATAL> <default.collaxa.cube.ws> no endpoint found - nothing to adjust
    <2006-12-07 09:39:02,559> <WARN> <default.collaxa.cube.ws> Could not lookup base endpoint!
    the problem of defining two bindings is that the url to my partner is redundant.

    Hi Clemens,
    The UDDI Version 3.0.2 Specification (http://www.uddi.org/pubs/uddi_v3.htm) say this:
    B.1.2 Using the "wsdlDeployment" value
    Instead of directly providing the network address in the accessPoint, it is occasionally useful or necessary to provide this information through indirect means. One common scenario for such a behavior is when the accessPoint is embedded within a WSDL file. In such a scenario, the UDDI accessPoint contains the address of the WSDL file, and the client then must retrieve the WSDL file and extract the end point address from the WSDL file itself.
    In this case, decorating the UDDI accessPoint with a useType="wsdlDeployment" is appropriate. A sample of such behavior is as follows:
    <bindingTemplate bindingKey="uddi:example.org:catalog">
       <description xml:lang="en">
           Browse catalog Web service
       </description>
       <accessPoint useType="wsdlDeployment">
           http://www.example.org/CatalogWebService/catalog.wsdl
       </accessPoint>
       <categoryBag>
           <keyedReference keyName="uddi-org:types:wsdl"
           keyValue="wsdlDeployment"
           tModelKey="uddi:uddi.org:categorization:types"/>
       </categoryBag>
    </bindingTemplate>In the example above, a client would be able to parse the result of the bindingTemplate and determine the end point of the Web service within the WSDL file discovered in the accessPoint element. Note that the bindingTemplate has also been categorized with the "wsdlDeployment" value from the uddi.org:categorization:types scheme so that it can be discovered through a find_binding API call.
    1) This means for me that providing one binding with useType=wsdlDeployment should be enough.
    2) Sadly the "Business Service Control" of the Service Registry (Publish new WSDL service) does not create the correct structure needed by the bpel-engine. The "Publish new WSDL service" wizard just creates one service with one binding with useType=other (http). So if i want to reuse this published service from bpel (as a service consumer) i have to switch to the "Service Registry Admin Control" and create a second binding with useType=wsdlDeployment. But i don't want the developers to get inside the "Service Registry Admin Control"! They should only work with the "Business Service Control".
    All this makes the usage of the service-registry very unhandy and reduce the acceptance for developers because of unnecessary manual steps and broken security principles.
    My wish for this issue is that the "Publish new WSDL service" inside the "Business Service Control" of the Service Registry would additionlly create this needed binding with useType=wsdlDeployment.
    Best Regards,
    Harald Reinmueller

  • WSDL without endpoint in Services Registry

    Hi,
    I have successfully configured an enterprise service from ECC 6.0 by following this tutorial ([Configuration of Enterprise Services using SICF and SOAMANAGER|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/20b723f8-a422-2c10-aca5-fe64eeda1ff2&overridelayout=true]). After the configuration, I published the enterprise service to the Services Registry using WSPUBLISH.
    However, when I tried to consume the service in Visual Composer, I got a connection error. Later, I discovered that it was due to the binding WSDL generated in SOAMANAGER in which the endpoint port was automatically set to 443 instead of 8001 (my http port). Luckily enough, I have found an identical problem posted to SDN forum ([soamanager referencing wrong port number in wsdl document |soamanager referencing wrong port number in wsdl document;). From there I learned that an SAPNOTE 1263112 must be uploaded to my ERP. Now, this problem is solved.
    Nevertheless, after I have built a VC model that consumes the service, which is now found in the Services Registry, deployed and run it, I got this error message "Error in connection: Could not execute Web service, consult your administrator". To investigate the source of the problem, I copied the URL of the WSDL generated in SOAMANAGER from the link Open WSDL document for selected binding and created a logical destination in NWA for the direct consumption in VC. This time, the VC model worked!
    This lead me to think that the problem lies in the binding WSDL in Services Registry. So, I checked the SR again and found that the URL for the binding WSDL in the "Endpoint" tab is different from the one in SOAMANAGER:
    1. In SR
    http://myserver:8001/sap/bc/srt/wsdl/bndg_4AAD0B64E0BC0263E1008000C0A8A53D/wsdl11/binding/ws_policy/document?sap-client=800
    2. In SOAMANAGER
    http://myserver:8001/sap/bc/srt/wsdl/bndg_4AAD0B64E0BC0263E1008000C0A8A53D/wsdl11/allinone/ws_policy/document?sap-client=800
    The binding WSDL in SR does not contain the endpoint. However, the endpoint is shown in the 2nd column "Target Address" of the endpoint table in "Endpoint" tab.
    To summarize, I could not consume service that was configured in SOAMANAGER and subsequently published to SR. But, with the WSDL in SOAMANAGER, the service could be directly consumed.
    Does anyone have idea about this problem?
    Thanks in advance.
    Regards,
    Joon Meng

    Hi,
    Usually endpoint in SR is published as per SOAMANAGER (allinone/ws_policy/document?sap-client=800). Try to republish service again using "WSPUBLISH" with endpoint and chose "force publication" option.
    You can also publish service using url directly from SR (goto "publish" tab).
    Regards,
    Gourav

  • Change standard port in Endpoint URL Services registry

    Hello all,
    I am trying to publish a Service Interface into the Services Registry from a Sender Agreement. This works fine. Default this is done with port 50000. I would like to have a standard value of port 80 there so I do not have to change this by hand each time i publish a service.
    I already have tried HTTP Mapping in the NWA but I do not see the endpoint published with port 80 in the Services Registry.
    Has anyone an idea of how to change this value?
    Best regards,
    Fons van Nuland

    here is the error from .net
    The document at the url
    http://XXXX:8002/sap/bc/srt/wsdl/bndg_DEEFA40807E3B8F1948E00215E56BC34/wsdl11/allinone/standard/document?sap-client=100 was not recognized as a known document type.
    The error message from each known type may help you fix the problem:
    - Report from 'WSDL Document' is 'There is an error in XML document (1, 500).'.
       - 'Element' is an invalid node type. Line 1, position 500.
    - Report from 'DISCO Document' is 'Discovery document at the URL http://XXXX::8002/sap/bc/srt/wsdl/bndg_DEEFA40807E3B8F1948E00215E56BC34/wsdl11/allinone/standard/document?sap-client=100 could not be found.'.
       - The document format is not recognized.
    - Report from 'XML Schema' is 'Expected Schema root. Make sure that the root element is <schema> and the namespace is 'http://www.w3.org/2001/XMLSchema' for an XSD schema or 'urn:schemas-microsoft-com:xml-data' for an XDR schema. An error occurred at , (1, 40).'.

  • Problems with discovering services from Service Registry in VC and NWDS

    Hello,
    I have followed step 1 "Brokered Service implemented in own system" in blog
    http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414900)ID1803376250DB00062216078043496017End?blog=/pub/wlg/8788
    in order to publish  a service from PI to the Services Registry (SR).
    It works fine and I can find the service in the SR and also test it successfully.
    However I can't discover the service from within Visual Composer or NWDS.
    I succeed in discovering standard SAP Enterprise Services from VC and NWDS.
    I'm working on CE 7.1 EHP 1 and PI 7.1 EHP 1.
    Does anyone know what the problem could be?
    // Best regards  Hans

    Hello Hans,
    Sorry, may be I should have been more specific.
    First, I want to verify that you're using at least Ehp1 SP2.
    The information that I need is the complete system details:
    Name, Host, SLD System ID, Type, ABAP Client.
    In addition, please reverify that you have a valid link to the endpoint.
    Only if you're using a version Ehp1 SP2 onwards, here are the seetings that you should fill:
    1. Open NWA>'SOA Managment'>'Application and Scenario Communication'
    2. Press on 'Single Service Administration' link
    3. Press on 'Customer Proxies' tab
    4. In the 'find' text box select for 'sr' and press on 'Go' button
    5. Select the 'ServicesRegistrySi' (This is the proxy to the Services Registry backend)
    6. Press on 'Configuration' tab
    7. Select the 'ServicesRegistrySiPort' (If it's the only result it will be marked by default)
    8. Press on the 'Edit' button and insert your SR URL
       (for example: http://sr.esworkplace.sap.com:80/ServicesRegistrySiService/ServicesRegistrySiPort)
    9. Press on the 'Security' tab and insert the requried authentication if needed
       In this example it will be:
       username: <your user namr>
       password: <your password>
    10. Save this configuration
    11. Defined proxy (if needed): NWA>'SOA Managment'>'Technical Configuration'
    12. Press on 'SOA Middleware Global settings and type the proxy's settings
    12. Save settins
    14. Now you can work with Service Registry in VC (server)
    In case you're using a lower version than Ehp1 SP2, please use the following link to configure your system:
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e058a805-68b2-2b10-6a8b-fc570f1c37d1&overridelayout=true
    BR,
    Hezi.

  • Services Registry in PI 7.1 - What is this and where is it used?

    Hi,
    Can anyone tell me what is Services Registry in PI 7.1 ? What featuers are available in it and where is it used or how its helpful?
    I dont have access to it in my system, so am curious to know the contents of it!!
    Do we define global data types by any chance in the Services Registry ?
    Cheers,
    S

    Hi,
    What is Service Registry?
    Definition: Service Registry is a registry for Webservices that is located centrally within an SOA landscape.  In simple words u201Cwhere are our services implemented?u201D can be identified by using Service Registry.
    PI 7.1 contains a UDDI v.3 compliant Service Registry contains information about services provided in that landscape with references to the WSDL metadata relevant for those services and to the locations of the callable service endpoints.
    How the Service Registry used in PI?
    1.     As a Webservice provider we can publish Webservice.
    2.     As a Webservice consumer we can search for and find Webservices for consumption.
    3.     We can test our Webservices.
    4.     Manage third party Webservices and classify them to provide them for consumption in our system landscape.
    5.     Providing Deployment information (i.e End point information).
    Enterprise Services Repository (ESR):
    To support strategic service oriented approach SAP provides a new Enterprise Service Repository. ESR is a central repository of information that contains all the services. ESR is a container, stores all the underlying Meta data of application objects like service interfaces and descriptions. The global data types, interfaces and business processes maintained in Enterprise service repository which can be reuse where needed. The first implementation of ESR and its associated editors come in SAP Netweaver04u2019s, which has been evolved from NetWeaver Exchange Infrastructure Integration Repository. Enterprise service repository is a design time repository of service objects for ESA. You can model all service design objects for a process and can reuse the data types and service objects which are already maintained. All enterprise services are published in a central Enterprise service repository so they can be used by anybody who really needs that service includes customers and partners.
    The Enterprise Service Repository is the evolution of what it was known as the Integration Repository in XI.  Now the Integration Repository is called the ESR and XI is called PI.  Using the Integration Repository as foundation for the ESR made a lot of sense since many of the capabilities were already there: metadata storage, defining message types, data types, operations, etc.
         ESR is just like Integration Repository for XI.  Here you can design/define your Service Interfaces and Enterprise Services.
         ESR is the central repository in which Service Interfaces and Enterprise Services are modeled centrally and their metadata is stored.
         In simple words u201CWhat does the service do and what does it need?u201D can be answered from ESR.
         ESR is used for: -
    1.     Definition of Processes and Services
    2.     Store Service Metadata
    3.     Central Modeling and Design Environment.
    Global Data Types
         Definition: Global Data Types are company-wide, defined data types based on international standards.  They are based on the SAP methodology and are defined in a standards-based way in the ESR.
         They are based on the ISO 15000-5 and UN/CEFACT CCTS standards and act as the semantic building blocks for service interfaces.
         Global Data Types help you in standardizing service definitions across your organization and provide the key building blocks that can be reused across all your service definitions.
         Global Data Types have been approved SAP-wide by the Governance Process for Business Content.
         Global Data Types have been defined in the ESR and are described by XML schema.
    Thanks,
    Satya Kumar

  • 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

  • Service Registry in PI 7.1 .. cannot connect from VC 7.1 on CE

    Hello
    I am trying to access PI 7.1 Service Registry which maintains Services published on ECC centrally. VC is used as access tool which is installed on CE7.1. I have changed the Destination Templates  UDDI_DESTINATION, CLASSIFICATION_DESTINATION to point to PI7.1 server
    also I have created another destination SID with type Services Registry to PI 7.1.
    Also changed the ServicesRegistrySIPort to point to PI 7.1 server instead of localhost and adjusted the port aswell.
    But I cannot get any Services in VC, does not find any where are there are many published and could be viewed in the WSnavigator on CE7.1.
    Any ideas or suggestions?
    regards
    Mustafa

    Hi,
    Please verify in the SR configuration that the port types that were published have a physical system defined, and that system has an SLD ID.
    VC can only work with physical systems containing an SLD ID
    Best Regards,
    Ran

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

  • How to "Manually" publish WCF service in Service Registry

    Since WCF service publication is not yet supported by ES Explorer for .NET, will someone know me how to do that in SAP NetWeaver CE 7.1.
    I did the following:
    Services Registry->Publish and picked up the WSDL from WCF, and pressed the Publish button.
    Now when I go to "Service Definition" tab, and put service interface name in Find dialog box, the service appears in "Found Service Definitions:.." list, and can see details in "General" and "Endpoints" tabs in the bottom.
    However, the "Classifications" and "System Details"  tab don't show anything since I just imported the standard WSDL from WCF without any SAP specific extesions.
    Can I somehow manually edit them, and classify my service, since I could not do that from the ES Explorer tool?
    Edited by: Fakher Halim on Dec 9, 2008 11:49 AM

    Rima,
    I only have publish button on my CE page. I an using  SAP NetWeaver    CE 7.1 SR5. It does not have a "Next" button on its web page. However, I could successfully do the classification of this service.
    Here is what I am doing:
    1. Going to the first page http://LOCALHOST:50000/index.html. Here I have 8 options, e.g. "Web Services Navigator"; "SAP NetWeaver   Administrator"; and "Services Registry".
    I  click on    "Services Registry".
    A new browser window opens. (I can also do the same by directly navigating to http://LOCALHOST:50000/sr and logging on).
    2. The title of this page is "Services Registry".
    I click on "Publish" Tab, and see "Publish Services" page underneath it. On this page I just have a single text box with accompanied label "Endpoint WSDL: " and a single yellow button "Publish"
    3. When I copy paste my service WSDL, the only button I can press is "Publish" .
    After pressing that button, and waiting for a few seconds a green checkbox appears with message indicating that service is successfully published. I never see the "Next" button you mentioned in your solution.
    Can you please guide me on that?

Maybe you are looking for