Page Comparison

The local WSDL promotion replace the current service WSDL and XSDs with new files supplied by the user.

...

After clicking "Execute" the next message will appear

DPOD's internal process will monitor and collect 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 sevice
3. DPOD will download all the WSDL/Schema files of the current service
4. DPOD will execute a second custom user script that will analyze the new WSDL/Schema files and will replace all the references in the files so they will point to the correct DataPower paths
5. DPOD will upload the new altered WSDL/Schema files to the temporary domain and will create a new service that uses this WSDL
6. The new temporary service will be created without any front side handlers, so it will not be accessible.
7. After creating the temporary service, DPOD will check the its 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 message about the WSDL/Schema 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. Run DPOD automatically runs the validation flow - and will continue to step 2 only if the validation was successful
2. Upload the altered files from the validation steps to the DataPower, create directories if needed
   Existing files with the same names may be overriden.
3. Export the original service
4. Change the WSDL address in the export
5. Import the origin service again.
6. Check the WSDL status and the service operational state
7. If the service is not up or the WSDL status is not okay - try to rollback the operation by uploading the original WSDL/Schema files to local store and importing the service again with the original unchanged WSDL address

...