Show / Hide Table of Contents

    What is new in Sentinet version 6.4

    1. Sentinet 6.4 requires .NET Framework version 4.8 Runtime to be installed on the computer(s) where Sentinet is running to take advantage of the latest Microsoft full .NET Framework version.

    2. Extended support for automated Sentinet deployments in the Microsoft Azure platform by providing Azure ARM templates, supporting files and documentation. Sentinet can now be installed in any cloud and in the Microsoft Azure Platform specifically from a single command with all required components, and with auto-scalability and network security requirements.

    3. Sentinet Virtualization Profiles feature, introduced in Sentinet 6.3, was further enhanced in Sentinet 6.4 to support additional configuration settings for “one-click virtualizations”. Each Virtualization Profile can be now configured with additional and optional Processing settings, Processing Pipeline and Monitoring settings, which include Monitoring Profile, Monitoring Tracing and Monitoring Filters.

      Virtualization Profiles Processing

      Virtualization Profiles Monitoring

      Virtual Services’ Name can be constructed using either a predefined Prefix, Suffix, or both. The default is still _vs Suffix.

      Prefix and Suffix

    4. Added new Pipeline Component, Cache Properties which allows to cache values of Context Properties and use them anywhere in the Processing Pipeline. Cache Property’s value is valid and available across multiple API calls until cache is expired. For example, you may make a custom external call from the Pipeline using HTTP Invoke component, and store something from its response in the Cache Property with the goal to use this response from the cache, and to avoid making external calls until Cache Property’s value expires.

      Cache Properties

    5. Extended Context Property component’s configuration to specify Cache Property as a Value Source. This allows to use Context Properties with values assigned from the values of Cache Properties (see example above, where Context Property value assigned from the Cache Property value can be used to examine if external calls must be bypassed).

    6. Extended Context Property component’s configuration to allow using other Context Properties’ values in the name of this Context Property.

      Property Name

    7. Context Property component’s configuration was extended to support Encrypted String Value Extractor to allow hidden usage of secrets in the Pipeline’s User Interface.

      Encrypted String

    8. Set HTTP Status Code and Stop pipeline components were extended to allow usage of a Context Property as the value of HTTP Status Code field.

      Usage of a Context Property

    9. Monitoring Filters are extended with Design view, where Monitoring Filters can be added/removed or modified interactively. Source view can still be used to configure Filters in raw XML format as in Sentinet version 6.3.

      Monitoring Filters Design

    10. Importing Sentinet export packages using Sentinet Administrative Console was extended to support User Interactive resolution of unmatched Sentinet Node(s). Previously, if Sentinet export package contains references to Sentinet Nodes which are not found in the target environment (there is no actual Node with the same Node Key as in the export package), Sentinet users had to either modify export package before it is used for import, or change Node Key to “pre-synchronize” source and target environments. With Sentinet version 6.4 Import Repository dialog box will show any Nodes that are not found in the target environment and suggest to resolve (to match) them against available Nodes. This simple step helps to avoid any manual changes in export packages or reconfigurations of the Nodes.

      Unresolved Nodes

    11. Extended X.509 Certificates’ expiration notifications with additional certificates, which are not monitored by default. For example, users can add their own Nodes’ SSL certificates to the list of certificates monitored by Sentinet.

      Monitored Certificates

    12. Added optional filtering of Access Rules based on the API element selected in the virtual service’s tree.

      Without Filtering

      Figure. All Access Rules without filtering.

      Show Applicable Only

      Figure. Access Rules applicable only to selected Multiply two integers selected API operation.
    13. Added Sentinet.ApiKey built-in Context Property which contains API Key provided in the request message.

    14. Added configurable number of days when Developer Portal Users start receiving API Key Expiration notification emails.

      API Key Expiration

    15. Added context specific prompt suggesting to use correct SQL syntax when searching transactions logs by the content of request and response messages, and Monitoring Properties’ values.

      SQL syntax Prompt

    16. Sentinet configuration (including its Repository Configuration Wizard) was extended to support SQL server Remote Distributor.

      Remote Distributor

      Note

      This feature was supported in some latest Sentinet 6.3 builds.

    17. Sentinet configuration (including its Repository Configuration Wizard) was extended to support bypassing Setup of SQL server replication, and allowing to configure replication outside of the Sentinet configuration.

      Bypass Replication

    Back to top Nevatech Sentinet Online Documentation