If you are upgrading from Version 7.0 or Version 6.1, also review the following changes to see how your post-migration development tasks might be affected:
Web user interface not enabled on migrated brokers
The web user interface for Web administration, REST administration, and Integration Registry is not enabled on migrated brokers. The web user interface is enabled by default on new integration nodes (brokers) (and brokers that were created in Version 8.0.0.1 and later), but this interface is disabled on brokers that are migrated from Version 8.0.0.0 or earlier. Therefore, you cannot use REST applications, Web administration, or the Integration Registry with brokers that are migrated from Version 8.0.0.0 or earlier until you enable the web user interface for those brokers.
For information, see Enabling and disabling the web user interface.
Actions on z/OS®
An Integration Registry is introduced in IBM Integration Bus Version 9.0. The registry requires the value of the MAXMMAPAREA to be set higher than the system default. The Integration Registry is always on, and so you must tune this value, even if you are not using the registry. For more information, see Integration Registry
Subflows and broker archive (BAR) files
The default option for building new BAR files in IBM Integration Bus Version 9.0 is to package message flows as source, with ESQL files also included as source. Some existing message flows might not be compatible with this default option, but you can select a compatibility option to maintain previous behavior when you build a new BAR file. Any existing BAR files keep the previous behavior, which is to recompile ESQL into a .cmf file rather than package ESQL as separate source files.
For information about the solutions that are affected, see Adding files to a broker archive.
Applications and Libraries
You can continue to use resources from a previous version of WebSphere Message Broker by importing them into a Version 9.0 workspace. However, you cannot create a message flow project in IBM Integration Bus Version 9.0. You can continue to use message flow projects from previous versions in the same way in Version 9.0 by migrating them to integration projects. You might want to continue to use message flow projects if you are working in a team environment, for example.
For more information, see Migrating development resources to IBM Integration Toolkit Version 9.0.
Message sets
In WebSphere Message Broker Version 8.0 and later, message model schema files contained in applications, integration services, and libraries are the preferred way to model messages for most data formats. Message sets are required if you use the MRM or IDOC domains. For more information about message modeling, see Message modeling concepts.
You can import message flows containing message sets from WebSphere Message Broker Version 7.0 into IBM Integration Bus Version 9.0. Your existing message sets can be viewed, compiled, and deployed. However, by default, your message sets are accessible in read-only mode and cannot be modified.
If you need to modify your existing message sets, or create new message sets or message definition files, you must first enable message set development in the IBM Integration Toolkit.
For more information, see Enabling message set development.
Message maps
In IBM Integration Bus Version 9.0, a graphical data mapping capability is used when you add a Mapping node to a message flow.
- DataDelete
- DataInsert
- DataUpdate
- Extract
- Mapping
- Warehouse
- ESQL Compute node, which contains an ESQL CALL statement that invokes a message map .msgmap
- The Version 6.1 or Version 7.0 message map operations are accessible only n read-only mode, and cannot be modified. To modify the transformation logic of an imported message flow that used Version 6.1 or Version 7.0 message mapping, you must convert the message map .msgmap file to a graphical data map .map file.
- To run an unconverted message map, the whole message flow or application must be deployed in a BAR file that is in compiled message format (a .cmf file) with the Compile and in-line option set. This deployment node might prevent the use of other new capabilities that require deploying as a source. For example: To use deployable subflows in a .subflow file, the solution must be deployed as source.
- The ESQL CALL statement cannot be used to invoke graphical data maps. When you convert flows that use the ESQL CALL statement, extra steps are required.
For more information, see Converting a message map from a .msgmap file to a .map file.
From IBM Integration Bus Version 9.0.0.1, the behavior of graphical data maps that are used in the flow Mapping node is altered when a broker function level is specified. When the function level is changed to 9.0.0.1 or later using the mqsichangebroker command, the graphical data maps are prepared for execution on deployment instead of when the first message is flowed through the node.
For a full list of function level changes that affect graphical data maps and how this might affect migration, see Message maps.
DFDL PIFs generated after Version 9.0.0.2 have a minimum runtime requirement of Version 9.0.0.0
In order to improve memory usage when deploying industry models, defunct information has been removed from the compiled grammar (PIF) format. This improvement means that compiled DFDL grammars from IBM Integration Bus Version 9.0.0.2 and later are not supported with runtimes from WebSphere Message Broker Version 8.0, even when a compatible function is used.
- You complete an in-place upgrade of WebSphere Message Broker Version 8.0 to IBM Integration Bus Version 9.0.0.2 or later.
- You redeploy one or more applications that use DFDL schemas while at the Version 9.0.0.2 or later level.
- You roll back the upgrade and revert to WebSphere Message Broker Version 8.0.
- You must now redeploy the applications that use the DFDL schemas that were redeployed at Version 9.0.0.2 or later, so that the DFDL grammar is recompiled at the Version 8 level. If you did not redeploy at the Version 9.0.0.2 or later level, then the grammar remained at the Version 8 compatible level.
There is no impact to users of IBM Integration Bus Version 9.0.0.1 and Version 9.0.0.0 that have moved to Version 9.0.0.2 and then back again. DFDL PIFs generated in IBM Integration Bus Version 9.0.0.2 or later have a minimum requirement of IBM Integration Bus Version 9.0.0.0.
Last updated Friday, 21 July 2017