HowTo Config PDA Devices

8/3/2019 HowTo Config PDA Devices

1/22

How-to GuideSAP Mobile Business Solutions

Configure Peripherals with Mobile Infrastructure

How ToConfigurePeripheral Driverswith Mobile

InfrastructureVersion 1.00 January 2007

Applicable Releases:Mobile Infrastructure MI 2.5


2/22

Copyright 2006 SAP AG. All rights reserved.

SAP Library document classification: PUBLIC

No part of this publication may be reproduced or transmitted in

any form or for any purpose without the express permission of

SAP AG. The information contained herein may be changed

without prior notice.

Some software products marketed by SAP AG and its

distributors contain proprietary software components of other

software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,

MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,

WebSphere, Netfinity, Tivoli, and Informix are trademarks or

registered trademarks of IBM Corporation in the United States

and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of

the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered

trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered

trademarks of W3C, World Wide Web Consortium,

Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc.,

used under license for technology invented and implemented by

Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP

NetWeaver, and other SAP products and services mentioned

herein as well as their respective logos are trademarks or

registered trademarks of SAP AG in Germany and in several

other countries all over the world. All other product and service

names mentioned are the trademarks of their respective

companies. Data contained in this document serves information

purposes only. National product specifications may vary.

These materials are subject to change without notice. These

materials are provided by SAP AG and its affiliated companies

("SAP Group") for informational purposes

only, without representation or warranty of any kind, and SAP

Group shall not be liable for errors or omissions with respect to

the materials. The only warranties for SAP Group products and

services are those that are set forth in the express warranty

statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additional

warranty.

These materials are provided as is without a warranty of any

kind, either express or implied, including but not limited to, the

implied warranties of merchantability, fitness for a particular

purpose, or non-infringement.

SAP shall not be liable for damages of any kind including

without limitation direct, special, indirect, or consequential

damages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the

information, text, graphics, links or other items contained within

these materials. SAP has no control over the information that

you may access through the use of hot links contained in thesematerials and does not endorse your use of third party web pages

nor provide any warranty whatsoever relating to third party web

pages.

SAP NetWeaver How-to Guides are intended to simplify the

product implementation. While specific product features and

procedures typically are explained in a practical business

context, it is not implied that those features and procedures are

the only approach in solving a specific business problem using

SAP NetWeaver. Should you wish to receive additional

information, clarification or support, please refer to SAP

Consulting.

Any software coding and/or code lines / strings (Code)

included in this documentation are only examples and are notintended to be used in a productive system environment. The

Code is only intended better explain and visualize the syntax and

phrasing rules of certain coding. SAP does not warrant the

correctness and completeness of the Code given herein, and SAP

shall not be liable for errors or damages caused by the usage of

the Code, except if such damages were caused by SAP

intentionally or grossly negligent.


3/22

1 Scenario...................................................................................................................1

2 Introduction.............................................................................................................1

2.1 Overview of Steps............................................................................................1

3 Step-by-Step Solution..............................................................................................3

3.1 Review related notes and upload drivers and connectors ..................................3

3.2 Configuring Peripherals with the NetWeaver Administrator.............................43.3 Configuring Peripherals with the WebConsole.................................................8

3.4 Configuring Bluetooth Printers from a Device ...............................................16

4 Appendix...............................................................................................................17

4.1 Naming Convention for Peripheral Driver Name............................................17

4.2 Naming Convention for Drivers and Connectors Add-Ons .............................18

4.3 Troubleshooting.............................................................................................18

4.3.1 Installation Errors...................................................................................18

4.3.2 Functionality Errors................................................................................18


4/22

- 1 -

1 Scenario

When implementing a mobile solution, the application may be more useful with the addition of aperipheral device, such as a printer, RFID reader or a barcode scanner. Installing the necessary

drivers and configuring them is a necessity in order to enable them to work properly. Specifically, thisguide will demonstrate how to configure a Symbol MF4T Bluetooth printer. Similar steps will need tobe followed to install and configure other peripheral devices.

The Troubleshooting section contains commonly encountered errors when installing any type ofperipheral.

2 Introduction

There are several steps required to install and configure peripheral drivers. It is necessary to upload

the drivers to the WebConsole/NetWeaver Administrator as well as the driver Connector. Both arenecessary in order for the peripheral drivers to function correctly.

In addition, certain peripheral drivers also require initial configuration before the peripheral driver willwork correctly. In the case of Bluetooth printers, you must configure the address of the Bluetooth towhich the device will print. This is an important consideration when choosing a Bluetooth printer.Although they are very easy to use once they are configured, this configuration takes time and needsto be considered as a necessary part of your mobile implementation with adequate time reserved toconfigure the devices.

The place to begin with configuring peripheral drivers is to review the composite CSS Note 761833.This note contains links to all release notes of supported drivers. Beginning with Mobile Infrastructure2.5 SP19, there will also be a pre-configuration section in the release note. This pre-configurationsection will specify any initial parameters that must be configured for the peripheral driver to functioncorrectly.

Be aware that for some drivers to communicate with the peripheral hardware, additional configurationmay be required for the hardware. For example to communicate a printer driver via serial, the baudrate configuration for the driver has to match the hardware baud rate. To change the hardwareconfiguration please read the peripherals documentation.

2.1 Overview of Steps

Depending on your system configuration and peripheral driver, the steps taken to enable it will vary.Please follow the steps as directed, based on your hardware setup and how you plan to configure theperipheral driver.

For example, there are two parameters that must be configured for the Symbol MF4T printer driver toprint using Bluetooth. These parameters are piprsymmf4t.cfg.Bluetooth.Peer andpiprsymmf4t.cfg.Bluetooth.PeerType. The possible values for PeerType parameter are either Nameor Address. The piprsymmf4t.cfg.Bluetooth.Peer parameter is set to printer_name by default andneeds to be set to the name or the address of the associated Bluetooth printer depending on thePeerType value. If the PeerType is set to Name then Peers value should be the printers Bluetoothname. If PeerType value is set to Address then Peers value should be the printers Bluetoothaddress.


5/22

- 2 -

This configuration can be done centrally via the WebConsole or the NetWeaver Administrator ordirectly on the device. It is recommended that you configure the peripheral drivers centrally. Onceyou perform the configuration directly on the device, you cannot modify that configuration centrally inthe future.


6/22

- 3 -

3 Step-by-Step Solution

3.1 Review related notes and upload drivers and connectors

1. Review Note 761833 DeliveredDrivers for Peripherals in SAP MI. Thisnote tells you where to find the driversand also includes all of the releasenotes for any supported device.

2. This note also contains release notes forall supported drivers. Find the relatedrelease note for the peripheral driver tobe configured. In this case, we willconfigure the Symbol MF4T printer, sowe will review the PIPRSYMMF4Trelease note.

For an explanation of the namingconvention, please refer to theAppendix of this document.


7/22

- 4 -

3. Review the Required Hardware andSoftware section of the release note toensure that you are using the correctversion of the driver. If yourhardware/software settings do notmatch these requirements, then you will

need to go back to select theappropriate release note for your currentsettings.

4. Download the appropriate driver as

indicated in Note 761833 for yourcurrent Mobile Infrastructure SP.

5. Upload the driver and connector to theWebConsole or the NetWeaverAdministrator as described in theinstallation guides.

3.2 Configuring Peripherals with the NetWeaver Administrator

1. Create a parameter set.

2. Under Mobile Infrastructure, selectParameter Sets from the left menu.Select Configuration Parameter Setsfor MI 7.0.

3. Click on the Create button under

Configuration Parameter Sets.


8/22

- 5 -

4. Enter the name and description of theparameter set. Then, click on theCreate button.

5. Click on the Edit button.

6. Enter MI_PIOS as the Parameter Set

Type on the Details tab below.

7. Click on the Parameters tab.

8. Click on the Add button.

9. Enterpiprsymmf4t.cfg.Bluetooth.Peer inthe Parameter Name column.

10. In the Parameter Value column, enterthe printer Bluetooth name or address.


9/22

- 6 -


12. Enterpiprsymmf4t.cfg.Bluetooth.PeerType inthe Parameter Name column.

13. Enter Address or Namecorresponding to the value entered forparameter Peer.

14. Click on the Save button.

15. Create a Device Configuration. Select

Device Configuration from the leftmenu.

16. Click on the Create button.

17. Enter the Device Configuration Nameand Description.


19. Click on the Parameter Sets tab below.


10/22

- 7 -

20. Click on the Add/Remove button onthe Parameter Sets tab.

21. Click on the Search button.

22. Select the Parameter Set you createdabove.

23. Select the >> button to move theParameter set to the AssignedParameter Sets column.



11/22

- 8 -

25. You can then assign the deviceconfiguration to a device as describedin the installation guide.

3.3 Configuring Peripherals with the WebConsole

1. Before you can deploy a configuration toa device, you need to create it first fromwithin your middleware (WebAS)system. Start transactionDEVICE_CONFIG.

2. In the Configuration of MonitoringFunctions section, enter the MonitoringConfiguration name and Description,and then click on the Create button.Please note that the MonitoringConfiguration name as well as thedescription cannot include spaces.


12/22

- 9 -

3. In the Monitoring Function column,select MI_PIOS for Configuration of theExternal Devices.

4. Put your cursor in the Parameter ID fieldand open the selection list.

5. Since we are configuring a Symbol

MF4T printer, scroll down until thebeginning of the piprsymmf4t.cfgparameters.


13/22

- 10 -

6. Select thepiprsymmf4t.cfg.Bluetooth.Peerparameter.

7. In the Parameter Value column, enterthe printer Bluetooth name or address.

8. One the next line, enter MI_PIOS in the

Monitoring Function column.


14/22

- 11 -

9. Scroll down until the beginning of thepiprsymmf4t.cfg parameters. Select thepiprsymmf4t.cfg.Bluetooth.PeerTypeparameter.

10. Enter Address or Namecorresponding to the value entered for

parameter Peer.11. Click on the Save button.

12. Next, in the Configuration of Mobile

Device section, create a Configurationof Mobile Device.

13. Enter the Device Configuration nameand Description.



15/22

- 12 -

15. In the Monitoring Functions tab, put yourcursor in the Monitoring Configurationcolumn and click on the pull downmenu.

16. Select the Monitoring Configuration youcreated in the previous steps.



16/22

- 13 -

18. To assign the Device Configuration toyour user, open the WebConsole.

19. In the Administer Mobile Devicessection, under the top Administrationtab, click on the Add Entries button.

20. Enter the user.

21. Select the pull down menu for themobile component

22. Click on the arrow next to Mobile

Component to close this section


17/22

- 14 -

23. Click on Device Configuration to openthis section.

24. Select the Device Configuration youcreated in the previous steps.


18/22

- 15 -

25. You can then select a particular device,or add the configuration to all devicesfor this user.


27. This configuration will now be deployedto the user on the next synchronization.


19/22

- 16 -

3.4 Configuring Bluetooth Printers from a Device

1. The following Bluetooth setup screensbelong to an Intermec device running a

Microsoft Bluetooth stack. While thisprocess can vary from device to device,this screen flow will show you thegeneral process to configuring theBluetooth printer from a device.

On the Mode tab, select the On option,then select the Wireless Printing tab.

2. Click on the Device Discovery button,then highlight the Device in question inthe Devices list box and click on theConnect button.


20/22

- 17 -

3. Choose the COM Port and check theEnable Wireless Printing checkbox.You can then print a test page from yourdevice.

4 Appendix

4.1 Naming Convention for Peripheral Driver Name

Peripheral names look like PIPRSYMMF4T. The first two characters of the peripheral name refer tothe type of service used for peripheral input and output. PIOS (Peripheral Input/Output Services) isthe only type of service supported at this time, so all driver names begin with the letters PI.

The next two characters of the peripheral name refer to the type of peripheral the driver represents.These include PR (printer), SC (scanner) and RF (RFID reader).


21/22

- 18 -

The next three characters of the peripheral name refer to the manufacturer of the device. Theseinclude INT (Intermec), SYM (Symbol), SKT (Socket) and MS (Microsoft desktop driver).

The last characters of the name refer to the device model, such as 6808, 750, MF4T, etc.

In the example of PIPRSYMMF4T, PI refers to PIOS, PR means printer, SYM means themanufacturer is Symbol, and the device model is MF4T.

4.2 Naming Convention for Drivers and Connectors Add-OnsAn example of a driver name is piprsymmf4t_ppc03_xsc_crm_1_1_4.

Driver names begin with the peripheral name as described above. The next section (ppc03 forPocketPC 2003 in this case) refers to the operating system of the client device. The next sectionrefers to the processor type used on the client device (xsc for XSCALE processor in this case). Thenext section refers to the Java Virtual Machine that is used on the device (crm for CreMe in thiscase). The last section refers to the version of the driver.

The connector is named in the same way, except the prefix is CONNECTOR instead of the peripheral

name.

4.3 Troubleshooting

If the peripheral does not work after installation and configuration it, check the jscpout.txt file. This filecan be found in the root folder of your device. The following are common errors found in the

jscpout.txt file.

4.3.1 Installation Errors

Error Solution

Unable to Load Library/Unsatisfied Link Error You installed a Socket driver without enhancingthe driver with the necessary third party softwareas described in the release note for these drivers.These drivers require third party software thatSAP does not deliver. Please refer to the releasenote for your selected driver and refer to theSpecial Installation Instructions section of therelease note for details on including the additionalfiles from the Socket Communications SDK.

Unable to Install PIOS Driver Error is resolved with SP19 in NetWeaver 2004or SP09 in NetWeaver 2004S.

4.3.2 Functionality Error

This error can occur after the installation of the peripheral is successful.

Error Solution

Unable to Print Job This error occurs when the peripheral is notconfigured correctly. For example, you will seethis error if you do not configure the MF4T Peerand PeerType configuration parameters asdescribed above.


22/22

www.sap.com/mobile

Documents

HowTo Config PDA Devices