IBM App Connect Enterprise

IBM ACE provides capabilities to build integration flows needed to support diverse integration requirements through a set of connectors to a range of data sources, including packaged applications, files, mobile devices, messaging systems, and databases.

IBM ACE avoids the point-to-point strain on development resources by connecting any application or service over multiple protocols, including SOAP, HTTP and JMS.

Modern secure authentication mechanisms, including the ability to perform actions on behalf of masquerading or delegate users, through MQ, HTTP and SOAP nodes are supported such as LDAP, X-AUTH, O-AUTH, and two-way SSL.

A major focus of IBM ACE in its recent releases has been the capability of the product's runtime to be fully hosted in a cloud.

IBM ACE embeds a Common Language Runtime to invoke any .NET logic as part of an integration.

IBM Integration Bus includes a comprehensive set of patterns and samples that demonstrate bi-directional connectivity with both Microsoft Dynamics CRM and MSMQ.

This promotes the ability of end users to focus on developing integration flows rather than installing, configuring, and managing the IBM ACE software.

In this version the development environment was redesigned using Eclipse and support for Web services was integrated into the product.

IBM App Connect Enterprise V12 also featured the use of 'Discovery Connectors', enabling integration developers to discover objects in systems such as Saas and Cloud, as well as discoverable on-premise applications.

IBM App Connect Enterprise consists of the following components: A SOA developer or integration developer defines message flows in the IBM ACE Toolkit by including several message flow nodes, each of which represents a set of actions that define a processing step.

A comprehensive range of operations can be performed on data, including routing, filtering, enrichment, multicast for publish-subscribe, sequencing, and aggregation.

These flexible integration capabilities are able to support the customer's choice of solution architecture, including service-oriented, event-oriented, data-driven, and file-based (batch or real-time).

IBM App Connect includes a set of performance monitoring tools that visually portray current server throughput rates, showing various metrics such as elapsed and CPU time in ways that immediately draw attention to performance bottlenecks and spikes in demand.

You can drill down into granular details, such as rates for individual connectors, and the tools enable you to correlate performance information with configuration changes so that you can quickly determine the performance impact of specific configuration changes, resource metrics can also be emitted to show what resources are being used by an integration service.

IBM App Connect supports policy-driven traffic shaping that enables greater visibility for system administrators and operational control over workload.

Traffic shaping enables system administrators to meet the demands when the quantity of new endpoints (such as mobile and cloud applications) exponentially increases by adjusting available system resources to meet that new demand, delay or redirect the traffic to cope with load spikes.

A key feature of IBM App Connect is the ability to abstract the business logic away from transport or protocol specifics.

The IBM ACE Toolkit enables developers to graphically design mediations, known as message flows, and related artifacts.

Once developed, these resources can be packaged into a broker archive (BAR) file and deployed to an integration node runtime environment or a container.

lex-event-processing capabilities that enable analysis of events to perform validation, enrichment, transformation and intelligent routing of messages based on a set of business rules.

How an ESB or Micro-services integration service simplifies adding new applications to the enterprise.