SDN Controller Programming Guide

111
<artifact type="bundle" name="com.hp.hm.hm-model" version="1.0.0.SNAPSHOT
"/>
<artifact type="bundle" name="com.hp.hm.hm-api" version="1.0.0.SNAPSHOT
"/>
<artifact type="bundle" name="com.hp.hm.hm-dao.api"
version="1.0.0.SNAPSHOT "/>
<artifact type="bundle" name="com.hp.hm.hm-dao.model"
version="1.0.0.SNAPSHOT "/>
<artifact type="bundle" name="com.hp.hm.hm-dao" version="1.0.0.SNAPSHOT
"/>
<artifact type="bundle" name="com.hp.hm.hm-bl" version="1.0.0.SNAPSHOT
"/>
</plan>
Application Descriptor
The application descriptor defines META-data that allows the controller to validate the application
being installed.
Under the application app folder (hm-app) create the application descriptor using the template
from the HP VAN SDN Controller SDK. The following list shows the sample application descriptor
(hm-app /hm.descriptor) after updating the template with the application information.
Application Descriptor:
App_id=com.hp.hm
App_name=Health-Monitor
Version=1.0.0.SNAPSHOT
Support_team=false
Vendor= Hewlett-Packard
Description=Health Monitor SDN Application
Any value can be set to the App_id property as long as it is unique across installed applications.
In the same way any value can be set to the App_name property; however consider that this value
is the one that appears in the SDN controller’s Applications view. Version attribute must match the
application’s version configured in the POM files.
Support_team specifies whether the application is mandatory from the team point of view. This
attribute has implications on the way controllers handle a failure. If a mandatory application fails,
the controller declares itself as non-operational and the team will react upon such a failure. If this
attribute is set as false the application can still be part of a team, however the controller is still
operational in the event of a failure in the application.
Application Packaging POM File
The installable application is a simple .zip file containing the output .jar files generated at the
target directory - at compile time - of each application module (“…/health-monitor/hm-
api/target/hm-api-1.0.0.jar” for example), plus the application deployment plan file (“…/health-
monitor/hm-app/hm.plan”).
This application .zip file is automatically generated after building the application if the application
generator tool was used to create the application, see Application Generator (Automatic
Workspace Creation) on page 114. The application zip file can be found under the ~/ hm-
app/target.