Skip to content

Deployment_of_the_Modules_Detailed

Jump to bottom
Nikos Kefalakis edited this page Mar 16, 2015 · 1 revision

##6) Running X-GSN:

  • Navigate to /openiot/modules/x-gsn/and run the command: mvn clean package

  • A folder named target will be created under this directory. This folder contains a file called: xgsn-1.1.4.jar

  • Run the script:

For Linux: ./gsn-start.sh

  • If you want to stop X-GSN for any reason, run the following script:

For Linux: ./gsn-stop.sh

Notice: the first two steps are done only for the first time to deploy the platform.

##7) Deployment of the Modules (only for the first time to deploy the platform):

Notice: OpenIoT modules depend on each other, so it is recommended that you follow the below order while deploying the full platform.

###utils.commons:

  • Navigate to /openiot-0.6.1/utils/utils.commons and run the command: mvn install

  • A folder named target will be created under this directory. This folder contains a file called: utils.commons.jar

  • Navigate to /openiot-0.6.1/utils/utils.commons/src/main/resources

  • Copy the file security-config.ini to the location: JBOSS_HOME/standalone/configuration

cp security-config.ini JBOSS_HOME/standalone/configuration

  • Navigate to /openiot-0.6.1/utils/utils.commons/src/main/resources/properties

  • Copy the file openiot.properties to the location: JBOSS_HOME/standalone/configuration

cp openiot.properties JBOSS_HOME/standalone/configuration

###Security Client:

  • Navigate to /openiot-0.6.1/modules/security/security-client and run the command: mvn install

  • A folder named target will be created under this directory. This folder contains a file called: security.client-0.0.1-SNAPSHOT.jar

###Lsm-light Client:

  • Navigate to /openiot-0.6.1/modules/lsm-light/lsm-light.client and run the command: mvn install

  • A folder named target will be created under this directory. This folder contains a file called: lsm-light.client-0.0.1.jar

###Ui.requestCommons:

  • Navigate to /openiot-0.6.1/ui/ui.requestCommons and type the command: mvn install

  • A folder named target will be created under this directory. This folder contains a file called: ui.requestCommons.jar

###Lsm-light Server:

  • Navigate to /openiot-0.6.1/modules/lsm-light/lsm-light.server and run the command: mvn clean package jboss:deploy

  • A folder named target will be created under this directory. This folder contains a file called: lsm-light.server.war

  • Copy this file to the location: JBOSS_HOME/standalone/deployments

cp lsm-light.server.war JBOSS_HOME/standalone/deployments

Notice: if jboss:deploy doesn’t work, replace it with jboss-as:deploy

###Security Management and Server:

  • Navigate to /openiot-0.6.1/modules/security/security-management and run the command: mvn clean package jboss:deploy

  • A folder named target will be created under this directory. This folder contains a file called: security.management.war

  • Copy this file to the location: JBOSS_HOME/standalone/deployments:

cp security.management.war JBOSS_HOME/standalone/deployments

Notice: if jboss:deploy doesn’t work, replace it with jboss-as:deploy

####Adding a New User and Some Modifications:

  • Sign up for a new user: eg: openiot/openiot
  • Log-out (make sure you are logged out from the application and from CAS log-out at the end of the page) and close the browser
  • Log-in again with: admin/secret
  • Go to Manage Services and edit the schemaEditor

[](Documentation/images/manual-installation-guide/Security_Management_1.png) * Change the URL to be: * Change the Secret to be: schemaEditor-secret and press Submit * Go to Manage Users and click on the user you have created

[](Documentation/images/manual-installation-guide/Security_Management_2.png) * Click on Select Service and add roles to each of the following: LSM usage role Schema editor usage role Scheduler usage role Sdum usage role X-GSN usage role * The following link will help you understand what is a role and how to use the security management interface: * Log-out again (from both) and close the browser.

  • Navigate to /openiot-0.6.1/modules/security/security-server and run the command: mvn clean package jboss:deploy

  • A folder named target will be created under this directory. This folder contains a file called: openiot-cas.war

  • Copy this file to the location: JBOSS_HOME/standalone/deployments

cp openiot-cas.war JBOSS_HOME/standalone/deployments

  • To make sure that everything is working, go to link:
    https://localhost:8443/openiot-cas (or replace localhost with the name of your server if you are running JBoss from a remote server)

  • Log-in with the new user you have created before in security management.

Notice: if jboss:deploy doesn’t work, replace it with jboss-as:deploy

###Scheduler Core:

  • Navigate to /openiot-0.6.1/modules/scheduler/scheduler.core and run the command: mvn clean package jboss:deploy

  • A folder named target will be created under this directory. This folder contains a file called: scheduler.core.war

  • Copy this file to the location: JBOSS_HOME/standalone/deployments :

cp scheduler.core.war JBOSS_HOME/standalone/deployments

Notice: if jboss:deploy doesn’t work, replace it with jboss-as:deploy

###SDUM Core:

  • Navigate to /openiot-0.6.1/modules/sdum/sdum.core and run the command: mvn clean package jboss:deploy

  • A folder named target will be created under this directory. This folder contains a file called: sdum.core.war

  • Copy this file to the location: JBOSS_HOME/standalone/deployments:
    cp sdum.core.war JBOSS_HOME/standalone/deployments

  • To make sure that everything is working, go to link:
    http://localhost:8080/sdum.core/rest/services (or replace localhost with the name of your server if you are running JBoss from a remote server)

Notice: if jboss:deploy doesn’t work, replace it with jboss-as:deploy

Notice: Both SDUM and Scheduler provide clients to test the server functions. These are SWING java programs. Please execute them as any other java swing program if needed.

###ui.requestDefinition:

  • Navigate to /openiot-0.6.1/ui/ui.requestDefinition and run the command: mvn clean package jboss:deploy

  • A folder named target will be created under this directory. This folder contains a file called: ui.requestDefinition.war

  • Copy this file to the location: JBOSS_HOME/standalone/deployments:

cp ui.requestDefinition.war JBOSS_HOME/standalone/deployments

  • To make sure that everything is working, go to link:
    http://localhost:8080/ui.requestDefinition/ (or replace localhost with the name of your server if you are running JBoss from a remote server)

  • Log-in with the new user you have created before in security management

  • To know how to use this interface after pushing data into the platform (will be shown later), please follow this link:

https://github.com/OpenIotOrg/openiot/wiki/Request-definition-use

  • UI Overview

[](Documentation/images/request-definition/01-ui-overview.png)

Notice: if jboss:deploy doesn’t work, replace it with jboss-as:deploy

###ui.requestPresentation:

  • Navigate to /openiot-0.6.1/ui/ui.requestPresentation and run the command: mvn clean package jboss:deploy

  • A folder named target will be created under this directory. This folder contains a file called: ui.requestPresentation.war

  • Copy this file to the location: JBOSS_HOME/standalone/deployments

cp ui.requestPresentation.war JBOSS_HOME/standalone/deployments

  • To make sure that everything is working, go to link:
    http://localhost:8080/ui.requestPresentation/ (or replace localhost with the name of your server if you are running JBoss from a remote server)

  • Log-in with the new user you have created before in security management

  • To know how to use this interface after pushing data into the platform (will be shown later), please follow this link:

https://github.com/OpenIotOrg/openiot/wiki/Request-presentation-use

  • UI Overview

[](Documentation/images/manual-installation-guide/Request_Presentation.png)

Notice: if jboss:deploy doesn’t work, replace it with jboss-as:deploy

###ui.schemaeditor:

  • Navigate to /openiot-0.6.1/ui/ui.schemaeditor and run the command: mvn clean package jboss:deploy

  • A folder named target will be created under this directory. This folder contains a file called: ui.schemaeditor.war

  • Copy this file to the location: JBOSS_HOME/standalone/deployments

cp ui.schemaeditor.war JBOSS_HOME/standalone/deployments

  • To make sure that everything is working, go to link:
    http://localhost:8080/ui.schemaeditor (or replace localhost with the name of your server if you are running JBoss from a remote server)

  • Log-in with the new user you have created before in security management

  • Details on how to use this interface are given later in this document.

Notice: if jboss:deploy doesn’t work, replace it with jboss-as:deploy

###Ide Core:

  • Navigate to /openiot-0.6.1/ui/ide/ide.core and run the command: mvn clean package jboss:deploy

  • A folder named target will be created under this directory. This folder contains a file called: ide.core.war

  • Copy this file to the location: JBOSS_HOME/standalone/deployments

cp ide.core.war JBOSS_HOME/standalone/deployments

  • To make sure that everything is working, go to link:
    http://localhost:8080/ide.core/ (or replace localhost with the name of your server if you are running JBoss from a remote server)

Notice: if jboss:deploy doesn’t work, replace it with jboss-as:deploy

####For better understanding of the platform, please read the documentation found here: https://github.com/OpenIotOrg/openiot/wiki/Documentation

https://github.com/OpenIotOrg/openiot/wiki/Developer-Setup-Instructions-Eclipse---OpenIoT-v0.6.1

footer

Main

Learn

Users

Developers

Community

##Roadmap

Other

Clone this wiki locally