Exchanging configuration and master data via data transfer packages

If you have already made configurations and entered master data in an AEB Engine, e.g. in a test system, you may sometimes want to transfer these to another system, e.g. to the production system. It is also possible that you have created a master client for your group, whose configuration and master data you now want to transfer to different clients of the same AEB Engine.

For this purpose, AEB has developed the “data transfer framework”. It supports the exchange of data between two clients of an AEB Engine or between two AEB Engines of the same name with the same service pack level.

It is, on the other hand, not suitable as:

  • An external interface to transfer data from another system to an AEB Engine or from an AEB Engine to another system
  • Long-term reusable backup

The data transfer takes place in three steps:

  • First, you define a “data transfer package”. It consists of objects of different master or configuration data.
  • Then download the data transfer package as a file.
  • Finally, upload this file again in your target system or the target client.

Transferable cross-product master data or configuration data

With the data transfer framework you can transfer cross-product master data or configuration data visible in your product and where you find the Add to data transfer package entry in the main menu. You can also transfer saved views for these objects.

Examples of cross-product master and configuration data:

  • Notification configurations
  • Notification texts
  • Users
  • Roles
  • Languages
  • Value lists
  • Value list entries

Transferable product-specific master data or configuration data

In addition, you can transfer product-specific master data or configuration data visible in your product and where you find the Add to data transfer package entry in the main menu. You can also transfer saved views for these objects.