4 - 2 TC75 Integrator Guide
Profiles
DataWedge is based on profiles and plug-ins. A profile contains information on how DataWedge should behave
with different applications.
Profile information consists of:
• Associated application
• Input plug-in configurations
• Output plug-in configurations
• Process plug-in configurations.
Using profiles, each application can have a specific DataWedge configuration. For example, each user application
can have a profile which outputs scanned data in the required format when that application comes to the
foreground. DataWedge can be configured to process the same set of captured data differently based on the
requirements of each application.
DataWedge includes the following visible and hidden pre-configured profiles which support specific built-in
applications:
• Visible profiles:
•Profile0 - created automatically the first time DataWedge runs. Generic profile used when there are no
user created profiles associated with an application.
• Launcher - enables scanning when the Launcher is in foreground. Note: to save battery power, disable
this profile when not required.
•DWDemo - provides support for the DWDemo application.
• Hidden profiles (not shown to the device):
• RD Client - provides support for MSP.
•MSP Agent - provides support for MSP.
• MspUserAttribute - provides support for MSP.
•Camera - disables scanning when the default camera application is in foreground.
• RhoElements - disables scanning when RhoElements is in foreground.
•StageNow - provides support for the StageNow application.
Profile0
Profile0 can be edited but cannot be associated with an application. That is, DataWedge allows manipulation of
plug-in settings for Profile0 but it does not allow assignment of a foreground application. This configuration allows
DataWedge to send output data to any foreground application other than applications associated with user-defined
profiles when Profile0 is enabled.
Profile0 can be disabled to allow DataWedge to only send output data to those applications which are associated
in user-defined profiles. For example, create a profile associating a specific application, disable Profile0 and then
scan. DataWedge only sends data to the application specified in the user-created profile. This adds additional
security to DataWedge enabling the sending of data only to specified applications.