IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Calling services > WSDL import and export files
Importing WSDL or XSD files
Importing Web Services Description Language (WSDL) files or XML Schema Definition (XSD) files into a module or library through an import function are discussed.
To import WSDL or XSD files into a module, right-click the module or library name in the Business Integration navigation view, and select Import from the menu. In the Import window, select WSDL and XSD and click Next. The Import a WSDL, XSD or Both wizard opens. Alternately, from the menu, you can select File > Import. In both cases if a module is selected then it will be preselected as the module for the imported files. If no module is selected, then you must select the module from the list available or create a new module.
Choose between importing a local WSDL or XSD file, which also lets you import both, or a remote WSDL or XSD file. Importing locally means the file is on your file system Importing remotely means that the file is on a remote location that can be accessed through a URL address.
- In the case of making the Local WSDL or XSD, or both selection, browse to the WSDL or XSD file and select the file or files. The Import dependent resources option, which is preselected, lets you see the references to the file you want to import in the lower pane. You can complete your import at this point by selecting Finish.
The Target module or library field indicates where the file or files will be sent. If you selected a module or library, you will see the name in the field. You can also choose another module or library or create a new one.
Selecting Download remote resources lets you also import the references your file may have. Clicking Next shows you the URL addresses of the remote references. You can select them if you want and complete the import by clicking Finish.
The imported file structure is preserved with respect to referenced files.
For example, suppose you had a file folder /customer containing PreferredCust.xsd and a file folder structure /customer/interface containing CustomerType.wsdl, which referenced PreferredCust.xsd. If you imported CustomerType.wsdl then the imported structure would have a root directory based on /customer (not /customer/interface).
Selecting Extract inline elements (both interfaces and inline business objects) lets you extract any inline elements into separate files at the point of your import. If you do not make this selection, your inline elements will have a decorator beside their name after you perform the import.
You can perform extraction later.
- In the case of making the Remote XSD or WSDL file selection, the interaction is similar to the Download remote resources selection. In the URL field, enter the URL address of the remote computer.
The Target module or library field indicates where the file or files will be sent. If you selected a module or library, you will see the name in the field. You can also choose another module or library or create a new one.
Separate inline business objects lets you separate inline XSD elements into business objects at the time that you import the file. If you do not make this selection, your inline elements will have a decorator beside their name after you perform the import. You can perform extraction later.
Separate interfaces (port types) from the other WSDL elements lets you extract the interface from a file. This feature is useful if you plan to use mediation or some other processing using these files and then want to have that work referred to from the same interface.
Related tasks:
Interoperability with services from other vendors
Export WSDL files
Related reference:
WSDL binding styles