Skip Navigation

Using enterprise simulation mode

Although Enterprise Simulation mode isn't suitable for production deployment of your app, it is ideal during development and for verifying proper execution and behavior when you migrate or convert existing
Android
apps to
BlackBerry Dynamics
.
In simulation mode, a valid activation key is not required to open the app because there is no direct communication with
BlackBerry Dynamics
servers in your organization.
Communication with the
BlackBerry Dynamics NOC
still takes place during initial activation of the app, even in Enterprise Simulation mode. This means that the NOC must be accessible from the environment in which the application is running.
In simulation mode your
BlackBerry Dynamics
apps are run on an
Android
virtual device or AVD that comes with the
Android SDK
.
The Secure Storage, Secure Communication, and Push Channel APIs are all available in Enterprise Simulation mode. However, the communication APIs will not be able to connect to your organization's application servers through the
BlackBerry Dynamics
proxy infrastructure. You can make connections to your organization's application servers if, for example, the AVD is running on a computer on your organization's LAN or VPN.
To enable simulation mode, whether you use an IDE or a text editor, you must change the following line in your application’s
settings.json
file. The
settings.json
file is located in the
../assets/
folder of the app and must remain there
Change this...
…to this
"GDLibraryMode":"GDEnterprise"
"GDLibraryMode":"GDEnterpriseSimulation"
When
GDLibraryMode
is set to
"GDLibraryMode":"GDEnterpriseSimulation"
, default enterprise authentication is invoked to open the application.
Be sure to change the value of
GDLibraryMode
back when done testing the app before compiling it for production.

Behavioral effects of enterprise simulation

In Enterprise Simulation mode, the app behaves differently than during standard enterprise execution in the following ways:
  • The word
    [Simulated]
    appears in the
    BlackBerry Dynamics
    Runtime user interface.
  • Any email address and activation key (PIN) is accepted for enterprise activation.
  • No information is actually sent to
    BlackBerry Dynamics
    servers, including the email address and activation key.
  • The provisioning and policy setup flow is only simulated in the UI.
  • A hard-coded set of security and compliance policies is enforced operation. Authentication delegation policy is not supported.
  • If you run an app built for enterprise simulation mode on a device and not an emulator, the app will be wiped.
  • If you try to change the mode from
    GDEnterprise
    to
    GDEnterpriseSimulation
    for an app that is already installed on a device, it will be wiped.
  • Lost password recovery is not available.
  • Inter-container Communication (ICC) cannot be used, which means that the Shared Services Framework cannot be used