Importing from WSDL files to create message definitions

You can add messages to a message set by importing WSDL files using either the New Message Definition File wizard or the mqsicreatemsgdefsfromwsdl command line utility.

Each WSDL file you import results in one or more new message definition file within the message set. A new message definition file is created for each namespace 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 wizard will allow you to choose a different file name.

If the message definition file already exists, you must have permitted overwriting to occur for the import to proceed, in which case the existing content is deleted and recreated.

The message set that you are importing the WSDL file into must be namespace enabled and should have an XML physical format to make the message set suitable for runtime parsing of XML messages such as SOAP.

A report file is generated during the import operation which will allow you to examine what occurred during the import process and check any errors that could have resulted.

You specify a single WSDL definition for each import operation. If the WSDL definition consists of a hierarchy of files, you need to supply the name of the file which contains the WSDL service or binding definitions. The WSDL definition being imported must contain one or more WSDL bindings for the import to proceed.

Importing using the New Message Definition File wizard

When you import using the New Message Definition File wizard, you can only specify one WSDL definition for each import operation. A WSDL definition could be held as one or more WSDL files and these will all be imported as a result of importing the definition. The WSDL definition being imported must contain one or more WSDL bindings for the import to proceed.

Importing using the command line

The WSDL command line importer (mqsicreatemsgdefsfromwsdl) can create a new 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 are the top level WSDL files and any imports are resolved using an absolute or relative location. The files are copied under the specified message set in a folder called importFiles and are not removed after the import, allowing the user to subsequently update or run validation on them in the workbench.

Physical information

An XML physical format layer is required, and must be added to an existing message set prior to importing the WSDL definition.

Related concepts
Message modeling concepts
Message definition files
Namespaces in the message model
Related tasks
Working with a message set
Creating a message definition file
Importing from WSDL
Importing WSDL definitions from the command line
Related reference
Importing from WSDL: generated objects and restrictions