# import¶

import is the main task for updating DataPower configuration. It imports previously exported configuration and files into a DataPower domain. The input for import can be created using WebGUI or DPBuddy’s export task. The functionality supported by import is similar to “Import Configuration” available from WebGUI. import can handle a stand-alone XML configuration file or a zip file containing both configuration and files to be uploaded to the DataPower file system.

Upon completion, import prints a report with the list of all updated configuration objects and files.

buddyImport is the alias of “import”. Eclipse Ant editor gives warning when dp:import is used as it confuses it with the Ant’s built-in import task. dp:buddyImport can be used to avoid this.

import allows for specifying Ant/Groovy/Gradle variables in any text node or an attribute of the deployment policy file. Any XML file used in transformation can also utilize references to Ant/Groovy/Gradle variables.

import supports transformation actions described in Using DPBuddy to Transform DataPower Configuration and XML Files. Transformations can be applied to XML import files or to the files inside a ZIP archive.

In certain cases DataPower automatically creates “GeneratedPolicy” objects with generated names. Generated policies may cause import to fail. If this is the case, you need to delete generated policies from the export file by adding the following directive to the transform:

<dpExclude class="GeneratedPolicy" />


## Attributes/Options¶

Attribute Description Required
file File to import. This could be a zip or an xml/xcfg file. Yes
overwriteFiles

If set to true, overwrite existing files with the files included with the import.

Defaults to true for zip files and to false for xml/xcfg configuration files.

No
overwriteObjects

If set to true, overwrite existing objects with the objects defined as part of this import.

Defaults to true (DataPower default).

No
rewriteLocalIp

If set to true, the local address bindings of services contained in the import package will be rewritten to match the equivalent interfaces of the device.

Defaults to false (DataPower default).

No
dryRun

If set to true, run import in “dry run” mode.

Defaults to false (DataPower default).

No
resolveVars

If set to true, attempt to resolve variables (${}) inside the export file. DPBuddy will raise an exception if any variables/properties remain unresolved. This setting is equivalent to defining an empty transform nested element. Defaults to false. No transformDefs File to load transform definitions from. Definitions are specified in XML (Apache Ant) format described in Using DPBuddy to Transform DataPower Configuration and XML Files. The file could contain multiple “transform” elements, each with its own “id” attribute. No transformId ID of the transform definition (transform XML element) in the transform definitions file. No applyUpdatesTo List of DataPower configuration class names and object names to update in HOCON format, e.g., ‘XMLFirewallService: fw1, WSGateway: proxy2’. The actual updates (what element to update and the values) are defined by the “updates” option. No updates Updates to apply to elements of the objects specified by ‘applyUpdatesTo’. HOCON format is used to specify element names and values, e.g., ‘LocalPort:8090, RemoteEndpointHostname: myHost’. This means that the “LocalPort” element of all objects matched by “applyUpdatesTo” will be set to “8090”. No transformOnly If set to true, DPBuddy will transform the files according to the nested transform element or the transformDefs option but it will not execute the import itself. In this mode, the task does not connect to DataPower. This is convenient for developing/troubleshooting transform actions. Defaults to false. No workDir Path to the directory used to hold temporary files. DPBuddy will unzip the content of the zip file into this directory. This is needed when transform/transformDefs is used to transform configuration files contained inside a zip file. Note that DPBuddy cleans this directory every time the import task is executed. If transform/transformDefs is not used or when the imported file is XML, workDir is ignored. Defaults to ${java.io.tmpdir}/dpbuddy/import. java.io.tmpdir is a Java system property. It usually defaults to /tmp on Unix and \Users\<user name>\AppData\Local\Temp on Windows.

No


## transformFiles Nested Element¶

transformFiles defines what files to transform by the transformation actions contained in the nested transform element. transformFiles can only be used if the imported file is “zip”. For XML import file transformation actions will be applied to the file referenced in the file attribute of the task.

transformFiles inherits all the attributes and elements of the Ant patternset. You have to define your include/exclude patterns in such a way that only XML files will be selected by the patternset. DPBuddy will attempt to apply all transformation actions to all matched files.

Usually, transformations are applied to the DataPower configuration file typically named “export.xml” in the zip file. In this case, you just need to specify “export.xml” in the includes of the transformFiles:

<transformFiles includes="export.xml">


transformFiles has to contain at least one transform element, as explained earlier in this document.

If transformFiles is omitted and the imported file is “zip”, transformation actions will be applied to “export.xml” inside the zip file. If “export.xml” does not exist, an error will be thrown.

You can specify multiple transformFiles, thus applying different transformation actions to different files.

## transform Nested Element¶

transform contains the transformation actions documented in the section Using DPBuddy to Transform XML Files Using DPBuddy to Transform DataPower Configuration and XML Files.