OS4X update

Requirements

If you have a software support bought with your software distribution, you may receive updates from time to time via several media. These media can be:

• Download links in the internet
• Files via OFTP, received via
  • ISDN
  • ENX
  • Internet
  • etc.

Run update automatically

These update files, if received via OFTP, have always the virtual filename

OS4X_UPDATE

When this flag is set, your OS4X installation tries to check the integrity and signature of this package internally. For this purpose, an event binary is (configured here) started. This event binary (default:

/opt/os4x/bin/os4xupdate

is started with the parameter "-f". It checks the signature of the file and if valid, it extracts the update procedure program and executes it in an OS4X shell. The update process searches for the OS4X environment variables and uses them to change and update the installation.

Run update semi-automatically (1)

If you have received such a signed update file manually or houy ave disabled this feature, you are able to re-start the event program manually. For this (in a standard environment), call the update program with appropriate parameters. They are documented here.

Example:

/opt/os4x/bin/os4xupdate -f /tmp/OS4X_UPDATE

Run update semi-automatically (2)

You may have received a file which is a verified and extracted version of the "OS4X_UPDATE" file. They have normally a file extension of ".sh". This file is a complete OS4X installation package, which checks if it's running inside OS4X. In order to do this manually, use the OS4X shell "shox".

Example:

/opt/os4x/bin/shox -e /tmp/os4x_update_linux_x86_he.sh

Run update manually (1)

You receive a gzipped TAR file which contains all files in this structure. You may exchange the binaries, scripts, programs, webinterfaces. You should do this in the following order:

1. make a backup of everything
2. copy all binaries to the target directory
   1. if swapping the whole directory, don't forget to copy the license file into the new directory!
3. check if the configuration file has changed it's schema ("/etc/os4x.conf")
4. copy the webinterface for administration to it's destination
   1. check the file "database.inc.php"
5. if OS4X Enteprise is installed:
   1. copy the OS4X web access client to it's target destination
   2. check the file "database.inc.php" in the OS4X web access directory
   3. copy all plugins
6. have a look at the configuration page of OS4X (administrative web interface)
7. run the OS4X database updater "os4x_dbupdate"!
8. restart the wanted daemons ("os4xrd", "os4xsqd", "os4xdebugd", "os4xclientd")