mqsimigratemsgsets command

Supported platforms

  • Windows
  • Linux (x86 platform)

Purpose

The mqsimigratemsgsets command imports all the files with the extension .mrp in the directory specified by the -d parameter. Files with any other extension are ignored.
Note:
  1. This command is for one way migration to the WebSphere Message Broker Version 6.0 Message Brokers Toolkit from the Version 2.1 release.
  2. When you migrate from Version 5.0 to Version 6.0 you need load only the Version 5.0 message set projects into the Version 6.0 workspace and when you save the projects they are saved in Version 6.0 format.
  3. Stop your Message Brokers Toolkit session before you invoke the command.
  4. If you are importing a very large .mrp file, you might find that the mqsimigratemsgsets command ends with a Java OutOfMemoryException.

    If your -d directory contains several .mrp files, try running the command repeatedly, each time with the -d directory holding a single .mrp file.

    Alternatively you can increase the amount of memory available using the mqsimigratemsgsets argument -vmargs -Xmx<nnn>M, where <nnn> is the number of megabytes of memory. For example:
    mqsimigratemsgsets ... -vmargs -Xmx256M

A report file with a default filename of mqsimigratemsgsets.report.txt is produced as a record of the command invocation. You can specify the -log parameter to override the default name and location for the report file; and the -v parameter to add additional information to the report file.

On Windows operating systems, the mqsimigratemsgflows.exe file is located in the <toolkit install>/eclipse directory. Similarly, on the Linux (x86 platform) operating system, the mqsimigratemsgflows file is located in the <toolkit install>/eclipse directory.

Syntax

Parameters

In most cases, you will need to use only the -d and -data parameters to specify the location of the .mrp files and the workspace.

-d <Directory>
(Required) The directory path, either absolute or relative, containing the .mrp files to import.
-data <workspacepath>
(Required) The path of the workspace in which your projects are created.

The workspace location is also the default location for projects. Relative paths are interpreted as being relative to the directory from which the command was started.

-rm
(Optional) Replace message set projects if they already exist. If the message set project already exists, a warning message is issued if this parameter is not specified and the .mrp file is ignored.
-g
(Optional) Always create global elements and global complex types.
-pl
(Optional) For elements with prefixed identifiers, always create local elements even when referenced more than once. Only use this option if BIP0195 warning messages appear in the report file, and associated duplicate element errors appear in the task list after import.
-log <filename>
Optional) Name and location of the generated report file
-v
(Optional) Instructs the importer to produce a verbose report detailing exactly what was created.
-part
(Optional) Partition the message sets into multiple .MXSD files, if the message set is large enough to warrant partitioning.

For information on what this command creates, and other points that you need to be aware of, see Migrating Message Sets from Version 2.1.

Authorization

No specific authority is required to invoke this command.

Examples

mqsimigratemsgsets -d c:\wmqi\test -v
mqsimigratemsgsets –d c:\wmqi\test –v –pl 
Related concepts
Message modeling concepts