The topics in this section explain the extent to which WebSphere Business Integration Event Broker Version 6.0 can coexist with previous versions and other products.
For information about WebSphere Business Integration Event Broker Version 6.0 coexisting with another instance of WebSphere Business Integration Event Broker Version 6.0 on the same system, see [LINK TO V6/V6 COEXISTENCE CONCEPT TOPIC]
WebSphere Business Integration Event Broker Version 6.0 can coexist with either a Version 2.1 or a Version 5.0 product on the same system.
You cannot install both a Version 2.1 and a Version 5.0 product on the same system, and you cannot install several instances of either Version 2.1 or Version 5.0 products on a single system.
When you migrate from a Version 2.1 or a Version 5.0 product to WebSphere Business Integration Event Broker Version 6.0, you do not need to uninstall the Version 2.1 or Version 5.0 product before installing WebSphere Business Integration Event Broker Version 6.0. You can install WebSphere Business Integration Event Broker Version 6.0 in a different location on the same system, migrate your components and resources to WebSphere Business Integration Event Broker Version 6.0, and uninstall the Version 2.1 or Version 5.0 product later when you are sure that you no longer require it.
Compared to a situation where the product that you are migrating from and the product that you are migrating to cannot coexist on the same system, your hardware requirements during migration might be reduced, especially if it is important to maintain high availability during migration.
With some restrictions, all Version 5.0 components can participate in a Version 6.0 broker domain and all Version 6.0 components can participate in a Version 5.0 broker domain. A Version 2.1 broker is the only Version 2.1 component that can take part in a Version 6.0 broker domain.
Coexistence of Version 6.0 components with components from previous versions means that you do not have to migrate all of your components at the same time. Instead you can migrate those components that can coexist with Version 6.0 components in stages.
Can the components operate together in a domain? | Version 6.0 Message Brokers Toolkit | Version 6.0 Configuration Manager | Version 6.0 broker | Version 6.0 User Name Server |
---|---|---|---|---|
Version 5.0 or Version 5.1 Message Brokers Toolkit | Yes1 | Yes | Yes | Yes |
Version 5.0 Configuration Manager | Yes | (Not applicable) | Yes | Yes |
Version 5.0 broker | Yes2 | Yes | Yes | Yes |
Version 5.0 User Name Server | (Not applicable) | Yes | Yes | (Not applicable) |
Version 2.1 Control Center | No | No | No | No |
Version 2.1 Configuration Manager | No | (Not applicable) | No | No |
Version 2.1 broker | Yes3 | Yes3 | Yes3 | Yes3 |
Version 2.1 User Name Server | (Not applicable) | No | No | (Not applicable) |
You can create and operate a heterogeneous network of MQSeries Publish/Subscribe brokers and WebSphere Business Integration Event Broker brokers. You can also migrate MQSeries Publish/Subscribe brokers to WebSphere Business Integration Event Broker brokers. For more information, see Migrating publish/subscribe applications.
You cannot [CHECK THIS WHEN FEATURE DOC IS APPROVED] install WebSphere Business Integration Event Broker and WebSphere Business Integration Message Broker as separate products on the same system. WebSphere Business Integration Message Broker, however, contains all the function of WebSphere Business Integration Event Broker.
[RELATED LINKS: Instances concept topic, V6/V6 coexistence concept topic]
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ah23930_ |