Striim 4.0.4 documentation

Table of Contents

What's new in Striim 4.0.4

The following features are new in this release.

Web UI

  • The console is available in the web UI (see Using the console in the web UI).

  • Users and roles can be managed in the web UI (see Users page).

  • Files can be uploaded to the server through the web UI (see My Files).

  • The Apps page can be filtered by name, status, and namespace.

  • The Message Log includes notifications of many routine events, such as completion of initial load and connection retries.

Application development

Sources and targets

Change data capture

  • Almost all special characters are supported in schema, table, and column names (see Using non-default case and special characters in table identifiers).

  • MongoDB supports SSL with TLS and Kerberos authentication.

  • Oracle Reader automatically buffers transactions larger than 100MB to disk (see "Transaction Buffer Type" in Oracle Reader properties).

  • Oracle Reader can read read tables containing BFILE columns, though the BFILE values will be null (see Oracle Reader data type support and correspondence).

  • PostgreSQL Reader supports Azure Database for PostgreSQL, Azure Database for PostgreSQL Flexible Server, and Google Cloud SQL for PostgreSQL.

  • PostgreSQL Reader supports wal2json version 2, which supports transactions larger than 1 GB.

Administration and monitoring

  • The discarded event count is displayed in Flow Designer (see Viewing discarded events).

  • Vaults can secure any property values, including passwords, tokens, and keys (see Using vaults).

  • The STOP command may be used on an application that is starting, and the UNDEPLOY command may be used on an application that is deploying.

  • The HALT status indicates that an application failure is due to an external cause, such as a source or target database being offline (see Application states).

  • Kafka SASL configuration has been moved from the Striim server environment to KafkaWriter's Kafka Config property (see Configuring Kafka). This allows SASL properties to be specified for multiple Kafka clusters.

  • LDAP authentication supports samaccountname. A single LDAP property set can support multiple users and multiple DCs (see Using LDAP authentication).

  • End-to-end lag (LEE) can display summary statistics for the most recent data or for a specified interval over a specified time range (see Monitoring end-to-end lag (LEE)).

Installation and configuration