BlackBerry Dynamics applications can be run in a mode in which the authentication of the end user at the enterprise is only simulated. This is enterprise simulation mode.

Enterprise simulation mode is for use when developers are developing new applications, or migrating existing applications.

In enterprise simulation mode, there is no need for a valid activation key, no communication with BlackBerry Dynamics servers at the enterprise, and in fact no need for these servers even to be in place. Communication with the BlackBerry Dynamics Network Operation Center does still take place in enterprise simulation mode.

Enterprise simulation mode isn't suitable for production deployment.

BlackBerry Dynamics applications can only be run in enterprise simulation mode on a device emulator, such as the Android emulator that comes with the Android SDK.

To switch on enterprise simulation mode, add an entry to the application's settings.json file as follows:

"GDLibraryMode": "GDEnterpriseSimulation"

The settings.json file must be in the assets/ folder of the application. Absence of this entry from the settings.json file means that the application will process default enterprise authentication.

Network Operation Center Access: Communication with the BlackBerry Dynamics Network Operation Center (NOC) takes place during initial activation of the application, even in enterprise simulation mode. This means that the NOC must be accessible from the environment in which the application is executing.

In enterprise simultaion mode, a BlackBerry Dynamics application behaves differently:

"Simulated" appears in the BlackBerry Dynamics runtime user interface, as shown in the screen capture below.
Any values can be entered in the BlackBerry Dynamics activation screen, and will be accepted for enterprise activation. A value that isn't an email address can be entered in the email address field. Any value that is long enough can be used as the access key.
No information will be sent to any BlackBerry Dynamics enterprise servers, not even the values entered in the set-up screen.
The provisioning and policy set-up flow will be simulated in the user interface.
A hard-coded set of security and compliance policies will be in operation. In these policies, authentication is not delegated.
If run on a real device, not a simulator, the application will be wiped.
Any attempt to change the mode of an application that is already installed from default to simulated will also result in a wipe.
There is no lost password recovery.
The BlackBerry Dynamics Inter-Container Communication (ICC) protocol cannot be used. This means that AppKinetics cannot be used.

The secure storage, secure communication, and Push Channel programming interfaces are all available in enterprise simulation mode. Secure communication connections can't be made via the BlackBerry Dynamics proxy infrastructure, but can be made directly. For example, a connection to an enterprise application server might be possible from a device emulator running on a machine that is on the enterprise LAN or VPN.

See also: GDAndroid, for default enterprise authorization processing.; Network Operation Center server addresses on the application developer portal for IP address and port number details.; Manuals page for the BlackBerry Dynamics enterprise servers for the Platform Overview. It has more information on the BlackBerry Dynamics enterprise servers.

Screen capture

The following screen capture shows how the BlackBerry Dynamics runtime user interface differs when enterprise simulation mode is switched on.

Application running in Enterprise Simulation Mode