Differences between Version 2.1 and Version 6.0 products

The following table outlines the main differences between the Version 2.1 and Version 6.0 products:
Version 2.1 Version 6.0 Why has this changed?
Installing the product
In Version 2.1, there can be only one copy of the product installed on the computer. You can install the Version 6.0 product alongside the Version 2.1 product and the two products can run side-by-side. The new mqsimigratecomponents command allows you to migrate components from Version 2.1 to Version 6.0. Permitting Version 6.0 to coexist with Version 2.1 allows for easier migration.
Entering commands on Windows
You enter Version 2.1 commands in a command window. You enter Version 6.0 commands in the Command Console, which is in the Start menu: Start > Programs > IBM WebSphere Message Brokers 6.0 > Command Console. Multiple versions of the product can now coexist. The Command Console ensures that the commands that you enter are directed to the correct version.
Configuration Manager Database Requirements
You must specify two data sources when creating a Version 2.1 Configuration Manager: a configuration database for message flow source and domain information, and an MRM database for message dictionary source.

When deleting a Configuration Manager, there are flags to remove the contents of these repositories (-n and -m for the configuration and MRM sources respectively).

There are no database requirements on the Configuration Manager.

Source data for both message flows and dictionaries is now stored inside the Eclipse workspace. Domain information is stored in an internal configuration repository in the file system on the Configuration Manager computer, and there are commands to back up and restore this repository (mqsibackupconfigmgr and mqsirestoreconfigmgr).

When you delete a Configuration Manager, the -n parameter now removes the contents of the internal repository and the -m parameter is ignored.

Removing the requirements on an external database simplifies the setup and administration of a Configuration Manager.
Starting the Control Center
When you start the Control Center, a prompt opens for the connection details of the Configuration Manager. The Control Center is now called the Message Brokers Toolkit and is based on the Eclipse framework.

To connect the Configuration Manager, you must create a connection file by clicking File > New > Other > Broker Administration > Domain.

Each set of Configuration Manager connection parameters is a file stored within the Eclipse workspace.

This allows you to share connection details more easily among multiple users, and allows you to manage multiple domains from a single Message Brokers Toolkit.

Displaying information in the Control Center
The Version 2.1 Control Center contains a set of tabs that determine the type of information that is shown (for example, assignments, topology, topics, subscriptions). In Version 6.0, there are two main screens of information (called perspectives):
  • Broker Application Development perspective, which allows you to create and edit message flows and message sets.
  • Broker Administration perspective, which shows you the state of the domain, as reported by the Configuration Manager, and allows you to manipulate it.

It is possible to switch perspectives using the Window menu.

The concept of perspectives is inherited from the Eclipse framework and allows you to switch easily to the information set that is most relevant to what you are doing.
Modifying message flows
In Version 2.1, message flows under development are stored in the Configuration Manager. In order to modify them, you must check them out, make your changes and then check them back in. In Version 6.0, message flows are created and modified in an Eclipse workspace; by default, this is on the file system on which the Message Brokers Toolkit is installed. Storing development objects in an Eclipse workspace allows you to manage them more effectively. Plug in third-party change-management tools into the Eclipse framework to provide better change control.
Assigning and deploying message flows and message sets
In Version 2.1, message sets were assigned to brokers and were available to all execution groups in that broker, and message flows were assigned to execution groups. When this is done, the deploy action causes the Configuration Manager to send the assigned message flows to the correct execution group. In Version 6.0, message flows and message sets are packaged in broker archives (bar files). These archives use a zipped file format to envelop a set of deployable objects.

To deploy a bar file to an execution group, use the Broker Administration perspective to drag and drop the bar file to the required execution group.

Bar files provide a transferable package of deployment, so that the same message flow logic can be applied to multiple brokers and domains.

Similar deployment concepts are used in other products.

Monitoring message flows
In Version 2.1, traffic lights show the run state of message flows. In Version 6.0, the Broker Administration perspective has an Alerts view that identifies any broker, execution group or message flow that is not running. The use of the Alerts view is consistent with other tools in the Eclipse framework and provides an accessible way of notifying you if anything is not processing messages as expected.
User roles    
In Version 2.1, several Windows user groups in the Configuration Manager are used to describe the typical role, and domain access, that each user has (for example, mqbrkrs, mqbrops, mqbrtpic, mqbrasgn). Membership of the mqbrkrs group is still required for administration of the broker component, but the mqsicreateaclentry command is now used to define specific user or group access control lists (ACLs) for each component (such as brokers and execution groups). Access control lists (ACLs) in the Configuration Manager allow administrators to control access to the domain at a much finer level of granularity.
Related concepts
Coexistence with previous versions and other products
New in Version 5.0
Product overview
Related tasks
Migrating from Version 2.1 products
Related reference
Migration and upgrade
mqsimigratecomponents command
mqsibackupconfigmgr command
mqsirestoreconfigmgr command
mqsicreateaclentry command