Kony MobileFabric Deployment Guide Release 7.3 Document Relevance and Accuracy This document is considered relevant to the Release stated on this title page and the document version stated on the Revision History page. Remember to always view and download the latest document version relevant to the software release you are using. 2017 by Kony, Inc. All rights reserved 1 of 26
Kony MobileFabric Deployment Guide Copyright 2014 Kony, Inc. All rights reserved. April, 2017 This document contains information proprietary to Kony, Inc., is bound by the Kony license agreements, and may not be used except in the context of understanding the use and methods of Kony, Inc., software without prior, express, written permission. Kony, Empowering Everywhere, Kony Nitro, and Kony Visualizer are trademarks of Kony, Inc. MobileFabric is a registered trademark of Kony, Inc. Microsoft, the Microsoft logo, Internet Explorer, Windows, and Windows Vista are registered trademarks of Microsoft Corporation. Apple, the Apple logo, itunes, iphone, ipad, OS X, Objective-C, Safari, Apple Pay, Apple Watch, and Xcode are trademarks or registered trademarks of Apple, Inc. Google, the Google logo, Android, and the Android logo are registered trademarks of Google, Inc. Chrome is a trademark of Google, Inc. BlackBerry, PlayBook, Research in Motion, and RIM are registered trademarks of BlackBerry. SAP and SAP Business Suite are registered trademarks of SAP SE in Germany and in several other countries. All other terms, trademarks, or service marks mentioned in this document have been capitalized and are to be considered the property of their respective owners. 2017 by Kony, Inc. All rights reserved 2 of 26
Kony MobileFabric Deployment Guide Revision History Date Document Version Description of Modifications/Release 04/10/2017 1.3 Document updated for 7.3 GA 10/24/2016 1.2 Document updated for 7.2 GA 07/18/2016 1.0 Document Released for MobileFabric 7.1 GA 2017 by Kony, Inc. All rights reserved 3 of 26
Kony MobileFabric Deployment Guide Table of Contents 1. Preface 5 1.1 Purpose 6 1.2 Intended Audience 6 1.3 Formatting Conventions Used in This Guide 6 1.4 Contact Us 8 2. Deployment Guide 9 2.1 Software Requirements 10 2.2 Deployment Topology 11 2.3 Development Topology 12 2.3.1 Moving a MobileFabric App to a Different Environment 13 2.4 App Server Sizing 13 2.4.1 Sample Hardware Configurations 14 2.5 Database Growth Sizing 18 2.6 Session Management 20 2.6.1 Memcache Session Management 21 2.6.2 J2EE In-built Session Management 23 3. Index 25 2017 by Kony, Inc. All rights reserved 4 of 26
1. Preface Kony MobileFabric Deployment Guide 1. Preface Kony MobileFabric is a Mobile Back-end as a Service (MBaaS) provider that helps developers build native and web apps for mobile. Various back-end services are easily integrated with the application irrespective of whether the application is built using JavaScript, PhoneGap, ios, or Android frameworks. MobileFabric allows you to define the back-end to build native mobile apps for ios, Android, and HTML5-based apps for modern browsers. MobileFabric ensures that developers build mobile applications quickly by focusing on core areas and obtaining secured back-end services instantly. MobileFabric has multiple features that can be used - Identity, Integration, Orchestration, Objects, Sync, and Engagement Services. These features can be accessed through a common, centralized console. For successful authentication with users, and to access the centralized features of MobileFabric, Kony recommends that you install the following MobileFabric features on premises: Kony MobileFabric Identity and Console Kony MobileFabric Integration Kony MobileFabric Engagement Services Kony MobileFabric Sync Services Kony MobileFabric supports the following back-end services for your applications: Identity: This feature allows you to define the type of authentication used for granting access to your application. MobileFabric supports the following authentication services: Microsoft Active Directory, Salesforce, Security Assertion Markup Language (SAML), Kony SAP Gateway, Kony Facebook, and Kony User Repository. Integration: This feature allows you to define various back-end services for your application. You can define the service in XML, SOAP, JSON, Java, Salesforce, and Kony SAP Gateway. 2017 by Kony, Inc. All rights reserved 5 of 26
1. Preface Kony MobileFabric Deployment Guide Orchestration: This feature allows you to create two types of orchestration services. They are: o Composite: Allows you to run two or more services concurrently or sequentially. o Looping: Allows you to run a single service in a loop until the loop ends or an exit criteria is met. Synchronization: This feature allows you to define the synchronization services for your application. Sync supports only Web Services, except SAP Sky. Engagement Services: This feature allows you to define and configure push messaging services for your application. 1.1 Purpose The document helps you familiarize with the Kony MobileFabric and provide procedural information to perform various tasks required to build your application. 1.2 Intended Audience This document is intended for developers who would like to turn their applications into an enterprisegrade applications using Kony back-end services. 1.3 Formatting Conventions Used in This Guide The following formatting conventions are used throughout the document: 2017 by Kony, Inc. All rights reserved 6 of 26
1. Preface Kony MobileFabric Deployment Guide Conventions Explanation Monospace User input text, system prompts, and responses File path Commands Program code File names Italic Emphasis Names of books and documents New terminology Bold Windows Menus Buttons Icons Fields Tabs Folders URL Active link to a URL. Note: Provides helpful hints or additional information. Important: Highlights actions or information that might cause problems to systems or data 2017 by Kony, Inc. All rights reserved 7 of 26
1. Preface Kony MobileFabric Deployment Guide 1.4 Contact Us We welcome your feedback on our documentation. Write to us at techpubs@kony.com. For technical questions, suggestions, and comments, or to report problems on Kony's product line, contact support@kony.com. 2017 by Kony, Inc. All rights reserved 8 of 26
2. Deployment Guide Guidelines for deploying MobileFabric on-premises. Kony MobileFabric is an enterprise-grade mobile backend as a service (MBaaS). How you set up MobileFabric depends your application requirements and the number of users of your applications. You can set up MobileFabric on-prem in many configurations with component servers that are configured on single or multiple physical and virtual hosts. "Software Requirements" on the next page "Deployment Topology" on page 11 "Development Topology" on page 12 "App Server Sizing" on page 13 "Database Growth Sizing" on page 18 "Session Management" on page 20 MobileFabric Deployment Glossary Term Definition presentation tier The top-most level of an application, the user interface. application tier The business logic, or logic tier, it controls the functionality of an application. J2EE Java Platform, Enterprise Edition EC2 Amazon Elastic Compute Cloud (Amazon EC2) is a web service that provides resizable compute capacity in the cloud. 2017 by Kony, Inc. All rights reserved 9 of 26
Term Definition RDS Amazon Relational Database Service (Amazon RDS) is a web service that makes it possible to set up, operate, and scale a relational database in the cloud. VM A virtual machine (VM) is an emulation of a particular computer system. UAT User acceptance testing. high availability A system or component that is continuously operational for a desirably long length of time. separation of concern A design principle for separating a computer program into distinct sections, such that each section addresses a separate concern. payload The part of the transmitted data that is the actual intended message. Payload does not include information sent with it such as headers or metadata, sometimes referred to as overhead data. A-series, Dv2- series Sizes and options for the Azure virtual machines. session affinity Enables the load balancer to bind a user's session to a specific instance. This ensures that all requests from the user during the session are sent to the same instance. 2.1 Software Requirements The following are the underlying software requirements for MobileFabric on-premises. 2017 by Kony, Inc. All rights reserved 10 of 26
For a complete list operating systems, app servers, databases, and Java Runtime Environment supported by Kony MobileFabric, refer to Software Requirements by Kony MobileFabric 7.1. Requirement Supported Operating System Linux or Windows Java Runtime Environment JDK 1.7 or 1.8 Session/cache management Memcached HTTP servers (reverse proxy) Apache or Microsoft IIS Application servers JBoss, or Tomcat, or WebLogic or WebSphere Database MySQL or MariaDB or Oracle or MS SQL or DB2 LUW 2.2 Deployment Topology The following diagram depicts the topology of a typical deployment of MobileFabric in a Production environment. Individual components can vary based on specific requirements. Note: If a load balancer is not present between the presentation tier and application tier, then you must configure load balancing and rewrite rules on the Apache or Microsoft IIS server. Note: The end user mobile device does not need to have access to the MobileFabric Console. You use the console for MobileFabric app development, deployment, management. 2017 by Kony, Inc. All rights reserved 11 of 26
2.3 Development Topology A development environment can consist of any or all of the services that form part of MobileFabric. The following diagram depicts the topology of a typical deployment of MobileFabric in a development environment. 2017 by Kony, Inc. All rights reserved 12 of 26
2.3.1 Moving a MobileFabric App to a Different Environment To move a MobileFabric app from a development environment to a production environment, export the app from the source (dev) environment, and import app in to the new environment for example, a UAT or Production environment. To learn more about moving a MobileFabric app, see Exporting and Importing an Application. 2.4 App Server Sizing This section provides a guide to sizing and capacity that can help you determine the optimal deployment configurations for your apps and user requirements. The following table illustrates the sizing for each MobileFabric component. 2017 by Kony, Inc. All rights reserved 13 of 26
MobileFabric Runtimes Throughput/Sec Capacity CPU Memory Integration & Identity 35 request/sec 1-1.25 million 1 CPU per JVM 3 GB with payload 50kb session per per year JVM Engagement 35 request/sec 60-70 pushes/sec 1 CPU per JVM 2 GB per JVM Sync 30 request/min 120 concurrent 1 CPU per JVM 3 GB with payload 1mb users/sec per JVM Note: 1 CPU and 2 GB is allocated for the operating system on each physical computer. Please note that Metrics and integration admin console Web archives (WARs) are installed as part of integration. The integration admin console provides basic reports. If advance reporting is required, install the reporting portal based on Jasper (Kony MobileFabric Reporting and Analytics - Installation Guide). Note: Metrics should be installed along with Integration services on the same physical computer. 2.4.1 Sample Hardware Configurations The following scenarios illustrate a range of hardware configurations for MobileFabric deployment. 2.4.1.1 Scenario A A company requires MobileFabric Integration to handle 1.25 million sessions/year, MobileFabric Engagement for 80 pushes/sec, and MobileFabric Sync for 120 concurrent users/sec. To maintain high availability, the customer adds an additional physical computer. 2017 by Kony, Inc. All rights reserved 14 of 26
Hardware Configuration MobileFabric Java virtual machines Physical Computer/VM 5 core & 12 GB RAM Console, Identity, Integration, Engagement and Sync Physical Computer/VM 4 core & 10 GB RAM Integration, Identity, Engagement and Sync Physical Computer/VM 2 core & 4-5 GB RAM Sync or Engagement or Integration and Identity Physical Computer/VM 4 core & 16 GB RAM (applicable for Database) Database components of the MobileFabric: Console (accounts and workspace) Identity (authglobaldb and authconfig) Integration (konyadmin, devicedb, konyreports (Metrics)) Engagement Sync 2.4.1.2 Scenario B A company requires MobileFabric Integration to handle 2 million sessions/year, MobileFabric Engagement for 80 pushes/sec, and MobileFabric Sync for 300 concurrent users/sec. To maintain high availability, the company adds an additional physical computer. Hardware Configuration MobileFabric Java virtual machines 1 Physical Computer/VM 8 core & 12 GB RAM 2 Integration & Identity, 3 Sync & 1 Engagement 2017 by Kony, Inc. All rights reserved 15 of 26
Hardware Configuration MobileFabric Java virtual machines 2 Physical Computers/VM 4 core & 10 GB RAM Integration + Identity, Engagement & Sync Physical Computer/VM 4 core & 16 GB RAM (applicable for Database) Database components of the MobileFabric: Console (accounts and workspace) Identity (authglobaldb and authconfig) Integration (konyadmin, devicedb, konyreports (Metrics)) Engagement Sync 2.4.1.3 Scenario C A company requires MobileFabric Integration, Identity, Engagement and Reports Portal for handling 1.2 million session/year on Azure Linux cloud with SQL Server. As an illustration, each Standard tier: Dv2-series Standard_D3_v2 server can handle 1.25 million sessions per year. Two Standard tier: Dv2-series Standard_D3_v2 servers are configured for high availability so that the environment can handle any spikes and serve up to 2 million sessions per year. For every additional 1.25 million session /year, you will need an additional Standard tier: Dv2-series Standard_D3_v2 server. If high availability is required for MobileFabric Console & Reports Portal, the deployment requires 2 Standard tier: A-series Standard_A2 servers. The following tables also include a configuration for AWS that uses EC2 and RDS for MySQL. For Production 2017 by Kony, Inc. All rights reserved 16 of 26
Azure AWS MobileFabric JVM s 2 standard tier Dv2-series Standard_D3_v2 2 M3 series m3.xlarge Integration & Identity, & Engagement 2 Standard tier A-series Standard_A2 2 T2 series t2.medium MobileFabric Console & Reports Portal Azure SQL Database Standard S1 (200 edtu per pool) or 2 Standard tier: Dv2-series Standard_D3_v2 for MySQL/SQL Server Amazon RDS for MySQL db.m4.2xlarge or 2 M3 series m3.xlarge for MySQL/SQL Server For Development/QA Azure AWS MobileFabric JVM s 1 standard tier A-series Standard_A3 1 M3 series m3.xlarge Integration & Identity, & Messaging Azure SQL Database Standard S1 (Basic (200 edtu per pool) or Standard tier: A- series Standard_a3 for MySQL/SQL Server Amazon RDS for MySQL db.m4.2xlarge or 2 M3 series m3.xlarge Note: If separation of concern and high availability of a particular runtime is important, you can configure runtimes on different physical nodes. For more information about VM sizes and other aspects of performance, see Sizes for virtual machines in Azure and Amazon EC2 Instance Types. 2017 by Kony, Inc. All rights reserved 17 of 26
2.5 Database Growth Sizing Database Component Data growth Size (GB) per year Planned Data Growth per year (%) Estimated Data size for 5 years In GB Data growth criteria KMS-Engagement 515 5 2846 0.1 million pushes per day 3000 - devices, EMM 300 5 1658 1500 IMEI, 1500 - users, 70000 apps, 1 crore request per month Sync 7 5 38 10000 sessions per day Metrics (Without Events) 288 0 1440 1 Million Application Sessions, 10Million Service Calls, 2 Million Custom Metrics per month 2017 by Kony, Inc. All rights reserved 18 of 26
Database Component Data growth Size (GB) per year Planned Data Growth per year (%) Estimated Data size for 5 years In GB Data growth criteria Metrics (With Events+geography) 1980 0 9900 1 Million Application Sessions, 10Million Service Calls, 2 Million Custom Metrics, 50 M Application Events, Geolocation database per month Admin Server 1 0 1 Mostly static data, excluding Logging feature (which is of trouble shooting data) Identity/auth 0.6 0 0.6 10000 users, 50 apps. This data does not grow 2017 by Kony, Inc. All rights reserved 19 of 26
Database Component Data growth Size (GB) per year Planned Data Growth per year (%) Estimated Data size for 5 years In GB Data growth criteria Waas 1 0 1 For 10 apps or 500 services with 10 operations each, asset size of 2 MB each Accounts 0.5 0 0.5 Mostly static data, excluding Logging feature (which is of trouble shooting data) 2.6 Session Management Kony MobileFabric server supports Memcache or J2EE in-built session management. Typically, Memcache is configured for Tomcat/JBoss based environments and J2EE in-built HTTP Session Management is configured for WebSphere/WebLogic environments. The following lists the session requirements for Memcache and J2EE in-built session management. Session Configuration Memcache J2EE In-built Session Session affinity load balancer Not required Required 2017 by Kony, Inc. All rights reserved 20 of 26
Session Configuration Memcache J2EE In-built Session Additional configuration Yes, need to install memcache software Not required. App servers provides session management Data replication Not Supported Yes, session replication needs to be configured on App Server 2.6.1 Memcache Session Management Memcache is an in-memory key-value store for small chunks of arbitrary data for example, strings, and objects. Memcache is a high-performance, distributed memory object caching system, generic in nature. Memcache does not support data replication across nodes. You can configure the Kony MobileFabric Server that is deployed on Tomcat to talk to any number of Memcache nodes. The nodes can be located on the same or different physical machines. All the user sessions are serialized and stored in the Memcache node. This makes it possible to deploy the Kony MobileFabric Server in an environment where session affinity is not available. The following describes typical scenarios that may occur when you use Memcache and how it handles sessions: 2.6.1.1 Scenario A Tomcat Instance is Down In this scenario, there will be no transaction failure as the session data is available in the Memcache node. The request is routed to the other Tomcat instances. The other Tomcat instances will retrieve the session data from the Memcache. 2.6.1.2 Scenario B Memcache Instance is Down In this scenario, if the session data is stored on the Memcache instance that is down, there will be a transaction failure. All the users whose session data was stored on the Memcache instance that went down, have to reinitiate the transaction. 2017 by Kony, Inc. All rights reserved 21 of 26
2.6.1.3 Scenario C Physical Computer is Down In this scenario, if the session data is stored on one of the Memcache instances of the physical computer that is down, there will be a transaction failure. All the users whose session data was stored on the Memcache instances of the failed physical computer, will have to reinitiate the transaction. The following illustrates the Memcache-Session Management scenario. 2017 by Kony, Inc. All rights reserved 22 of 26
2.6.2 J2EE In-built Session Management J2EE-based Application servers provide HTTP-based session capabilities by default. The HTTP session is managed via an in-memory key-value store. The HTTP sessions will not survive application server restarts. The following diagram illustrates this scenario. The following describes typical scenarios that may occur when you use J2EE in-built session management and how it handles sessions: 2.6.2.1 Scenario A WebLogic/Websphere Instance is Down 2017 by Kony, Inc. All rights reserved 23 of 26
In this scenario, all the users of this instance will have to reinitiate the transaction. 2.6.2.2 Scenario B Physical Computer is Down In this scenario, all the users of this physical computer will have to re-initiate the transaction. Note: If you configure session replication, the user will not have to re-initiate the transaction for the app server/physical computer restart or breakdown. You can configure session replication for small server farms for example, 2-10 app server instances. Session replication will require additional CPU and a very high-speed network connection between the app server nodes. 2017 by Kony, Inc. All rights reserved 24 of 26
3. Index Kony MobileFabric Deployment Guide 3. Index capacity 13 C configurations hardware 14 deploying on-premises 9 D deployment session management 20 sizing 13 software requirements 10 deployment topology 11 development topology 12 environment E development 12 move MobileFabric app 13 production 11 glossary of deployment 9 G 2017 by Kony, Inc. All rights reserved 25 of 26
3. Index Kony MobileFabric Deployment Guide hardware configurations 14 H high availability 14 J2EE-based app servers 23 J Memcache 21 M MobileFabric 5 move MobileFabric app 13 production environment 11 P session management 20 S J2EE in-built 23 Memcache 21 sizing 13 software requirements 10 topology 11 T 2017 by Kony, Inc. All rights reserved 26 of 26