mqsimigratemsgflows command

Supported platforms

  • Windows
  • Linux (x86 platform)

Purpose

Use the mqsimigratemsgflows command to create new flows in the WebSphere Message Broker Version 6.0 format, based on existing exported flows from a WebSphere MQ Integrator Broker Version 2.1 Configuration Manager.

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 .msgflow files into the Version 6.0 workspace and when you save the files they are saved in Version 6.0 format.

    In addition, you can use this command to deploy exported user-defined node definitions from Version 2.1 to Version 6.0. To recreate the user-defined nodes in Version 6.0 you must manually redefine them.

  3. Stop your Message Brokers Toolkit session before you invoke the command.
  4. Specify the workspace location using the -data flag.
If your path contains spaces, enclose the entire path name in double quotation marks.

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

-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.

-p ProjectName
(Required) The project name where the new flows are created. If the project already exists, the flows are added to this project. If the project does not exist, this command creates it.
-d DirectoryPath
(Required) The directory path where the exported flows can be found.

A relative path is interpreted from the current working directory. You can specify a full path. All nested directories are ignored.

The flow name becomes the name of the .msgflow file. You can change this name to meet the local file naming conventions.

Duplicate message flows are ignored; any error of this form is reported in the migration report file.

-rm
(Optional) Replace message flow projects if they already exist.
-log <filepath>
(Optional) Report file.

If you do not specify an alternative, this command generates a detailed migration log in the <install_dir>/eclipse/ folder. The log-file has the default name of "mqsimigratemsgflows.report.txt".

For further information on flow migration, see Migrating message flows from Version 2.1.

Authorization

No specific authority is required to invoke this command.

Examples

mqsimigratemsgflows -p sample -d c:\wmqi\test