What's new in Striim Platform 5.4.4

Creation and maintenance of Db2 for z/OS CDC applications has been simplified with a more integrated experience to manage the Striim Agent for Db2 for z/OS.

After you have set up the Agent for Db2 for z/OS, you can manage the entire lifecycle of the data pipeline from within the Striim UI, including creating, modifying, starting, and stopping the pipeline. You can configure your Db2 credentials using Striim Vault and you can apply Striim’s roles and permissions to your Db2 pipelines. You can observe error messages from the Agent for Db2 for z/OS from the Striim UI and monitoring systems. Any failures in the Db2 processes will gracefully propagate to Striim, and the application will halt or terminate depending on the severity of the failures.  You can also review and debug the Agent configuration from within the Striim UI.

Striim syntax offers improved support for the Agent for Db2 for z/OS and Db2 pipelines. For example, the DESCRIBE component will print the Agent’s properties, and Db2 pipelines now support the SCHEMA.TABLE syntax that is supported by Striim’s adapters for relational databases.

For more information, See Db2 for z/OS initial setup for CDC and Creating a Db2 for z/OS CDC application.

Spanner Writer and Spanner PG Dialect Writer support writing to UUID and UUID array columns, and Spanner Batch Reader and Spanner Database Reader support reading them, in both the GoogleSQL and PostgreSQL dialects. UUID columns are detected automatically, with no additional properties required, and UUID columns can be used as primary keys and key columns. This simplifies replication to and from Spanner for tables that use UUIDs as identifiers. For more information, see Support for UUID data types in Spanner targets.

Smart Alert and custom alert notifications sent by email, Slack, or Microsoft Teams now identify where an alert originated by including the Striim product name and the cluster name. In email notifications, the subject line begins with the cluster name. This makes it easier to identify, filter, and route alerts when you run multiple Striim clusters. No configuration is required.

If you use mailbox rules or other automation that matches the full subject line of alert emails, or that parses Slack or Teams alert messages, update it to account for the added name.

For more information, see Alerting in Striim.

Striim Platform now ships with Kafka 4.3.1, upgraded from Kafka 3.9.1. This upgrade resolves four High CVEs reported in Kafka 3.9.1. The internal Kafka server used for persisted streams runs in KRaft mode and no longer uses ZooKeeper. For more information, see Persisting a stream to Kafka.Persisting a stream to Kafka