The features listed below were added to DPOD. The following conventions are used in this document:

 - Some actions are required to enable the feature.
 - This is a Tech Preview feature. Consult the release notes for more information. 

New Features 1.0.7

Tenant Support 

• Added the ability to monitor transactions information on appliance with Tenants.
• Resource monitoring and appliance maintenance are not available for tenants.

API Connect Integration

• New API Connect Recent Activity dashboard that displays a high-level overview of APIs activity.
• The Early Failing Requests Dashboard in now also available in API Connect view.
• Alerts can be generated based on some of APIs latency data.
• Auto Setup Domains feature detects a Domain Reset to auto-setup it again.

Maintenance Plans Improvements

• DPOD now provides the ability to upgrade virtual and physical appliance firmware (requires firmware 7.5+) - see limitations

• Maintenance Plan for Syncing DataPower Appliance Configuration is now supported (initially announced as tech preview from v1.0.5)

Improved User Experience

• The transaction error analysis now indicates whether a probe was enabled during its execution.
• New latency alerts based on percentile.
• Added latency percentile data to Service URL/URI Calls dashboards.
• Payload capture can be enabled on multiple devices or domains at once.

• DevOps Services Portal - allow to setup a separate temporary domain (for WSDL validation and promotion) for each device.

• Columns can be hidden or reordered in the Transactions, Raw Messages and API Connect Transactions pages.
• New Internal Monitoring page that shows DPOD's components status and recent alerts to assist monitoring DPOD internal health.

New Features 1.0.6

DevOps Services Portal 

• DPOD now provides a new self service DevOps portal for traditional services. This is a new portal dashboard where end-users can:
  
  • Execute two new actions on SOAP Web services with local WSDL: validate and promote
    • The Validate action uploads your new WSDL and schema files to a temporary location, validates its compilation and creates a temporary WS-Gateway to ensure the object is up.
    • Promote action allows uploading a new WSDL and schema files to the target location (device and domain) and creating a new version of the service.
  • Execute two new actions on SOAP Web services with remote WSDL: validate and promote
    • The Validate action updates a new or existing URL of a remote WSDL, validates its compilation, and creates a temporary WS-Gateway to ensure the object is up.
    • The Promote action updates a new or existing URL of a remote WSDL in a target location (Device and Domain), and creates a newer version of the service.
• All actions require permissions set by a security policy (custom roles).
• Each action may be extended or customized using Python scripts. Example scripts are open source and may be obtained from a git repository - see docs 

Early Failing Requests dashboard

• Added a new dashboard for early failing requests (such as TLS/SSL failures) - where a request is received but is unable to reach the execution phase of a Processing Rule of a Service - (requires firmware 7.5.2.4+)

Service API Dashboard

• DPOD now provides a new dashboard that provides statistics pertaining to service URIs. These statistics include the number of invocations and min/max/avg latency in addition to the Service API (URL) Dashboard

Improved User Experience

• Users can now save favorite filter combinations and use them in subsequent sessions.

• A new free text search field was added to the Transactions List page and Raw Messages Page where the user may enter a single value that will be searched across various data fields.
• Service filter now supports auto completion.
• All applicable filters support multi-select of values.
• Users can now change the size of the series (number of values) that is displayed in charts of type "top N".
• A recent notifications panel was added to The Navigation Bar. It displays the recent UI notifications for the user (not persisted).
• A new "Share" button added. It allows sharing the current page (including filters, transaction ID etc.) by copying/pasting the current URL or by sending it via email
• Time range filters now provides more options: last 10 minutes, start of day, start of week, this month.
• Consistent behavior across pages of zoom into a transaction or use its value as a filter criteria.

Data Migration Procedure

• From time to time, DPOD customers may be required to install a new DPOD installation while preserving the data already collected. for example:
  • Customer deployed DPOD Appliance mode at version v1.0.0 with CentOS 6.7 and now requires to migrate to CentOS 7.2 introduced at version v1.0.2+.
  • Customer deployed DPOD on a virtual server but load increased and now requires a physical server.
  • Customer deployed DPOD Appliance mode but wants to migrate to Non-Appliance mode (RHEL) to better comply with their organization security requirements and standards.
• New procedure and tools were introduced to support customers with migration of an existing DPOD Store data to a new DPOD installation in each of the scenarios above.

New Features 1.0.5

API Connect Integration

DPOD now has new capabilities when coupled with API Connect v5.0.7.2+ (API-C) and DPOD

• Display a dedicated transaction list with only API-C transactions

• Filter by API-C fields (e.g. API name, API version, catalog, HTTP method, API urls and a dozen more fields)

• Calculate and display latency graphs for each policy execution inside an API (including custom policies)

• Provide both API-C and DataPower views of the same transaction, and the ability to switch between them

• A new dashboard of APIs and the date they were last executed in the system.

• API payloads may now be captured

• Automatically run setup DPOD log targets for each new API-C domain created. (This requires enablement in the monitored device configuration). Further configuration based on domain name prefix is available.

 To activate API-C integration, perform (from the Web Console) a re-configuration of all your log targets in the DataPower that runs the API-C domain. You can also use the auto-setup feature to handle API-C domains created in the future.

Maintenance Plan for Syncing DataPower Appliance Configuration () - see limitations

DPOD now provides a multitude of syncing capabilities:

• Sync a single source configuration (domains/devices from a single appliance) to multiple targets (domains/devices) accordingly. Wildcard patterns supported.

• A script may be executed as part of the sync lifecycle - before running, on completion and before/after each single sync.

• Periodic sync task scheduling 

• The domain or device may be quiesced before execution

• Configuration sync with password map alias, provided that phrase and all objects are already at target and completely identical (firmware 7.5.2.4 and above)

 To use this feature, a remote file system for temporary storage is required. Ensure to read and understand this feature's limitations, as it disables runtime while syncing

Maintenance Plan for DataPower Backup and Appliance Configuration - see limitations

DPOD now provides a multitude of backup capabilities:

• Backup a group of devices/domains. Wildcard patterns supported.

• Domain or device export or secure backup

• Ability to quiesce the domain or device before execution

• A script may be executed as part of the backup lifecycle - before running, on completion and before/after each single backup

 To use this feature, a remote file system for temporary storage is required. Ensure to read and understand this feature's limitations, as it disables runtime while performing the backup

Side Call Analysis - firmware 7.6+

• DPOD now provides latency analysis for calls performed within a transaction using protocols such as HTTP, MQ, LDAP, ODBC.

• DPOD now provides details of the order of execution for these side calls.

 To activate Side Call Analysis on DPOD run re-configuration of all your log targets in the DataPower that runs the API-C domain.

External APM Integration () - firmware 7.6+

• DPOD now provides the ability to push transaction aggregated data as one JSON record to external APMs (such as Tivoli APM) or log aggregators (such as Splunk).

 To activate this feature, a series of manual configuration steps will need to be performed, and a system shutdown will be required.

Service API Dashboard

• DPOD now provides a new dashboard that shows statistics pertaining to a service URL, such number of invocations and min/max/avg latency.

Introducing DPOD environment

• A monitored device may now be attached to several DPOD installations.

• Naming each DPOD installation and reflection of this.

• Node naming and configuration editing from the UI.
   During installation / upgrade you will need to set the system variables.

Feature Improvements

• New alert for transaction errors

• New report: export basic monitored device service configuration

• Improved High Availability Scenarios 

  • A limited Active / Active scenario is now supported if the same monitored device is connected to two separate and independent DPOD installations

  • New REST APIs introduced, to support Active / Standby scenario

• New filter to search logs by B2B message id or B2B partner id

• Improved error Analysis by providing simple human readable errors that are most common in:

  • SSL scenarios within a transaction
  • Side calls scenarios within a transaction (when the Side Call feature is enabled)
  • API Connect scenarios within a transaction (when the API-C feature is enabled)

Deprecated features in future versions

• The Extended Transaction feature is expected to be deprecated for customers using firmware above 7.6. This feature will be replaced using a Non-Intrusive technique in upcoming releases.