abas Software AG

1. Requirements for automatic update

The abas installer can automatically update the installed components. The latest modules for the existing abas ERP version are downloaded and installed. The automated update currently only works if a certain combination of modules is available (those who are needed for the abas dashboard).

The following components must already be installed for the automatic update and listed in abasfile.yml:

  • keycloak

  • user_administration

  • rest_api

  • license_controller

  • jwt_auth_userinfo

  • dashboard

  • mongodb

  • webserver

Please also make sure that the abasfile.yml is in the HOMEDIR of the s3 user.

2. Update the abas Installer

To update the components, the abas Installer must be installed at least in version 0.12.0.
If you have already installed the abas Installer, you can update it with the abas-installer-manage-tool:

  • update-wrapper: Complete reinstallation of all included tools (ONLY up to version 0.10.0 necessary)

  • update-installer: Get the latest installer image only

sudo abas-installer-manage -a update-installer

check the version with the command "abas-installer --version"

3. Update der Module

The update runs in 2 steps.

  • the current version information is downloaded and compared with the existing abasfile.yml. The current versions are automatically entered in the abasfile.yml. The original file is stored in HOMEDIR under "abasfile_<Datum>_backup.yml".

  • After the download has been completed and the abasfile has been updated, the update can be started

With an update, the modules are automatically downloaded by the abas installer and stored under /opt/abas-installer/workspace/modules/

  1. Login as s3 user
    su - s3

  2. update the abasfiles.yml

    • cd ${HOMEDIR}

    • /usr/local/bin/abas-installer update-abasfile

    • Confirm with y

  3. update modules

    • /usr/local/bin/abas-installer update-modules

    • alternatively /usr/local/bin/abas-installer update-modules -m /opt/abas-installer/workspace/modules

After the update, the latest module sources can be found under /opt/abas-installer/workspace/modules
In case of future changes to the abasfile (e.g. if another client is added or BPM is installed), this folder should always be referenced with the -m Option.

As soon as the module update has run through, check with "docker ps" whether all Docker have been started properly.
Docker installed in the standard scope of delivery:

  • abas-nginx

  • dashboard-api

  • abas-mongodb

  • jwt-auth-userinfo

  • mw

  • tenant-administration-onprem

  • abas-keycloak

  • postgres

  • license-server

3.1. Updating BPM to version 1.1.1

The BPM database will not be changed, the saved workflows will be maintained.

To update abas BPM, perform the following steps:

  1. Download the latest abas Installer modules
    Download and unpack using this link or perform the following steps:

  2. Adapt the abasfile

  3. Stop BPM:

    • Open the module directory

    • docker-compose down

  4. Install the modules:

    • abas-installer check-configuration -m <module directory>

    • abas-installer update-modules -i <ESDK module> -m <module directory>

    • If the License Controller is not available:
      abas-installer install-modules -i <License Controller module> -m <module directory>

    • abas-installer update-modules -i <BPM module> -m <module directory>

  5. Start BPM:

    • Open the module directory

    • docker-compose up -d

    • Starting can take up to 15 minutes.

  6. Read the license terms:

    • Administration Overview: Open <hostname>/workflow/administration/

    • Click the License Terms tab

    • After reading the license terms, click Agree license term

  7. Open the BPM apps:

    • Workflow Designer: <hostname>:8181/workflow/designer/

    • Workflow Task Overview: <hostname>/workflow/taskoverview/

    • Administration Overview: <hostname>/workflow/administration/

    • Camunda: <hostname>:8088/camunda

    • Use the credentials for Keycloak.