The following conventions are used in this document:

...

DPOD now provides a new self - service DevOps portal for traditional services.  This is a new portal dashboard where end-users can:

...

The Validate action will upload your new WSDL and schema files to a temporary location and validate its compilation and will create a temporary WS-Gateway to ensure the object is up.
The Promote action will upload your new WSDL and schema files to the target location (Device and Domain) - and create a newer version of your service.
Execute two new actions on SOAP Web service with remote WSDL : validate and promote
The Validate action will update a new URL of your remote WSDL, validate its compilation and create a temporary WS-Gateway to ensure the object is up.
The Promote action will update a new URL of your remote WSDL in a target location (Device and Domain) - and create a newer version of your service.
All actions require permission set by a security policy (custom roles)
Search & filter for services and see their key configurations

...

• Execute two new actions on SOAP Web Services service with local WSDL : validate and promote
  • The Validate action allows uploading a will upload your new WSDL and schema files to a temporary location , validating their and validate its compilation and creating will create a temporary WS-Gateway to ensure the object is up.
  • The Promote action
  allows uploading
  • will update a new
  WSDL and schema files to the
  • URL of your remote WSDL in a target location (
  device
  • Device and
  domain
  • Domain) - and
  creating
  • create a
  new
  • newer version of
  the
  • your service.
• Execute two new actions
on SOAP
• on SOAP Web
Services
• service with remote WSDL : validate and promote
  • The Validate action
allows updating the
• • will update a new URL of
the
• • your remote WSDL,
validating
• • validate its compilation and
creating
• • create a temporary WS-Gateway to ensure the object is up.
  • The Promote action
allows updating the
• • will update a new URL of
the
• • your remote WSDL in a target location (
device
• • Device and
domain
• • Domain) - and
creating
• • create a
new
• • newer version of
the
• • your service.
• All actions require permissions permission set by a security policy (custom roles).
• Each action Action can be extended/ customized using PERL scripts (example . Example scripts are open source and should be obtain by user from a git repo - see docs). docs 

Early Failing Requests dashboard

• A new dashboard has been added for early failing requests (such as SSL failures), showing requests that were received but were not able to reach the execution phase of a Processing Rule of a Service - requires IDG firmware 7.5.2.4+

...

• Users can now save favorite filters combinations for later use.

• A new free text search field was added to the transactions list 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-selection of values.
• Users can now change the size of the series (number of values) that is displayed in charts of type "top N".
• Add recent notifications panel that displays the recent UI notifications of the user (not persisted).
• Add a new "Share" button that allows sharing the current page (including filters, transaction ID etc.) by copying/pasting the current URL or by sending it via email
• Add more values to time range filters: last 10 minutes, start of day, start of week, this month.
• Provide consistent behavior across pages of drill-down into a transaction or use displayed value as a filter criteria.

...

• DPOD customers may require from time to time 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 since then load has increased and it is required to move to physical servers to handle the load.
  • Customer deployed DPOD Appliance mode but wants to migrate to Non-Appliance mode (based on RHEL) to better comply with organization's security requirements and standards.
• New procedure and tools were introduced for customers to migrate an existing DPOD Store data to a new DPOD installation for each of the scenarios above.

New Features 1.0.5

API Connect Integration

...