For many projects it might be desirable to use Apache Maven to update DataPower configuration or to upload files to a device.
This has several benefits:
* Maven is a de-facto standard tool for building Java EE applications, so using the same tool to perform DataPower management tasks is convenient.
* Integration with the Maven lifecycle and phases (e.g., running integration tests after uploading an XSLT file to the device).
* Usage of Maven profiles so that DataPower connection properties could be defined as part of a profile.
This can be accomplished by invoking dpbuddy’s Ant tasks using Maven’s AntRun plugin.
Following is the example:
org.apache.maven.plugins
maven-antrun-plugin
1.7
Note how you can define a prefix for custom dpbuddy tasks as part of the “target”.
You should be using Maven instead of Ant for managing properties, so “dpbuddy.home” and “resourcesDir” can be defined in the POM itself (or you can use properties plugin if you want storing properties in a separate file) :
${project.build.sourceDirectory}/../resources
/home/dpbuddy
You can use Maven profiles to define DataPower connection properties:
dev
user
EXAMPLE ONLY
dev
https://10.0.0.1
To execute our dpbuddy tasks simply run
mvn antrun:run -P dev
Note that we did not attach our configuration to any Maven phase; you can do it by defining the target as part of the plugin’s “execution” element, there are numerous examples in the plugin’s documentation.
