Process Unit
The following program description deals with:
- Remarks on the Program Function
- Remarks on the Input Fields
- Use the Index to find the required field description.
Note
Before you can work with the MICROS Retail OSCAR POS program, all the different system specific data has to be defined. The setting up of the system data at the time of the initial installation is, as a rule, carried out by the MICROS GmbH support personnel, and this also applies to any of the modifications to the system configuration at a later stage.
For the user, at least one installation has to be defined. For each installation in the system, the user has to set up a hierarchical structure, where respective system units such as master and backup units, and process units such as server, client and domain programs have to be defined.
Example:
|
Installation 1 |
||||
|
System unit 1 |
|
System unit 2 |
||
|
Process units |
|
Process units |
||
|
Client |
For POS 1 |
|
Client |
For POS 2 |
|
Server |
Server (Master) |
|
Backup |
Server (Backup) |
|
Daemon |
Demon |
|
Daemon |
Demon |
|
Device |
Devices (remote printer) |
|
|
|
|
Subserver |
Subserver |
|
|
|
Further information on the optional configuration of an MICROS Retail OSCAR POS backup server and the communication of transaction data with the MICROS Retail OSCAR POS database can be found in Chapter Server/backup server procedure.
Remarks on the Program Function
By use of this program you can update data for the process units in the system, i.e. insert new units, edit and delete the existing ones. You can also display the data on the screen for enquiry only.
Process units are directly assigned to an installation. Each process unit has a unique process unit number and designation.
Process unit Configuration
You can assign any arbitrary number to the specific process unit. However, it is recommended that specific ranges of numbers are assigned to the different units so as to have a better overview of the data in the system.
The following ranges are recommended for the respective process units:
- 1-999
MICROS Retail OSCAR POS CLIENT process units for POS terminals drink dispenser ASCII-COM etc.(autostart). - 1000-1999
MICROS Retail OSCAR POS CLIENT (Login unit) process units for administrative terminals (user Login). - 2001-2999
MICROS Retail OSCAR POS-DEMON process units for process supervision of a system unit. - 3000
MICROS Retail OSCAR POS SERVER process unit. - 3001
MICROS Retail OSCAR POS BACKUP process unit. - 3002
MICROS Retail OSCAR POS DEVICE process unit for remote devices - 4000
SUBSERVER process unit for parallel processing of terminal transactions.
- 5000
Fast load client processing unit for loading clients with internal Isam database, File by file instead of data record by data record.
Attention!
It is only allowed to configure a processing unit from type "Fast load" once for an installation. This type of client will only be used for faster loading the POS clients with own database.
NOTE!
POS clients and server in an installation can have different program version installed. Data is converted "on the fly":
If communication between POS clients is to run error-free they must all have the same program version.
This applies at present to the following client types:
- Client type "Position Server"
POS clients and position server must have identical program versions. - Client type "Scale server"
POS clients and server must have identical program versions. - Client type "Fast load client"
POS clients and server must have identical program versions.
Remarks on the Input Fields
This paragraph will provide a short overview over the options available for updating these Basic Data.
Just like in almost any other program:
- The Input Mask may be different in your MICROS Retail OSCAR POS program depending on the set-up of the application. In some cases some Data Fields may be missing.
- Some input fields may contain default values or defined selection options; these cannot be updated.
- The input mask contains some fields that require an entry and others in which entries are optional.
- If the data record is updated via multi-page input masks, go to the Dialog Window by clicking on the appropriate buttons with <Mouse key 1>.
- The same procedure applies to call up another update program from this program.
- In some cases you may find that so-called "Switches" which - depending on the default - can be activated or deactivated with <Mouse key 1>. Activated switches are identified by their dark color, deactivated switches are lighter-colored.
Installation
Permitted input range: numeric, 1 - 9999
Enter the number of the installation to which the process unit is to be assigned. The designation of the installation will be displayed to the right of the field. Without this assignment, the process unit cannot be created in the system.
For creating a new record, enter an unused number into this Key Field.
For changes or deletions, retrieve the record by entering the number in this field. If you do not know the number, you can also select the data record via the Search Function.
Process Unit
Permitted input range: numeric, 1 - 9999
Enter the number of the process unit. You can assign an arbitrary number, however, it is recommended to assign specific range of numbers to the different process units to have a better system overview. Please use the suggested Number Range for the respective units.
For creating a new record, enter an unused number into this Key Field.
For changes or deletions, retrieve the record by entering the number in this field. If you do not know the number, you can also select the data record via the Search Function.
Designation
Permitted input range: alphanumeric, max. 20 characters
Enter a descriptive name for the process unit. Use a name which reflects the function and the system unit of this process unit.
The name entered is displayed in the Dispatcher for processing units with the activated option “Graphic”.
Login Name
Permitted input range: alphanumeric, max. 20 characters
Entries in this field are only necessary if this processin gunit is a Login unit for administrative purposes.
Enter the name of the user in this field who is allowed to start a login unit for administrative purposes. The appropriate login name (user) must be set up by the system administration.
When an authorised user logs onto the system with the name entered here, a process unit will be started automatically from the system.
Note:
Please note that processing units of type Login
imot are not linked to any specific system unit and do not have their own
database. An administrator can start a login unit on every system unit within a
local network. The data access is always via the server database.
NOTE!
Entry of the MICROS Retail OSCAR POS_USER=Username in file "oscar.ini" changes the reaction of
MICROS Retail OSCAR POS under Vista only. The reaction remains the same in all
other Windows operating systems.
If the environment variable "MICROS Retail OSCAR POS_USER" is not set for Vista the Oscar service (oscard) starts all processing units which are to be started automatically with GUI in the currently valid console session (if a console session exists). Normally, POS which work with Autologin can be operated in this way.
If however MICROS Retail OSCAR POS_USER=Username was set oscard starts the processing units to be started automatically with GUI only in sessions for the operator stated (provided this operator is signed on). This setting is advisable if the operators continuously move from system unit to system unit or if the system unit is to be operated via Remote Desktop / Terminal Server.
Program Type
Field with fixed preset selection options
Apart from defining the purpose of the process unit, a specific program type has also to be linked.
The following program types are supported by the various process units:
Server
- Process units for database server
Client
- Process unit for POS terminals as automatically starting process units with firm link to a system unit.
- Process unit for Login units which are used as administrative terminals. Login units do not have firm links to a specific system unit. They are started from entry of command "oscar" by an authorized user.
- Process unit for drink dispenser or for ASCII communication as automatically starting process unit with firm link to a system unitt.
- Process unit for a DTM order as automatically starting process unit with firm link to a system unit.
- Process unit for production, preparation and dispensing positions with a configured fast-food system (ECRFF, ProdSrv, PrepSrv). Detailed information on setting up a fast-food system can be found in documentation Fast-food system.
DAEMON
- Process units for background processing of the system unit. For each system unit, its own particular process unit of the type MICROS Retail OSCAR POS demon has to be set up.
BACKUP
- Process unit for the backup server of the MICROS Retail OSCAR POS program. It is possible to set up this process unit on the same system unit where the master server is set up. For the reason of data security and system backup purposes, this way of setting up the backup server should be avoided and used in exceptional cases only.
- Further information on the optional configuration of an MICROS Retail OSCAR POS backup server and the communication of the transaction data with the MICROS Retail OSCAR POS database can be found in the Chapter Server/Backup server procedure.
Device
- Process units for devices such as printers, beverage dispensers, etc.
SUBSERVER
- Process unit for parallel processing of
terminal transactions in an installation. They are used to increase the
efficiency during processing of terminal transactions.
The configuration of subserver process units is only feasible if several branches belong to an installation. In this case, a subserver process unit can be linked to each branch for processing terminal transactions.
The link of a subserver process unit is done in program Application -> Organisation -Branch -> Add.data in field "Subserver".
Several subserver process units can be configured on the same system unit or assigned to individual system units.
Note:
Subserver processing units should only be used in conjunction with external SQL databases (MS-SQL /Oracle) as these can be configured on a scale.
Subserver processing units when using the ISAM database does not produce a speed advantage during processing of terminal transactions.
System Unit
Permitted input range: numeric, 1 - 9999
Enter the number of the system unit, on which the process unit is running on.
For creating a new record, enter an unused number into this Key Field.
For changes or deletions, retrieve the record by entering the number in this field. If you do not know the number, you can also select the data record via the Search Function.
Language
Permitted input range: numeric, 1 - 99
Enter the number of the appropriate language. If you do not know the number, you can also select the data record via the Search Function.
NOTE!:
If the language setting is to be changed later for a POS Client the client
database must be re-loaded. Alternatively, you can set the environment variable
"MICROS Retail OSCAR POS_CLIENTLOADALL=Y" in file oscar.ini so that
all data is stored in the client database.
An entry is necessary only if this process unit is of the type "MICROS Retail OSCAR POS Client". If this field contains no entry, the standard system option for language is used as default as per the entry "MICROS Retail OSCAR POSLANG= " in file "oscar.ini" or in file "oscar.def".
- The entry MICROS Retail OSCAR POSLANG=2 (2=English) in file oscar.ini for the standard language applies to WIN-NT
- The entry MICROS Retail OSCAR POSLANG=2 (2=English) in file oscar.def for the standard language applies to UNIX.
The following nos. are at present assigned for specific languages:
- 1 German
- 2 English
- 3 Francais
- 4 Swedish
- 5 Norwegian
- 6 Finnish
- 7 Denmark
- 8 Spain
- 9 reserved
- 10 Netherlands
- 11 Croatia
- 12 Czech Republic
- 13 Slowenia
- 14 Hungary
- 15 Italian
- 16 Polish
- 17 Portuguese
- 18 Greek
- 19 Icelandic
- 20 Cyrillic
- 21 Crnogorski ( = Montenegro)
- 22 Bosanski ( = Bosnia)
- 23 Srpski = (Serbia)
- 24 Makedonski = (Macedonia)
- 25 Slovencina = Slowakia
- 26 Latvia = Latvia
- 27 Austria
- 28 Shqipe (Albania)
- 29 Bulgarien
- 30 Estonia
- 99 Wizzard (reserved)
Note:
The number assignment is done by MICROS Retail
s Deutschland GmbH only. The name of the language should not be changed.
Warning
Please note that the value for the environment
variable "InternalCodePage=0-7" in file oscar.ini is set for conversion of the code page to ensure that the correct code page table is
supported for the graphic user interface and the input and output of the
connected peripheral equipment for the MICROS Retail OSCAR POS application.
The following value ranges (at present 0 - 7) are permitted depending on the operating system (UNIX / LINUX / WINDOWS) in use:
- 0 = CP ISO 8859-1 (UNIX / LINUX) /1252 WINDOWS
- 1 = CP ISO 8859-2 (UNIX / LINUX)
- 2 = CP ISO 8859-15 (UNIX / LINUX)
- 3 = WINDOWS 1250 (Eastern Europe)
- 4 = WINDOWS (Turkish)
- 5 = WINDOWS (Baltic)
- 6 = WINDOWS (Cyrillic)
- 7 = WINDOWS (Greek)
Program Name
Permitted input range: alphanumeric, max 32 characters
Enter the name of the application program which is to be started automatically when this processing unit is started. If this is a POS application, the screen layout must be linked to the appropriate program (see Screen layout).
The program name is dependent on the type of application to which this processing unit is to be linked. If no valid program name is entered in this field, the dispatcher is started as the default setting. The application is started with button Sales. The form name is entered in program System -> User interface -> Applications -> ECR application.
The following POS applications can be entered in this field:
|
Hospitality / SS Terminal programs (LINUX) |
||||
|
POS program |
Operating system |
Size |
Screen layout |
Market sector |
|
KasseRS_X |
LINUX |
640x480 |
No layout |
Hospitality |
|
KasseSS_X |
LINUX |
640x480 |
No layout |
SS |
|
KasseT2_X |
LINUX |
640x480 |
Standard layout |
SS / Hospitality |
|
KasseT3_X |
LINUX |
800x600 |
Big layout |
SS / Hospitality |
|
Hospitality / SS Terminal programs (Windows) |
||||
|
POS program |
Operating system |
Size |
Screen layout |
Market sector |
|
KasseT2 |
WINDOWS |
640x480 |
Standard layout |
SS / Hospitality |
|
KasseT3 |
WINDOWS |
800x600 |
Big layout |
SS / Hospitality |
|
KassePocket |
WINDOWS |
|
PocketPC layout |
SS / Hospitality |
|
FastFood POS programs (LINUX) |
||||
|
POS program |
Operating system |
Size |
Screen layout |
Market sector |
|
KasseFF_X |
LINUX |
640x480 |
Fast Food layout |
FastFood |
|
KasseFFBig_X |
LINUX |
800x600 |
Big layout |
FastFood |
|
FastFood POS programs (Windows) |
||||
|
POS program |
Operating system |
Size |
Screen layout |
Market sector |
|
KasseFF |
WINDOWS |
640x480 |
Fast Food layout |
FastFood |
|
KasseFFBig |
WINDOWS |
800x600 |
Big layout |
FastFood |
|
Hospitality ECR programs (Windows)) |
||||
|
POS program |
OS |
Size |
Screen Layout |
Market sector |
|
KasseRS |
WINDOWS |
640x480 |
Ohne Layout |
Hospitality |
|
KasseT2_30blueH |
WINDOWS |
800x600 |
Standard layout_30H |
Hospitality |
|
KasseT2_30blueHXA |
WINDOWS |
1024x768 |
Std layout_30HXA |
Hospitality |
|
KasseT2_30blueHXB |
WINDOWS |
1152x864 |
Std layout_30HXB |
Hospitality |
|
KasseT2_30greenH |
WINDOWS |
800x600 |
Standard layout_30H |
Hospitality |
|
KasseT2_30greenHXA |
WINDOWS |
1024x768 |
Std layout_30HXA |
Hospitality |
|
KasseT2_30greenHXB |
WINDOWS |
1152x864 |
Std layout_30HXB |
Hospitality |
|
KasseT2_30LblueH |
WINDOWS |
800x600 |
Standard Layout_30LH |
Hospitality |
|
KasseT2_30LblueHXA |
WINDOWS |
1024x768 |
Std Layout_30LHXA |
Hospitality |
|
KasseT2_30FblueHXA |
WINDOWS |
1024x768 |
Std Layout_30FHXA |
Hospitality |
|
KasseT2_30LblueHXB |
WINDOWS |
1152x864 |
Std Layout_30LHXB |
Hospitality |
|
KasseT2_30FblueHXB |
WINDOWS |
1152x864 |
Std Layout_30FHXB |
Hospitality |
|
KasseT2_30LgreenH |
WINDOWS |
800x600 |
Standard Layout_30LH |
Hospitality |
|
KasseT2_30LgreenHXA |
WINDOWS |
1024x768 |
Std Layout_30LHXA |
Hospitality |
|
KasseT2_30FgreenHXA |
WINDOWS |
1024x768 |
Std Layout_30FHXA |
Hospitality |
|
KasseT2_30LgreenHXB |
WINDOWS |
1152x864 |
Std Layout_30LHXB |
Hospitality |
|
KasseT2_30FgreenHXB |
WINDOWS |
1152x864 |
Std Layout_30FHXB |
Hospitality |
|
KasseT2_30LorangeH |
WINDOWS |
800x600 |
Standard Layout_30LH |
Hospitality |
|
KasseT2_30LorangeHXA |
WINDOWS |
1024x768 |
Std Layout_30LHXA |
Hospitality |
|
KasseT2_30ForangeHXA |
WINDOWS |
1024x768 |
Std Layout_30FHXA |
Hospitality |
|
KasseT2_30LorangeHXB |
WINDOWS |
1152x864 |
Std Layout_30LHXB |
Hospitality |
|
KasseT2_30ForangeHXB |
WINDOWS |
1152x864 |
Std Layout_30FHXB |
Hospitality |
|
KasseT2_30orangeH |
WINDOWS |
800x600 |
Standard layout_30H |
Hospitality |
|
KasseT2_30orangeHXA |
WINDOWS |
1024x768 |
Std layout_30HXA |
Hospitality |
|
KasseT2_30orangeHXB |
WINDOWS |
1152x864 |
Std layout_30HXB |
Hospitality |
|
KasseT2_40_1024 |
WINDOWS |
1024x768 |
Layout_40_1024 |
Hospitality |
|
KasseT2_40_1152 |
WINDOWS |
1152x864 |
Layout_40_1152 |
Hospitality |
|
Kasse2_To_1024 |
WINDOWS |
1024x768 |
Layout2_To_1024 |
Hospitality |
|
Kasse2_To_1024 |
WINDOWS |
1024x768 |
Layout2_To_B1024 |
Hospitality |
|
SS POS program (Windows) |
||||
|
POS program |
OS |
Size |
Screen. Layout |
Market sector |
|
Kasse |
WINDOWS |
640x480 |
Ohne Layout |
SS |
|
KasseSB |
WINDOWS |
640x480 |
Ohne Layout |
SS |
|
KasseSB30blue |
WINDOWS |
800x600 |
Ohne Layout |
SS |
|
KasseSB30green |
WINDOWS |
800x600 |
Ohne Layout |
SS |
|
KasseSB30orange |
WINDOWS |
800x600 |
Ohne Layou |
SS |
|
KasseSB30VGAblue |
WINDOWS |
640x480 |
Ohne Layout |
SS |
|
KasseSB30VGAgreen |
WINDOWS |
640x480 |
Ohne Layout |
SS |
|
KasseSB30VGAorange |
WINDOWS |
640x480 |
Ohne Layout |
SS |
|
KasseSB30XAblue |
WINDOWS |
1024x768 |
Std layout_30XA |
SS |
|
KasseSB30XAgreen |
WINDOWS |
1024x768 |
Std layout_30XA |
SS |
|
KasseSB30XAorange |
WINDOWS |
1024x768 |
Std layout_30XA |
SS |
|
KasseSB30XBblue |
WINDOWS |
1152x864 |
Std layout_30XB |
SS |
|
KasseSB30XBgreen |
WINDOWS |
1152x864 |
Std layout_30XB |
SS |
|
KasseSB30XBorange |
WINDOWS |
1152x864 |
Std layout_30XB |
SS |
|
KasseT2_30blue |
WINDOWS |
800x600 |
Standard layout_30 |
SS |
|
KasseT2_30blueXA |
WINDOWS |
1024x768 |
Std layout_30XA |
SS |
|
KasseT2_30blueXB |
WINDOWS |
1152x864 |
Std layout_30XB |
SS |
|
KasseT2_30green |
WINDOWS |
800x600 |
Standard layout_30 |
SS |
|
KasseT2_30greenXA |
WINDOWS |
1024x768 |
Std layout_30XA |
SS |
|
KasseT2_30greenXB |
WINDOWS |
1152x864 |
Std layout_30XB |
SS |
|
KasseT2_30Lblue |
WINDOWS |
800x600 |
Standard Layout_30L |
SS |
|
KasseT2_30LblueXA |
WINDOWS |
1024x768 |
Std Layout_30LXA |
SS |
|
KasseT2_30FblueXA |
WINDOWS |
1024x768 |
Std Layout_30FXA |
SS |
|
KasseT2_30LblueXB |
WINDOWS |
1152x864 |
Std Layout_30LXB |
SS |
|
KasseT2_30FblueXB |
WINDOWS |
1152x864 |
Std Layout_30FXB |
SS |
|
KasseT2_30Lgreen |
WINDOWS |
800x600 |
Standard Layout_30L |
SS |
|
KasseT2_30LgreenXA |
WINDOWS |
1024x768 |
Std Layout_30LXA |
SS |
|
KasseT2_30FgreenXA |
WINDOWS |
1024x768 |
Std Layout_30FXA |
SS |
|
KasseT2_30LgreenXB |
WINDOWS |
1152x864 |
Std Layout_30LXB |
SS |
|
KasseT2_30FgreenXB |
WINDOWS |
1152x864 |
Std Layout_30FXB |
SS |
|
KasseT2_30Lorange |
WINDOWS |
800x600 |
Standard Layout_30L |
SS |
|
KasseT2_30LorangeXA |
WINDOWS |
1024x768 |
Std Layout_30LXA |
SS |
|
KasseT2_30ForangeXA |
WINDOWS |
1024x768 |
Std Layout_30FXA |
SS |
|
KasseT2_30LorangeXB |
WINDOWS |
1152x864 |
Std Layout_30LXB |
SS |
|
KasseT2_30ForangeXB |
WINDOWS |
1152x864 |
Std Layout_30FXB |
SS |
|
KasseT2_30orange |
WINDOWS |
800x600 |
Standard layout_30 |
SS |
|
KasseT2_30orangeXA |
WINDOWS |
1024x768 |
Std layout_30XA |
SS |
|
KasseT2_30orangeXB |
WINDOWS |
1152x864 |
Std layout_30XB |
SS |
|
KasseT2_40_1024 |
WINDOWS |
1024x768 |
Layout_40_1024 |
SS |
|
KasseT2_40_1152 |
WINDOWS |
1152x864 |
Layout_40_1152 |
SS |
|
Kasse2_To_1024 |
WINDOWS |
1024x768 |
Layout2_To_1024 |
SS |
|
Kasse2_To_1024 |
WINDOWS |
1024x768 |
Layout2_To_B1024 |
Ss |
If this is a processing unit which is to be configured for the production area of a Fast Food system, the following program name should be entered
- ProdSrv
If this is a processing unit which is to be configured for the dispensing area of a Fast food system, the following name should be entered here
- PrepSrv
If this is a processing unit which is responsible for ASCII communication, the name of the appropriate program should be entered here.
- AscRS =
- AscSS =
- AscST =
If this is a processing unit which is to be configured for a DTM order, the following program name should be entered here
- DTMClient
Note:
The appropriate name for the automatic start
of an ECR application or for the ASCII communication can be found under System
-> User interface ->Applications and then the appropriate application
components, e.g. ECR application,. ASCII Com, DTM,
etc
Fixed port number
Entry range permitted: numeric, 1 – 99999
This entry is always necessary if your network has a firewall with port access control configured. For certain applications e.g. Devices service or Scales Server the fixed port number is mandatory.
Click on the graphic for
further help with setting up MICROS Retail OSCAR POS Ports.
Graphic
Button activated : This
process unit works with graphical user interface.
Button deactivated : No graphical user interface.
This option should only be activated for processing units of type MICROS Retail OSCAR POS Client.
Activate this option only if you want to use a system unit with a graphical user interface. For all system units without graphical user interface, such as "Operating Module" with a 2-line display, this option has to be switched off.
Has database
Button activated : This
process unit works with its own database.
Button deactivated : This process unit does not work with its own
database.
The following general information applies:
- Processing units type Oscar Server and Oscar Backup have to work with their own database, i.e. this option must be on.
- Processing units type Oscar
Client have to work with their own database so that the linked
POS terminals can work in Offline mode. This option must
be set for restaurant operation where the linked terminals work in Guest
Check mode.
Note:
Normally POS clients have to work with their own database.
Please note the settings in program Terminal type: operation type (waiter terminal, table no. system or itemisation, etc.) for the linked terminals. - Deactivate this option for processing units type "Oscar Demon" and for "Oscar Client" if this MICROS Retail OSCAR POS client is to be used as a login unit.
X Server
Button activated : This
process unit uses its own X Server.
Button deactivated : This process unit has no X Server.
Activate this option only if the operating system UNIX or LINUX is in use and this processing unit is to be linked to a system unit type "POS terminal" with graphic user interface (touchscreen or administration terminal).
Screen mouse
Button activated: Mouse
control for navigation within the item information and the additional help at
the terminal
Button deactivated: Key control for navigation within the item
information and the additional help at the terminal
Note:
If a touchscreen is in use or if navigation
with a mouse is required, this option should be on.
If an ADS POS keyboard with control keys is in use, this option must be off.
The file name for a HTML file can be stated in program Terminal type in field "Info address" and in program Article ->Link in field "Info address". Additional information on items or help at the terminal can also be stored here. The content of the file is shown in the browser window of the online help after key INFOCHAR or HELPINFO have been operated at the terminal. Navigation within a window can be done with the help of the connected mouse or with special control keys on the POS keyboard.
Click
on the graphic for further help with setting up Navigation
keys for help at the terminal.
Fast load client
Switch activated: This
client supports the fast loading of clients with ISAM database.
Switch deactivated: This client does not supports the fast
loading of clients with ISAM database.
Attention!
It is only allowed to configure a processing unit from type "Fast
load" once for an installation. This type of client will only be used for
faster loading the POS clients with own database. The environment variable "OSCAR_CLIENTLOADALL=Y"
must be set in the file "..\oscar.ini".
A fast load client must be the type of "client" with the activated option "has database" and without the the option "Graphic". The fast load client has to be linked to a terminal.
Notes:
MICROS Retail OSCAR POS terminal clients saving a part of the server database in their own client database, to be able to let the terminal operate in offline mode.
Without the existence of a fast load client the loading of the client database will be done record by record. This can take a long time in larger installation.
With the configuration of a fast load client the loading of the client database will be done file by file from the fast load client. The synchronization between the server and the fast load client will be stopped during the loading procedure of the client databases. After the loading process of the terminal clients was succsessful, the syncronization will automatically resume.
Sol
Switch activated: This
client is used for the mobile terminal device "Orderman Sol".
Switch deactivated: This client will not be used for the
mobile terminal device "Orderman Sol".
Note:
Additional
settings are necessary for the configuration of Orderman Sol:
Option:
· Graphic = off
· Has database = on
· X Server = off
· With screen mouse = off
· Fast load client = off
· Sol = on
The program name "KassePocket" must be entered in field "Program name". In program terminal the touch layout "Ordlayout_H", English or Deutsch must be assigned.
Click
onto the graphic for further help with programming of an Orderman device.
Index
- Designation
- Fast load client
- Fixed port number
- Graphic
- Has database
- Installation
- Language
- Login Name
- Process unit
- Program name
- Program type
- Screen mouse
- Sol
- System unit
- X server
Salzufer 8
D-10587 Berlin Germany