The following program
description deals with:
Normally, the complete
software update is determined by the rules file "Rules". Each software update contains a file with the name
"Rules" in the ZIP archive. The appropriate values for the
running of a software update are defined in this file. The identical
"Rules" file must be available in both archives for software updates
in a mixture of systems (Windows and Linux).
A software update can be completed in three different ways:
·
Complete update (completeupdate = 1)
In this version it is assumed that the complete files for an operable
MICROS Retail OSCAR POS system are in the archive of the software update.
After start of the software update the archive is unpacked in a temporary
directory and the directory "work.srv" is then copied from the
original MICROS Retail OSCAR POS directory to the temporary directory. In addition the
original file "oscar.ini" is copied into directory "bin" of
the temporary directory. At the end of this operation, the directory names are
exchanged so that the original directory is given the name of the temporary
directory and the name of the temporary directory is given the original name.
·
Partial update (completeupdate = 0)
In this version it
is assumed that not all files are in the archive of the software
update, but the relevant files such as *.lib *.dll *.exe etc., are available
for an operable MICROS Retail OSCAR POS program. After start of the software update a
complete replica of the original MICROS Retail OSCAR POS directory is copied into the
temporary directory. The archive of the software update is then unpacked in the
temporary directory. The original file "oscar.ini" is also copied
into the directory "bin" of the temporary directory.
·
Small update (completeupdate = 0 und Smallupdate = 1)
In this version it
is assumed that the archive of the software update only contains uncritical
files such as *.fgl. *.fsm, *.asc,
*.bmp. After start of the software update the archive is unpacked in the
original directory of the MICROS Retail OSCAR POS program. No copy and no temporary directory
is generated for the MICROS Retail OSCAR POS program.
A file named
"oscar.ini.chg" or "oscar.def.chg" can be handed over to
change the file "oscar.ini" for Windows or the file
"oscar.def" for Linux in directory./bin. The environment variables to
be set are marked at the beginning of a line with "S:" and the
environment variables to be deleted are marked with "R:".
Example:
·
Oscar.ini.chg
R:MICROS Retail OSCAR POS_OMLPATH=..\logs,30
S:MICROS Retail OSCAR POS_VERSION="Oscar3_ASU_Test_3"
·
Oscar.def.chg
R:SALESDEBUG =Y
S:OSINTERDEBUG=Y
In update program System
-> Configuration -> Update Status the user can carry out an automatic
software update for the MICROS Retail OSCAR POS program. A software update can only be
carried out for an installation and the related terminal clients. If the MICROS Retail OSCAR POS
POS installation comprises a multi-branch installation (main and
sub-installations) a separate software update will have to be executed for each
installation.
Note:
If a software
update is to be carried out for a multi-installation, each installation is
subjected to the software update. The status data for a software update for all
connected sub-installations can be transferred to the main installation (head
office) with button Get update status in program Installation.
A software update is
delivered in the form of a ZIP archive of the name "oscupdnnn"
whereas "nnn" can be used as an additional description. The
name extension for the archive file is ".zip" for Windows and
".tgz" for Linux (compressed tar file). This file has to be copied to
the directory "..\work" of the system unit on which the MICROS Retail OSCAR POS
POS server process is running. In addition to the files of the MICROS Retail OSCAR POS
program update, the ZIP archive also contains the file "Rules" which defines the sequence
of the software update.
The software update is to
be started via the button "Start Update " in the update program
Update State or by embedding the FGL file
"LstUpdateState.fgl" in a report chain which is then to be
started by use of a scheduler. The execution of the software update takes place
exclusively on the system unit on which the MICROS Retail OSCAR POS server is operated. In
addition, you have to make sure that the existing terminal clients are online
and no operator has signed on.
Warning!
On Windows processors no other programs should be started from the MICROS Retail OSCAR POS
directory. The administration terminal must be started as the automatic login
client. The DOS entry request should not be found in the current directory in
the MICROS Retail OSCAR POS directory tree. The Daemon clients should be cleared from the
server database for configured MICROS Retail OSCAR POS clients which are not to be updated.
After the software update
has been started, all necessary program steps will be executed and recorded
automatically. The state of the program steps can be viewed during the
installation of the software update in the update program Update State.
Detailed information on the software update procedure can also be viewed in the
update programs Sys. Units Update State
and Update Log. In
addition, a protocol of the whole software update can be printed out.
Note:
If errors occur
during the software update, they will be recorded and might lead to a complete
cancellation of the entire update process. Depending on the software update's
state of progress in such cases, a so-ca<lled "roll-back" will be
carried out to restore the condition of the installation as it has been before
the start of the update for the purpose of being able to keep on working
properly. By use of the recorded status, system and error messages in the
programs Update State, Sys. Units Update States and Update Log, the reason for the cancellation can be
determined before the update is started once again.
In the following
description, the start and procedure of a faultless software update will be
described. In addition, you will find notes on possible error messages and
their meaning. The program steps described in the following are only for your
information and will be carried out automatically.
Warning!
On Windows processors no other programs should be started from the MICROS Retail OSCAR POS
directory. The administration terminal must be started as the automatic login
client. The DOS entry request should not be found in the current directory in
the MICROS Retail OSCAR POS directory tree. The Daemon clients should be cleared from the
server database for configured MICROS Retail OSCAR POS clients which are not to be updated.
Attention!
If errors occur
during the software update, they will be recorded in the programs Update State, Sys.
Units Update State and Update Log. Errors
can lead to the cancellation of the software update and – in particular cases –
the complete restoration of the old MICROS Retail OSCAR POS installation ("Roll-back").
When a "Roll-back" is carried out, the old installation's
ability to work is definitely guaranteed.
Every software update
includes i a file called "Rules" in its ZIP archive. In this
file, the software update process is defined by the related values.
Note:
A "Rules" file can be added
to an existing zip archive with the
following command:
zip -u upd4.zip Rules
The following values
can be included in the "Rules" file:
·
SmallUpdate (Default
= 0)
With this software update (switch "Complete update" =deactivated and
switch "No rollback" =active) no backup of the current MICROS Retail OSCAR POS
directory will be generated. Therefore, there cannot be a rollback of the software
update. This software update variation should only be used for uncritical files
(*.fgl; *.fsm; *.asc; *.bmp).
The following values
will be entered automatically.:
MICROS Retail Deutschland GmbH
Salzufer 8
D-10587 Berlin