...
For more information, see SAP Subscription Billing.
Version Handling for Streams
Streams now include configuration information in versions, providing the possibility to save specific configurations within the functions. You can explore different configurations for each function(s) within the stream.
The parameters and configurations are separated for a more convenient setup — configurations refer to the parameters that define the behavior of the individual Functions placed within the stream while the parameters define the operational aspects.
Versioning provides control mechanisms on when to save a working stream version.
Streams created in this way allow for easier comparison between the exports. The addition of tags and comments allows for easier organization and management of complex use cases.
...
Use Cases
Creating a Test Environment for Stream Testing
In this use case, you can create a test environment for stream testing without the need to modify the logic of the original stream. When you want to test a stream in a different environment, a new copy of the stream is generated, ensuring the integrity of the original stream's configuration. The only adjustment required is to modify the parameters of the copied stream, directing them to the test environment. By doing so, you can safely evaluate the stream's functionality and performance without introducing any risks associated with modifying the original stream. This allows for thorough testing while maintaining the reliability and stability of the production stream.
Stream Optimization and Configuration Replacement
This use case focuses on stream optimization by allowing you to create a copy of the stream and test different codes, add or remove nodes, and experiment with a new configuration. Once you are satisfied with the optimized version, the existing stream can be seamlessly replaced with the new version, all while preserving traceability through logs and audits. By enabling you to make changes and evaluate the performance of the new configuration, this use case ensures that stream optimization can be achieved without sacrificing accountability and traceability. The ability to replace the existing stream with the optimized version streamlines the implementation of improvements and enhances the overall efficiency of the system.
Improved Stream Handling
A new mode called View, has been introduced to prevent unintended changes to the stream configuration. In contrast, the Edit mode grants the flexibility to modify all aspects of the stream.
The introduction of View and Edit modes ensures the protection of the stream when multiple individuals are editing simultaneously. Versions are initially created in Edit mode and subsequently opened in View mode. This distinction helps maintain the integrity of the stream configuration. It is important to note that only users with delegated permissions have the authority to revise the stream's configuration and parameters, ensuring proper control and governance.
To prevent the loss of any changes made to a configuration, the stream management system includes an integrated autosave functionality. When editing a stream in Edit Mode, the system automatically saves the changes as an autosave version. This ensures that the latest modifications are securely stored until the user commits the changes. By keeping a single autosave version, the system avoids cluttering the View History with multiple versions. The primary purpose of this functionality is to safeguard against unintended loss of configuration changes and provide users with the ability to revert to a previous configuration if desired. This streamlined approach ensures efficient management of changes while maintaining the integrity of the stream's configuration.
This functionality simplifies the tracking of changes during stream development, making it more convenient to monitor the progress. Versions are easily identifiable in the logs and audit information, providing a clear history of modifications. The ability to handle versions brings valuable usability benefits, allowing updated configurations to seamlessly update existing streams while preserving their states, history, logs, and audit information. This ensures a smooth transition and enhanced manageability of the stream environment.