SDN Controller Programming Guide

110

pom.xml after updating the template with Table 2. A pom.xml for each application module must

be created under the module’s folder.

Sample Application Module POM File:

<?xml version="1.0" encoding="UTF-8"?>

<project xmlns="http://maven.apache.org/POM/4.0.0"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://maven.apache.org/POM/4.0.0

http://maven.apache.org/maven-v4_0_0.xsd">

<version>1.0.0-SNAPSHOT</version>

</parent>

<packaging>bundle</packaging>

<description>Health Monitor - API Bundle</description>

</dependencies>

</project>

Application Deployment Plan

Plans encapsulate the artifacts of an application as a single unit. Plans are XML files that have

a .plan file extension, such as multi-artifact.plan. The structure of the XML file is simple: the root

element is <plan> with attributes specifying the name of the plan, the version, atomicity, and

scoping. Then, for each artifact that makes up the application, a <artifact> element is added,

using its attributes to specify the type of artifact and its name and version. A template for the plan

can be found in the HP VAN SDN Controller SDK.

Under the application app folder (hm-app) create the application deployment plan using the

template from the HP VAN SDN Controller SDK. The following list shows the sample application

deployment plan (hm-app /hm.plan) after updating the template with the application modules.

Sample Application Deployment Plan:

<?xml version="1.0" encoding="UTF-8"?>

<plan name="Health Monitor" version="1.0.0" scoped="false" atomic="false"

xmlns="http://www.eclipse.org/virgo/schema/plan"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="

http://www.eclipse.org/virgo/schema/plan

http://www.eclipse.org/virgo/schema/plan/eclipse-virgo-

plan.xsd">