Axway Sentinel 4.2.0 release notes

Product and documentation delivery

The installer program, Sentinel 4.2.0 installation package, and all product documentation are available for download from the Axway support website: https://support.axway.com.

  • The Axway Sentinel Installation Guide has been reformatted and updated. This guide includes information on system prerequisites, requirements, installation, configuration, and upgrade requirements.
  • A new guide called the Axway Web Dashboard User Guide has been created. This guide includes new features and functionality for the Sentinel Web Dashboard feature.
  • The Axway Configuration User Guide has been reformatted and updated to include new features and functionality.

New features and enhancements

Infrastructure changes

With this Sentinel version, Axway Administration and Infrastructure modules are no long part of the Sentinel installation packages. Since Axway Infrastructure comprised the default web server Axway Tomcat (version) used to deploy Sentinel web application, in Sentinel 4.2.0 a new web server (Jetty version 8) is delivered with Sentinel. The commands used to start, stop and acquire the status of Sentinel will also act on the embedded web server, rendering the operation of Sentinel much simpler.

During upgrade, Sentinel web applications are automatically migrated to the new web server if they were initially deployed on the default internal web server (Axway Tomcat). Notably, the default ports where Sentinel web applications (Sentinel Monitoring and Sentinel Web Dashboard) will be available in this case, will change to 1309. If deployed on an external web server, the mentioned web applications will not be moved, nor will the associated ports change. For more information about the upgrade of installations done with Axway Installer's Cluster-mode, refer to the Axway Sentinel Installation Guide.

Cluster-mode installation

Prior to Sentinel 4.2.0, Axway Installer offered the "Cluster-mode" installation, to ease the deployment of Sentinel in Active/Passive clusters. Since this installation mode only provided a limited cluster installation, not responding to the needs of customers, it was removed in Sentinel 4.2.0. For more information on the upgrade from a cluster-mode installation, refer to the Axway Sentinel Installation Guide.

Regardless, Sentinel 4.2.0 continues to support deployment in an Active/Passive cluster by using the Advanced installation mode, and manually installing the product on the different cluster nodes. Depending on the users' needs, the shared disk content must be selected and implemented manually.

In the near future, documentation will be available on a reference Active/Passive cluster installation for Sentinel. Until then, contact your Axway representative for additional support on how deploy Sentinel in Active/Passive cluster in your environment.

User access management in Web Dashboard

Starting with Sentinel 4.2.0, integration between PassPort AM and Sentinel Web Dashboard is significantly improved. Custom user exit and Sentinel Administration has also been enhanced to facilitate centralized governance of Web Dashboard access management. The main improvements include:

  • Fine grained access in Web Dashboard can be controlled entirely from within PassPort, using new predefined or custom privileges. The list of PassPort predefined privileges was enriched to control access to Web Dashboard objects. New PassPort resources and associated actions are added for extended flexibility, allowing the definition of custom privileges. The notion of Web Dashboard Workspace is removed, contributing to the simplicity and efficiency of fine grained access management in Web Dashboard. For installations obtained via an upgrade, manual configuration is necessary to activate Web Dashboard fine grained access management from within PassPort. User access management when using Sentinel Administration or a custom user exit is not changed. For more information, see the Axway Sentinel Web Dashboard User Guide, section User access management.
  • Email addresses and phone numbers of PassPort users are automatically reused in Web Dashboard when sending email notifications or SMS. This improvement significantly simplifies the set up and maintenance of Web Dashboard notifications.
  • Access to data can be controlled per user or user group centrally from within the access manager, relying on Personalized fields. Since Sentinel 4.2.0, Web Dashboard Personalized fields may be directly defined from the access manager of choice (PassPort AM, custom user exit or Sentinel Administration). For more information, see the Sentinel Web Dashboard User Guide, section User access management.
  • Each Web Dashboard user can set in their preferences the preferred language, time-zone, Web Dashboard theme and Web Dashboard home page. In addition, administrators can set defaults centrally from the access manager of choice.

Execution of Sentinel Commands (external scripts) from Web Dashboard

Starting with Sentinel 4.2.0, Sentinel Commands are automatically available in Web Dashboard searches. As Sentinel Commands enable the user to execute external scripts or even custom Java classes from the context of search results, this can be a very powerful feature extending Sentinel's capabilities. In addition to the usual features of Sentinel Commands (for example, remote execution on Event Router and interactive command execution taking into account user input), Web Dashboard simplifies the use of Sentinel Commands. Also, combining Sentinel Commands with the capabilities of Web Dashboard makes these much more flexible and powerful. For additional information about Sentinel Commands in Web Dashboard, see the Axway Sentinel Web Dashboard User Guide.

Accessibility Compliance

Axway strives to create accessible products and documentation for users. Accessibility in Sentinel is understood as the design of Sentinel and its services for people with disabilities; therefore, it complies with standards like the United States Section 508 requirements or the Web Content Accessibility Guidelines (WCAG) Version 2.0.

For Sentinel 4.2.0 a pragmatic approach is adopted, with immediate benefit for users with disabilities. The strategy contains two directions:

  • Identify and focus on the right persona
  • Identify and work with the key use cases

Sentinel persona can fall into three big categories:

  • Administrators: users who install, operate, configure and maintain the product.
  • Developers: users who provide content, for example who create reports and dashboards.
  • End Users: users who work with reports and dashboards created by developers.

Users matching the End User persona outnumber all other users in Sentinel; therefore, they are the main target of accessibility in Sentinel. The only strategic application destined for the End Users is Sentinel Web Dashboard. By focusing on the correct Sentinel module, the identified people and on realistic use cases, we ensure a relevantly accessible product. For details on accessibility (for example, the covered accessibility categories or the different scenarios) read more in the Axway Sentinel Web Dashboard User Guide.

Note   For maximum accessibility, we recommend using Internet Explorer 11 and JAWS screen reader version 15.

Security improvements

Since security is a constant concern for Sentinel, in Sentinel 4.2.0 we have added the following related features:

  • TLSv1.2 is added as the default protocol used in secure communications. In comparison, SSLv3 is not allowed by the latest Java 8 updates and several browsers.
  • It is possible to configure a secure connection between Sentinel and the underlying database, during or after installation. This is valid for Sentinel server, but also for Sentinel Web Dashboard. World objects in Web Dashboard can also be configured to rely on secure connections.
  • Auditing user actions in Web Dashboard is available, totally integrated with the already existing audit mechanism in Sentinel. This means the already existing configurations regarding audit apply to Web Dashboard, as well as the target output (Tracking Database or files on the file system). Only sensible activity is tracked (for example, creation or deletion of objects).
  • By full support of Java 8 Runtime Environment, you benefit important security updates of the Java Runtime Environment.

Composer replacement

In our effort to eliminate Composer from the product dependencies of Sentinel, the Sentinel REST API is enriched with services to handle the deployment into and removal from production of Sentinel Tracking Objects and Sentinel Commands without the need to restart Sentinel server. With this, customers relying only on Sentinel Web Dashboard for data representation do not need Composer to design and deploy the necessary configuration for Sentinel.

To encourage the usage of Web Dashboard as a replacement for Dashboard V3, it is now possible to deploy custom maps in Web Dashboard reports and dashboards. Maps can be created from scratch in the form of SVG files and can be used in reports and dashboards. This allows the creation of fully adapted content to meet business needs.

Enhanced command line import/export tool for Web Dashboard

With Sentinel 4.2.0, exporting Web Dashboard object is much easier. You can quickly specify the objects you want to export by using the well known wild-cards (*) and (?).

Cross-database portable data dictionaries, reports and dashboards in Web Dashboard

By carefully designing data dictionaries, they can be configured to support cross-database portable reports and dashboards. With a simple setting, you can create case insensitive data dictionaries that retrieve data from any case insensitive database server.

Usability enhancements on Web Dashboard reports and dashboards

With Sentinel 4.2.0, the following enhancements were implemented to enhance the visibility and efficiency of end users what concerns reports and dashboards:

  • Filters applied on dashboards are visible. This enhances visibility on dashboards. Filters applied on reports are also enhanced and redesigned to be read easier.
  • When navigating from one report to another, a bread-crumb trail helps the user to ease navigation. This makes investigations using drill-down much faster and easier.

Proactive features

Alerting by email on reaching a certain threshold for the Sentinel buffer files is possible with Sentinel 4.2.0. This way, administrators can take preventive measures in time, to avoid the situation when Sentinel is no longer able to process events.

Additional supported databases

The following databases were added to this release:

  • Microsoft SQL Server 2014
  • MySQL 5.7

Additional supported platforms

The following platforms were added to this release:

  • Red Hat 7
  • Suse Enterprise Linux 12
  • Oracle Enterprise Linux 6, 7

For the client side only (concerning the operation of Sentinel client applications), additionally to Windows 7, the following operating systems are supported, starting with Sentinel 4.2.0:

  • Windows 8.1
  • Windows 10

Platforms with discontinued support

Since the following platforms do not offer support for Java 8 or have reached end of mainstream support, they are not supported starting with Sentinel 4.2.0. There is no install package for these platforms and no Upgrade Pack.

  • Oracle Solaris 10 on sun-x86-32 and sun-sparc-32 bit architectures
  • HP-UX 11iV1 (11.11)
  • HP-UX 11iV2 (11.23)
  • Suse Linux Enterprise Server 10
  • Windows Server 2003
  • Windows Server 2008
  • Windows Server 2008 R2

Database servers with discontinued support

Since the following database servers have reached their mainstream support, they are not supported starting with Sentinel 4.2.0.

  • Microsoft SQL Server 2005
  • Microsoft SQL Server 2008 R2
  • MySQL 5.1
  • Oracle 10gR2 (10.1)
  • Oracle 11gR1 (11.1)

Supported Java Runtime Environment

Sentinel 4.2.0 is fully Java 8 compliant, and is also incompatible with earlier Java versions (6 and 7). It embeds a Java 8 Virtual Machine for the Sentinel Server and requires a Java 8 Runtime Environment on the client side. By supporting Java 8 on both server and client side, you can benefit of the numerous Oracle updates concerning the Java Runtime Environment rendering your environment safer and more performance.

The Java Universal Agent API binaries delivered within the Sentinel installation are also Java 8 compatible and automatically incompatible with previous Java versions.

Fixed issues

Internal ID Description
142717 In case of a distributed Sentinel environment, if the V3 dashboards are configured to refresh upon arrival of Sentinel notifications, they fail to do so. With this fix, the V3 dashboards will be correctly refreshed if configured so.
151952 The Oracle driver delivered in Sentinel is not up-to-date (is version 11). This could impact DataGuard support, secure database connection, etc. With Sentinel 4.2, the employed Oracle JDBC driver version was updated to 12.1.0.2.
140790 It is not possible to activate or deactivate the RMI API with a manual configuration setting on Sentinel server side. With this fix, the RMI API is by default deactivated, and a manual configuration action is necessary on Sentinel server side to activate it.
150024 It is not possible to configure JVM arguments for Sentinel server without modifying the trkserver script. With this fix, it is possible to define the environment variable SENTINEL_JVM_OPTIONS. The value of this variable is transmitted to the Sentinel JVM.
145473 In Alerts UI, when editing and copying an alert from the Detailed view page, actions on Chrome are blocked in loading if the login is done through Single Sign On.
150925 Sentinel Java Universal Agent API does not support TLSv1.1 and TLSv1.2 protocols. With this fix, the protocols are supported.
131428 The parameter "timerRulesPerThread" is not documented. With Sentinel 4.2.0, the Axway Sentinel Configuration Guide was updated with the necessary information.
141711 In Sentinel Web Monitoring (Flex) the Event Graph window freezes if it is opened from Cycle Graph window.

Known issues

  • Criteria comprised of multiple conditions in Correlation rules are not evaluated correctly. Due to this defect, false alerts can be triggered. This impacts Correlation engine and alerts in Alerts UI. It is strongly recommended to apply Service Pack 1 after installing Sentinel 4.2.0 or after upgrading to 4.2.0.
  • Web Dashboard reports containing a field of type WEEK cannot be executed on World object pointing to a DB2 database.
  • PassPort user properties cannot be accessed if at least one public property of type "Date only" or "Time of day" is defined in PassPort. As a workaround, do not define such public properties in PassPort (140996).
  • REST API cannot be deactivated using the setting publicapi.rest.enable=false in server.properties.
  • The Data Entry Assistant cannot be accessed for Sentinel Monitoring Applet
  • SMTPhost is not correctly updated using updateServerProperties tool
  • Sentinel applets (Sentinel Monitoring, Sentinel Correlation Viewer and Sentinel Administration) cannot be accessed with Google Chrome version 45 and later, due to the limitations introduced in the browser. We recommend using other supported browsers to access the Sentinel Applets. See the list of supported browser in the Sentinel Installation Guide.

Axway Sentinel is accompanied by a complete set of documentation, covering all aspects of using the product. These documents include the following:

  • Axway Sentinel Release Notes
  • Axway Sentinel Configuration Guide
  • Axway Sentinel User Guide
  • Axway Sentinel Web Dashboard User Guide
  • Axway Sentinel API Developer Guide
  • Axway Sentinel Installation Guide
  • Axway Sentinel Security Guide
  • Axway Supported Platforms
  • Axway Interoperability Matrix
  • Axway Interoperability Guide
  • Axway Database 4.6 Administrator Guide

Support services

The Axway Global Support team provides worldwide 24 x 7 support for customers with active support agreements.
Email support@axway.com or visit docs.axway.com.

Copyright © 2015 Axway. All rights reserved

 

Related Links