- About this guide
- BlackBerry Dynamics background
- BlackBerry Dynamics API reference
- FIPS 140-2 compliance
- Easy Activation
- Securing cut-copy-paste on devices (Data Leakage Prevention, or DLP)
- Shared Services Framework
- Support for fingerprint authentication
- Support for Face ID
- Support for certificates
- Support for the "Do not require password" setting
- Bypassing the App Lock screen
- BlackBerry Dynamics contributor code on GitHub
- Supported languages
- Requirements
- BlackBerry Dynamics software versions
- Compatibility with earlier releases
- Software requirements
- BlackBerry Dynamics entitlement ID and version
- Requirements: Frameworks and libraries
- Requirement: URL scheme
- Required build-time declarations: URL type
- Using NSURLSystem for KCD
- GDAssets.bundle required in build phase
- Compatibility with the BlackBerry Dynamics Launcher Library
- App UI restrictions
- Supported and unsupported features on iOS
- Link for FIPS in Objective-C or C++
- Steps to get started with the BlackBerry Dynamics SDK
- Programming with the BlackBerry Dynamics SDK and BlackBerry Enterprise Mobility Server services
- Sample apps in Objective-C
- BlackBerry Dynamics and the Swift programming language
- Testing and troubleshooting
- Readying your app for deployment: server setup
- Details of support for client certificates
- BlackBerry Docs
- BlackBerry Dynamics SDK for iOS 5.0
- BlackBerry Dynamics SDK For iOS Development Guide
- Readying your app for deployment: server setup
Readying your app for deployment: server setup
You want to test your app on a BlackBerry server before you deploy it into production. You need to become familiar with how to setup and configure such a server. You have options available: either
BlackBerry UEM
or the older Good Control
.Check with your IT or other department to see what test servers might already be available in your organization.
BlackBerry UEM preferred
BlackBerry UEM
preferredBlackBerry UEM
is the primary server configuration to test and deploy your app. If you upgrade from
Good Control
to BlackBerry UEM
, you not only get to use the great feature set that Good Control
provides but you also get to take advantage of an enhanced feature set such as:
- Support for more policies for operating systems
- Better app management
- More container types
- Improved administration and provisioning
- Advanced connectivity and networking
- Expanded compliance and integrity checking
- Additional email, content, location, and certificate features
- Access to BlackBerry Web Services APIs
BlackBerry UEM
to manage BlackBerry
Dynamics
apps, see the BlackBerry UEM
Administration Guide.Standalone Good Control
Good Control
The standalone
Good Control
server is also available, but BlackBerry encourages you to use BlackBerry UEM
for your tests and deployment. For information about getting started with Good Control
, see Developer Bootstrap: Good Control
Essentials.