Webinar: Blueprint for omnichannel integration architecture

Are you interested in the insights to how organizations are implementing the foundational integration building blocks that lead to successful communication with their customers?

This story is about how an omnichannel customer experience makes customer engagement across all channels as efficient as engagement with a single channel. Let’s take a detailed look at an architecture blueprint based on research of actual customer solutions, and gain insight into how your integration architecture can map to support your customers’ omnichannel experiences.

Register for this webinar and you’ll gain insights on how your current architecture can map to support your customers experiences, for a detailed look at an architectural blueprint based on successful customer solutions, and receive instruction on how to discuss an omnichannel architecture in detail.

omnichannel integration architectureHere’s the official abstract, so join us on 12 Dec 2019 for a detailed look at a blueprint for omnichannel integration architecture:

Agile integration is a broadly scoped discussion around how to use all the services and power contained in your organization’s current architecture. While the topic is interesting in its own right, let’s take a deeper look at a specific solution within the integration context: providing an omnichannel customer experience. Omnichannel is the integration and orchestration of channels to make the experience of customer engagement across all channels as efficient as engagement with 1 channel. 

Be sure to register and look forward to seeing you there?

Enhanced containerized integration services on OpenShift: Red Hat Fuse Integration Services

Updated and enhanced integration services are now available on Red Hat OpenShift. A containerized, formatted version of Red Hat Fuse 6.3 is now available for simplified deployments on OpenShift instances.

Technology is shifting so rapidly — from cloud-based architectures, Internet of Things and a variety of devices for interaction, new data streams, and mobile apps, to name a few — that organizations have to be able to create and deploy applications and process data quickly. Traditional, monolithic systems and top-heavy ESB-style integration approaches tend to be too slow and rigid to enable this level rapid innovation.

That is where an agile integration framework like Red Hat Fuse can be a foundational element in your IT and digital strategy. Agile integration has three core capabilities: distributed integration, containers, and an API-based architecture.

  1. Red Hat Fuse uses the lightweight distributed integration patterns of the underlying Apache Camel project.
  2. As part of the JBoss middleware services on OpenShift, Red Hat Fuse is available for rapid deployment within container and cloud environments. Red Hat OpenShift is based on Docker and Kubernetes. Container architectures allow developers to build and integrate traditional and microservices-based applications at scale quickly.
  3. Red Hat Fuse can be used together with Red Hat 3scale API Management Platform as an engine to develop and deploy APIs, both internally to development groups and externally for customer and partner ecosystems.

Integration technologies help organizations build on their existing infrastructures even as they pivot to new cloud-based and service-based architectures.

Features (and Benefits) at a Glance

  • Spring Boot support
  • Custom-developed, containerized applications based on Apache Camel 2.18
  • Integration with Hystrix and Zipkin microservices frameworks
  • An optimized integration environment for microservices applications on Red Hat OpenShift
  • Path to transition off existing Apache Karaf-based applications to cloud architectures
  • Consistent hybrid integration platform across their enterprise

More Information

Healthcare Integration Solutions: Red Hat Fuse vs. JCAPS

As discussed in our previous post, healthcare companies face many integration challenges: complex data standards like HIPAA and HL7,  differences in applications across the healthcare industry, and increasing regulations about meaningful use and value-based care.

These challenges are compounded by legacy technologies. Many healthcare companies’ internal enterprise applications were set up years ago using various data formats that cannot directly interoperate with one another.  One way to solve this problem was to turn to enterprise service buses (ESBs) to transform and normalize data across different applications for cross-company communications, and a popular system was Java Composite Application Platform Suite (JCAPS). JCAPS was an effective way to integrate existing systems using ESBs to standardize data– and critical for healthcare providers, it offered support for HL7 data standards. JCAPS also introduced business services which allowed IT architects to design service-oriented architectures (SOA) to try to make those separate systems more responsive.

However, Oracle is quietly deprecating JCAPS — the end of extended support is next January — and customers are being advised to migrate to a different Oracle suite. With a deadline looming in less than a year, IT leaders in the healthcare industry have to start looking for a new integration solution. Now is the time to start defining the requirements for the next generation of healthcare data interoperability solution.

Continue reading “Healthcare Integration Solutions: Red Hat Fuse vs. JCAPS”

Red Hat announces availability of containerized middleware capabilities on OpenShift

A little more than two years ago, we announced Red Hat’s “xPaaS” initiative to provide Red Hat JBoss Middleware on OpenShift and introduce a new way of building and deploying enterprise applications. Our efforts in executing against that vision and roadmap have entailed a lot of work and have been very exciting.

Continue reading “Red Hat announces availability of containerized middleware capabilities on OpenShift”