Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "OM2M/Configuration"

(Configure the Gateway SCL)
(Configure the Gateway SCL)
Line 56: Line 56:
 
| org.eclipse.om2m.guestRequestingEntity|| Default GSCL guest requesting entity. (username / password)|| guest/guest
 
| org.eclipse.om2m.guestRequestingEntity|| Default GSCL guest requesting entity. (username / password)|| guest/guest
 
|}
 
|}
 +
 
* The GSCL configuration file contains 4 additional parameters to specify the remote NSCL to which the GSCL will be authenticated.
 
* The GSCL configuration file contains 4 additional parameters to specify the remote NSCL to which the GSCL will be authenticated.
 
{{CTable}}
 
{{CTable}}

Revision as of 10:49, 18 April 2014

Configure the Network SCL

  • Go to the “om2m/nscl” directory.
  • Edit the file “configuration/config.ini” to configure the NSCL. You can keep the current configuration for a local demo.
Parameter Description Example
org.eclipse.om2m.sclType SCL type NSCL
org.eclipse.om2m.sclBaseAddress NSCL ip address 127.0.0.1
org.eclipse.equinox.http.jetty.http.port NSCL listening port 8080
org.eclipse.om2m.sclBaseContext NSCL listening context /om2m
org.eclipse.om2m.dbFile NSCL Embedded database file name nscl.db4o
org.eclipse.om2m.sclBaseId Network SclBase resource id nscl
org.eclipse.om2m.reset Reset NSCL database after each restart true
org.eclipse.om2m.sclBaseProtocol.default NSCL default communication protocol http
org.eclipse.om2m.maxNrOfInstances Maximum number of instances stored in a ContentInstances resource 10
org.eclipse.om2m.adminRequestingEntity Default NSCL admin requesting entity. (username / password) admin/admin
org.eclipse.om2m.guestRequestingEntity Default NSCL guest requesting entity. (username / password) guest/guest

Configure the Gateway SCL

  • Go to the “om2m/gscl” directory.
  • Edit the file “configuration/config.ini” to configure the GSCL. You can keep the current configuration for a local demo.
Parameter Description Example
org.eclipse.om2m.sclType SCL type GSCL
org.eclipse.om2m.sclBaseAddress GSCL ip address 127.0.0.1
org.eclipse.equinox.http.jetty.http.port GSCL listening port 8181
org.eclipse.om2m.sclBaseContext GSCL listening context /om2m
org.eclipse.om2m.dbFile GSCL Embedded database file name gscl.db4o
org.eclipse.om2m.sclBaseId Gateway SclBase resource id gscl
org.eclipse.om2m.reset Reset GSCL database after each restart true
org.eclipse.om2m.sclBaseProtocol.default GSCL default communication protocol http
org.eclipse.om2m.maxNrOfInstances Maximum number of instances stored in a ContentInstances resource 10
org.eclipse.om2m.adminRequestingEntity Default GSCL admin requesting entity. (username / password) admin/admin
org.eclipse.om2m.guestRequestingEntity Default GSCL guest requesting entity. (username / password) guest/guest
  • The GSCL configuration file contains 4 additional parameters to specify the remote NSCL to which the GSCL will be authenticated.
Parameter Description Example
org.eclipse.om2m.remoteNsclId Remote Network SCL Id nscl
org.eclipse.om2m.remoteNsclAddress Remote Network SCL ip address 127.0.0.1
org.eclipse.om2m.remoteNsclPort Remote Network SCL listening port 8080
org.eclipse.om2m.remoteNsclContext Remote Network SCL listening context /om2m
  • You can configure GSCL and NSCL to work on the same machine for a local demo by setting different listening ports. You can configure them to work on distributed machines by setting their correct ip addresses. It is possible to configure multiple GSCLs by setting differing identifiers.

Back to the top