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).'.

Similar Messages

  • 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

  • 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

  • How to change the port in the URL of a BSP Iview

    Hello,
    we have several appraisal templates released in our R/3 system and we can access them by the portal.
    We are changing our systems and we are implementing a load balanced in order to improve the connections with the portal. So we need to know how can we change the port of the server that appears in the URL when we go to MSS ->teamviewer and select one appraisal to see the information of the template.
    We need to change it and indicate the port of the load balanced http://emsapl404pre.endesa.es:8000/sap/bc/bsp/sap/hap_document...) not the port of one of the WAS server as we have now http://emsapl404pre.endesa.es:8302/sap/bc/bsp/sap/hap_document...)
    Thanks in advanced.
    Best regards.
    Seshen

    Hi,
    Just view any BSP Application in SE80 and the click on Utilities(M)->Settings.
    This will fgive you option to change URL and port number of the URL..
    It will be under the Business server Pages tab in the settings window.
    Hope this helps.
    <b><i>Do reward each useful answer..!</i></b>
    Thanks,
    Tatvagna.

  • 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

  • Changing default port on deployed Web Service

    Hi,
    I have developed and deployed a Web service with HTTPS security level. When I check the generated WSDL, I get a correct URL. Bet when I analyse the content of the WSDL, all URLs are formed as:
    <import location="https://domain.fr:-1/..." />
    <address location="https://domain.fr:-1/..." />
    Why do I get the -1 port on all the WSDL's URLs ? How may I get rid of this ?
    Thanks in advance for your help/
    Thibault

    I don't believe that it's possible.  Do you have a mechanism to contact the app publisher?
    Also, please do not use the super-sized bolded font.  It's extremely annoying.

  • Importing the ES Bundle webservices into the Service Registry of PI

    Experts,
    We have an ECC 6.0 Enhancement Pack 3, PI 7.1, and CE 7.1 landscape and are having some trouble getting the Enterprise Web Services that come with EP3 to show up in the Service Registry that came with PI.
    We are following the guide "CE, ESR, AND DISCOVERY SYSTEM BUILDING AN END-TO-END ENTERPRISE SOA SCENARIO", https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/108ef7ba-8abd-2a10-f787-d5f29c5f1b88
    All of the references to CE we have been replacing with PI since we want to use the SR that came with PI instead of CE.
    We can get all the way up to step 6 in section 3.3 where it tells us to use LPCONFIG to create a logical port pointing to the Service Registry. We we run this tcode we get a message telling us to go to SOAMANAGER.  I found the following URL
    http://help.sap.com/saphelp_nwpi71/helpdata/en/44/cc8fd368c873dfe10000000a11466f/frameset.htm
    That describes how to do this however when we go into the NWA we do not see a 'Call Parameters' tab.
    Basically it looks like the process is as follows:
    1) On ECC 6.0, use Sm59 to create a RFC connection.
    2) On ECC 6.0, use WSPARAM to create a Enterprise Registry parameter
    3) From PI, launch SOAMANAGER to create a logical port
    4) ON ECC 6.0, use WSPUBLISH to select the webservices we want to show up in the Service Registry.
    Does this sound like the correct method?

    I should add, this is the error message that we are getting:
    SoapFaultCode:1  Cannot create implementation instance. Nested message:
    An exception occurred while obtaining UDDI Logical Ports. Please, check
    your c onfiguration settings (UDDI Endpoint or UDDI wsdl
    file)[_DestinationService Impl7000] Application or service
    service:tcesiesp~srv tried to access des tination UDDI_DESTINATION of
    type WSDestinationTemplate which does not curr ently exist in the
    destination service. You can create destinations in the NWA under
    Configuration Management->Infrastructure->Destinations..

  • Changing FTP Port in 10.3

    hi,
    i am searching everywhere on how to change the port of the ftp service built into OSX 10.3. but no luck on find anything.
    can someone please tell me how to change this port 20-21 to someting else such as 22-23.
    thanks.

    May I suggest searching in the standard Unix man pages when dealing with low-level services like ftp? "man ftpd" states:
    "ftpd is the Internet File Transfer Protocol server process. The server uses the TCP protocol and listens at the port specified in the ``ftp'' service specification; see services(5)."
    Thus, you would need to modify the /etc/services file to change the default port (21). As a side note, ftp is considered an unsafe service nowadays for secure file transfers - the recommended service is sftp, which is part of the secure shell package. If you need to use it for unauthenticated file transfers (aka "anonymous ftp"), following all the safety precautions stated on the same "man ftpd" is very important to keep your Mac from getting hacked.
    PowerBook G4 15/1.25GHz Mac OS X (10.3.9)

  • How to change the endpoint url of the siebel service ?

    Hi All,
    JDev : 11.1.1.5
    I am fetching data from the siebel webservice. I created the proxy client from the Siebel WSDL in the JDeveloper. It was working fine.
    Now the endpoint URL(Server) is changed. This service fails to connect to that server. The service name is same.
    I want to fetch the end point urls from a property file, so that, even again if the server is changed, i have to change it in my property file.
    How to change the End point URL at runtime before calling the service ?
    This is my endpoint URL.
    http://oa8181.us.oracle.com:10800/eai_enu/start.swe/#%7Bhttp%3A%2F%2Fpolicing.oracle.com%2F%7DPolicing_spcQuery_spcIncidents_spcWF?wsdl?SWEExtSource=WebService&SWEExtCmd=Execute&UserName=AUSTINP&Password=AUSTINP
    Now it is pointing to this
    http://oa8023.us.oracle.com:7777/eai_enu/start.swe/#%7Bhttp%3A%2F%2Fpolicing.oracle.com%2F%7DPolicing_spcQuery_spcIncidents_spcWF?wsdl?SWEExtSource=WebService&SWEExtCmd=Execute&UserName=AUSTINP&Password=AUSTINP
    Give me some solution.

    See if this helps:
    http://kingsfleet.blogspot.co.uk/2008/12/controlling-what-service-proxy-uses-at.html

  • Changing Endpoints on Service section of a published service (wsdl)

    Hi all,
    I'm working with a PI 7.1 System using SOAP adapter and configuring Web services. When I publish on to the SR from the Sender Agreement the generated WSDL keeps on the Service element two port elements with the corresponding web service locations; "http://<Server>:50000/XISOAPAdapter/..." and "https://<Server>:443/XISOAPAdapter/..."
    What do I need to do to change the port where de locations of the services are ubicated and WSDL keeps a location like "http://<Server>:50010/XISOAPAdapter/..." or any other port. Is this posible? It's there any configuration that I can do to change or add more target adress for publication to my services?
    Thanks for your help.

    Hi Jaun ,
    generated WSDL keeps on the Service element two port elements with the corresponding web service locations; "http://<Server>:50000/XISOAPAdapter/..." and "https://<Server>:443/XISOAPAdapter/..."
    while testing a soap scenario with soap UI tool, i also saw two endpoint urls for my wsdl request.I had selected http://<Server>:50000/XISOAPAdapter/ for posting as it works fine,no idea why second url came.
    can you try changing the endpoints in soamanager transaction in PI ,i guess here under web service administration ,there is a provision of editing the End points.
    In service registry ..if you go to test services there also it can be edited before posting ,but again its for testing only u can do in WS navigator page.
    Regards,
    srinivas

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

  • 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

  • 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

  • OWSM friendly service endpoint URL

    I am planning to use OWSM to ensure security requirements in my systems, but OWSM Gateway generates endpoint URL's as:
    http://<server>:<port>/gateway/services/SID000xxxx
    Is there some way to provide a more friendly endpoint URL to my protected services ?
    Thanks,
    Schiroky

    When you initially registered the service you also gave it a name. It can also be referred to by this name instead of the generated name. For example,
    http://<server>:<port>/gateway/services/myservice
    Which also has a generated id of:
    http://<server>:<port>/gateway/services/SID0003003

Maybe you are looking for