Performing Administrative Tasks on a Single Device 

Procedure

You do not need to perform the following steps in a sequence.

...

       1.      You can assign additional mobile components to the device based on your requirements. For example, to enable application users to print data from their respective mobile applications, you must assign the required printer driver.

More information: Assigning Mobile Components to a Device

       2.      You can assign additional distribution model (DM) software component versions to a device based on your requirements.

You migrate a device from Mobile Infrastructure (MI) to the Data Orchestration Engine (DOE). Then, you roll out this device with the Mobile Asset Management (MAM) application. Later, you deploy a Sales Order application on this device. To ensure that the data related to the Sales Order application is transferred to the device, you must assign the corresponding DM software component version to the device.

More information: Assigning DM Software Component Versions to a Device

       3.      If the data objects associated with a device are not enabled for synchronization, then you must manually extract data for that particular device in the Data Orchestration Engine (DOE).

All the data objects in the production environment are enabled for synchronization. In the test environment, you may not sync enable some of the data objects for test purposes. For example, you want to count the number of data object instances that are transferred to a device when you trigger data extract for that particular device. In this case, you must not set the status of the data objects associated with the specified device as sync enabled.

More information: Extracting Data for a Device

       4.      If a distribution rule has not been assigned to any device during design time, you can assign a rule manually to a device based on your requirements.

More information: Assigning Rules to a Device

       5.      You must assign users to a device to ensure that only authorized users can use the device to exchange data with the DOE.

More information: Assigning Users to a Device

       6.      A device profile allows you to logically group mobile components, DM software component versions, and configuration templates. You can assign device profiles to a device based on your requirements.

If you want to roll out 100 devices in Europe with two applications, Application A and Application B, and another 100 devices in Asia with two applications, Application C and Application D, then you can:

                                                  i.       Create a device profile, Device Profile A and assign the two applications, Application A and Application B.

                                                ii.       Create a device profile, Device Profile B and assign the two applications, Application C and Application D.

                                               iii.       Assign Device Profile A to the 100 devices in Europe.

                                               iv.       Assign Device Profile B to the 100 devices in Asia.

This ensures that you do not have to assign the applications individually to each of the 200 devices.

More information: Assigning Device Profiles to a Device

       7.      In the production environment, if the data objects are sync enabled, it can have an impact on performance. Therefore, you can configure the behavior of queue refresh when a device connects to the data orchestration engine (DOE) to synchronize data.

More information: Configuring Queue Refresh