IBM App Connect Enterprise, Version 11.0.0.2 Operating Systems: Windows, Linux


Behavioral changes in Version 11.0

Depending on your current version of IBM® Integration Bus, IBM App Connect Enterprise Version 11.0 might introduce several technical changes in behavior. These changes might affect your post-migration development tasks.

The changes that affect you vary depending on your current version. Review the following changes to see how your post-migration development tasks might be affected:

Platform support

IBM App Connect Enterprise Version 11.0 is currently available on:
  • Windows
  • Linux

For detailed information about the platforms that are supported, visit the IBM App Connect Enterprise Version 11.0 system requirements web page.

The Statement of general direction in the IBM App Connect Enterprise Version 11.0 announcement letter outlines intention regarding support for other platforms.

Policies control and update message flow and message flow node properties

At earlier releases, configurable services allow you to control and update connection properties and other operational properties of message flows and message flow nodes at run time. In IBM App Connect Enterprise Version 11.0, policies perform this administrative role.

You can migrate your existing configurable policies by using the mqsiextractcomponents command. If you are performing parallel migration, you need to create policies to replace your configurable services.

For more information, see Overriding properties at run time with policies.

Nodes that are no longer available

Your message flows from earlier versions will work at IBM App Connect Enterprise Version 11.0. However, a number of message flow nodes are unavailable at Version 11.0; if your earlier message flows include them, consider reworking them.

The following nodes are unavailable in IBM App Connect Enterprise Version 11.0:
  • DataDelete node
  • DataInsert node
  • DataUpdate node
  • Extract node
  • Mapping node from WebSphere® Message Broker Version 7.0 and earlier versions
  • MQOptimizedFlow node
  • Real-timeOptimizedFlow node
  • Warehouse node
If you try to use a message flow that contains any of these nodes, the message flow does not start and message BIP2355 is written to the syslog. The message mapping (.msgmap) on these Version 7.0 nodes can be viewed but they cannot be deployed to the runtime in IBM App Connect Enterprise Version 11.0.

For details of other nodes that are unavailable in IBM App Connect Enterprise Version 11.0, see Built-in nodes.

High availability (HA) support

Multi-instance integration nodes and the HTTP proxy servlet are not currently supported. You can, however, use an external HA manager or a Windows Cluster.

For more information, see Using an integration node with an existing high availability manager and Using an integration node with an existing Windows Cluster (Windows Server).

IBM App Connect Enterprise Version 11.0 REST administration API (REST API) Version 2 is available to issue administration commands

IBM App Connect Enterprise Version 11.0 does not include the IBM Integration API. Instead, you can use the REST API (Version 2) that is provided in IBM App Connect Enterprise Version 11.0 to issue administration commands.

For more information, see Managing resources by using the administration REST API.

Web user interface extended to support administration tasks

IBM App Connect Enterprise Version 11.0 does not include IBM Integration Explorer. Instead, the web user interface is extended to support integration node administration tasks such as creating and managing integration servers, and deploying and managing resources.

For more information, see IBM App Connect Enterprise web user interface.

Additional options for administration security

In IBM App Connect Enterprise Version 11.0, you have two options for configuring administration security. As in previous versions, you can configure queue-based permissions by using WebSphere MQ queues on the queue manager that is specified on the integration node, or you can configure file-based permissions on your integration node, which you set by using the mqsichangefileauth command.

If you have configured administration security and then you perform parallel migration to integration nodes that are not configured with queue managers, you must reconfigure your administration security to use file-based permissions. Any security permissions that are set before migration are not retained after migration.

For more information, see Authorizing users for administration.

Administration scripts might need to be updated

A number of commands are not available at this release. In addition, some parameters for administration commands that connect to integration nodes and integration servers have changed; see the command reference topics for more information: Commands. The MQBrokerConnectionParameters IBM Integration API class has also been deprecated; see the Javadoc for the IBM Integration API.

IBM App Connect Enterprise Toolkit help topics might include details of function that is not available to you

By default, the IBM App Connect Enterprise Toolkit is now configured to use online product documentation to provide context-sensitive help from the latest information that is available. In previous versions, the IBM App Connect Enterprise Toolkit contained local help documentation, which was not automatically updated when new information became available. There is no difference in the way that help is displayed in the IBM App Connect Enterprise Toolkit. However, the content of the IBM App Connect Enterprise section of the online product documentation is updated when fix packs are made available. If you have not deployed the latest fix pack, the help information might include details of function that is not available to you.

If you do not want to access the online product documentation, you can download and install a local source of product documentation. For information about local documentation options, see Adding documentation to the IBM App Connect Enterprise Toolkit.

Message maps: change in behavior

In IBM App Connect Enterprise Version 11.0, the behavior of the Assign transform in the Graphical Data Mapping editor has been corrected when you assign an empty string to an element.
  • In previous versions, when you perform an Assign transform on a target element that is defined as xsd:string, the Graphical Data Mapping editor sets the internal NULL value in the message tree for that element.
  • In IBM App Connect Enterprise Version 11.0, when you perform an Assign transform on a target element that is defined as xsd:string, the Graphical Data Mapping editor sets the element value to the empty string '' value.
For message formats such as XML, this change in behavior has no impact on the message flow. However, if your message flow has logic that tests that the value of an element is the internal NULL value, you must modify the test to look for the empty string value, or modify the map to use the new iib:nullvalue() function. To call the new function, you use a Custom XPath transform.

Message maps are validated at deployment time

In IBM App Connect Enterprise Version 11.0, message maps are prepared for execution on deployment instead of when the first message flows through the Mapping node. For more information, see Deploying message maps.


bh19400_.htm | Last updated 2018-11-02 14:46:24