Kony MobileFabric Installation Guide Linux

Kony MobileFabric

Installation Guide - Linux

On-Premises

Release 7.3Document 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 272

Kony MobileFabric Installation Guide - LinuxVersion1.9

Copyright 2014 by Kony, Inc.

All rights reserved.

April, 2017

This document contains information proprietary to Kony, Inc., is bound by the Kony license

agreements, andmay not be used except in the context of understanding the use andmethods 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, theMicrosoft logo, Internet Explorer, Windows, andWindowsVista are

registered trademarks of Microsoft Corporation. Apple, the Apple logo, iTunes, iPhone, iPad, OS X,

Objective-C, Safari, Apple Pay, AppleWatch, 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 inMotion, 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

servicemarksmentioned in this document have been capitalized and are to be considered the

property of their respective owners.


Kony MobileFabric On-Premises Installation Guide Linux Ver - 1.0

Copyright 2014 Kony, Inc., All rights reserved. Page 3 of 272

Revision History

Date Document Version Description of Modifications/Release

04/10/2017 1.9 Document updated for 7.3 GA Release

l Added support for MariaDB for Tomcat and

JBoss only.

l Added support for JBoss 7

l Added support for Java 8 onWebSphere

l Added support forWebSphere 8.5.5.10

l Updated bundled Apache Tomcat to

version 7.0.75

l Added ability to changeMobileFabric IP

after installation

l Metrics now configured automatically as

part of MobileFabric install onWebSphere

l Updated cookie settings on bundled JBoss

to prevent XSS attacks

l Added support for changing context root

for all MobileFabric components

03/16/2017 1.8 Document updated for 7.2.x Release

l Added support for installingMobileFabric

on a pre-configured standalone JBoss

02/27/2017 1.7 Document updated for 7.2.x Hotfix Release

l Added support for Context Root-path

Installation

Kony MobileFabric On-Premises Installation Guide Linux Ver - 1.0

Copyright 2014 Kony, Inc., All rights reserved. Page 4 of 272

Date Document Version Description of Modifications/Release

10/24/2016 1.6 Document updated for 7.2 Release

l Added support for Tomcat 7.0.70

l Added support for Shutdown port in

Tomcat

l Added support for Licensing Types for new

installation

08/22/2016 1.5 Document updated for 7.1.1 Hotfix Release

l Added support for DB2

07/18/2016 1.4 Document Released for MobileFabric 7.1 GA

l Added support for MobileFabric server

startup after successful installation of

MobileFabric (single node).

l Added support for Enabling JMS in the

JBoss Multinode through the installer.

l Added support for Tablespace choice for

Oracle

l Added support for Upgrade from 6.5.2GA

to 7.1GA

06/08/2016 1.3 Document updated for 7.0.1.x Hotfix Release

04/26/2016 1.2 Document updated for MobileFabric 7.0.1

02/29/2016 1.0 Document Released for MobileFabric 7.0


Table of Contents

1. Preface 11

1.1 Purpose 12

1.2 Intended Audience 12

1.3 Formatting ConventionsUsed in ThisGuide 12

1.4 Related Documents 13

1.5 Contact Us 13

2. Prerequisites 14

2.1 Software Requirements 14

2.2 Hardware Requirements 14

2.3 Corporate Firewall Settings - Engagement Services 14

2.4 Creating the Installation User for Linux 14

2.5 Heap and PermGen Settings 15

2.6 Configure the Standalone Existing JBoss 15

2.7 Configure Port Settings for Multinode Loadbalancer Setups 16

2.8 How to DisableWeakCiphers in Tomcat 17

2.9 How to DisableWeakCiphers in JBoss 18

2.10 JMS Configuration - WebSphereMultinode 18

3. MobileFabric Topology and Components 20

3.1 Developer Environment 23

3.2 Production Environment 24



4. MobileFabric Installation on Single Node and Multinode 25

5. Preinstallation Tasks 27

5.1 Prerequisites for MobileFabric with Oracle 27

5.2 Prerequisites for MobileFabric with DB2 30

5.3 Prerequisites for MobileFabric with SQL Server 32

5.4 DownloadMobileFabric Installer 33

5.5 Steps before installing (or) upgradingMobileFabric with the existing database 34

5.6 Create /tmp Folder 35

5.7 Install Memcached Server 35

5.7.1 libevent (memcached dependency) 35

5.7.2 Memcached Server 36

5.8 Increase JVMmemory for WebLogic Server 37

5.9 PlaceMS SQLServer Connector JAR inWebLogic Classpath 37

5.10 Configure JMS for Metrics in DomainMode for WebLogic or JBoss 38

5.11 Configure Load Balancers for Sending Host Information inMultinode 41

5.12 Configure Hibernate Dialect inWebLogic (only for WebLogic) 42

5.13 Update Listen Interfaces in host.xml for JBossCluster 42

5.14 Comment the javax-persistence-module for Kony Engagement Services on JBoss

Cluster 43

5.15 Increase innodb_log_file_size in my.cnf file - MySQL 44

5.16 Tuning File Descriptor Limits on Linux 44



5.17 Create Locator Component for Oracle Database 46

5.18 Configure Load Balancer as Proxy in JBossMultinode Setup (Optional if SSLOffloading

at Load Balancer) 48

5.19 Configure Property Settings for Logs - (only for WebSphere) 49

5.20 Install MobileFabric on a RemoteWebSphere Server with Global Security Enabled 50

5.21 Download and Install the Unrestricted JCE Policy Files 51

5.22 How to Configure Connector - JBoss 52

6. Installation Modes - Kony MobileFabric 53

6.1 Installing KonyMobileFabric - Console-mode 54

6.1.1 StandaloneMode (Single Node) Installation 54

6.1.2 InstallingMobileFabric on a Pre-configured Standalone JBoss 113

6.1.3 Configure JMS for Metrics on Existing Standalone JBoss 149

6.1.4 JBossDomainMode (Multinode) Installation 153

6.2 Installing KonyMobileFabric - Silent-mode 194

7. How to Stop and Start MobileFabric 196

7.1 Tomcat Server 196

7.1.1 Windows - To stop and start Tomcat Server 196

7.1.2 Linux - To stop and start Tomcat Server 196

7.2 To start JMS Server on Tomcat 196

7.2.1 Windows - To start JMS Server on Tomcat 196

7.2.2 Linux - To start JMS Server on Tomcat 196



7.3 JBoss Server 197

7.3.1 Windows - To stop and start JBoss Server 197

7.3.2 Linux - To stop and start JBoss Server 197

7.4 To start JMS Server on JBoss 197

7.4.1 Windows - To start JMS Server on JBoss 197

7.4.2 Linux - To start JMS Server on JBoss 197

7.4.3 For Multinode - JBoss 198

7.5 WebLogic Server 198

7.5.1 Windows - To stop and start WebLogic Server 198

7.5.2 Linux - To stop and start WebLogic Server 198

7.6 WebSphere Server 199

7.6.1 Windows - To stop and start WebSphere Server 199

7.6.2 Linux - To stop and start WebSphere Server 199

8. Upgrading Kony MobileFabric Components 200

8.1 Prerequisites 200

9. Installing Hotfix Archives for MobileFabric - Linux 208

9.1 Patch Installer GA Versions 208

9.2 Prerequisites 208

10. Uninstalling Kony MobileFabric 215

11. Post-Installation Tasks 218

11.1 Configuring Secure Sockets Layer (SSL) Certificate 218



11.1.1 How to Add an Installer Generated Self-Signed SSLCertificate to Cacerts 219

11.1.2 How to Add an Existing SSLCertificate to Cacerts 219

11.2 JDK Version Compatibility 220

11.3 How to ConfigureMemcached for Integration Services 221

11.4 Configure Deployment of mbaasportal.war File for Multi-Node 222

11.5 How to Load DeviceDB Data (User Agents Data) 222

11.6 Remote Installation Pre-requisites 225

11.6.1 InstallingMobileFarbic Remotely 225

12. FAQs and Troubleshooting 226

12.1 How to Configure JBossCluster 235

12.2 How to Configure a Custom JAR File onWebLogic 235

12.3 How to Configure Heap and PermGen Size 236

12.3.1 Configuring Heap and PermGen Size for Tomcat 236

12.3.2 Configuring Heap and PermGen Size for JBoss 236

12.3.3 Configuring Heap and PermGen Size for WebLogic 237

12.4 How to ConfigureMobileFabric Behind a Reverse Proxy 237

12.5 How to Configure Frontend HTTPS to Tomcat HTTP Redirection 239

12.6 WebSphere FAQs 239

12.7 How to Change Log Levels 239

12.8 Context Root-path 242

12.8.1 Approach 1: Changing Context Root Path after the installation using the Installer 243



12.8.2 Approach 2: Changing Context Root usingManual Install Steps 255

12.8.3 Accessing Context Based Root MobileFabric Instance through Visualizer

Enterprise 270


1. Preface Kony MobileFabric Installation Guide - LinuxVersion1.9

1. Preface

KonyMobileFabric is aMobile Back-end as a Service (MBaaS) provider that helps developers build

native and web apps for mobile. MobileFabric allows you to define the back-end to build nativemobile

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 hasmultiple features that can be used - Identity, Integration,

Objects, Orchestration, Sync, and Engagement Services. These features can be accessed through a

common, centralized console.

For successful authentication with users, and to access centralized features of MobileFabric, Kony

recommends that you install the followingMobileFabric features on premises:

l KonyMobileFabric Identity and Console

l KonyMobileFabric Integration

l KonyMobileFabric Engagement Services

l KonyMobileFabric Sync

KonyMobileFabric supports the following back-end services for your applications:

l 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 AssertionMarkup Language (SAML), Kony SAP Gateway,

Kony Facebook, and KonyUser Repository.

l 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.

l Orchestration: This feature allows you to create two types of orchestration services. They are:

n Composite: Allows you to run two or more services concurrently or sequentially.

n Looping: Allows you to run a single service in a loop until the loop ends or an exit criteria is

met.



l Synchronization: This feature allows you to define the synchronization services for your

application. Sync supports onlyWeb Services, except SAP Sky.

l Engagement Services: This feature allows you to define and configure pushmessaging

services for your application.

1.1 Purpose

This document helps you install and configure KonyMobileFabric using the installer on Linux.

1.2 Intended Audience

This document is intended for engineers or developers who are responsible for installing and

configuring KonyMobileFabric. We assume that the reader of this document is familiar with installing

applications in a Linux environment.

1.3 Formatting Conventions Used in This Guide

The following formatting conventions are used throughout the document:

Convention Explanation

Monospace l User input text, system prompts, and responses

l File path

l Commands

l Program code

l File names

Italic l Emphasis

l Names of books and documents

l New terminology



Convention Explanation

Bold l Windows

l Menus

l Buttons

l Icons

l Fields

l Tabs

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

1.4 Related Documents

Document Purpose

Kony MobileFabric

User Guide

This guide helps you understand how to create a Kony MobileFabric

account, add services, and publish apps.

1.5 Contact Us

Wewelcome your feedback on our documentation. Email us at [email protected].

For technical questions, suggestions, and comments or to report problems on Kony's product line,

contact [email protected].


mailto:[email protected]?subject=Documentation Feedbackmailto:[email protected]

2. Prerequisites Kony MobileFabric Installation Guide - LinuxVersion1.9

2. Prerequisites

The following sections provide information about the software and hardware required to install Kony

MobileFabric Console.

2.1 Software Requirements

For software system requirements, click here.

2.2 Hardware Requirements

Component Requirement

Processor Quad-core processor

Memory 16GB

Internal Storage 150GB

Network 100Mbps Ethernet interface card

2.3 Corporate Firewall Settings - Engagement Services

For more details, click Corporate Firewall Settings - Engagement Services

2.4 Creating the Installation User for Linux

To create a user, follow these steps:


http://docs.kony.com/7_3/konylibrary/general/mobilefabric_supported_devices_os_browsers/Default.htm#MobileFabric.htmhttp://docs.kony.com/konylibrary/mobilefabric/kony_mobilefabric_manual_install_guide/Default.htm#Prerequisites.htm%23CorporateFirewallSettings_KMS?TocPath=Prerequisites|Hardware%2520Requirements|_____5


1. From your MobileFabric install system, open Linux terminal.

Note: For security and administrative reasons, install and run KonyMobileFabric Installer

as a non-root user.

2. Run the following commands:

# adduser core

# passwd core

2.5 Heap and PermGen Settings

For Oracle Java 7 and Java 8, configure the heap settings for your application servers. In case of

Oracle Java 7, you also need to configure PermGen settings.

l Tomcat heap and PermGen settings

l JBoss heap and PermGen settings

l WebLogic heap and PermGen settings

l WebSphere heap settings

2.6 Configure the Standalone Existing JBoss

To install MobileFabric on a existing standalone JBoss, follow the steps to configure the standalone

JBoss:

1. Open the standalone.xml from the /standalone/configuration.

2. Configure JBoss to listen for remotemanagement requests as below:

l Add under the


binding-group>

l Add following section under the

3. For Engagement Services to work, remove the following subsystem:

|

4. In case of installing all theMobileFabric components, follow these steps to increase heap size by

setting the JAVA_OPTS in the \standalone\bin\standalone.sh/bat:

l standalone.bat:

set "JAVA_OPTS= -server -Xms2048m -Xmx2048m"

l standalone.sh:

JAVA_OPTS="-server -Xms1024M -Xmx1024M"

2.7 Configure Port Settings for Multinode Loadbalancer Setups

Before installingMobileFabric on an application server, for the application server to communicate with

aWeb Server properly, youmust open the port 80.



2.8 How to Disable Weak Ciphers in Tomcat

To disable weak ciphers, modify the SSLConnector container attribute inside the server.xml with

the required https connector tag details. The server.xml is located in the \tomcat\conf folder.

Add the following is a sample details to SSL connector tag:

SSLEnabled="true" sslEnabledProtocols="TLSv1.2" ciphers="TLS_ECDHE_

RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_

ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_

SHA,TLS_ECDHE_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_

SHA256,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256,

TLS_RSA_WITH_AES_256_CBC_SHA,SSL_RSA_WITH_RC4_128_SHA"

For example, the following is a samplemodified https connector tag:

;

Note: Upgrade the SSLCipher list to the latest available versions.



2.9 How to Disable Weak Ciphers in JBoss

To disable weak ciphers, replace the https-listener under JBoss subsystem/undertow, for

example,

For example, the following is a sample for https connector tag:

For example, the following is a samplemodified https connector tag:

2.10 JMS Configuration - WebSphere Multinode

To enableMetrics, run theMetrics/JMSmultinode configuration as a pre-requisite beforeMobileFabric

Installation inWebSpheremultinode.



Note: Choose Configure JMS Server and JMSModule for Integration Cluster (Metrics) - single

Integrationmember on each node as pre-requisite when running single integration server

members on each node.

Note: Choose Configure JMS Server and JMSModule for a Separate Reports Cluster (Metrics)

multiple integration clustersmembers on each node as pre-requisite when runningmultiple

integration server members on each node by separatingmetrics cluster.


http://docs.kony.com/konylibrary/mobilefabric/jms_multinode_configuration#Configure_JMS_Server_-_IntegrationCluster.htmhttp://docs.kony.com/konylibrary/mobilefabric/jms_multinode_configuration#Configure_JMS_Server_-_IntegrationCluster.htmhttp://docs.kony.com/konylibrary/mobilefabric/jms_multinode_configuration#Configure_JMS_Server_-_ReportsCluster.htmhttp://docs.kony.com/konylibrary/mobilefabric/jms_multinode_configuration#Configure_JMS_Server_-_ReportsCluster.htm

3. MobileFabric Topology and Components Kony MobileFabric Installation Guide - LinuxVersion1.9

3. MobileFabric Topology and Components

MobileFabric topology explains the logical arrangement of various components, such as, console,

identity services, developer environment, and production environment.

In design time you configure appswith services, and publish them to a developer environment. After

you confirm the changes in the apps, these appswill need to be published to a production

environment. Authorized users can access apps onmobile devices from a production environment.

An overview of theMobileFabric architecture and components follows:



An overview of theMobileFabric deployment architecture follows:

The following table describes the components of MobileFabric:

Convention Description

Identity This component validates user accounts and applications for authentication

and authorization.

l Authentication identifies log-on credentials of a user.

l Authorization allows or denies access to resources based on a user's

role.

Identity is used to authenticate and authorize runtime and design-time users.




Accounts The accounts component contains information about what a user can do,

such as create other users, delete users, create environments, delete

environments, and publish apps to an environment.

This component uses auth service for authorizing requests based on user

roles.

Workspace

(WaaS)

Workspace configures MBaaS services (applications, identity, integration,

orchestration, synchronization, and engagement services). After these

services are configured, these services must be published to respective

clouds/environments so that the services are available for run-time use.

Console/Portal The console/portal is the user interface for configuring services for an

application.

Environments

(Engagement

Services, Sync

Services,

Integration

Services)

This component adds runtime capabilities to apps, such as engagement

services, synchronization services, and integration services.

Admin Admin provides the capability to list down the set of services published and

test the services shown as well. Also you can view list of published apps and

provides the delete apps functionality. In Kony Cloud, changing the log levels

and checking the logs features are available as the cloud is managed by

Kony. You can also view reports if you are usingmetrics module. This is an

optional component.

For more details, refer to http://docs.kony.com/konylibrary/integration/kony_

mobilefabric_integration_ service_admin_console_user_guide/Default.htm


http://docs.kony.com/konylibrary/integration/kony_mobilefabric_integration_service_admin_console_user_guide/Default.htmhttp://docs.kony.com/konylibrary/integration/kony_mobilefabric_integration_service_admin_console_user_guide/Default.htm



Middleware This component exists between amobile device and an endpoint server. It

receives a request from amobile device, sends it to an endpoint server,

fetches the response from the backend and provides the required information

to the device in the JSON format.

Services Services component is used only whenMobileFabric is integrated. It has

same runtime capabilities as themiddleware.

Note: To use Kony Sever with MobileFabric integrated, you can ignore

themiddleware.war. Similarly when you use only standalone Kony

Server, you can ignore the services.war.

For more details, refer to http://docs.kony.com/konylibrary/integration.html

Note: TheMobileFabric components can be configured on one node or separate nodes - for

example, you can use one of the following choices:

-Install All Components on one node.

- Install KonyMobileFabric Console, Identity Services, Integration Services, Engagement

Services, and Sync Services on separate nodes.

For frequently asked questions and troubleshooting, refer to FAQs and Troubleshooting.

3.1 Developer Environment

For development environment, a developer can preferably install MobileFabric components in a

standalonemode (single node) on a local environment. For more details, refer to Single Node

Installation.


http://docs.kony.com/konylibrary/integration.html


Important: KonyMobileFabric Installer supports Tomcat, JBoss,WebLogic, andWebSphere.

Tomcat on single-node only. For multi-node installation on Tomcat, refer to MobileFabricManual

Install Guide.

KonyMobileFabric Consolidated installer supports JBoss on single node (Standalone Mode) and

multi-node (Domain Mode).

Important: By default KonyMobileFabric Consolidated installer supportsmemcached server only

in case of multinode installation.

By default KonyMobileFabric Consolidated installer is not enabled with memcached server for

single node installation (Tomcat and JBoss.) If you want usememcached server, follow manual

steps provided at How to Install Memcached Server.

3.2 Production Environment

For production environment, domainmode (multinode) installation with HTTPs protocol is preferred.

Multinode installation helps to enable better performance, high availability, and load balancing. For

more details, refer to Multinode Installation.


http://docs.kony.com/konylibrary/mf_manual_install.htmhttp://docs.kony.com/konylibrary/mf_manual_install.htm

4. MobileFabric Installation on Single Node and

Multinode

Kony MobileFabric Installation Guide -

LinuxVersion1.9

4. MobileFabric Installation on Single Node and Multinode

You can install MobileFabric in a domainmode (multinode) or a standalonemode (single node) on a

local environment.

The following table detailsMobileFabric installation supported for a single node andmultinode

installations.

MobileFabric Components can be installed Single Node Multinode

Console

l Workspace

l Accounts

Identity

Integration

l Admin

l Middleware

l Services

l Metrics

Sync

l Sync Console


4. MobileFabric Installation on Single Node and

Multinode

Kony MobileFabric Installation Guide -

LinuxVersion1.9

MobileFabric Components can be installed Single Node Multinode

l Sync Services

Engagement Services


5. Preinstallation Tasks Kony MobileFabric Installation Guide - LinuxVersion1.9

5. Preinstallation Tasks

Before you install MobileFabric Console Installer, youmust perform the following preinstallation tasks:

l Ensure access to a database server.

l A database user should be granted all required permissions as per this document.

l To use your existing SSL certificate, map the SSL certificate to the domain name you want to

use.

l To install in domain (multi-node) mode, the JBoss cluster should be preconfigured.

5.1 Prerequisites for MobileFabric with Oracle

For installing MobileFabric Database for Oracle, complete the following steps:

Note: Only a qualified Oracle Database Administrator (DBA) must handle the Oracle Database

setup in order to successfully complete theMobileFabric database deployment. Oracle software

must be installed and basic databasemust be created before to continue with MobileFabric

database schema setup.

Important: Ensure that a dedicated database user must not be an application user (for example,

konydevicedb) for installation of database. A dedicated user gets logged into audit logs.

After granting privileges, disconnect existing session, and use new session in order to get the new

privileges loaded to the user.

l Unicode support needs to be enabled in Database. This is possible only while creating a database

needed for MobileFabric with a Unicode character set with the properties for Database character set as

AL32UTF8 and National character set as AL16UTF16.



l Create the following three tablespaces. These tablespaces will be used to createMobileFabric

database objects:

o Tables and data tablespace: MF_DATA

o Index tablespace: MF_INDEX

o Lob tablespace: MF_LOB_DATA

l Using an SQLPlus or another Database client, connect to youOracle database as Sysdba.

Replace the with actual data file path on the Oracle database server.

CREATE TABLESPACE MF_DATA DATAFILE '/MF_DATA_01.DBF'

SIZE 2048M AUTOEXTEND ON NEXT 100M MAXSIZE 5120M;

CREATE TABLESPACE MF_INDEX DATAFILE '/MF_INDEX_01.DBF'

SIZE 2048M AUTOEXTEND ON NEXT 100M MAXSIZE 5120M;

CREATE TABLESPACE MF_LOB_DATA DATAFILE '/MF_LOB_DATA_

01.DBF' SIZE 2048M AUTOEXTEND ON NEXT 100M MAXSIZE 5120M;

l Create a dedicated database user with default tablespaces (MF_DATA) and grant quota to two other

tablespaces (MF_INDEX andMF_LOB_DATA tablespaces).

o To create a user based on your Oracle 11g or 12c without PDB, which will be used in the JDBC.

CREATE USER IDENTIFIED BY DEFAULT

TABLESPACE MF_DATA TEMPORARY TABLESPACE TEM PROFILE DEFAULT;

GRANT TO with admin option;

ALTER USER QUOTA UNLIMITED ON MF_DATA;

ALTER USER QUOTA UNLIMITED ON MF_INDEX;

ALTER USER QUOTA UNLIMITED ON MF_LOB_DATA;

--------------

CREATE JOB, CREATE PROCEDURE, CREATE SEQUENCE, CREATE SESSION,

CREATE TABLE, CREATE TABLESPACE, CREATE TRIGGER, CREATE TYPE,

CREATE USER, CREATE VIEW, ALTER SESSION, ALTER TABLESPACE, ALTER

USER, CREATE ANY INDEX, ALTER ANY TABLE, CREATE ANY TABLE



o To create a dedicated database user based on your Oracle 12c with PDB, then create a

dedicated database local user inside PDB, which will be used in the Java

Database Connectivity (JDBC) authentication.

Alter session set container = PDB ;

CREATE USER IDENTIFIED BY

DEFAULT TABLESPACE MF_DATA TEMPORARY TABLESPACE TEMP

PROFILE DEFAULT CONTAINER=CURRENT;

GRANT TO with admin option

CONTAINER=CURRENT;

ALTER USER QUOTA UNLIMITED ON MF_DATA

CONTAINER=CURRENT;

ALTER USER QUOTA UNLIMITED ON MF_INDEX

CONTAINER=CURRENT;

ALTER USER QUOTA UNLIMITED ON MF_LOB_DATA

CONTAINER=CURRENT;

--------------

CREATE JOB, CREATE PROCEDURE, CREATE SEQUENCE, CREATE SESSION,

CREATE TABLE, CREATE TABLESPACE, CREATE TRIGGER, CREATE TYPE,

CREATE USER, CREATE VIEW, ALTER SESSION, ALTER TABLESPACE, ALTER

USER, CREATE ANY INDEX, ALTER ANY TABLE, CREATE ANY TABLE

l If you are usingMobileFabric installer to setupMobileFabric database, then please choose the below

options based on your Oracle database version.

o If Oracle database is created with PDB option of Oracle 12c, use service name pointing to PDB in

the JDBC URL such as pdborclorpdbmfdb

jdbc:oracle:thin:@:1521/pdbmfdb

For example: jdbc:oracle:thin:@192.168.1.2:1521/pdbmfdb

o But if your database is 11g or 12c without PDB, then you can useORACLE_SID in the JDBC

URLsuch asorcl or mfdb.



jdbc:oracle:thin:@:1521:mfdb

For example: jdbc:oracle:thin:@192.168.1.2:1521:mfdb

5.2 Prerequisites for MobileFabric with DB2

Important: Download the following DB2 JARs from IBM download site:

- IBMDB2 Type 4 Driver (db2jcc4.jar)

- DB2 JDBC Driver licence (db2jcc_license_cu.jar)

The version of the downloaded JARs should be compatible with your installed DB2Database

version.

For IBMDB2, while creating database, choose 32k page size as default tablespace. Because after a

database with page size as default tablespace is created, you will not be able tomodify the page size

of the default tablespace. Additionally you need to create three tablespaces: one for tables and data,

one for index, and the other tablespace for Large objects (LOBs). For creating tablespace, the details

are provided int he below sections.

Create the Big tablespace with big bufferpool of 32K page size.Only DB2 database administrator (DBA) or

equivalent DB user will have access to create database with default tablespace with particular

pagesize/bufferpool. In DB2, whenever Binary LargeObject (BLOB) and Character LargeObject (CLOB) are

used, you need to have the database created with default tablespace as well as default temp tablespace with

big pagesize of 32k.

-- Replace with your actual database name.

CONNECT TO ;

CREATE BUFFERPOOL BIGBUFFERPOOL IMMEDIATE ALL DBPARTITIONNUMS

SIZE AUTOMATIC NUMBLOCKPAGES 100 BLOCKSIZE 100 PAGESIZE 32K;

COMMIT;

-- To create a tablespace for tables and Data



CREATE LARGE TABLESPACE IN DATABASE PARTITION GROUP

IBMDEFAULTGROUP

PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 32 PREFETCHSIZE

AUTOMATIC

BUFFERPOOL BIGBUFFERPOOL OVERHEAD 7.5 TRANSFERRATE 0.06 AUTORESIZE YES

INITIALSIZE 32M NO FILE SYSTEM CACHING;

COMMIT;

-- To create an index tablespace


IBMDEFAULTGROUP


AUTOMATIC



COMMIT;

-- To create a LOB tablespace


IBMDEFAULTGROUP


AUTOMATIC



COMMIT;

CREATE SYSTEM TEMPORARY TABLESPACE "BIGTEMP" IN DATABASE PARTITION GROUP

IBMTEMPGROUP

PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE USING STOGROUP IBMSTOGROUP

EXTENTSIZE 1M

PREFETCHSIZE AUTOMATIC BUFFERPOOL BIGBUFFERPOOL;



COMMIT;

CONNECT RESET;

5.3 Prerequisites for MobileFabric with SQL Server

l Database User security role: Create a database login dbclient using SQL server

authenticationwith server roles as sysadmin and public

l Database and schema access: Installer will make use of the above login to create necessary

databases and schemas required for the selectedMobileFabric components.

l Database Growth sizing: Refer to MobileFabric Deployment Guide > DatabaseGrowth Sizing

l Database Transaction log size: Allocate sufficient space for the Transaction log file based on

all the transactions activity of all theMobileFabric components installed and as per your

database backup policy. Because transaction log sizing is linked to database backup. If

additional application logging/events are enabled inmultiple components of MobileFabric, then

youmay need to consider additional size for the transaction log.

l Temp Database and temp log: This is based on usage of all the databases on the server

instance, by all applications connecting to these databases. In case of MobileFabric, for sizing of

the temp database, consider auto growth with increment size should be of 100MB andwith

maximum size to 10GB. But if application logging/events are enabled inmultiple components of

MobileFabric, then themaximum size should be increased upto 20GB. This size will get

reclaimed as and when the DB is restarted.

l Database versions: You can use SQLServer Standard Edition or SQLServer Enterprise

Edition database for installingMobileFabric. MobileFabric is compatible with these editions.

There are no prerequisites specific to these editions asMobileFabric uses features common to

both editions.

l Backup plan: Youmust use your organization's defined backup and retention policies for

Backup strategies for your database.


http://docs.kony.com/konylibrary/konyfabric/kony_Fabric_deployment_guide/Default.htm#Deployment.htm%23DBSizing?TocPath=_____8


5.4 Download MobileFabric Installer

l DownloadKonyMobileFabricSetup.tar.gz file from

http://community.kony.com/downloads and extract the file. To download KonyMobileFabric

installer from the community portal, follow these steps:

1. Log in to http://community.kony.com/downloads. You can obtain a user name and

password from your sales representative or partner.

2. Click the Kony MobileFabric tab.

3. Select the specific release version from the Kony MobileFabric Installer (Consolidated

Installer for all features) drop-down list and then click on the specific release related files

you want to download. For example, if you want to download Kony MobileFabric

7.3.0 GA installer, select the 7.3.0 GA version from the drop-down list, and

then click the Installer_Linux link. The following is a sample screen.


http://community.kony.com/downloadshttp://community.kony.com/downloads


TheKonyMobileFabricSetup.tar.gz file contains the following files:

n KonyMobileFabricInstaller-7.3.0.0_GA.bin

n installer.properties - This file is required for silent installation.

n README.txt

5.5 Steps before installing (or) upgrading MobileFabric with the exist-

ing database

Perform the following activities before installing (or) upgradingMobileFabric with the existing

database:



l Take database backup

l Make sure you havepreviouslyinstalled directory

l Takea backupof applications deployed at theserverlevel. (Post installation, take backup of the

changes done to the binaries).

l Post installation (or)upgradeprocess, replaceoldauthService.keyandworkspaceService.key

(applicable only for identity and workspace components).

5.6 Create /tmp Folder

MobileFabric Installer required a /tmp folder in Linux environment to unpack installer. When the /tmp

folder is not found, the Installer shows I/O exception at the time of unpack exception, shown below:

This must specify in the pre-req of installation. Installation

must required temp folder to unpack MF installer (either

default / custom temp folder).

5.7 Install Memcached Server

Memcached is a high-performance, distributedmemory object caching system, generic in nature, but

intended for use in speeding up dynamic web applications by alleviating database load.

5.7.1 libevent (memcached dependency)

Thelibevent API provides amechanism to execute a callback function when a specific event

occurs on a file descriptor or after a timeout has been reached. Furthermore, libevent also support

callbacks due to signals or regular timeouts.

libevent is meant to replace the event loop found in event driven network servers. An application

just needs to call event_dispatch() and then add or remove events dynamically without having to

change the event loop. Refer to http://libevent.org/

To install libevent (memcached dependency), follow these steps:


http://libevent.org/


1. First, checkwhether libevent is installed on your computer. To check, type the below

command in your Linux terminal:

whereis libevent

2. If you do not findlibevent on your system, download and install it. Downloadlibevent-

1.4.8-stable.tar.gz. Refer to http://libevent.org/

3. Extract the libevent-1.4.8-stable.

4. In your Linux terminal, type the below command:

cd libevent-1.4.8-stable

./configure

make

make install

5. Type the below command to create a symlink to libevent

ln -s /usr/local/lib/libevent-1.4.so.2 /usr/lib

Now that you have installed the dependencies, install thememcahced server.

5.7.2 Memcached Server

To install Memcached Server, follow these steps:

1. Download thememcached server.

2. Extract the zip file.

3. Open the Linux terminal.


http://libevent.org/


4. Go to../memcache directory.

5. Run the following command:

tar xfz memcached-1.2.6.tar.gz

cd memcached-1.2.6

./configure

make

make install

memcached -d -m 1024 -u root -l 127.0.0.1 -p 11211

Important: RunMemcached as a daemon (d = daemon, m = memory, u = user, l = IP to

listen to, p = port)

5.8 Increase JVM memory for WebLogic Server

For asuccessful deployment of MobileFabricWar files onWebLogic server, increase the PermGen

memory inWebLogicmemory arguments. For more details, refer to Heap and PermGen Settings

5.9 Place MS SQL Server Connector JAR in WebLogic Classpath

If you want to install MS SQLServer Database withWebLogic, then you need tomanually place the

sqljdbc4.jar file in theWebLogic classpath.

Important: To add thesqljdbc4.jar file in theWebLogic classpath, perform the following

steps before startingMobileFabric installation.

To add sqljdbc4.jar file in the WebLogic classpath, follow these steps:



1. Place thesqljdbc4.jar in the /server/lib folder.

2. Edit the commEnv.cmd/sh script in the /oracle_common/common/bin.

3. Prepend your JAR file to theWEBLOGIC_CLASSPATH environment variable like set

WEBLOGIC_CLASSPATH=%WL_HOME%\server\lib\sqljdbc4.jar;%JAVA_

HOME%\lib\tools.jar;%PROFILE_CLASSPATH%;%ANT_

CONTRIB%\lib\ant-contrib.jar;%CAM_NODEMANAGER_JAR_PATH%

4. Restart the server.

5.10 Configure JMS for Metrics in Domain Mode for WebLogic or

JBoss

In App Services console, Healthcheck for access to reporting queue fails for WebLogic and JBoss

cluster.

l For WebLogic: To pass the healthcheck for access to reporting queue, while

installingWebLogic cluster, youmust select both admin server and cluster options.

l For JBoss: To pass the healthcheck for access to reporting queue, youmust

create an application user and add the user to JMS role.

While creating an application user in JBoss domainmode, youmust use the following default

credentials for the new user.

l Username = admin

l Password = admin

In case you have used values other than the default values to create an user, follow

these steps:



1. Open themobilefabric_configuration table in theadmindb.

2. Modify the default values for metrics.securityPrincipalName and

metrics.userName properties with the new username.

metrics.securityPrincipalName =

metrics.userName =

3. Encrypt the password and thenmodify the default values for

securityCredentials and metrics.password properties with encrypted

value of the new password.

securityCredentials =

metrics.password =

To encrypt a value, follow these steps:

1. Create a Java class.

2. Addkonyserver-utils.jar to your class path.

Path for konyserver-utils.jar: /KonyMobileFabric_

Plugins/middleware/konyserver-utils.jar

3. Call themethodEncryptDecryptText.encryptText

(). This will return encrypted value.

Creating an application user in JBoss



Go to /bin folder and run theadd-users.sh/.bat file,

shown below:

After the installation, the system shows all pass including Access to Reporting Queue

mainly.



You have successfully configured themetrics.

5.11 Configure Load Balancers for Sending Host Information in

Multinode

When user is installingMobileFabric onmultinode environment, the user should checkwhether the

parameter: proxypreserveHost is set to On in the Loadbalancer configuration file to send host

in the headers.

If the proxypreserveHost is not configured, the loadbalancer will not send host in the headers. Users

cannot launchMobileFabric Console.

The above configuration is based on the loadbalancer.

For example:

l For Apache: preserveHost On

l For HAProxy: preserve host flag is not required.



5.12 Configure Hibernate Dialect in WebLogic (only for WebLogic)

For the Engagement Services to work with Oracle DB, set the following parameter in the

setDomainEnv.sh and run thesetDomainEnv.sh before starting theWebLogic server.

-Dhibernate.dialect=org.hibernate.dialect.Oracle10gDialect

5.13 Update Listen Interfaces in host.xml for JBoss Cluster

For JBoss domainmode installation, configure the following interface address.

1. Go to/domain/configuration/host.xml

2. In place of existinginterfaces xml tag, replace the default content with below details:



5.14 Comment the javax-persistence-module for Kony Engagement

Services on JBoss Cluster

If you are installing Kony Engagement Services on JBoss domainmode installation, comment the

below persistencemodule in thedomain.xml file.

1. Go to/domain/configuration/domain.xml

2. Comment the below xml tag. Comment the persistencemodule at four places in the

domain.xml file.



5.15 Increase innodb_log_file_size in my.cnf file - MySQL

Note: If the size of your application ismore than the variable size of server database, an error

occurs. Ensure the variablemax_allowed_packet_size is set to a higher value than the

application size.

To avoid this error, increase the global variable in the server database.

- Modify the SQLStatement toSet global max_allowed_

packet=10*1024*1024.

In this statement the server database size is configured to 10-Megabytes(MB).

For example, if your application size is 1024-kilobytes (1MB) and you try to publish an application

fromKony Studio of 2048-Kilobytes(2MB) an error appears while publishing. Increase thesize of

server database to a valuemore than 2048-Kilobytes (2MB) for publishing the application.

For innodb_log_file_size, the value is set to 48M by default.

In the my.cnf file, increase the innodb_log_file_size =

5.16 Tuning File Descriptor Limits on Linux

To run the enterprise applications successfully on Linux distribution, youmay have to update some of

the default kernel parameter settings.

In Linux, there is a limit to the number of file descriptors that a process can open. The default is set to

1024 per process. You can increase this limit for optimum performance.

To increase the file descriptor limit, follow these steps:



Note: Based on the user you create for your app server and database, increase the file descriptor

limit for the user accordingly.

For example: In this procedure, the created user isWebLogic for running theWebLogic server.

You can follow these steps to increase the file descriptor limit based on your application server and

database such as Tomcat, JBoss,WebLogic, or WebSphere.

1. Log on to Linux system and change toWebLogic user.

2. Enter the following command:

[weblogic@localhost ~]$ ulimit -n

If the result is displayed as 32768, skip the following steps. The limit is set for optimum

performance. Else, perform the steps to increase the limit.

3. Increase the file descriptors limits.

You can limit WebLogic user to specific limits by editing /etc/security/limits.conf file.

a. Enter the following command to edit the file:

vi /etc/security/limits.conf

b. SetWebLogic user soft and hard limits by adding the following lines:

weblogic soft nofile 32768

weblogic hard nofile 32768

c. Save and close the file. Log out and log back in again.

d. Verify the changes by entering the following command:



[weblogic@localhost ~]$ ulimit -n

It should display 32768.

4. Restart your App server

5.17 Create Locator Component for Oracle Database

By default when anOracle database is created using DBCA or Oracle Installer Enterprise Edition with

create database option, the SDO_Geometry object type will be default created as part of locator

component.

If the database is created using scripts by followingmanual process, then the Locator component will

not be created. You need to create the locator component for your Oracle database separately.

Verify if the locator component is already installed

Run the below queries in the Oracle database used for Installer:

Select comp_name, version, status from dba_registry where upper

(comp_name) like '%MEDIA';

Select username from dba_users where username = 'MDSYS'

If the above statements return zero records andMDSYS schema is not created, then follow these

steps to create theMDSYS schema and install the locator component manually.

The following steps need to be executed by a SYSDBA only.

To create Locator or MDSYS schema, follow these steps in option #1 or option #2:

l Option #1. Follow DBCA or Oracle Installer enterprise edition with create database option to

create Oracle database. Use the same database duringMobileFabric Installation.



l Option #2. Run the following scripts on the database to be used for MobileFabric, where Oracle

locator is not installed.

i. Connect as SYSDBA

sqlplus "/as sysdba"

ii. CreateMDSYS User if not exists:

Create user mdsys identified by secret default tablespace

sysaux

A secret is a dummy password. Provide the password that is used duringMDSYS user

creation.

iii. Run the below SQL to grant the privileges:

SQL>@?/md/admin/mdprivs.sql

iv. Connect to MDSYS user:

Conn mdsys/secret

A secret is dummy password. Provide the password that is used duringMDSYS user

creation.

v. Run the below SQL to create the locator objects:

SQL>@?/md/admin/catmdloc.sql

All the above.sql files executed will be available as part of database software md folder.

Once theOracle locator is installed, run the Installer to setupMobileFabric. The system should

not throw the error: Invalid Data Type SDO_GEOMENTRY



Note: As per Oracle 12cRelease 1 (12.1) documentation, Oracle Locator is available with

the following editions:

l Oracle Database Standard Edition One

l Oracle Database Standard Edition

l Oracle Database Enterprise Edition

l Oracle Database Express Edition (Oracle Database XE)

For more information regarding Oracle licensing, refer to Oracle Database documentation.

Important: SDO_GEOMETRY is part of Oracle Locator, which is free and does not need

additional licensing, but this is bundled with Oracle Spatial, which is part of enterprise

edition licensing.

For more details, please go through the followingOracle reference document:

Doc ID 1066837.1 :- Oracle Spatial andOracle Locator Licensing Information.

5.18 Configure Load Balancer as Proxy in JBoss Multinode Setup

(Optional if SSL Offloading at Load Balancer)

1. Navigate to your MobileFabric install directory and open thedomain.xml file.

2. In thedomain.xml, update all the http connector tags to include the scheme and

proxy-port details.

For example,



5.19 Configure Property Settings for Logs - (only for WebSphere)

Tomake theLOG_ROOT variable accessible to applications, set the variable under custom properties

of process definition.

1. Log in toWebSphere Admin Console.

2. Go to Servers > Server Types > WebSphere application servers.

3. Click Application Server. (For example, server1, it is the default server created with

WebSphere installation).

4. Go to Server Infrastructure section, expand Java and Process Management and click

Custom Properties.

5. Go to Custom Properties, click Java Virtual Machine.

6. Click New to add LOG_ROOT property.

7. Enter LOG_ROOT as name.



8. Enter ${LOG_ROOT} as value.

9. Save the configuration.

After setting theLOG_ROOT variable under custom properties, logs are created under \IBM_

WebSphere\WebSphere\AppServer\profiles\AppSrv02\logs\konymflogs

5.20 Install MobileFabric on a Remote WebSphere Server with Global

Security Enabled

To get server groups of a remoteWebSphere Server using a SOAP port, follow these steps before

running theMobileFabric Installer.

1. Install IBMWebSphere SDK on a systemwhere you want to run theMobileFabric Installer.

2. Add the SSL certificate to DMGR. For more details, click How to Add an Existing Secure

Sockets Layer (SSL) Certificate.

3. Launch a Terminal window.

4. Go to the location of theMobileFabric Installer.



5. Run theMobileFabric Installer as follows:

KonyMobileFabricInstaller-7.x.bin LAX_VM

5.21 Download and Install the Unrestricted JCE Policy Files

In accordance with the United States of America export restrictions, Java that is bundled with the

server has limited encryption key sizes that can be used in the server operation. In order to

successfully convert signed client certificates or sign server Certificate Signing Request for use in the

server, youmust download the following bundled encryption policy files and replace themwith the

unrestricted files published by the Java vendor.

l local_policy.jar

l US_export_policy.jar

To Configure Unrestricted JCE Policy Files for WebSphere, follow these steps:

For WebSphere, follow the steps provided in the link:

https://www.ibm.com/support/knowledgecenter/SS8JFY_

7.5.0/com.ibm.lmt75.doc/com.ibm.license.mgmt.security.doc/lmt_scr_downloading_installing_jce_

policyfiles.html

To Configure Unrestricted JCE Policy Files for Tomcat, JBoss, or WebLogic, follow these steps:

1. Go to the Oracle Java SE download

pagehttp://www.oracle.com/technetwork/java/javase/downloads/index.html

2. Scroll down to Additional Resources section. You will find Java Cryptography Extension

(JCE) Unlimited Strength Jurisdiction Policy File.

3. Download the JCE version that matches your installed JVM, for example,

UnlimitedJCEPolicyJDK.zip.


https://www.ibm.com/support/knowledgecenter/SS8JFY_7.5.0/com.ibm.lmt75.doc/com.ibm.license.mgmt.security.doc/lmt_scr_downloading_installing_jce_policyfiles.htmlhttps://www.ibm.com/support/knowledgecenter/SS8JFY_7.5.0/com.ibm.lmt75.doc/com.ibm.license.mgmt.security.doc/lmt_scr_downloading_installing_jce_policyfiles.htmlhttps://www.ibm.com/support/knowledgecenter/SS8JFY_7.5.0/com.ibm.lmt75.doc/com.ibm.license.mgmt.security.doc/lmt_scr_downloading_installing_jce_policyfiles.htmlhttp://www.oracle.com/technetwork/java/javase/downloads/index.html


4. Extract the downloaded zip file. TheUnlimitedJCEPolicyJDK.zip file

contains the following files:

l local_policy.jar

l US_export_policy.jar

l README.txt

5. Copy the .jar files (local_policy.jar and US_export_policy.jar) to/lib/security/

Note: These jars will be already there so you have to overwrite them. Back up the existing

jars before you overwrite themwith new jars.

6. Restart your application server.

After the encryption policy files are installed, you should be able to successfully convert signed

client certificates for use in the server.

5.22 How to Configure Connector - JBoss

For importing an app toMobileFabric Console properly, youmust have set the enough value for the

max-post-size in thestandalone.xml file. For more details, refer to Configure Connectors -

JBoss.


http://docs.kony.com/konylibrary/mobilefabric/kony_mobilefabric_manual_install_guide/Default.htm#Configuring_Connectors_and_WAR_JBoss.htm?TocPath=Prerequisites|Configuring%2520Installation%2520Mode%2520(App%2520Servers)|How%2520to%2520Install%2520JBoss|_____2http://docs.kony.com/konylibrary/mobilefabric/kony_mobilefabric_manual_install_guide/Default.htm#Configuring_Connectors_and_WAR_JBoss.htm?TocPath=Prerequisites|Configuring%2520Installation%2520Mode%2520(App%2520Servers)|How%2520to%2520Install%2520JBoss|_____2

6. Installation Modes - Kony MobileFabric Kony MobileFabric Installation Guide - LinuxVersion1.9

6. Installation Modes - Kony MobileFabric

You can install MobileFabric by any of the followingmodes:

Important: Ensure that you have the required hardware and access to the supporting software as

mentioned in the Prerequisites section and performed the steps asmentioned in the Pre-

installation Tasks section.

l InstallingMobileFabric - Console-mode (for command-line-driven installations)

l StandaloneMode (Single Node) Installation

l StandaloneMode (Single Node) Installation on a pre-configured JBoss

l JBossMultinode Installation

l InstallingMobileFabric - Silent-mode (for working with limited or no user interaction)



6.1 Installing Kony MobileFabric - Console-mode

Note: If a user installs KonyMobileFabric Console on a partition different from the user's home

directory, the user must have read/write execute permissions.

This section of the document provides you with the instructions for installing and configuring Kony

MobileFabric Console.

Important: Ensure that you have the required hardware and access to the supporting software as

mentioned in the Prerequisites section and performed the steps asmentioned in the Pre-

installation Tasks section.

Make sure you have proper administrative rights to install KonyMobileFabric on your computer.

You also need a user where KonyMobileFabric will be installed.

The directory contains the log files logging each invocation of the installer. Tomake

problem identification easier, provide these log files to Konywhen reporting an issue.

6.1.1 Standalone Mode (Single Node) Installation

To install Kony MobileFabric Console using the installer, follow these steps:

1. Execute the following command to switch to the user that you created.

# su - username

2. Press Enter. The system prompt you to enter the password.

3. Enter the password, and press Enter.

4. Unzip theKonyMobileFabricSetup.tar.gz file, and navigate to the folder

KonyMobileFabric_Installer_Linux.



5. Start the ./KonyMobileFabricInstaller-7.3.0.0_GA.bin file by executing the following

command:

Preparing to install...

Extracting the JRE from the installer archive...

Unpacking the JRE...

Extracting the installation resources from the installer

archive...

Configuring the installer for this system's environment...

Launching installer...

==================================================================

=============

Kony MobileFabric (created with InstallAnywhere)

------------------------------------------------------------------

-------------

Preparing CONSOLE Mode Installation...

==================================================================

=============

Introduction

------------

Kony MobileFabric is a set of enterprise-grade mobile

infrastructure services that makes it easy to build amazing apps

that integrate and support all of your backend systems. With open,

standards-based development, scalable and secure services, and

exceptional agility, enterprises can dramatically reduce the cost

and complexity of enterprise mobility projects.

To proceed with installation, please confirm that the following

prerequisites have been met -

1. Database server for installation. MySQL, MariaDB, Oracle, MS

SQL Server and DB2 are the

supported databases. MariaDB is supported for Tomcat/JBoss



only.

2. Corresponding database user should exist and that user should

have all required

privileges as per the documentation.

3. If you want to use your existing SSL certificate then please

have the SSL certificate

mapped to the domain name you want to use.

4. If you want to install with JBoss/ WebLogic/ WebSphere as an

option for application

server, then have the application server preconfigured. Please

note that single node

JBoss is also bundled as part of the installer, in case you

want to install afresh.

To change input, type 'back' to go back to the previous step.

To cancel the installation, type 'quit' at any time.

For troubleshooting & help on the installation, use

http://docs.kony.com/konylibrary/mobilefabric/resources/installer.

htm

For getting started on Kony MobileFabric, refer

http://community.kony.com/documentation

For upgrading Kony MobileFabric, refer online documentation.

If you have more questions or feedback, you can join our

http://community.kony.com/ or, raise a http://support.kony.com/.

->1- Continue with Installation.

2- Abort Installation.

ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS TO ACCEPT

THE DEFAULT:


http://docs.kony.com/konylibrary/mobilefabric/resources/installer.htmhttp://docs.kony.com/konylibrary/mobilefabric/resources/installer.htmhttp://community.kony.com/documentationhttp://docs.kony.com/konylibrary/mobilefabric/kony_mobilefabric_linux_install_guide/Default.htm#Upgrading_Kony_MobileFabric_on_Linux.htm?TocPath=_____8http://community.kony.com/http://support.kony.com/


6. Press Enter. The Software License Agreement details appear.

==================================================================

======

License Agreement

-----------------

Installation and Use of Kony MobileFabric Console Requires

Acceptance of the Following License Agreement:

KONY, INC.

SOFTWARE LICENSE AGREEMENT

THE TERMS AND CONDITIONS CONTAINED HEREIN CONSTITUTE A LEGAL

AGREEMENT.

THIS AGREEMENT ("AGREEMENT") CONTAINS THE ENTIRE AGREEMENT BETWEEN

YOU ("LICENSEE") AND KONY, INC. ("KONY") WITH RESPECT TO THE TERMS

AND CONDITIONS DESCRIBED HEREIN. READ THIS AGREEMENT CAREFULLY

BEFORE YOU CLICK THE "I ACCEPT" BUTTON BELOW. BY CLICKING ON THE

"I ACCEPT" BUTTON, YOU ACKNOWLEDGE THAT (1) YOU ARE AUTHORIZED TO

ENTER THIS AGREEMENT FOR AND ON BEHALF OF YOUR COMPANY, AND ARE

DOING SO, AND (2) YOU HAVE READ AND UNDERSTAND AND AGREE THAT YOU

AND THE COMPANY SHALL BE BOUND BY THESE TERMS AND CONDITIONS AND

ALL MODIFICATIONS AND ADDITIONS PROVIDED FOR. IF YOU DO NOT AGREE

WITH THESE TERMS AND CONDITIONS, CLICK ON THE "I DO NOT ACCEPT"

BUTTON BELOW AND INSTALLATION WILL TERMINATE.

DO YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT? (Y/N): Y

7. Press Y to accept the agreement. The Installation Type details appear.

==================================================================

=============

Installation Type

-----------------



Please select whether to perform a new installation or upgrade an

existing installation.

->1- New Installation

2- Upgrade an existing installation

ENTER THE NUMBER FOR YOUR CHOICE, OR PRESS TO ACCEPT THE

DEFAULT::

8. Press Enter to continue with new installation.

The following installation types are supported for new installation:

l Production for the production instance.

l Non-Production for larger environments like QA or UAT.

l Development for singlemachine instance.

==================================================================

=============

Licensing Type

--------------

Installation environment is set to Development by default . Please

select the appropriate type based on your license.

Select Development for single machine instance, Non-Production for

larger environments like QA or UAT and Production for the

production instance.

1- Production

2- Non-Production



->3- Development


DEFAULT::

9. Enter your choice and press Enter. The Install Components details appear.

==================================================================

=====

Install Components

------------------

Please select Kony MobileFabric components to install.

The Console is the administrative interface to manage your apps,

environments and users.

The Identity Service helps you to use a single gateway for all

your authentication and authorization requests.

The Integration Service helps you connect with any enterprise or

third-party system to mobilize and orchestrate your data.

Enterprise-grade mobile messaging solution with a marketer-

oriented approach to campaign management.

Synchronization platform for mobile application. With it's offline

support, you can do more by collaborating data between devices and

server.

In a development scenario, all components can be installed on the

same box. However, it is recommended to install these components

on separate boxes for production environment.

->1- Console

->2- Identity Services

->3- Integration Services

->4- Engagement Services



->5- Sync Services

ENTER A COMMA-SEPARATED LIST OF NUMBERS REPRESENTING THE DESIRED

CHOICES, OR PRESS TO ACCEPT THE DEFAULT::

l Console - To install KonyMobileFabric Console, type 1 and press Enter.

The system creates the following databases: mfconsoledb,

mfaccountsdb, andmfreportsdb.

o Click here for Accounts schema diagram

o Click here for Workspace schema diagram

o Click here for ReportsDB (Metrics) schema diagram

l Identity Services - To install Kony Identity Services, type 2 and press Enter.

The system creates the following databases: idglobaldb and

idconfigdb.

o Click here for Identity schema diagram

l Integration Services - To install KonyMobileFabric Integration, type 3 and press Enter.

The system creates the following databases: konyadmindb andmfreportsdb.

o Click here for Admin DB schema diagram

o Click here for ReportsDB (Metrics) schema diagram

l Engagement Services - To install KonyMobileFabric Engagement Services, type 4 and

press Enter.

The system creates the following database: kpnsdb.

o Click here for Engagement Server schema diagram

l Sync Services - To install KonyMobileFabric Sync, type 5 and press Enter.

The system creates the following database: syncconsole.

o Click here for Sync Server schema diagram

Reports Database


http://docs.kony.com/7_x_PDFs/MFSchema_Diagrams/accounts.pnghttp://docs.kony.com/7_x_PDFs/MFSchema_Diagrams/workspace.pnghttp://docs.kony.com/7_x_PDFs/MFSchema_Diagrams/metrics.pnghttp://docs.kony.com/7_x_PDFs/MFSchema_Diagrams/identity.pnghttp://docs.kony.com/7_x_PDFs/MFSchema_Diagrams/admin_server.pnghttp://docs.kony.com/7_x_PDFs/MFSchema_Diagrams/metrics.pnghttp://docs.kony.com/7_x_PDFs/MFSchema_Diagrams/engagement.pnghttp://docs.kony.com/7_x_PDFs/MFSchema_Diagrams/sync_server.png


The reports database is used for configuring reports.

The Installer creates themfreportsdb if you choose either Console or Integration Services:

l Console without Integration Services (with or without Engagement Services and Sync

Services)

l Console and Integration Services (with or without Engagement Services and Sync

Services)

l Integration Services without Console (with or without Engagement Services and Sync

Services)

Reports Database for Integration on a Separate Node:

While installing console and integration on separate nodes, the installer prompts you to point the

reports database during the integration installation.

For example:

You have installed only Console on one node. The installer creates these three databases such

asmfreportsdb along with themfconsoledb and

mfaccountsdb. For example, your report database name is konymfreportsdb1

When you install the integration with or without one or more components (identity, Engagement

Services or Sync Services) on a separate node, the installer displays the Reports Database

Name field in the Database Details window. If the installer prompts you to enter the existing

reports db, enter the reports database name (for example, konymfreportsdb1) in the

Database Details window > Reports Database Name field. Refer to the Database Details

option.

Refer to creating a reports database, for example, mfreports.



10. Press Enter to continue the installation. The Install Folder details appear.

==================================================================

=====

Install Folder

---------------------

Please choose a destination folder for this installation.

NOTE: The installation path should not contain any special

characters.

Default Install Folder: /home/user1/KonyMobileFabric

ENTER AN ABSOLUTE PATH, OR PRESS TO ACCEPT THE DEFAULT

:

Note: By default, KonyMobileFabric is installed at the home directory of the user.

11. Press Enter to continue the installation. The installer prompts for the Application Server details

as follows:

Important: MobileFabric Installer supports Tomcat , JBoss,WebLogic, andWebSphere.

MobileFabric Installer supports Tomcat on single node only. For multinode installation on

Tomcat, refer to MobileFabricManual Install Guide.

MobileFabric Installer supports JBoss on single node (Standalone Mode) andmultinode

(Domain Mode).

==================================================================

=============

Application Server

------------------


http://docs.kony.com/konylibrary/mobilefabric/kony_mobilefabric_manual_install_guide/Default.htm


Enter requested information

->1- Tomcat 7.0.75

2- JBoss 7.0

3- WebLogic 12.1.3

4- WebSphere 8.5.5.5


DEFAULT::

12. In the Application Server, type the appropriate option and press Enter.

l If you choose 1- Tomcat, the HTTP or HTTPS details appear.

l If you choose 2- JBoss, the InstallationMode details appear.

l If you choose 3- WebLogic 12.1.3, the Application Server Details details for WebLogic

appear.

l If you choose 4- WebSphere 8.5.5.5, the Application Server Details details for

WebSphere appear.

13. Press Enter to continue the installation. The InstallationMode details appear.

==================================================================

=============

Installation Mode

-----------------

Please select your required installation mode. Standalone mode is

for single node deployment whereas domain mode is for multi node

deployment in JBoss cluster. Please note that if you want to

install in domain mode then JBoss cluster should be preconfigured.

Note: If you are running JBoss in Domain node for a production

setup, please procure appropriate licenses from Red Hat, Inc.



->1- Standalone Mode (Single Node)

2- Standalone Mode (Existing)

3- Domain Mode (Multi Node)


DEFAULT::

l Standalone Mode (Single Node): To install MobileFabric on single node on JBoss that is

bundled with theMobileFabric installer, chooseStandalone Mode (Single Node).

l Standalone Mode (Existing): To install MobileFabric on single node on JBoss that is

installed on your machine, choose Standalone Mode (Existing). For more details on how

to install MobileFabric on the existing JBoss, refer to InstallingMobileFabric on a pre-

configured standalone JBoss - (Single Node).

l Domain Mode (Multinode): To install MobileFabric on JBossmultinode, choose Domain

Mode. Before installing domainmode, ensure that the JBoss cluster is configured on your

install system. For more details on how to install MobileFabric on Domainmode, refer to

JBossMultinode Installation Procedure.

Important: Before installingMobileFabric on domainmode, ensure that the JBoss

cluster is configured on your install system.

14. In the InstallationMode if you type 1 and press Enter, the HTTP or HTTPS details appear.

==================================================================

======

HTTP or HTTPS

-------------

Please select the communication protocol you want to use.

->1- HTTP



2- HTTPS


DEFAULT::

a. In HTTP or HTTPS if you select 1 and press Enter, the following details in the Details for

Application Server details appear.

For Tomcat

=============================================================

==================

Details for Application Server

------------------------------

Please enter the Hostname/IP Address and port you want to

use. The default value is the IP Address of this machine.

Hostname/IP Address (Default: ):

HTTP Port (Default: 8080): 8181

Java Messaging Service (JMS) Port (used for licensing and

reporting) (Default: 4447):

Tomcat Shutdown Port (Default: 38011):

For JBoss

=============================================================

==================


------------------------------






HTTP Port (Default: 8080): 8181



Important: In case of Tomcat, enter the Tomcat shutdown port.

b. In the HTTP or HTTPS, if you type 2 and press Enter, the following details in the Details

for Application Server details appear.

For Tomcat

=============================================================

==================


------------------------------



NOTE: If you want to use your existing SSL certificate then

please have the SSL certificate mapped to the domain name you

want to use.


HTTP Port (Default: 8080):

HTTPS Port (Default: 8443):





Tomcat Shutdown Port (Default: 38011):

For JBoss

=============================================================

==================


------------------------------



NOTE: If you want to use your existing SSL certificate then

please have the SSL certificate mapped to the domain name you

want to use.


HTTP Port (Default: 8080):

HTTPS Port (Default: 8443):





Important: After installing KonyMobileFabric, import your SSL certificate (for

example, domain.subdomain.crt) into your MobileFabric installer's JRE trusted

certificate authority (CA) certificates file - for example, /jre/lib/security/cacerts

If your SSL certificate is not configured, the system displays an error - for example,

"peer not authenticated".

For details, refer to Troubleshoot with SSLCertificate Issues.

Note: Based on the inputs provided in the previousHTTP or HTTPS> a or HTTP

or HTTPS> b, one of the following error messages appears:

l If a port is already in use, the installer displays the following error message:

=========================================================

======================

Validation of Host Detail

-------------------------

Port 22 is already in use.

Please provide a different port.

->1- Go back to give valid input.


ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS

TO ACCEPT THE DEFAULT:



l If you provide an invalid port, the installer displays the following error message:

=========================================================

======================

Port Validation

---------------

Please enter a valid port. Port should be in between 1-

65535.

->1- Go back to give valid port.



TO ACCEPT THE DEFAULT::

l If you provide an invalid Hostname/IP address, the installer displays the following

error message:

=========================================================

======================

Invalid Hostname/IP Address

---------------------------

Please enter a valid hostname/IP address.

->1- Go back to give valid details.



TO ACCEPT THE DEFAULT:

15. Provide the Hostname/IP Address, HTTPPort, and HTTPSPort, and press Enter. The SSL

Configuration for HTTPS Communication details appear only if you select HTTPS. Choose one

of the following two options:



==================================================================

======

SSL Configuration for HTTPS Communication

-----------------------------------------

Please select the appropriate option to proceed.

->1- Create self-signed certificate

2- Provide SSL certificate


DEFAULT::

a. In the SSLConfiguration for HTTPS Communication, if you select 1, the Details for self-

signed SSLCertificate details appear.

Important: To add an existing SSL certificate to cacerts file, refer to How to Add Your

Existing SSLCertificate.

=============================================================

===========

Details for self-signed SSL Certificate

-----------------------------------------

Please provide the following details to create self-signed

certificate. All the fields are mandatory.

Please note that the path of self-signed certificate will be

/root/KonyMobileFabric/keystore.jks.

Organizational Unit (DEFAULT: ): platform

Host Name (DEFAULT: ): kony.com



Company (DEFAULT: ): Kony

City (DEFAULT: ): HYD

State (DEFAULT: ): AP

Country (DEFAULT: ): IND

Note: The path for a self-signed certificate will be in this location: \keystore.jks

b. In the SSLConfiguration for HTTPS Communication, if you select 2, the SSLCertificate

Details details appear.

Note: Provide path for .jks file as input.

=============================================================

===========

SSL Certificate Details

-----------------------

Please provide the following details

Absolute Path to Keystore File (Default: ):

/downloads/_.konylabs.net.2016.jks

c. Type the details. The installer prompts for Password for keystore file details as follows:

=============================================================

===========

Password for keystore file

-----------------------------------------



Password should contain minimum six characters and should not

contain space.

Please enter the password:

l If you enter an incorrect password -- for example, one that is fewer than six

characters, contains a space, or is empty -- the following error message for an

invalid keystore password is displayed.

=========================================================

===============

Password for keystore file

-----------------------------------------

=========================================================

===============

Invalid Keystore Password

-------------------------

Keystore password must be at least six characters and

should not contain space.

PRESS TO ACCEPT THE FOLLOWING (OK):

16. Type the password.

Important: Follow the below step only when you chooseWebLogic 12.1.3 in the

Application Server window. Otherwise, click Next to configure Database Details.

17. If you chooseWebLogic 12.1.3 in the Application Server, only then the following Application

Server Details for WebLogic will appear.

==================================================================

=============

Application Server Details

--------------------------



Please enter the details of preconfigured Weblogic server.

Fully Qualified Public URL of MobileFabric (Default: ):

IP Address/Hostname of WebLogic Management Server (Default:

10.10.24.51):

WebLogic Management Port (Default: 7001)

WebLogic JMS Port (Defau

Kony MobileFabric Installation Guide Linux

Documents

Transcript of Kony MobileFabric Installation Guide Linux