See information about the latest product version
Perform post-migration tasks
After you migrate to WebSphere® Message Broker Version 8.0, finish setting up your environment.
Test the WebSphere Message Broker Version 8.0 broker resources and components to verify that you experience no loss or unexpected change of functionality. Some changes in behavior might be caused by defects that were fixed between versions.
The following topics describe further tasks that you can complete after migration:
- Reviewing technical changes in WebSphere Message Broker Version 8.0
- Migrating deployable resources
- Setting up a command environment
- Migrating a flow that contains JMS nodes
- Migrating a flow that contains File nodes
- Migrating a flow supporting ?wsdl queries
- Migrating Message Broker API applications
- Updating error processing routines
- Delete the Version 7.0 or Version
6.1 components (Version
6.1 Configuration Manager, Version
6.1 User
Name Server,
and brokers that you replaced but did not migrate)..
If the broker that you migrated shares a queue manager with the Version 6.1 Configuration Manager, the default server connection channel SYSTEM.BKR.CONFIG, which was created when you created the Configuration Manager, is deleted when you delete the Configuration Manager. The Version 8.0 broker requires this channel for connections from the WebSphere Message Broker Explorer, the WebSphere Message Broker Toolkit, and CMP applications. You must re-create this channel on the broker queue manager after you delete the Configuration Manager.
- Remove the installed code for Version 7.0 or Version 6.1.
- Delete the broker database from Version 6.1. You can also remove the installed database product, if you do not use it for other purposes.
Access the Version 7.0 or Version 6.1 information center for details of these tasks.