User manual

2 - 14
...Log\ScannerConfigUtility.txt contains detailed results of the push, pull and update firmware
operations performed during installation.
ReM.config
The ReM.config file contains the configuration data the silent installer uses to install the client agent.
Basic Layout
The layout of a simple ReM.config is shown below:
<ReMConfig>
<ConfigurationData>
<MBeanType> </MBeanType>
<ScannerModel> </ScannerModel>
<LogicalName> </LogicalName>
<Interface> </Interface>
<PortNumber> </PortNumber>
<USBSerial> </USBSerial>
<Restart>yes</Restart>
</ConfigurationData>
</ReMConfig>
You may need to use additional XML tags for your scanner installation, including using the ReM Licens-
ing File (see page 2-8). The table below describes the XML tags used with ReM.config:
Note: All tag names are case sensitive but the data is not.
Tag Description
<MBeanType> Type of ReM client agent to be installed. Possible values: JPOS, HHI or
FD.
For Honeywell models beginning with MS or IS (or legacy Metrologic
scanners) use JPOS or, if you want to deploy the Filter Driver, FD. (See
page 2-6 for more information about the Filter Driver.)
Use HHI for all other supported Honeywell (or legacy Hand Held Prod-
ucts) scanners.
<ScannerModel> See Scanner Model Names on page B-2 for valid scanner model num-
bers.
<LogicalName> For IS and MS models only: a name you assign to the scanner using let-
ters, numbers and underscores. (Do not use other special characters.)
For all other supported models, ReM automatically assigns a Logical
Name of “HHI” followed by the scanner model number.
<Interface> Possible values: RS232 (for RS232 and USB Serial) and USB (for USB
IBM OEM/SurePOS).
<ProductID> A unique number given to a USB device that identifies it from a set of
devices connected to different USB ports. The default is 0x0009. (USB
interfaces only.)
<PortNumber> For RS232 and USB Serial (Virtual Com) interfaces only. The port num-
ber through which the scanner is connected to its host.