Upgrade the BEMS software
If you installed the BEMS services on separate computers, complete this task on each computer that you installed a service on. Depending on the services that you install on the computer, some steps might not apply.
- Make sure you log in with the BEMS service account you created to install BEMS.
- Verify that you completed the prerequisites and preinstallation and tasks.
- Verify that the BEMS debug logging level is not set to Debug or Trace, or the upgrade or repair of the BEMS instance fails. For more information, visit KB 42408.
- Verify that you have the password for the BEMS service account.
- If you upgrade BEMS in a cluster environment, back up the BEMS cluster database.
- By default, encrypt=false is prepopulated in the Additional properties, so data between BEMS and the SQL Server is not encrypted. Existing properties that you have configured are retained. If your environment requires data to be encrypted, and requires verification of the TLS certificate, you must change the encrypt option in the Additional properties to true and add trustServerCertificate=false separated by a semicolon (no space before or after the semicolon) during the installation or after in the Dashboard. Make sure that you first import the CA certificate that is signing your SQL Server certificate into the Java certificate store before you change the properties, or BEMS will be unable to connect to the SQL Server database. For more information, see Import the CA certificate into the Java certificate store.
Note: If you enable encryption for all data that is sent between BEMS and the SQL Server, it may cause higher than normal CPU usage.