JBoss Fuse

Summit Live Blog: Middleware security: Authentication, authorization, and auditing services

As you would expect, security is a key focus for Red Hat.  Secure by default is more than a goal, it is a guiding principle across all product lines.  Middleware is no exception and there are some amazing things going on in this space. Divya Mehra and Vikas Kumar of Red Hat walked us through some of the recent innovations, including the recently released Red Hat SSO, product built upon KeyCloak. Derek Walker of SWIFT also spoke about how the leading financial system message broker relies upon JBoss Fuse for secure messaging.

Security is one of the most important topics in computing today, it can be separated into three key pillars and further mapped into middleware features:

  • Confidentiality
    • Authentication
    • Authorization
  • Integrity
    • Audit logging
    • non-repudiation
  • Availability
    • Clustering
    • Guaranteed Delivery

In short, Red Hat JBoss Middleware is secure and open source throughout the entire product line, giving customers increased assurances, such as:

  • Known, fully open source components
    • built securely from source
  • Proactive security notifications and fixes
  • Standards-based
    • OpenJDK
    • SAML 2.0, Kerberos, OpenID Connect
    • TLS, WS-security

Red Hat SSO is the newest member of this product line, providing a brand new server for complete identity management federation:

  • SAML 2.0
  • OpenID Connect
  • OAuth 2.0

It also comes with client adapters, allowing customers to easily integrate their applications with Red Hat SSO or other standard-compliant identity provider.

Red Hat SSO server is a complete, stand-alone product and is Red Hat’s solution for web-based federation.  It can interface with Red Hat Identity Management (IdM) for integration with internal corporate identity management.  It can also work with Active Directory and plain LDAP.  There is native OpenStack and OpenShift integration with Red Hat SSO coming down the line as well.

Continue reading “Summit Live Blog: Middleware security: Authentication, authorization, and auditing services”

Share

DevNation Live Blog: Open source IoT gateway: A tale of Eclipse Kura, Apache Camel, and RHIoT

At DevNation, Red Hat developer Henryk Konsek, gave a talk on an open source gateway for Internet of Things (IoT), using Apache Camel, Eclipse Kura, Much of the focus of the talk was on the scalability needed when IoT is really embraced by organizations. The key take away from the talk is that IoT in reality is all about messaging. Successful implementations will rely on the things we’ve already learned from Enterprise Integration Patterns (EIP).

Continue reading DevNation Live Blog: Open source IoT gateway: A tale of Eclipse Kura, Apache Camel, and RHIoT

Share

Create Resilient Camel applications with Hystrix

Apache Camel is a mature integration library (over 9 years old now) that implements all the patterns from Enterprise Integration Patterns book, but Camel is not only an EIP implementation library, it is a modern framework that constantly evolves, adds new patterns and adapts to the changes in the industry.

Apart from tens of connectors added in each release, Camel goes hand-in-hand with the new features provided by the new versions of Java language itself and other Java frameworks. With time some architectural styles such as SOA and ESB lose attraction and new architectural styles such as REST, Microservices get popular.

To enable developers do integrations using these new trends, Camel responds by adding new DSLs such the REST DSL and new patterns such as the Circuit Breaker, and components such as Spring Boot, and that’s not all and we are nowhere near done. With technologies such as linux containers and Kubernetes, the IT industry is moving forward even faster now, and Camel is evolving in order to ease the developers as it always has been.

Continue reading “Create Resilient Camel applications with Hystrix”

Share

JBoss Fuse Tooling – Camel File Validation – Existing, Improved and New

Red Hat JBoss Fuse is an open source, lightweight and modular integration platform that allows you to connect services and systems across your entire application portfolio. And if you’re familiar with Fuse, you’re probably familiar with the Fuse Tooling that comes with Red Hat JBoss Developer Studio.

As I mentioned in this earlier post, the 8.0.0.Beta2 version of JBoss Fuse Tooling is available. In this article I will cover another new and updated feature: validations. I will explain what was already available and what’s new which improves productivity.

Continue reading “JBoss Fuse Tooling – Camel File Validation – Existing, Improved and New”

Share

JBoss Fuse Tooling – Support of Global configurations

Red Hat JBoss Fuse is an open source, lightweight and modular integration platform that allows you to connect services and systems across your entire application portfolio. And if you’re familiar with Fuse, you’re probably familiar with the Fuse Tooling that comes with Red Hat JBoss Developer Studio.

As I mentioned in an earlier post, the 8.0.0.Beta2 version of JBoss Fuse Tooling is now available. Apart from the diagram tooling rework, there is yet another new, awaited feature. You can find it in the new “Configurations” editor — designed to manipulate global configurations, i.e. elements defined at the Camel context scope.

Continue reading “JBoss Fuse Tooling – Support of Global configurations”

Share

JBoss Fuse Tooling – Diagram reworked: New shiny colors! (and more)

If you are a developer working on integration projects with JBoss Fuse, you’ll be happy to hear that the Fuse tooling has recently been reworked to provide a brighter look and feel, a more sensible, approachable automatic layout.

The work is still in progress, but already available in beta. It can be installed into the new JBoss Developer Studio version 9.1.0.GA.

To check out the latest features, please install the latest JBoss Developer Studio (available here). Then follow the steps below (see screenshot for reference) to add JBoss Fuse Tooling 8.0 Beta 2.

Continue reading “JBoss Fuse Tooling – Diagram reworked: New shiny colors! (and more)”

Share

Persistent Custom MDC Logging in Apache Camel

Logging is an ubiquitous need in any production quality application, and one common scenario is to log the active (logged in) username, or to log the user and order IDs for customer order event details. This is typically done to create an audit trail so that issues can be more easily traced should something go wrong, but there are any number of reasons why you might decide to create a custom log.

Mapped Diagnostic Contexts (MDCs) in Apache Camel are great for creating custom logging statements, and will easily meet our needs for these use cases.  MDC is offered by both slf4j and log4j, and is also supported by JBoss Logging. (Apache Camel is a part of the Red Hat JBoss Fuse integration platform.)

In addition, you can use something like GELF to automatically index any MDC, thus allowing them to be easily searched using ElasticSearch (logging configuration is not required for this feature), so there are a few reasons why this might be an appealing solution.

This article will demonstrate how to set up MDC to perform custom logging.

Continue reading “Persistent Custom MDC Logging in Apache Camel”

Share

API Management with JBoss Fuse on Openshift and 3scale on Amazon Web Services – Part 1

Introduction

A way organizations deal with the progression towards a more connected and API driven world, is by implementing a lightweight SOA/REST API architecture for application services to simplify the delivery of modern apps and services.

In the following blog series, we’re going to show how solutions based on 3scale and Red Hat JBoss Fuse enable organizations to create right interfaces to their internal systems thus enabling them to thrive in the networked, integrated economy.

Among the API Management scenarios that can be addresses by 3cale and Red Hat with JBoss Fuse on OpenShift, we have selected to showcase the following:

  1. Scenario 1 — A Fuse on Openshift application containing the API. The API is managed by 3scale with the API gateway hosted on Amazon Web Services (AWS) via the 3scale AMI.
  2. Scenario 2 — A Fuse on Openshift application containing the API. The API is managed by 3scale with the API gateway hosted via APIcast (3scale’s cloud hosted API gateway)
  3. Scenario 3 — A Fuse on Openshift application containing the API. The API is managed by 3scale with the API gateway hosted on Openshift

Continue reading “API Management with JBoss Fuse on Openshift and 3scale on Amazon Web Services – Part 1”

Share

Using JBoss Fuse and 3scale for API Management

Since Red Hat and 3scale announced our partnership a year ago, we’ve seen great interest by companies and developers to use JBoss Middleware with 3scale API management technology (check out the solution brief here: Enabling success in the API economy).

In this webinar recording, we introduced you to how you can manage and control APIs (including a practical demo) using Red Hat® JBoss® Fuse, OpenShift by Red Hat, and 3scale.

Continue reading “Using JBoss Fuse and 3scale for API Management”

Share