From f5a52adf0f2d0b69385b86b85f84e2c26b41e877 Mon Sep 17 00:00:00 2001 From: Dafina Karamanoleva Date: Tue, 3 Sep 2024 10:59:00 +0300 Subject: [PATCH 01/12] [DM-3890]: Changed DM title to be title cased. --- README.md | 2 +- .../cra-general-aspects-bundle/how-it-works.md | 2 +- .../cra-general-aspects-bundle/when-to-use.md | 2 +- .../accessing-cra.md | 2 +- .../managing-assets-bundle/asset-hierarchy.md | 14 +++++++------- .../working-with-assets.md | 4 ++-- content/cockpit/smart-rules-collection.md | 2 +- .../extensible-device-registration.md | 6 +++--- .../device-management.md | 2 +- content/concepts/concepts-introduction.md | 2 +- content/concepts/interfacing-devices.md | 2 +- .../data-subscriptions.md | 2 +- .../configuring-offloading-jobs.md | 2 +- .../device-integration/device-certificates.md | 6 +++--- .../integration-life-cycle.md | 6 +++--- .../fragment-library-bundle/connectivity.md | 2 +- .../fragment-library-bundle/device-info.md | 4 ++-- .../fragment-ibrary-introduction.md | 6 +++--- .../mqtt-bundle/integration-life-cycle.md | 2 +- .../mqtt-examples-bundle/hello-mqtt-c.md | 2 +- .../hello-mqtt-java-certificates.md | 2 +- .../mqtt-examples-bundle/hello-mqtt-java.md | 2 +- .../hello-mqtt-javascript.md | 2 +- .../mqtt-examples-bundle/hello-mqtt-nodejs.md | 2 +- .../mqtt-examples-bundle/hello-mqtt-python.md | 2 +- .../mqtt-examples-bundle/hello-mqtt.md | 8 ++++---- content/device-integration/mqtt.md | 2 +- .../hello-rest-x509.md | 2 +- .../rest-client-examples-bundle/hello-rest.md | 2 +- content/device-management-application-card.md | 4 ++-- .../device-management-application/_index.html | 2 +- .../connectivity.md | 8 ++++---- .../using-smart-groups.md | 2 +- .../home-dashboard.md | 4 ++-- .../managing-device-data.md | 10 +++++----- .../managing-device-types.md | 2 +- .../monitoring-and-controlling-devices.md | 4 ++-- .../monitoring-device-services.md | 4 ++-- .../registering-devices.md | 6 +++--- .../smartrest-templates.md | 4 ++-- .../viewing-device-details.md | 2 +- .../asset-hierarchy-bundle/creating-assets-ui.md | 2 +- content/get-familiar-with-the-ui/gui-features.md | 2 +- .../get-familiar-with-the-ui/ui-introduction.md | 2 +- content/glossary/d.md | 4 ++-- content/glossary/l.md | 2 +- content/glossary/m.md | 2 +- content/glossary/o.md | 2 +- content/glossary/p.md | 2 +- .../java-bundle/ip-tracker-microservice.md | 4 ++-- content/oee/oee-faq-bundle/dashboards.md | 2 +- content/oee/oee-faq-bundle/platform.md | 4 ++-- .../cloud-fieldbus-bundle/connecting-fieldbus.md | 8 ++++---- .../deprovisioning-lora-devices.md | 2 +- .../lora-actility-bundle/introduction.md | 2 +- .../lora-creating-device-protocols.md | 2 +- .../lora-sending-operations.md | 2 +- .../registering-lora-devices.md | 4 ++-- .../device-registration-via-platform.md | 4 ++-- .../loriot-creating-device-protocols.md | 2 +- .../loriot-sending-operations.md | 2 +- .../deploying-sample-codec-microservice.md | 4 ++-- .../lwm2m-bundle/device-details.md | 2 +- .../lwm2m-bundle/device-protocols.md | 4 ++-- .../lwm2m-bundle/registering-lwm2m-devices.md | 4 ++-- .../sigfox-bundle/device-protocols.md | 2 +- .../sigfox-bundle/introduction.md | 2 +- .../sigfox-bundle/registering-sigfox-devices.md | 4 ++-- .../sigfox-bundle/sending-operations.md | 2 +- content/quick-start/first-steps.md | 2 +- content/sector/device_management/_index.md | 2 +- content/sensor-app/controlling-devices.md | 2 +- content/sensor-app/registering-the-sensor-app.md | 2 +- content/standard-tenant/alarm-mapping.md | 2 +- .../ecosystem-bundle/managing-applications.md | 2 +- .../ecosystem-bundle/subscribed-applications.md | 2 +- content/standard-tenant/home-screen.md | 2 +- .../managing-permissions-bundle/global-roles.md | 2 +- .../improving-performance.md | 6 +++--- content/standard-tenant/managing-permissions.md | 2 +- .../analytics-builder-bundle/getting-started.md | 16 ++++++++-------- .../models-and-devices.md | 2 +- .../using-the-model-editor.md | 2 +- .../introduction-analytics.md | 2 +- data/component.json | 16 ++++++++-------- data/productarea.json | 2 +- static/admin/config.yml | 6 +++--- 87 files changed, 150 insertions(+), 150 deletions(-) diff --git a/README.md b/README.md index 7b874d7bf9..6f3f00b153 100644 --- a/README.md +++ b/README.md @@ -111,7 +111,7 @@ weight: 10 # to set the position in the page ## Add content as Markdown or HTML * Certified hardware kits and software libraries you can use to bring your remote assets into the cloud. -* Device management, data visualization and remote control functionality through the web. +* Device Management, data visualization and remote control functionality through the web. * Rapid customization of the above through [real-time processing](/concepts/realtime) and [Cumulocity applications](/concepts/applications). * APIs for extending the existing functionality or interfacing Cumulocity with your other IT services such as ERP or CRM systems. Cumulocity can also host your HTML5 applications. […] diff --git a/content/cloud-remote-access/cra-general-aspects-bundle/how-it-works.md b/content/cloud-remote-access/cra-general-aspects-bundle/how-it-works.md index 1d8a93d36a..41de65df25 100644 --- a/content/cloud-remote-access/cra-general-aspects-bundle/how-it-works.md +++ b/content/cloud-remote-access/cra-general-aspects-bundle/how-it-works.md @@ -17,7 +17,7 @@ The following protocols are supported: See [Supported protocols and gateways](/cloud-remote-access/communication/#supported-protocols) for details. -Cloud Remote Access works as in the illustration below. The remotely controlled device runs a VNC, SSH or Telnet server and is connected to a gateway compatible with Cloud Remote Access. This gateway must be registered as a device within the Device management application in {{< product-c8y-iot >}}. More information about registering devices and instructions can be found in [Registering devices](/device-management-application/registering-devices). +Cloud Remote Access works as in the illustration below. The remotely controlled device runs a VNC, SSH or Telnet server and is connected to a gateway compatible with Cloud Remote Access. This gateway must be registered as a device within the Device Management application in {{< product-c8y-iot >}}. More information about registering devices and instructions can be found in [Registering devices](/device-management-application/registering-devices). ![Cloud Remote Access - VNC](/images/cra/cra-VNC2.png) diff --git a/content/cloud-remote-access/cra-general-aspects-bundle/when-to-use.md b/content/cloud-remote-access/cra-general-aspects-bundle/when-to-use.md index cb767e7c6f..6e082e139e 100644 --- a/content/cloud-remote-access/cra-general-aspects-bundle/when-to-use.md +++ b/content/cloud-remote-access/cra-general-aspects-bundle/when-to-use.md @@ -4,7 +4,7 @@ weight: 30 layout: bundle --- -To provide the best level of control, remote devices should be represented as devices in the [Device management application](/device-management-application) of {{< product-c8y-iot >}}, with the corresponding reporting, remote control and real-time functionality. +To provide the best level of control, remote devices should be represented as devices in the [Device Management application](/device-management-application) of {{< product-c8y-iot >}}, with the corresponding reporting, remote control and real-time functionality. In some cases however, it is not possible or not economic to implement every aspect of a machine or remote device in a {{< product-c8y-iot >}} agent. For example, in case of a legacy device that does not have APIs for accessing certain parts of the functionality, or in case of a device that has many very low-level configuration parameters that would be very involved to map to {{< product-c8y-iot >}}. diff --git a/content/cloud-remote-access/using-cloud-remote-access-bundle/accessing-cra.md b/content/cloud-remote-access/using-cloud-remote-access-bundle/accessing-cra.md index a10e91a95b..deb16fccbc 100644 --- a/content/cloud-remote-access/using-cloud-remote-access-bundle/accessing-cra.md +++ b/content/cloud-remote-access/using-cloud-remote-access-bundle/accessing-cra.md @@ -4,7 +4,7 @@ weight: 20 layout: bundle --- -In the Device management application in the {{< product-c8y-iot >}} platform, click **All devices** in the **Devices** menu and select the desired gateway from the device list. +In the Device Management application in the {{< product-c8y-iot >}} platform, click **All devices** in the **Devices** menu and select the desired gateway from the device list. When you open the gateway you will find the **Remote access** tab in its tab list. diff --git a/content/cockpit/managing-assets-bundle/asset-hierarchy.md b/content/cockpit/managing-assets-bundle/asset-hierarchy.md index a45c75aa7b..9553783d79 100644 --- a/content/cockpit/managing-assets-bundle/asset-hierarchy.md +++ b/content/cockpit/managing-assets-bundle/asset-hierarchy.md @@ -22,23 +22,23 @@ Assets are organized in hierarchies. For example, an energy monitoring applicati The asset hierarchy is composed of two types of objects: -* **Groups**: Objects which group single devices or other groups. Groups can either be created in the Cockpit application or in the Device management application. +* **Groups**: Objects which group single devices or other groups. Groups can either be created in the Cockpit application or in the Device Management application. * **Custom assets**: Objects defined by an asset model and created in the [Digital twin manager](/dtm/dtm-introduction/) application. -* **Devices**: Devices which are linked into the asset hierarchy. Before you can use devices in the Cockpit application, they must be connected to {{< product-c8y-iot >}}. This is done in the Device management application. For details on connecting devices refer to [Registering devices](/device-management-application/registering-devices/). +* **Devices**: Devices which are linked into the asset hierarchy. Before you can use devices in the Cockpit application, they must be connected to {{< product-c8y-iot >}}. This is done in the Device Management application. For details on connecting devices refer to [Registering devices](/device-management-application/registering-devices/). In this example, the group objects represent a building asset. The device objects represent the room asset. The group names and hierarchy can be defined individually by the user. The hierarchy can have multiple levels, like region level, city level, street level, building level, floor level and room level. Any device can be part of multiple and different hierarchies, like part of regional hierarchy and part of customer hierarchy. To position a device in the asset hierarchy, you must "assign" the device to the respective group (see below). {{< c8y-admon-info >}} -Single devices are not managed in the Cockpit application. They are managed in the Device management application. +Single devices are not managed in the Cockpit application. They are managed in the Device Management application. {{< /c8y-admon-info >}} {{< c8y-admon-related >}} - [Getting started > Technical concepts > {{< product-c8y-iot >}}'s domain model](/concepts/domain-model/) for details on {{< product-c8y-iot >}}'s domain model. -- [Device management > Device management application](/device-management-application/) for details on working with devices in {{< product-c8y-iot >}}. +- [Device Management > Device Management application](/device-management-application/) for details on working with devices in {{< product-c8y-iot >}}. - Refer to the [{{< product-c8y-iot >}} Codex](https://styleguide.cumulocity.com/apps/codex/#/) for more information on developing applications in the {{< product-c8y-iot >}} environment. Moreover find various related tutorials in the [{{< sag-dev-community >}}]({{< link-sag-tech-forum >}}). {{< /c8y-admon-related >}} @@ -69,10 +69,10 @@ The second example shows how gateway devices can be used in the Cockpit applicat ![Linked gateway devices](/images/users-guide/cockpit/cockpit-groups-image3.png) -Gateway devices are as well represented as top level devices in the Device management application. Their attached devices (like for example Modbus or KNX devices) are shown as child devices. These child devices can be organized in the asset hierarchy in the Cockpit application as shown above. +Gateway devices are as well represented as top level devices in the Device Management application. Their attached devices (like for example Modbus or KNX devices) are shown as child devices. These child devices can be organized in the asset hierarchy in the Cockpit application as shown above. -As you can see from the example, devices can have completely different hierarchies in the Device management application and in the Cockpit application: -While inside the Device management application all child devices are below the gateway device, the same child devices are organized in two different buildings in the Cockpit. +As you can see from the example, devices can have completely different hierarchies in the Device Management application and in the Cockpit application: +While inside the Device Management application all child devices are below the gateway device, the same child devices are organized in two different buildings in the Cockpit. ### Cockpit assets versus business assets {#cockpit-assets-versus-business-assets} diff --git a/content/cockpit/managing-assets-bundle/working-with-assets.md b/content/cockpit/managing-assets-bundle/working-with-assets.md index 9085e780d9..791b93bdcd 100644 --- a/content/cockpit/managing-assets-bundle/working-with-assets.md +++ b/content/cockpit/managing-assets-bundle/working-with-assets.md @@ -19,7 +19,7 @@ Moreover, subassets are shown in the **Subassets** tab of the particular group w {{< c8y-admon-info >}} The count displayed on top of the table on the **Subassets** tab shows the total number of child assets assigned to the current group. Any type of managed object can be a child asset. For more details on the counting of objects refer to the operation [Retrieve all child assets of a specific managed object](https://{{< domain-c8y >}}/api/core/#operation/getManagedObjectChildAssetsResource) in the {{< openapi >}}. -If you add a gateway device, the child devices are not shown. To show child devices, you must add them to the related asset. Details related to the child hierarchy are visible and editable in the Device management application. +If you add a gateway device, the child devices are not shown. To show child devices, you must add them to the related asset. Details related to the child hierarchy are visible and editable in the Device Management application. {{< /c8y-admon-info >}} Use the navigator, to navigate through the asset hierarchy. @@ -96,7 +96,7 @@ In the resulting dialog box, you can select to also delete all devices inside th ### To assign devices to a group {#to-assign-devices-to-a-group} -Before adding a device to the asset hierarchy, it must be connected to {{< product-c8y-iot >}}. Connecting devices to the platform is done in the Device management application. For details on connecting devices refer to [Device management application](/device-management-application/registering-devices/). +Before adding a device to the asset hierarchy, it must be connected to {{< product-c8y-iot >}}. Connecting devices to the platform is done in the Device Management application. For details on connecting devices refer to [Device Management application](/device-management-application/registering-devices/). To assign devices to a group, follow these steps: diff --git a/content/cockpit/smart-rules-collection.md b/content/cockpit/smart-rules-collection.md index ac7432f927..7aa7b41ce4 100644 --- a/content/cockpit/smart-rules-collection.md +++ b/content/cockpit/smart-rules-collection.md @@ -13,7 +13,7 @@ In certain rule parameters, various trigger fields can be used as variables, see {{< /c8y-admon-info >}} {{< c8y-admon-related >}} -- [Device management > Monitoring and controlling devices > Working with alarms](/device-management-application/monitoring-and-controlling-devices/#working-with-alarms) for details on alarms in {{< product-c8y-iot >}}. +- [Device Management > Monitoring and controlling devices > Working with alarms](/device-management-application/monitoring-and-controlling-devices/#working-with-alarms) for details on alarms in {{< product-c8y-iot >}}. - [Analytics > Streaming analytics > Troubleshooting and diagnostics > Alarms generated by the Apama-ctrl microservice](/streaming-analytics/troubleshooting/#alarms) for more information on alarms for smart rules generated by the Apama-ctrl microservice. - [Alarms](https://{{< domain-c8y >}}/api/core/#tag/Alarms) in the {{< openapi >}} for details on managing alarms via REST. {{< /c8y-admon-related >}} diff --git a/content/concepts/applications-bundle/extensible-device-registration.md b/content/concepts/applications-bundle/extensible-device-registration.md index 37bfd5877e..a1fe85d478 100644 --- a/content/concepts/applications-bundle/extensible-device-registration.md +++ b/content/concepts/applications-bundle/extensible-device-registration.md @@ -20,7 +20,7 @@ Extensible device registration requires [application extensions](/concepts/appli The extended device registration provides the following advantages: -- **Extensibility of the device registration wizard**: You can easily add own forms to the device registration wizard in the Device management application UI. The values to be entered in the user-specified forms can be freely customized by the device integration developers. +- **Extensibility of the device registration wizard**: You can easily add own forms to the device registration wizard in the Device Management application UI. The values to be entered in the user-specified forms can be freely customized by the device integration developers. - **Support for bulk registration using custom CSV**: You can customize the bulk registration and hence implement support for CSV files of a different format. @@ -62,7 +62,7 @@ There are two types of extensions: ### Single device registration {#single-device-registration} -After enabling the `extensibleDeviceRegistration` extension type, the **Devices** > **Register device** menu in the Device management application is extended with an entry corresponding to the extension `name` property. +After enabling the `extensibleDeviceRegistration` extension type, the **Devices** > **Register device** menu in the Device Management application is extended with an entry corresponding to the extension `name` property. From now on, everything will be rendered based on data provided via the custom microservice. The added menu entry opens a window which fetches the form definition using the following endpoint: @@ -170,7 +170,7 @@ The following diagram visualizes the single device registration flow: Many device integrations require the registration of many devices at the same time. Currently, all protocols must rely on the bulk registration mechanism of the platform, which often either requires too many fields or requires custom fields to be added. The latter ones can however so far not be validated, as the core directly creates devices -- and microservices and agents have no control over the properties being written to the managed objects. -After enabling the `extensibleBulkDeviceRegistration` extension type, the Device management > Devices > Register device `Bulk device registration` modal is displayed with an extended wizard entry corresponding to the extension `name` property. +After enabling the `extensibleBulkDeviceRegistration` extension type, the Device Management > Devices > Register device `Bulk device registration` modal is displayed with an extended wizard entry corresponding to the extension `name` property. Additionally, the microservice provides the title of the wizard step and example bulk file(s): ```json diff --git a/content/concepts/concepts-introduction-bundle/device-management.md b/content/concepts/concepts-introduction-bundle/device-management.md index 12b59c002b..7bb998fac1 100644 --- a/content/concepts/concepts-introduction-bundle/device-management.md +++ b/content/concepts/concepts-introduction-bundle/device-management.md @@ -1,5 +1,5 @@ --- -title: Device management +title: Device Management weight: 40 --- diff --git a/content/concepts/concepts-introduction.md b/content/concepts/concepts-introduction.md index 63183a6bb7..32fc60ce2b 100644 --- a/content/concepts/concepts-introduction.md +++ b/content/concepts/concepts-introduction.md @@ -13,7 +13,7 @@ sector: {{< product-c8y-iot >}} provides * Certified software libraries you can use to bring your remote assets into the cloud. -* Device management, data visualization and remote control functionality through the web. +* Device Management, data visualization and remote control functionality through the web. * Rapid customization of these functionalities through [real-time processing](/concepts/realtime) and [applications](/concepts/applications). * APIs for extending the existing functionality or interfacing {{< product-c8y-iot >}} with your other IT services such as ERP or CRM systems. {{< product-c8y-iot >}} can also host your HTML5 applications. diff --git a/content/concepts/interfacing-devices.md b/content/concepts/interfacing-devices.md index c06d46b3ab..d0a0b854c1 100644 --- a/content/concepts/interfacing-devices.md +++ b/content/concepts/interfacing-devices.md @@ -15,7 +15,7 @@ To interface these systems with {{< product-c8y-iot >}}, a driver software calle {{< c8y-admon-related >}} - [Getting started > Technical concepts > {{< product-c8y-iot >}}´s domain model](/concepts/domain-model) for understanding the data structures exchanged between agents and the {{< product-c8y-iot >}} core. -- [Device management > Device integration](/device-integration) for understanding in detail how to develop agent software using the REST or MQTT protocols. +- [Device Management > Device integration](/device-integration) for understanding in detail how to develop agent software using the REST or MQTT protocols. - [REST implementation](https://{{< domain-c8y >}}/api/core/#section/REST-implementation) in the {{< openapi >}}, for a detailed specification of the interfaces between agents and the {{< product-c8y-iot >}} core. {{< /c8y-admon-related >}} diff --git a/content/data-broker/data-broker-application-bundle/data-subscriptions.md b/content/data-broker/data-broker-application-bundle/data-subscriptions.md index bc823abc81..52be24fa32 100644 --- a/content/data-broker/data-broker-application-bundle/data-subscriptions.md +++ b/content/data-broker/data-broker-application-bundle/data-subscriptions.md @@ -27,7 +27,7 @@ Use the toggle to temporarily stop forwarding data into your tenant. 3. When the connection is established, click **Accept** to start forwarding data into your tenant. The subscription is active now. 4. You can use the toggle in the card to temporarily stop forwarding data into your tenant. -You can now navigate to the Device management application or the Cockpit application. You will find a new "virtual group" with a specific icon showing the forwarded devices. The group will have the same name as your subscription. Devices are "lazily" created on the destination side whenever they send data for the first time after setting up an active subscription. +You can now navigate to the Device Management application or the Cockpit application. You will find a new "virtual group" with a specific icon showing the forwarded devices. The group will have the same name as your subscription. Devices are "lazily" created on the destination side whenever they send data for the first time after setting up an active subscription. ![Data broker group in cockpit app](/images/users-guide/enterprise-tenant/et-data-broker-group-created.png) diff --git a/content/datahub/working-with-datahub-bundle/configuring-offloading-jobs.md b/content/datahub/working-with-datahub-bundle/configuring-offloading-jobs.md index 1a33c909d9..adbe8a5465 100644 --- a/content/datahub/working-with-datahub-bundle/configuring-offloading-jobs.md +++ b/content/datahub/working-with-datahub-bundle/configuring-offloading-jobs.md @@ -230,7 +230,7 @@ The first time an offloading run processes multiple fragments with the correspon ##### Raising alarms {#raising-alarms} -Offloading as well as compaction runs may fail due to various reasons such as network issues and timeouts. As described in [History per offloading pipeline](/datahub/working-with-datahub/#history-per-offloading-job) and [History of compactions per offloading pipeline](/datahub/working-with-datahub/#history-compaction-per-offloading-job), the offloading and compaction job histories provide details for successful and failed runs. Additionally, an alarm can be raised within the {{< product-c8y-iot >}} platform in case of a failure. Such an alarm is available in the {{< product-c8y-iot >}} [Device management application](/device-management-application/monitoring-and-controlling-devices/#working-with-alarms). +Offloading as well as compaction runs may fail due to various reasons such as network issues and timeouts. As described in [History per offloading pipeline](/datahub/working-with-datahub/#history-per-offloading-job) and [History of compactions per offloading pipeline](/datahub/working-with-datahub/#history-compaction-per-offloading-job), the offloading and compaction job histories provide details for successful and failed runs. Additionally, an alarm can be raised within the {{< product-c8y-iot >}} platform in case of a failure. Such an alarm is available in the {{< product-c8y-iot >}} [Device Management application](/device-management-application/monitoring-and-controlling-devices/#working-with-alarms). Under **Create alarm on** you can activate raising alarms for offloading as well as compaction failures. Per default, the setting is activated for offloading and deactivated for compaction failures. When activated and an offloading run fails, an alarm is raised. If the offloading fails multiple times in a row, the associated alarm is updated with each new failure. The more successive runs fail, the higher the severity of the alarm will be, ranging from warning up to critical. Each alarm comprises information which offloading pipeline has failed and how often it has failed in a row. The same applies to alarms being raised for compaction failures. diff --git a/content/device-integration/device-certificates.md b/content/device-integration/device-certificates.md index 18126a2d7c..978782f038 100644 --- a/content/device-integration/device-certificates.md +++ b/content/device-integration/device-certificates.md @@ -52,7 +52,7 @@ The device_user will be created when the API is called for the first time, provi **Bulk registration** -The user for the device can also be created via the standard [bulk registration](/device-management-application/registering-devices/#to-bulk-register-devices) in the Device management application. +The user for the device can also be created via the standard [bulk registration](/device-management-application/registering-devices/#to-bulk-register-devices) in the Device Management application. The CSV file used in bulk registration should meet the requirements described in [Create a bulk device credentials request](https://{{< domain-c8y >}}/api/core/#operation/postBulkNewDeviceRequestCollectionResource) in the {{< openapi >}}. Moreover, it is required that the CSV file has an additional column AUTH_TYPE with value CERTIFICATES, and that the column CREDENTIALS is either not present or has an empty value. @@ -329,7 +329,7 @@ Upload your CA (or intermediate) certificate to the platform. This operation wil **Via UI:** -1. In the Device management application, navigate to the **Management** menu in the navigator and select **Trusted certificates**. +1. In the Device Management application, navigate to the **Management** menu in the navigator and select **Trusted certificates**. 2. In the resulting dialog, enter a custom name for the new certificate. 3. Drop your CA certificate (caCert.pem or intermediateCert.pem). 4. Select the **Auto registration** check box. @@ -376,7 +376,7 @@ To ensure verification of ownership by the uploader, a proof of possession is re The steps for the proof of possession are as follows: -1. Navigate to **Management** > **Trusted certificates** in the Device management application and verify that the certificate has been uploaded properly. +1. Navigate to **Management** > **Trusted certificates** in the Device Management application and verify that the certificate has been uploaded properly.
![Verify certificate](/images/mqtt/mqtt-cert-check.png) 2. In the **Proof of Possession** section of the certificate details, download the verification code. diff --git a/content/device-integration/device-integration-rest-bundle/integration-life-cycle.md b/content/device-integration/device-integration-rest-bundle/integration-life-cycle.md index 273f0f5bd7..5fd999c17a 100644 --- a/content/device-integration/device-integration-rest-bundle/integration-life-cycle.md +++ b/content/device-integration/device-integration-rest-bundle/integration-life-cycle.md @@ -193,7 +193,7 @@ To create a managed object, issue a POST request on the managed objects collecti The example above contains a number of metadata items for the device: -- "c8y\_IsDevice" marks devices that can be managed using {{< product-c8y-iot >}}'s Device management application. +- "c8y\_IsDevice" marks devices that can be managed using {{< product-c8y-iot >}}'s Device Management application. - "com\_cumulocity\_model\_Agent" marks devices running a {{< product-c8y-iot >}} agent. Such devices will receive all operations targeted to themselves and their children for routing. - "c8y\_SupportedOperations" states that this device can be restarted and configured. In addition, it can carry out software and firmware updates. @@ -524,9 +524,9 @@ Do the following: 1. Turn off the old physical device. 2. [Register and bootstrap](/device-management-application/registering-devices) the new device just like a regular device. 3. After the device has created its new managed object, turn the new physical device off. -4. Open the new device object in [{{< product-c8y-iot >}}'s Device management application](/device-management-application/viewing-device-details/#info) and look up the device owner and the device's external IDs. +4. Open the new device object in [{{< product-c8y-iot >}}'s Device Management application](/device-management-application/viewing-device-details/#info) and look up the device owner and the device's external IDs. 5. Remove the external IDs from the device. -6. Open the old device in {{< product-c8y-iot >}}'s Device management application and change its owner to the one you looked up, and also add the external IDs you removed from the new device. +6. Open the old device in {{< product-c8y-iot >}}'s Device Management application and change its owner to the one you looked up, and also add the external IDs you removed from the new device. 7. Remove the new device object that was created earlier but keep the device user. 9. Turn on the new physical device. diff --git a/content/device-integration/fragment-library-bundle/connectivity.md b/content/device-integration/fragment-library-bundle/connectivity.md index cdb9838c7e..0dea27d813 100644 --- a/content/device-integration/fragment-library-bundle/connectivity.md +++ b/content/device-integration/fragment-library-bundle/connectivity.md @@ -6,7 +6,7 @@ sector: - device_management --- -The **Connectivity** tab integrates with a 3rd party SIM management platform to provide SIM management functionality within the {{< product-c8y-iot >}} Device management application. The tab appears for a device when all of the following criteria are met: +The **Connectivity** tab integrates with a 3rd party SIM management platform to provide SIM management functionality within the {{< product-c8y-iot >}} Device Management application. The tab appears for a device when all of the following criteria are met: 1. Connectivity microservice is subscribed and configured 2. The device managed object contains the ```c8y_Mobile``` fragment with the MSISDN or ICCID property set diff --git a/content/device-integration/fragment-library-bundle/device-info.md b/content/device-integration/fragment-library-bundle/device-info.md index b31ea5d69d..d377d8d1e3 100644 --- a/content/device-integration/fragment-library-bundle/device-info.md +++ b/content/device-integration/fragment-library-bundle/device-info.md @@ -10,7 +10,7 @@ The **Device information** tab is a predefined dashboard with several widgets th ### Device marker {#device-marker} - A device is marked in the inventory with a ```c8y_IsDevice``` fragment in its own managed object. Only devices with this fragment appear in the all **All devices** list in the Device management application. + A device is marked in the inventory with a ```c8y_IsDevice``` fragment in its own managed object. Only devices with this fragment appear in the all **All devices** list in the Device Management application. ```http PUT /inventory/managedObjects/ @@ -48,7 +48,7 @@ Devices capable of restarting remotely can announce this capability by adding th #### Restart operation {#restart-operation} -Upon clicking the **Restart** button in the Device management application an operation as follows is sent: +Upon clicking the **Restart** button in the Device Management application an operation as follows is sent: ```json { diff --git a/content/device-integration/fragment-library-bundle/fragment-ibrary-introduction.md b/content/device-integration/fragment-library-bundle/fragment-ibrary-introduction.md index 19e55e1136..37a11bce24 100644 --- a/content/device-integration/fragment-library-bundle/fragment-ibrary-introduction.md +++ b/content/device-integration/fragment-library-bundle/fragment-ibrary-introduction.md @@ -14,10 +14,10 @@ If you are interested in details on exposing the {{< product-c8y-iot >}}´s func Moreover, see [SmartREST](/smartrest/smartrest-two) for more information on SmartREST and a complete list of all SmartREST templates mentioned throughout the following sections. -To start with device management, open the **All devices** tab in the **Devices** menu of the Device management application. Click on a device in the list to open the device details of this particular device. You will see various tabs and particular information on each of them. +To start with device management, open the **All devices** tab in the **Devices** menu of the Device Management application. Click on a device in the list to open the device details of this particular device. You will see various tabs and particular information on each of them. {{< c8y-admon-info >}} -For a detailed explanation of each tab and its related configuration via the UI, see also [Device management application > Viewing device details](/device-management-application/viewing-device-details). +For a detailed explanation of each tab and its related configuration via the UI, see also [Device Management application > Viewing device details](/device-management-application/viewing-device-details). {{< /c8y-admon-info >}} ![Device details](/images/reference-guide/device-details.png) @@ -86,7 +86,7 @@ The following fragments can be added to the ```c8y_SupportedOperations``` fragme c8y_Network -Sends data to the Network tab in the Device management application and displays the network information +Sends data to the Network tab in the Device Management application and displays the network information c8y_Position diff --git a/content/device-integration/mqtt-bundle/integration-life-cycle.md b/content/device-integration/mqtt-bundle/integration-life-cycle.md index 889ae37183..feddabe3e4 100644 --- a/content/device-integration/mqtt-bundle/integration-life-cycle.md +++ b/content/device-integration/mqtt-bundle/integration-life-cycle.md @@ -48,7 +48,7 @@ For more information, refer to the [Hello MQTT](/device-integration/mqtt-example The process works as follows: * {{< product-c8y-iot >}} assumes that each device has some form of unique ID. For instance, a good device identifier can be the MAC address of the network adapter, the IMEI of a mobile device or a hardware serial number. -* When you take a new device into use, you enter this unique ID into **Device registration** in the Device management application in {{< product-c8y-iot >}}, and start the device. +* When you take a new device into use, you enter this unique ID into **Device registration** in the Device Management application in {{< product-c8y-iot >}}, and start the device. * The device will use this ID as part of the [MQTT ClientId](/device-integration/mqtt#mqtt-clientid) and static user credentials that can be enquired from [product support](/additional-resources/contacting-support/). * The device subscribes to the topic s/dcr. * The device starts publishing continuous empty messages on the topic s/ucr to notify the server that it is ready to retrieve credentials. diff --git a/content/device-integration/mqtt-examples-bundle/hello-mqtt-c.md b/content/device-integration/mqtt-examples-bundle/hello-mqtt-c.md index 144cb399bd..8fc775921e 100644 --- a/content/device-integration/mqtt-examples-bundle/hello-mqtt-c.md +++ b/content/device-integration/mqtt-examples-bundle/hello-mqtt-c.md @@ -136,7 +136,7 @@ Message '100,C MQTT,c8y_MQTTDevice' with delivery token 1 delivered ... ``` -After starting the application, you should see a new device in the Device management application, listed in **All devices**. +After starting the application, you should see a new device in the Device Management application, listed in **All devices**. Additionally, if there will be a new operation created for this device (for example `c8y_Restart`), information about it will be printed to the console. diff --git a/content/device-integration/mqtt-examples-bundle/hello-mqtt-java-certificates.md b/content/device-integration/mqtt-examples-bundle/hello-mqtt-java-certificates.md index 5f0201bf5c..746918ea13 100644 --- a/content/device-integration/mqtt-examples-bundle/hello-mqtt-java-certificates.md +++ b/content/device-integration/mqtt-examples-bundle/hello-mqtt-java-certificates.md @@ -21,7 +21,7 @@ In order to follow this tutorial, check the following prerequisites: If you don't have a valid certificate, you can generate one for testing purposes, following the instructions below. 1. Download the scripts from the [cumulocity-examples](https://github.com/SoftwareAG/cumulocity-examples/tree/develop/mqtt-client/scripts) repository. -2. Create a root self-signed certificate (execute the script *00createRootSelfSignedCertificate.sh*) and upload it to your tenant. You can do it via [the Device management application in the UI](/device-management-application/managing-device-data/#managing-trusted-certificates) or via [REST](https://{{< domain-c8y >}}/api/core/#tag/Tenant-API). +2. Create a root self-signed certificate (execute the script *00createRootSelfSignedCertificate.sh*) and upload it to your tenant. You can do it via [the Device Management application in the UI](/device-management-application/managing-device-data/#managing-trusted-certificates) or via [REST](https://{{< domain-c8y >}}/api/core/#tag/Tenant-API). 3. Create and sign the certificate (execute the script *01createSignedCertificate.sh*). 4. Move the certificates to keystore (execute the script *02moveCertificatesToKeystore.sh*). Additionally, if only the device leaf certificate is needed in the keystore, use the --leafonly option. 5. Finally, import the trusted certificate into keystore running the following command: diff --git a/content/device-integration/mqtt-examples-bundle/hello-mqtt-java.md b/content/device-integration/mqtt-examples-bundle/hello-mqtt-java.md index 3e221f3fc1..e466919f58 100644 --- a/content/device-integration/mqtt-examples-bundle/hello-mqtt-java.md +++ b/content/device-integration/mqtt-examples-bundle/hello-mqtt-java.md @@ -204,7 +204,7 @@ $ mvn exec:java -Dexec.mainClass="c8y.example.App" Received operation 510,123456789 ``` -After starting the application, you should see a new registered device in the Device management application, listed in **All devices**. In the **Measurements** tab, you will see the temperature measurements being sent by your client. +After starting the application, you should see a new registered device in the Device Management application, listed in **All devices**. In the **Measurements** tab, you will see the temperature measurements being sent by your client. Additionally, if there will be a new operation created for this device (for example `c8y_Restart`), information about it will be printed to the console. diff --git a/content/device-integration/mqtt-examples-bundle/hello-mqtt-javascript.md b/content/device-integration/mqtt-examples-bundle/hello-mqtt-javascript.md index 5d92684c27..e674d892b8 100644 --- a/content/device-integration/mqtt-examples-bundle/hello-mqtt-javascript.md +++ b/content/device-integration/mqtt-examples-bundle/hello-mqtt-javascript.md @@ -150,7 +150,7 @@ Note that the subscription is established after the device creation, otherwise i #### Running the application {#running-the-application} -Open the *hello_mqtt_js.html* file in a browser. You should see a new registered device in the Device management application, listed in **All devices**. In the **Measurements** tab, you will see the temperature measurements being sent by your client. +Open the *hello_mqtt_js.html* file in a browser. You should see a new registered device in the Device Management application, listed in **All devices**. In the **Measurements** tab, you will see the temperature measurements being sent by your client. Additionally, if there will be a new operation created for this device (for example `c8y_Restart`), related information will be displayed in the browser page. diff --git a/content/device-integration/mqtt-examples-bundle/hello-mqtt-nodejs.md b/content/device-integration/mqtt-examples-bundle/hello-mqtt-nodejs.md index 181330123e..1488f4ac77 100644 --- a/content/device-integration/mqtt-examples-bundle/hello-mqtt-nodejs.md +++ b/content/device-integration/mqtt-examples-bundle/hello-mqtt-nodejs.md @@ -127,7 +127,7 @@ Installation needs to be done only once. Afterwards, you only must execute the f $ npm start ``` -You should see a new registered device in the Device management application, listed in **All devices**. In the **Measurements** tab, you will see the temperature measurements being sent by your client. +You should see a new registered device in the Device Management application, listed in **All devices**. In the **Measurements** tab, you will see the temperature measurements being sent by your client. Additionally, if there will be a new operation created for this device (for example `c8y_Restart`), related information about it will be printed to the console. diff --git a/content/device-integration/mqtt-examples-bundle/hello-mqtt-python.md b/content/device-integration/mqtt-examples-bundle/hello-mqtt-python.md index 4a4fc7331d..b0417b106e 100644 --- a/content/device-integration/mqtt-examples-bundle/hello-mqtt-python.md +++ b/content/device-integration/mqtt-examples-bundle/hello-mqtt-python.md @@ -169,7 +169,7 @@ To run the script just use the command: $ python3 hello_mqtt.py ``` -After starting the application you should see a new registered device in the Device management application, listed in **All devices**. In the **Measurements** tab, you will see the temperature measurements being sent by your client. +After starting the application you should see a new registered device in the Device Management application, listed in **All devices**. In the **Measurements** tab, you will see the temperature measurements being sent by your client. Additionally, if there will be a new operation created for this device (for example `c8y_Restart`), information about it will be printed to the console. diff --git a/content/device-integration/mqtt-examples-bundle/hello-mqtt.md b/content/device-integration/mqtt-examples-bundle/hello-mqtt.md index 812dc0fcc0..6176e7c2ae 100644 --- a/content/device-integration/mqtt-examples-bundle/hello-mqtt.md +++ b/content/device-integration/mqtt-examples-bundle/hello-mqtt.md @@ -62,7 +62,7 @@ The first message sent will create our device. Although the static templates sup 100,My first MQTT device,c8y_MQTTdevice ``` -Afterwards, you will find this device in the Device management application as a new device. If you switch to the **Identity** tab of the device you will notice that there was an identity created automatically to link the device to the MQTT ClientId. +Afterwards, you will find this device in the Device Management application as a new device. If you switch to the **Identity** tab of the device you will notice that there was an identity created automatically to link the device to the MQTT ClientId. Besides the name and the type, the device does not have more information, so master data must be added. @@ -77,7 +77,7 @@ The required interval can be set with the template `117` and just takes a single 117,10 ``` -After a reload of the **Info** page of your device in the Device management application, you should see the information we just added. +After a reload of the **Info** page of your device in the Device Management application, you should see the information we just added. ##### Creating measurements {#creating-measurements} @@ -106,7 +106,7 @@ Besides the measurements above, we can also use the template `200` to create a m 200,myCustomTemperatureMeasurement,fahrenheit,75.2,F ``` -After a reload in the Device management application, you should see 4 graphs with the newly added measurements in the **Measurements** tab of your device. +After a reload in the Device Management application, you should see 4 graphs with the newly added measurements in the **Measurements** tab of your device. ##### Creating alarms {#creating-alarms} @@ -148,7 +148,7 @@ The template `401` lets you create location events and takes latitude, longitude 401,51.227741,6.773456 ``` -In the Device management application, you can see one event in the event list but the location has not been updated. This is because on REST these are different requests. Instead of the template `401`, you can use the template `402` in MQTT. It works exactly the same as `401` but additionally it also updates the position of the device itself. +In the Device Management application, you can see one event in the event list but the location has not been updated. This is because on REST these are different requests. Instead of the template `401`, you can use the template `402` in MQTT. It works exactly the same as `401` but additionally it also updates the position of the device itself. ```text 402,51.227741,6.773456 diff --git a/content/device-integration/mqtt.md b/content/device-integration/mqtt.md index 0e66812969..0a61c58e6f 100644 --- a/content/device-integration/mqtt.md +++ b/content/device-integration/mqtt.md @@ -11,7 +11,7 @@ The MQTT implementation of {{< product-c8y-iot >}} provides the following benefi * Multi-tenancy support: A single endpoint serves multiple tenants. * Device identity management: Devices authenticate using device-specific credentials. * Device registration: Non-personalized devices can be deployed by pairing them with {{< product-c8y-iot >}} tenants. -* Device management: Rich, pre-defined device management payload formats to enable out-of-the-box management of millions of devices. +* Device Management: Rich, pre-defined device management payload formats to enable out-of-the-box management of millions of devices. * Standard IoT payload formats: Pre-defined payload formats to support IoT sensor readings, alarm management, remote control and device hierarchies. * Custom payload formats: Additional payload formats can be added. * Minimum traffic overhead. diff --git a/content/device-integration/rest-client-examples-bundle/hello-rest-x509.md b/content/device-integration/rest-client-examples-bundle/hello-rest-x509.md index c3cd245cbf..9ae42dd1f4 100644 --- a/content/device-integration/rest-client-examples-bundle/hello-rest-x509.md +++ b/content/device-integration/rest-client-examples-bundle/hello-rest-x509.md @@ -34,7 +34,7 @@ This will compile the project. If you don't have a valid certificate, you can generate one for testing purposes, following the instructions below. 1. Download the scripts from the [cumulocity-examples](https://github.com/SoftwareAG/cumulocity-examples/tree/develop/mqtt-client/scripts) repository. -2. Create a root self-signed certificate (execute the script *00createRootSelfSignedCertificate.sh*) and upload it to your tenant. You can do it via [the Device management application in the UI](/device-management-application/managing-device-data/#managing-trusted-certificates) or via [REST](https://{{< domain-c8y >}}/api/core/#tag/Tenant-API). +2. Create a root self-signed certificate (execute the script *00createRootSelfSignedCertificate.sh*) and upload it to your tenant. You can do it via [the Device Management application in the UI](/device-management-application/managing-device-data/#managing-trusted-certificates) or via [REST](https://{{< domain-c8y >}}/api/core/#tag/Tenant-API). 3. Create and sign the certificate (execute the script *01createSignedCertificate.sh*). 4. Move the certificates to keystore (execute the script *02moveCertificatesToKeystore.sh*). 5. Download the public server key from the respective environment and import it into JKS using this command: diff --git a/content/device-integration/rest-client-examples-bundle/hello-rest.md b/content/device-integration/rest-client-examples-bundle/hello-rest.md index 1427c72bbe..b67dd9955c 100644 --- a/content/device-integration/rest-client-examples-bundle/hello-rest.md +++ b/content/device-integration/rest-client-examples-bundle/hello-rest.md @@ -139,7 +139,7 @@ The response to that request will look like this: If you like to, you can repeat sending measurements. Before sending the request again, you should update the timestamp (value of attribute 'time') in order to create a time series. -Now you are done. Enter the Device management application in the {{< product-c8y-iot >}} UI, select your device on the "All devices" page and switch to the "Measurements" tab. Here you can see your measurement data. +Now you are done. Enter the Device Management application in the {{< product-c8y-iot >}} UI, select your device on the "All devices" page and switch to the "Measurements" tab. Here you can see your measurement data. If you do not see data, you might need to change the filter setting to, for example, "last week" to include the timestamp you used in your submitted measurement. diff --git a/content/device-management-application-card.md b/content/device-management-application-card.md index a1d7a4da22..d5a0230588 100644 --- a/content/device-management-application-card.md +++ b/content/device-management-application-card.md @@ -1,5 +1,5 @@ --- -title: Device management application +title: Device Management application icon: "c8y-icon c8y-icon-device-management" type: root layout: redirect @@ -13,4 +13,4 @@ outputs: - html --- -The Device management application enables you to manage and monitor devices and to control and troubleshoot devices remotely. +The Device Management application enables you to manage and monitor devices and to control and troubleshoot devices remotely. diff --git a/content/device-management-application/_index.html b/content/device-management-application/_index.html index 64a971a5bd..77632fe783 100644 --- a/content/device-management-application/_index.html +++ b/content/device-management-application/_index.html @@ -1,4 +1,4 @@ --- -title: Device management application +title: Device Management application layout: redirect --- diff --git a/content/device-management-application/connectivity.md b/content/device-management-application/connectivity.md index d96af752c6..571e4a98ed 100644 --- a/content/device-management-application/connectivity.md +++ b/content/device-management-application/connectivity.md @@ -7,11 +7,11 @@ sector: --- {{< c8y-admon-related >}} -* [Device management > Device integration > Fragment library > Connectivity](/device-integration/fragment-library/#connectivity) for details on the `c8y_Mobile` fragment used in managed objects. +* [Device Management > Device integration > Fragment library > Connectivity](/device-integration/fragment-library/#connectivity) for details on the `c8y_Mobile` fragment used in managed objects. * [Platform administration > {{< standard-tenant >}} administration > Changing settings > Connectivity](/standard-tenant/changing-settings/#connectivity) for information on how to change the connectivity settings via the UI. {{< /c8y-admon-related >}} -The Connectivity agent, which works from within the {{< product-c8y-iot >}} Device management application, provides basic information on mobile devices and additional connectivity details. +The Connectivity agent, which works from within the {{< product-c8y-iot >}} Device Management application, provides basic information on mobile devices and additional connectivity details. The {{< product-c8y-iot >}} platform integrates with the SIM connectivity platforms Comarch, Ericsson, Jasper and Kite. @@ -47,7 +47,7 @@ The following sections describe: * How to configure the [connectivity for the SIM provider](#configuring-the-connectivity-for-the-sim-provider) in your {{< product-c8y-iot >}} tenant. * How to [link SIMs and mobile devices](#linking-sims-and-mobile-devices). * Which information is shown in the [Connectivity tab](#connectivity-tab). -* How to [manage connectivity](#checking-connectivity) from the Device management application. +* How to [manage connectivity](#checking-connectivity) from the Device Management application. ### Setting up your Jasper Control Center account {#setting-up-your-jasper-control-center-account} @@ -94,7 +94,7 @@ A longer cache duration means less traffic to your SIM provider while a shorter ### Linking SIMs and mobile devices {#linking-sims-and-mobile-devices} -Switch to the Device management application and navigate to a device that is connected through a SIM card managed by the SIM provider of your choice. The device should have a **Connectivity** tab. If this tab is not shown, one of the following applies: +Switch to the Device Management application and navigate to a device that is connected through a SIM card managed by the SIM provider of your choice. The device should have a **Connectivity** tab. If this tab is not shown, one of the following applies: * Your user does not have permissions for Connectivity. * The device is not linked to a SIM card. diff --git a/content/device-management-application/grouping-devices-bundle/using-smart-groups.md b/content/device-management-application/grouping-devices-bundle/using-smart-groups.md index 03f2304270..1fb549f43b 100644 --- a/content/device-management-application/grouping-devices-bundle/using-smart-groups.md +++ b/content/device-management-application/grouping-devices-bundle/using-smart-groups.md @@ -16,7 +16,7 @@ helpcontent: Smart groups are groups dynamically constructed based on filtering criteria. This type of group can be used, for example, for bulk upgrades of devices of a certain type to a new software or firmware version. {{< c8y-admon-info >}} -Smart groups are only available in the Device management application and not visible in the Cockpit application. +Smart groups are only available in the Device Management application and not visible in the Cockpit application. {{< /c8y-admon-info >}} Smart groups can be created from the device list. diff --git a/content/device-management-application/home-dashboard.md b/content/device-management-application/home-dashboard.md index 40276835e2..f1bb947692 100644 --- a/content/device-management-application/home-dashboard.md +++ b/content/device-management-application/home-dashboard.md @@ -6,7 +6,7 @@ sector: - device_management --- -The Home screen of the Device management application is a dashboard which shows data for the tenant. +The Home screen of the Device Management application is a dashboard which shows data for the tenant. ![Home dashboard](/images/users-guide/DeviceManagement/device-management-home-screen.png) @@ -14,6 +14,6 @@ The data shown on the Home dashboard is shared by all users of the tenant. By de The Home dashboard can be edited and designed individually according to your needs. You can add, remove or change widgets which are displayed here. For details on editing a dashboard, refer to [Working with dashboards](/cockpit/working-with-dashboards/). -The Device management application dashboard works just like the Cockpit dashboard. +The Device Management application dashboard works just like the Cockpit dashboard. To reset the Home dashboard to its default, click **Restore dashboard** at the right of the top menu bar. diff --git a/content/device-management-application/managing-device-data.md b/content/device-management-application/managing-device-data.md index 1e6165a013..96e4415e79 100644 --- a/content/device-management-application/managing-device-data.md +++ b/content/device-management-application/managing-device-data.md @@ -10,12 +10,12 @@ sector: --- {{< c8y-admon-related >}} -* [Device management > Device integration > Fragment library > Firmware](/device-integration/fragment-library/#firmware) for details on the `c8y_Firmware` fragment used in managed objects. -* [Device management > Device integration > Fragment library > Software](/device-integration/fragment-library/#software) for details on legacy software management via the `c8y_SoftwareList` fragment, software updates via the `c8y_SoftwareUpdate` fragment and advanced software management via the `c8y_SupportedOperations` and `c8y_SupportedSoftwareTypes` fragments used in managed objects. -* [Device management > Device integration > Fragment library > Configuration](/device-integration/fragment-library/#configuration) for details on text-based configuration, file-based configuration and typed file-based configuration. +* [Device Management > Device integration > Fragment library > Firmware](/device-integration/fragment-library/#firmware) for details on the `c8y_Firmware` fragment used in managed objects. +* [Device Management > Device integration > Fragment library > Software](/device-integration/fragment-library/#software) for details on legacy software management via the `c8y_SoftwareList` fragment, software updates via the `c8y_SoftwareUpdate` fragment and advanced software management via the `c8y_SupportedOperations` and `c8y_SupportedSoftwareTypes` fragments used in managed objects. +* [Device Management > Device integration > Fragment library > Configuration](/device-integration/fragment-library/#configuration) for details on text-based configuration, file-based configuration and typed file-based configuration. * The [device credentials API](https://{{< domain-c8y >}}/api/core/#tag/Device-credentials) for REST API methods concerning device credentials. -* [Device management > Device integration > Fragment library > Device profile](/device-integration/fragment-library/#device-profile) for details on the `c8y_DeviceProfile` fragment used in managed objects. -* [Device management > Device integration > Device integration using MQTT > Device certificates](/device-integration/mqtt/#device-certificates) for information on device certificates in the context of MQTT. +* [Device Management > Device integration > Fragment library > Device profile](/device-integration/fragment-library/#device-profile) for details on the `c8y_DeviceProfile` fragment used in managed objects. +* [Device Management > Device integration > Device integration using MQTT > Device certificates](/device-integration/mqtt/#device-certificates) for information on device certificates in the context of MQTT. {{< /c8y-admon-related >}} The Device Management application provides features that support you in efficiently managing your devices. diff --git a/content/device-management-application/managing-device-types.md b/content/device-management-application/managing-device-types.md index e2f56b0431..6a8a45632a 100644 --- a/content/device-management-application/managing-device-types.md +++ b/content/device-management-application/managing-device-types.md @@ -18,7 +18,7 @@ helpcontent: {{< c8y-admon-related >}} * [Getting started > Technical concepts > Interfacing devices](/concepts/interfacing-devices/) for information on the concepts relevant for interfacing IoT devices and other IoT-related data sources with {{< product-c8y-iot >}}. -* [Device management > Protocol integration](/protocol-integration/) for a list of protocols, parameters and network connectivity options for devices. +* [Device Management > Protocol integration](/protocol-integration/) for a list of protocols, parameters and network connectivity options for devices. {{< /c8y-admon-related >}} To process data from various device types, {{< product-c8y-iot >}} uses device protocols which are stored in a database. diff --git a/content/device-management-application/monitoring-and-controlling-devices.md b/content/device-management-application/monitoring-and-controlling-devices.md index 068b8b620a..52069e5b7c 100644 --- a/content/device-management-application/monitoring-and-controlling-devices.md +++ b/content/device-management-application/monitoring-and-controlling-devices.md @@ -10,9 +10,9 @@ sector: --- {{< c8y-admon-related >}} -* [Device management > Device integration > Fragment library > Device availability](/device-integration/fragment-library/#device-availability) for details on the `c8y_RequiredAvailability`, `c8y_UnavailabilityAlarm`, `c8y_Availability` and `c8y_Connection` fragments used in managed objects. +* [Device Management > Device integration > Fragment library > Device availability](/device-integration/fragment-library/#device-availability) for details on the `c8y_RequiredAvailability`, `c8y_UnavailabilityAlarm`, `c8y_Availability` and `c8y_Connection` fragments used in managed objects. * The [alarms API](https://{{< domain-c8y >}}/api/core/#tag/Alarms) for REST API methods concerning alarms. -* [Device management > Device integration > Fragment library > Alarms](/device-integration/fragment-library/#alarms) for details on how to raise and clear alarms. +* [Device Management > Device integration > Fragment library > Alarms](/device-integration/fragment-library/#alarms) for details on how to raise and clear alarms. * The [operations API](https://{{< domain-c8y >}}/api/core/#tag/Operations) for REST API methods concerning operations. * The [bulk operations API](https://{{< domain-c8y >}}/api/core/#tag/Bulk-operations) for REST API methods concerning bulk operations. {{< /c8y-admon-related >}} diff --git a/content/device-management-application/monitoring-device-services.md b/content/device-management-application/monitoring-device-services.md index 7e5f5afc8f..8dd51f32d2 100644 --- a/content/device-management-application/monitoring-device-services.md +++ b/content/device-management-application/monitoring-device-services.md @@ -8,10 +8,10 @@ sector: {{< c8y-admon-related >}} * The [alarms API](https://{{< domain-c8y >}}/api/core/#tag/Alarms) for REST API methods concerning alarms. -* [Device management > Device integration > Fragment library > Alarms](/device-integration/fragment-library/#alarms) for details on how to raise and clear alarms. +* [Device Management > Device integration > Fragment library > Alarms](/device-integration/fragment-library/#alarms) for details on how to raise and clear alarms. * The [events API](https://{{< domain-c8y >}}/api/core/#tag/Events) for REST API methods concerning events. * The [measurements API](https://{{< domain-c8y >}}/api/core/#tag/Measurements) for REST API methods concerning measurements. -* [Device management > Device integration > Fragment library > Measurements](/device-integration/fragment-library/#measurements) for details on measurements. +* [Device Management > Device integration > Fragment library > Measurements](/device-integration/fragment-library/#measurements) for details on measurements. {{< /c8y-admon-related >}} The Device Management application lets you monitor the data that your devices send about the services they are running. diff --git a/content/device-management-application/registering-devices.md b/content/device-management-application/registering-devices.md index 8a67bc0833..ce8cf6e9a9 100644 --- a/content/device-management-application/registering-devices.md +++ b/content/device-management-application/registering-devices.md @@ -39,9 +39,9 @@ helpcontent: --- {{< c8y-admon-related >}} -* [Device management > Protocol integration](/protocol-integration/) for details on registering devices using various standard protocol types. -* [Device management > Device integration](/device-integration/introduction) for step-by-step instructions on registering devices. -* [Device management > Device integration > Device integration using REST](/device-integration/device-integration-rest/) for a detailed descriptions on device integration via REST. +* [Device Management > Protocol integration](/protocol-integration/) for details on registering devices using various standard protocol types. +* [Device Management > Device integration](/device-integration/introduction) for step-by-step instructions on registering devices. +* [Device Management > Device integration > Device integration using REST](/device-integration/device-integration-rest/) for a detailed descriptions on device integration via REST. * The [New device requests API](https://{{< domain-c8y >}}/api/core/#tag/New-device-requests) for REST API methods concerning the creation of new devices. {{< /c8y-admon-related >}} diff --git a/content/device-management-application/smartrest-templates.md b/content/device-management-application/smartrest-templates.md index bcd2aa6bae..c060515d0b 100644 --- a/content/device-management-application/smartrest-templates.md +++ b/content/device-management-application/smartrest-templates.md @@ -24,8 +24,8 @@ SmartREST templates are a collection of request and response templates used to c To ease the device integration, {{< product-c8y-iot >}} supports static templates that can be used without the need for creating your own templates. These templates focus only on the most commonly used messages for device management. For further information on static templates, refer to the [MQTT static templates](/smartrest/mqtt-static-templates). {{< c8y-admon-related >}} -* [Device management > SmartREST > SmartREST 2.0](/smartrest/smartrest-two/) for details on the SmartREST protocol, the data format used, as well as the anatomy and registration of SmartREST templates. -* [Device management > Device integration > Device integration using MQTT](/device-integration/mqtt/) for information on integrating devices via MQTT. +* [Device Management > SmartREST > SmartREST 2.0](/smartrest/smartrest-two/) for details on the SmartREST protocol, the data format used, as well as the anatomy and registration of SmartREST templates. +* [Device Management > Device integration > Device integration using MQTT](/device-integration/mqtt/) for information on integrating devices via MQTT. {{< /c8y-admon-related >}} Open the **SmartREST template** page from the **Device Types** menu in the navigator. diff --git a/content/device-management-application/viewing-device-details.md b/content/device-management-application/viewing-device-details.md index 80712838af..6827431ec3 100644 --- a/content/device-management-application/viewing-device-details.md +++ b/content/device-management-application/viewing-device-details.md @@ -203,7 +203,7 @@ Only one Y-axis is rendered if the measurements belong to the same series. To see detailed information about the measured values, hover over the chart. A tooltip will be displayed with detailed information on the measurement next to your cursor (the tooltip will "snap" to the closest measurement). {{< c8y-admon-info >}} -We recommend you to have max. 20 series per measurement for optimal performance and readability of a single graph in Device management (the graph displays all available series). If you need to display only a few series from the measurement, we advise you to use Data explorer in Cockpit where you can select series to be shown in the graph. +We recommend you to have max. 20 series per measurement for optimal performance and readability of a single graph in Device Management (the graph displays all available series). If you need to display only a few series from the measurement, we advise you to use Data explorer in Cockpit where you can select series to be shown in the graph. {{< /c8y-admon-info >}} **Time range and aggregation** diff --git a/content/dtm/asset-hierarchy-bundle/creating-assets-ui.md b/content/dtm/asset-hierarchy-bundle/creating-assets-ui.md index ea9f1e016a..9afcb59b11 100644 --- a/content/dtm/asset-hierarchy-bundle/creating-assets-ui.md +++ b/content/dtm/asset-hierarchy-bundle/creating-assets-ui.md @@ -79,7 +79,7 @@ When you create a new asset you have the option of assigning one or more devices ![Assigning devices to an asset](/images/dtm/assets/dtm-assets-assign-devices.png) -To add a new device, add it through the Device management application. +To add a new device, add it through the Device Management application. Refer to [Registering devices](/device-management-application/registering-devices/) for further information. {{< c8y-admon-info>}} diff --git a/content/get-familiar-with-the-ui/gui-features.md b/content/get-familiar-with-the-ui/gui-features.md index f86cf66fd5..d5d3ea7836 100644 --- a/content/get-familiar-with-the-ui/gui-features.md +++ b/content/get-familiar-with-the-ui/gui-features.md @@ -189,4 +189,4 @@ You will only see such changes in the navigator of the application, in which you **Example** -If you unassign a device from a group in the Device management application it is immediately removed from the group in the navigator of your current application. However, if you have another window open with another Device management application, you won't see the changes, but will only see the changes after a refresh or another request (expanding a group in the navigator for example). +If you unassign a device from a group in the Device Management application it is immediately removed from the group in the navigator of your current application. However, if you have another window open with another Device Management application, you won't see the changes, but will only see the changes after a refresh or another request (expanding a group in the navigator for example). diff --git a/content/get-familiar-with-the-ui/ui-introduction.md b/content/get-familiar-with-the-ui/ui-introduction.md index 4f64533f2c..39247cfd01 100644 --- a/content/get-familiar-with-the-ui/ui-introduction.md +++ b/content/get-familiar-with-the-ui/ui-introduction.md @@ -15,5 +15,5 @@ In the entire documentation you find detailed description on the usage of the re Specifically, check out the following sections: - [Platform administration > {{< standard-tenant >}} administration](/standard-tenant/) for details on the Administration application. -- [Device management > Device management application](/device-management-application/) for details on the Device management application. +- [Device Management > Device Management application](/device-management-application/) for details on the Device Management application. - [Application enablement & solutions > Cockpit](/cockpit/) for details on the Cockpit application. diff --git a/content/glossary/d.md b/content/glossary/d.md index 846ce3559d..86cffd145f 100644 --- a/content/glossary/d.md +++ b/content/glossary/d.md @@ -44,7 +44,7 @@ Devices are a special type of [asset](/glossary/a/#asset). They can constitute a The Device Management application is one of the default applications of {{< product-c8y-iot >}}. The Device Management application provides functionalities for connecting, managing and monitoring devices and allows to control and troubleshoot devices remotely. -For details see [Device management > Device management application](/device-management-application/). +For details see [Device Management > Device Management application](/device-management-application/). ### Device protocol {#device-protocol} @@ -52,7 +52,7 @@ For details see [Device management > Device management application](/device-mana A device protocol defines how data from a specific device type should be transferred into the {{< product-c8y-iot >}} platform. It contains protocol-specific information about where the data is obtained from, how to transform it, and how to store it in {{< product-c8y-iot >}}. The definition of the device protocol differs based on the underlying protocol used by the device (for example, Modbus, LoRa, OPC UA or LWM2M). -For details see [Device management > Protocol integration](/protocol-integration/). +For details see [Device Management > Protocol integration](/protocol-integration/). ### Digital twin {#digital-twin} diff --git a/content/glossary/l.md b/content/glossary/l.md index 8342cb3120..999b570285 100644 --- a/content/glossary/l.md +++ b/content/glossary/l.md @@ -10,4 +10,4 @@ sector: Lightweight M2M (LWM2M) is a traffic and resource-optimized protocol to remotely manage IoT devices. {{< product-c8y-iot >}} provides support for easily connecting any LWM2M device to the platform. -For details see [Device management > Protocol integration > LWM2M](/protocol-integration/lwm2m). +For details see [Device Management > Protocol integration > LWM2M](/protocol-integration/lwm2m). diff --git a/content/glossary/m.md b/content/glossary/m.md index a27aa98878..1d3f60f9c9 100644 --- a/content/glossary/m.md +++ b/content/glossary/m.md @@ -59,7 +59,7 @@ The behavior of a block inside a model does not depend on other blocks. There ca {{< product-c8y-iot >}} supports MQTT, an OASIS standard messaging protocol, for device integration. -For details see [Device management > Device integration > Device integration using MQTT](/device-integration/mqtt). +For details see [Device Management > Device integration > Device integration using MQTT](/device-integration/mqtt). ### Multi-tenancy {#multi-tenancy} diff --git a/content/glossary/o.md b/content/glossary/o.md index 2e6526ebc0..0034bf5fa7 100644 --- a/content/glossary/o.md +++ b/content/glossary/o.md @@ -20,7 +20,7 @@ OPC Unified Architecture (OPC UA) is a standard to enable the communication betw One component of the OPC UA integration in {{< product-c8y-iot >}} is the OPC UA device gateway. The OPC UA device gateway is a stand-alone Java program that communicates with OPC UA server(s) and the {{< product-c8y-iot >}} platform. It stores data into the {{< product-c8y-iot >}} database via REST. The gateway must be registered as {{< product-c8y-iot >}} device. -For details see [Device management > Protocol integration > OPC UA](/protocol-integration/opcua). +For details see [Device Management > Protocol integration > OPC UA](/protocol-integration/opcua). ### Operations {#operations} diff --git a/content/glossary/p.md b/content/glossary/p.md index 763589c795..535d75c42e 100644 --- a/content/glossary/p.md +++ b/content/glossary/p.md @@ -23,7 +23,7 @@ See also [General Availability](/glossary/g/#ga) and [Public Preview](/glossary/ ### Product area {#product-area} -In the change logs (or release notes for yearly releases respectively) changes can be filtered for various parameters one of which is the product area. The product area is a high-level functional area, for example, "Device Management & connectivity". +In the change logs (or release notes for yearly releases respectively) changes can be filtered for various parameters one of which is the product area. The product area is a high-level functional area, for example, "Device Management & Connectivity". See also [Components](/glossary/c/#components). diff --git a/content/microservice-sdk/java-bundle/ip-tracker-microservice.md b/content/microservice-sdk/java-bundle/ip-tracker-microservice.md index 4404dd5272..8b189ae583 100644 --- a/content/microservice-sdk/java-bundle/ip-tracker-microservice.md +++ b/content/microservice-sdk/java-bundle/ip-tracker-microservice.md @@ -139,7 +139,7 @@ BODY: You will get the ID of your managed object in the response. Assign this ID to the `"tracker.id"` key in your _cumulocity.json_ file. -On the {{< product-c8y-iot >}} platform, navigate to **Devices** > **All devices** in the Device management application to verify that your device has been created and its location is displayed on the map. +On the {{< product-c8y-iot >}} platform, navigate to **Devices** > **All devices** in the Device Management application to verify that your device has been created and its location is displayed on the map. ![Microservice tracking](/images/microservices-sdk/ms-tracking-newdevice.png) @@ -436,7 +436,7 @@ The response will be similar to: Using the endpoint location/locations will return five stored events by default. You can use the `max` parameter to specify a higher number. -In the Device management application, navigate to **Devices** > **All devices** and locate your microservice tracker. +In the Device Management application, navigate to **Devices** > **All devices** and locate your microservice tracker. Under **Tracking** you will see a map with the tracked locations. You can also develop your own web application and customize a map widget. Refer to [Application library](/web/libraries/#application-library). diff --git a/content/oee/oee-faq-bundle/dashboards.md b/content/oee/oee-faq-bundle/dashboards.md index 7886631b7c..73e200d421 100644 --- a/content/oee/oee-faq-bundle/dashboards.md +++ b/content/oee/oee-faq-bundle/dashboards.md @@ -14,7 +14,7 @@ In the example below the selected calculation interval is '1 minute'. There are ### What do alarms in a Machine Dashboard mean? {#what-do-alarms-in-a-machine-dashboard-mean} -If an alarm occurs in an OEE Machine Dashboard, this indicates that the mapping must be revised and adapted again. If this has been done, no further alarms should occur. Nevertheless, it is recommended to clear the alarm in the device details of the profile in the {{< product-c8y-iot >}} Device management application. This is the only way, the parameters displayed in the alarm will be renewed if a similar alarm occurs. The time stamp is also updated automatically without further action. +If an alarm occurs in an OEE Machine Dashboard, this indicates that the mapping must be revised and adapted again. If this has been done, no further alarms should occur. Nevertheless, it is recommended to clear the alarm in the device details of the profile in the {{< product-c8y-iot >}} Device Management application. This is the only way, the parameters displayed in the alarm will be renewed if a similar alarm occurs. The time stamp is also updated automatically without further action. ![Dashboard alarm](/images/oee/faq/faq-dashboard-alarm.png) diff --git a/content/oee/oee-faq-bundle/platform.md b/content/oee/oee-faq-bundle/platform.md index 149660aa0d..4261000fcb 100644 --- a/content/oee/oee-faq-bundle/platform.md +++ b/content/oee/oee-faq-bundle/platform.md @@ -38,8 +38,8 @@ For more details on how to correctly set up property names and series names see ### Where do I find the calculated OEE measurements of a profile in the platform? {#where-do-i-find-the-calculated-oee-measurements-of-a-profile-in-the-platform} -1. Go to the parent machine in the Device management application and open the child devices of the machine. +1. Go to the parent machine in the Device Management application and open the child devices of the machine. 2. The profile is a child device of the machine. You can identify it via the profile name. If the profile name is "XYZ" for example, then the child device will be called "XYZ[OEE calculation profile]". 3. Navigate to the **Measurements tab** of the child device. You should see the OEE measurements. -Alternatively, you can also use the built-in search in the Device management application to search for the name of the profile. +Alternatively, you can also use the built-in search in the Device Management application to search for the name of the profile. diff --git a/content/protocol-integration/cloud-fieldbus-bundle/connecting-fieldbus.md b/content/protocol-integration/cloud-fieldbus-bundle/connecting-fieldbus.md index 975258dfd5..c6db45f070 100644 --- a/content/protocol-integration/cloud-fieldbus-bundle/connecting-fieldbus.md +++ b/content/protocol-integration/cloud-fieldbus-bundle/connecting-fieldbus.md @@ -14,7 +14,7 @@ To connect a Modbus/RTU device, follow these steps: 1. Physically connect the Modbus/RTU device through a RS-485 or RS-232 cable to the terminal. 2. Assign the device a unique Modbus address according to the instructions provided with the Modbus device (for example by setting a jumper on the device). 3. Check the serial communication settings of the device according to the instructions provided with the Modbus device (that is, baud rates and communication protocol). These must match with all devices on the bus. -4. In the Device management application, click **All devices** in the **Devices** menu in the navigator. In the device list, select the terminal and switch to the **Modbus** tab. +4. In the Device Management application, click **All devices** in the **Devices** menu in the navigator. In the device list, select the terminal and switch to the **Modbus** tab. 5. Change the communication settings shown in the **Serial communication** section to match the settings on the bus, if needed. 6. Change the transmit rate and the polling rate according to your requirements. The transmit rate is the frequency where measurements are sent to {{< product-c8y-iot >}}. The polling rate is the frequency at which the Modbus devices are polled for changes. 7. Click **Save** to save your settings. @@ -35,7 +35,7 @@ To connect a Modbus/TCP device, follow these steps: 1. Make sure that the Modbus/TCP device is connected to the terminal, that is, directly through an Ethernet cable or through a switch. If you are using a Modbus gateway, configure the gateway in a way it can communicate with the Modbus devices behind the gateway. 2. Check the network settings of the device using the instructions provided with the device. -3. In the Device management application, click **All devices** in the **Devices** menu in the navigator. In the device list, select the terminal and switch to the **Network** tab. Verify that the LAN settings of the terminal match the settings of the device so that TCP communication can be established. +3. In the Device Management application, click **All devices** in the **Devices** menu in the navigator. In the device list, select the terminal and switch to the **Network** tab. Verify that the LAN settings of the terminal match the settings of the device so that TCP communication can be established. 4. Switch to the **Modbus** tab. 5. Change the transmit rate and the polling rate according to your requirements. The transmit rate is the frequency at which measurements are sent to {{< product-c8y-iot >}}. The polling rate is the frequency at which the Modbus devices are polled for changes. 6. Click **Save** to save your settings. @@ -60,7 +60,7 @@ To connect a CAN device, follow these steps: 1. Physically connect the CAN device to the terminal. 2. Check the serial communication baud rate of the device according to the instructions provided with the device. These must match all devices on the bus. -3. In the Device management application, click **All devices** in the **Devices** menu in the navigator. In the device list, select the terminal and switch to the **CAN Bus** tab. +3. In the Device Management application, click **All devices** in the **Devices** menu in the navigator. In the device list, select the terminal and switch to the **CAN Bus** tab. 4. Change the baud rate setting shown in the section **CAN Bus communication** to match the settings on the bus, if needed. 5. Change the transmit rate according to your requirements. The transmit rate is the frequency where measurements are sent to {{< product-c8y-iot >}}. 6. Click **Save** to save your settings. @@ -84,7 +84,7 @@ Connecting Profibus devices slightly differs from the regular plug & play approa To connect a Profibus device, follow these steps: 1. Physically wire the Profibus device to the terminal. -2. In the Device management application, click **All devices** in the **Devices** menu in the navigator. In the device list, select the terminal and switch to the **Profibus** tab. +2. In the Device Management application, click **All devices** in the **Devices** menu in the navigator. In the device list, select the terminal and switch to the **Profibus** tab. 3. The baud rate is automatically detected by the gateway and it is displayed here. 4. Change the transmit rate according to your requirements. The transmit rate is the interval at which measurements are sent to {{< product-c8y-iot >}}. 5. Set the device address of the terminal. diff --git a/content/protocol-integration/lora-actility-bundle/deprovisioning-lora-devices.md b/content/protocol-integration/lora-actility-bundle/deprovisioning-lora-devices.md index 4b4d1cfd3b..aaa72cf998 100644 --- a/content/protocol-integration/lora-actility-bundle/deprovisioning-lora-devices.md +++ b/content/protocol-integration/lora-actility-bundle/deprovisioning-lora-devices.md @@ -6,7 +6,7 @@ layout: redirect You can deprovision a LoRa device in the ThingPark platform. This means that the device will no longer be connected to the network. Its history data will still be available in {{< product-c8y-iot >}}, but the device will be deleted in ThingPark. -To deprovision a device, navigate to the respective device in the Device management application under **All devices**. Click **More** in the top right and select **Deprovision device**. +To deprovision a device, navigate to the respective device in the Device Management application under **All devices**. Click **More** in the top right and select **Deprovision device**. ![Deprovision device](/images/device-protocols/lora-actility/lora-devices-deprovision.png) diff --git a/content/protocol-integration/lora-actility-bundle/introduction.md b/content/protocol-integration/lora-actility-bundle/introduction.md index dfe7966819..0ebf82923e 100644 --- a/content/protocol-integration/lora-actility-bundle/introduction.md +++ b/content/protocol-integration/lora-actility-bundle/introduction.md @@ -6,7 +6,7 @@ layout: redirect {{< product-c8y-iot >}} can interface with LoRa devices through Actility's ThingPark Wireless, Enterprise or Community edition. You can: -* Provision and deprovision LoRa devices easily using the {{< product-c8y-iot >}} Device management application. No interaction in the ThingPark user interface is required. +* Provision and deprovision LoRa devices easily using the {{< product-c8y-iot >}} Device Management application. No interaction in the ThingPark user interface is required. * Decode upstream payload packets using a web-based user interface. * Debug and postprocess raw device data through {{< product-c8y-iot >}} events. * Send downstream data to the device using {{< product-c8y-iot >}} operations. diff --git a/content/protocol-integration/lora-actility-bundle/lora-creating-device-protocols.md b/content/protocol-integration/lora-actility-bundle/lora-creating-device-protocols.md index d2e70b76c8..4813427625 100644 --- a/content/protocol-integration/lora-actility-bundle/lora-creating-device-protocols.md +++ b/content/protocol-integration/lora-actility-bundle/lora-creating-device-protocols.md @@ -18,7 +18,7 @@ Device protocol mapping only supports decoding for fixed byte positions based on The length for the device payload parts, which is set in the **Number of bits** field, can be maximum 32 bits (4 bytes). {{< /c8y-admon-info >}} -In order to create a device protocol, navigate to the Device management application and select **Device protocols** in the **Device types** menu in the navigator. You can either import an existing device protocol or create a new one or use the device protocols created by an LPWAN custom codec microservice. +In order to create a device protocol, navigate to the Device Management application and select **Device protocols** in the **Device types** menu in the navigator. You can either import an existing device protocol or create a new one or use the device protocols created by an LPWAN custom codec microservice. ### Importing a predefined device protocol {#importing-a-predefined-device-protocol} diff --git a/content/protocol-integration/lora-actility-bundle/lora-sending-operations.md b/content/protocol-integration/lora-actility-bundle/lora-sending-operations.md index b34e5a9de4..65c11d0f6c 100644 --- a/content/protocol-integration/lora-actility-bundle/lora-sending-operations.md +++ b/content/protocol-integration/lora-actility-bundle/lora-sending-operations.md @@ -6,7 +6,7 @@ layout: redirect If a LoRa device supports receiving hexadecimal commands, you can send them using shell operations. Notice that these commands are not serial monitor commands. -In order to send an operation, navigate to the device you want to send an operation to in the Device management application under **All devices**. Switch to the **Shell** tab. +In order to send an operation, navigate to the device you want to send an operation to in the Device Management application under **All devices**. Switch to the **Shell** tab. In the following screenshot you can find some examples of a device protocol's predefined commands and their format. diff --git a/content/protocol-integration/lora-actility-bundle/registering-lora-devices.md b/content/protocol-integration/lora-actility-bundle/registering-lora-devices.md index 7f90746da8..68817bb037 100644 --- a/content/protocol-integration/lora-actility-bundle/registering-lora-devices.md +++ b/content/protocol-integration/lora-actility-bundle/registering-lora-devices.md @@ -5,7 +5,7 @@ layout: redirect --- -To register a LoRa device in {{< product-c8y-iot >}} navigate to **Devices** > **Registration** in the Device management application, click **Register device** at the top right and select **Single device registration** > **Actility LoRa** from the dropdown. +To register a LoRa device in {{< product-c8y-iot >}} navigate to **Devices** > **Registration** in the Device Management application, click **Register device** at the top right and select **Single device registration** > **Actility LoRa** from the dropdown. ![Register devices](/images/device-protocols/lora-actility/lora-selection.png) @@ -34,7 +34,7 @@ The provision status is shown under **Device data** in the **Info** tab of the d ![Device data](/images/device-protocols/lora-actility/lora-devices-devicedata.png) -For more information on viewing and managing your connected devices, also refer to the [Device management application](/device-management-application). +For more information on viewing and managing your connected devices, also refer to the [Device Management application](/device-management-application). In order to migrate the device from one LNS Connection to another, the device must be re-registered. Navigate to the **LPWAN** tab of the Device. diff --git a/content/protocol-integration/lora-loriot-bundle/device-registration-via-platform.md b/content/protocol-integration/lora-loriot-bundle/device-registration-via-platform.md index 505ee3182b..24758291f2 100644 --- a/content/protocol-integration/lora-loriot-bundle/device-registration-via-platform.md +++ b/content/protocol-integration/lora-loriot-bundle/device-registration-via-platform.md @@ -48,7 +48,7 @@ If there are devices associated with the connection, an error message appears, s ### Loriot device registration {#loriot-device-registration} -To register a Loriot device in {{< product-c8y-iot >}} navigate to **Devices** > **Registration** in the Device management application, click **Register device** at the top right and select **Single device registration** > **LORIOT LoRa** from the dropdown. +To register a Loriot device in {{< product-c8y-iot >}} navigate to **Devices** > **Registration** in the Device Management application, click **Register device** at the top right and select **Single device registration** > **LORIOT LoRa** from the dropdown. ![Register devices](/images/device-protocols/lora-loriot/loriot-selection.png) @@ -72,7 +72,7 @@ Click **Register** to submit the device registration request and create the devi You can verify that the device is connected by incoming events. Click on a device and open its **Events** tab. All events related to this device are listed. -For more information on viewing and managing your connected devices, also refer to the [Device management application](/device-management-application/). +For more information on viewing and managing your connected devices, also refer to the [Device Management application](/device-management-application/). In order to migrate the device from one LNS connection to another, the device must be re-registered: diff --git a/content/protocol-integration/lora-loriot-bundle/loriot-creating-device-protocols.md b/content/protocol-integration/lora-loriot-bundle/loriot-creating-device-protocols.md index a0db2b27c1..5733802a0a 100644 --- a/content/protocol-integration/lora-loriot-bundle/loriot-creating-device-protocols.md +++ b/content/protocol-integration/lora-loriot-bundle/loriot-creating-device-protocols.md @@ -14,7 +14,7 @@ Device protocol mapping only supports decoding for fixed byte positions based on The length for the device payload parts, which is set in the **Number of bits** field, can be maximum 32 bits (4 bytes). {{< /c8y-admon-info >}} -In order to create a device protocol, navigate to the Device management application and select **Device protocols** in the **Device types** menu in the navigator. You can either import an existing device protocol or create a new one. +In order to create a device protocol, navigate to the Device Management application and select **Device protocols** in the **Device types** menu in the navigator. You can either import an existing device protocol or create a new one. ### Importing a predefined device protocol {#importing-a-predefined-device-protocol} diff --git a/content/protocol-integration/lora-loriot-bundle/loriot-sending-operations.md b/content/protocol-integration/lora-loriot-bundle/loriot-sending-operations.md index ef55823615..cf9522f2d6 100644 --- a/content/protocol-integration/lora-loriot-bundle/loriot-sending-operations.md +++ b/content/protocol-integration/lora-loriot-bundle/loriot-sending-operations.md @@ -6,7 +6,7 @@ layout: redirect If a Loriot device supports hexadecimal commands, you can send them using shell operations. Notice that these commands are not serial monitor commands. -In order to send an operation, navigate to the device you want to send an operation to in the Device management application under **All devices**. Switch to the **Shell** tab. +In order to send an operation, navigate to the device you want to send an operation to in the Device Management application under **All devices**. Switch to the **Shell** tab. In the following screenshot you can find some examples of a device protocol's predefined commands and their format: diff --git a/content/protocol-integration/lpwan-custom-codec-bundle/deploying-sample-codec-microservice.md b/content/protocol-integration/lpwan-custom-codec-bundle/deploying-sample-codec-microservice.md index e7747619ce..45e7c9b59f 100644 --- a/content/protocol-integration/lpwan-custom-codec-bundle/deploying-sample-codec-microservice.md +++ b/content/protocol-integration/lpwan-custom-codec-bundle/deploying-sample-codec-microservice.md @@ -9,9 +9,9 @@ Steps to build the example codec `lora-codec-lansitec` microservice. 1. Clone the https://github.com/SoftwareAG/cumulocity-examples.git repository. 2. Build the microservice using `mvn clean install`. This creates a ZIP file of the lanitec codec microservice. 3. Deploy the microservice by uploading the ZIP file using the {{< product-c8y-iot >}} Administration UI. -4. Open the Device management application. Under **Device protocols**, you should now see the device protocols with type "lpwan" created by the lansitec codec microservice. +4. Open the Device Management application. Under **Device protocols**, you should now see the device protocols with type "lpwan" created by the lansitec codec microservice. -The image below shows the device protocols option in the Device management application. +The image below shows the device protocols option in the Device Management application. ![Device Protocols Page](/images/device-protocols/lpwan-custom-codec/lpwan-device-protocols-page.png) diff --git a/content/protocol-integration/lwm2m-bundle/device-details.md b/content/protocol-integration/lwm2m-bundle/device-details.md index d5f8af8454..3948b6e0df 100644 --- a/content/protocol-integration/lwm2m-bundle/device-details.md +++ b/content/protocol-integration/lwm2m-bundle/device-details.md @@ -5,7 +5,7 @@ layout: redirect --- {{< c8y-admon-info >}} -In the Device management application, you can view all details of a device. The following details are specific to LWM2M devices. For information on general details refer to [Viewing device details](/device-management-application/viewing-device-details) in the Device management section. +In the Device Management application, you can view all details of a device. The following details are specific to LWM2M devices. For information on general details refer to [Viewing device details](/device-management-application/viewing-device-details) in the Device Management section. {{< /c8y-admon-info >}} ### Objects {#objects} diff --git a/content/protocol-integration/lwm2m-bundle/device-protocols.md b/content/protocol-integration/lwm2m-bundle/device-protocols.md index b170d7ce2c..381d12ad55 100644 --- a/content/protocol-integration/lwm2m-bundle/device-protocols.md +++ b/content/protocol-integration/lwm2m-bundle/device-protocols.md @@ -5,7 +5,7 @@ layout: redirect --- To process data from LWM2M devices, {{< product-c8y-iot >}} uses device protocols. -Device protocols are accessible through the **Devices Types** menu in the Device management application. For details on the general usage, see [Managing device types](/device-management-application/managing-device-types). +Device protocols are accessible through the **Devices Types** menu in the Device Management application. For details on the general usage, see [Managing device types](/device-management-application/managing-device-types). ### Creating LWM2M device protocols {#creating-lwm2m-device-protocols} @@ -13,7 +13,7 @@ Once you have registered a device, you can manage LWM2M device protocols. Each p To add a new LWM2M device protocol follow these steps: -1. In the Device management application, move to the **Device protocol** page. +1. In the Device Management application, move to the **Device protocol** page. 2. Click **Add device protocol** in the top menu bar. 3. In the upcoming dialog select **LWM2M** as device protocol type. 4. Next, upload an appropriate DDF or XML file. DDF or XML files describe the data provided by your device. They are typically provided by the manufacturer or by standards bodies such as IPSO. There are also 3 "special" device protocols (DDF files) for standard OMA objects: 6 (location tracking), 5 (firmware update) and 3 (device information). If these files are not uploaded, then neither location tracking nor firmware updates will work. By default, the LWM2M agent adds mappings to these objects and knows how to "handle" their information without any additional configuration. The XML schema used by LWM2M can be found at [http://www.openmobilealliance.org/tech/profiles/LWM2M.xsd](http://www.openmobilealliance.org/tech/profiles/LWM2M.xsd).
diff --git a/content/protocol-integration/lwm2m-bundle/registering-lwm2m-devices.md b/content/protocol-integration/lwm2m-bundle/registering-lwm2m-devices.md index 6b638284b0..ae30d72a2e 100644 --- a/content/protocol-integration/lwm2m-bundle/registering-lwm2m-devices.md +++ b/content/protocol-integration/lwm2m-bundle/registering-lwm2m-devices.md @@ -17,7 +17,7 @@ You can register a LWM2M device in {{< product-c8y-iot >}} in two ways: ### Single device registration {#single-device-registration} -To register a LWM2M device in {{< product-c8y-iot >}} navigate to **Devices** > **Registration** in the Device management application, click **Register device** at the top right and select **Single device registration** > **LWM2M** from the dropdown. +To register a LWM2M device in {{< product-c8y-iot >}} navigate to **Devices** > **Registration** in the Device Management application, click **Register device** at the top right and select **Single device registration** > **LWM2M** from the dropdown. The LWM2M device registration wizard has four steps: * **Device** - configuration of globally unique device identifier. @@ -36,7 +36,7 @@ The UI will display a confirmation message. If there is a number of devices to be registered at the same time, it is more convenient to use bulk device registration. -To register the LWM2M devices in {{< product-c8y-iot >}}, navigate to **Devices** > **Registration** in the Device management application, click **Register device** at the top right and select **Bulk device registration** > **LWM2M** from the dropdown. +To register the LWM2M devices in {{< product-c8y-iot >}}, navigate to **Devices** > **Registration** in the Device Management application, click **Register device** at the top right and select **Bulk device registration** > **LWM2M** from the dropdown. Upload a CSV file with the registration data in the resulting bulk registration dialog. The dialog also contains CSV template links. Refer to [Device settings](#device-settings), [Security settings](#security-settings), diff --git a/content/protocol-integration/sigfox-bundle/device-protocols.md b/content/protocol-integration/sigfox-bundle/device-protocols.md index d7c47fb6d3..a8108ef02a 100644 --- a/content/protocol-integration/sigfox-bundle/device-protocols.md +++ b/content/protocol-integration/sigfox-bundle/device-protocols.md @@ -18,7 +18,7 @@ Device protocol mapping only supports decoding for fixed byte positions based on The length for the device payload parts, which is set in the **Number of bits** field, can be maximum 32 bits (4 bytes). {{< /c8y-admon-info >}} -To create device protocols, select **Device protocols** in the **Device types** menu in the navigator of the Device management application. You can either import an existing device protocol or create a new one. +To create device protocols, select **Device protocols** in the **Device types** menu in the navigator of the Device Management application. You can either import an existing device protocol or create a new one. ### Importing a device protocol {#importing-a-device-protocol} diff --git a/content/protocol-integration/sigfox-bundle/introduction.md b/content/protocol-integration/sigfox-bundle/introduction.md index d59847fddf..e9a7fb8822 100644 --- a/content/protocol-integration/sigfox-bundle/introduction.md +++ b/content/protocol-integration/sigfox-bundle/introduction.md @@ -6,7 +6,7 @@ layout: redirect {{< product-c8y-iot >}} can interface with Sigfox devices through the Sigfox Cloud. You can: -- Provision Sigfox devices easily using {{< product-c8y-iot >}} Device management application. +- Provision Sigfox devices easily using {{< product-c8y-iot >}} Device Management application. - Decode upstream payload packets using a web-based user interface. - Debug and post-process raw device data through {{< product-c8y-iot >}} events. - Send downstream data to the device using {{< product-c8y-iot >}} operations. diff --git a/content/protocol-integration/sigfox-bundle/registering-sigfox-devices.md b/content/protocol-integration/sigfox-bundle/registering-sigfox-devices.md index 751e19081b..03bc6ba7ce 100644 --- a/content/protocol-integration/sigfox-bundle/registering-sigfox-devices.md +++ b/content/protocol-integration/sigfox-bundle/registering-sigfox-devices.md @@ -5,7 +5,7 @@ layout: redirect --- -To register a Sigfox device in {{< product-c8y-iot >}} navigate to **Devices** > **Registration** in the Device management application, click **Register device** at the top right and select **Single device registration** > **Sigfox** from the dropdown. +To register a Sigfox device in {{< product-c8y-iot >}} navigate to **Devices** > **Registration** in the Device Management application, click **Register device** at the top right and select **Single device registration** > **Sigfox** from the dropdown. ![Register devices](/images/device-protocols/sigfox/sigfox-registration.png) @@ -38,7 +38,7 @@ Click **Register** to submit the device registration request and create the devi You can verify that the device is really connected by checking that events are actually coming in. You can do so by clicking on a device and opening its **Events** tab. All events related to this device are listed here. -For more information on viewing and managing your connected devices, also refer to the [Device management application](/device-management-application/). +For more information on viewing and managing your connected devices, also refer to the [Device Management application](/device-management-application/). In order to migrate the device from one LNS connection to another, the device must be re-registered. Navigate to the **LPWAN** tab of the Device. diff --git a/content/protocol-integration/sigfox-bundle/sending-operations.md b/content/protocol-integration/sigfox-bundle/sending-operations.md index 556cea3462..a470ba2aa8 100644 --- a/content/protocol-integration/sigfox-bundle/sending-operations.md +++ b/content/protocol-integration/sigfox-bundle/sending-operations.md @@ -5,7 +5,7 @@ layout: redirect --- -If the device supports sending hexadecimal commands, you can send commands from the Shell. In the Device management application, navigate to the device you want to send an operation to in the **All devices** page. Switch to the **Shell** tab. +If the device supports sending hexadecimal commands, you can send commands from the Shell. In the Device Management application, navigate to the device you want to send an operation to in the **All devices** page. Switch to the **Shell** tab. {{< c8y-admon-info >}} Operations do not go to a status of EXECUTING immediately. They go to EXECUTING when the device is expecting the downlink message. Afterwards, the pending operation which is created first goes to a status of EXECUTING. diff --git a/content/quick-start/first-steps.md b/content/quick-start/first-steps.md index 9bfce5cfa6..ae40170614 100644 --- a/content/quick-start/first-steps.md +++ b/content/quick-start/first-steps.md @@ -56,7 +56,7 @@ See [User options and settings](/get-familiar-with-the-ui/user-settings/) for de ### Step 3: Register a device -To connect a device to {{< product-c8y-iot >}}, you must register it in the platform. This is done in the **Device management application**. Under [Registering devices](/device-management-application/registering-devices/) you find a detailed description of the general registration process. +To connect a device to {{< product-c8y-iot >}}, you must register it in the platform. This is done in the **Device Management application**. Under [Registering devices](/device-management-application/registering-devices/) you find a detailed description of the general registration process. Moreover, we offer two step-by-step descriptions to easily register a first device to your {{< product-c8y-iot >}} account: diff --git a/content/sector/device_management/_index.md b/content/sector/device_management/_index.md index 42d7b54730..39737dbf48 100644 --- a/content/sector/device_management/_index.md +++ b/content/sector/device_management/_index.md @@ -1,5 +1,5 @@ --- -title: "Device management & connectivity" +title: "Device Management & Connectivity" icon: "c8y-icon c8y-icon-device-management" weight: 30 svg: '}} -The smartphone must remain connected to {{< product-c8y-iot >}} to receive these commands. On the device's own dashboard, online devices are shown with a green map-marker. You can also determine if the device is connected in the Device management application. On the **All Devices** page two green arrows indicate that a device is online. Moreover, the individual device info pages contain a "Device status" widget. +The smartphone must remain connected to {{< product-c8y-iot >}} to receive these commands. On the device's own dashboard, online devices are shown with a green map-marker. You can also determine if the device is connected in the Device Management application. On the **All Devices** page two green arrows indicate that a device is online. Moreover, the individual device info pages contain a "Device status" widget. {{< /c8y-admon-info >}} diff --git a/content/sensor-app/registering-the-sensor-app.md b/content/sensor-app/registering-the-sensor-app.md index b998f15b9b..b4a9647714 100644 --- a/content/sensor-app/registering-the-sensor-app.md +++ b/content/sensor-app/registering-the-sensor-app.md @@ -33,7 +33,7 @@ QR codes not supported by the {{< sensor-app >}} are highlighted using a red reg ### Manual registration {#manual-registration} -1. On a desktop or laptop computer, open a web browser and log in to your {{< product-c8y-iot >}} tenant. In the Device management application, select **Devices > Registration** from the navigator. +1. On a desktop or laptop computer, open a web browser and log in to your {{< product-c8y-iot >}} tenant. In the Device Management application, select **Devices > Registration** from the navigator. ![Manual registration](/images/users-guide/csa/csa-device-registration.png) diff --git a/content/standard-tenant/alarm-mapping.md b/content/standard-tenant/alarm-mapping.md index 68fc12d5dc..46a9637425 100644 --- a/content/standard-tenant/alarm-mapping.md +++ b/content/standard-tenant/alarm-mapping.md @@ -26,7 +26,7 @@ For easier user access management, the above permissions are included in the glo {{< /c8y-admon-req >}} {{< c8y-admon-related >}} -- [Device management > Device management application> Monitoring and controlling devices > Working with alarms](/device-management-application/monitoring-and-controlling-devices/#working-with-alarms) for information on working with alarms in general. +- [Device Management > Device Management application> Monitoring and controlling devices > Working with alarms](/device-management-application/monitoring-and-controlling-devices/#working-with-alarms) for information on working with alarms in general. - [Alarms](https://{{< domain-c8y >}}/api/core/#tag/Alarms) in the {{< openapi >}} for details on managing alarms via REST. {{< /c8y-admon-related >}} diff --git a/content/standard-tenant/ecosystem-bundle/managing-applications.md b/content/standard-tenant/ecosystem-bundle/managing-applications.md index 1a5354af99..69b2983724 100644 --- a/content/standard-tenant/ecosystem-bundle/managing-applications.md +++ b/content/standard-tenant/ecosystem-bundle/managing-applications.md @@ -60,7 +60,7 @@ Click the application or click the menu icon }} ### To delete an application {#to-delete-an-application} diff --git a/content/standard-tenant/ecosystem-bundle/subscribed-applications.md b/content/standard-tenant/ecosystem-bundle/subscribed-applications.md index d33bb26076..260f5d9621 100644 --- a/content/standard-tenant/ecosystem-bundle/subscribed-applications.md +++ b/content/standard-tenant/ecosystem-bundle/subscribed-applications.md @@ -49,7 +49,7 @@ Below all applications are listed which are by default available in the {{< stan -Device management +Device Management Manage and monitor devices, and control and troubleshoot devices remotely devicemanagement Web application diff --git a/content/standard-tenant/home-screen.md b/content/standard-tenant/home-screen.md index daab5bf9fa..db0e714b3d 100644 --- a/content/standard-tenant/home-screen.md +++ b/content/standard-tenant/home-screen.md @@ -34,5 +34,5 @@ The capacity sections show: * Device API requests - counting only when the API is called from a device (for example sending a measurement). * Storage - the total amount of data stored in your account. This amount can be changed by [retention rules](/standard-tenant/managing-data/#retention-rules) and by the amount and size of [stored files](/standard-tenant/managing-data/#files-repository). * Root devices - the number of root devices connected to your account, excluding child devices. -* Devices - the total number of devices connected to your account. This is the sum of the devices listed in the [All devices](/device-management-application/viewing-all-devices/) page of the Device management application and their direct and indirect child devices. +* Devices - the total number of devices connected to your account. This is the sum of the devices listed in the [All devices](/device-management-application/viewing-all-devices/) page of the Device Management application and their direct and indirect child devices. * Users - the sum of all users configured in this account, active and inactive. diff --git a/content/standard-tenant/managing-permissions-bundle/global-roles.md b/content/standard-tenant/managing-permissions-bundle/global-roles.md index c0a3f17673..cab3418d11 100644 --- a/content/standard-tenant/managing-permissions-bundle/global-roles.md +++ b/content/standard-tenant/managing-permissions-bundle/global-roles.md @@ -63,7 +63,7 @@ Furthermore, the following pre-configured roles are initially provided. Devicemanagement User -Can access the Device management application. The user will be able to use the simulator and to run bulk operations. In addition, you should add a role providing access to devices. +Can access the Device Management application. The user will be able to use the simulator and to run bulk operations. In addition, you should add a role providing access to devices. Global Manager diff --git a/content/standard-tenant/managing-permissions-bundle/improving-performance.md b/content/standard-tenant/managing-permissions-bundle/improving-performance.md index cba93b93b0..780f2051ed 100644 --- a/content/standard-tenant/managing-permissions-bundle/improving-performance.md +++ b/content/standard-tenant/managing-permissions-bundle/improving-performance.md @@ -10,9 +10,9 @@ The {{< product-c8y-iot >}} platform provides optimized UI performance for users The performance of the following UI pages is improved: * In the device details view, the tabs **Info**, **Measurements**, **Alarms**, **Events** and **Control**. -* Pages with aggregated alarm views from multiple devices, if the number of alarms in the system is low, for example, Cockpit > Home dashboard, Cockpit > Alarms and Device management > Home. -* Pages with aggregated events from multiple devices, if the number of events is low, for example, Device management > Events. -* Pages with aggregated operations from multiple devices, if the number of operations is low, for example, Device management > Decie control > Single operations. +* Pages with aggregated alarm views from multiple devices, if the number of alarms in the system is low, for example, Cockpit > Home dashboard, Cockpit > Alarms and Device Management > Home. +* Pages with aggregated events from multiple devices, if the number of events is low, for example, Device Management > Events. +* Pages with aggregated operations from multiple devices, if the number of operations is low, for example, Device Management > Decie control > Single operations. As an administrator, you can disable the performance feature by doing the following: - On platform level via the configuration file (only available for platform administrators, see the *{{< product-c8y-iot >}} - Operations guide* for details). diff --git a/content/standard-tenant/managing-permissions.md b/content/standard-tenant/managing-permissions.md index 7f74a188ec..0f9467d4b4 100644 --- a/content/standard-tenant/managing-permissions.md +++ b/content/standard-tenant/managing-permissions.md @@ -38,7 +38,7 @@ The above permissions can be used to create roles for robust user management. Ev - [Platform administration > {{< standard-tenant >}} management > Managing users](/standard-tenant/managing-users) for information on managing users in general. - [Platform administration > {{< standard-tenant >}} management > Managing applications](/standard-tenant/ecosystem/#managing-applications) for more information on managing applications. - [Platform administration > {{< enterprise-tenant >}} administration > Managing user hierarchies](/enterprise-tenant/managing-user-hierarchies) for more information on managing user hierarchies. -- [Device management > Device integration > Fragment library](/device-integration/fragment-library/) for further information on fragment types. +- [Device Management > Device integration > Fragment library](/device-integration/fragment-library/) for further information on fragment types. - [Roles](https://{{< domain-c8y >}}/api/core/#tag/Roles) and [Inventory Roles](https://{{< domain-c8y >}}/api/core/#tag/Inventory-Roles) in the {{< openapi >}} for managing permissions via REST. - {{< /c8y-admon-related >}} diff --git a/content/streaming-analytics/analytics-builder-bundle/getting-started.md b/content/streaming-analytics/analytics-builder-bundle/getting-started.md index f682866314..8dca96f94c 100644 --- a/content/streaming-analytics/analytics-builder-bundle/getting-started.md +++ b/content/streaming-analytics/analytics-builder-bundle/getting-started.md @@ -28,7 +28,7 @@ The model that you add will contain three blocks: - An input block which receives measurement values from a device. - A block that calculates the mean of the measurement values over time. -- An output block that sends the calculated mean values to {{< product-c8y-iot >}}'s Device management application so that they can be viewed there. +- An output block that sends the calculated mean values to {{< product-c8y-iot >}}'s Device Management application so that they can be viewed there. When you have completed all steps below, your model will look similar to the following: @@ -113,11 +113,11 @@ A card for the newly added model is shown on the **Models** tab of the model man 1. Click the drop-down menu on the card which currently shows **Draft** and select **Production**. 2. Click the toggle button on the card which currently shows **Inactive**. This changes the state to **Active**. -#### Step 9: Go to the Device management and view the measurements {#step-9-go-to-the-device-management-and-view-the-measurements} +#### Step 9: Go to the Device Management and view the measurements {#step-9-go-to-the-device-management-and-view-the-measurements} -To view the measurements that are sent from your active model, you must switch to the Device management application. See [Device management application](/device-management-application/) for detailed information. +To view the measurements that are sent from your active model, you must switch to the Device Management application. See [Device Management application](/device-management-application/) for detailed information. -1. Go to the Device management application. +1. Go to the Device Management application. 2. In the navigator on the left, click **Devices** and then **All devices**. 3. Locate your device and click its name to display the device details. 4. Click **Measurements** on the left. This is a dynamic tab which is only shown when measurements are available for the device. @@ -205,12 +205,12 @@ Once the instance has been activated, send in the data from your device. The ins For our example case with the gyroscope measurements from a smartphone, it should be sufficient that you simply turn off the smartphone display while the {{< sensor-app >}} is still running. -#### Step 6: Go to the Device management application and view the alarms {#step-6-go-to-the-device-management-application-and-view-the-alarms} +#### Step 6: Go to the Device Management application and view the alarms {#step-6-go-to-the-device-management-application-and-view-the-alarms} -To view the alarms that are sent from your active instance, you must switch to the Device management application. -See [Device management application](/device-management-application/) for detailed information. +To view the alarms that are sent from your active instance, you must switch to the Device Management application. +See [Device Management application](/device-management-application/) for detailed information. -1. Go to the Device management application. +1. Go to the Device Management application. 2. In the navigator on the left, click **Devices** and then **All devices**. 3. Locate your device and click its name to display the device details. 4. Click **Alarms** on the left. diff --git a/content/streaming-analytics/analytics-builder-bundle/models-and-devices.md b/content/streaming-analytics/analytics-builder-bundle/models-and-devices.md index d68e8ee383..96b507773d 100644 --- a/content/streaming-analytics/analytics-builder-bundle/models-and-devices.md +++ b/content/streaming-analytics/analytics-builder-bundle/models-and-devices.md @@ -87,7 +87,7 @@ By default, the virtual devices are kept for 30 days. If you want to change this See also [Configuration](/streaming-analytics/analytics-builder/#configuration). -Virtual devices are not shown in the Device management application. Use [REST](/smartrest/smartrest-introduction/) operations to find these entries. +Virtual devices are not shown in the Device Management application. Use [REST](/smartrest/smartrest-introduction/) operations to find these entries. ### Connections between models {#connections-between-models} diff --git a/content/streaming-analytics/analytics-builder-bundle/using-the-model-editor.md b/content/streaming-analytics/analytics-builder-bundle/using-the-model-editor.md index eb20c700bc..4d24f643e5 100644 --- a/content/streaming-analytics/analytics-builder-bundle/using-the-model-editor.md +++ b/content/streaming-analytics/analytics-builder-bundle/using-the-model-editor.md @@ -303,7 +303,7 @@ The above icons are only enabled when there is an operation that can be undone o #### Replacing sources or destinations {#replacing-sources-or-destinations} -You can find the input sources or output destinations that are used in the current model and replace them with other input sources or output destinations that are currently registered in the {{< product-c8y-iot >}} inventory \(visualized in the Device management application\). +You can find the input sources or output destinations that are used in the current model and replace them with other input sources or output destinations that are currently registered in the {{< product-c8y-iot >}} inventory \(visualized in the Device Management application\). {{< c8y-admon-info>}} In the rules below, the term device refers to a device or other asset \(but not to a group\). diff --git a/content/streaming-analytics/introduction-analytics.md b/content/streaming-analytics/introduction-analytics.md index 7c5b8e4edc..910bc7d9c4 100644 --- a/content/streaming-analytics/introduction-analytics.md +++ b/content/streaming-analytics/introduction-analytics.md @@ -9,7 +9,7 @@ aliases: --- Devices and sensors can be connected to {{< product-c8y-iot >}}. See [Interfacing devices](/concepts/interfacing-devices/) and [Device integration using MQTT](/device-integration/mqtt/). -Sensors result in `Measurement` or `Event` objects in {{< product-c8y-iot >}}, and devices can receive `Operation` objects created within the {{< product-c8y-iot >}} platform. All of these objects \(`Measurement`, `Event`, `Operation`\) will be associated with a single device in the {{< product-c8y-iot >}} platform. A device may have multiple types of measurement associated with it, and the types of measurements each device supports may be the same as other devices or different to other devices. Once devices are connected to {{< product-c8y-iot >}}, information about these devices is stored in the {{< product-c8y-iot >}} inventory. These are visible in the Device management application, which can also be used to view `Measurement`, `Event` or `Operation` objects associated with that device. See [Device management](/section/device_management/) for more information. +Sensors result in `Measurement` or `Event` objects in {{< product-c8y-iot >}}, and devices can receive `Operation` objects created within the {{< product-c8y-iot >}} platform. All of these objects \(`Measurement`, `Event`, `Operation`\) will be associated with a single device in the {{< product-c8y-iot >}} platform. A device may have multiple types of measurement associated with it, and the types of measurements each device supports may be the same as other devices or different to other devices. Once devices are connected to {{< product-c8y-iot >}}, information about these devices is stored in the {{< product-c8y-iot >}} inventory. These are visible in the Device Management application, which can also be used to view `Measurement`, `Event` or `Operation` objects associated with that device. See [Device Management](/section/device_management/) for more information. Using the Streaming Analytics application, you can add your own logic to your IoT solution for immediate processing of incoming data from devices or other data sources. These user-defined operations can, for example, alert applications of new incoming data, create new operations based on the received data (such as sending an alarm when a threshold for a sensor is exceeded), or trigger operations on devices. diff --git a/data/component.json b/data/component.json index 30428d25f3..48ce30ebf2 100644 --- a/data/component.json +++ b/data/component.json @@ -86,7 +86,7 @@ "product_area": [ { "value": "product_area-m1iHjqikD", - "label": "Device management & connectivity" + "label": "Device Management & Connectivity" } ] }, @@ -96,7 +96,7 @@ "product_area": [ { "value": "product_area-m1iHjqikD", - "label": "Device management & connectivity" + "label": "Device Management & Connectivity" } ] }, @@ -106,7 +106,7 @@ "product_area": [ { "value": "product_area-m1iHjqikD", - "label": "Device management & connectivity" + "label": "Device Management & Connectivity" } ] }, @@ -116,7 +116,7 @@ "product_area": [ { "value": "product_area-m1iHjqikD", - "label": "Device management & connectivity" + "label": "Device Management & Connectivity" } ] }, @@ -126,7 +126,7 @@ "product_area": [ { "value": "product_area-m1iHjqikD", - "label": "Device management & connectivity" + "label": "Device Management & Connectivity" } ] }, @@ -136,7 +136,7 @@ "product_area": [ { "value": "product_area-m1iHjqikD", - "label": "Device management & connectivity" + "label": "Device Management & Connectivity" } ] }, @@ -146,7 +146,7 @@ "product_area": [ { "value": "product_area-m1iHjqikD", - "label": "Device management & connectivity" + "label": "Device Management & Connectivity" } ] }, @@ -156,7 +156,7 @@ "product_area": [ { "value": "product_area-m1iHjqikD", - "label": "Device management & connectivity" + "label": "Device Management & Connectivity" } ] }, diff --git a/data/productarea.json b/data/productarea.json index 2bb9dffede..a6259983bd 100644 --- a/data/productarea.json +++ b/data/productarea.json @@ -9,7 +9,7 @@ "id": "product_area-eC7h0SiQ2b" }, { - "option": "Device management & connectivity", + "option": "Device Management & Connectivity", "id": "product_area-m1iHjqikD" }, { diff --git a/static/admin/config.yml b/static/admin/config.yml index 3ae077a047..359da87906 100644 --- a/static/admin/config.yml +++ b/static/admin/config.yml @@ -113,15 +113,15 @@ collections: - { label: "Body", name: "body", widget: "markdown"} - name: "device_management" - label: "Device management & connectivity" + label: "Device Management & Connectivity" folder: "content/change-logs/device-management" - description: "Change log entries for the Device management & connectivity product area" + description: "Change log entries for the Device Management & Connectivity product area" create: true slug: "{{fields.build_artifact.0.label}}-{{fields.version}}-{{slug}}" fields: - {label: "Date",name: "date",widget: "datetime", format: "YYYY-MM-DD", default: "", required: false} - {label: "Title", name: "title", widget: "string"} - - {label: "Product area", name: "product_area", widget: "hidden", default: "Device management & connectivity"} + - {label: "Product area", name: "product_area", widget: "hidden", default: "Device Management & Connectivity"} - label: Change type name: change_type widget: ncw-file-relation From 56ae98414b791de2a4f4186035e63d41a9958437 Mon Sep 17 00:00:00 2001 From: BeateRixen Date: Wed, 4 Sep 2024 17:11:49 +0200 Subject: [PATCH 02/12] Fixed wrong heading in links with breadcrumbs --- .../cockpit/managing-assets-bundle/asset-hierarchy.md | 2 +- content/cockpit/smart-rules-collection.md | 2 +- .../extensible-device-registration.md | 2 +- content/concepts/interfacing-devices.md | 2 +- content/device-management-application/connectivity.md | 2 +- .../managing-device-data.md | 10 +++++----- .../managing-device-types.md | 2 +- .../monitoring-and-controlling-devices.md | 4 ++-- .../monitoring-device-services.md | 4 ++-- .../registering-devices.md | 6 +++--- .../smartrest-templates.md | 4 ++-- content/get-familiar-with-the-ui/ui-introduction.md | 2 +- content/glossary/d.md | 4 ++-- content/glossary/l.md | 2 +- content/glossary/m.md | 2 +- content/glossary/o.md | 2 +- content/standard-tenant/alarm-mapping.md | 2 +- .../improving-performance.md | 6 +++--- content/standard-tenant/managing-permissions.md | 2 +- 19 files changed, 31 insertions(+), 31 deletions(-) diff --git a/content/cockpit/managing-assets-bundle/asset-hierarchy.md b/content/cockpit/managing-assets-bundle/asset-hierarchy.md index 9553783d79..c67279c3dc 100644 --- a/content/cockpit/managing-assets-bundle/asset-hierarchy.md +++ b/content/cockpit/managing-assets-bundle/asset-hierarchy.md @@ -38,7 +38,7 @@ Single devices are not managed in the Cockpit application. They are managed in t {{< c8y-admon-related >}} - [Getting started > Technical concepts > {{< product-c8y-iot >}}'s domain model](/concepts/domain-model/) for details on {{< product-c8y-iot >}}'s domain model. -- [Device Management > Device Management application](/device-management-application/) for details on working with devices in {{< product-c8y-iot >}}. +- [Device management & connectivity > Device Management application](/device-management-application/) for details on working with devices in {{< product-c8y-iot >}}. - Refer to the [{{< product-c8y-iot >}} Codex](https://styleguide.cumulocity.com/apps/codex/#/) for more information on developing applications in the {{< product-c8y-iot >}} environment. Moreover find various related tutorials in the [{{< sag-dev-community >}}]({{< link-sag-tech-forum >}}). {{< /c8y-admon-related >}} diff --git a/content/cockpit/smart-rules-collection.md b/content/cockpit/smart-rules-collection.md index 7aa7b41ce4..d57e3c9693 100644 --- a/content/cockpit/smart-rules-collection.md +++ b/content/cockpit/smart-rules-collection.md @@ -13,7 +13,7 @@ In certain rule parameters, various trigger fields can be used as variables, see {{< /c8y-admon-info >}} {{< c8y-admon-related >}} -- [Device Management > Monitoring and controlling devices > Working with alarms](/device-management-application/monitoring-and-controlling-devices/#working-with-alarms) for details on alarms in {{< product-c8y-iot >}}. +- [Device management & connectivity > Monitoring and controlling devices > Working with alarms](/device-management-application/monitoring-and-controlling-devices/#working-with-alarms) for details on alarms in {{< product-c8y-iot >}}. - [Analytics > Streaming analytics > Troubleshooting and diagnostics > Alarms generated by the Apama-ctrl microservice](/streaming-analytics/troubleshooting/#alarms) for more information on alarms for smart rules generated by the Apama-ctrl microservice. - [Alarms](https://{{< domain-c8y >}}/api/core/#tag/Alarms) in the {{< openapi >}} for details on managing alarms via REST. {{< /c8y-admon-related >}} diff --git a/content/concepts/applications-bundle/extensible-device-registration.md b/content/concepts/applications-bundle/extensible-device-registration.md index a1fe85d478..952735fc7e 100644 --- a/content/concepts/applications-bundle/extensible-device-registration.md +++ b/content/concepts/applications-bundle/extensible-device-registration.md @@ -170,7 +170,7 @@ The following diagram visualizes the single device registration flow: Many device integrations require the registration of many devices at the same time. Currently, all protocols must rely on the bulk registration mechanism of the platform, which often either requires too many fields or requires custom fields to be added. The latter ones can however so far not be validated, as the core directly creates devices -- and microservices and agents have no control over the properties being written to the managed objects. -After enabling the `extensibleBulkDeviceRegistration` extension type, the Device Management > Devices > Register device `Bulk device registration` modal is displayed with an extended wizard entry corresponding to the extension `name` property. +After enabling the `extensibleBulkDeviceRegistration` extension type, the Device management & connectivity > Devices > Register device `Bulk device registration` modal is displayed with an extended wizard entry corresponding to the extension `name` property. Additionally, the microservice provides the title of the wizard step and example bulk file(s): ```json diff --git a/content/concepts/interfacing-devices.md b/content/concepts/interfacing-devices.md index d0a0b854c1..0b14e0a270 100644 --- a/content/concepts/interfacing-devices.md +++ b/content/concepts/interfacing-devices.md @@ -15,7 +15,7 @@ To interface these systems with {{< product-c8y-iot >}}, a driver software calle {{< c8y-admon-related >}} - [Getting started > Technical concepts > {{< product-c8y-iot >}}´s domain model](/concepts/domain-model) for understanding the data structures exchanged between agents and the {{< product-c8y-iot >}} core. -- [Device Management > Device integration](/device-integration) for understanding in detail how to develop agent software using the REST or MQTT protocols. +- [Device management & connectivity > Device integration](/device-integration) for understanding in detail how to develop agent software using the REST or MQTT protocols. - [REST implementation](https://{{< domain-c8y >}}/api/core/#section/REST-implementation) in the {{< openapi >}}, for a detailed specification of the interfaces between agents and the {{< product-c8y-iot >}} core. {{< /c8y-admon-related >}} diff --git a/content/device-management-application/connectivity.md b/content/device-management-application/connectivity.md index 571e4a98ed..838e2d3fa1 100644 --- a/content/device-management-application/connectivity.md +++ b/content/device-management-application/connectivity.md @@ -7,7 +7,7 @@ sector: --- {{< c8y-admon-related >}} -* [Device Management > Device integration > Fragment library > Connectivity](/device-integration/fragment-library/#connectivity) for details on the `c8y_Mobile` fragment used in managed objects. +* [Device management & connectivity > Device integration > Fragment library > Connectivity](/device-integration/fragment-library/#connectivity) for details on the `c8y_Mobile` fragment used in managed objects. * [Platform administration > {{< standard-tenant >}} administration > Changing settings > Connectivity](/standard-tenant/changing-settings/#connectivity) for information on how to change the connectivity settings via the UI. {{< /c8y-admon-related >}} diff --git a/content/device-management-application/managing-device-data.md b/content/device-management-application/managing-device-data.md index 96e4415e79..547efd2c8e 100644 --- a/content/device-management-application/managing-device-data.md +++ b/content/device-management-application/managing-device-data.md @@ -10,12 +10,12 @@ sector: --- {{< c8y-admon-related >}} -* [Device Management > Device integration > Fragment library > Firmware](/device-integration/fragment-library/#firmware) for details on the `c8y_Firmware` fragment used in managed objects. -* [Device Management > Device integration > Fragment library > Software](/device-integration/fragment-library/#software) for details on legacy software management via the `c8y_SoftwareList` fragment, software updates via the `c8y_SoftwareUpdate` fragment and advanced software management via the `c8y_SupportedOperations` and `c8y_SupportedSoftwareTypes` fragments used in managed objects. -* [Device Management > Device integration > Fragment library > Configuration](/device-integration/fragment-library/#configuration) for details on text-based configuration, file-based configuration and typed file-based configuration. +* [Device management & connectivity > Device integration > Fragment library > Firmware](/device-integration/fragment-library/#firmware) for details on the `c8y_Firmware` fragment used in managed objects. +* [Device management & connectivity > Device integration > Fragment library > Software](/device-integration/fragment-library/#software) for details on legacy software management via the `c8y_SoftwareList` fragment, software updates via the `c8y_SoftwareUpdate` fragment and advanced software management via the `c8y_SupportedOperations` and `c8y_SupportedSoftwareTypes` fragments used in managed objects. +* [Device management & connectivity > Device integration > Fragment library > Configuration](/device-integration/fragment-library/#configuration) for details on text-based configuration, file-based configuration and typed file-based configuration. * The [device credentials API](https://{{< domain-c8y >}}/api/core/#tag/Device-credentials) for REST API methods concerning device credentials. -* [Device Management > Device integration > Fragment library > Device profile](/device-integration/fragment-library/#device-profile) for details on the `c8y_DeviceProfile` fragment used in managed objects. -* [Device Management > Device integration > Device integration using MQTT > Device certificates](/device-integration/mqtt/#device-certificates) for information on device certificates in the context of MQTT. +* [Device management & connectivity > Device integration > Fragment library > Device profile](/device-integration/fragment-library/#device-profile) for details on the `c8y_DeviceProfile` fragment used in managed objects. +* [Device management & connectivity > Device integration > Device integration using MQTT > Device certificates](/device-integration/mqtt/#device-certificates) for information on device certificates in the context of MQTT. {{< /c8y-admon-related >}} The Device Management application provides features that support you in efficiently managing your devices. diff --git a/content/device-management-application/managing-device-types.md b/content/device-management-application/managing-device-types.md index 6a8a45632a..9b188d17f2 100644 --- a/content/device-management-application/managing-device-types.md +++ b/content/device-management-application/managing-device-types.md @@ -18,7 +18,7 @@ helpcontent: {{< c8y-admon-related >}} * [Getting started > Technical concepts > Interfacing devices](/concepts/interfacing-devices/) for information on the concepts relevant for interfacing IoT devices and other IoT-related data sources with {{< product-c8y-iot >}}. -* [Device Management > Protocol integration](/protocol-integration/) for a list of protocols, parameters and network connectivity options for devices. +* [Device management & connectivity > Protocol integration](/protocol-integration/) for a list of protocols, parameters and network connectivity options for devices. {{< /c8y-admon-related >}} To process data from various device types, {{< product-c8y-iot >}} uses device protocols which are stored in a database. diff --git a/content/device-management-application/monitoring-and-controlling-devices.md b/content/device-management-application/monitoring-and-controlling-devices.md index 52069e5b7c..1fa9912b8a 100644 --- a/content/device-management-application/monitoring-and-controlling-devices.md +++ b/content/device-management-application/monitoring-and-controlling-devices.md @@ -10,9 +10,9 @@ sector: --- {{< c8y-admon-related >}} -* [Device Management > Device integration > Fragment library > Device availability](/device-integration/fragment-library/#device-availability) for details on the `c8y_RequiredAvailability`, `c8y_UnavailabilityAlarm`, `c8y_Availability` and `c8y_Connection` fragments used in managed objects. +* [Device management & connectivity > Device integration > Fragment library > Device availability](/device-integration/fragment-library/#device-availability) for details on the `c8y_RequiredAvailability`, `c8y_UnavailabilityAlarm`, `c8y_Availability` and `c8y_Connection` fragments used in managed objects. * The [alarms API](https://{{< domain-c8y >}}/api/core/#tag/Alarms) for REST API methods concerning alarms. -* [Device Management > Device integration > Fragment library > Alarms](/device-integration/fragment-library/#alarms) for details on how to raise and clear alarms. +* [Device management & connectivity > Device integration > Fragment library > Alarms](/device-integration/fragment-library/#alarms) for details on how to raise and clear alarms. * The [operations API](https://{{< domain-c8y >}}/api/core/#tag/Operations) for REST API methods concerning operations. * The [bulk operations API](https://{{< domain-c8y >}}/api/core/#tag/Bulk-operations) for REST API methods concerning bulk operations. {{< /c8y-admon-related >}} diff --git a/content/device-management-application/monitoring-device-services.md b/content/device-management-application/monitoring-device-services.md index 8dd51f32d2..5aac7943ec 100644 --- a/content/device-management-application/monitoring-device-services.md +++ b/content/device-management-application/monitoring-device-services.md @@ -8,10 +8,10 @@ sector: {{< c8y-admon-related >}} * The [alarms API](https://{{< domain-c8y >}}/api/core/#tag/Alarms) for REST API methods concerning alarms. -* [Device Management > Device integration > Fragment library > Alarms](/device-integration/fragment-library/#alarms) for details on how to raise and clear alarms. +* [Device management & connectivity > Device integration > Fragment library > Alarms](/device-integration/fragment-library/#alarms) for details on how to raise and clear alarms. * The [events API](https://{{< domain-c8y >}}/api/core/#tag/Events) for REST API methods concerning events. * The [measurements API](https://{{< domain-c8y >}}/api/core/#tag/Measurements) for REST API methods concerning measurements. -* [Device Management > Device integration > Fragment library > Measurements](/device-integration/fragment-library/#measurements) for details on measurements. +* [Device management & connectivity > Device integration > Fragment library > Measurements](/device-integration/fragment-library/#measurements) for details on measurements. {{< /c8y-admon-related >}} The Device Management application lets you monitor the data that your devices send about the services they are running. diff --git a/content/device-management-application/registering-devices.md b/content/device-management-application/registering-devices.md index ce8cf6e9a9..94f162d92e 100644 --- a/content/device-management-application/registering-devices.md +++ b/content/device-management-application/registering-devices.md @@ -39,9 +39,9 @@ helpcontent: --- {{< c8y-admon-related >}} -* [Device Management > Protocol integration](/protocol-integration/) for details on registering devices using various standard protocol types. -* [Device Management > Device integration](/device-integration/introduction) for step-by-step instructions on registering devices. -* [Device Management > Device integration > Device integration using REST](/device-integration/device-integration-rest/) for a detailed descriptions on device integration via REST. +* [Device management & connectivity > Protocol integration](/protocol-integration/) for details on registering devices using various standard protocol types. +* [Device management & connectivity > Device integration](/device-integration/introduction) for step-by-step instructions on registering devices. +* [Device management & connectivity > Device integration > Device integration using REST](/device-integration/device-integration-rest/) for a detailed descriptions on device integration via REST. * The [New device requests API](https://{{< domain-c8y >}}/api/core/#tag/New-device-requests) for REST API methods concerning the creation of new devices. {{< /c8y-admon-related >}} diff --git a/content/device-management-application/smartrest-templates.md b/content/device-management-application/smartrest-templates.md index c060515d0b..251925b2c1 100644 --- a/content/device-management-application/smartrest-templates.md +++ b/content/device-management-application/smartrest-templates.md @@ -24,8 +24,8 @@ SmartREST templates are a collection of request and response templates used to c To ease the device integration, {{< product-c8y-iot >}} supports static templates that can be used without the need for creating your own templates. These templates focus only on the most commonly used messages for device management. For further information on static templates, refer to the [MQTT static templates](/smartrest/mqtt-static-templates). {{< c8y-admon-related >}} -* [Device Management > SmartREST > SmartREST 2.0](/smartrest/smartrest-two/) for details on the SmartREST protocol, the data format used, as well as the anatomy and registration of SmartREST templates. -* [Device Management > Device integration > Device integration using MQTT](/device-integration/mqtt/) for information on integrating devices via MQTT. +* [Device management & connectivity > SmartREST > SmartREST 2.0](/smartrest/smartrest-two/) for details on the SmartREST protocol, the data format used, as well as the anatomy and registration of SmartREST templates. +* [Device management & connectivity > Device integration > Device integration using MQTT](/device-integration/mqtt/) for information on integrating devices via MQTT. {{< /c8y-admon-related >}} Open the **SmartREST template** page from the **Device Types** menu in the navigator. diff --git a/content/get-familiar-with-the-ui/ui-introduction.md b/content/get-familiar-with-the-ui/ui-introduction.md index 39247cfd01..0e6ccca644 100644 --- a/content/get-familiar-with-the-ui/ui-introduction.md +++ b/content/get-familiar-with-the-ui/ui-introduction.md @@ -15,5 +15,5 @@ In the entire documentation you find detailed description on the usage of the re Specifically, check out the following sections: - [Platform administration > {{< standard-tenant >}} administration](/standard-tenant/) for details on the Administration application. -- [Device Management > Device Management application](/device-management-application/) for details on the Device Management application. +- [Device management & connectivity > Device Management application](/device-management-application/) for details on the Device Management application. - [Application enablement & solutions > Cockpit](/cockpit/) for details on the Cockpit application. diff --git a/content/glossary/d.md b/content/glossary/d.md index 86cffd145f..e2883517c3 100644 --- a/content/glossary/d.md +++ b/content/glossary/d.md @@ -44,7 +44,7 @@ Devices are a special type of [asset](/glossary/a/#asset). They can constitute a The Device Management application is one of the default applications of {{< product-c8y-iot >}}. The Device Management application provides functionalities for connecting, managing and monitoring devices and allows to control and troubleshoot devices remotely. -For details see [Device Management > Device Management application](/device-management-application/). +For details see [Device management & connectivity > Device Management application](/device-management-application/). ### Device protocol {#device-protocol} @@ -52,7 +52,7 @@ For details see [Device Management > Device Management application](/device-mana A device protocol defines how data from a specific device type should be transferred into the {{< product-c8y-iot >}} platform. It contains protocol-specific information about where the data is obtained from, how to transform it, and how to store it in {{< product-c8y-iot >}}. The definition of the device protocol differs based on the underlying protocol used by the device (for example, Modbus, LoRa, OPC UA or LWM2M). -For details see [Device Management > Protocol integration](/protocol-integration/). +For details see [Device management & connectivity > Protocol integration](/protocol-integration/). ### Digital twin {#digital-twin} diff --git a/content/glossary/l.md b/content/glossary/l.md index 999b570285..6f1f3a76ad 100644 --- a/content/glossary/l.md +++ b/content/glossary/l.md @@ -10,4 +10,4 @@ sector: Lightweight M2M (LWM2M) is a traffic and resource-optimized protocol to remotely manage IoT devices. {{< product-c8y-iot >}} provides support for easily connecting any LWM2M device to the platform. -For details see [Device Management > Protocol integration > LWM2M](/protocol-integration/lwm2m). +For details see [Device management & connectivity > Protocol integration > LWM2M](/protocol-integration/lwm2m). diff --git a/content/glossary/m.md b/content/glossary/m.md index 1d3f60f9c9..92de008f09 100644 --- a/content/glossary/m.md +++ b/content/glossary/m.md @@ -59,7 +59,7 @@ The behavior of a block inside a model does not depend on other blocks. There ca {{< product-c8y-iot >}} supports MQTT, an OASIS standard messaging protocol, for device integration. -For details see [Device Management > Device integration > Device integration using MQTT](/device-integration/mqtt). +For details see [Device management & connectivity > Device integration > Device integration using MQTT](/device-integration/mqtt). ### Multi-tenancy {#multi-tenancy} diff --git a/content/glossary/o.md b/content/glossary/o.md index 0034bf5fa7..cc3e32f78e 100644 --- a/content/glossary/o.md +++ b/content/glossary/o.md @@ -20,7 +20,7 @@ OPC Unified Architecture (OPC UA) is a standard to enable the communication betw One component of the OPC UA integration in {{< product-c8y-iot >}} is the OPC UA device gateway. The OPC UA device gateway is a stand-alone Java program that communicates with OPC UA server(s) and the {{< product-c8y-iot >}} platform. It stores data into the {{< product-c8y-iot >}} database via REST. The gateway must be registered as {{< product-c8y-iot >}} device. -For details see [Device Management > Protocol integration > OPC UA](/protocol-integration/opcua). +For details see [Device management & connectivity > Protocol integration > OPC UA](/protocol-integration/opcua). ### Operations {#operations} diff --git a/content/standard-tenant/alarm-mapping.md b/content/standard-tenant/alarm-mapping.md index 46a9637425..107b925958 100644 --- a/content/standard-tenant/alarm-mapping.md +++ b/content/standard-tenant/alarm-mapping.md @@ -26,7 +26,7 @@ For easier user access management, the above permissions are included in the glo {{< /c8y-admon-req >}} {{< c8y-admon-related >}} -- [Device Management > Device Management application> Monitoring and controlling devices > Working with alarms](/device-management-application/monitoring-and-controlling-devices/#working-with-alarms) for information on working with alarms in general. +- [Device management & connectivity > Device Management application> Monitoring and controlling devices > Working with alarms](/device-management-application/monitoring-and-controlling-devices/#working-with-alarms) for information on working with alarms in general. - [Alarms](https://{{< domain-c8y >}}/api/core/#tag/Alarms) in the {{< openapi >}} for details on managing alarms via REST. {{< /c8y-admon-related >}} diff --git a/content/standard-tenant/managing-permissions-bundle/improving-performance.md b/content/standard-tenant/managing-permissions-bundle/improving-performance.md index 780f2051ed..95fc2f8fbf 100644 --- a/content/standard-tenant/managing-permissions-bundle/improving-performance.md +++ b/content/standard-tenant/managing-permissions-bundle/improving-performance.md @@ -10,9 +10,9 @@ The {{< product-c8y-iot >}} platform provides optimized UI performance for users The performance of the following UI pages is improved: * In the device details view, the tabs **Info**, **Measurements**, **Alarms**, **Events** and **Control**. -* Pages with aggregated alarm views from multiple devices, if the number of alarms in the system is low, for example, Cockpit > Home dashboard, Cockpit > Alarms and Device Management > Home. -* Pages with aggregated events from multiple devices, if the number of events is low, for example, Device Management > Events. -* Pages with aggregated operations from multiple devices, if the number of operations is low, for example, Device Management > Decie control > Single operations. +* Pages with aggregated alarm views from multiple devices, if the number of alarms in the system is low, for example, Cockpit > Home dashboard, Cockpit > Alarms and Device management & connectivity > Home. +* Pages with aggregated events from multiple devices, if the number of events is low, for example, Device management & connectivity > Events. +* Pages with aggregated operations from multiple devices, if the number of operations is low, for example, Device management & connectivity > Decie control > Single operations. As an administrator, you can disable the performance feature by doing the following: - On platform level via the configuration file (only available for platform administrators, see the *{{< product-c8y-iot >}} - Operations guide* for details). diff --git a/content/standard-tenant/managing-permissions.md b/content/standard-tenant/managing-permissions.md index 0f9467d4b4..6e1708fa5a 100644 --- a/content/standard-tenant/managing-permissions.md +++ b/content/standard-tenant/managing-permissions.md @@ -38,7 +38,7 @@ The above permissions can be used to create roles for robust user management. Ev - [Platform administration > {{< standard-tenant >}} management > Managing users](/standard-tenant/managing-users) for information on managing users in general. - [Platform administration > {{< standard-tenant >}} management > Managing applications](/standard-tenant/ecosystem/#managing-applications) for more information on managing applications. - [Platform administration > {{< enterprise-tenant >}} administration > Managing user hierarchies](/enterprise-tenant/managing-user-hierarchies) for more information on managing user hierarchies. -- [Device Management > Device integration > Fragment library](/device-integration/fragment-library/) for further information on fragment types. +- [Device management & connectivity > Device integration > Fragment library](/device-integration/fragment-library/) for further information on fragment types. - [Roles](https://{{< domain-c8y >}}/api/core/#tag/Roles) and [Inventory Roles](https://{{< domain-c8y >}}/api/core/#tag/Inventory-Roles) in the {{< openapi >}} for managing permissions via REST. - {{< /c8y-admon-related >}} From 4ba27c2d69b2bdc1c4458ce8bef376c6d713a6c3 Mon Sep 17 00:00:00 2001 From: Dafina Karamanoleva <92030501+dafkk@users.noreply.github.com> Date: Thu, 5 Sep 2024 14:19:23 +0300 Subject: [PATCH 03/12] Update content/concepts/concepts-introduction-bundle/device-management.md Co-authored-by: Beate Rixen <90445236+BeateRixen@users.noreply.github.com> --- .../concepts/concepts-introduction-bundle/device-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/concepts/concepts-introduction-bundle/device-management.md b/content/concepts/concepts-introduction-bundle/device-management.md index 7bb998fac1..12b59c002b 100644 --- a/content/concepts/concepts-introduction-bundle/device-management.md +++ b/content/concepts/concepts-introduction-bundle/device-management.md @@ -1,5 +1,5 @@ --- -title: Device Management +title: Device management weight: 40 --- From f683306da9db9d0bb44258db52fb73447536c595 Mon Sep 17 00:00:00 2001 From: Dafina Karamanoleva <92030501+dafkk@users.noreply.github.com> Date: Thu, 5 Sep 2024 14:19:34 +0300 Subject: [PATCH 04/12] Update content/concepts/concepts-introduction.md Co-authored-by: Beate Rixen <90445236+BeateRixen@users.noreply.github.com> --- content/concepts/concepts-introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/concepts/concepts-introduction.md b/content/concepts/concepts-introduction.md index 32fc60ce2b..63183a6bb7 100644 --- a/content/concepts/concepts-introduction.md +++ b/content/concepts/concepts-introduction.md @@ -13,7 +13,7 @@ sector: {{< product-c8y-iot >}} provides * Certified software libraries you can use to bring your remote assets into the cloud. -* Device Management, data visualization and remote control functionality through the web. +* Device management, data visualization and remote control functionality through the web. * Rapid customization of these functionalities through [real-time processing](/concepts/realtime) and [applications](/concepts/applications). * APIs for extending the existing functionality or interfacing {{< product-c8y-iot >}} with your other IT services such as ERP or CRM systems. {{< product-c8y-iot >}} can also host your HTML5 applications. From d33563e4c3966b7ce9adf7dbe84ba46d0f455719 Mon Sep 17 00:00:00 2001 From: Dafina Karamanoleva <92030501+dafkk@users.noreply.github.com> Date: Thu, 5 Sep 2024 14:19:41 +0300 Subject: [PATCH 05/12] Update content/streaming-analytics/analytics-builder-bundle/getting-started.md Co-authored-by: Beate Rixen <90445236+BeateRixen@users.noreply.github.com> --- .../analytics-builder-bundle/getting-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/streaming-analytics/analytics-builder-bundle/getting-started.md b/content/streaming-analytics/analytics-builder-bundle/getting-started.md index 8dca96f94c..cc82e5b415 100644 --- a/content/streaming-analytics/analytics-builder-bundle/getting-started.md +++ b/content/streaming-analytics/analytics-builder-bundle/getting-started.md @@ -113,7 +113,7 @@ A card for the newly added model is shown on the **Models** tab of the model man 1. Click the drop-down menu on the card which currently shows **Draft** and select **Production**. 2. Click the toggle button on the card which currently shows **Inactive**. This changes the state to **Active**. -#### Step 9: Go to the Device Management and view the measurements {#step-9-go-to-the-device-management-and-view-the-measurements} +#### Step 9: Go to the Device Management application and view the measurements {#step-9-go-to-the-device-management-and-view-the-measurements} To view the measurements that are sent from your active model, you must switch to the Device Management application. See [Device Management application](/device-management-application/) for detailed information. From d075d6a8a84cc664daaec4478863649c4d45cfb9 Mon Sep 17 00:00:00 2001 From: Dafina Karamanoleva <92030501+dafkk@users.noreply.github.com> Date: Thu, 5 Sep 2024 14:20:08 +0300 Subject: [PATCH 06/12] Update content/device-integration/mqtt.md Co-authored-by: Beate Rixen <90445236+BeateRixen@users.noreply.github.com> --- content/device-integration/mqtt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/device-integration/mqtt.md b/content/device-integration/mqtt.md index 0a61c58e6f..0e66812969 100644 --- a/content/device-integration/mqtt.md +++ b/content/device-integration/mqtt.md @@ -11,7 +11,7 @@ The MQTT implementation of {{< product-c8y-iot >}} provides the following benefi * Multi-tenancy support: A single endpoint serves multiple tenants. * Device identity management: Devices authenticate using device-specific credentials. * Device registration: Non-personalized devices can be deployed by pairing them with {{< product-c8y-iot >}} tenants. -* Device Management: Rich, pre-defined device management payload formats to enable out-of-the-box management of millions of devices. +* Device management: Rich, pre-defined device management payload formats to enable out-of-the-box management of millions of devices. * Standard IoT payload formats: Pre-defined payload formats to support IoT sensor readings, alarm management, remote control and device hierarchies. * Custom payload formats: Additional payload formats can be added. * Minimum traffic overhead. From da8914114f148660579278a958ebfec919f0af52 Mon Sep 17 00:00:00 2001 From: Dafina Karamanoleva <92030501+dafkk@users.noreply.github.com> Date: Thu, 5 Sep 2024 14:21:30 +0300 Subject: [PATCH 07/12] Update content/protocol-integration/lwm2m-bundle/device-details.md Co-authored-by: Beate Rixen <90445236+BeateRixen@users.noreply.github.com> --- content/protocol-integration/lwm2m-bundle/device-details.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/protocol-integration/lwm2m-bundle/device-details.md b/content/protocol-integration/lwm2m-bundle/device-details.md index 3948b6e0df..b56069efcb 100644 --- a/content/protocol-integration/lwm2m-bundle/device-details.md +++ b/content/protocol-integration/lwm2m-bundle/device-details.md @@ -5,7 +5,7 @@ layout: redirect --- {{< c8y-admon-info >}} -In the Device Management application, you can view all details of a device. The following details are specific to LWM2M devices. For information on general details refer to [Viewing device details](/device-management-application/viewing-device-details) in the Device Management section. +In the Device Management application, you can view all details of a device. The following details are specific to LWM2M devices. For information on general details refer to [Viewing device details](/device-management-application/viewing-device-details). {{< /c8y-admon-info >}} ### Objects {#objects} From 0cc8246116973610e48994be389c528dc35cd03d Mon Sep 17 00:00:00 2001 From: Dafina Karamanoleva <92030501+dafkk@users.noreply.github.com> Date: Thu, 5 Sep 2024 14:21:50 +0300 Subject: [PATCH 08/12] Update content/device-management-application/viewing-device-details.md Co-authored-by: Beate Rixen <90445236+BeateRixen@users.noreply.github.com> --- content/device-management-application/viewing-device-details.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/device-management-application/viewing-device-details.md b/content/device-management-application/viewing-device-details.md index 6827431ec3..9f09cfadf9 100644 --- a/content/device-management-application/viewing-device-details.md +++ b/content/device-management-application/viewing-device-details.md @@ -203,7 +203,7 @@ Only one Y-axis is rendered if the measurements belong to the same series. To see detailed information about the measured values, hover over the chart. A tooltip will be displayed with detailed information on the measurement next to your cursor (the tooltip will "snap" to the closest measurement). {{< c8y-admon-info >}} -We recommend you to have max. 20 series per measurement for optimal performance and readability of a single graph in Device Management (the graph displays all available series). If you need to display only a few series from the measurement, we advise you to use Data explorer in Cockpit where you can select series to be shown in the graph. +We recommend you to have max. 20 series per measurement for optimal performance and readability of a single graph in the Device Management application (the graph displays all available series). If you need to display only a few series from the measurement, we advise you to use Data explorer in Cockpit where you can select series to be shown in the graph. {{< /c8y-admon-info >}} **Time range and aggregation** From 3fff2d463bfc1f6527a88cb66e7b48a8c5098272 Mon Sep 17 00:00:00 2001 From: Dafina Karamanoleva <92030501+dafkk@users.noreply.github.com> Date: Thu, 5 Sep 2024 14:22:06 +0300 Subject: [PATCH 09/12] Update content/glossary/p.md Co-authored-by: Beate Rixen <90445236+BeateRixen@users.noreply.github.com> --- content/glossary/p.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/glossary/p.md b/content/glossary/p.md index 535d75c42e..57a4062085 100644 --- a/content/glossary/p.md +++ b/content/glossary/p.md @@ -23,7 +23,7 @@ See also [General Availability](/glossary/g/#ga) and [Public Preview](/glossary/ ### Product area {#product-area} -In the change logs (or release notes for yearly releases respectively) changes can be filtered for various parameters one of which is the product area. The product area is a high-level functional area, for example, "Device Management & Connectivity". +In the change logs (or release notes for yearly releases respectively) changes can be filtered for various parameters one of which is the product area. The product area is a high-level functional area, for example, "Device management & connectivity". See also [Components](/glossary/c/#components). From 88eb417b154d7dd76bec96c1d5321f9f8619d58f Mon Sep 17 00:00:00 2001 From: Dafina Karamanoleva Date: Thu, 5 Sep 2024 14:28:39 +0300 Subject: [PATCH 10/12] [DM-3890]: PR comments. --- README.md | 2 +- .../support-of-developing-agents.md | 2 +- content/sector/device_management/_index.md | 2 +- .../introduction-analytics.md | 2 +- data/component.json | 16 ++++++++-------- data/productarea.json | 2 +- static/admin/config.yml | 6 +++--- 7 files changed, 16 insertions(+), 16 deletions(-) diff --git a/README.md b/README.md index 6f3f00b153..7b874d7bf9 100644 --- a/README.md +++ b/README.md @@ -111,7 +111,7 @@ weight: 10 # to set the position in the page ## Add content as Markdown or HTML * Certified hardware kits and software libraries you can use to bring your remote assets into the cloud. -* Device Management, data visualization and remote control functionality through the web. +* Device management, data visualization and remote control functionality through the web. * Rapid customization of the above through [real-time processing](/concepts/realtime) and [Cumulocity applications](/concepts/applications). * APIs for extending the existing functionality or interfacing Cumulocity with your other IT services such as ERP or CRM systems. Cumulocity can also host your HTML5 applications. […] diff --git a/content/concepts/interfacing-devices-bundle/support-of-developing-agents.md b/content/concepts/interfacing-devices-bundle/support-of-developing-agents.md index b518868254..78c4eb93df 100644 --- a/content/concepts/interfacing-devices-bundle/support-of-developing-agents.md +++ b/content/concepts/interfacing-devices-bundle/support-of-developing-agents.md @@ -9,6 +9,6 @@ sector: {{< product-c8y-iot >}} supports agent development on three different levels: -* It supports open source agents and drivers, for example [{{< product-c8y-iot >}} Device Management Reference Agent](https://github.com/SoftwareAG/cumulocity-devicemanagement-agent) or [thin-edge.io](https://thin-edge.github.io/thin-edge.io/). +* It supports open source agents and drivers, for example [{{< product-c8y-iot >}} Device management Reference Agent](https://github.com/SoftwareAG/cumulocity-devicemanagement-agent) or [thin-edge.io](https://thin-edge.github.io/thin-edge.io/). * Client libraries for major runtime environments such as C/C++, Java and Lua, again as open source in [github.com](https://github.com/SoftwareAG). * Technology-neutral [REST APIs](/device-integration/device-integration-rest/) for other runtime environments. diff --git a/content/sector/device_management/_index.md b/content/sector/device_management/_index.md index 39737dbf48..42d7b54730 100644 --- a/content/sector/device_management/_index.md +++ b/content/sector/device_management/_index.md @@ -1,5 +1,5 @@ --- -title: "Device Management & Connectivity" +title: "Device management & connectivity" icon: "c8y-icon c8y-icon-device-management" weight: 30 svg: '}}. See [Interfacing devices](/concepts/interfacing-devices/) and [Device integration using MQTT](/device-integration/mqtt/). -Sensors result in `Measurement` or `Event` objects in {{< product-c8y-iot >}}, and devices can receive `Operation` objects created within the {{< product-c8y-iot >}} platform. All of these objects \(`Measurement`, `Event`, `Operation`\) will be associated with a single device in the {{< product-c8y-iot >}} platform. A device may have multiple types of measurement associated with it, and the types of measurements each device supports may be the same as other devices or different to other devices. Once devices are connected to {{< product-c8y-iot >}}, information about these devices is stored in the {{< product-c8y-iot >}} inventory. These are visible in the Device Management application, which can also be used to view `Measurement`, `Event` or `Operation` objects associated with that device. See [Device Management](/section/device_management/) for more information. +Sensors result in `Measurement` or `Event` objects in {{< product-c8y-iot >}}, and devices can receive `Operation` objects created within the {{< product-c8y-iot >}} platform. All of these objects \(`Measurement`, `Event`, `Operation`\) will be associated with a single device in the {{< product-c8y-iot >}} platform. A device may have multiple types of measurement associated with it, and the types of measurements each device supports may be the same as other devices or different to other devices. Once devices are connected to {{< product-c8y-iot >}}, information about these devices is stored in the {{< product-c8y-iot >}} inventory. These are visible in the Device Management application, which can also be used to view `Measurement`, `Event` or `Operation` objects associated with that device. See [Device management & connectivity](/section/device_management/) for more information. Using the Streaming Analytics application, you can add your own logic to your IoT solution for immediate processing of incoming data from devices or other data sources. These user-defined operations can, for example, alert applications of new incoming data, create new operations based on the received data (such as sending an alarm when a threshold for a sensor is exceeded), or trigger operations on devices. diff --git a/data/component.json b/data/component.json index 48ce30ebf2..30428d25f3 100644 --- a/data/component.json +++ b/data/component.json @@ -86,7 +86,7 @@ "product_area": [ { "value": "product_area-m1iHjqikD", - "label": "Device Management & Connectivity" + "label": "Device management & connectivity" } ] }, @@ -96,7 +96,7 @@ "product_area": [ { "value": "product_area-m1iHjqikD", - "label": "Device Management & Connectivity" + "label": "Device management & connectivity" } ] }, @@ -106,7 +106,7 @@ "product_area": [ { "value": "product_area-m1iHjqikD", - "label": "Device Management & Connectivity" + "label": "Device management & connectivity" } ] }, @@ -116,7 +116,7 @@ "product_area": [ { "value": "product_area-m1iHjqikD", - "label": "Device Management & Connectivity" + "label": "Device management & connectivity" } ] }, @@ -126,7 +126,7 @@ "product_area": [ { "value": "product_area-m1iHjqikD", - "label": "Device Management & Connectivity" + "label": "Device management & connectivity" } ] }, @@ -136,7 +136,7 @@ "product_area": [ { "value": "product_area-m1iHjqikD", - "label": "Device Management & Connectivity" + "label": "Device management & connectivity" } ] }, @@ -146,7 +146,7 @@ "product_area": [ { "value": "product_area-m1iHjqikD", - "label": "Device Management & Connectivity" + "label": "Device management & connectivity" } ] }, @@ -156,7 +156,7 @@ "product_area": [ { "value": "product_area-m1iHjqikD", - "label": "Device Management & Connectivity" + "label": "Device management & connectivity" } ] }, diff --git a/data/productarea.json b/data/productarea.json index a6259983bd..2bb9dffede 100644 --- a/data/productarea.json +++ b/data/productarea.json @@ -9,7 +9,7 @@ "id": "product_area-eC7h0SiQ2b" }, { - "option": "Device Management & Connectivity", + "option": "Device management & connectivity", "id": "product_area-m1iHjqikD" }, { diff --git a/static/admin/config.yml b/static/admin/config.yml index 359da87906..3ae077a047 100644 --- a/static/admin/config.yml +++ b/static/admin/config.yml @@ -113,15 +113,15 @@ collections: - { label: "Body", name: "body", widget: "markdown"} - name: "device_management" - label: "Device Management & Connectivity" + label: "Device management & connectivity" folder: "content/change-logs/device-management" - description: "Change log entries for the Device Management & Connectivity product area" + description: "Change log entries for the Device management & connectivity product area" create: true slug: "{{fields.build_artifact.0.label}}-{{fields.version}}-{{slug}}" fields: - {label: "Date",name: "date",widget: "datetime", format: "YYYY-MM-DD", default: "", required: false} - {label: "Title", name: "title", widget: "string"} - - {label: "Product area", name: "product_area", widget: "hidden", default: "Device Management & Connectivity"} + - {label: "Product area", name: "product_area", widget: "hidden", default: "Device management & connectivity"} - label: Change type name: change_type widget: ncw-file-relation From 40aea176c6016c17357f4e453533fb2038379294 Mon Sep 17 00:00:00 2001 From: Beate Rixen <90445236+BeateRixen@users.noreply.github.com> Date: Thu, 12 Sep 2024 11:12:20 +0200 Subject: [PATCH 11/12] Update content/concepts/interfacing-devices-bundle/support-of-developing-agents.md --- .../interfacing-devices-bundle/support-of-developing-agents.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/concepts/interfacing-devices-bundle/support-of-developing-agents.md b/content/concepts/interfacing-devices-bundle/support-of-developing-agents.md index 78c4eb93df..b518868254 100644 --- a/content/concepts/interfacing-devices-bundle/support-of-developing-agents.md +++ b/content/concepts/interfacing-devices-bundle/support-of-developing-agents.md @@ -9,6 +9,6 @@ sector: {{< product-c8y-iot >}} supports agent development on three different levels: -* It supports open source agents and drivers, for example [{{< product-c8y-iot >}} Device management Reference Agent](https://github.com/SoftwareAG/cumulocity-devicemanagement-agent) or [thin-edge.io](https://thin-edge.github.io/thin-edge.io/). +* It supports open source agents and drivers, for example [{{< product-c8y-iot >}} Device Management Reference Agent](https://github.com/SoftwareAG/cumulocity-devicemanagement-agent) or [thin-edge.io](https://thin-edge.github.io/thin-edge.io/). * Client libraries for major runtime environments such as C/C++, Java and Lua, again as open source in [github.com](https://github.com/SoftwareAG). * Technology-neutral [REST APIs](/device-integration/device-integration-rest/) for other runtime environments. From 3bcf282e80119fd53907f1804bf4d86fb96ebbc0 Mon Sep 17 00:00:00 2001 From: Beate Rixen <90445236+BeateRixen@users.noreply.github.com> Date: Thu, 12 Sep 2024 11:12:26 +0200 Subject: [PATCH 12/12] Update content/standard-tenant/managing-permissions-bundle/improving-performance.md --- .../managing-permissions-bundle/improving-performance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/standard-tenant/managing-permissions-bundle/improving-performance.md b/content/standard-tenant/managing-permissions-bundle/improving-performance.md index 95fc2f8fbf..68668d3c6f 100644 --- a/content/standard-tenant/managing-permissions-bundle/improving-performance.md +++ b/content/standard-tenant/managing-permissions-bundle/improving-performance.md @@ -12,7 +12,7 @@ The performance of the following UI pages is improved: * In the device details view, the tabs **Info**, **Measurements**, **Alarms**, **Events** and **Control**. * Pages with aggregated alarm views from multiple devices, if the number of alarms in the system is low, for example, Cockpit > Home dashboard, Cockpit > Alarms and Device management & connectivity > Home. * Pages with aggregated events from multiple devices, if the number of events is low, for example, Device management & connectivity > Events. -* Pages with aggregated operations from multiple devices, if the number of operations is low, for example, Device management & connectivity > Decie control > Single operations. +* Pages with aggregated operations from multiple devices, if the number of operations is low, for example, Device management & connectivity > Device control > Single operations. As an administrator, you can disable the performance feature by doing the following: - On platform level via the configuration file (only available for platform administrators, see the *{{< product-c8y-iot >}} - Operations guide* for details).