![]() ![]() In our case, we confirmed an issue with Blackberry support that there is a problem with the SSL handshake from the log: If you encounter an error similar to the below, check with your network administrator. Then, restart the Good Technology Common Services in the Windows Services Manager for it to take effect. Per Blackberry: “Because APNS pushes are sent using the BlackBerry Dynamics NOC, which resides outside of your enterprise network, a proxy server might be required to access the BlackBerry Dynamics NOC.”įill in the information that fits your environment. This may or may not be required depending on your network configuration. The exact setting is based on your environment and thus may look different than mine. Now, we are ready to configure Microsoft Exchange Server. Do not use the cluster name or hostname of the server in the cluster. If the BEMS database is migrated to SQL AlwaysOn Availability Group (AAG) later on, you will need to set the server to the AlwaysOn Listener as FQDN. Namely, the areas of focus are:įor the Database, there should not be anything to configure other than testing to make sure the connection is successful. Specifically, we will configure the Push Notification service. We will now move onto configuring BEMS service. Simply by removing any special character from your password, you will be able to save your credential here. Why is this an issue is beyond anyone’s guess.Īnd here’s how to specify the credential.Īs I mentioned earlier, you will get the error below if your password contains any special character. Interestingly or not, your online portal password must not contain a list of special characters including an exclamation point per this KB. To expedite troubleshooting with Blackberry technical support in the future, it’s best to specify the log upload credentials which should be the same as the one you use to log onto Blackberry myAccount. We will now enable log file compression to save valuable disk space on the server. Next, we will add dashboard administrators so that other admins on your team can log into the same dashboard. Usually, http is fine assuming both the proxy server (s) and BEMS server(s) are behind the same firewall. Let’s start with configuring the Blackberry Dynamics server in BEMS.įill in the hostname as FQDN and specify the protocol that is required in your environment. From your local workstation: Unlike UEM, you need to configure most of the settings within each BEMS independently if more than one instance exists in your environment.To access the BEMS dashboard, you can navigate via either of the URLs below: Otherwise, you may run into database connectivity issue during configuration. The same can happen to UEM as well.Īs I mentioned in part 1 of this series, you may also want to check and confirm the account specified under Log On As for Good Technology Common Services (Window service) matches what you used during installation. Otherwise, you may run into a compatibility issue with BEMS later on. In this post, I will focus on configuring BEMS for Blackberry Push Notifications.īefore proceeding further, I highly recommend turning off auto-update within Java. Welcome back! This is part 2 of the series on implementing Blackberry Enterprise Mobility Server (BEMS).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |