FAQ - Key Considerations and Best Practices for BME upgrade

FAQ - Key Considerations and Best Practices for BME upgrade

This article lists the key considerations and best practices when upgrading an existing WebEdition (WE) installation to BME. Upgrading the server software itself is a straight forward procedure that is taken care by the installer. But connecting the Clients (Devices & EnrollClient) to BME require careful consideration based on the site constellation. 

Its recommended to upgrade Enroll components (BCS10 and EC10) to v20.x when upgrading to BME. Beware v20.x is compatible only with BME and FW3.xx. In case, terminals run FW2.xx, then enroll components should be retained on v10.x.

(a) Connecting new terminals (FW3.x) using Activation code (recommended):
The simplest and recommended option is to connect the terminals using activation code displayed at the completion of startup wizard. During activation, the required connection settings are transferred under the hood masking all the complexities from the installer. The BCS20/EC20 also supports activation code mechanism. Also, this option is documented in BME install guide.

(b) Connecting existing terminals (upgraded from FW2.x to FW3.x) without factory reset:
When upgrading existing WE installations, to connect devices running FW2 the option (1) requires factory reset which may not be feasible due to infrastructure constraints. In this case, it is recommended to upgrade the terminals to FW3 (its available for all platforms incl. Series 12) and then connect using the procedure described in Technote: TN WebEdition Upgrade to BME PREMIUM
The BME connection package is not required if TBS signed certificate is used since all other connection parameters could be set in DeviceConfig. In case of BME installer generated certificate or custom signed, pls contact TBS support for connection package.
 
(c) Connecting existing terminals (FW2.x):
Due to site constraints, it may not be possible to update the existing Clients to latest versions before connecting to BME. For such scenarios the KB article https://help-center.tbs-biometrics.com/portal/en/kb/articles/faq-procedure-to-connect-fw2-and-ec10-bcs10-to-biomanager-enterprise-r20 explains the detailed procedure to connect FW2 and EC10/BCS10 to BME.
The FW 1.xx is not compatible with BME 


    • Related Articles

    • FAQ - System upgrade rules and recommendations

      This article explains in simple terms the requirements when upgrading the individual components in TBS system. Refer to Compatibility Matrix for further details. 1. Upgrading to WebEdition R10.5 or newer Required None. The server is backward ...

    • HowTo - Handle 'Invalid License key' error in BioManager

      BioManager reports error “Invalid License Key” after applying the license key. Solution In few installations, we observed that this error is caused by local Windows IIS server rejecting the 'PUT' REST call which is invoked when the license is applied ...

    • FAQ - Guidelines for Configuring BME with a Public IP

      This article provides recommendations on configuring BME with a public IP address or Fully Qualified Domain Name (FQDN). There are different approaches to making BME accessible beyond the internal network. Below are some of these options along with ...

    • FAQ - Guidelines for activating Clients in Miniserver BME

      This article provides the guidelines to activating Clients in BioManager ENTERPRISE (BME) running in MiniServer. In BME, Clients are validated using an activation code, which involves dedicated WebSockets (WS) channel within BME. Once activated, ...

    • FAQ - Basic backup/restore of WE database in the same MS SQL Server

      Question How can I simply backup and restore TBS WebEdition server database (in the same SQL Server installation)? Answer In order to prevent data loss, it is a good practice to regularly backup content of TBS WebEdition server database. This article ...