Device to Cloud Command Line Interface Application Commands

--name <string>, -n <string>
The required --name option defines the unique identifier of the application object.
Valid characters for the application name are: digits (0-9), lower and upper case ascii characters (A-Z and a-z), special characters “-”, “_”.

--description <string>, -de <string>
An additonal description for the application.

--application-type <application-type>, --at <application-type>
With the option --application-type the type of the application can be defined. As default value webHook is used.
Following application types are currently supported

--urls <list-of-urls>, -us <list-of-urls>
With the --urls option you can define one or multiple application urls. In the normal case you only define a single url per application. But for special casses such as debugging multiple urls are supported.

You have the following possibilities to define the list of associated urls:

--connection-properties <json-object>, -cp <json-object>
With the option --connection-properties you can configure the connection of the application. It is a key/value map as json object. In the case of a webHook application thoses connection properties are the header fields which are attached to each HTTP POST request to forward the received device uplink messages to the application.

--connection-properties '{
    "Authorization":"cm9sYW5kLmJhbGRpbkB0ZWxla29tLmRlOlI5OXR0RCM/P3F0P0htJkE=",
    "iot-decoding-selector":"adeunis"
}'

--profile-file <file>, -p <file>
DMO access profile file which shall be used instead of the current activated on in the d2c configuration.

--origin <string>, -o <string>
Each request to the DMO API requires the HTTP header field X-M2M-ORIGIN. With the option –origin you can overwrite the default value of d2ccli. By convension oneM2M requires that the X-M2M-ORIGIN value is prefixed with a C character. This is done automatically by d2c, so please define the origin without the leading C.

--name <string>, -n <string>
In case you want to retriev the detail information of specific application you can use the option --name to identify the application.

--id <string>, -i <string>
In case you want to retriev the detail information of specific application you can use the option --id to identify the application.

--select <select fields>, -s <select fields>
A comma seperated list of element names which shall be selected from the returned objects and written to stdout as CSV or JSON format. To control if the output is written in CSV or JSON format use the –format option. To understand which fields are available to select you can run d2c get-applications without –select option to see which fields are part of the queried devices or you can read the documentation Key Concepts of Device to Cloud .

--format <CSV | JSON>, -f <CSV | JSON>
With the –format option you can control in which format the queried resource objects shall be written to stdout. If you don’t define any select fields with –select option the default format is JSON. If you define select fields with –select option the default format is CSV.

--separator-char <char>
If the –select option is used the selected elements are written to the stdout as CSV. With –separator-char you can control which character shall be used to seperate the different fields from each other in the output. By default ; is used as separator character.

--result-content-indicator <rci>, -rci <rci>
With the option –result-content-indicator you can control the amount of content which is returned as a result. The following indicators can be used:

--limit <int>, -li <int>
To controll the number of resource objects in the result you can use the option –limit. With the –limit option in combination with the –offset option, you can implement a pagination process to walk through large amounts of resource objects.

--offset <int>, -offset <int>
With the –offset option you can define the index or offset of the first object in the response. Normally you use the –offset option together with the –limit option to implement a pagination process.

--profile-file <file>, -p <file>
DMO access profile file which shall be used instead of the current activated on in the d2c configuration.

--origin <string>, -o <string>
Each request to the DMO API requires the HTTP header field X-M2M-ORIGIN. With the option –origin you can overwrite the default value of d2ccli. By convension oneM2M requires that the X-M2M-ORIGIN value is prefixed with a C character. This is done automatically by d2c, so please define the origin without the leading C.

--name <string>, -n <string>
The required --name option defines the unique identifier of the application. Alternatively you can use --id option instead of --name to identify the application.

--id <string>, -i <string>
The required --id option defines the unique identifier of the application. Alternatively you can use --name option instead of --id to identify the application.

--description <string>, -de <string>
With --description option you can define the description of the application.

--urls <list-of-urls>, -us <list-of-urls>
With the --urls option you can modify the list of application urls. In the normal case you only define a single url per application. But for special casses such as debugging multiple urls are supported.

You have the following possibilities to modify the list of associated urls:

--connection-properties <json-object>, -cp <json-object>
With the option --connection-properties you can configure the connection of an application. It is a key/value map as json object. In the case of a webHook application thoses connection properties are the header fields which are attached to each HTTP POST request to forward the received device uplink messages to the application.

--connection-properties '{
    "Authorization":"cm9sYW5kLmJhbGRpbkB0ZWxla29tLmRlOlI5OXR0RCM/P3F0P0htJkE=",
    "iot-decoding-selector":"adeunis"
}'

To control if a single property shall be added to or deleted from the current map of properties you can prefix the property name with one of the following operation indicators:

--profile-file <file>, -p <file>
DMO access profile file which shall be used instead of the current activated on in the d2c configuration.

--origin <string>, -o <string>
Each request to the DMO API requires the HTTP header field X-M2M-ORIGIN. With the option –origin you can overwrite the default value of d2ccli. By convension oneM2M requires that the X-M2M-ORIGIN value is prefixed with a C character. This is done automatically by d2c, so please define the origin without the leading C.