Importing XSDs and WSDLs into Business Objects

If your processes need to manipulate structured data whose structure is defined in XSD files or WSDL files, the structure of the data can be imported into the Business Objects folder.

Note: This is only done on WSDL files if you are not going to call the interfaces in the web service defined in the WSDL file. If you intend to call the interfaces, import the WSDL as described in Importing WSDLs into the Service Descriptors Folder .

Once the import has completed, you can explore the data structures that have been imported in the Business Objects folder. Structured data can also be manipulated in scripts in the same way as user-defined BOMs.

If you modify these imported BOMs, the copy of the definitions in TIBCO Business Studio will differ from the source that they came from, causing TIBCO Business Studio to display a warning.

Despite the warning, this mismatch is normal if you have data types that are defined in an external system, then imported and extended to cope with known and future requirements. The following is an example of how this might be used: If you have an existing database, the structure of its tables can be exported into an XSD file, which can then be imported into TIBCO Business Studio. The information about the table structure can be used in tasks that interact with the database.

Once the data structure in the XSD (or WSDL) file has been imported into a BOM, web services can be defined and WSDLs generated for other applications to invoke the new web services that use the structured data from the imported files.