Versions Compared

Old Version 51

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Hanan Kenan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

(red star) - Some actions are required to enable the feature.
(thumbs up) - 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

Maintenance Plans Improvements

Improved User Experience

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.
      • The Promote action updates allows uploading a new URL of a remote WSDL in a WSDL and schema files to the target location (Device device and Domaindomain) , and creates creating a newer 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 PERL Python scripts. Example scripts are open source and may be obtained from a git repository - see docs docs (red star)

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+)

...

  • 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.

...

  • 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.

(red star) 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 ((thumbs up)) - see limitations

DPOD now provides a multitude of syncing capabilities:

...

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

...