Before you can use certain features of the DevOps portal, you will need the following setup/configuration:

Remote or Local WSDL Validation/Promotion

1. If you wish to use Remote or Local WSDL validation or promotion - create a temporary domain(s) for DPOD operations
   DPOD will create temporary services on this domain in order to validate the service WSDL and may upload files to the local filesystem.
   a. Per-device temporary domain:
   From Monitored Devices→monitored device→Settings Tab, choose a temporary domain 
   The temporary domain needs to be accessible to this device, you may choose the same temporary domain for multiple devices

   b. Default temporary domain for all devices that don't have per-device setup
   Enter the temporary domain's device name in DPOD's system parameter (see "DevOps Portal Parameters" section under system parameters)
   Enter the temporary domain's name in DPOD's system parameter (see "DevOps Portal Parameters" section under system parameters)

   It is the Gateway admin's responsibility to clear the temporary domain's content and/or services.
   DPOD does not clear the domain's content.
   Once DPOD finished validating or promoting a service, the temporary service and its files are no longer required and can be safely deleted.

   For remote WSDL validation or promotion - the temporary domain should have access to the remote WSDL address.
   Read Remote WSDL Validation and Promotion to learn more about how the remote WSDL validation is performed

2. If you wish to use Local WSDL validation or promotion you will need to use two custom Python scripts,
   a. a script to analyze the WSDL/XSD files
   b. a script to replace references in the WSDL/XSD files.
   see DevOps Services Portal's User Scripts for more information about the script specifications.
   Once you uploaded the scripts to DPOD, you will need to setup their path and names in DPOD's system parameters so DPOD can use them (see "DevOps Portal Parameters" section under system parameters)
   c. You can limit the maximum WSDL and XSD file sizes that users are allowed to upload (see "DevOps Portal Parameters" section under system parameters)
3. After setting up the monitored devices, you can setup DNS translations for the DevOps services list page

Import Service

1. You can set whether a deployment policy is mandatory for imports - see "Deployment Policy is Mandatory for Import Service" in system parameters for more info (refresh your browser page after changing the system parameter value)
2. The users will be promoted to select a deployment policy from a list of deployment policies that were pre-loaded to a specific folder in DPOD's
   Set the folder from the "Import Service Deployment Policies Path" parameter in  system parameters and upload files to the DPOD server using any file-transfer program (refresh your browser page after changing the system parameter value)
3. You can set a size limit to the uploaded import files, the default value is 10MB, see "Import Service Max Upload File Size in KB" in system parameters for more info
4. The Import service process includes two custom user scripts,
    The first script gets the user deployment policy's selection, and can override or change it.
   The second script performs validations on the export file, before the import begins.
   The location of the scripts is set in system parameters, default scripts and setup is supplied, you may replace or edit the initial scripts. 
   see DevOps Services Portal's User Scripts for more information about the script specifications.