Change in the namespace of the Client proxy?

Hi All,
   I want to know if there is way to change the name space in an existing client proxy. The problem is the provider system is not fully set up yet. So the provider keeps changing the URL to the web services. What is the best way to handle such a situation ?
Do I need to re-create the proxy each time the namespace is changed or just the regeneration of the proxy is enough? In either case I believe WSDL file should be updated. Please guide me...
Edited by: varaprasad bhagavatula on Apr 20, 2010 7:03 PM

changing URL of endpoint(webservice) won't affect your proxy but changing namespace will affect (there is difference between namespace and endpoint url),
1. If URL is changing then there is no need to create proxy again but change configuration part in SOAMANAGER.
2. If namespace is changed then you need to create proxy again.

Similar Messages

  • How to change the Namespace of the payload

    I have 2 questions about the namespace of the XML Payload.
    1. How can I change the Namespace Prefix?
    Since we have SP13 the prefix is <b>p2</b> with the previous Versions the prefix was <b>p1</b> or <b>p0</b> . Is there a possibility to change this prefix (without an external XSLT or Java Mapping)?
    2. How can I change the whole Namespace?
    I know the function of the Message-Type to change the namespace of the Message. But in one scenario I have to implement 3 namespace statements and 1 schema location
    <b><ns0:ZMCFAUF1 xmlns:ns0="TDB" xmlns:xdb="" xmlns:xsi="" xsi:schemaLocation="TDB zmcfauf1.xsd"></b>
    Is there a possibility to implement this without an external Mapping?
    Thank you for your help

    Hi Thomas,
    according to your first question: Why does this matter to you? As I already wrote in another thread:
    According to the XML namespace declaration the prefixes are just internal aliases with no external meaning.
    E.g. <ns1:abc xmlns:ns1="" /> and
    <iLikeLongPrefixes:abc xmlns:iLikeLongPrefixes ="" /> are totally equivalent according to the XML namespace specification.
    Therefore, everyone (human or machine) who produces a program can choose the prefixes as he wants. Moreover, he may change the rules for creating these prefixes without being incompatible.
    Consequently, the namespace prefixes should not be important for you.

  • [svn:osmf:] 14357: Moved constants for namespace ( also added a version number to the namespace) and the metadata key to the MASTPluginInfo class so these constants can be used from player code .

    Revision: 14357
    Revision: 14357
    Author:   [email protected]
    Date:     2010-02-23 09:41:57 -0800 (Tue, 23 Feb 2010)
    Log Message:
    Moved constants for namespace (also added a version number to the namespace) and the metadata key to the MASTPluginInfo class so these constants can be used from player code.
    Modified Paths:

    Revision: 14357
    Revision: 14357
    Author:   [email protected]
    Date:     2010-02-23 09:41:57 -0800 (Tue, 23 Feb 2010)
    Log Message:
    Moved constants for namespace (also added a version number to the namespace) and the metadata key to the MASTPluginInfo class so these constants can be used from player code.
    Modified Paths:

  • Unknown Namespace when creating Client Proxy

    I'm trying to generate a client proxy using Local File.
    It gives error
    Incorrect value: Unknown Namespace urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2
    The wsdl file does not give any error.
    This error seems to be coming from XSD file  named UBL-CommonAggregateComponents-2.0.xsd
    Below is part of this XSD file.
    Can you tell me what is the problem here.
    <!-- ===== xsd:schema Element With Namespaces Declarations ===== --><xsd:schema xmlns:xsd=""
                version="2.0"><!-- ===== Imports ===== --><xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
       <xsd:import namespace="urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2"
       <xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:QualifiedDatatypes-2"

    Hi ,
    Make sure no restriction from firewall on proxy settings.
    Namespace you are using for client proxy may not be available for consumption/not published.
    Also , Try to check connection.
    OSS note 944029 will give you SAP restrictions on name space.

  • Problem with the namespace in the soap message ' xmlns:p1'

    I have released a WSDL file which the siebel system is consuming to send the data to SAP XI .
    the extract of the WSDL file is as below
    <b><?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions name="MI_Customer" targetNamespace="" xmlns:p1="" xmlns:wsdl=""><wsdl:types><xsd:schema targetNamespace="" xmlns="" xmlns:xsd=""><xsd:element name="MT_Customer" </b>
    if we see in the there is a attribute called xmlns:p1 which is creaing the problem as data sent is as below
    <b>  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
    - <MT_Customer xmlns="" xmlns:xsd="" xmlns:SOAP-ENV="" xmlns:xsi="">
    - <Customer>
    due to this the XI system is not triggring the mapping.
    as XI expects the data in the below format which we generated with the stylus studio tool
    <b> <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
    - <p1:MT_Customer xmlns:p1="" xmlns:SOAP-ENV="">
    - <Customer>
    If anyone has any Idea as to how can we overcome this problem

    just a thought..... did u try removing xmlns:p1="" from your WSDL file ?
    Try to remove that and proceed in your development.

  • Changing the namespace prefix in OSB body content

    I would like to change the namespace prefix of the namespace in the content of the Body in OSB (Replacing g: with dg:)
    For example:
    should become
    Any idea how can I do this?

    Re: Namespace replace/rename issue in ALSB

  • Regarding Changing the Namespace And Data Type in XSD File

    Hi All,
    I am Doing File -
    IDOC Interface.
    I have XSD File For File Sysyetm and IDOC For ECC.
    In XSD File I Have Different Name Space And Data Type ,
    I Created the Data Type as Same as the XSD File Data type
    I Have Namespaces Are Different,
    So,I Changed the Namespace in the XSD File with the New Namespace Which I created in IR.
    I Changed in Two Places Like this
    <b><xsd:schema targetNamespace=";" xmlns=";"</b>
    But it is giving Error lik this
    <b>Cannot load schema with the target namespace to namespace;</b>

    Hi Vasanth,
    Thats what I am Asking
    I want to Import XSD File in Data Type
    Before I Import the XSD File into Data type  I changed the Namespace in the XSD to My Namespace Which is in IR. And I Created the Data Type Name in IR Which I Have in XSD FIle .
    So I Am Getting this Error
    Please Let me Know Wat to do

  • What is the Difference Between Adapter and Proxy

    Hi Master,
    I want to know the Difference Between Adapters and Proxies.
    And when we are using proxies and Adapters....

    Adapters are part of the Adapter Framework. Adapters provide the technical connectivity to enable the integration of SAP and non-SAP applications through XI’s Integration Engine.Again, Adapters are used for connectivity from and to external systems with XI that cannot communicate via proxies.Adapters are only required in SAP systems older than 6.20 and external systems.
    Systems based on 6.20or higher can communicate directly with proxies.
    The literal definition of a proxy is an object / process authorized to act for another; an agent or a substitute. In simpler terms, proxies in the XI context are objects used to encapsulate the creation (from a sender system) or parsing of XML (at a receiver system) as well as the communication with the relevant runtime components required to send or receive those messages.
    Proxies are generated from Message Interface in IR.
    The Proxy Runtime controls these objects / processes, and can itself be controlled by the applications it communicates with. The Proxy Runtime currently has the following components available: 1. ABAP Proxy Runtime – Communication using XI or Web Services a. Web Service Runtime 2. Java Proxy Runtime – Communication using XI (J2EE) The objects that the Proxy Runtime then controls are created via Proxy Generation, for both ABAP and Java. In the following sections a ‘client’ proxy is used by an application to send messages outside of the system it resides in (normally to the IS in this context). Conversely, a ‘server’ proxy is used by an application to receive messages from sources outside itself (again, normally the IS in this context).

  • Missing Namespace with the SOAP msg sent by C#

    Hi All,
    The wsdl file is generated by SAP XI. I used the XMLSpy to test it and get successful response.
    Then I used wsdl.exe of .net 2.0 sdk to generate the C# proxy class, and use csc.exe to compile it to a dll, and then refer it in the project. After sent the soap message by C#, the XI shows the message is wrong, then I compare this soap envelop body with the one I sent by the XMLSpy as follow:
    <MT_PP_014_PrdOrderGoodsRcv xmlns="">
    <m:MT_PP_014_PrdOrderGoodsRcv xmlns:m="">
    so it is the namespace, according the xml generated by C#, the MT_PP_014_PrdOrderGoodsRcv element isn't inlucded in the namespace, which cause the error.
    Anyone know how to fix it?
    Thanks and B'Rgds,

    Hi YiNing,
    the message created by C# is indeed wrong.
    Check that in XMLSpy message, the default namespace is never set and that the message namespace is set to prefix "m" and that only the root tag is included in this namespace. All the other tags have no namespace (since they are not attached to any namespace prefix) or have the default namespace, which was not set.
    On the other hand, in the C# message, the default namespace is set in the root tag. The root tag is related to the default namespace (it has no prefix) and hence it has the proper namespace. However, the other tags are also related to the default namespace (no namespace prefix) which was set. So these other tags are the erroneous ones.
    Try to check that in your proxy, but it seems like a bug in the proxy generator application.
    Just as a test, send the message from C# in a request from XMLSpy (replace the automatically generated message inside SOAP Body). The same error would be expected.
    Also as a test, send this message in XMLSpy:
    <MT_PP_014_PrdOrderGoodsRcv xmlns="">
    <content xmlns="">

  • Using namespaces in the XML QUERY

    I need to included a namespace of i: in the query below.
    the namespace is : ""
    How can I include the namespace in the query below?
    Is this possible?
    SELECT XMLELEMENT("i:Trade", XMLELEMENT("i:Level",2.25),
                                 XMLELEMENT("i:Style", 250),
                    FROM DUAL

    What's wrong with Sundars answer in this Writing a Procedure to return back XML. Please help.?

  • Problem in the Namespace

    Hi All,
           I am trying to upload an xml file. but while uploading the file in the External Definition, there i am not getting any message nor the namespace in the MESSAGE tab.
    The url which i am is using is like for Ex::( "") .
      But when i am using some other url or when i am truncating the url also i am getting it right,
      Now the problem is i have to use this url only.
         So if anyone can let me know how can i do this. Or how can i increase the namespace length.
    or if there is any other way out then please let me know .

    XI namespace has a limit of 60 character. And the namespace has more than 60 chars.
    U cant increase the limit. So better to use some other namespace.

  • Can we define a namespace in the B2B for the XML which generates for EDI

    Hi All,
    I have defined an EDI 856 document which is a inbound. When I give a input EDI message the translation happens and it generates an XML message. So, in the XML message that is generated it gives me a junk namespace.
    <Transaction-856 xmlns="NS_31CA8D0F33324F95A0BF15D85539C27E20081212182610" xmlns:xsi="" XDataVersion="1.0" Standard="X12" Version="V5020" CreatedDate="2009-01-06T15:56:35" CreatedBy="ECXEngine_837" GUID="{C0F6BEDD-356C-41BA-A89F-775061F2EFAF}">
    So, is there a way in B2B where we could give the namespace of my choice .And that namespace would be generated in the XML File.
    Thanks in advance.

    Hi Dheeraj,
    The XSD which i am using already has the namespace in the format which you mentioned.
    Ex:-<xsd:schema xmlns="urn:oracle:integration:b2b:DCC1FCD2811C47748DF43A39F735F4F0" targetNamespace="urn:oracle:integration:b2b:DCC1FCD2811C47748DF43A39F735F4F0" xmlns:xsd="" version="1.0" elementFormDefault="qualified">
    But still, while generating the XML file it gives the junk namespace.

  • Error while creating a client proxy for CBR.RU

    I need to consume web service. Here is the link:
    I tried to make an own client proxy with SE80 transaction. (edit object->enterprise services -> client proxy -> create) After completing wizard an error occurs with text:
    Incorrect value: Unknown Namespace
    The same schema works perfecrly with this web service:
    In this case proxy class is created with no errors and everything is fine.
    Could anybody let me know what's the reason of such bug, please? I'm not competent with XML schemas so it's kind of difficult to understand what's wrong with WSDL file from CBR.RU

    Late response I know, but I have solved a similar problem recently and thought I would share.
    Firstly, the problem is not with the namespace. The "Namespace ..." part is just stating the namespace the "Incorrect Value" has. So this error is complaining about the value "Unknown" - which isn't very helpful.
    It appears the SAP SE80 importer does not like elements like the following because it can't understand <s:element ref="s:schema" />. It appears this is a common thing to be included in .NET generated WSDLs.
     <s:element minOccurs="0" maxOccurs="1" name="GetCursDynamicResult">      <s:complexType>          <s:sequence>               <s:element ref="s:schema" />               <s:any />          </s:sequence>     </s:complexType></s:element> 
    SAP will also not like this example as it does not support mixed content (see:
    <s:element minOccurs="0" maxOccurs="1" name="SaldoXMLResult">
         <s:complexType mixed="true">
                   <s:any />
    You can "Fix" the problem in both cases by removing the offending text in a local copy of the WSDL file so remove line 4 in the first example and change line 2 in the second to <s:complexType> the proxy can then be generated. No idea if the resulting service will be fully operational though!

  • Client proxy to file(xml) scenario configuration

    I have done client proxy to file (xml) ,while executing abap code there is no error, but xml msg is not received in particular target directory. so i want to know about 1. What are the configuration required for client proxy to pi(with T.Code).
                                                  to monitor client proxy in ecc and pi.
    please reply me

    1. What are the configuration required for client proxy to pi(with T.Code).
    1.       Create a HTTP connection in the business system using transaction SM59
    Technical Setting & Logon Security details:
    u2022         Connection Type: H
    u2022         Target Host: System name
    u2022         Service Number: HTTP Port name
    u2022         Path Prefix:
    2.       Configuration Business system as local Integration Engine.
    1.       Go to Transaction SXMB_ADM
    2.       Choose Edit --> Change Global Configuration Data.
    3.       Select Role of Business System: Application system
    check maintain SLD Access data / not by using T.C  SLDAPICUST
    SLDAPICUST->check  XI Server is it activate/not
    4.test LCR Connection by using SLDCHECK. to monitor client proxy in ecc .
    trigger the report by using T.c se38 and check the status in SXMB_MONI in ECC.
    Edited by: bhavanisankar.solasu on Feb 13, 2012 11:09 AM

  • Unable to invoke ADFBC based ws using client proxy

    I created a custom am method and exposed it as a webservice and deployed it to my integrated wls.
    Then i generated the client proxy specifying the wsdl running at localhost.
    now when i am trying to call the service method from client proxy i get following exception. Not sure how to resolve..please advise.. java.lang.IllegalArgumentException: prefix ns1 is not bound to a namespace
         at $Proxy43.storePost(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(
         at java.lang.reflect.Method.invoke(
         at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(
         at $Proxy44.storePost(Unknown Source)
         at oracle.apps.crm.smm.view.service.proxy.SmmAMServiceSoapHttpPortClient.main(
    Caused by: java.lang.IllegalArgumentException: prefix ns1 is not bound to a namespace
         at com.sun.xml.bind.DatatypeConverterImpl._parseQName(
         at com.sun.xml.bind.v2.runtime.unmarshaller.XsiTypeLoader.parseXsiType(
         at com.sun.xml.bind.v2.runtime.unmarshaller.XsiTypeLoader.startElement(
         at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext._startElement(
         at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.startElement(
         at com.sun.xml.bind.v2.runtime.unmarshaller.InterningXmlVisitor.startElement(
         at com.sun.xml.bind.v2.runtime.unmarshaller.SAXConnector.startElement(

    Hi Bora,
    I guess that you are having a username/password for directory manager on OUD proxy (let's say cn=proxymgr / proxypwd), and another username/password for directory manager your ODSEE servers (let's say cn=odseemgr / odseepwd).
    When you connect to OUD proxy using cn=proxymgr to perform a search on your backend, OUD proxy creates a connection to the ODSEE backend with the same credentials (because the proxy is configured in use-client-identity mode), i.e. cn=proxymgr / proxypwd. If this user does not exist on ODSEE (or has the same name with a different password), you get an error 49.
    To avoid this issue, OUD proxy offers configuration parameters in the proxy-workflow-element: the exclude-list and remote-ldap-server-bind-dn / remote-ldap-server-bind-password. You have to add cn=proxymgr to the exclude-list, and set remote-ldap-server-bind-dn to cn=odseemgr, remote-ldap-server-bind-password to odseepwd.
    This way, when connecting with cn=proxymgr, the proxy will know that he should not use the client credentials, but rather cn=odseemgr when discussing with ODSEE backend.
    This concept is explained in OUD admin guide, Configuring the Bind Mode.

Maybe you are looking for

  • MSI 865PE Neo2 and USB WD (MY BOOK) external HDD

    Ok, so recently i went out an brought a My Book. I plugged it in and formatted it.. Next morning i came out turned of my PC and the computer hung during POST. after a few attempts at booting the PC up, i unplugged the MY BOOK from the USB port and re

  • Navigation Using Script?

    Hi all, I'm looking for advice on how the experts do this kind of thing. (Link below) The text navigation next to the guy in the middle of the flash piece has a nice bounce to it (both the text and the arrow glow). I can create this using a movie in

  • Reinstalling Safari on OS 10.5.8

    Hi Everyone, A while back I deleted my Safari program as I opted to use Firefox instead.  Now I have discovered that it may be a better browser to access certain webinars I need to participate in.  I have tried to download a version appropriate for m

  • 10.2 companion CD

    This CD includes 1.6 version of ApEx. What is the right order of staps to get 2.2 installed on a 10.2 data base? 1. install HTTP server from the companion CD - installing this option will not create marvel directory within the new apex home - this op

  • HT4972 Why 2nd generation IPod Touch is not allowed to update with newer IOS?

    Why 2nd generation ipod touch not allowed to update its OS to IOS 5 or later? This limitation made that IPod more or less useless as updated apps cannot be installed.