Deploying a Production App Scope
This section describes some common tasks when deploying the Akula Server into a production environment. Some tasks are specific to an app scope, and other tasks are specific to your environment.
Configuring the server environment
The Akula Server uses built-in services such as a database and embedded JMS server so that you can develop apps quickly. In a production environment, however, you will want to connect the Akula Server to your enterprise back end systems.
The following table describes embedded or pre-configured Akula services that you typically replace with your enterprise back end systems:
The Akula Server includes an embedded Apache Derby database for development and testing purposes. The database is responsible for managing users, sessions, data sync, and other configuration and run-time information.
In a production environment, connect the Akula Server to any JDBC-compliant database. For more information, see Specify the Database for the Akula Server.
The Akula Server push and action queue services use an embedded JMS server (ActiveMQ). In a production environment, configure Akula to use your enterprise-class JMS server.
For more information, see Configure a JMS Server.
The Akula Server includes an internal Memcached implementation for session caching. In a production environment, configure Akula to use an external cache manager.
For more information, see Configuring Session Caching.
The Akula authentication mechanism relies on an external realm, where the realm contains the collection of users and groups that can connect to an app scope running on the Akula Server. Before deploying a production AKZ file, be sure your Akula Server is configured to use your enterprise security manager.
For more information, see Defining a Security Manager.
Configuring your app scope
This section describes some common practices you might use when preparing an app scope (AKZ) for deployment. For information on creating and deploying an AKZ file, see Building and Deploying AKZ Files.
The following table describes app-scope specific tasks that you should perform before deploying the AKZ file to your server:
Developer Mode includes extra information about errors that can be used by developers when troubleshooting. By default, Developer Mode on the Akula Server is enabled. Before deploying your AKZ file, disable Developer Mode for your app scope by setting the value of the
For more information, see Handling Exceptions and Errors.
In a production environment, you should consider reducing the logging levels of your app scope. The default log levels for the Akula Server include INFO and WARN messages, in addition to ERROR messages.
For more information, see Configure Logging.
While building and testing an app scope, you typically use app properties that are specific to the development environment. For example, you might use custom app properties to define locations of testing or development servers. When preparing for deployment, be sure to update app properties so that you are pointing to production services or using values appropriate to a production environment.
For more information, see App Properties Overview.
|Akula Administrator Group|
To disable the server administrator group, set the
For more information, see Define Akula Server Administrators.
|Roles and Users|
After configuring the security manager to use your production security environment, you should then do the following for your production-ready app scope before deploying it:
For more information, see Authorizing Users.
If your app scope uses push notifications on the iOS platform, you should set
For more information, see Configuring Apps for Push.