Install the BEMS software
- Verify that you completed the preinstallation and prerequisite requirements.
- If your organization uses AlwaysOn support for SQL Server, complete the steps in Appendix: AlwaysOn Availability support for SQL Server and verify that you have the FQDN of the AlwaysOn Listener and name of the database that is added to the AlwaysOn Availability Group available before you install the BEMS software. For information about supported SQL Server versions, see the BEMS Compatibility Matrix.
When you install the BEMS services on separate computers, all steps will not apply. Complete this task on each computer that you install one or more services on.
- By default, encrypt=false is prepopulated in the Additional properties, so data between BEMS and the SQL Server is not encrypted. 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.