Вы находитесь на странице: 1из 22

How-to Guide SAP Mobile Business Solutions Configure Peripherals with Mobile Infrastructure

How To Configure Peripheral Drivers with Mobile Infrastructure


Version 1.00 January 2007 Applicable Releases: Mobile Infrastructure MI 2.5

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 these materials 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 not intended 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.

1 2

Scenario...................................................................................................................1 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.............................4 3.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

1 Scenario
When implementing a mobile solution, the application may be more useful with the addition of a peripheral 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, this guide will demonstrate how to configure a Symbol MF4T Bluetooth printer. Similar steps will need to be followed to install and configure other peripheral devices. The Troubleshooting section contains commonly encountered errors when installing any type of peripheral.

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 are necessary in order for the peripheral drivers to function correctly. In addition, certain peripheral drivers also require initial configuration before the peripheral driver will work correctly. In the case of Bluetooth printers, you must configure the address of the Bluetooth to which 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 needs to be considered as a necessary part of your mobile implementation with adequate time reserved to configure 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 Infrastructure 2.5 SP19, there will also be a pre-configuration section in the release note. This pre-configuration section will specify any initial parameters that must be configured for the peripheral driver to function correctly. Be aware that for some drivers to communicate with the peripheral hardware, additional configuration may be required for the hardware. For example to communicate a printer driver via serial, the baud rate configuration for the driver has to match the hardware baud rate. To change the hardware configuration 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 the peripheral driver. For example, there are two parameters that must be configured for the Symbol MF4T printer driver to print using Bluetooth. These parameters are piprsymmf4t.cfg.Bluetooth.Peer and piprsymmf4t.cfg.Bluetooth.PeerType. The possible values for PeerType parameter are either Name or Address. The piprsymmf4t.cfg.Bluetooth.Peer parameter is set to printer_name by default and needs to be set to the name or the address of the associated Bluetooth printer depending on the PeerType value. If the PeerType is set to Name then Peers value should be the printers Bluetooth name. If PeerType value is set to Address then Peers value should be the printers Bluetooth address.

-1-

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

-2-

3 Step-by-Step Solution
3.1
1.

Review related notes and upload drivers and connectors


Review Note 761833 Delivered Drivers for Peripherals in SAP MI. This note tells you where to find the drivers and also includes all of the release notes for any supported device.

2.

This note also contains release notes for all supported drivers. Find the related release note for the peripheral driver to be configured. In this case, we will configure the Symbol MF4T printer, so we will review the PIPRSYMMF4T release note. For an explanation of the naming convention, please refer to the Appendix of this document.

-3-

3.

Review the Required Hardware and Software section of the release note to ensure that you are using the correct version of the driver. If your hardware/software settings do not match these requirements, then you will need to go back to select the appropriate release note for your current settings.

4.

Download the appropriate driver as indicated in Note 761833 for your current Mobile Infrastructure SP. Upload the driver and connector to the WebConsole or the NetWeaver Administrator as described in the installation guides.

5.

3.2
1. 2.

Configuring Peripherals with the NetWeaver Administrator


Create a parameter set. Under Mobile Infrastructure, select Parameter Sets from the left menu. Select Configuration Parameter Sets for MI 7.0. Click on the Create button under Configuration Parameter Sets.

3.

-4-

4.

Enter the name and description of the parameter set. Then, click on the Create button. Click on the Edit button.

5.

6.

Enter MI_PIOS as the Parameter Set Type on the Details tab below.

7. 8. 9.

Click on the Parameters tab. Click on the Add button. Enter piprsymmf4t.cfg.Bluetooth.Peer in the Parameter Name column.

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

-5-

11. Click on the Add button. 12. Enter


piprsymmf4t.cfg.Bluetooth.PeerType in

the Parameter Name column. 13. Enter Address or Name corresponding to the value entered for parameter Peer. 14. Click on the Save button.

15. Create a Device Configuration. Select Device Configuration from the left menu.

16. Click on the Create button. 17. Enter the Device Configuration Name and Description. 18. Click on the Create button. 19. Click on the Parameter Sets tab below.

-6-

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

21. Click on the Search button.

22. Select the Parameter Set you created above. 23. Select the >> button to move the Parameter set to the Assigned Parameter Sets column. 24. Click on the Save button.

-7-

25. You can then assign the device configuration to a device as described in the installation guide.

3.3
1.

Configuring Peripherals with the WebConsole


Before you can deploy a configuration to a device, you need to create it first from within your middleware (WebAS) system. Start transaction DEVICE_CONFIG.

2.

In the Configuration of Monitoring Functions section, enter the Monitoring Configuration name and Description, and then click on the Create button. Please note that the Monitoring Configuration name as well as the description cannot include spaces.

-8-

3.

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

4.

Put your cursor in the Parameter ID field and open the selection list.

5.

Since we are configuring a Symbol MF4T printer, scroll down until the beginning of the piprsymmf4t.cfg parameters.

-9-

6.

Select the piprsymmf4t.cfg.Bluetooth.Peer parameter.

7.

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

8.

One the next line, enter MI_PIOS in the Monitoring Function column.

- 10 -

9.

Scroll down until the beginning of the piprsymmf4t.cfg parameters. Select the piprsymmf4t.cfg.Bluetooth.PeerType parameter.

10. Enter Address or Name corresponding to the value entered for parameter Peer. 11. Click on the Save button.

12. Next, in the Configuration of Mobile Device section, create a Configuration of Mobile Device. 13. Enter the Device Configuration name and Description. 14. Click on the Create button.

- 11 -

15. In the Monitoring Functions tab, put your cursor in the Monitoring Configuration column and click on the pull down menu.

16. Select the Monitoring Configuration you created in the previous steps.

17. Click on the Save button.

- 12 -

18. To assign the Device Configuration to your user, open the WebConsole. 19. In the Administer Mobile Devices section, under the top Administration tab, click on the Add Entries button. 20. Enter the user. 21. Select the pull down menu for the mobile component

22. Click on the arrow next to Mobile Component to close this section

- 13 -

23. Click on Device Configuration to open this section.

24. Select the Device Configuration you created in the previous steps.

- 14 -

25. You can then select a particular device, or add the configuration to all devices for this user. 26. Click on the Add button. 27. This configuration will now be deployed to the user on the next synchronization.

- 15 -

3.4
1.

Configuring Bluetooth Printers from a Device


The following Bluetooth setup screens belong to an Intermec device running a Microsoft Bluetooth stack. While this process can vary from device to device, this screen flow will show you the general process to configuring the Bluetooth 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 in the Devices list box and click on the Connect button.

- 16 -

3.

Choose the COM Port and check the Enable Wireless Printing checkbox. You can then print a test page from your device.

4 Appendix
4.1 Naming Convention for Peripheral Driver Name

Peripheral names look like PIPRSYMMF4T. The first two characters of the peripheral name refer to the type of service used for peripheral input and output. PIOS (Peripheral Input/Output Services) is the 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).

- 17 -

The next three characters of the peripheral name refer to the manufacturer of the device. These include 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 the manufacturer is Symbol, and the device model is MF4T.

4.2

Naming Convention for Drivers and Connectors Add-Ons

An 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 for PocketPC 2003 in this case) refers to the operating system of the client device. The next section refers to the processor type used on the client device (xsc for XSCALE processor in this case). The next section refers to the Java Virtual Machine that is used on the device (crm for CreMe in this case). 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 file can 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 Solution You installed a Socket driver without enhancing the driver with the necessary third party software as described in the release note for these drivers. These drivers require third party software that SAP does not deliver. Please refer to the release note for your selected driver and refer to the Special Installation Instructions section of the release note for details on including the additional files from the Socket Communications SDK. Error is resolved with SP19 in NetWeaver 2004 or SP09 in NetWeaver 2004S.

Error Unable to Load Library/Unsatisfied Link Error

Unable to Install PIOS Driver

4.3.2 Functionality Error This error can occur after the installation of the peripheral is successful. Error Unable to Print Job Solution This error occurs when the peripheral is not configured correctly. For example, you will see this error if you do not configure the MF4T Peer and PeerType configuration parameters as described above.

- 18 -

www.sap.com/mobile

Вам также может понравиться