New function added in Version 9.0 fix packs

Message flows

How the FileOutput node deals with failures

You can define the action that the node takes with the output file if the final processing of a file fails. This section describes the outcome for each action taken by the node on final file processing failure given the write mode and the type of transfer:How the broker processes files.

Logging

Performance logging of the broker-wide HTTP listener

Parameters are added to the mqsichangeproperties command to enable performance logging of the broker-wide HTTP listener.

For more information, see Broker-wide HTTP listener parameters.

Platforms and environments

ReSequence failure mode

Resequence message processing now contains a retry mechanism to control how to handle downstream failures. For more information, see Resequence node.

Increased support for JDBC drivers

Any JDBC provider is supported, therefore if a JDBC provider is not listed in the supported database table, IBM Integration Bus provides limited support. This support has the following restrictions: The driver must be a JDBC Type 4 (Pure Java™) driver. Global transaction coordination (XA) is not supported. Discoverability in the Graphical Data Mapper is not supported, and the automatic determination of field types in Graphical Data Maps is supported only if the driver correctly and fully implements java.sql.PreparedStatement.getParameterMetaData(). For more information about the field types, see Data type considerations for mapping database content.

For more information about supported JDBC drivers, see Supported databases or the IBM Integration Bus system requirements: http://www.ibm.com/software/integration/wbimessagebroker/requirements/.

JDBCProviders configurable service

A unique security key securityIdentity performs a second broker registry lookup to find an entry under the broker DSN entries, which store the encrypted password for the user identity for connection logon authentication on their associated host system; for example, jdbc::mysecurityIdentity. For more information on securityIdentity and alternative authentication methods, see JDBCProviders configurable service.

Simplicity and productivity

mqsireportdbparms command

You can return a list of parameters that are set on a broker. In addition, you can use the mqsireportdbparms to check if security credentials are set, or identify if you are using the correct password for a broker.

For more information about using the mqsireportdbparms command, see mqsireportdbparms command.

Message flows

Read remote files over FTP and SFTP using the FileRead node

When a FileReadnode has the Remote Transfer option selected, and a local file is not available, one is transferred from a remote server. If the Delete remote file after successful transfer property is selected, then after successfully transferring a file it is deleted from the remote server, otherwise it is left in place.

For more information about using the reading remote files with the FileReadnode, see FileRead node and Using local environment variables with file nodes.

Override the Reply properties on the SCARequestnode

When an SCARequest nodeis used with a WebSphere MQ, it is possible to override the Request Queue Manager and Request Queue using the LocalEnvironment.

For more information about overriding the Reply properties, see SCARequest node.

Java Isolation at the Application level

Previous versions of IBM Integration Bus do not support Java isolation in applications. Now, a Java class loader is built for each application, and it contains only the Java that is deployed in that application and any included libraries.

For more information about Java isolation, see JavaCompute node.

Graphical mapping

Creating a message map programmatically

You can use the Graphical Data Map Specification Language to create a message map programmatically.

You can create a map programmatically when you have meta-data that defines the transformation logic that needs to be applied to an input message to produce the output.

For example, you can write a JAXB based program that builds the map using JAXB classes generated from the provided MSL schema. The program reads XML data that defines the input elements to be mapped and the output elements.

For more information, see Creating a message map programmatically.

Universal connectivity for SOA

Security Identity Propagation for the Siebel Request Node

The previously available Security Identity Propagation support for SAPRequest nodes has been extended for use with the SiebelRequest node. This new behavior means that you can use a Security Profile to extract security tokens at runtime and then propagate the identity to Siebel. This allows you set the credentials dynamically, and therefore you do not have to use the same Identity for every request made.

For more information about this new support, see Propagating security credentials to Siebel and SAP requests

Platforms and environments

Additional features that detail improved control over message processing, updated ODBC database driver support, and support for Standard Edition on z/OS®.

Updated DataDirect drivers

The DataDirect ODBC drivers were updated from V7.0 to V7.1. The newer Oracle driver provides support for Oracle Advanced Security features. In addition, the DataDirect SQL Server (Native) Wire Protocol driver is now included as well as to the DataDirect SQL Server Legacy Wire Protocol driver.

For more information, see Connecting to a database from Linux and UNIX systems by using the IBM Integration ODBC Database Extender

Troubleshooting and support

New service trace option and examples

In addition to the safe and fast modes available for user trace, there is a third mode temp that is available with integration server service trace only. This mode is the same as safe mode, but trace is automatically switched off when the component restarts. You can also specify up to 10 BIP numbers to stop the trace automatically.

For examples and more information about this mqsichangetrace option, see mqsichangetrace command - Windows, Linux, and UNIX systems

Simplicity and productivity

Nodes added to Scale and Express Edition

The following nodes are now available in Scale and Express Edition:

• AggregateControl node
• AggregateReply
• AggregateRequest
• DatabaseRoute node
• DatabaseRetrieve node

To see the full list of available nodes for each operation mode, see IBM Integration features.

Message flows

Configuring the XPath cache

An integration server keeps a cache of compiled XPath expressions to help reduce the processor usage of parsing and re-creating XPath expressions that are used repeatedly during message flow execution. This cache is shared by all message flows within an integration server. However, this default size might become a performance bottleneck for customers who use many XPath expressions with a single flow invocation completely invalidating the cache. Altering the size of the XPath cache might improve message flow performance. For examples and information about altering the default cache size, see Configuring the XPath cache.

Graphical Data Mapping

Access to broker properties directly from a message map

You can access broker properties from a Mapping node directly. You can use any of the following functions:

• mb:getBrokerName()
• mb:getQueueManagerName()
• mb:getNodeName()
• mb:getMessageFlowName()
• mb:getApplicationName()
• mb:getLibraryName()

For more information, see Accessing broker properties from a Mapping node.

Enhancements handling nulls in graphical data transformations

Additional support for handling nulls in graphical data transformations. For example, when you use a Move transform to copy a non-XML input element to an XML output element that is defined as nillable in the schema, the output XML element also has the xsi:nil attribute set.

For more information, see Handling nulls in message maps.

Universal and independent

Integration service JavaScript client API

An integration service developer can generate a JavaScript client API from an existing integration service. The JavaScript client API provides operation functions that a JavaScript developer can call from a program that is running in a JavaScript environment. For more information about the integration service JavaScript client API, see Integration service JavaScript client API.

Integrated security enhancements for HTTP and SOAP nodes

You can now configure the HTTP and SOAP nodes to use the transport-level security protocols NT Lan Manager (NTLM), Kerberos, and Simple and Protected Negotiation (SPNEGO). These protocols are collectively known as Integrated Windows Authentication (IWA).

For more information about IWA, see Integrated Windows Authentication.

Dynamic operation management

Resource statistics messages in JSON format

Resource statistics show the performance and operating details of resources that are used by your integration servers. You can now generate resource statistics messages in JSON format, in addition to the existing XML format. For more information, see Resource statistics.

High performance and scalability

Setting up the JNDI interface for the proxy servlet

The proxy servlet initialization parameters must be configured for the broker environment that the proxy servlet is connecting to each time the proxy servlet is deployed to the servlet container. It is now possible to configure the web.xml parameters only once through the JNDI in WebSphere Application Server, regardless of how many future deployments there might be of the proxy servlet. Because the JNDI configuration parameters take precedence over the initialization parameters in the web.xml file, using this method means that you need to set up at the application server side only once for any future deployments of the proxy servlet.

These setup tasks must all be completed in the WebSphere Application Server administrative console. For a full list of the steps, see Setting up the JNDI interface for the proxy servlet.

Platforms and environments

Additional features that detail improved control over message processing, updated ODBC database driver support, and support for Standard Edition on z/OS.

Scale mode is supported for z/OS systems

In scale mode, the broker operates with a limited set of nodes for use with unlimited integration servers. Message flows are unlimited.

For more information about scale mode, see Operation modes. For information about the licences for different versions of IBM Integration Bus, see License requirements.

SQL Server ODBC database drivers for Solaris on x86-64 systems

Microsoft SQL Server is now supported for Solaris on x86-64 systems.

For instructions on remote access to an SQL Server, see Connecting to a database from Linux and UNIX systems by using the IBM Integration ODBC Database Extender, and for sample ODBC configuration files for Solaris on x86-64, see Sample IBM Integration Bus ODBC configuration files.

Graphical Data Mapping

Using function levels with graphical data maps

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, see Using function levels with graphical data maps.

Accessing user-defined properties directly from a message map

You can access properties that you have associated with a message flow from a message map.

For more information, see Accessing user-defined properties from a Mapping node.

Universal connectivity for SOA

Generate business objects according to SAP naming conventions

You can generate business object names to match the SAP XI standard by selecting Generate business objects according to SAP naming conventions. For more information, see SAP connection properties for the Adapter Connection wizard.

Microsoft SQL Server support for recording and replaying data

You can configure a Microsoft SQL Server database to be used as a data store for recording and replaying data. When the database has been configured, you can select a data capture store that is configured to use an SQL Server database and view the recorded data.

For more information about configuring an SQL Server database, see Creating and configuring a Microsoft SQL Server database for recording data.