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.
- Profile0 - is a generic Profile that takes effect for any unassociated foreground app.
- Launcher - is the Profile used when the Launcher screen is in the foreground.
- DWDemo - contains settings for DWDemo, the DataWedge Demo app app. When DWDemo comes to the foreground, data captured with DataWedge is handed to the DWDemo application and displayed in a window on the device.
- User-defined - Profiles are always visible, can be associated with one or more apps, and can be edited as needed.
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. This provides a measure of security by restricting output to applications or servers to which DataWedge has been specifically associated.
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.
Input Plug-ins specify:
- Barcode scanners (laser, imager, camera, Bluetooth scanner)
- Data Capture Plus (DCP)
- Magnetic Stripe Readers (MSR)
- Radio-frequency Identification (RFID)
- Serial port(s)
- SimulScan hardware
Process Plug-ins specify:
- Basic data formatting (append with keystrokes, prefix, suffix, etc.)
- Advanced data formatting (rules-based data manipulation)
Output Plug-ins specify:
- Keystrokes (emulates manual keyboard input)
- Intent (programmatic hand-off of data)
- IP Output (sending data to a server over IP)