Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.


Share this Page URL
Help

Migration and coexistence > Coexistence - Pg. 31

3.2.1 Coexistence In order to make migration simpler, you can install WebSphere Message Broker V6.0 alongside WebSphere MQ Integrator V2.1. Coexistence also extends to the broker domain components. It is possible to view and administer the WebSphere MQ Integrator brokers from the Message Brokers Toolkit, which replaces the Control Center. User profiles and the Command Console Because multiple versions of the product can now exist on a single machine, a profile needs to be created to select the instance that you want to work with. This initializes the environment so that the correct commands can be invoked from the correct installation of the code. On Windows, typing a command such as mqsilist on the command line invokes the WebSphere MQ Integrator V2.1 command. In order to run the command against the WebSphere Message Broker V6.0 of the product and any V6.0 components, you have to do it using the Command Console. This is available via Start Programs IBM WebSphere Message Brokers 6.0 Command Console. It is also possible to create a customized command profile for Windows using the sample profile, which is found in the WebSphere Message Broker Information Center. On Linux and Unix platforms, an environment profile is provided in the bin directory of the install location that can be run to initialize the environment for the selected installed instance. Domain coexistence Another feature intended to make migration easier by doing it in stages is the coexistence of components. For WebSphere MQ Integrator only the broker can coexist with WebSphere Message Broker V6.0 components. This is because the Control Center and the WebSphere MQ Integrator Configuration Manager cannot administer WebSphere Message Broker V6.0 components. The Control Center, Configuration Manager, and User Name Server need to migrate to Version 6.0, but the broker can remain at Version 2.1 and still be part of a Version 6.0 domain. It is possible to maintain WebSphere MQ Integrator V2.1 brokers and to administer them and deploy to them from the Message Brokers Toolkit and the WebSphere Message Broker V6.0 Configuration Manager. The brokers must be from the following products and at least at the stated service levels: WebSphere MQ Integrator Broker V2.1 at fix pack six or later WebSphere MQ Integrator V2.1 at fix pack six or later Chapter 3. What is new for WebSphere MQ Integrator V2.1 users 31