OS4X Core administrative scripts
daxware2os4x
If you want to migrate from a Hüngsberg Daxware system to OS4X, you can easily use this script to mass-import all partner entries to OS4X. Just point the variable "PASSW_DAX" to the appropriate file. Example:
PASSW_DAX=/tmp/passw.dax
The rest of the script works out-of-the-box if you have a configured OS4X system running.
swan2os4x.ksh
To mass-import partner entries from SWAN 1.5 database to OS4X, the company SSC GmbH created this script which is free to use. You should run this script from a shell where the environment variable "SWAN_HOME" is available. Also check the position of the OS4X program "os4xped", which is being called in line 68 (also check the echo command on line 67).
os4xbackup
This script works without parameters. It checks the configuration file and the backup directory (as given in the configuration panel). If all requirements are fulfilled, a SQL dump will be saved with a timestamp extension in the backup directory. The output of a sample run is:
hostname:/opt/os4x/scripts # ./os4xbackup backup file: /opt/os4x/backup/os4x.20050113.182639.sql
So you can re-use the output for further post-processes.
os4xrestore
For restoring the OS4X database, make sure all OS4X processes are stopped. Also make sure the database is up and running. If you are not sure which file you want to restore, start the script without any parameter. It will say something like this:
hostname:/opt/os4x/scripts # ./os4xrestore no backup file as parameter 1 given. choose one of the existing: os4x.20041015.205850.sql os4x.20041222.175616.sql os4x.20050113.182639.sql
These are the existing database dump files in the backup directory as configured in the configuration panel. If you are sure which file to restore, start the script with the filename as given above as the only parameter.
hostname:/opt/os4x/scripts # ./os4xrestore os4x.20050113.182639.sql backup file: /opt/os4x/backup/os4x.20050113.182639.sql restored
Now you can safely start the OS4X processes again.