IBM DataPower Operations Dashboard v1.0.14.0

A newer version of this product documentation is available.

You are viewing an older version. View latest at IBM DPOD Documentation.

Local WSDL Validation and Promotion

Owned by Assaf Cohen (Deactivated)
Last updated: Aug 21, 2018 by Hanan Kenan

The local WSDL promotion replaces the current service WSDL and XSD with new files supplied by the user.


In some cases, depending on the WSDL contents, the old WSEndpointRewritePolicy that is attached to the WS-Proxy can not be used with the new WSDL.
In those cases, the Front-Side Handlers may need to be re-added manually to the WS-Proxy after the WSDL promotion is done.


Initiating a New Validate or Promote Local WSDL Request

Choose either Validate Local WSDL or Promote Local  WSDL from the DevOps Services List to initiate the process

Changing a service with Local WSDL to a remote WSDL or vice versa is not supported


DPOD only supports WSDL/XSD files that are located in the local:/// directory
DPOD does not support files in other locations such as the store:/// or temp:/// directories


  1. Choose one WSDL file
  2. Choose zero or more XSD files (note that you can select multiple files at once from the XSD file browser).
  3. Click "Upload" - this will upload your new files to DPOD (not to the DataPower!)
  4. If the upload was successful, click on "Execute" to request a new WSDL validation/promotion

After clicking "Execute" the following message appears

DPOD's internal process will monitor and start executing pending requests every one minute.

Validation Flow

  1. DPOD will use a temporary domain on a monitored device that was chosen and created by the admin.
  2. First DPOD will execute a custom user script that will analyze the current service's WSDL and will return all the schema files used by the service
  3. DPOD will download all the WSDL/XSD files of the current service
  4. DPOD will execute a second custom user script to analyze the new WSDL/XSD files and replace all the references in the files so they point to the correct DataPower paths
  5. DPOD will upload the new altered WSDL/XSD files to the temporary domain and create a new service that uses this WSDL
  6. The new temporary service will be created without any front side handlers.
  7. After creating the temporary service, DPOD checks the DataPower's WSDL compilation status.
Messages from the validation steps may return DataPower errors or messages about service with a random name such as DD0396FC-D428-40E8-B64C-913824FD16D4 - this is the name of the temporary service used by DPOD.
The same applies to messages about the WSDL/XSD validation, they will be uploaded to the temporary domain local storage in local:///temp-service-name/ (e.g. local:///DD0396FC-D428-40E8-B64C-913824FD16D4/)

Promotion Flow

  1. DPOD first runs the validation flow and will continue to step 2 only if the validation was successful
  2. DPOD uploads the altered files from the validation steps to the DataPower, and creates any directories if needed.
    Existing files with identical names may be overriden.
  3. DPOD exports the original service
  4. DPOD changes the WSDL address in the export
  5. DPOD imports the original service with the modified WSDL address.
  6. DPOD checks the WSDL status and the service operational state
  7. If the service is not up or the WSDL status is not ok - DPOD tries to rollback the operation by uploading the original WSDL/XSD files to local store and importing the service again with the original unchanged WSDL address


IBM DataPower Operations Dashboard (DPOD) v1.0.14.0