Integration

Using the Yeoman Camel-Project generator to jump start a project

Using the Yeoman Camel-Project generator to jump start a project

The Red Hat Fuse Tooling team recently broadened its focus from a cross-platform, single-IDE (Eclipse) approach to a cross-platform, cross-IDE approach (Eclipse, VS Code, Che), starting several concerted efforts to provide tools that work across platforms and development environments. Supporting VS Code has become a priority that led us to explore using the Yeoman framework for project and file generation to provide developers a way to jump start their Fuse/Camel development efforts.

This article describes the Yeoman framework and the new Yeoman-based Camel-Project generator the Fuse Tooling team created, and it shows how to install and run the generator.

Continue reading “Using the Yeoman Camel-Project generator to jump start a project”

Share
Integration of container platform essentials (Part 5)

Integration of container platform essentials (Part 5)

In Part 4 of this series, we looked into details that determine how your integration becomes the key to transforming your omnichannel customer experience.

It started with laying out the process of how I’ve approached the use case by researching successful customer portfolio solutions as the basis for a generic architectural blueprint. Now it’s time to cover more blueprint details.

This article discusses the core elements in the blueprint (container platform and microservices) that are crucial to the generic architectural overview.

Continue reading “Integration of container platform essentials (Part 5)”

Share
Integration of API management details (Part 4)

Integration of API management details (Part 4)

In Part 3 of this series, we started diving into the details that determine how your integration becomes the key to transforming your customer experience.

It started with laying out the process of how I’ve approached the use case by researching successful customer portfolio solutions as the basis for a generic architectural blueprint. Now it’s time to cover various blueprint details.

This article takes you deeper into specific elements (API management and reverse proxy) of the generic architectural overview.

Continue reading “Integration of API management details (Part 4)”

Share
Modern business logic tooling workshop, lab 1: Installation

Modern business logic tooling workshop, lab 1: Installation

Recently I’ve started updating my free online workshops for business rules and process automation that showcase how to get started using modern business logic tooling. These updates start with moving from Red Hat JBoss BRMS to Red Hat Decision Manager and from Red Hat JBoss BPM Suite to Red Hat Process Automation Manager.

This article highlights the first lab update for Red Hat Decision Manager, where you learn to install Decision Manager on your laptop.

Let’s take a look at the lab, shall we?

Continue reading “Modern business logic tooling workshop, lab 1: Installation”

Share
Integration of external application details (Part 3)

Integration of external application details (Part 3)

In Part 2 of this series, we took a high-level view of the common architectural elements that determine how your integration becomes the key to transforming your customer experience.

I laid out how I’ve approached the use case and how I’ve used successful customer portfolio solutions as the basis for researching a generic architectural blueprint. The only thing left to cover was the order in which you’ll be led through the blueprint details.

This article takes you deeper to cover details pertaining to the specific elements (mobile and web application deployments) of the generic architectural overview.

Continue reading “Integration of external application details (Part 3)”

Share
Demystifying the Red Hat Decision Manager and Process Automation Manager Remote Client

Demystifying the Red Hat Decision Manager and Process Automation Manager Remote Client

KIE-Server is the light-weight, cloud-native, rules and process execution runtime of the Red Hat Decision Manager (RHDM) and Red Hat Process Automation Manager (RHPAM) platforms. Lately, I’ve gotten more and more questions on how to use the KIE-Server Client Java API to interact with the KIE-Server execution runtime of RHDM (formerly called Red Hat JBoss BRMS) and RHPAM (RHPAM). To answers these questions, and to create a future reference, I decided to write a number of code examples, accompanied by this article.

The KIE-Server Client Java API provides an easy way for Java applications to communicate with the KIE-Server execution engine of RHDM and RHPAM. The API abstracts the application from the underlying REST and/or JMS communication protocol and transport, making integrations with the server easier to build, test, and maintain.

Continue reading “Demystifying the Red Hat Decision Manager and Process Automation Manager Remote Client”

Share
How to integrate a remote Red Hat AMQ 7 cluster on Red Hat JBoss EAP 7

How to integrate a remote Red Hat AMQ 7 cluster on Red Hat JBoss EAP 7

It is very common in an integration landscape to have different components connected using a messaging system such as Red Hat AMQ 7 (RHAMQ 7). In this landscape, usually, there are JEE application servers, such as Red Hat JBoss Enterprise Application Platform 7 (JBoss EAP 7), to deploy and run applications connected to the messaging system.

This article describes in detail how to integrate a remote RHAMQ 7 cluster on a JBoss EAP 7 server, and it covers in detail the different configurations and components and some tips to improve your message-driven beans (MDBs) applications.

Continue reading “How to integrate a remote Red Hat AMQ 7 cluster on Red Hat JBoss EAP 7”

Share
Quickly try Red Hat Process Automation Manager in your cloud

Quickly try Red Hat Process Automation Manager in your cloud

It’s been some time since I last talked with you about putting JBoss BPM Suite (now called Red Hat Process Automation Manager) into your cloud, and with the new release, it’s time to talk AppDev in the cloud again.

It’s time to update the story and see how to put Red Hat Process Automation Manager in your cloud so you are set up with a standard configuration to start your first business rules project.

With the easy installation demo project described below, you can leverage process automation tooling through the business central web console running containerized on any Red Hat OpenShift.

Let’s take a closer look at how this works.

Continue reading “Quickly try Red Hat Process Automation Manager in your cloud”

Share
Common architectural elements for modern integration architectures (Part 2)

Common architectural elements for modern integration architectures (Part 2)

In Part 1 of this series, we explored a use case around integration being the key to transforming your customer experience.

I laid out how I’ve approached the use case and how I’ve used successful customer portfolio solutions as the basis for researching a generic architectural blueprint. The only thing left to cover was the order in which you’ll be led through the blueprint details.

This article, which is Part 2 of the series, starts the real journey at the very top, with a generic architecture from which we’ll discuss the common architectural elements one by one.

Continue reading “Common architectural elements for modern integration architectures (Part 2)”

Share
How integration is key to customer experience (Part 1)

How integration is key to customer experience (Part 1)

For the past few months, I’ve been digging into my new role with a group of Portfolio Architects, looking specifically at integration as the key to omnichannel customer experience.

It’s an interesting challenge in that we’ve been given the mission of creating architectural content based on common customer adoption patterns. That’s very different from most of the traditional marketing activities usually associated with generating content for the sole purpose of positioning products for solutions. When you’re basing the content on actual execution in solution delivery, you’re cutting out the chuff. 

What’s that mean?

It means that it’s going to provide you with a way to implement a solution using open source technologies by focusing on the integrations, structures, and interactions that actually have been proven to work.

What’s not included is any vendor promises that you’ll find in normal marketing content: those promises that, when it gets down to implementation crunch time, might not fully deliver.

Enter the term architectural blueprint. 

In this series of articles, let’s look at these blueprints, how they are created, and what value they provide for your solution designs.

Continue reading “How integration is key to customer experience (Part 1)”

Share