Device Profile

You can create the following types of device profiles:

Application

A device profile of type application is a logical grouping of the following:

Mobile components
- Applications to be installed on the device
- Framework to be installed on the device
- Database to be installed on the device
- Add-ons, patches or upgrades to be deployed on the device
- Agents to be deployed on the device

DM Software component versions
Agent Configurations

If you want to create a set of devices that must have specific mobile components, DM software component versions, or agent configurations, then you can:

Create a device profile
Assign the required mobile components, DM SWCVs, or agent configurations to the device profile
Assign the device profile to the required devices

This ensures that you do not have to assign the mobile components, agent configurations, or DM SWCVs to each device individually.

Example Example

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:

Create a device profile, Device Profile A and assign the two applications, Application A and Application B.
Create a device profile, Device Profile B and assign the two applications, Application C and Application D.
Assign Device Profile A to the 100 devices in Europe.
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.

End of the example.

Framework

A device profile of type framework contains client configuration information, such as DB cache size, DB log size, path for client installation, and so on. Therefore, to ensure that this information is transferred to devices, you must create a device profile of type framework and assign it to the required devices.