SD&UM Develop

System requirements

All you need to build this project is Java 7.0 (Java SDK 1.7) or later, Maven 3.0 or later and LSM-Light client library installed to your local maven repository. The application this project produces is designed to be run on JBoss Enterprise Application Platform 6 or JBoss AS 7.1.

To install LSM-Light client library go to OpenIoT GitHub under utils/lib/lsmApiLibraryMavenInstall and download “lsmlibs.jar”. Go to the folder you downloaded the jar file thru the command line and execute the following maven command:

mvn install:install-file -Dfile=lsmlibs.jar -DgroupId=org.openiot -DartifactId=lsm.api -Dversion=0.0.1 -Dpackaging=jar

Download

To download SDUM’s source code use your favorite git client and retrieve the code from one of the following URLs:

• HTTPS: https://github.com/OpenIotOrg/openiot.git
• SSH: [email protected]:OpenIotOrg/openiot.git The scheduler is available under the openiot/modules/sdum/ folder.

Deploy from the source code

If you have not yet done so, you must Configure Maven before testing the scheduler deployment. After that:

Start the JBoss

Start the JBoss Enterprise Application Platform 6 or JBoss AS 7.1 with the Web Profile

1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
   • For Linux: JBOSS_HOME/bin/standalone.sh
   • For Windows: JBOSS_HOME\bin\standalone.bat

Build and Deploy the Scheduler

NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line.

1. Make sure you have started the JBoss Server as described above.

2. Open a command line and navigate to the root directory of the scheduler Project.

3. Type this command to build and deploy the archive: mvn clean package jboss-as:deploy

4. This will deploy target/scheduler.core.war to the running instance of the server.

Properties Set-Up/Configuration

The SD&UM uses the global properties file. Directions on how to use and configure can be found here

Access the application

The application will be running at the following URL: http://localhost:8080/sdum.core/.

Undeploy the Archive

1. Make sure you have started the JBoss Server as described above.

2. Open a command line and navigate to the root directory of the scheduler Project.

3. When you are finished testing, type this command to undeploy the archive: mvn jboss-as:undeploy

Run in Eclipse

Integrating and Starting JBoss server

You can start JBoss Application Server and deploy the Scheduler from Eclipse using JBoss tools. Detailed instructions on how to integrate and start JBoss AS from Eclipse with JBoss Tools are available here .

Integrating and deploying SD&UM

To integrate and deploy the SD&UM in Eclipse one should follow the steps below:

1. Import Existing maven project File>Import>Maven>Existing Maven Projects

2. Click the “Browse” button and navigate to the SD&UM’s source code directory that has been previously downloaded.

3. Choose the sdum.core and click the Finish button.

4. Right click on the sdum.core project and choose Run As>Maven Build…

5. Insert the following to:

• Goals: clean package jboss-as:deploy
• Profiles: arq-jbossas-remote
• Name: sdum.core package-deploy (or your preferred name)

Click the Run button (the JBoss Server should be already running). The project will automatically build itself, get deployed and run at the JBoss AS running instance. From now on this configuration should be available at the Eclipse Run Configurations under Maven Build.

To Undeploy the scheduler from the running instance of the JBoss AS follow the steps below:

1. Right click on the “sdum.core” project and choose Run As>Maven Build…

2. Insert the following to:

• Goals: jboss-as:undeploy
• Profiles: arq-jbossas-remote
• Name: sdum.core undeploy (or your preferred name)

Click the Run button (the JBoss Server should be already running). The project will automatically be undeployed from the JBoss AS running instance. From now on this configuration should be available at the Eclipse Run Configurations under Maven Build.