Version Control #

A version control system helps manage the data transfer from test environment to production environment by keeping track of all modifications.
Git or Azure DevOps are version control systems that can be used to ensure:

  • The deployment of new extractions, sources and destinations can not cause fundamental damage to the data load of the productive landscape.
  • User rights and other features allow for changes to be checked and corrected in advance.
  • Quick and easy rollbacks of changes.

For more information on how to set up version control, refer to the knowledge base article Deploying Extractions Using Git Version Control.

Configuration Files #

All configuration files of extractions, sources and the server are stored in the sub-directory config of the Board Connector program directory (C:\Program Files\BOARDConnector\config). Use the config directory for setting up a version control system or creating manual backups.

Filename Description
extractions Directory containing the extractions. Each sub-directory contains an extraction of the same name.
servers Directory containing the server settings.
sources Directory containing SAP connections. Each sub-directory contains a source of the same name.
version.txt Text file containing the product version of the current configuration. See also New Installation and Update.

Manual Backups #

Recommendation: Make sure to create regular backups of the configuration files to save the work invested in designing and optimizing your data extraction processes.

A backup allows you to easily switch back to the previous product version, if needed. See also section Installation and Update.

How do to Create a Backup?

Copy the complete config directory (C:\Program Files\BOARDConnector\config by default) of the machine running the Board Connector Service and store the files in safe and secure locations. Optionally, copy the complete logs directory (C:\Program Files\BOARDConnector\logs by default) to create a backup of the log files. To backup your licence, create a copy of your BOARDConnectorLicense.json file.

Warning! Data security.
Both config and logs directories may contain sensitive information.

How to Restore a Backup?

  1. To restore the configuration files, remove the config directory from the program directory (C:\Program Files\BOARDConnector by deafult) of the machine running the Board Connector Service.
  2. Copy the backup of the config directory into the program directory.
  3. To restore the licence replace the BOARDConnectorLicense.json file within the program directory with the backup.

Warning! Data Loss!
Restoring the backup of the config directory replaces the exisiting configuration. Make sure to remove the existing files before restoring the backups.

Manual Migration to a Different Machine #

Configuration files can be migrated partially or entirely (full migration).

Depending on your scenario it can make sense to conduct a partial migration - e.g., if you transport extractions from a test to a production environment.

When replacing a machine completely, conduct a full migration.

Prerequisite: Board Connector versions installed on both machines match.

Tip: To check the version of your product, open the Designer, navigate to Help > Info or press [F12].

Tip: Install the matching version on the different machine by using the BOARDConnectorSetup.exe from the program directory (C:\Program Files\BOARDConnector by default) of the current machine.

  1. Create a backup of the config directory of the current machine.
  2. Decide whether you need a partial or a full migration.
    For a full migration you can restore the entire config directory on the different machine. You can alternatively restore parts of the backup, by copying e.g., only the destinations or extractions directories.
  3. Restart the Board Connector Service, when performing a full migration or copying the server directory onto the different machine.

Note: When migrating to a new server, a new license file must be issued for that server. Contact our sales team at for more information.