IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Message Sets: Importing WSDL definitions from the command line

WSDL definitions can be imported using the (mqsicreatemsgdefsfromwsdl) command.

Before you start:

Before you attempt this task, read the following information:

mqsicreatemsgdefsfromwsdl command.

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 message set that is namespace enabled.

If you are adding new message definition files to an existing message set, the message set must have an XML physical format layer. To improve Web services interoperability, avoid unnecessary customization of the XML physical format layer for messages that participate 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:

Create a new message set based on an existing message set. The physical format information from the base message set is also created in the new message set.
Use the IBM® Integration Toolkit to create or open the message set and directly add the physical formats to the message set prior to importing the WSDL definitions into it.

Before starting the import, the mqsicreatemsgdefsfromwsdl command copies the WSDL files that it needs into the workspace. These are the top level WSDL file and any further files that might 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 finishes. This allows you to update them, or run validation on them, in the IBM Integration Toolkit at a later time.

To import WSDL definitions using the command line:

Close the IBM Integration Toolkit. The IBM Integration Toolkit must not be running when you use the command line importer.
Invoke the mqsicreatemsgdefsfromwsdl command from a command prompt; you must specify 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.
When the command has completed, check the log file. The name of the log file is the name that you specified in the command, and it has the file extension *.wsdl.report.txt. This report is created when you invoke the mqsicreatemsgdefsfromwsdl command and, by default, it 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).
Start the IBM Integration Toolkit and switch to the Integration Development perspective. The message definition file that was created by the mqsicreatemsgdefsfromwsdl command is visible in the project that you specified.

If an error occurs during the import of a WSDL definition, carefully check any errors that are reported. By default, all errors are written both 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.

ad30510_.htm |

Last updated Friday, 21 July 2017