Download lagu ibu pertiwi. Overview Profiles and Plug-ins form the basis of most DataWedge functionality. Profiles include all the information about how DataWedge should behave when providing scanning services for a particular application.

DataWedge allows you to easily capture data via the integrated barcode scanner, camera and NFC, as well as attached peripherals, including magnetic stripe.

Much of that information comes from Plug-ins, which determine how the data will be input, processed and output. Each Profile generally contains four elements: • An Input Plug-in - to determine how data will be acquired (i.e. A barcode scanner) • A Process Plug-in - to specify how the acquired data should be manipulated • An Output Plug-in - to control the passing of data to an application • An associated application - (or activity) with which to link DataWedge actions When associated with an app, DataWedge can be invoked to scan and acquire the data, format or append it in a specified way, and pass it to the associated app when the app comes to the foreground. DataWedge also includes Profile0, which works with any unassociated application that comes to the foreground. Profile0 contains baseline settings that can be tailored to suit individual needs. This allows DataWedge to be used out of the box with little or no setup.

Important: Control of barcode scanning hardware is exclusive. When DataWedge is active, Scanner and Barcode APIs of apps such as Enterprise Browser and others will be inoperative. Likewise, when an app such as Enterprise Browser controls the scanning hardware, other apps (including DataWedge) are locked out. It is therefore important to understand how to take control of a device's scanner hardware and, if necessary, release it to other apps when scanning is complete.

For more information, see Disable DataWedge section. Profiles A DataWedge Profile contains information about how DataWedge should behave with one or more associated applications, and provides a means to allow different apps that might be acquiring the same data to do different things with it. For example, while 'App A' might require that a TAB be sent after each dataset is passed from DataWedge, 'App B' might require the ENTER key to be pressed instead. Through Profiles, DataWedge can be configured to process the same set of captured data according to the requirements of any number of individual applications. Alternatively, a single Profile can be created and associated with many applications, acquiring and processing data in exactly the same way for all. Any number of Profiles can be created to suit all the needs of an enterprise. DataWedge also includes several pre-configured Profiles to support general needs or for specific apps that are built into every device.

Some of these, such as Profile0, are visible to the user and can be edited as needed. Others contain fixed parameters and are not visible or configurable.

Visible Profiles • Profile0 - is a generic that takes effect for any unassociated foreground app. • Launcher - is used when the Launcher screen is in the foreground. • DWDemo - is used with DWDemo, the app.

When DWDemo comes to the foreground, data captured with DataWedge is handed to the DWDemo application. • User-defined - profiles are always visible and available for editing.

Hidden Profiles • RD Client - provides support for Zebra's Rapid Deploy app and third-party MDM solutions. • MSP Agent - provides support for Zebra's legacy Mobility Services Platform (MSP). • MspUserAttribute - provides additional support for MSP. • Camera - disables scanning when the default camera application is in the foreground. • RhoElements - disables scanning when RhoElements is in the foreground. Profile0 Profile0 is a generic Profile that automatically takes effect for any app that comes to the foreground that has not been associated with DataWedge.

This can be useful for quickly acquiring data using an app that has just been installed, for example, or when using an app that has not yet been configured by an administrator for use with DataWedge. All parameters of Profile0 can be edited except its association.

Profile0 also can be disabled within a Profile. This provides a measure of security by restricting output to applications or servers to which DataWedge has been specifically associated. Plug-ins Plug-ins extend DataWedge functionality to support device hardware, peripherals, data processing and transport. Plug-ins are used to configure how data will be acquired by DataWedge, manipulated or altered for an app, and output to an app or server.