- BEMS Core service
- Steps to configure the BEMS-Core
- Importing CA Certificates for BEMS
- Importing and configuring certificates
- Replacing the autogenerated SSL certificate
- Configuring HTTPS for BEMS to the BlackBerry Proxy or Good Proxy server
- Assign the BEMS SSL certificate to users
- Keystore commands
- Add dashboard administrators
- BEMS-Core database
- Configure the BlackBerry Dynamics server in BEMS
- Configure a web proxy server
- Enabling log file compression
- Uploading BEMS log and statistical information
- Firebase Push Notifications
- Enabling FIPS Mode in BEMS
- Configuring BlackBerry Dynamics Launcher
- Next steps
- Appendix: Java Memory Settings
- Appendix: Server-side services
- BlackBerry Docs
- BlackBerry Enterprise Mobility Server 3.5
- Configuring BEMS-Core
- Importing and configuring certificates
- Replacing the autogenerated SSL certificate
- Steps to replace the autogenerated SSL certificate with a self-signed certificate for one BEMS node
- Move the certificate into the BEMS keystore
Move the certificate into the BEMS keystore
BEMS
keystore- Copy the keystore file to theBEMSkeystore. The keystore filename is bems.pfx or a non bems.pfx filename (for example, bemsnew.pfx).
- Stop theGood Technology Common Servicesservice from theWindowsService Manager.
- Navigate to<.drive>:\Program Files\BlackBerry\BlackBerry Enterprise Mobility Server\Good Server Distribution\gems-quickstart-<version>\etc\keystores
- In the keystores folder, rename the bems.pfx file to bems_bak.pfx.
- Copy the bems.pfx or the new keystore file (for example, bemsnew.pfx), file fromC:\bemscertto<.drive>:\Program Files\BlackBerry\BlackBerry Enterprise Mobility Server\Good Server Distribution\gems-quickstart-<version>\etc\keystores
- Rename the file to bems.pfx.