Message Sets: Importing from the command line

This describes how to use the command line importer mqsicreatemsgdefs to import C, COBOL copybooks, XML DTD or XML Schema in order to populate a message set with message definitions.

Before you begin

Tip: A message set is the original container for message models used by IBM® Integration Bus. In WebSphere® Message Broker Version 8.0 and later, message model schema files contained in applications and libraries are the preferred way to model messages for most data formats. Message sets continue to be supported, and are required if you use the MRM or IDOC domains. If you need to model data formats for use in the MRM or IDOC domains, you must first enable message set development in the IBM Integration Toolkit. For more information, see Enabling message set development .

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

The command line importer allows you to create a new message set, into which the message definition files will be placed. When you create a new message set from the command line, only the logical information is created by default. However, the command line importer allows you to 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. If you want physical format information to be created as well, you must take the following steps before you invoke the mqsicreatemsgdefs command:

  1. Using the IBM Integration Toolkit, create a message set in your workspace that is to be used as a base message set.
  2. To this base message set, add the physical formats that you want to be created in your new message set.

About this task

To import C, COBOL copybooks, XML DTD or XML Schema using the command line:

Procedure

  1. Close the IBM Integration Toolkit.
    This must not be running when you use the command line importer.
  2. Invoke the mqsicreatemsgdefs command from a command prompt specifying the message set project name, path name of the source files folder, and any other optional parameters that you require. If you want to add physical formats to the new message set that the mqsicreatemsgdefs 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, open mqsicreatemsgdefs.report.txt.
    This report is created when you invoke the mqsicreatemsgdefs 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 mqsicreatemsgdefs was invoked.
    • The message set level action.
    • The name of the file or files that have been imported.
    • Details of the import process (for example, any warnings that have been generated and message model objects that have been created).
    • The number of files imported.
  4. Start the IBM Integration Toolkit and switch to the Integration Development perspective.
    The message definition file that was created when you invoked mqsicreatemsgdefs is visible in the project that you specified.

Results

If an error occurs during the import of a C, COBOL copybook, XML DTD, or XML Schema file, carefully check any errors that the importer reports. By default, all errors are written to the screen and to the log 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.