External definitions problem

hi experts, i have wsdl file, i upload it to xi as external definition but there are no any messages in "messages" tab.
i tried to generate some requests using Altova xm spy so it works fine, in XI it is not.
Help pls.

Hi,
Are you able to deploy the External definition without any issues?
If you have deployed it, then go to the WSDL tab in the external definition and check.
If you are able to successfully deploy it, then create Message interface and check the Context objects, you would be able to see the structure.
If you are not able to see the messages then there should be some issue with the WSDL.
Thanks,

Similar Messages

  • "Messages" problem after importing .xsd file as external definition

    Hello,
    I received an .xsd file from a customer and need to import it as an "External Definition" in order to create the "Message Interface". The structure of the xsd looks like this:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:px="http://www.opentrans.org/XMLSchema/1.0" targetNamespace="http://www.opentrans.org/XMLSchema/1.0" elementFormDefault="qualified">
    <xsd:element name="ORDER">
    </xsd:element>
    <xsd:element name="ADDRESS">
    </xsd:element>
    <xsd:element name="ARTICLE_ID">
    </xsd:element>
    </xsd:schema>
    After importing and looking at the tab "Messages" I get numerous entries, for each <xsd:element> I get one message! But I basically only need one "Message" that holds my complete xsd-file.
    I tried inserting <xsd:element name="COMPLETEORDER"> right after the <xsd:schema>-Tag but that didn't work either. Somehow I need to sum up all the <xsd:elements>.
    Does anyone have an idea? Thank you very much!
    Peter

    Hello Prateek, Hello everyone,
    I now know what the problem is. I downloaded XMLspy and checked on the structure:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:px="http://www.opentrans.org/XMLSchema/1.0" targetNamespace="http://www.opentrans.org/XMLSchema/1.0" elementFormDefault="qualified">
    <xsd:element name="ORDER">
    </xsd:element>
    <xsd:element name="ADDRESS">
    </xsd:element>
    <xsd:element name="ARTICLE_ID">
    </xsd:element>
    <xsd:simpleType name="dtBOOLEAN">
    </xsd:simpleType>
    <xsd:simpleType name="dtCOUNTRIES">
    </xsd:simpleType>
    <xsd:element name="SUPPLIER_AID">
    </xsd:element>
    <xsd:simpleType name="typeSUPPLIER_AID">
    </xsd:simpleType>
    </xsd:schema>
    Between the long list of <xsd:element> tags there are some simpleTypes on the same
    level. Now if I insert
    <xsd:element name="COMPLETEORDER">
    <xsd:complexType>
    <xsd:sequence>
    on top, the <xsd:sequence> would be on the same level as the simpleTypes - which is not valid!
    But can I just move all the simpleTypes, e.g. into an <xsd:element>??
    That would be changing the customer's structure which I think is not a good thing!?
    Thank you again for your help! I really appreciate it!
    Best regards,
    Peter

  • Problem Loading WSDL in External Definition

    Hello people,
    i'm having some problems When i'm Importing the WSDL in external definitions, the Messages are not being Recognized, it doesnt load the message structures, if i try in any other program that uses the WSDL like SoapUI, the wsdl works fine.
    Here is the WSDL links
    http://siatepqa.suseso.cl:8888/Siatep/WSToken?wsdl
    http://siatepqa.suseso.cl:8888/Siatep/WSIngreso?wsdl
    http://siatep.suseso.cl:8888/SusesoSiatep/WSToken?wsdl
    http://siatep.suseso.cl:8888/SusesoSiatep/WSIngreso?wsdl
    anyone can help?

    Hi,
    http://siatepqa.suseso.cl:8888/Siatep/WSToken?wsdl
    I checked the WSDL from the above link. The issue that I noticed is that you are importing the schema structure in your above WSDL. PI is unable to recognize the external reference. SOAPUI (or similar tool) will recognize the external reference.
    Best option is that you should re-modify your above WSDL and provide the schema in this WSDL itself. It should then work just fine.
    Hope this helps.
    Regards,
    Neetesh

  • External definition import WSDL complex type problem

    Hi,
    i have created a webservice using apache axis and created an external definition for the service. You can see the respective WSDL recognized by XI below. The service takes an array of adresses. Unfortunately, when I want to define the message mapping, theres only the array but not the address attributes. What would be a proper definition of the service?
    Cheers,
    Heiko
    ===================================================
    1. WSDL from external defintion:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://localhost:8080/axis/services/AdressService">
         <wsdl:types>
              <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://localhost:8080/axis/services/AdressService" targetNamespace="http://localhost:8080/axis/services/AdressService">
                   <xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
                   <xsd:complexType xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" name="AddressDto">
                        <xsd:sequence>
                             <xsd:element name="ID" type="xsd:string" nillable="true" />
                             <xsd:element name="name" type="xsd:string" nillable="true" />
                             <xsd:element name="strasse" type="xsd:string" nillable="true" />
                             <xsd:element name="ort" type="xsd:string" nillable="true" />
                        </xsd:sequence>
                   </xsd:complexType>
                   <xsd:complexType xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" name="ArrayOfAddressDto">
                        <xsd:complexContent>
                             <xsd:restriction base="soapenc:Array">
                                  <xsd:attribute ref="soapenc:arrayType" wsdl:arrayType="impl:AddressDto[]" />
                             </xsd:restriction>
                        </xsd:complexContent>
                   </xsd:complexType>
              </xsd:schema>
         </wsdl:types>
         <wsdl:message name="writeAddressDataResponse" />
         <wsdl:message name="writeAddressDataRequest">
              <wsdl:part xmlns:generateduniqueprefix3="http://localhost:8080/axis/services/AdressService" name="addresses" type="generateduniqueprefix3:ArrayOfAddressDto" />
         </wsdl:message>
    </wsdl:definitions>
    2. XSD extracted from WSDL:
    <?xml version="1.0" encoding="UTF-8"?>
    <xsd:schema targetNamespace="http://localhost:8080/axis/services/AdressService" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://localhost:8080/axis/services/AdressService">
      <xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
      <xsd:element name="addresses" type="ArrayOfAddressDto" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
      <xsd:complexType name="ArrayOfAddressDto" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
        <xsd:complexContent>
          <xsd:restriction base="soapenc:Array">
            <xsd:attribute ref="soapenc:arrayType" wsdl:arrayType="impl:AddressDto[]" xmlns:xsd="http://www.w3.org/2001/XMLSchema" />
          </xsd:restriction>
        </xsd:complexContent>
      </xsd:complexType>
    </xsd:schema>
    ??? Where are the atributes of the address here ???

    Hi Heiko,
    XI does not support the use of soapenc:array. Please refer to http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16556272 regarding the use of this construct.
    Greetings Stephan

  • Multi-Mapping Error in PI 7.1 - External Definitions

    Hi all,
    We have just upgraded to PI 7.1 from 7.0 and run into an issue with message multi-mappings, just wondered if anyone else had met the same issue and worked it out...
    When creating a message mapping, we are using as the target an external definition which is defined by an XSD generated by a third party tool (Seeburger).
    When I map 1:1 (1 source message to one target message) in the message mapper, all is fine but if I try to create a multi mapping, I get an error. The process is:
    a) I have a message mapping with one target message, defined as an External Definition.
    b) I then go to Signature tab and add a second target message as an External Definition
    c) Click back to Definition tab
    d) Get the error "Object XXXXX | YYYYY not found" - where XXXXX is the external def name and YYYYY is the namespace (the SWCV namespace that is, not the XML namespace)
    This only seems to happen with External Definitions which are autogenerated and I strongly suspect that is has to do with the fact that the tool that generates them always  does so without an XML namespace. I have not proved this though (other Ext Defs with namespaces work for multi-mappings but that is not the only difference so I can't be sure that is the issue but have a strong hunch. This problem did not occur in 7.0.
    Anyone got any ideas?
    Thanks,
    Chris

    Hi,
    This would not be of much help but, I was able to encounter this issue in XI 3.0.
    What we did was to manually edit the XSD and add a namespace to it. I'm not sure if PI 7.1 is able to handle mutiple namespaces, so we limited it to this value <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> and made sure that this value is used for all the External Definitions used in the multi-mapping.
    Regards,

  • Not able to see "External Definitions" in Integration Repository

    Hi Experts,
    I am working on PI 7.1.
    In the Integration Repository Menu :
    SAP Basis --->SAP Basis 7.10 ->http://sap.com/xi/XI/System ->
    "Service Interfaces",
    "Message Types"
    "Fault Message Types",
    "Data Types",
    "Adapter Metadata"
                                      only are visible.
    We need the "External Definitions". Is it  not available in the standard SAP PI 7.1 ?
    Do we have to import it explicitly?
    Kindly advice.
    Thanks in advance
    ~ Suraj

    Hey NM,
        Thanks a lot for your suggestion. problem got resolved when i did what you said (checking the attributes with developers user id's)
    Thanks
      Sourav

  • PI does not keep sequence of XSD for external definition

    Hi,
    currently I face following problem. I have an XSD which decribes a MSCONS market message that contains following sequence:
         <xs:complexType name="MSCONS">
              <xs:sequence>
                   <xs:element name="UNH" type="UNH"/>
                   <xs:element name="BGM" type="BGM"/>
                   <xs:element name="DTM" type="DTM"/>
                   <xs:element name="NAD" type="NAD" minOccurs="2" maxOccurs="2"/>
                   <xs:element name="UNS" type="UNS"/>
                   <xs:element name="NAD" type="NAD" maxOccurs="unbounded"/>
                   <xs:element name="CNT" type="CNT" minOccurs="0" maxOccurs="99"/>
                   <xs:element name="UNT" type="UNT"/>
              </xs:sequence>
         </xs:complexType>
    There are 2 NAD elements, followed by an UNS element, followed by an NAD element again. When I upload that XSD to PI as an external definition, the message is described as:
    MSCONS     Message                         
    -> MSCONS     Element     MSCONS     1               Metered services consumption report message
    -> -> UNH     Element     UNH     1               
    -> -> BGM     Element     BGM     1               
    -> -> DTM     Element     DTM     1               
    -> -> NAD     Element     NAD     1..unbounded               
    -> -> UNS     Element     UNS     1               
    -> -> CNT     Element     CNT     0..99               
    -> -> UNT     Element     UNT     1     
    All the NAD elements are summarized before UNS element. After mapping I will get an message which is not valid to XSD, because sequence is not correct.
    Does anyone knows a solution/workaround for that issue. Would appreciate you help.
    Thank you and Best Regards,
    Nico

    > All the NAD elements are summarized before UNS element. After mapping I will get an message which is not valid to XSD, because sequence is not correct.
    >
    > Does anyone knows a solution/workaround for that issue. Would appreciate you help.
    No. There is no way. The way how graphical mapping works internally makes it impossible to achieve your requirement.
    As work around use two different nodes NDA and NAD1 and rename it with a simple Java mapping as second mapping step.

  • Scenario proxy to soap synchronous with external definitions

    Hi all,
    I have a problem with my scenario.
    In development environment all is working fine, but when I have transported to preproduction environment and we have executed my scenario I have the following error:
    <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: http://geisiedes.endesa.es/WSRespuesta/WsRespuestaSIE.asmx/EnviarRespuestaNocturnaWF.</SAP:AdditionalText>
    <SAP:Stack />
    I attach the receiver communication channel configuration.(cc_config.jpg)
    I changed the target URL in the receiver channel, with the preproduction machine, but I didn't change the sopa action because is define in the wsdl ( soap_action.jpg).
    I have othe external definitions for preproduction environmet but its contect is different to external definitions in development change the reference to machine where geisiepre instead geiseides.
    Whe I import this external definitions I lose the configuration in messages mappings.
    How can I solve this problem? Is mandatory to have the same external definitions in the three environments??
    Thanks and best regards
    Mónica

    Hi Monica,
    I normally use the all the tag content in the SOAPAction tag, but you can try with EnviarRespuestaNocturnaPC in the SOAP receiver communication channel.
    Have you tried to test your wsdl endpoint with SOAPui?, you can get sometimes valuable information about how design/configure in PI and if the request is identical in PI and in SOAPui.
    Regards.

  • Messages not adviced in extern definition after import wsdl-file from WAS

    Hi friends,
    after importing the three wsld-files in repository (extern definitions) the messages are not adviced. The referendes to the files are fine, because the name is shown at the tab externe...
    But i´m not shure wheather i tool the right link ant Web Service Navigator. It is right to download the default SAP WSDL Files or the default one? Because in the SAP WSDL-files there will be an exception during import in XI repository (tag sap:useFeatur). What is the problem that the messages are not shown on the tab messages in externe definitions?
    Thanks in advance,
    Frank

    I've the same problem. Here is my WSDL:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions targetNamespace="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns:intf="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="blablabla.de" xmlns:tns2="http://net.jboss.org/jmx" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <wsdl:types>
              <schema targetNamespace="blablabla.de" xmlns="http://www.w3.org/2001/XMLSchema">
                   <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
                   <complexType name="MSOBean">
                        <sequence>
                             <element name="installationName" nillable="true" type="xsd:string"/>
                             <element name="requestId" nillable="true" type="xsd:string"/>
                             <element name="returnCode" type="xsd:int"/>
                             <element name="returnMessage" nillable="true" type="xsd:string"/>
                        </sequence>
                   </complexType>
                   <complexType name="MSIBean">
                        <sequence>
                             <element name="password" nillable="true" type="xsd:string"/>
                             <element name="project" nillable="true" type="xsd:string"/>
                             <element name="requestId" nillable="true" type="xsd:string"/>
                             <element name="userId" nillable="true" type="xsd:string"/>
                        </sequence>
                   </complexType>
              </schema>
         </wsdl:types>
         <wsdl:message name="actualizeRequest">
              <wsdl:part name="inData" type="tns1:MSIBean"/>
         </wsdl:message>
         <wsdl:message name="actualizeResponse">
              <wsdl:part name="actualizeReturn" type="tns1:MSOBean"/>
         </wsdl:message>
         <wsdl:portType name="MSService">
              <wsdl:operation name="actualize" parameterOrder="inData">
                   <wsdl:input message="impl:actualizeRequest" name="actualizeRequest"/>
                   <wsdl:output message="impl:actualizeResponse" name="actualizeResponse"/>
              </wsdl:operation>
         </wsdl:portType>
         <wsdl:binding name="MyServicesSoapBinding" type="impl:MSService">
              <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
              <wsdl:operation name="actualize">
                   <wsdlsoap:operation soapAction=""/>
                   <wsdl:input name="actualizeRequest">
                        <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://blablabla.de" use="encoded"/>
                   </wsdl:input>
                   <wsdl:output name="actualizeResponse">
                        <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://blablabla.de:8080/jboss-net/services/MyServices" use="encoded"/>
                   </wsdl:output>
              </wsdl:operation>
         </wsdl:binding>
         <wsdl:service name="MSServiceService">
              <wsdl:port binding="impl:MyServicesSoapBinding" name="MyServices">
                   <wsdlsoap:address location="http://blablabla.de:8080/jboss-net/services/MyServices"/>
              </wsdl:port>
         </wsdl:service>
    </wsdl:definitions>
    No Idea.

  • DTD files as external Definition

    Hi ,
    Read lot of threads on this which are having same problem ,some of them got solved none of them posted how did they succeded on those.
    i am getting error like Name "ds:Signature" is incorrect, when i tried to inport the .dtd file as external definition,so I did try converting dtd file to XSD ,it is creating the 3 xsd files and none of them are valid each one of them are error.But however the DTD file is valid .
    Using Invoicedetail DTD file for my scenario.
    you can download the file from http://cxml.org
    Please let me knw on this.
    Thanks,
    Madhu

    Hi,
    Here are the errors for the 3 xsd's
    1.     Value 'ds:Signature' is not allowed for attribute 'ref'.
              Hint: A valid value would be 'xml:lang'.
              Error location: xs:schema / xs:element / xs:complexType / xs:sequence / xs:element / @ref
    2.     Value 'ds:Signature' is not allowed for attribute 'ref'.
              Hint: A valid value would be 'xml:lang'.
              Error location: xs:schema / xs:element / xs:complexType / xs:sequence / xs:element / @ref
    3.                   Value 'xades:Identifier' is not allowed for attribute 'ref'.
              Hint: A valid value would be 'xml:lang'.
              Error location: xs:schema / xs:element / xs:complexType / xs:sequence / xs:element / @ref
    these errors are coming in xml spy when i tried to validate .
    Thanks,
    Madhu
    Edited by: madhu204 on Jul 23, 2009 4:54 PM
    Edited by: madhu204 on Jul 23, 2009 4:55 PM

  • External Definition (wsdl) with abstract xsd element

    Hello All,
    we are trying to call a webservice, here is the wsdl:
    https://www.1link.com/fr/demo-sn/site/gaiwebservice.asmx?WSDL
    the problem is that the GAIJobLine element is defined as abstract:
    <s:complexType name="GAIJobLine" abstract="true">
    and there several elements which are extending GAIJobLine, for example:
    <s:complexType name="GAITyreLine">
                        <s:complexContent mixed="false">
                             <s:extension base="tns:GAIJobLine">
    So in our mapping we need to map to those element which are extending base element and not to the abstract one, but Graphical mapping displays only GAIJobLIne base element.
    Does anybody know how we can map to extended elements without mannually changing wsdl?
    Best Regards,
    Artsiom Anichenka

    thanks for your reply!
    the extended elements are seen when I open wsdl in XMLSpy.
    they are also visible in external definition object, but the main problem is that in the mapping only the base lement is displayed and there is no possobility to choose the extension.
    Maybe this kind os XSDs (with abstract base types and extended elements) are just not supported by PI711?

  • External definition

    Hi All,
    I have imported xsd files as external definitions. They are showing messaages list without any space.While using them in message mapping they are not showing the fields. Even in the case of direct import into message mapping also the same result.I am not getting the problem. Any suggestions to solve this..
    Thanks in advance,
    Kartikeya

    hi,
    i think this helps..
    some of the tags are not supported by message mapping...like choice and complex..
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2089f29b-b10a-2a10-5297-e258df0c1bfc
    Thanks,
    vijaya.

  • Import external definition to message type

    Hello
    I have scenario file to IDOC.
    I don’t know way in this time I not successful to import my external definition to message type.
    Any idea?
    Elad

    Hello again,
    I try to solve mapping problem
    Hello again,
    I have scenario from file(xml) to IDOC.
    In outbound side I have XSD file and I imported this file and I use with him in outbound interface.
    In inbound side I have IDOC.
    I have mapping problem issue.
    When I test this mapping I have this error message:
    Cannot produce target element /ZORD_CREATE. Check xml instance is valid for source XSD and target-field mapping fulfills requirements of target XSD
    Any idea?
    Elad

  • Error importing xsd as external definition

    I'm importing a wsdl file as external definition and it references some xsd files that I'm trying to import too. Specifically there are 2 of them that I can't import in PI, as I get the next error:
    Error when loading XML document (Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.UnknownHostException: www.w3.org)
    XSD files might be found under next urls:
    [XAdES.xsd|https://www3.aeat.es/ADUA/internet/es/aeat/dit/adu/xades/XAdES.xsd]
    [xmldsig-core-schema.xsd|https://www3.aeat.es/ADUA/internet/es/aeat/dit/adu/xades/xmldsig-core-schema.xsd]
    and are meant to be used to sign the document.
    I have validated the files using the service in the next url:
    [http://www.w3.org/2001/03/webdata/xsv|http://www.w3.org/2001/03/webdata/xsv] as well as in Altova XML Spy.
    Has anyone any idea of what the problem might be? It is really interfering in my development.
    Thanks in advance.

    Ok I think I might have solved it. First there was a pair of problems with the file xmldsig-core-schema.xsd.
    1. The name couldn't be used in PI as '-' characters are not allowed.
    I changed the name to xmldsig_core_schema.xsd
    2. The file had these lines at the start:
    <!DOCTYPE schema PUBLIC "-//W3C//DTD XMLSchema 200102//EN" "http://www.w3.org/2001/XMLSchema.dtd" [
         <!ATTLIST schema
         xmlns:ds CDATA #FIXED "http://www.w3.org/2000/09/xmldsig#"
    >
         <!ENTITY dsig 'http://www.w3.org/2000/09/xmldsig#'>
         <!ENTITY % p ''>
         <!ENTITY % s ''>
    ]>
    PI doesn't like that if you import the file as XSD because I guess that is DTD not XSD format.
    I removed those lines.
    With these two changes this file could be imported.
    However I still had problems with the XAdES.xsd file. PI couldn't recognize the import of xmldsig-core-schema.xsd file:
    <xsd:import namespace="http://www.w3.org/2000/09/xmldsig#" schemaLocation="http://www.w3.org/TR/2002/
    REC-xmldsig-core-20020212/xmldsig-core-schema.xsd"/>
    It didn't like the URL, so I changed it to make reference to my local file.
    After this, it all worked. The question is, will it also work in runtime when I'll make use of these external definitions created? Or will my changes have an impact on the results? I guess it will work fine but perhaps I'm wrong.
    Besides, when activated I got the next warning:
    Name of '/schema/complexType("TimeStampType")/sequence/choice/element("XMLTimeStamp")' starts with 'xml'
    There's an element name that starts by XML. Is this forbidden? Will I have problems if I activate and use it just as it is?
    Thanks for the answers.

  • Issue while importing the WSDL file in the External Definitions - PI 7.0

    Dear all Experts
    After importing the WSDL file in the external External Definitions we are not able to view the " name and namespace " in the messages tab.
    Request you to advise on the issue.
    We are using the PI 7.0
    Regards
    Machindra Patade

    Dear All
    Got the answer"
    The problem is in the namespace description LENGTH,
    Note the following restrictions for XI or PI installations:
    ·         Maximum length of repository namespaces and XML namespaces: 60 Characters. Due to this restriction, the import of XSD files and WSDL files prepares difficulties as an external definition; you can solve these difficulties using Note 901988.
    ·         Maximum length of object names in the Integration Repository and Integration Directory: 120 characters
    As of SAP NetWeaver Process Integration 7.10 Support Package 7, the enhancement of the maximum length of namespaces to 255 is supported in the configuration and runtime.
    Please check the below SAP 2 notes in regards to above mail.
    SAP Note 901988 - Integration Builder: Namespace of external definitions
    SAP Note 870809 - Integration Builder: Length of namespaces and object names

Maybe you are looking for