What else is new if you are migrating from WebSphere Message Broker Version 7.0?

You can use the IBM Integration Bus web user interface to administer integration node resources. The web user interface enables web users to access integration node resources through an HTTP client, and provides integration administrators with a way to administer integration node resources. The web user interface is enabled by default for new integration nodes.

For more information, see IBM Integration Bus web user interface.

IBM Integration Bus supports the REST management API for integration node administration.

For more information, see Representational State Transfer (REST) API.

For more information, see Converting existing projects to applications and libraries.

Web services are now a first-class artifact in IBM Integration Bus. You can create web services in the new Services editor, and implement the operations as message flows.

For more information, see Developing integration solutions by using integration services.

You can now export mapping information from Compute nodes, for use in impact analysis and data lineage operations in products such as IBM InfoSphere® Metadata Workbench. See Exporting mapping information from Compute nodes.

An optional property that controls whether the integration node connects to a database server by using XA Protocol. For more information, see Setting up a JDBC provider for type 4 connections.

For more information, see Creating a multi-instance integration node.

For more information, see Data Analysis.

When you design a message flow that handles large messages that are made up of repeating structures, you can code Java methods that help to reduce the storage load on the integration node.

For more information, see Working with large input messages to propagate multiple output messages.

For more information, see Data caching overview.

IBM Integration Bus Developer Edition is a full function version of the product, which you can use for evaluative purposes. You can download the Developer Edition at no charge and you are free to use it for as long as you require, within the terms of the license.

Developer mode is introduced with the Developer Edition. All integration nodes that you create in theDeveloper Edition are created in Developer mode by default.

There is no longer a Trial Edition for IBM Integration Bus.

Developer Edition is restricted to processing one message per second.

For more information, see Operation modes.

Enable the new capability by using the-f parameter on the mqsichangebroker command, as described in mqsichangebroker command. You must stop the cache before you can enable the capability for the integration node.

For more information, see WebSphere eXtreme Scale grids.

By default, each server starts with a domain name that is derived by the integration node. In previous versions of WebSphere Message Broker, the domain name for all servers in all embedded caches was an empty string. Servers in different domains cannot collaborate in the same grid. Therefore, for a cache that spans more than one integration node, you must enable the new capability for these integration nodes at the same time.

integration nodes on IBM Integration Bus Version 10.0 can still collaborate in the same grid as integration nodes on WebSphere Message Broker Version 8.0.0.2 or earlier. In this scenario, the capability should not be enabled on the WebSphere eXtreme Scale servers, and then the servers continue to use an empty string as the domain name; servers report aBIP7140 warning message to the system log with this information.

Enable the capability by using the-f parameter on the mqsichangebroker command, as described in mqsichangebroker command.

For more information, see Configuring the embedded global cache by using commands.

You can specify how long data exists in the global cache by setting a time to live value. You specify this value when you get an MbGlobalMap object. The value applies to all cache entries that are created by using that MbGlobalMap object in that instance of the JavaCompute node. After the specified time, the affected data is removed from the global cache automatically.

Enable the new capability by using the -f parameter on the mqsichangebroker command, as described in mqsichangebroker command. You must stop the cache before you can enable the capability for the integration node.

For more information, see Embedded global cache.

Scale mode provides support for unlimited integration servers and a defined subset of nodes. In Scale mode, you can create multiple integration nodes and deploy message flows containing the supported nodes to your integration servers.WebSphere Enterprise Service Bus customers can obtain a transfer license, which enables them to migrate to IBM Integration Bus and to create and run integration nodes in Scale mode.

For more information, see Operation modes.

An optional property that assigns additional processing threads to enable processing of timed out aggregation messages in the AggregateReply node. For more information, see Processing timed out aggregation messages.

For more information, see Resource management overview.

For more information, see Managing integration nodes by using the IBM Integration API.

Create table parameter types for your user-defined patterns. For more information, see Using tables for pattern parameters.

The improved graphical mapping is high-performing, scalable, and dynamic.

Graphical data maps enable you to create transformations that take an input message assembly and build a required output message assembly. For more information, see Using message maps.

• New DFDL message modeling support

  You can use the Data Format Description Language(DFDL) support in IBM Integration Bus to model the structure of general text and binary formatted messages in a way that is independent of the message format.

  For more information, see Data Format Description Language (DFDL).

• New DFDL schema editor

  You can use the DFDL schema editor to create, edit, and test DFDL message models within the IBM Integration Toolkit.

  For more information, see DFDL schema editor.

• New DFDL domain

  You can use the DFDL domain to parse and write a wide variety of message formats that have a DFDL message model. The DFDL domain is primarily intended for non-XML message formats.

  For more information, see DFDL parser and domain.

• New .NETCompute node

  You can use the Microsoft .NET Framework (.NET) support in IBM Integration Bus to host and run .NETapplications and code from inside an integration server.

  The .NETCompute node routes or transforms messages by using any Common Language Runtime (CLR) compliant .NET programming language, such asC#, Visual Basic (VB), F# and C++/CLI (Common Language Infrastructure). By using this node, the integration node can interact with other applications that have .NET or Component Object Model (COM) interfaces and perform tasks such as message enrichment, by obtaining data from these applications.

  For information about configuring and using the .NETCompute node, see .NETCompute node and Using .NET.

• ESQL enhancements

  .NET methods can be called directly from ESQL.

  For more information, see CREATE FUNCTION statement and CREATE PROCEDURE statement.

For more information, see Using Activity Logs.

For more information, see Editing configurable properties in a BAR file.

For more information, see Subflows.

For more information, see Deploying an ESQL file.

For more information, see Configurable services.

For audit purposes or problem determination, you might want to keep a record of messages that pass through a message flow. You can record those messages in a database, then view them. For more information, see Recording, viewing, and replaying data.

For more information, see JMSReceive node.

You can view your integration node resources, including web services, by using IBM Integration Bus administration for WebSphere Application Server. See Administering integration nodes from WebSphere Application Server.

You can import C header files; see Creating a DFDL schema file by using the New Message Model wizard. Field length prefixes are supported.

You can modify database content from your Graphical Data Maps; see Modifying data in a database by using mapping .

You can also convert a message map from a previous version of IBM Integration Bus to a graphical data map; see Converting a message map from a .msgmap file to a .map file.

You can configure your integration servers so that the SOAP nodes use the integration node HTTP listener to process HTTP messages, rather than the integration server listener. Using the integration node listener can simplify the administration of your integration node configuration. For more information, see HTTP listeners.

Use new HTTP asynchronous nodes to call an HTTP web service and receive an asynchronous response without blocked waiting. For more information, see Using HTTP asynchronous request-response.

You can also use HTTP asynchronous response-request behavior instead of WS-Addressing with the SOAPAsyncRequest node to make HTTP requests and receive an asynchronous response. For more information, see Choosing asynchronous behavior for the SOAPAsyncRequest node.

You can generate port and URL data from your integration nodes to use for connecting to a web server such as IBM HTTP Server. You can also generate configuration files for WebSphere Application Server plug-ins or Apache mod_proxy modules to use for connecting to web servers. For more information, see Using external web servers with IBM Integration Bus.

You can use Java Architecture for XML Binding (JAXB) with a JavaCompute node to process your messages by accessing, creating, and manipulating JAXB Java object classes that you generate from your message model schema files. For more information, see Using JAXB with a JavaCompute node.

• Integration server classloading allows only a single defined integration server to access and load any JAR files that are placed in the integration servershared-classes directory.
• Integration node-level classloading allows only a single defined integration node to access and load any JAR files that are placed in integration node level shared-classes directory.

A new classloading precedence order is also defined.

For more information, see Java shared classloader.

You can now specify a Java classloader in your ESQL to use for loading your Java methods. For more information, see Configuring classloaders for ESQL routines.

You can now create a .NET application domain to package .NET assemblies, and other associated resources, in a BAR file. The .NET application domain is deployed to the run time as a first-class object.

For more information, see .NET application domains.

For more information, see Local environment overrides for the remote server on the FileOutput node.

You can control access to integration node resources through the web user interface and the RESTful application programming interface(API). As an integration administrator, you can create web user accounts. The web user accounts have security permissions that are based on their role, which is an associated system account. The permissions are checked to determine the users' authorization to complete tasks in the web user interface or the RESTful application programming interface (API).

The record and replay capability is enhanced to include support for Oracle databases and role-based security, and enhancements to the web user interface for viewing and replaying data.

You can use the mqsiwebuseradmin command to administer user accounts for the web user interface. You can use this command to create or remove a web user, set or change a web user's password,or assign a web user account to a role.

You can view the full content of a runtime BIP message, including the user response and explanation sections, by using the mqsiexplain command.

For more information, see mqsiexplain command.

For more information, see IBM Support Assistant Data Collector.

For more information, see Selecting a problem collector for IBM Support Assistant Data Collector.

For more information, see Operation modes.

For more information about supported databases, seeIBM Integration Bus system requirements.

For more information, see Database connections.

For more information, see Activity Logs.