API integration

Event driven publish/subscribe

Application data integration

High speed file transfers

They can be included as part of the container image for applications to access storage

They are integrated into the core OpenShift deployment

They are installed and configured in the host machines where the master nodes will run

They are typically shipped as container images and have to be installed by a cluster administrator

Send and share large files and folders stored in on-premises data centers and major clouds

Secure and reliable transfer of sensitive data, such as payment information, between applications

Managed file transfer capabilities using messaging transport to move data

Create distributed event-streaming platform to ingest a large volume of data in real-time

Data migration to, from, and between on-premises data centers and any major cloud

The database used by all Cloud Pak for Integration components is corrupted

OpenShift has lost all worker nodes

The majority of master/control plane hosts are lost

One of the master nodes has gone off line

They can include actions for a callable flow

They use the Connector API to stage API assemblies to an IBM API Connect catalog

They must be packaged in an immutable Docker integration image

They can be exported as a BAR file for deployment in an integration server

Provides ability to visualize issues in near real time so they can be worked on and reduce wait times

Provides a fully managed Apache Kafka service

Delivers cross-component tracing and insights on call paths and latencies

Provides data streaming functions and optimized bandwidth tiers

A Windows .NET compatibility library available in the OpenShift Developer Catalog

A Kubernetes native container runtime implementation that integrates closely with CoreOS

The graphical user interface for Operators to administer applications/workloads running on OpenShift

An optional version of Docker optimized for OpenShift when running on cloud provider platforms