Axway Sentinel


You must log in or register to view this page

Axway Sentinel is a real-time Business Activity Monitoring (BAM) solution that provides end-to-end visibility into business processes. It helps organizations monitor data flows, ensure compliance, and prevent potential losses by tracking events from various applications and systems, including both Axway and third-party systems. By leveraging Sentinel, users create dashboards for real-time monitoring of key performance indicators and trigger automated responses to events. 

Architecture

The example of the product components and patterns interaction is displayed in the following table.

Software pattern summary

The following table gives an overview of the pattern characteristics:

Product component

OS type

Versioning

Pattern depth

Axway Sentinel

UNIXCommand (Active), PathInstance-based

Platforms supported by the pattern

The pattern discovers Axway Sentinel deployments on the UNIX system.

Identification

To run a discovery of the product, the pattern must be triggered. This section describes conditions under which the pattern can be triggered.

Software instance triggers

The following table gives details about the pattern trigger:

PatternTrigger nodeAttributeConditionArgument
Axway SentinelDiscoveredProcess

cmd 

matches

unix_cmd 'java'

 and 
argsmatches

regex

(?i)sentinel-common-core-\d+\S+?\.jar

Simple identification mappings

The following component/process is identified by using the simple identity mappings that map the product's known processes:

Name

Condition

Axway Sentinel

 

unix_cmd 'java'

regex

(?i)sentinel-common-core-\d+\S+?\.jar

Versioning

Version information for the product is collected by using the active and path versioning methods.

Active versioning

If the install root is defined, the pattern constructs the path to the display.sh script by using the install root and runs <install_root>/display.sh | grep Sentinel on the target host. It captures the output and extracts the version number by using a regular expression. If the command fails or does not return a version, it does not proceed further.

Path versioning

The pattern attempts to extract the version from the installation path by using this regular expression:

(?i)V(\d+(?:\.\d+)*)

Subject matter expertise

Inputs from subject matter experts are welcome on any other potential approaches not discussed in this topic.

Testing

The pattern has been tested against the available customer data.

Open issues

There are no known open issues with this pattern.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*