Die BPC Version 4.1 wird nicht mehr gewartet.

Sollten Sie diese BPC Version nutzen, empfehlen wir Ihnen eine Migration auf eine aktuelle Version. Die Dokumentation zur neusten BPC Version finden Sie hier. Sollten Sie Fragen haben, wenden Sie sich bitte an unseren Support.

Installation with a Preconfigured BPC

A preconfigured BPC can be started immediately after running Installation. This is particularly useful in a Kubernetes/container environment.

Prerequisites and Preparation

An existing BPC installation is required, whose configuration will serve as the basis for the new system. To do this, export the required configurations from that installation via Deployment into a JSON file (Deployment Target).

Usage

Rename the JSON file previously created via Deployment. It must have the file extension .bpc-deployment-export. Now copy this file into the [KARAF]/deploy directory in the newly set up system. The configurations it contains will be imported automatically.

Notes:

  • The system checks every 3 seconds to see if a file with this file extension exists in the [KARAF]/deploy directory

  • Only deployment exports in which ALL used modules are loaded can be imported. For example, if Karaf is currently booting up, the system will try again in 3 seconds, and so on.

File extension

As mentioned above, the file to be imported must initially have the file extension .bpc-deployment-export.

After processing, this import file is renamed so that the same file isn’t processed repeatedly. It will be given one of the following file name extensions:

  • .processed - after successful processing

  • .empty - if the import file does not contain module information

  • .invalid_json - if the import file does not contain valid JSON

  • .error - if an error occurred while checking whether all relevant modules were loaded

  • .error_on_import - if a problem occurred during the import

Keywords:
Press Esc to exit full screen
Modal image placeholder
Press Esc to exit full screen