Provides information about adjusting device management settings in RM.
The backend modules related to OSGi device management own configurations in the OSGi Configuration Admin that allow you to adjust device management settings in your RM system. You can view and manage backend configurations through the console user iterface, or programmatically using the Configuration Admin API.
For more information please refer to: System Configuration

OSGi Device Management Configuration

This configuration has a PID: mprm.ms.gm. It is provided by the OSGi Device Manager (packages/osgidm/osgidm.core.manager.be.ms.jar) bundle. It contains the following properties:

Property ID

User-Friendly Name

Type

Default Value

Description

gm.net.port.ssltcp

SSL TCP Port

int

2443

Local port used for secure SSL TCP communication with the OSGi devices.

gm.net.port.udp

Plain UDP Port

int

1501

Local port used for non-secure UDP communication with the OSGi devices.

gm.net.port.secure:udp

Secure UDP Port

int

1503

Local port used for secure UDP communication with the OSGi devices.

gm.net.port.tcp

Plain TCP Port

int

1501

Local port used for non-secure TCP communication with the OSGi devices.

gm.net.port.secure:tcp

Secure TCP Port

int

1503

Required. Local port used for secure TCP communication with devices.

gm.net.port.ws

WebSocket Port

int

1505

Local port used for WebSocket communication with the OSGi devices.

gm.transports

Supported Network Transports

array

ssltcp udp http https tcp secure:udp secure:http secure:tcp ws

Contains the list of network transport over which the OSGi devices can communicate with the Management Server(s).

gm.allow.gw.register

Allow Device Autoregistration

boolean

true

Specifies whether non registered OSGi devices will be accepted and will be registered automatically in the RM.

gw.net.client.authentication

Require secure device authentication

boolean

false

Specifies whether the secure connection will require certificate-based authentication of the OSGi devices.

gm.cluster.external_distribution

External Load Distribution

boolean

false

Setting this property to true disables the RM provided distribution of the devices between the RM hosts in the cluster. This is in case an external load balancer is used.

OSGi Devices Management Performance Options

This configuration has a PID: gm.performance.pid. It is provided by the OSGi Device Manager (packages/osgidm/osgidm.core.manager.be.ms.jar) bundle. It contains the following properties:

Property ID

User-Friendly Name

Type

Default Value

Description

gateways.max.online

Max Online Devices per Backend Host

int

10000

Maximum number of devices which could be simultaneously connected to a single backend host included in a management server.

gateways.cache.size

OSGi Devices Cache Size

int

2000

Maximum number of OSGi Device data records, which will be cached in memory.

bundle.cache.size

OSGi Bundles Cache Size

int

100

Maximum number of devices, which bundles will be hold in memory.

sys.props.sets.cache.size

System Property Tables Cache Size

int

100

Maximum number of system property tables of the managed devices hold in memory.

single.sys.props.cache.size

Single System Properties Cache Size

int

1000

Maximum number of single key-name pairs of OSGi device system properties hold in the memory.

permissions.list.size

Bundle Permission Set Cache Size

int

100

Maximum number of full bundle permissions set hold in memory.

single.permissions.size

Single Bundle Permissions Cache Size

int

200

Maximum number of single bundle permissions hold in memory.

configurations.size

Bundle Configurations Cache Size

int

300

Maximum number of bundle configuration dictionaries hold in memory.

services.size

Bundle Services Cache Size

int

100

Maximum number of service registration dictionaries hold in memory.

registration.props.size

Registration Properties Cache Size

int

150

Maximum number of OSGi Device registration propery tables hold in the memory.

Provisioning Service Configuration

This configuration has a PID: prm.prvsrv.pid. It is provided by the Provisioning Provisioning RAS (packages/osgidm/osgidm.provisioning.ms.jar). It contains the following properties:

Property ID

User-Friendly Name

Type

Default Value

Description

prm.prv.secure

Security Mode

boolean

false

Defines if the backend provisioning service has to run in secure mode.

prm.prv.try2http

Try Secondary Http Port

boolean

true

Defines if the registration of the device on port 80 fails with a java.io.FileNotFound exception, it will try to register it on port 8080.

prm.prv.natsupport

NAT Support

boolean

true

Defines if the management server should be resolved via a device network added to the RM networks.

prm.prv.securedownload

HTTPS Download Mode

boolean

false

Defines if provisioning should be done over HTTPS and if download of bundles from the inventory's Http Accessible Bundle Group should performed over HTTPS.

prm.prv.securelog

Secure Remote Logging

boolean

true

If the provisioning backend service should send 'https' remote log URLs to provisioned clients.

prm.prv.log.url

External Remote Log URL

string


External remote log URL to send to provisioned clients. If not set, internally supported remote log URL is sent.

prm.discoverer.timeout

Default Discovery Timeout

int

5000

Default timeout (in ms) for device discovery requests.

Periodical Connection Manager Configuration

This configuration has a PID: prm.connman.pid. It is provided by the OSGi Device Connection Manager bundle (packages/osgidm/osgidm.core.connection.manager.be.ms.jar). It contains the following properties:

Property ID

User-Friendly Name

Type

Default Value

Description

enabled

Enabled

boolean

false

Specifies whether the Connection Management is enabled.

checkPeriod

Check Period

int

60

Check period, in seconds for closing inactive connections and if configured, alerting for exceeded offline times. The value can vary from 1 to 65535.

checkOffline

Check Exceeded Offline Times

boolean

true

Check and raise alerts for Connectors that have exceeded their allowed offline time.