When you have completed migration from Version 5.0, you can remove resources from the computer.
Before you start
Make sure that
the migration was successful and that you no longer need to retain the flexibility
to use WebSphere® Event
Broker Version 5.0 code
and resources.
To remove unwanted files and database tables
after migration:
- If you no longer need WebSphere Business
Integration Event Broker Version 5.0,
remove it from the computer. Refer to the WebSphere Business
Integration Event Broker Version 5.0 information
center for instructions about uninstalling the product.
- If you no longer use prerequisite software products that are required
by Version 5.0 but not for Version 6.0, remove them. For example, DB2® might no longer be required. For
instructions, refer to the documentation for those products.
- If you do not remove DB2,
you might want to remove the DB2 database
tables used by Configuration
Manager Version 5.0.
In Version 6.0, the Configuration
Manager stores the domain configuration
in an internal repository instead of an external database. Therefore you cannot
use your Version 5.0 Configuration
Manager DB2 database tables with the Version 6.0 Configuration
Manager.
To
remove the
Configuration
Manager DB2 database
tables, drop the following database tables by using the
DB2 DROP
TABLE command. If the
Configuration
Manager tables
are in a
DB2 database by themselves,
drop the whole database by using the
DB2 DROP
DATABASE command.
- CACLGROUPS
- CBROKER
- CBROKERCEG
- CCOLLECTIVE
- CCOLLECTIVECBROKER
- CDELETE
- CEG
- CEGCMSGFLOW
- CEGCMSGPROJECT
- CLOG
- CMSGFLOW
- CMSGPROJECT
- CNEIGHBOURS
- COUTSTANDING
- CPROXY
- CPROXYCRESOURCE
- CSUBSCRIBE
- CTOPIC
- CTOPICCTOPIC
- CTOPOLOGY
- CTRACE
- CUUIDLOCKS