Subtopics
- Reviewing technical changes in IBM Integration Bus Version 9.0
Some minor changes in behavior are present in IBM Integration Bus Version 9.0 if you are migrating from Version 7.0 or Version 6.1; for example, those changes that are caused by defects that were fixed between versions. - Migrating deployable resources
You can continue to use legacy resources in IBM Integration Bus. However, if you want to continue developing resources created in WebSphere Message Broker Version 6 and Version 7, you must migrate them. - Setting up a command environment
After you have installed the product on one of the distributed systems, you must initialize the environment before you can use a runtime component or command. - Migrating a flow that contains JMS nodes
When you migrate a message flow from Version 7.0 that contains JMS nodes, you might have to update the value of the Transaction mode property. - Migrating a flow that contains File nodes
If you migrate message flows that contain File nodes to IBM Integration Bus Version 9.0, ensure that your NFS server appropriately supports file locking. - Migrating a flow supporting ?wsdl queries
If you want WSDL and XML Schema information to be made available for existing SOAPInput-SOAPReply flows that implement web services, you must explicitly set the SOAPInput node property Enable support for ?wsdl and redeploy the flow. - Migrating CMP applications
If you have applications that use the IBM Integration API (CMP), check that they access the correct resources. - Updating error processing routines
Update your message processing to handle new or reused messages, and to delete obsolete messages.
Parent topic: Migrating
Related concepts:
Related tasks:
Related reference:
Last updated Friday, 21 July 2017