The wait is over: JBoss Web Server 5 with Tomcat 9 is here!

We are excited to announce the general availability of Red Hat JBoss Web Server 5.0 for Red Hat Enterprise Linux and the technology preview of transactions processing with Narayana. JWS 5 is available through zip, RPM, Maven repository, and the Red Hat Container Catalog.

Red Hat JBoss Web Server combines market-leading open source technologies with enterprise capabilities to provide a single solution for large-scale websites and lightweight web applications. It combines the world’s most deployed web server (Apache) with the top servlet engine (Tomcat) and excellent support for middleware (ours).

Continue reading “The wait is over: JBoss Web Server 5 with Tomcat 9 is here!”

Process management and business logic for responsive cloud-native applications: Red Hat Process Automation Manager is released

Today, Red Hat announced the latest major release of its business process suite, with a new name and several major changes that pivot the focus of the product itself. Red Hat Process Automation Manager is about more than providing a business process modeler or optimizing resource allocation. This is the first generation (at Red Hat) of a digital automation platform — a hub where business users and technical developers can collaborate to create strategically-relevant, intelligent applications.

Red Hat Process Automation Manager has two core conceptual areas:

  • The first is based on decision management (the “intelligent” part of intelligent or even-driven applications). This includes the decision engine of Red Hat Decision Manager and allows automated, immediate responses to interactions, from event processing to resource optimization.
  • Second, Process Automation Manager provides the means of modeling and applying business logic within an application. In combination with a graphical UI, these creates a platform for business users to be able to design business logic in collaboration with the technical teams.

New feature: Process management + case management

The heart of a BPM platform is the “BP” — business process modeling. The previous BPM Suite supported BPMN, the notation specification for business process models, and DMN, the notation specification for data models. The assumption behind a lot of these specs is that the workflows or processes being modeled are relatively static or sequential. For certain types of business processes, that is an accurate assumption (things like resource optimization or scheduling). However, in many organizations, there are also processes which are not linear or which may follow different steps in a dynamic sequence or may be interrupted or require human intervention at certain points. These are generally defined within a related notation specification, Case Management Model Notation (CMMN).

While there are differences, there is also a lot of conceptual overlap between business processes / BPMN and case management processes / CMMN. Process Automation Manager combines the functionality of both process models and case management models within a single digital automation platform. (This is covered in more detail in the blog post here.)

Supporting both linear process / task models and dynamic or unpredictable case management models within the same platform allows developers to have a simpler development process (and, combined with other features like Process Automation Manager’s new graphical UI, makes collaboration with business users easier).

Process Automation Manager also supports other types of modeling and visualizing data and worflows:

  • Data modeling
  • Decision modeling
  • Custom data dashboards
  • Process simulations

New Feature: An easier way for business users to collaborate (graphical UI)

Previous versions of Red Hat JBoss BPM Suite were designed around business process logic, but were intended to be used by Java developers within the application development process. Beginning with this Process Automation Manager 7.0 release, there is a new Entando UI included with the platform. This provides an easier, graphical interface where business users can just drag and drop elements into their models — using ultimately the same platform that the developers are using to create the application. Business processes, rules, and logic can be written into the application essentially without having to write a single line of code.

This also effectively changes the workflow for creating event- and process-driven application. Previously, developers did all the work within their development environment. Now, business users can work in parallel (using the Process Automation Manager UI) to create artifacts which can be pulled into the developer’s IDE and code. Everything can then be packaged up and deployed in containers or other environments.

New feature: Cloud (and container) native applications

With more distributed, hybrid infrastructures, it is imperative that applications be able to function exactly the same regardless of the underlying platform. And those applications need to be designed, natively, to work in a distributed, dynamic environment so that they can be rapidly deployed, updated, or scaled.

Process Automation Manager can itself run in Red Hat OpenShift containers, in public or private clouds, on-premise, or in all environments — depending on the needs of your development and infrastructure teams. Additionally, the models and applications created using Process Automation Manager as a platform can be deployed into cloud instances, OpenShift containers, or local instances. This allows truly hybrid development, testing, and production environments.

Process Automation Manager components, applications, and models can all be exposed and accessed using REST APIs, allowing integration with other software applications or management tools.

Additional Resources

  • Dive a little deeper into process automation technology with our tech overview.
  • For general information about the Process Automation Manager, check out the datasheet.
  • There are different use cases for process automation and a business decision engine. The FAQ runs through some things to consider.
  • Get started by actually using the Process Automation Manager. Red Hat Developers has a whole “hello world” example, waiting for you.

Announcing: Red Hat Fuse 7 is now available

After several technical previews over the last few months, Red Hat Fuse is officially available. This is a significant release, both for Fuse itself and for integration platforms, because it represents a shift from more traditional, on-premise, centralized integration architecture to distributed, hybrid environment integration architecture.

Integration itself has historically been a bottleneck for infrastructure design and changes. The integration points were largely centralized and controlled by a central team in an attempt to manage dependencies and standardize data management between applications. However, that centralization also made change difficult, and it was governed more by procedure and bureaucracy than business innovation. As with traditional infrastructure architecture more generally, integration has not historically been an agile or adaptive architecture.

Red Hat Fuse (and related community projects) is the beginning of a departure from traditional, rigid integration platforms to more agile, distributed integration design. Fuse introduces three major features in the latest release:

  • Fuse Online, fully hosted Fuse applications and integrations. Fuse Online provides immediate access to the functionality of Fuse, without having to install and configure it on-premise. Developers can begin testing and customizing integrations immediately. Connectors can be uploaded to the online development area to allow even more integrations.
  • Fuse container images for Red Hat OpenShift. Fuse runs natively on OpenShift, allowing local, containerized integration points to be created in development teams and to be designed, tested, and updated within DevOps workflows as part of the overall application development cycle.
  • A drag-and-drop UI for integration pattern design. While integration development is typically done within IT teams, integration design relies on business knowledge. Business managers and analysts need to be able to collaborate effectively with their development teams. The new Fuse Ignite UI (based on the Syndesis.io project) is a lowcode way to develop integration — business users can use design elements to create integration architectures and to work with their development teams, within the same tool set.

These three features allow more agile integration development. Fuse installations can span online, on-premise, or container based environments without reducing functionality. This allows an integration platform that crosses environments, and be as lightweight and decentralized as an individual development team or an enterprise-wide platform. The lowcode UI allows business users to be brought directly into the application development cycle, enabling business logic to be incorporated into the integration application design from the beginning.

Additionally, Fuse 7 contains these new features:

  • Support for Spring Boot deployment for Fuse applications
  • 50 new application connectors (with a total of over 200 included connectors)
  • A new monitoring subsystem
  • Updated component versions, including new versions of Red Hat JBoss Enterprise Application Platform and Apache Camel
  • A new name (Red Hat Fuse, rather than Red Hat JBoss Fuse)

 

Additional Resources

Why are our Application Platform Partners succeeding in Digital Transformation?

Last year we set out to start the Application Platform Partner Initiative with the objective to enable deeper collaboration with partners focused on application platform and emerging technologies. We planned to create a collaborative go-to-market strategy between Red Hat and participating partner organizations focused on optimizing the value chain for application development and integration projects.

The Application Platform Partner Initiative focuses on Application Development-related and other emerging technology offerings, which revenue increased 42% in our last fiscal year up to $624 million. Partners like the APPs are contributing to this growth and we are happy to see the momentum continuing, and their trust on Red Hat as a strategic partner. What started out as a pilot has developed into a fully fledged initiative with 28 partners across North America, who are as committed as we are to the role opens source plays at the core of digital transformation.

As part of the success of this initiative, for the first time this year, we have created the Application Platform Partner Pavilion in Red Hat Summit.  Arctiq, Crossvale, Kovarus, Levvel, Li9, Lighthouse, OSI, Shadow-Soft, VeriStor and Vizuri will join us this year in the pavilion. Don’t miss a chance to get to know the advanced solutions they have created on top of Openshift and Red Hat Middleware products, which they will be showcasing at Red Hat Summit. Check out, for example, Arctiq Value Stream Mapping (VSM), Crossvale CloudBalancer for Red Hat® OpenShift or Vizuri log aggregation solutions.

These partners are delivering a strong investment in enablement, and commitment in their go-to-market alliance with Red Hat, including co-marketing and sales collaboration. As some examples of planned activities, Arctiq is running a Modern Mobile App Development event and Crossvale an OpenShift roadshow).

Levvel has been an active participant in the APP program, doing joint webinars, customer workshops and panel discussions to promote Red Hat emerging technologies. As a result, they have influenced and closed quite a few customers and have a long list of potential opportunities. Don’t forget to attend their coming up event “App Transformation Workshop: Monoliths to Microservices”!

Shadow-Soft has been particularly focused on growing the customer base with our OpenShift and JBoss product family with innovative sales and marketing strategies that are turning into a growing pipeline of opportunities, and running events around digital transformation.

Veristor joined recently the APP program and is growing rapidly their different practices around OpenShift and Red Hat Middleware, like DevOps and Agile Consulting, Services and Software Development practice.

OSI, an international company with a long experience with JBoss, is also growing in the US and have worked on an Agile Integration demo environment focusing on JBoss Fuse Integration platform to support their customer engagements, including integration with cloud and on-premise systems. Try to attend their “Monoliths to Microservices: App Transformation Workshop” right after Summit.

Vizuri has been a Red Hat partner for over 10 years. Having delivered more than 120 JBoss-related engagements, their JBoss experience and expertise helps customers reduce risk and improve time-to-value, while avoiding project delays and unplanned downtime. You can’t miss their take on How To Manage Business Rules In A Microservices Architecture using OpenShift and JBoss BRMS.

Having recently joined the APP program, Astellent has heavily invested in enablement and marketing, while achieving exciting customer success. Read their views on the newly launched Red Hat Decision Manager 7.

Lighthouse has been helping businesses with the right mix of Red Hat’s public, on-premises, and hybrid cloud technologies, customizing them to fit their unique business needs. They have also been active with unique marketing events like the one with the Red Sox coming in May.

As you can see, APP partners are working closely with Red Hat to establish a sales, marketing, and delivery practice around Red Hat technologies, including Red Hat JBoss Middleware, Red Hat OpenShift, and Red Hat Mobile Application Platform.

In the words of John Bleuer, VP, Strategic Partners, North America, “I am thrilled that as year one of the program ends, the sophistication of our partner solutioning and delivery abilities has increased dramatically; many partners are working with us in industry and line of business (including healthcare, payments, and e-commerce); other partners are adding sophistication into the DevOps / automation practices with Openshift, Jenkins, and Ansible, while others are honing their skills delivering app modernization and integration & BPM solutions in a cloud native environment, containerized in OpenShift.  It’s an exciting time at Red Hat”.

The market is looking to digital transformation initiatives to grow and maintain competitive advantage. Challenges range from confined platforms to complex architectures, from rigid processes to lack of agility. Together with our partners, we can play a critical role to help our customers overcome those to become growing, competitive organizations.

We hope to see you at Red Hat Summit checking them out, as well as at the Red Hat Summit Ecosystem Expo!

Red Hat OpenShift Application Runtimes: Delivering new productivity, performance, and stronger standards support with its latest sprint release

Red Hat OpenShift Application Runtimes is a collection of cloud-native application runtimes that are optimized to run on OpenShift, including Eclipse Vert.x, Node.js, Spring Boot, and WildFly Swarm. In addition, OpenShift Application Runtimes includes the Launch Service, which helps developers get up and running quickly in the cloud through a number of ready-to-run examples — or missions — that streamline developer productivity.

New Cache Booster with JBoss Data Grid integration

In our latest continuous delivery release, we have added a new cache mission  that demonstrates how to use a cache to increase the response time of applications.  This mission shows you how to:

  1. Deploy a cache to OpenShift.
  2. Use a cache within an application.

The common use case for this booster is to cache service result sets to decrease latency associated with data access as well as reduce workload on backend service.  Another very common use case is to reduce the data volume of message send across in distributed system.

Continue reading “Red Hat OpenShift Application Runtimes: Delivering new productivity, performance, and stronger standards support with its latest sprint release”

Jakarta EE is officially out

Jakarta EE is officially out! OK, given the amount of publicity and evangelising we and others have done around EE4J and Jakarta EE over the past few months, you would be forgiven for thinking it was already the case, but it wasn’t … until today!

I cannot stress enough how important this is to our industry. The number of Java™ developers globally is estimated at over 14 million. The Java EE market is estimated at a high multi-billion dollar value to the industry. Yes, there are other languages out there and other frameworks but none of them have yet made the impact Java™ and Java EE has over the years. Of course, Java EE was not perfect for a variety of reasons, but if you consider how much of an impact it has had on the industry given known and debated limitations, just imagine how much it can bring in the years ahead if it were improved.

With the release of Jakarta EE, we all have a chance to collaborate and build on the good things it inherits, whilst at the same time working to evolve those pieces which are no longer relevant or perhaps never were quite what was needed. Working within the open processes of the Eclipse Foundation vendors, Java™ communities, individuals etc. are all able to interact as peers with no one vendor holding a higher role than another. We’ve seen this exact same process work extremely well in a relatively short period of time with Eclipse MicroProfile and I believe Jakarta EE can do at least as well.

When talking about Java EE and now Jakarta EE some often focus only on the technologies. Fortunately, those of us who have been in the open source world long enough appreciate that the community is just as important. With Jakarta EE, all of us involved in working towards the release hope that we can use it as a catalyst to bring together often disparate Java™ communities under a single banner. Too often, Java EE has been a divisive topic for some vendors and some communities, resulting in fractures and often working on the same problems but pulling in different directions. If Jakarta EE does only one thing, and that is bringing everyone together to collaborate, then I would still deem it a success!

I’ll finish by discussing why Red Hat® has been helping to lead this effort along with others. I can summarise this pretty easily: enterprise Java™ remains critical to our customers and communities, and we believe that despite the increase of other languages and frameworks, it should remain so for many years to come. Red Hat, and JBoss® before it, has contributed to J2EE™, Java EE, and Eclipse MicroProfile for years, and we believe that sharing our experiences and working on open source implementations is important for the industry as a whole, no matter what language you may be using. We believe it’s important to leverage Jakarta EE in the cloud and to a wider range of communities than in the past. We’re here to stay and will continue to help lead!

Onward!

To learn more, join these upcoming live sessions:

Learning Process Driven Application Development with JBoss BPM

Are you interested in an introduction to the concepts of process management (BPM)?

Do you want to learn how your business can leverage process driven application delivery?

Are you looking for an easy to understand guide to mastering Red Hat JBoss BPM Suite tooling?

Do you want a step-by-step introduction to setting up JBoss BPM Suite, then coverage of practical and important topics like data modeling, designing business rules and processes,  detailed real world examples, and tips for testing?

For the last few years I’ve been working on putting years of working with JBoss BPM Suite, community projects Drools and jBPM together in one easy to understand book.

In 2017, Red Hat put the first chapter online for free and literally thousands downloaded it starting their journey on the road to delivering process driven application with JBoss BPM Suite. Many of you have reached out over the years to ask about the completion of this book and where you can get it.

The good news isthat the book is available and Red Hat’s providing ebook downloads for free!

Let’s look at how this works, shall we?

Continue reading “Learning Process Driven Application Development with JBoss BPM”

Announcing Red Hat Fuse 7.0 Technical Preview 3

On November 2, 2017, we announced the technical preview of a new low-code integration platform called Red Hat Fuse Online. This technical preview provided a first chance for users to experience the new platform and provide feedback.

Building on the feedback we’ve received with the  Red Hat Fuse Online technical preview, we are happy to announce the Red Hat Fuse 7.0 technical preview 3 (TP3).

Continue reading “Announcing Red Hat Fuse 7.0 Technical Preview 3”

Announcing: Red Hat Decision Manager 7.0 Is Now Available

Red Hat has announced the release of Red Hat Decision Manager 7. Decision Manager is the evolution of Red Hat JBoss BRMS and provides a platform to develop rules-based applications and services.

As applications and services become more central to business strategies, business users will become increasingly involved in the development process. Software that aids in creating applications without directly writing code is known as low-code development. Decision Manager provides tools, including an updated UI and enhanced wizards, that help business users participate more actively in application development.

Major Use Cases

Decision service as a microservice

Decision Manager has a more modular architecture, such as a decision service, an execution server, and a management interface. Each component can be containerized and deployed as an image on Red Hat OpenShift Container Platform. Developers can create discrete services for specific needs and deploy those “micro-rules” in a microservices architecture. This approach is covered more in another blog post.

Continue reading “Announcing: Red Hat Decision Manager 7.0 Is Now Available”

New Documentation with JBoss EAP 7.1: Performance Tuning Guide

Red Hat JBoss Enterprise Application Platform 7 (JBoss EAP) is optimized for performance out-of-the-box. However, a frequent request that we receive from customers is for advice on how to further monitor and tune their JBoss EAP environment for even better performance.

To meet this customer demand, the JBoss EAP Customer Content Services team has produced a new Performance Tuning Guide that is now available with JBoss EAP 7.1.

We have worked with multiple teams inside Red Hat to produce this guide, including software, performance, and quality engineering, as well as Red Hat consultants, solution architects, and support engineers.

The new guide covers high-level JBoss EAP performance advice, including:

  • Monitoring JBoss EAP performance
  • Diagnosing performance issues
  • Tuning JBoss EAP subsystems and components, including:
    • JVM tuning
    • EJB subsystem
    • Datasources and resource adapters
    • Messaging subsystem
    • Undertow subsystem
    • IO subsystem
    • JGroups subsystem
    • Transactions subsystem

We’d love to know what you think of this new guide! The best way to send us your feedback on documentation is to create a new discussion on the Red Hat Customer Portal.