External Definition - PortType and Bindings missing in WSDL tab

I have created a valid wsdl - document type and imported it into the IR.  Almost everything looks OK.  No errors on the import, messages show in the message tab.  However, when I look at the wsdl tab, I notice that only about half of my orginal wsdl is displayed.  The PortType and Bindings nodes are missing.  Is there a reason why XI might be stripping this off?
Edited by: Mark Ortiz on Sep 4, 2008 6:42 PM

Hi
when u import the wsdl file in IR, It will treat as the structure and when u see in the wsdl file in wsdl tab all the methods and namespace are equal but the system information differs.It takes the info of the Xi server.
But u need to give the wsdl info in ID , It reads system info from ID only not from IR( IR acts as skeleton)
Regards,
Jayasimha jangam

Similar Messages

  • Webservice definition . Error when displaying the wsdl tab

    Hello Everybody .
    I am trying to create a webservice of a  funtion module .
    When i am checking al the service definitions tabs of this web service I got the following error on the wsdl tab :
    *Internal error GET_SIDL in CL_WS_MD_VIF-->GET_WSDL; inform the person responsible.*
    Any ideas in order to solve this problem  ?
    Many Thanks

    Hi Adem,
    I am also facing the same problem.
    When I type SOAMANAGER,my browser gets opened but it says page can't find.
    You got any solution?Can you please share it to me?
    Thanks,
    Snehal Mehta

  • RSAT and the missing Attribute Editor tab [solution]

    PROBLEM
    When you install RSAT on a Vista workstation or Server 2008 system, that is managing a 2000/2003 based forest, you do not see the Attribute Editor tab when looking at the properties of a User or Computer object in Active Directory Users and Computers(ADUC).
    MORE INFORMATION
    The Display Specifier is not updated in the Configuration Naming context, because the 2008 schema changes have not been executed on the forest. Part of the upgrade updates the forest Display Specifiers.  The Attribute Editor tab actually uses functions within the ADSIEDIT tool , more specifically the ADSIEDIT.DLL extension. Although the DLL is probably registered on the RSAT system, the ConfigNC need updating, in order to expose the tab in the ADUC interface.
    SOLUTION
    Use the ADSIEDIT tool (or other tool of choice...ADexplorer, LDP etc), with a user who has rights to modify the Configuration Naming Context.
    Navigate to cn=<languagepage>, cn=configuration, dc=<domainname>
                 (where <languagepage> is your relevant language...see http://support.microsoft.com/kb/324097)
                 (where <domainname> is your domain dn)
    Under the cn=User-Display object, edit AdminPropertyPages and add the line 11,{c7436f12-a27f-4cab-aaca-2bd27ed1b773}
    Under the cn=Computer-Display object, edit AdminPropertyPages and add the line 12,{c7436f12-a27f-4cab-aaca-2bd27ed1b773}
    Under the cn=Default-Display object, edit AdminPropertyPages and add the line 4,{c7436f12-a27f-4cab-aaca-2bd27ed1b773}
    Open ADUC from the Vista or Server 2008 and you should now see the Attribute Editor for the object you selected.  Note: Attribute editor is only shown when ADUC is in Advanced View.
     -Stuart Hudman

    Never mind, i got it.... the prefix number is irrelevant as long as it is in sequential order... to be able to see the attribute editor tab for groups i just
    Under the cn=group-Display object,
    edit AdminPropertyPages and
    add the line 5,{c7436f12-a27f-4cab-aaca-2bd27ed1b773}
    the first number (5,) was my next available number.
    FYI: English is 409. the actual DN would be cn=409,
    cn=DisplaySpecifiers, cn=configuration, dc=<domainname>

  • External Definitions

    Hi Friends,
         There is a requirement for external definition to import.  I got one file from client text file having xml data. So i have save as to .XSD format and tested in XI while uploading into external definitions.
         As per my knowledge, .XSD/wsdl/dtd file can be used for external definitions. And, it acts as Message type so create MI .
    So , if we request from client , is there specific format is there for .XSD??? Is it only message type else data type possible ???
    How to guide the client to get the .XSD files?
    Thank you
    Deva

    Hi Deva,
    first convert XML file in to XSD,for that you can use XML Editors ALTOVA XML Spy or Styalus studio to conver XML to XSD.
    you can get free trail versions available.
    The XML to XSD conversion process very easy , just google it.
    if you have XSD then you no need to create Data type and Message Type.
    Regards,
    Raj

  • Need of External definition

    Hey guys
    i was just wondering as to why we need to import an XSD or WSDL in External definition when we can directly import that using the tabs in Datatypes and Message Interface.
    is it because of shipment purposes?do we always need to create an External definition first and then import that in datatype or Message Interface?
    thanx
    ahmad

    Hi Ahmad,
          Added to Archanas  point,External Defination are used in XI to import the any wsdl files from any remote stystem or any landscape.
        Let's take an example you have webservice which is not in your landscape and you want to use that webservice in your business requirement...in such a situation you can imort that wsdl file as external defeniation in XI and  you can map the reqired fields....here we are making use of webservice as external definiation which is not in ur landscape.
        Hope you clear about what is the use of exeternal definition
    Thanks and Regards,
    chandu.

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

  • Add new field in External Definition

    Hi,
    I have a scenario where I have to add just one extra field in in the Outbound DT.
    In our case we do not have DT, but External Definition say BAPI_XYZ.xsd
    I export the .xsd file from Tools --> Export Original Document (Category: xsd, Messages:From All available global elements" )and the BAPI_XYZ.xsd is saved in my desktop.
    I just add this piece of code in the place where I need it.
    <xsd:element name="PLANNING_VER" minOccurs="0"><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength Value="8"/></xsd:restriction></xsd:simpleType></xsd:element>
    After this I import the XSD and save it undre external definition. But when I open this new xsd in the message mapping I get the error "BAPI_XYZ has No messages" and the structure is not loaded.
    In the existing External definition when I move to the "Messages" Tab I can see an entry "BAPI_XYZ.Response" . The same is not available when I add the extra field and impor the new XSD
    Can some one pls help??
    Regards
    Prasanna

    Hi Prasanna 
    There is an issue with XSD. Value = "8" should be small v.
    Please insert the below code at correct position.
    <xsd:element name="PLANNING_VER" minOccurs="0">
       <xsd:simpleType>
          <xsd:restriction base="xsd:string">
             <xsd:minLength value="8" />
          </xsd:restriction>
       </xsd:simpleType>
    </xsd:element>
    After that check that XSD is well formed and valied or not. You can use Validator for XML Schema W3C [Link|http://www.w3.org/2001/03/webdata/xsv] , XML editor (XMLspy), Eclipse, NetBeans.
    Regards,
    Raghu_Vamsee

  • Importing WSDL into External Definitions

    Hi,
    I got WSDLs from WAS WS Navigator, I have imported the WSDL from <b>porttypes</b> folder but I don't see any messages in the messages tab of External Definitions.
    See below my WSDL
    <?xml version="1.0" encoding="utf-8"?>
    <!--            Generated by WSDLDefinitionsParser    --><wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns0="urn:xEM_MeasurementImportVi" targetNamespace="urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document" xmlns:tns="urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document">
      <wsdl:types>
        <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:java/lang" xmlns:tns="urn:java/lang" elementFormDefault="qualified">
          <xs:complexType name="ArrayOfint">
            <xs:sequence>
              <xs:element maxOccurs="unbounded" minOccurs="0" name="int" type="xs:int" nillable="true"/>
            </xs:sequence>
          </xs:complexType>
          <xs:complexType name="ArrayOfString">
            <xs:sequence>
              <xs:element maxOccurs="unbounded" minOccurs="0" name="String" type="xs:string" nillable="true"/>
            </xs:sequence>
          </xs:complexType>
        </xs:schema>
        <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:com.technidata.em.imp.consumption" xmlns:tns="urn:com.technidata.em.imp.consumption" elementFormDefault="qualified">
          <xs:complexType name="ReturnCode">
            <xs:sequence>
              <xs:element name="code" type="xs:int"/>
              <xs:element name="description" type="xs:string" nillable="true" minOccurs="0"/>
            </xs:sequence>
          </xs:complexType>
          <xs:complexType name="ArrayOfReturnCode">
            <xs:sequence>
              <xs:element maxOccurs="unbounded" minOccurs="0" name="ReturnCode" type="tns:ReturnCode" nillable="true"/>
            </xs:sequence>
          </xs:complexType>
        </xs:schema>
        <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:com.technidata.em" xmlns:tns="urn:com.technidata.em" elementFormDefault="qualified">
          <xs:complexType name="Measurement">
            <xs:sequence>
              <xs:element name="pSystemId" type="xs:string" nillable="true" minOccurs="0"/>
              <xs:element name="pSystemTagId" type="xs:string" nillable="true" minOccurs="0"/>
              <xs:element name="pDate" type="xs:dateTime" nillable="true" minOccurs="0"/>
              <xs:element name="pValue" type="xs:double"/>
              <xs:element name="pUnit" type="xs:string" nillable="true" minOccurs="0"/>
              <xs:element name="pDescription" type="xs:string" nillable="true" minOccurs="0"/>
            </xs:sequence>
          </xs:complexType>
          <xs:complexType name="ArrayOfMeasurement">
            <xs:sequence>
              <xs:element maxOccurs="unbounded" minOccurs="0" name="Measurement" type="tns:Measurement" nillable="true"/>
            </xs:sequence>
          </xs:complexType>
        </xs:schema>
        <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:xEM_MeasurementImportVi" xmlns:tns="urn:xEM_MeasurementImportVi" elementFormDefault="qualified" xmlns:s1="urn:java/lang" xmlns:s2="urn:com.technidata.em.imp.consumption" xmlns:s0="urn:com.technidata.em">
          <xs:import namespace="urn:java/lang"/>
          <xs:import namespace="urn:com.technidata.em.imp.consumption"/>
          <xs:import namespace="urn:com.technidata.em"/>
          <xs:element name="checkConnection">
            <xs:complexType>
              <xs:sequence/>
            </xs:complexType>
          </xs:element>
          <xs:element name="checkConnectionResponse">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Response" type="xs:string" nillable="true"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="doMeasurementImport">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="pSystemId" type="xs:string" nillable="true"/>
                <xs:element name="pSystemTagId" type="xs:string" nillable="true"/>
                <xs:element name="pDate" type="xs:dateTime" nillable="true"/>
                <xs:element name="pValue" type="xs:double"/>
                <xs:element name="pUnit" type="xs:string" nillable="true"/>
                <xs:element name="pDescription" type="xs:string" nillable="true"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="doMeasurementImportResponse">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Response" type="xs:int"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="doMeasurementsImport">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="pMeasurements" type="s0:ArrayOfMeasurement" nillable="true"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="doMeasurementsImportResponse">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Response" type="s1:ArrayOfint" nillable="true"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="getErrorCodes">
            <xs:complexType>
              <xs:sequence/>
            </xs:complexType>
          </xs:element>
          <xs:element name="getErrorCodesResponse">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Response" type="s2:ArrayOfReturnCode" nillable="true"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="getSupportedUnits">
            <xs:complexType>
              <xs:sequence/>
            </xs:complexType>
          </xs:element>
          <xs:element name="getSupportedUnitsResponse">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Response" type="s1:ArrayOfString" nillable="true"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:schema>
      </wsdl:types>
      <wsdl:message name="checkConnectionIn_doc">
        <wsdl:part name="parameters" element="ns0:checkConnection"/>
      </wsdl:message>
      <wsdl:message name="checkConnectionOut_doc">
        <wsdl:part name="parameters" element="ns0:checkConnectionResponse"/>
      </wsdl:message>
      <wsdl:message name="doMeasurementImportIn_doc">
        <wsdl:part name="parameters" element="ns0:doMeasurementImport"/>
      </wsdl:message>
      <wsdl:message name="doMeasurementImportOut_doc">
        <wsdl:part name="parameters" element="ns0:doMeasurementImportResponse"/>
      </wsdl:message>
      <wsdl:message name="doMeasurementsImportIn_doc">
        <wsdl:part name="parameters" element="ns0:doMeasurementsImport"/>
      </wsdl:message>
      <wsdl:message name="doMeasurementsImportOut_doc">
        <wsdl:part name="parameters" element="ns0:doMeasurementsImportResponse"/>
      </wsdl:message>
      <wsdl:message name="getErrorCodesIn_doc">
        <wsdl:part name="parameters" element="ns0:getErrorCodes"/>
      </wsdl:message>
      <wsdl:message name="getErrorCodesOut_doc">
        <wsdl:part name="parameters" element="ns0:getErrorCodesResponse"/>
      </wsdl:message>
      <wsdl:message name="getSupportedUnitsIn_doc">
        <wsdl:part name="parameters" element="ns0:getSupportedUnits"/>
      </wsdl:message>
      <wsdl:message name="getSupportedUnitsOut_doc">
        <wsdl:part name="parameters" element="ns0:getSupportedUnitsResponse"/>
      </wsdl:message>
      <wsdl:portType name="xEM_MeasurementImportVi_Document">
        <wsdl:operation name="checkConnection">
          <wsdl:input message="tns:checkConnectionIn_doc"/>
          <wsdl:output message="tns:checkConnectionOut_doc"/>
        </wsdl:operation>
        <wsdl:operation name="doMeasurementImport">
          <wsdl:input message="tns:doMeasurementImportIn_doc"/>
          <wsdl:output message="tns:doMeasurementImportOut_doc"/>
        </wsdl:operation>
        <wsdl:operation name="doMeasurementsImport">
          <wsdl:input message="tns:doMeasurementsImportIn_doc"/>
          <wsdl:output message="tns:doMeasurementsImportOut_doc"/>
        </wsdl:operation>
        <wsdl:operation name="getErrorCodes">
          <wsdl:input message="tns:getErrorCodesIn_doc"/>
          <wsdl:output message="tns:getErrorCodesOut_doc"/>
        </wsdl:operation>
        <wsdl:operation name="getSupportedUnits">
          <wsdl:input message="tns:getSupportedUnitsIn_doc"/>
          <wsdl:output message="tns:getSupportedUnitsOut_doc"/>
        </wsdl:operation>
      </wsdl:portType>
    </wsdl:definitions>
    Appreciate your quick response.
    Srini Sandaka

    Hi,
    I diagnose the problem, the problem with the name space length.
    Orginal NameSpace: <i>urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document</i>
    Modified NameSpace: <i>urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/documen</i>
    The <b>External Definitions</b> is recognizing only 60 characters namespace. If the namespace exceed 60 characters it is not showing any messages in the messages tab.
    Will make any problem to call the WebService from XI since we are changing the original namespace in the WSDL and imported into XI.
    How can we overcome this problem, is it a limitation.
    Thanks
    Srini Sandaka

  • 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

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

  • Import SAP WSDL into External Definition

    Hi Friends,
    I'd like to import a WSDL into XI External Definition. However, the WSDL is gained from Web AS Web Service Navigator. So it is a zip file and consists of three WSDL files. How can I import them into the external definition?
    Thanks + Regards
    Jerome

    Hi Jerome,
    If you have three wsld files then aren't those three messages?
    have you tried importing them as external definitions one by one?
    you can check how the message structre looks like
    when you try to use the external definition inside a
    message mapping (remember you don't create message type from external definitions)
    Futher reference:
    http://help.sap.com/saphelp_nw04/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm
    BTW
    while creating external defnitions (WSDL)
    you can only choose wsld file or XML - nothing else
    Regards,
    michal

  • No messages under the 'Messages' tab for imported WSDL in External Definitions

    Dear All,
    I import this WSDL to the External Definitions but it is not showing any messages in the 'Messages' tab while WSDL clearly has message interfaces in it. Attached is the WSDL. You help is very much appreciated.
    Regards,
    Adil Khalil

    Hi, imported wsdl shouldn't have any import instruction.
    All import instruction should be changed to content of importing file.
    I see the code <xsd:import namespace="http://ouaf.oracle.com/"/> in your file.
    Hmm. but I imported you file and everything is fine
    Message was edited by: Mikhail Koshkin

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

  • 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 and used them as Data Type Templates

    hi all
    how to Develop external definition and used them as Data Type Templates .
    Thank u
    Swari

    HI
    External Definitions: If a definition of the message structure exists in wsdl, xsd, dtd formats, we can use it in the integration repository by importing it as an external definition.
    External Definations:
    An external definition enables you to import a local WSDL, XSD, or DTD file to the Integration Repository and specify which parts of the schema to extract as the description for a message. You can use these extracted message schema as:
    Output or input messages in message interfaces
    Source or target structures for message mappings
    There is a series of standard schema for describing the message structure at runtime. WSDL (Web Service Description Language), XSD (XML Schema Definition Language), or DTDs (Document Type Definitions) are often used to describe message schema. If a description of the message structure already exists in one of the above formats, you can use it in the Integration Repository by importing it as an external definition rather than re-entering it manually using the data type editor.
    Have a look at
    http://help.sap.com/saphelp_nw04/helpdata/en/43/ce49ef1019087ae10000000a1553f6/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/ba/d4c23b95c8466ce10000000a114084/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm
    cheers

Maybe you are looking for