Eliminate the impact of temporary access loss to the VBD cluster (8.4)
Improvements to the reliability of Visual Business Director (VBD) include the ability to continue writing data to a VBD dataset while the corresponding server node is unavailable, enhancements to single-case data flows that write data to VBD, and a reduction in the VBD cache size.
Starting in version 8.4 of Pega Platform™, VBD uses Stream API to asynchronously write data to the VBD server. Each VBD server node listens to the stream and reads the records from the stream in batches. If a node is temporarily unavailable, the writing can now continue, improving the stability of the process.
After a previously unavailable node is back online, you can now check the new Real-time Data Grid page for information about the node status. The diagnostic displays the number of records that have not yet been read from the VBD stream. If nodes are working without incident, the diagnostic shows no records, as in the following figure:diagnostic on the
If a node is or was recently unavailable, the diagnostic shows the number of records that remain to be processed. After the node is back online, the number should automatically decrease over time, as VBD data is read from the stream.
Previous topic Configure your chatbot for detecting small talk (8.4) Next topic Enrich your Proposition Filter rules with conditions based on strategy results (8.4)