There is some outdated documentation at our wiki page: https://wiki.opendaylight.org/view/IoTDM:Main
Some general information can be found in developer guide for IoTDM, see IoTDM Developer Guide.
There is more actual developers documentation as README files in IoTDM’s sources.
Since this project implements OneM2M specifications including protocol bindings it is also opening multiple ports for plugins providing mapping between protocol specific representation of data to the common format used by onem2m-core. Port numbers opened by IoTDM depends on configuration of these plugins and also depends on number of instances of the plugins.
There are some default server port numbers pre-configured for OneM2M related plugins, e.g.: HTTP: 8282(TCP), CoAP: 5683(UDP), Websocket: 8888(TCP) which are enabled by default.
HTTPS and CoAPS communication can be used instead of unsecured versions but it must be configured properly. There are implemented also other experimental plugins opening ports by default: odl-onem2mexample:: 8283(TCP), dl-onem2medevice:: 8284(TCP) and 123(UDP)
The experimental features odl-iotdmbundleloader and odl-iotdmkaraffeatureloader are insecure in this version since there are not implemented any security mechanisms yet.
There are several low priority issues opened in IoTDM’s Bugzilla. Here are some major issues: 7990 - Race condition after resource delete - https://bugs.opendaylight.org/show_bug.cgi?id=7990 4316 - “mni” and “mbs” does not work stable - https://bugs.opendaylight.org/show_bug.cgi?id=4316
Subset of functionality described in OneM2M specifications: http://onem2m.org/technical/published-documents