What's New

The What's New topic lists new and revised features of TIBCO BusinessEvents® Enterprise Edition version 6.3.0 compared to the previous version with reference to documentation.

• Apache Pulsar® Channel

  You can now use Apache Pulsar® channel to send and receive messages from a Pulsar broker. The Pulsar channel converts the incoming Pulsar messages to BusinessEvents events and transforms BusinessEvents events as outgoing Pulsar messages.

  For details, see Apache Pulsar Channel.

• Support for Apache Avro™

  A new serializer KafkaAvroSerializer serializer (com.tibco.cep.driver.kafka.serializer.KafkaAvroSerializer) has been added to support Apache Avro™ schemas.

  TIBCO BusinessEvents® Enterprise Edition now supports validation of Apache Kafka® messages by using Schema Registry. Schema Registry ensures data consistency and increases data quality. In this release, Confluent Schema Registry and TIBCO Schema Registry are supported.

  For details, see Using the Apache Kafka Schema Registry.

• Using Apache Cassandra™ as a Channel

  You can use DataStax CDC for Apache Cassandra® to read Change Data Capture (CDC) changes and publish messages to pulsar topics. Then Pulsar channel processes messages published on the pulsar topic and ingest events into TIBCO BusinessEvents® Enterprise Edition application.

  Apache Cassandra™ Store Catalog functions available in the TIBCO BusinessEvents Contribution repository in GitHub allows you to connect to external Cassandra and perform different operations.

  To use these features, see TIBCO BusinessEvents Contribution repository in GitHub.

• Store based locking implementation

  Earlier locking was implemented as part of the cluster provider: FTL, Ignite, or Legacy ActiveSpaces. Now you can implement locking on the underlying store. Store-based locking provides a single consistent way of locking irrespective of cluster and store provider combination.

  For details, see Implementation of Locking by Using a Store.

• System Metrics Enhancements

  You can now monitor the following system metrics by using any configured metric store:

  • RTC Transaction Manager Report

  • Individual Agent Performance Attributes

  • Cache Performance Attributes

  • Overall Inference Agent Statistics

  You can now configure whether the application metrics of an entity need to be published or not.

  For more information, see Application Metrics Configurations.

• Support for data center replication by using GridGain

  TIBCO BusinessEvents® Enterprise Edition now supports Data Center replication feature by using GridGain. By replicating data across multiple data centers, you can prevent downtime during any of the data center failures. By using GridGain, you can replicate cache data between clusters.

  For details, see Configuring Apache Ignite as a Cache Provider.

Changes in Functionality

The following functionality has been changed in this release of TIBCO BusinessEvents® Enterprise Edition:

• The following features are moved to GitHub. These features are no longer bundled with TIBCO BusinessEvents Enterprise Edition. To use these features, see TIBCO BusinessEvents Contribution Repository in GitHub:
  • Kinesis Channel

  • Kafka Streams Channel

  • MQTT Channel

  • StreamBase Channel

  • TIBCO LiveView Metric Store

  • Analytics Catalog Functions

• TIBCO® Enterprise Administrator JARs are removed from the BE_HOME/teagent/lib/teasdk folder. The TEA_HOME environment variable is added in the be-teagent.tra file. When running the TIBCO BusinessEvents Enterprise Administrator agent, you must set the TEA_HOME in the be-teagent.tra file.

• When running the hot deploy phase of BusinessEvents application, you can skip the earlier phases by using the disablePhases property. You can add this property in the pom.xml project file inside the beProjectDetails tag. After adding this property all earlier phases: compile, test, package, and install are skipped.

• Datadirect SQL Server JDBC driver JARs are no longer bundled with TIBCO BusinessEvents Enterprise Edition. In the Linux environment, this driver allows you to connect to SQL Server by using Windows authentication. To use Datadirect SQL Server JDBC driver, use the following steps:

  1. Download Datadirect SQL Server JDBC driver JARs and copy into <TIBCO_HOME>/lib/ext/tibco.

  2. Edit the project JDBC resource to specify driver name and Database URL as global variables. In the global variable, use driver name as com.ddtek.jdbc.sqlserver.SQLServerDriver. Ensure to have AuthenticationMethod=ntlmjava in the Database URL.

     For more information, see JDBC Connection Reference.

TIBCO Software, Platforms, and Third-Party Software

For the updated list of supported TIBCO Software, platforms, and third-party software, see the readme.txt file provided with TIBCO BusinessEvents® Enterprise Edition.