Installation

GUI

Server

Upgrade from 3.5.x to datasqill 4.0

Prerequisite: The directory ~datasqill/apps does not exist anymore

  • Stop datasqill (see Appendix / Server Operation)
Update h2
  • Stop h2 (see Appendix / Server Operation)
  • Copy new h2ctl.sh script into the h2 directory
  • Delete h2.sh, stoph2.sh and backup.sh
  • Check whether the current datasqill-h2-4.0.0.jar is used for h2 and replace if necessary
  • Check whether the current driver h2-1.4.199_Softquadrat-P6.jar is in use and replace if necessary
  • Start h2 again:
    h2server/h2ctl.sh start
  • Defragment h2:
    h2server/h2ctl.sh defrag
  • Start h2 backup:
    h2server/h2ctl.sh backup

  • Set up h2 start/stop (See Appendix / Server Operation)

  • Adapt your own scripts. E.g. automated backup

Replace datasqill Server

  • datasqill user backup

    tar cfz datasqill-3.x.tgz bin datasqill-server lib mod-src

  • Delete files no longer used

    rm -rf datasqill-server install.dsdb update.sh

  • Unpack new datasqill version

    tar xfz <source-directory>/ds_server_<customer>-4.0.tgz

  • Align datasqill.env with datasqill.env.template

    • Adjust port in template
    • Adjust directory for logs
    • Adjust mail settings

  • Set up crontab or services (see Appendix / Server Operation)

  • Log off and log on again as user datasqill so that the new variables are set

  • Deploy repository adjustments

    ./update.sh

  • Start datasqill

  • Adapt all scripts for backup and use h2ctl.sh backup

Update to datasqill Version 3.5.1

Due to the different modules used, there is one archive per customer. The software is identical; only the installed modules differ.

All commands must be executed as datasqill-user in their home directory.

  • Copy the file datasqill--3.5.1.tgz into the home directory of the datasqill user.

  • Create new directory ds3.5 in the home directory of datasqill:

    mkdir ds3.5
  • Stop datasqill Server

a. If the datasqill server is started via Crontab boot entry, stop it manually. This can be checked with:

crontab -l

The tomee.sh call should be there. Then stop the datasqill server with:

~/datasqill-server/tomee stop

b. Or if the datasqill server is managed via a Linux service, stop it with:

sudo systemctl stop tomee
  • Backup the home directory
    tar cfz ds3.5.tgz apps bin .bash_profile .keyfile datasqill-server

Here you may need to use .profile instead of .bash_profile. Check with "ls -la" in the home directory first.

  • Unpack new datasqill version into the directory

    tar xfz datasqill-<customer>-3.5.1.tgz -C ds3.5

  • Check whether the settings are correct

    cat ds3.5/bin/datasqill.env
    • Do the TOMEE variables match. Check in
      cat datasqill-server/conf/server.xml

The first line should contain the shutdown port (8005) and shutdown command (SHUTDOWN). The connector port (17491) is specified further down.

  • Where is Tomee installed
    grep CATALINA_HOME datasqill-server/tomee.sh

The path for CATALINA_HOME may need to be adjusted in ds3.5/bin/datasqill.env. Further settings in ds3.5/bin/datasqill.env must be checked and aligned.

Installation

Make sure beforehand that no templates have been modified.

If templates have been modified, compare with the current versions under ds3.5/mod-src and reapply the changes after installation

Execute update
ds3.5/update.sh
Set datasqill profile

Add or adjust the following in ~/.profile or ~/.bash_profile:

. ~/bin/datasqill.env
export PATH=$PATH:$HOME/bin
Set datasqill autostart

This section is only to be executed if the server is started via Crontab boot entry. This can be checked with:

crontab -l

The tomee.sh call should be there.

Adjust crontab
crontab -e

Replace the line that says "tomee.sh start" with

@reboot . bin/datasqill.env && catalina.sh start 2>&1 >>/home/datasqill/tomee.log
Start datasqill Server

Then start the datasqill server again. With automatic start via Crontab, a simple:

catalina.sh start

suffices.

If the datasqill server is managed and controlled via Linux services, restart it with:

sudo systemctl start tomee

Conclusion

When everything runs stably, the temporary files and the old tomee.sh can be deleted

rm -rf ds3.4.tgz ds3.5 datasqill-<customer>-3.5.tgz datasqill-server/tomee.sh