Chapter 4. Fuse Standalone

4.1. Supported containers

Fuse standalone 7.2 is supported on the following runtime containers:

  • Spring Boot (standalone)
  • Apache Karaf
  • Red Hat JBoss Enterprise Application Platform (JBoss EAP)

4.2. Technology Preview features

The following features of Fuse standalone are Technology Preview only and are not supported in Fuse 7.2:

Saga EIP
The Saga Enterprise Integration Pattern (EIP) is a technology preview feature and features only the In-Memory Saga service (which is not suitable for a production environments). The LRA Saga service is not supported. For more details, see section Saga EIP of the "Apache Camel Development Guide".

4.3. BOM files for Fuse 7.2

To configure your Maven projects to use the supported Fuse 7.2 artifacts, use the BOM versions documented in this section.

4.3.1. Old-style BOM

To upgrade your Fuse standalone applications to use the 7.2 dependencies, edit the Maven pom.xml and change the versions of the BOMs and Maven plugins listed in the following table:

Table 4.1. Maven BOM and plugin versions for 7.2 using the old-style BOM

Container TypeMaven BOM or Plugin Artifact groupId/artifactIdVersion for Fuse 7.2

Spring Boot

io.fabric8/fabric8-project-bom-camel-spring-boot

3.0.11.fuse-720027-redhat-00001

io.fabric8/fabric8-maven-plugin

3.5.33.fuse-720026-redhat-00001

org.springframework.boot/spring-boot-maven-plugin

1.5.16.RELEASE

Apache Karaf

org.jboss.fuse/jboss-fuse-parent

7.2.0.fuse-720035-redhat-00001

io.fabric8/fabric8-project-bom-fuse-karaf

3.0.11.fuse-720027-redhat-00001

org.apache.karaf.tooling/karaf-maven-plugin

4.2.0.fuse-720061-redhat-00001

JBoss EAP

org.wildfly.camel/wildfly-camel-bom

5.2.0.fuse-720023-redhat-00001

4.3.2. New-style BOM

To upgrade your Fuse standalone applications to use the 7.2 dependencies, edit the Maven pom.xml and change the versions of the BOMs and Maven plugins listed in the following table:

Table 4.2. Maven BOM and plugin versions for 7.2 using the new-style BOM

Container TypeMaven BOM or Plugin Artifact groupId/artifactIdVersion for Fuse 7.2

Spring Boot

org.jboss.redhat-fuse/fuse-springboot-bom

7.2.0.fuse-720020-redhat-00001

org.jboss.redhat-fuse/fabric8-maven-plugin

7.2.0.fuse-720020-redhat-00001

org.jboss.redhat-fuse/spring-boot-maven-plugin

7.2.0.fuse-720020-redhat-00001

Apache Karaf

org.jboss.redhat-fuse/fuse-karaf-bom

7.2.0.fuse-720020-redhat-00001

org.jboss.redhat-fuse/karaf-maven-plugin

7.2.0.fuse-720020-redhat-00001

JBoss EAP

org.jboss.redhat-fuse/fuse-eap-bom

7.2.0.fuse-720020-redhat-00001

For more details about using the new-style BOM, see Migrate Maven Projects in "Migration Guide".

4.4. Important notes

Important notes for the Fuse 7.2 release of the Fuse standalone distribution:

Generating an authentication token for camel-linkedin

LinkedIn has started responding to login forms using a CAPTCHA, which makes it impossible to use the username/password login approach for a standalone headless Fuse process. As an alternative the component was enhanced so that a LinkedIn access token can be generated and configured in an accessToken component property. Also an expiryTime property allows configuring the token expiry time in milliseconds since the Unix Epoch, which defaults to 60 days if not provided. The component tries to login again if the token expires, but the username/password approach is likely to result in a CAPTCHA response and a failed login. Hence the component is unable to automatically refresh tokens on its own.

The token can be generated using a web browser and a utility such as curl and following the OAuth login process for LinkedIn as documented at https://developer.linkedin.com/docs/oauth2. As the document describes, user needs to login using a browser to generate an authorization code, which in turn is used to generate an access token to be configured in the LinkedIn component. The generated token is valid for 60 days, so the process has to be repeated periodically to manually update the token and the Fuse application needs to be restarted with the refreshed token.

camel-kafka component has been updated to use Kafka 2.0.0 client
For better compatibility with AMQ Streams (Red Hat’s distribution of Apache Kafka), the camel-kafka component has been upgraded to use the the Kafka 2.0.0 client library.
Using XA transactions on AMQ connections
When using an XA connection to an AMQ broker, you should set the connection parameter jms.xaAckMode=1 on the broker URL explicitly for the XAConnectionFactory. Spring Boot actuator health checks may not work in this configuration and they should be disabled by setting management.health.jms.enabled=false in the application.properties file.