XSD or WSDL

Hi,
I need to import the structure for XI --> Web Services scenario.
What file should I need: XSD or WSDL?
I'm a bit confused here. In IB there is an explicit option to import XSD, while somebody advised me to import the WSDL file.
Please advise.
Thanks

Hi Rokie,
We use the wsdl file for Webservice..
There is the option to import wsdl as well in XI exactly at the same place where you are looking for xsd.. just drop down that box and find wsdl option.
check this blog for referance....
/people/shabarish.vijayakumar/blog/2007/11/07/walkthrough--soap-xi-rfcbapi
Sachin

Similar Messages

CustomizeWSDL, importing xsd in wsdl file.

We have requirement of importing centralized XSD files in WSDL,
1) based on best practices I believe we should do following:
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" >
<import namespace="http://xmlns.oracle.com/HelloWorld" schemaLocation="http://localhost:7777/xsd/HelloWorld.xsd"/>
</schema>
</types>
2) Now, for life cycle management I thought of writing custom Ant task, but I believe customizeWSDL should take care of it,
I tried,
<customizeWSDL inFile="${process.dir}/bpel/WriteToMyFile.wsdl" outFile="${process.dir}/bpel/WriteToMyFile.wsdl">
<wsdlImport namespace="http://xmlns.oracle.com/HelloWorld" locationURI="http://${http.hostname}:${http.port}/xsd/HelloWorld.xsd" />
</customizeWSDL>
but it didn't work. I know it is for wsdl import, but based document it says XSD and WSDL import are both supported in customizeWSDL.
I looked at the source code of customizeWSDL as well, it doesn't look like there is any special xsdImport child tag inside customizeWSDL.
Can anybody please help me here??
Thanks a lot!
Chintan

Hi Ninad,
WS Policy is Standard that is used by any intregration tools while generating the .WSDL's, If the 3 party systems cannot understand WS Policy, you can easily remove them by using tools like XML notepad, XML spy in deleting them and feed in your WSDL files to the 3rd party systems.
Hope this clears your issue.
Thanks,
KishoreJ.

Want to download the segment structure into xsd or wsdl

Hi Guys,
I want to dwonload the segement structure (E1KNA1M) into XSD or WSDL.
Then i can import into XI as datatype,
How can i download the segment structure into XSD?
Thanks
Srinivas

Srinivas,
I tried to put the E1KNA1M segment xsd here. But it seems I cannot do because the length of it is more than 15000 characters. So I just send a mail this xsd. Take a look and update here.
What I did basically is copied the DEBMAS.DEBMAS04 xsd into altova xml spy and manually deleted all the segments except E1KNA1M segement. You can change the name of the segment names also if you want.
Regards,
---Satish

XSD from WSDL SOAP response

From WSDL, I have SOAP respose as
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <soapenv:Body>
          <ns1:getDistanceResponse xmlns:ns1="http://DefaultNamespace" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
               <ns1:getDistanceReturn xsi:type="xsd:double">0.0</ns1:getDistanceReturn>
          </ns1:getDistanceResponse>
     </soapenv:Body>
</soapenv:Envelope>
How do I create XSD so that I can import external defintion in designer message_type without typing the fields from scratch?
Here is the XSD:-
<?xml version="1.0" encoding="ISO-8859-1"?><xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"><xs:element name="getDistanceResponse"><xs:annotation><xs:documentation>Comment describing your root element</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:element name="getDistanceReturn" type="xs:double" /></xs:sequence></xs:complexType></xs:element></xs:schema>

Satish,
When I look at /people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1, from WSDL an XSD is created for getDistanceResponse.
Also there is a note from Shabarish "At my first try i used the messages getDistanceRequest and getDistanceResponse in my mapping but later found out that it wasnt the message structure that the webservice expected."
Hence wondering how to create XSD from WSDL so that I can use the structures in message mapping.
In this case it is simple, so i can create the data type but for complex it is better to create XSD from WSDL. May be I'm not putting the right words and question. Please help

Import External XSD into WSDL ?

Hello,
How to import external XSD like ABC.xsd into WSDL ?? Or Do I also need to enter namespece in the BPEL source file ??
Actually I have created a BPEL that using some XML input along with namespace like
<ssml name="asd" xlmns:abc="urn:ssml:core:3:5"> So I need to define this namespace somewhere in BPEL or WSDL.
Thanks

you can drag your external xsd to types section in WSDL file from your XSD folder then it will comes automatically
If you want to place your external xsd in XSD folder then copy that xsd and paste in XSD folder in your project directory

How to create xsd and wsdl..?

Dear All,
I am new to BPEL.
Can anyone help me on creating xsd and wsdl.
Thanks

the easiest way is using jdeveloper xsd builder to define your types ..
the wsdl itself is just a defintion of
a) types (either here or in a schema)
b) messages
c) operations (like functions)
d) and bindings .. to specify the technology ..
I would take a look on http://www.w3schools.com/WSDL/ which a tutorial ..
and then use jdev to create the things ..
hth clemens

Consuming URL renames XSD and WSDL files in OSB

We try to define a proxy service in the OSB 11g by consuming an URL.
We have all our WSDLs, XSDs etc online available, that is references like import of include in a WSDL uses URLs to identify other WSDLs or XSDs. In fact a webservice has a concrete WSDL which imports an abstract WSDL. The abstract WSDL imports XSD's. The XSD's file can import another XSD's as well. It is more or less a tree structure of XML documents.
When we try to define a proxy or business service on the concrete WSDL in Eclipse by consuming the URL ending on ?wsdl, all meaningfull names of XSD's are replaced by generated names i.e. common.xsd becomes xml_1233.xsd. And all URL references are replaced by file references. The depencency tree is preserved, everthing is still valid however the names are no longer human readable.
Is there any way to preserve the filenames of XML documents?
With kinds regards,
Jornica

Hi Anuj,
I followed this link to create the MDS connection and local MDS repository, should I create an empty composite project and place the
zip file of my xsd's in this and bundle that in to an MAR file? Are there any documents that talks about MAR creation?
Thanks,
Jai.

Extracting XSD from WSDL

Hi Everyone,
I am looking at a very simple scenario: Flat file to Web Service Through SAP XI.
I have created a web service in SAP ECC system. With the help of WSDL document of the web service i created a Message Interface(External Definitions).
On the other hand, i created the data type, message type and message interface for the flat file. Now, When i want to do the message mapping, I only have one message type.
I want to Extract XSD from the WSDL document of the webservice in order to do the message mapping. Can you help me out with this.
Thanks
chan

you dont need XSD,you can just import WSDL itself as you import XSD in the IR.but make sure you select WSDL as the structure.I mean you will have options like DTD,XSD,WSDL.here select WSDL.
and you would get the structure for the other message structure.you can use it as either Ooutbound or inbound.

XSD and WSDL in MDS

Experts,
Can someone give me the steps to create a project, add the xsd and wsld files in it and deploy the project to MDS.
Thanks,
Jai.

Hi Anuj,
I followed this link to create the MDS connection and local MDS repository, should I create an empty composite project and place the
zip file of my xsd's in this and bundle that in to an MAR file? Are there any documents that talks about MAR creation?
Thanks,
Jai.

Problem Import WSDL with XSD import Schema

Hi SCN, i have problem
I have a WSDL that references an xsd, but the structure is not visible in PI.
   <wsdl:types>
      <xsd:schema targetNamespace="http://tempuri.org/Imports">
         <xsd:import schemaLocation="http://bilbolab****.net/ServiceItemHO.svc?xsd=xsd0" namespace="http://tempuri.org/" />
         <xsd:import schemaLocation="http://bilbolab.****.net/ServiceItemHO.svc?xsd=xsd1" namespace="http://schemas.microsoft.com/2003/10/Serialization/" />
         <xsd:import schemaLocation="http://bilbolab.*****.net/ServiceItemHO.svc?xsd=xsd2" namespace="http://schemas.datacontract.org/2004/07/ItemHO.BO" />
      </xsd:schema>
   </wsdl:types>
   <wsdl:message name="iVistaHO_AddItemHO_InputMessage">
      <wsdl:part name="parameters" element="tns:AddItemHO" />
   </wsdl:message>
WSDL works well using SoapUI.
When imported to PI parameters is not displayed
I Need Help
Thank you.

Hi, Dihiansan. I don't understand your proposal
I need you see the structure in PI how in SoapUI.
It is possible?
Regards

How do I include XSD definition inside WSDL?

Hello,
I am pasting the WSDL and XSD (They were sent as a seperate files)
The Name space that was mentioned in the WSDL is different from where I am currently developing .
I would like to do the following 3 things
1. Include XSD inside WSDL definition
2. Change the existing Name space to the ones created now.
(the current name space is *http://abcd.com/SPAG*)
3. Is there any other free software that works like XML SPY?
The reference in the WSDL to the XSD is provided at "schema....... "
If I copy the XSD in place of <xsd schema></xsd schema> tabs
its generating me no message present or null exception
please help ....
The WSDL and XSD are as follows :
*WSDL* :
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/"
             xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
             xmlns:xsd="http://www.w3.org/2001/XMLSchema"
             xmlns:n="http://www.abcd.com/application/ws/network"
             xmlns:svc="http://www.abcd.com/application/ws/network/service"
             targetNamespace="http://www.abcd.com/application/ws/network/service">
     <types>
          <xsd:schema>
               <xsd:import namespace="http://www.abcd.com/application/ws/network" schemaLocation="../schema/Network.xsd"/>
          </xsd:schema>
     </types>
     <message name="NetworksRequest">
          <part name="request" element="n:Networks"/>
     </message>
     <portType name="NetworkPortType">
          <operation name="importNetworks">
               <input message="svc:NetworksRequest"/>
          </operation>
          <operation name="deleteNetworks">
               <input message="svc:NetworksRequest"/>
          </operation>
     </portType>
     <binding name="NetworkBinding" type="svc:NetworkPortType">
          <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
          <operation name="importNetworks">
               <soap:operation soapAction="importNetworks"/>
               <input><soap:body use="literal"/></input>
          </operation>
          <operation name="deleteNetworks">
               <soap:operation soapAction="deleteNetworks"/>
               <input><soap:body use="literal"/></input>
          </operation>
     </binding>
     <service name="Network">
          <port name="NetworkPort" binding="svc:NetworkBinding">
               <soap:address location="http://localhost:8080/axis/services/Network"/>
          </port>
     </service>
</definitions>
XSD :
<schema xmlns="http://www.w3.org/2001/XMLSchema"
          xmlns:n="http://www.abcd.com/application/ws/network"
          xmlns:nt="http://www.abcd.com/application/ws/networkType"
        xmlns:att="http://www.abcd.com/application/ws/entityAttribute"
        targetNamespace="http://www.abcd.com/application/ws/network"
        elementFormDefault="qualified">
     <import namespace="http://www.abcd.com/application/ws/entityAttribute" schemaLocation="../schema/EntityAttribute.xsd"/>
     <import namespace="http://www.abcd.com/application/ws/networkType" schemaLocation="../schema/NetworkType.xsd"/>
     
     <element name="Networks" type="n:Networks"/>
     
     <complexType name="Networks">
          <sequence>
               <element name="Network" type="n:Network" minOccurs="0" maxOccurs="unbounded"/>
          </sequence>
     </complexType>
     <complexType name="Network">
          <sequence>
               <element name="description" type="n:descriptionString" minOccurs="0"/>
               <element name="CustomAttributes" type="n:CustomAttributes" minOccurs="0"/>
          </sequence>
          <attribute name="name" type="n:nameString" use="required"/>
          <attribute name="type" type="nt:nameString" default="General"/>
          <attribute name="indenture" type="int"/>
     </complexType>
     <complexType name="CustomAttributes">
          <sequence>
               <element ref="att:CustomAttribute" minOccurs="0" maxOccurs="8"/>
          </sequence>
     </complexType>
     
     <simpleType name="descriptionString">
          <restriction base="string">
               <maxLength value="64"/>
          </restriction>
     </simpleType>
     <simpleType name="nameString">
          <restriction base="string">
               <maxLength value="64"/>
          </restriction>
     </simpleType>
</schema>
1. Please guide me how do I include XSD in the above structure
2. do I need to change NS in all the places in the above structure in order to change the existing name space to the current one?
3. Is there a free software that works like XML Spy in looking at webservice definitions?
Regards,
Nikhil
All useful replies will be rewarded ****

Hi Nikhil,
first include the following code into u r XSD.
<?xml version="1.0" encoding="UTF-8" ?>
- <xsd:schema targetNamespace="http://abcd.com/SAPAG" xmlns="http://abcd.com/SAPAG" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
please follow the below steps.
- <complexType name="Networks">
make it as <XSD:complexType name="Networks">
-<element name="Networks">
make it as <XSD:element name="Networks">
and similarly -<sequence>
in any XSD the following tag will be there
i.e -<xsd:annotation>
but it's not mandotory...with out that aslo we can import it as data type.
if possible, please check with alredy exiting xsd definations.
regards
mahesh.

HUGE PROBLEM: xsd:import generates invalid WSDL during deploy (11.1.1.3.0)

Hi,
I have a big problem:
if I create a bpel/mediator based on XSDs that use xsd:import, like this:
<xsd:import schemaLocation="./Generic.xsd" namespace="http://test.mydomain.com/test/Generic"/>
when i deploy, I get an error trying to test the service using oracle EM.
THe error looks like:
Either the WSDL URL is invalid or the WSDL file is not valid or incorrect. - java.io.IOException: WSDLException: faultCode=OTHER_ERROR: Lettura di WSDL da http://dev-oraclevmmac:8001/soa-infra/services/default/TestSOAProject/bpelprocess2_client_ep?XSD=./xsd/Test.xsd non riuscita: WSDL non trovato
What can I do ?

Yes, of course XSD and WSDL are valid inside JDev. I validated them also using XMLSpy.
The problem is that the WSDL becomes invalid through deployment.
But, after some hour of investigation, I've come to a solution: I have to puth the ABSOLUTE PATH ('relative' to the .bpel file) inside each xsd:import and inside wsdls.
So, my example is now:
<xsd:import schemaLocation="../xsd/Generic.xsd" namespace="http://test.mydomain.com/test/Generic"/>

XSD Namespace and WSDL Namespaces

Hi,
I have a wsdl in which I'm defining a xsd schema in the <wsdl:types> element. Can we have same targetnamespace for both (wsdl) and (xsd that is defined in wsdl <types> element) ?? Please clarify.
Thanks
Edited by: bpeltechie on Jul 5, 2012 2:17 PM

Yes, you can have the same target name space for both wsdl and schema file. Tried with a helloworld.wsdl and helloworld.xsd its valid scenario.
HelloWorldBPELProcess.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="HelloWorldBPELProcess"
targetNamespace="*http://xmlns.oracle.com/PIMtoRPASAmendment_jws/Helloworld/HelloWorldBPELProcess*"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:client="http://xmlns.oracle.com/PIMtoRPASAmendment_jws/Helloworld/HelloWorldBPELProcess"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
<wsdl:types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="*http://xmlns.oracle.com/PIMtoRPASAmendment_jws/Helloworld/HelloWorldBPELProcess*" schemaLocation="xsd/HelloWorldBPELProcess.xsd" />
</schema>
</wsdl:types>
HelloWorldBPELProcess.xsd file.
<?xml version="1.0" encoding="UTF-8"?>
<schema attributeFormDefault="unqualified"
     elementFormDefault="qualified"
     targetNamespace="*http://xmlns.oracle.com/PIMtoRPASAmendment_jws/Helloworld/HelloWorldBPELProcess*"
     xmlns="http://www.w3.org/2001/XMLSchema">
     <element name="process">
          <complexType>
               <sequence>
                    <element name="input" type="string"/>
               </sequence>
          </complexType>
     </element>
</schema>
Thanks,
Vijay
Edited by: veejai24 on 05-Jul-2012 04:03

Xsd, wsdl locations on SOA 11G Server

In SOA 11G.
What is the location/path on SOA 11G server, where I can place XSD, WSDL(of external system) and import into my Composite or BPEL process.
Thanks
Edited by: user13326981 on Oct 7, 2010 12:07 PM

Deploying a static web application is one option and the other option is to use an apache to host all the xsd and wsdl.
The advantage of apache is during development you can have the files hosted on a lighter server that is always running in the background.
These urls can then be replaced during deployment using the Config plan and build scripts.

Unable to create web service from wsdl that contains xsd as import

I have written a WSDL and tried to create the web services by weblogic workshop.
Prior to that I have created the war file and able to deploy them properly. Also able to access any wsdl by hitting the server.
But when I am trying to create the web services by weblogic workshop its throwing error as "URL is not well formed" for those XSDs which I have imported in my WSDL. I have kept all my XSDs and WSDLs in the same folder.
The WSDL has given below :
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:intf="http://soapheader.ibm.com" xmlns:impl="http://soapheader.ibm.com" xmlns:MessageContext="MessageContext" xmlns:AlertUpdateRequest="AlertUpdateRequest" xmlns:AlertFetchResponse="AlertFetchResponse" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://soapheader.ibm.com">
     <import namespace="MessageContext" location="http://localhost:7001/WebApplicationWeb/gss/xsd/MessageContext.xsd"/>
     <import namespace="AlertUpdateRequest" location="http://localhost:7001/WebApplicationWeb/gss/xsd/AlertUpdateRequest.xsd"/>
     <import namespace="AlertFetchResponse" location="http://localhost:7001/WebApplicationWeb/gss/xsd/AlertFetchResponse.xsd"/>
     <wsdl:types>
          <schema elementFormDefault="qualified" targetNamespace="http://ggg.com" xmlns="http://www.w3.org/2001/XMLSchema">
          </schema>
     </wsdl:types>
     <wsdl:message name="alertUpdateRequest">
          <wsdl:part name="parameters" element="AlertUpdateRequest:AlertUpdateRequest"/>
          <wsdl:part name="request_header" element="MessageContext:MessageContext"/>
     </wsdl:message>
     <wsdl:message name="alertUpdateResponse">
          <wsdl:part name="parameters" element="AlertUpdateRequest:AlertUpdateRequest"/>
          <wsdl:part name="request_header" element="MessageContext:MessageContext"/>
     </wsdl:message>
     <wsdl:message name="alertFetchRequest">
          <wsdl:part name="parameters" element="AlertFetchResponse:AlertFetchResponse"/>
          <wsdl:part name="request_header" element="MessageContext:MessageContext"/>
     </wsdl:message>
     <wsdl:message name="alertFetchResponse">
          <wsdl:part name="parameters" element="AlertFetchResponse:AlertFetchResponse"/>
          <wsdl:part name="request_header" element="MessageContext:MessageContext"/>
     </wsdl:message>
     <wsdl:portType name="AlertUpdateService">
          <wsdl:operation name="getAlertUpdate">
               <wsdl:input name="alertUpdateRequest" message="intf:alertUpdateRequest"/>
               <wsdl:output name="alertUpdateResponse" message="intf:alertUpdateResponse"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:portType name="AlertFetchService">
          <wsdl:operation name="getAlert">
               <wsdl:input name="alertUpdateRequest" message="intf:alertFetchRequest"/>
               <wsdl:output name="alertUpdateResponse" message="intf:alertFetchResponse"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:binding name="AlertUpdateServiceSoapBinding" type="intf:AlertUpdateService">
          <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name="getAlertUpdate">
               <wsdlsoap:operation/>
               <wsdl:input>
                    <wsdlsoap:header message="intf:alertUpdateRequest" part="request_header" use="literal"/>
                    <wsdlsoap:body parts="parameters" use="literal"/>
               </wsdl:input>
               <wsdl:output>
                    <wsdlsoap:header message="intf:alertUpdateResponse" part="request_header" use="literal"/>
                    <wsdlsoap:body parts="parameters" use="literal"/>
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:binding name="AlertFetchServiceSoapBinding" type="intf:AlertFetchService">
          <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name="getAlert">
               <wsdlsoap:operation/>
               <wsdl:input>
                    <wsdlsoap:header message="intf:alertFetchRequest" part="request_header" use="literal"/>
                    <wsdlsoap:body parts="parameters" use="literal"/>
               </wsdl:input>
               <wsdl:output>
                    <wsdlsoap:header message="intf:alertFetchResponse" part="request_header" use="literal"/>
                    <wsdlsoap:body parts="parameters" use="literal"/>
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:service name="AlertUpdateServiceService">
          <wsdl:port name="AlertUpdateService" binding="intf:AlertUpdateServiceSoapBinding">
               <wsdlsoap:address location="http://localhost:9080/SOAPHeaderWeb/services/AlertUpdateService"/>
          </wsdl:port>
     </wsdl:service>
     <wsdl:service name="AlertFetchServiceService">
          <wsdl:port name="AlertFetchService" binding="intf:AlertFetchServiceSoapBinding">
               <wsdlsoap:address location="http://localhost:9080/SOAPHeaderWeb/services/AlertFetchService"/>
          </wsdl:port>
     </wsdl:service>
</wsdl:definitions>

Hi,
From your description I am assuming that you are using JAX-WS, if not get back to me as I might have another bug to look at.
The problem is that the annotation @Oneway needs to be added to the methods in java files for this to work correctly. You can either do this manually or use the PI in the code editor. I have raised bug 6266513 to track the fact this annotation is not written out properly. I have logged bug 6266556 to track the nillable=true and extranious elements you will see when you do add @Oneway.
Thanks for the quality of your bug report, and we would of course welcome any other feedback good or bad you would like to give us.
Gerard Davison
JDeveloper Web Services Team

XSD or WSDL

Similar Messages

Maybe you are looking for