Importing WSDL definitions from the command line

This describes how to how to use the WSDL command line importer (mqsicreatemsgdefsfromwsdl) to populate a message set with message definitions.

Before you start:

Before you attempt this task, you should read the following information:

The WSDL command line importer allows you to create a new namespace enabled message set, into which the message definition files will be placed. It also allows you to add message definition files to an existing namespace enabled message set which must be namespace enabled.

If you are adding new message definition files to an existing message set, it should also have an XML physical format layer. In order to improve web services interoperability, you should avoid unnecessary customization of the XML physical format layer for messages participating in web services processes.

When you create a new message set from the command line, only the logical information is created by default. If you require physical formats in the message set you have two options:

The mqsicreatemsgdefsfromwsdl command copies the WSDL files it needs into the workspace before the import runs. These are the top level WSDL file and any further files that may be imported by it. 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.

To import WSDL definitions using the command line:

  1. Close the workbench. This must not be running when you use the command line importer.
  2. Invoke the mqsicreatemsgdefsfromwsdl command from a command prompt specifying the message set project name, the path name of the directory where the top level WSDL file is located, the name of that file, the location of the workspace, and any other optional parameters that you require. If you want to add physical formats to the new message set that the mqsicreatemsgdefsfromwsdl command creates, specify the base message set that contains these physical formats as the -base parameter on the import command line.
  3. When the command has completed, check log file. It has the file descriptor *.wsdl.report.txt and the name will be the one you specified in the command. This report is created when you invoke the mqsicreatemsgdefsfromwsdl command and by default is written to the directory from which you invoked the command. The report provides you with the following information:
    • Details of the parameters that were used when mqsicreatemsgdefsfromwsdl was invoked.
    • The name of the file that has been imported.
    • Details of the import process (for example, any warnings that have been generated and message model objects that have been created).
  4. Start the workbench and switch to the Broker Application Development perspective. The message definition file that was created when you invoked mqsicreatemsgdefsfromwsdl is visible in the project that you specified.

If an error occurs during the import of a WSDL definition, carefully check any errors that the importer reports. By default, all errors are written to the screen and to the file described above. To gather additional information about the import, specify the -v (Verbose) command line parameter. This parameter displays more detailed information as the import proceeds.

Related concepts
Ways to create message definitions
Importing from other model representations to create message definitions
Related tasks
Working with a message set project
Creating a message set
Related reference
mqsicreatemsgdefsfromwsdl command
mqsicreatemsgdefs command
Import formats