Update a configuration by creating a new version
If you want to update an existing project configuration, you can create a new version of it. A typical use case is to fix a configuration bug or change an encryption key.
The configuration file in the editable BALCFG format.
I don't have the BALCFG file. What can I do?
First, please find out the configuration name and version. They're e.g. displayed in BALTECH ID-engine Explorer. Name and version are the file name of the corresponding BALCFG file. With that file name, you can check back with the provider of the configuration. If you bought the reader with a pre-existing configuration, let us know the file name, and we'll provide the BALCFG file to you.
Please note that BEC/BEC2 files cannot be edited. Likewise, it's not possible to read out and edit a reader's configuration. Access to a reader's configuration is limited to support purposes and only covers non-security-relevant data.
Create new configuration version
Open BALTECH ConfigEditor.
If you haven't installed it yet, you can download it here as part of BALTECH ToolSuite.
Open the BALCFG file of the configuration you want to create a new version of.
Click Create a New Version.
A new draft version is created.
Make the required changes to the configuration.
- To view and edit the settings in an existing component, select it in the Configuration Components list at the top right.
- To delete an existing component, select it and click the Minus icon.
- To add a new component, click the Plus icon.
For configurations created with ConfigEditor v5.00 or above, you'll be notified if added components are incompatible with existing ones, or if you've deleted a required component.
In Administrative Information, describe the Changes in This Version.
Click File > Save Draft.
The new version will be saved as a draft. Once you've tested your changes and are happy with them, release the new version to export a deployable file. You can deploy this file to your readers without having to remove the previous version.
The description of changes will be added to the Change Log, and the BALCFG file's name changes from -DRAFT to -<version number>.
Keep the default versioning
The version information that is automatically added to BALCFG file names helps you keep track of your versions: -DRAFT files are work in progress, whereas files with version numbers have a defined state. By sticking to this versioning, you avoid confusion as you'll never end up with 2 competing versions having the same version number.