Driver Configuration 

Purpose

Peripheral Input Output Services (PIOS) drivers can be configured by modifying several parameters. Parameters are defined for different configurations, and configurations are divided into configuration types. The system administrator can modify configuration parameters with the SAP NetWeaver Mobile Administrator.

Implementation Considerations

Mobile driver component parameters are created with four tokens. The tokens are driver name, configuration type, configuration name, and parameter. When you modify the driver parameters, you must follow this naming convention:

<driver name>.<configuration type>.<configuration name>.<parameter>=value

Tokens and values are case-sensitive. To change a parameter value, you must enter the correct name in the NetWeaver Mobile Administrator configuration.

Integration

Use the SAP NetWeaver Mobile Administrator to configure and assign drivers. The PIOS Configuration Agent together with Agent Framework and DOE enable administrators to assign values to configuration parameters of PIOS drivers in client devices.

Features

Several parameters can be used to change options for a driver. These parameters are defined for configurations that are separated into configuration types. PIOS drivers use the driver configuration type (cfg) to store parameters that modify how drivers connect to peripherals. This configuration type is also used to store parameters that are specific from driver to driver. Another configuration type is used to store the font configuration parameters (fntcfg) for the Printer peripheral type. This configuration type (fntcfg) is used to configure fonts supported by the driver.

System administrators can modify driver configuration and font configuration parameters with the SAP NetWeaver Mobile Administrator.

Constraints

●      Adding a font with the font configuration parameters does not install the font on the physical printer. Printer fonts must be installed manually on the printer and must match the configured parameters.

●      There is no validation check when you apply driver configuration values. You must configure a driver properly to ensure expected behavior.

Example

Examples of driver parameter configuration and font configuration parameters follow:

●      This example shows a driver configuration parameter for the piprsymmf4t (Symbol microFlash 4t) printer driver. This line sets the serial port baud rate to 9600 bits per second:

piprsymmf4t.cfg.Serial.BaudRate=9600

●      This example shows a modified font configuration parameter for the piprmswin32 (Microsoft Windows 32-bit) printer driver. This line sets the bitmapped bold italic font options to bold and italic:

piprmswin32.fntcfg.BitmappedBoldItalic.Options=bold,italic

More Information

You can find a list of all available parameters in an SAP note for each driver. For a list of available drivers, refer to the collective SAP Note 761833.