Global Scheduler Use

System requirements

All you need to run this project is Java 7.0 (Java SDK 1.7) or later and JBoss Enterprise Application Platform 6 or JBoss AS 7.1.

Deployment/Undeployment

JBoss AS 6.0

Deploy: To deploy the scheduler on JBoss AS 6.0, copy the scheduler.core.war to the server's deploy directory.

Undeploy: Remove the app war scheduler.core.war from the JBoss deploy directory while the server is running.

JBoss AS 7.0

Deploy: To deploy the scheduler on JBoss AS 7.0, copy the scheduler.core.war to the server's standalone/deployments directory.

Undeploy: To undeploy the application, you need to remove the .deployed marker file that is generated upon successful deployment of the scheduler module.

You can find more detailed directions on the ins and outs of deployment on JBoss AS7 here.

Properties Set-Up/Configuration

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

Manual

This module is expected to be used from the OpenIoT Request Definition user interface. Instructions on how to install and use this interface can be found in Request-Definition. In case you would like to use a third party application use the restful web services from the URLs listed below (the inputs and the outputs of these services are defined in API Specifications Table here):

• Welcome Message listing the available services:
  • http://localhost:8080/scheduler.core/rest/services
• Discover Sensors :
  • http://localhost:8080/scheduler.core/rest/services/discoverSensors
• Registering a new service:
  • http://localhost:8080/scheduler.core/rest/services/registerService
• Unregister Service :
  • http://localhost:8080/scheduler.core/rest/services/unregisterApp
• Update Service:
  • http://localhost:8080/scheduler.core/rest/services/updateApp
• Get Application:
  • http://localhost:8080/scheduler.core/rest/services/getApplication
• Get Service:
  • http://localhost:8080/scheduler.core/rest/services/getService
• Get User:
  • http://localhost:8080/scheduler.core/rest/services/getUser
• Get Available Application IDs:
  • http://localhost:8080/scheduler.core/rest/services/getAvailableAppIDs
• Get Available Service IDs :
  • http://localhost:8080/scheduler.core/rest/services/getAvailableServiceIDs
• Get Available Applications :
  • http://localhost:8080/scheduler.core/rest/services/getAvailableApps

Security Configuration

Service

For using the scheduler, a REST service must be created. When the OpenIoT graph is initialized, a REST service is created for the scheduler with the following key and secret as defined in the openiot.properties:

• security.initialize.scheduler.key=scheduler
• security.initialize.scheduler.secret=scheduler.secret

The key and secret of the service must correspond to the key and secret specified in the global security-config.ini file in the configuration section devoted to the scheduler.

Permissions

Users need to have the permission "*" to access various functionality of the scheduler. The permission "*" is created upon initialization of the OpenIoT graph for the scheduler service.

Roles

The role "AllPermRole" is created upon initialization of the OpenIoT graph for the scheduler service. The permission "*" is assigned to this role.