In the `mbed_cloud_dev_credentials.c` file, note the device endpoint name in the following line: `const char MBED_CLOUD_DEV_BOOTSTRAP_ENDPOINT_NAME = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" `. Bootstrapping the device enables you to associate custom properties to the device, such as assigning the device to a region to which a certain policy applies. In the field, a technician would enter the endpoint name in the SDA technician application or use the device ID if the device has bootstrapped. You can also use tools such as () to supply long names to the application. **Notes about endpoint name:** For the convenience of the demo and for development purposes, you can provide a default endpoint name in the `arm-sda-android/app/src/main/res/values/properties.xml` file, as described above. device_ep is the device endpoint name, which you can see in the mbed_cloud_dev_credentials.c file you downloaded earlier.account_id is your account ID, which you can see in Device Management Portal by selecting Team configuration > Team profile from the side menu.env\_url is the Device Management base URL (this URL is different only if you have Device Management on-premises).Paste your device endpoint name from the developer certificate To connect to Device Management, you must provide your application with the Device Management base URL, your device's endpoint name or device ID and your account ID by editing the arm-sda-android/app/src/main/res/values/properties.xml file: To include the secure device access SDK as a library in your project and build the APK:Ĭlone the SDA SDK GitHub repository to your computer. You can use the SDA SDK in Android applications to implement an SDA technician application that logs into Izuma Device Management, requests an access token and then connects to the IoT device to instruct it to perform the requested operation. Setting up the Android Package Kit (APK) Setting up the Android Package Kit (APK)
0 kommentar(er)
