Peripheral Input/Output Services Architecture 

Purpose

These services provided by SAP NetWeaver Mobile to provide peripheral access to mobile applications. PIOS provides an abstraction layer between the application and the peripheral. A developer using PIOS does not need to be concerned about the implementation details of each peripheral model supported. Instead the developer targets abstracted functionality provided by the peripheral and required by the application.

Integration

The PIOS architecture has design components, runtime components, and an administration component. The design time components are integrated into the SAP NetWeaver Developer Studio. Runtime components and the administration component are integrated into the SAP NetWeaver Mobile client and the SAP NetWeaver Mobile Administrator respectively.

Design-time components

●      Peripheral Support Emulator Actions - SAP NetWeaver Developer Studio toolbar components that are used to emulate the peripheral features required by a mobile application

○       Open the Emulator Launch Configurations Manager – Allows the developer to browse and select a created launch configuration and modify it in order to launch it with support for the Peripheral I/O Emulator.

○       Launch the Peripheral I/O Emulator - Launches the Peripheral I/O Emulator

●      Peripheral Emulator -Emulates peripheral functionality according to settings determined by the developer

Runtime components

●      PIOS Classes in the SAP NetWeaver Mobile client - Used to find, connect, and use functionality available in supported peripheral types

●      Mobile Driver Component - Component containing the software modules required to make use of a specific peripheral model on a client device

Example

The following diagram provides an overview of the PIOS architecture:

 

More Information

For more information about the Peripheral Input/Output Services Architecture and answers to frequently asked questions, refer to SAP Note 853397.