The following conventions are used in this document:

 - Some action is required to enable the feature.

 - This is a Tech Preview Feature. Consult the release notes for more information.

New Features

The following are features added to DPOD in the current release

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.