ad30550_.htm |
Last updated Friday, 21 July 2017Import WSDL files by using the New Message Definition File From WSDL file wizard, the Start from WSDL and/or XSD files Quick Start wizard, or the mqsicreatemsgdefsfromwsdl command.
Each WSDL file that you import results in one or more new message definition files within the message set. A new message definition file is created for each namespace that is defined for the message set. The name of the message definition file defaults to the name of the WSDL file, but the New Message Definition File From WSDL file wizard allows you to choose a different file name.
If the message definition file exists, you must have permitted overwriting to occur for the import to proceed. The existing content is deleted and re-created.
The message set that you are importing the WSDL file into must be namespace-enabled. If it uses the MRM domain, it must have an XML physical format so that the message set is suitable for the runtime parsing of XML messages such as SOAP.
Use the report generated during the import operation to see what happened and to check any errors.
You specify a single WSDL definition for each import operation. If the WSDL definition consists of a hierarchy of files, you must supply the name of the file that contains the WSDL service or binding definitions. The WSDL definition that is imported must contain one or more WSDL bindings for the import to proceed. You can then select multiple bindings from the WSDL definition to define messages to model in the message set.
When you import by using the New Message Definition File wizard, you can specify only one WSDL definition for each import operation. A WSDL definition can be held as one or more WSDL files, which are all imported as a result of importing the definition. The WSDL definition that is imported must contain one or more WSDL bindings for the import to proceed.
The WSDL command-line importer (mqsicreatemsgdefsfromwsdl) can create a message set or update an existing one. If the message set project exists, it must be namespace-enabled and have an XML physical format layer. If the project does not exist, a new namespace-enabled project is created. If the import succeeds, new message definition files are added to the message set.
The mqsicreatemsgdefsfromwsdl command allows you to import one WSDL definition in a single operation.
The mqsicreatemsgdefsfromwsdl command copies the WSDL files it needs into the workspace before the import runs. These files are the top-level WSDL files and any imports are resolved by using an absolute or relative location. The files are copied under the specified message set in a folder called importFiles. They are not removed after the import; the user can later update or run validation on them in the IBM® Integration Toolkit.
An XML physical format layer is required for the MRM domain, and must be added to an existing message set before importing the WSDL definition.
Last updated Friday, 21 July 2017