What's New
The What's New topic lists new and revised features of TIBCO BusinessEvents® version 5.5 compared to the previous version with reference to documentation.
Kubernetes Support
TIBCO BusinessEvents and rule management server (RMS) applications can now be deployed on an Amazon Web Services (AWS) based Kubernetes cluster.
For more information about running TIBCO BusinessEvents and RMS applications in Kubernetes, see Running TIBCO BusinessEvents® on AWS Based Kubernetes Cluster and Running RMS Applications in Kubernetes.
TIBCO ActiveSpaces 3.x Catalog Functions
New catalog functions are available for interaction with an external TIBCO ActiveSpaces 3.x cluster.
For more information about TIBCO BusinessEvents and TIBCO ActiveSpaces 3.x integration, see TIBCO BusinessEvents and TIBCO ActiveSpaces 3.x Integration.
TIBCO BusinessEvents® WebStudio New User Interface
For information about WebStudio new UI, see WebStudio New User Interface.
FTL Channel
TIBCO BusinessEvents now provides a new channel to communicate with TIBCO FTL. TIBCO BusinessEvents can now send and receive events using TIBCO FTL as transport. You can also use catalog functions in TIBCO BusinessEvents to communicate with TIBCO FTL. The FTL channel also supports secure communication using SSL.
For more information about FTL channel, see FTL Channel.
Kafka Channel
- You can now configure SASL and SSL based secured communication with Kafka. For details about security protocols, see Configuration for Kafka Channel .
- You can now use Include Event Type field to specify when to suppress the original behavior of including ns and nm fields during serialization and deserialization.
- The existing serializer KafkaStringPayloadSerializer is now replaced with KafkaXmlSerializer to also include event properties for serialization and deserialization. A Kafka JSON message serializer KafkaJsonSerializer is added. For details about Kafka channel serializers, see Kafka Channel.
Rule Management Server (RMS)
- You can now hot deploy artifacts for in-memory projects. Added a new property <project name>.<environment name>.ws.jmx.inMemory to specify if the project is a in-memory project. For more information about the property <project name>.<environment name>.ws.jmx.inMemory, see Hot Deployment Property Group
- TIBCO BusinessEvents now ships a reference implementation code and API for custom source control repository. For details about integrating your repository with RMS, see Integrating Custom Repository with RMS.
Maven Integration
Additional Maven phases for hot deployment and Docker-related commands have been added.
For information about TIBCO BusinessEvents Maven plug-in phases, see BusinessEvents Maven Plug-in Phases.
Docker
- You can now specify any of the BusinessEvents engine and JVM properties as environment variables while running BusinessEvents applications in Docker. For more details, see Running TIBCO BusinessEvents® Application in Docker.
- In Linux platform, you can now generate BusinessEvents image of a significantly reduced size. For more details, see (Linux Only) Building a Lightweight Docker Image for TIBCO BusinessEvents®
TIBCO BusinessEvents Enterprise Administration Agent
- You can now auto-detect TIBCO BusinessEvents installations for individual machines. For more details about auto-detecting TIBCO BusinessEvents installations, see Auto-detecting BusinessEvents Installations on Host Machines.
- You can now create duplicate deployment profiles that you can reuse in different environments. For more details about duplicate deployment profiles, see Creating a Duplicate Deployment Profile.
- You can now use existing global variables, TIBCO BusinessEvents properties, and system properties while creating a deployment profile. For details about creating a deployment profile, see Adding an Application Deployment Profile.
- Added new operations in TIBCO BusinessEvents Enterprise Administration Agent CLI to:
For more details about TIBCO BusinessEvents Enterprise Administration Agent CLI commands, see TIBCO BusinessEvents Enterprise Administrator Agent Commands Reference.
Configuration Properties
- Added the be.engine.cluster.as.connection.retry.count property to configure the number of connection retries. For more details about the be.engine.cluster.as.connection.retry.count property, see CDD Cluster Tab DataGrid Properties Reference.
- Added the be.channel.jms.session.recover.onAckFailure property to specify if session auto-recovery is required in case of the acknowledgment failure of unexpired messages. For more details about the be.channel.jms.session.recover.onAckFailure property, see CDD Processing Units Tab JMS Server Connection Properties.
- Added support for creating composite indexes for concepts from the CDD file. For more details about the composite indexes section, see CDD Cluster Tab Domain Object Override Settings Reference.
The studio-tools Utility
The studio-tools utility has a new parameter -jc for the buildEar operation to include the specified Java classpath. For more details about the buildEar operation, see Building an EAR File at the Command Line.