abas Software AG
Current versions:
- Hybrid-Cloud: 1.1.1-b910
- On-Premises: 1.0.0

1. Prerequisites

  • abas ERP Version: 2016r4n13, 2017r2n07, 2017r3n03, 2017r4 or later

  • Latest docker and docker-compose

  • Valid credentials for Extranet

  • SSH Access

  • Activated EDP

  • Linux distributions, according to the abas ERP requirements

  • One password definition (license) for performing service tasks (autmated operations)

  • 8 GB RAM

  • 10 GB disk space (+ dynamic, depending on the number of processes and created data)

  • Can be installed on the same machine as abas ERP, or on a dedicated server

2. Installation

Operation model Standard installation abas Installer



Not supported


Not supported


3. Configuration

After you have followed one of the installation guides, the installed abas BPM product need to be configured.
Our esdk app integrates abas BPM functionality into abas ERP.
The following steps will help you to configure this integration.

3.1. Link a erp user to its BPM / Camunda counterpart

The email of a password definition is used by abas BPM to get the camunda user of the logged in ERP user.
Only ERP users that have a BPM / Camunda counterpart are able to trigger and complete workflow steps or
use the infosystem processcenter.

Add the users email to a ERP password definition and check if a BPM / Camunda user exists with the same email as it’s ID.

3.2. Setup connection between abas ERP and the abas BPM engine

The integration of abas BPM in abas ERP needs credentials to establish connections with the abas BPM engine.

Please follow this instruction:

  • Get the API key in oder to authenticate against bpm engine.
    Note: When regenerating the API Key or deleting this user, the integrations will stop working!

    • Login the abas BPM Admin Dashboard with an admin user.

    • Goto the tab API Key, click on the button Generate to generate one API Key for this user.

  • Create a new Web user (V-93-01) object in abas ERP.

    • Create a new Web user object.

    • In the field Login(login), you set the login abas-bpm.

    • In the field Description(descr), you set the REST URL - http://{bpm-server}:8088/engine-rest of the BPM engine.

    • In the field E-Mail(emailAddr), you set the API Key that you have generated in Admin Dashboard.

    • Save the object.

  • Test the connection:

    • Open the infosystem processcenter with a ERP user that has already a BPM user counterpart and use the start workflow button.
      You should get the list of executable process definitions, if any is deployed.

Only admin users can have access to API Key, that he can generate and see the API Key.
The API Key that is generated in Admin Dashboard should be setted in the Web user object in abas ERP. abas BPM uses this information to connect to bpm engine.
If you click on the Generate API Key button again when the API Key is already avaiable, the API Key will be updated and you will get a new one. Please be very careful by regenerating or deleting the API Key, before you check that the API Key has not been used anywhere.
The abas BPM essential app uses this to communicate with the REST API. You have to configure this URL here to point to a valid REST service. The port 8088 is defined in the docker-compose.yml file. The URL should be something like http://{bpm-server}:8088/engine-rest. The server where bpm engine is running should be reachable from the server where the ERP is installed.

3.3. How to activate abas BPM on abas screens

As an example, if you have created one trigger for the customer object (0:1), you have to add the following Event handlers for the customer screen in the fop.txt:

# Customer workflow
0  * maskein * * * java:de.abas.workflow.erp.handler.WorkflowEventHandler@wkflw
0  * maskpruef * * * java:de.abas.workflow.erp.handler.WorkflowEventHandler@wkflw
0  * maskende * * * java:de.abas.workflow.erp.handler.WorkflowEventHandler@wkflw

Not only for the erp objects which are used within triggers, but also objects which are used in workflow abas tasks!

You have a workflow which will be triggerd when a new customer from a foreign country is being created.
The second workflow task is - create a new customer contact object.
In this case, you need to add the abas BPM Event Handlers for the customer erp object as well as the customer contact object.

3.4. Task Overview - Open abas gui to perform an abas workflow task

In abas BPM you can design user tasks of different types. The abas task is the type that integrates with abas ERP. When a user performs this task in the Task Overview, an abas screen will open.

If you enabled the UI_CONFIG for 2017 and 2016 or native gui, the browser will use the abasurl command to open a screen. On windows systems a registry entry is needed therefore and may not be existent in your setup.

Follow the steps in the taskoverview guide to setup the registry entry.

4. Migrations

4.1. Change from hybrid to the on-premise operation model

Please note, that the products can not run in a mixed operation model, hybrid and on-premises.
Depending on your preferred operation model and the applications that you are planning to use, you will need to choose either the operation model hybrid or On-Premise.
If you have no important data that needs to be kept/migrated in your existing hybrid installation, you can skip the migration process. In this case, you can download the workflows (BPMN files) on a local file system, delete the hybrid installation, install the On-Premises version and import/load your workflows again.

If you have an existing hybrid setup of abas BPM 0.304.0 (or older) and want to migrate it to the on-premise model, take these steps.

  1. Update your existing installation to version 1.0.0 as described here.

  2. Install on-premises using this guide.