Discoverability and ease of installation of Apache Camel tooling based on the Language Server Protocol has been improved. Manual download and installation of binaries is no longer necessary! For the Eclipse desktop IDE and the VS Code environment you can now find and install the Camel tooling directly from the marketplaces for each development environment.
Camel Language Server is now also available in Red Hat OpenShift.io!
In this article, I will show you how you can install Camel tooling via the marketplaces for Eclipse and VS Code. I will also show how to enable Camel tooling in your OpenShift.io workspace.
Continue reading “Apache Camel URI completion: easy installation for Eclipse, VS Code, and OpenShift.io”
We are excited to announce a Developer Preview of Red Hat AMQ Streams, a new addition to Red Hat AMQ, focused on running Apache Kafka on OpenShift.
Apache Kafka is a leading real-time, distributed messaging platform for building data pipelines and streaming applications.
Using Kafka, applications can:
- Publish and subscribe to streams of records.
- Store streams of records.
- Process records as they occur.
Continue reading “Announcing AMQ Streams: Apache Kafka on OpenShift”
Red Hat JBoss AMQ 7 provides fast, lightweight, and secure messaging for internet-scale applications. In addition, AMQ 7 components use industry-standard message protocols and support a wide range of programming languages and operating environments.
Therefore, AMQ 7 gives you the strong foundation you need to build modern distributed applications. Especially relevant is that multiple instances of AMQ 7 brokers can be grouped together to share message processing load.
Each broker manages its own messages and connections and is connected to other brokers with “cluster bridges” that are used to send topology information, such as queues and consumers, as well as load balancing messages.
AMQ 7 supports two different strategies for backing up a server: shared store and replication.
Continue reading “Automating AMQ 7 High Availability Deployment”
The community editions of JBoss Tools 4.5.3 and JBoss Developer Studio 11.3 for Eclipse Oxygen.3a are here waiting for you. Check it out!
JBoss Developer Studio comes with everything pre-bundled in its installer. Simply download it from our JBoss Products page and run it like this:
java -jar jboss-devstudio-<installername>.jar
JBoss Tools or Bring-Your-Own-Eclipse (BYOE) JBoss Developer Studio require a bit more:
This release requires at least Eclipse 4.7 (Oxygen) but we recommend using the latest Eclipse 4.7.3a Oxygen JEE Bundle since then you get most of the dependencies preinstalled.
Once you have installed Eclipse, you can either find us on the Eclipse Marketplace under “JBoss Tools” or “Red Hat JBoss Developer Studio”.
For JBoss Tools, you can also use our update site directly.
What is new?
Continue reading “Announcing Developer Studio 11.3.0.GA, JBoss Tools 4.5.3 for Eclipse Oxygen.3a”
Hopefully by now, you know how to write your first Rest DSL Camel Route using Spring Boot. If not, check this post first. Now that you have your route written, it’s time to write a unit test for it. Many people find Apache Camel unit testing a big struggle to figure out. Luckily, when using Spring Boot with the Apache Camel Rest DSL testing, a Rest Route isn’t too difficult.
Continue reading “Unit Testing for Camel Rest DSL and Spring Boot”
In this article, we will discuss using the Apache Camel ZooKeeper component, and demonstrate how easily we can set up a fail-over scenario for Apache Camel Routes. While working in a clustered environment, situations arise where a user wants to have a backup or slave route which will become active only when the master (or the currently active) route stops working. There are different ways to achieve this: one can use Quartz to configure a master-slave setup; JGroups can also be used. In a Fabric8 environment, there is a master component which can easily be set up as a failover scenario.
Continue reading “Setting Up a Failover Scenario Using Apache Camel ZooKeeper”
Rest services are becoming more and more popular for communication between systems. Now that Red Hat supports the use of Red Hat JBoss Fuse with Apache Camel Spring Boot, learn how you can get started with the Rest DSL and Spring Boot. These directions will use the camel-servlet component, although various components can be used.
Continue reading “Writing Your First Camel Spring Boot Project With the Rest DSL”
The all new and shiny Red Hat Decision Manager 7 has been recently released. Decision Manager 7 is the successor to Red Hat JBoss BRMS, our business rules and decision management platform. In this post we will have a look at the primary new features and provide instructions on how to get started with the new platform, either on your local machine or in an OpenShift Container Platform.
Red Hat Decision Manager 7 focuses on four main themes: Fit & Finish, Cloud-Native, Decision Model and Notation (DMN), and Business Optimizer.
Continue reading “Getting Started with Red Hat Decision Manager 7”
Red Hat JBoss® BPM Suite and Red Hat Decision Manager (formerly Red Hat JBoss BRMS) both use an artifact packaging known as a “KJAR”, or knowledge artifact, since version 6. What is this file type? What separates it from a standard JAR file?
The basic summary
In very few words, a KJAR is a standard JAR file that has some extra files included. A KJAR keeps the same
.jar extension as a JAR file, because its basic file structure is identical to that of a JAR.
Continue reading “What is a KJAR?”