Deploying MobileFabric in your Environment: Part I - Topology
Ajay Bhat - May 23, 2016 - Engineering
This post is Part I of a multi-part series focusing on deploying MobileFabric in your On Premise environment. In this series, Pattabhi Dasari and I will provide details on how to plan out your MobileFabric deployment, and share best practices.
Introduction
Kony MobileFabric is an enterprise-grade mobile backend as a service (MBaaS). Depending on a customer’s app requirements, number of users and other factors, it can be set up in various configurations with component servers configured on single or multiple physical / virtual hosts. Over the course of the next few posts, we’ll go through a detailed description of various software and hardware requirements to get MobileFabric set up in a production environment.
Software Requirements
Operating System: Linux / Windows
Java Runtime Environment: JDK 1.7 or 1.8
Session/cache management: Memcached
Http Servers (reverse proxy): Apache/Microsoft IIS
Application Servers: JBoss, or Tomcat, or Weblogic or WebSphere
Database: MySQL or Oracle or MS SQL or DB2
NOTE: Refer Kony MobileFabric documentation for exact versions of the above software supported for your version of Kony MobileFabric.
Deployment Topology
A typical deployment topology for MobileFabric in Production looks like the diagram below (individual components may vary based on individual requirements)
NOTE
1. If a Load Balancer is not present between the Presentation Tier and Application Tier, then load balancing and rewrite rules need to be configured on Apache/Microsoft IIS server.
2. The end user mobile device does NOT need to have access to the MobileFabric Console, which is used only for MobileFabric app development / deployment / management.
A development environment can consist of any or all of the services that form part of MobileFabric. A typical development environment is shown below:
For moving a MobileFabric app from a development environment to a production environment, you need to export the app from the source (dev) environment, and import it into the new environment (say, UAT or Production). More information on how to achieve this is here.
In part II, we’ll discuss sizing requirements for MobileFabric.