Package oracle.iot.client.device

API for directly–connected devices and gateway devices as clients of the Oracle IoT Cloud Service.

See: Description

Interface Summary

Interface	Description
VirtualDevice.ActionCallback	A callback interface for receiving notification of an Action.
VirtualDevice.Callable<T>	Deprecated This API does not support actions with multiple arguments.

Class Summary

Class	Description
Alert	An Alert to be sent to the server.
Data	Represents a set of custom data fields (key/value pairs) to be sent to the server.
DirectlyConnectedDevice	A directly-connected device is able to send messages to, and receive messages from, the IoT server.
GatewayDevice	A GatewayDevice is capable of registering indirectly–connected devices and proxies messages for indirectly–connected devices.
VirtualDevice	VirtualDevice for a device-client adds methods to handle write-only and executable actions.
VirtualDevice.ActionEvent	An event passed to the ActionCallback.

Package oracle.iot.client.device Description

API for directly–connected devices and gateway devices as clients of the Oracle IoT Cloud Service. A directly–connected device client is able to send messages to, and receive requests from, the server. A gateway device client is also able to register indirectly–connected devices with the server and to proxy messages to and from the server on behalf of the indirectly–connected devices.

A directly–connected device or a gateway device is first registered on the server with an activation identifier. This identifier is used by the client to activate the device (establish a secure connection between the device and the Oracle IoT Cloud Service). The device must be activated by the application before messages can be sent or received. The activate method will activate the registered device at which point the server will create an endpoint identifier for the device. The DirectlyConnectedDevice or GatewayDevice must be activated before it can be used to create a VirtualDevice or register indirectly–connected devices.

The activate method need only be called once. The method DirectlyConnectedDevice.isActivated() should be called before calling activate. If activate is called on a DirectlyConnectedDevice or GatewayDevice that is already activated, an IllegalStateException will be thrown.