Kony Fabric Installation Guide Windows · KonyFabricInstallationGuide-Windows Version1.12...

Kony Fabric

Installation Guide - Windows

On-Premises

Release V8 SP4Document 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.

© 2020 by Kony, Inc. All rights reserved 1 of 393

Kony Fabric Installation Guide - WindowsVersion1.12

Copyright © 2014 by Kony, Inc.

All rights reserved.

February, 2020

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

Fabric, KonyNitro, 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.



Revision History

Date Document Version Description of Modifications/Release

01/26/2020 1.12 Document published for adding Upgrading Custom

Metrics Component.

10/18/2019 1.11 Document published for adding Upgrade from Kony

Fabric 8.2.

09/26/2019 1.10 Document published for adding Prerequisites for

Upgrade fromMobileFabric 7.x to Kony Fabric 8.x.

08/05/2019 1.9 Document published after modifying the -DKMS_

CORE_VERSION for JBoss, WebLogic, and

WebSphere.

08/05/2019 1.8 Document published after modifying Application

Servers Pre-installation Tasks for JBoss, WebLogic,

andWebSphere.

06/20/2019 1.7 Document published after modifying Corporate Firewall

Settings - Engagement Services

04/18/2019 1.6 Document Published for V8 SP4 FP1HF1

02/27/2019 1.5 Document Published for V8 SP4 FP1

09/24/2018 1.4 Document Published for V8 SP3



09/19/2017 1.0 Document Published for V8GA



Table of Contents

1. Preface 13

1.1 Purpose 14

1.2 Intended Audience 14

1.3 Formatting ConventionsUsed in ThisGuide 15

1.4 Related Documents 16

1.5 Contact Us 16

2. Prerequisites 17

2.1 Software Requirements 17

2.2 Hardware Requirements 17

2.3 Network Settings 18

2.3.1 Corporate Firewall Settings - Engagement Services 18

2.3.2 Proxy Settings for Integration Service 21

2.3.3 Network Settings - Licensing 22

2.4 Database Prerequisites 23

2.4.1 Prerequisites for Kony Fabric with Oracle 23

2.4.2 Prerequisites for Kony Fabric with DB2 25

2.4.3 Prerequisites for Kony Fabric with SQL Server 27

2.4.4 Prerequisites for Kony Fabric with MSSQL - Applicable for Engagement Services 28

2.4.5 Prerequisites for Kony Fabric with MySQL 29

2.4.5.1 Applicable for Engagement Services 29



2.4.5.2 Applicable for Identity Services 30

2.5 Application Servers Prerequisites 31

2.5.1 Tomcat Prerequisites 31

2.5.1.1 How to DisableWeakCiphers 31

2.5.1.2 Heap and PermGen Settings 32

2.5.2 JBoss Prerequisites 32


2.5.2.2 Configuration of Database Driver Module 32

2.5.2.3 Configure the Standalone Existing JBoss 33

2.5.2.4 Configure the Log Locations - JBoss 35

2.5.2.5 Configure the Standalone Existing JBosswith Self-Signed Certificate (JBoss 7.1) 35

2.5.2.6 Configure Port Settings for Multinode Loadbalancer Setups 36

2.5.3 WebLogic Prerequisites 37


2.5.3.2 Security Configurations 37

2.5.3.3 Configure the Log Locations - WebLogic 37

2.5.4 WebSphere Prerequisites 38


2.5.4.2 How to Enable TLSv1.2 Protocol 38

2.5.4.3 How to Retrieve Server Groups inWebSphere when using Admin Security with

TLS v1.2 40



2.5.4.4 SOAP Connector Port details for WebSphere 42

2.5.4.5 Updating the SSL Socket Factory Providers 45

2.5.4.6 NGINX Load Balancer Configuration 45

3. Kony Fabric Topology and Components 47

3.1 Developer Environment 52

3.2 Production Environment 53

4. Kony Fabric Installation on Single Node and Multinode 54

5. Pre-Installation Tasks 55

5.1 Download Kony Fabric Installer 55

5.2 Steps before installing (or) upgrading Kony Fabric with the existing database 55

5.3 Add a User in Local Group Policy (Log on as a Service) 56

5.4 Install Memcached Server 59

5.5 Configure Load Balancers for Sending Host Information inMultinode 61

5.5.0.1 Configure Hibernate Dialect inWebLogic (only for WebLogic) 62

5.6 Download and Install the Unrestricted JCE Policy Files 62

5.7 Database Pre-Installation Tasks 64

5.7.1 MySQL 64

5.7.1.1 Increase innodb_log_file_size in my.ini file - MySQL 64

5.7.2 SQL Server 64

5.7.3 WindowsAuthentication Support 64

5.7.4 Oracle 65



5.7.4.1 Create Locator Component for Oracle Database 65

5.7.5 MariaDB 67

5.7.5.1 Increase the table_definition_cache and table_open_cache values 67

5.8 Application Servers Pre-Installation Tasks 68

5.8.1 JBoss 68

5.8.1.1 Configure Load Balancer as Proxy in JBossMultinode Setup (Optional if SSL

Offloading at Load Balancer) 68

5.8.1.2 Update Listen Interfaces in host.xml for JBossCluster 68

5.8.1.3 Comment the javax-persistence-module for Kony Engagement Services on

JBossCluster 69

5.8.1.4 How to Configure Connector - JBoss 70

5.8.1.5 How to Increase Timeout andMaximumHeap Size Settings - JBoss 70

5.8.1.6 How to Configure Engagement Services - JBoss 71

5.8.2 WebLogic 72

5.8.2.1 Increase JVMmemory for WebLogic Server 72

5.8.2.2 PlaceMS SQLServer Connector JAR inWebLogic Classpath 72

5.8.2.3 How to Configure Engagement Services - WebLogic 72

5.8.3 WebSphere 73

5.8.3.1 Install Kony Fabric on a RemoteWebSphere Server with Global Security Enabled73

5.8.3.2 Configure Property Settings for Logs - (only for WebSphere) 73

5.8.3.3 Support Deployment of apiportal.war onWebSphere Server 75

5.8.3.4 Updating authService.war and accounts.war for WebSphere 9 75



5.8.3.5 How to Configure Engagement Services - WebSphere 76

6. Installation Modes - Kony Fabric 77

6.1 Installing Kony Fabric - GUI (for Windows installations) 78

6.1.1 Installing Kony Fabric on Tomcat 78

6.1.2 Installing Kony Fabric on JBossGUI (for Windows installations) 116

6.1.2.1 Installing Kony Fabric on a StandaloneMode in Bundled JBoss 117

6.1.2.2 Installing Kony Fabric on a StandaloneMode in a Pre-configured JBoss 158

6.1.2.3 Installing Kony Fabric on a DomainMode (Multi node installation in pre-

configured JBoss cluster) 184

6.1.3 Installing Kony Fabric onWebLogic 218

6.1.4 Installing Kony Fabric onWebSphere 252

6.2 Installing Kony Fabric - Silent-mode 287

7. How to Stop and Start Kony Fabric 289

7.1 Tomcat Server 289

7.2 JBoss Server 289

7.2.1 For Multinode - JBoss 289

7.3 WebLogic Server 289

7.4 WebSphere Server 290

7.4.1 Windows - To stop and start WebSphere Server 290

8. Upgrading Kony Fabric 291

8.1 Prerequisites for Upgrade fromMobileFabric 7.x to Kony Fabric 8.x 291



8.2 Upgrading Kony Fabric using installer 293

8.3 Prerequisites 294

8.4 Upgrading Kony Fabric to V8 SP4 304

8.4.1 Prerequisites 306

8.5 Upgrade fromKony Fabric V8 SP2 to V8 SP4 313

8.6 Upgrading CustomMetrics Component 314

9. Installing Hot Fix Archives for Kony Fabric - Windows 316

9.1 Patch Installer GA Versions 316

9.2 Prerequisites 317

10. Uninstalling Kony Fabric 324

11. Post-Installation Tasks 330

11.1 Configuring Secure Sockets Layer (SSL) Certificate 330

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

11.1.2 How to Add an Existing SSLCertificate to Cacerts 331

11.2 JDK Version Compatibility 332

11.3 How to Update Security Configuration in Config.xml (Required in case ofWebLogic

installation) 333

11.4 How to ConfigureMemcache for Integration Services 334

11.5 Configure Deployment of mbaasportal.war File for Multi-Node 336

11.6 Remote Installation Pre-requisites 336

11.6.1 Installing Kony Fabric Remotely 336



11.7 How to Turn off the Send usage data anonymously feature 336

11.8 Configuring Datasource for performance improvements for JBoss pre-existing and

DomainMode 337

11.9 Health CheckURL 338

11.10 Steps to enable SAPJCo 339

11.10.1 Steps for Tomcat 339

11.10.2 Steps for JBoss 340

11.10.2.1 JBoss - Standalone (Bundled) 340

11.10.2.2 JBoss - Standalone(Pre-configured)/Domainmode 340

11.10.3 Steps for Weblogic 341

11.10.4 Steps for Websphere 342

12. FAQs and Troubleshooting 343

12.1 Hostname/Port changes for Tomcat Application Server 362

12.2 Hostname/Port changes for JBoss Application Server 362

12.3 How to Configure JBossCluster 363

12.4 How to Configure a Custom JAR File onWebLogic 363

12.5 How to Configure Heap and PermGen Size 364

12.5.1 Configuring Heap and PermGen Size for Tomcat 364

12.5.2 Configuring Heap and PermGen Size for JBoss 364

12.5.3 Configuring Heap and PermGen Size for WebLogic 365

12.5.4 Configuring Heap and PermGen Size for WebSphere 365



12.6 How to Configure Kony Fabric Behind a Reverse Proxy 365

12.7 Preserving Proxy if Load Balancer or Proxy Server is Configured 367

12.8 How to Configure Frontend HTTPS to Tomcat HTTP Redirection 368

12.9 WebSphere FAQs 368

12.10 How to Change Log Levels 368

12.11 Context Root-path 371

12.11.1 Approach 1: Changing Context Root Path after the installation using the Installer 372

12.11.2 Approach 2: Changing Context Root usingManual Install Steps 380

12.11.3 Accessing Context Based Root Kony Fabric Instance through Visualizer

Enterprise 392


1. Preface Kony Fabric Installation Guide - WindowsVersion1.12

1. Preface

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

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

iOS, Android, and HTML5-based apps for modern browsers. Kony Fabric ensures that developers

build mobile applications quickly by focusing on core areas and obtaining secured back-end services

instantly. Kony Fabric hasmultiple features that can be used - Identity, Integration, Orchestration, 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 Kony Fabric, Kony

recommends that you install the following Kony Fabric features on premises:

l Kony Fabric Identity and Console

l API Developer Portal

l Kony Fabric Integration

l Kony Fabric Engagement Services

Kony Fabric 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. Kony Fabric supports the following authentication services:

o Enterprise Identity: Microsoft Active Directory, Open LDAP, Salesforce, Security

AssertionMarkup Language (SAML), Kony SAP Gateway, OAuth 2.0, Okta, Custom,

andOAuth Provider.

o Social Identity: Google, Instagram, Microsoft, BOX, Facebook, LinkedIn, Amazon, and

Yahoo.

l API Developer Portal: This feature allows you create a Portal for exposing APIs created using

Kony Fabric. Developers from internal and external partner teams can access the portal created

to explore and test the APIs



l Integration: This feature allows you to define various back-end services for your application.

You can define the following integration services:

o Technology Adapters: XML, SOAP, JSON, Java, JavaScript, and APIProxy.

o Business Adapters: Kony SAP Gateway, MuleSoft, AWSAPIGateway, Relational

Database, MongoDB, RAML, OpenAPI (Swagger), Salesforce, and IBMMQ.

l Orchestration: Service orchestration is the coordination or integration of several services and

exposing them as a single service. 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.

l Objects: Allows you to create appmodels for LOB objects, storage objects, and Service-Driven

Objects.

l Offline sync: This feature allows you to define the synchronization services for your application.

Sync supports onlyWeb Services, except SAP Sky.

l Logic: The logic services feature in Kony Fabric helps you import and integrate Node.js services

(APIs) directly into Kony Fabric for developing server-side and networking applications.

l Engagement: This feature allows you to send push notifications, email, SMS and passes to

subscribed applications.

1.1 Purpose

This document helps you install and configure Kony Fabric using the installer onWindows.

1.2 Intended Audience

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

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

applications in aWindows 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

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.



Convention Explanation

Important:Highlights actions or information that might cause problems to

systems or data

1.4 Related Documents

Document Purpose

Kony Fabric User

Guide

This guide helps you understand how to create a Kony Fabric 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 Fabric Installation Guide - WindowsVersion1.12

2. Prerequisites

The following sections explain the software and hardware required to install Kony Fabric 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


http://docs.kony.com/konylibrary/general/konyfabric_supported_devices_os_browsers/Default.htm#MobileFabric.htm?TocPath=Kony%2520MobileFabric|_____0


2.3 Network Settings

2.3.1 Corporate Firewall Settings - Engagement Services

Source Destination Ports Protocol

Direction

Action

Description

Engage

ment

Server

https://api.push.apple.com:443/3/device/ 443 TCP Both Allow Allow the

Engagem

ent Server

to access

Apple

APNS

HTTP2

production

URL

Engage

ment

Server

https://api.jpush.cn/v3/push 443 TCP Outbou

nd

Allow Allow the

Engagem

ent Server

to access

the JPush

notificatio

n server

URL

Engage

ment

Server

https://api.development.push.apple.com:

443/3/device/

443 TCP Both Allow Allow the

Engagem

ent Server

to access

Apple

APNS

HTTP2

developm

ent URL




Direction

Action

Description

Engage

ment

Server

https://fcm.googleapis.com 443 TCP Outbou

nd

Allow Allow the

Engagem

ent Server

to access

Firebase

Cloud

Messagin

g (FCM)

service

Engage

ment

Server

feedback.push.apple.com,

feedback.sandbox.push.apple.com,

17.0.0.0/8 (17.0.0.1 to 17.255.255.254)

2196 TCP Outbou

nd

Allow Allow the

Engagem

ent Server

to access

APNS

feedback

service

Engage

ment

Server

gateway.push.apple.com,

gateway.sandbox.push.apple.com,

17.0.0.0/8 (17.0.0.1 to 17.255.255.254)

2195 TCP Outbou

nd

Allow Allow the

Engagem

ent Server

to access

Apple's

APNS

Engage

ment

Server

All subdomains of

pushapi.eval.blackberry.com Sample

Push URL:

https://cpxxxxxxxxxxxxxxxxxxxxxx.

pushapi.eval.blackberry.com/mss/PD_

pushRequest

443 TCP Outbou

nd

Allow Allow

connect to

Blackberr

y Cloud

through

this port




Direction

Action

Description

Engage

ment

Server

http://sn1.notify.live.net 443 TCP Outbou

nd

Allow Allow

connect to

Windows

Cloud

(MPNS)

through

this port

Engage

ment

Server

https://login.live.com 443 TCP Outbou

nd

Allow Allow

connect to

Windows

Cloud

(WNS)

through

this port

Internal

Corporat

eWiFi

router for

Android

Mobile

Devices

Allow your firewall to accept outgoing

connections to all IP addresses contained

in the IP blocks listed in Google's ASN of

15169. Reference link for the IP

Addresses http://bgp.he.net/AS15169

5228,

5229,5

230

TCP,

HTTP,

HTTP

S,

UDP

Both Allow Android

devices

will

connect to

GCM

through

this port

Internal

Corporat

eWiFi

router for

iOS

Devices

gateway.push.apple.com,

feedback.push.apple.com,

gateway.sandbox.push.apple.com,

feedback.sandbox.push.apple.com,

17.0.0.0/8 (17.0.0.1 to 17.255.255.254)

5223 TCP Both Allow Apple

devices

connect to

APNS

servers

through

this port


http://bgp.he.net/AS15169



Direction

Action

Description

Internal

Corporat

eWiFi

router for

iOS

Devices

ax.init.itunes.apple.com, ocsp.apple.com 80, 443 TCP Both Allow Apple

devices

will

connect to

public

Apple

OCSP

and

iTunes

service

through

this port

Internal

Corporat

eWiFi

router for

Window

Devices

Add the list IPs specified in the following

WNS URL http://www.microsoft.com/en-

us/download/details.aspx?id=44238

TCP,

HTTP,

HTTP

S,

UDP

Both Allow Windows

devices

will

connect to

WNS

through

this port

Internal

Corporat

eWiFi

router for

Window

Devices

Add the list IPs specified in the following

MPNS URL:

https://www.microsoft.com/en-

us/download/details.aspx?id=44535

TCP,

HTTP,

HTTP

S,

UDP

Both Allow Windows

devices

will

connect to

MPNS

through

this port

2.3.2 Proxy Settings for Integration Service

To add an Integration Service Environment when the proxy is set at an App Server level, enable the

following proxy settings at the JVM level:


http://www.microsoft.com/en-us/download/details.aspx?id=44238http://www.microsoft.com/en-us/download/details.aspx?id=44238https://www.microsoft.com/en-us/download/details.aspx?id=44535https://www.microsoft.com/en-us/download/details.aspx?id=44535


l Dkony.http.proxyHost= 10.0.4.29

l Dkony.http.proxyPort= 2080

l Dkony.http.proxyUser= websphere

l Dkony.http.proxyPassword= 3MqGU9e5nv3B

2.3.3 Network Settings - Licensing

The on-premises server should allow outbound requests to https://manage.kony.com and allow

inbound requests from our License servers (IPs, mentioned at the end, can be whitelisted in a

customer’s firewall).

An on-premises Fabric 'development' or 'non-production' license can be activated without making the

on-premises Identity URL available to our License servers. However, a 'production' license requires

the Identity URL to be available to our License servers at the time of activation and thereafter as the

license is validated on a weekly frequency. Each time that a production license is validated, the license

validity is good for 30 days from the last successful validation. The Identity URL is expected to remain

available to our License server for the entirety of their licensing term.

The Fabric Identity account tenant must be accessible on the internet. The Cloud license activation

screen displays the Identity tenant configured in on-premise console. (For example,

https:konyfabric.mycompany.com/authService)

Cloud license activation flow appends “/accounts” to the Identity URL . (For example,

https:konyfabric.mycompany.com/authService/accounts). The URLmust be accessible on the public

internet for license activation to work. The response of the URL should be “Welcome to Test Auth

Service”.

Communication fromKony's License servers will originate from the following IP addresses, which can

be whitelisted in an organization's firewall configuration:

l 54.208.192.84

l 54.208.192.248


https://manage.kony.com/


2.4 Database Prerequisites

Before you install Kony Fabric Console Installer, youmust perform the following Pre-Installation 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.

2.4.1 Prerequisites for Kony Fabric with Oracle

For installing Kony Fabric 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 the Kony Fabric database deployment. Oracle software

must be installed and basic databasemust be created before to continue with Kony Fabric

database schema setup.

Important: Ensure that a dedicated database user must not be an application user 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 Kony Fabric 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 create Kony Fabric 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 TEMP PROFILE DEFAULT;

GRANT DBA TO ;

ALTER USER QUOTA UNLIMITED ON MF_DATA;

ALTER USER QUOTA UNLIMITED ON MF_INDEX;

ALTER USER QUOTA UNLIMITED ON MF_LOB_DATA;

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 DBA TO 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;

l If you are using Kony Fabric installer to setup Kony Fabric 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 pdborcl orpdbmfdb

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

URL such as orcl or mfdb.

jdbc:oracle:thin:@:1521:mfdb

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

2.4.2 Prerequisites for Kony Fabric 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.

Note: FromV8 SP4 FP1HF1 onwards, DB2 is not supported for bundled Tomcat and JBoss

servers.



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.

For more details on How to Create the Big tablespace in DB2, click here: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;

Note: If Kony Fabric installation with DB2 fails, youmust verify the following settings:.

db2set DB2_COMPATIBILITY_VECTOR=ORA

db2set DB2_DEFERRED_PREPARE_SEMANTICS=YES

2.4.3 Prerequisites for Kony Fabric 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 selected Kony Fabric components.

l Database Growth sizing: Refer to Kony Fabric 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 the Kony Fabric 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 Kony Fabric, 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 Kony Fabric, 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

Kony Fabric, 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 SQL Server Standard Edition or SQL Server Enterprise

Edition database for installing Kony Fabric. Kony Fabric is compatible with these editions.

There are no prerequisites specific to these editions as Kony Fabric 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.

2.4.4 Prerequisites for Kony Fabric with MSSQL - Applicable for Engagement Services

Database collation needs to be set for a database. This is possible while creating a database with your

required language as database collation. For example, use Database collation as Arabic_100_CI_AS

for Arabic language support. Similarly for other languages use appropriate collation for support. Use

SQL Server Management Studio to create a database with the name as kpnsdb and with appropriate

collation support.


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


2.4.5 Prerequisites for Kony Fabric with MySQL

2.4.5.1 Applicable for Engagement Services

1. Create the database needed for Engagement Serviceswith unicode character set as UTF8.

Also ensure that youmodify the my.cnf or my.ini with the following parameters:

[client]

default-character-set = utf8

[mysql]

default-character-set = utf8

[mysqld]|

character-set-client-handshake = FALSE

collation_server='utf8_unicode_ci'

character_set_server='utf8'

2. Next, restart theMySQL service and run the following query to verify the details:

mysql> show variables like '%coll%';

+----------------------+-----------------+

| Variable_name | Value |

+----------------------+-----------------+

| collation_connection | utf8_unicode_ci |

| collation_database | utf8_unicode_ci |

| collation_server | utf8_unicode_ci |

+----------------------+-----------------+

3 rows in set (0.00 sec)

mysql> show variables like '%char%';

+--------------------------+----------------------------+

| Variable_name | Value |

+--------------------------+----------------------------+

| character_set_client | utf8 |

| character_set_connection | utf8 |

| character_set_database | utf8 |

| character_set_filesystem | binary |



| character_set_results | utf8 |

| character_set_server | utf8 |

| character_set_system | utf8 |

| character_sets_dir | /usr/share/mysql/charsets/ |

+--------------------------+----------------------------+

2.4.5.2 Applicable for Identity Services

If you are using any lower versions of MySQL 5.7 such as v5.7.12 or lower during installation, youmay

encounter an error due to which the installation rolls back. This error occurs due to a bug in theMySQL

database.

For more information, refer MySQLBugs

Following are the error details:

l Error: Migration V810_27_01__

DeleteDuplicateAcsUserIdProviderGuidRowsAddUniqueConstraint.sql failed

l SQL State: HY000

l Error Code: 1093

l Error Message: You can't specify target table 'users' for update in FROMclause

l Location:

To resolve this error, run the following commands in theMySQLServer:

1. Execute the following command before running the installer:

SET GLOBAL optimizer_switch = 'derived_merge=off';

2. Once the installation is done, set derived_mergeON using the following command:

SET GLOBAL optimizer_switch = 'derived_merge=on';


https://bugs.mysql.com/bug.php?id=79286


2.5 Application Servers Prerequisites

2.5.1 Tomcat Prerequisites

2.5.1.1 How to Disable Weak Ciphers

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.5.1.2 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. Tomcat heap and PermGen settings

Note: FromV8 SP4 FP1HF1 onwards, Java 11 is supported for bundled Tomcat and JBoss

servers.

2.5.2 JBoss Prerequisites



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

Note: FromV8 SP4 FP1HF1 onwards, Java 11 is supported for bundled Tomcat and JBoss

servers.

2.5.2.2 Configuration of Database Driver Module

1. Extract the com.zip file.

The unzipped folder structure will becom\mysql\main.

2. Stop the JBoss Application Server.

3. For JBoss configured in the standalonemode, copy the extractedcom.zip folder and place it

in the {JBOSS_HOME}/modules/ path. For the domainmode, place the unzipped

com.zip folder (com\mysql\main\) in the{JBOSS_HOME}/modules/ path for

each of themaster/slavemachines.

4. Open and edit the appropriate configuration file based on the configured JBossmode.


http://docs.kony.com/8_x_PDFs/com.zip


For example, domain.xml in the domainmode andstandalone-full.xml in the

standalonemode. These files are available at {JBOSS_HOME}

/domain/configuration and{JBOSS_HOME}

/standalone/configuration folders respectively.

5. Search for the tag and add the

appropriate globalmodule based on the database selected.

For example, add the following code for the domainmode:

6. Save the changes.

7. Start the JBoss Server.

2.5.2.3 Configure the Standalone Existing JBoss

To install Kony Fabric on an existing standalone JBoss, follow the steps to configure the standalone

JBoss:

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

2. Configure Hostname/IP in the standalone.xml file for JBoss, as below:



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

l Add under the

l Add following section under the

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

|

5. In case of installing all the Kony Fabric 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.5.2.4 Configure the Log Locations - JBoss

To specify the log location where the logs for all Kony Fabric components will be generated, youmust

add the following parameter in the JVMarguments present instandalone.bat/domain.bat

( for Windows) or standalone.sh/domain.sh(for Unix):

-Duser.home=""

2.5.2.5 Configure the Standalone Existing JBoss with Self-Signed Certificate (JBoss 7.1)

If you need to use existing JBosswith self-signed certificate, follow these steps:

1. Add an Existing SSLCertificate to Cacerts. For more details, click How to Add an Existing

Secure Sockets Layer (SSL) Certificate.

2. Copy the keystore file to /standalone/configuration folder.

3. Modify thestandalone.xml by adding the following security-realm in the

security-realms section.

Here = Name of the keystore file. (for example, keystore.jks)

= Password of keystore file.


http://docs.kony.com/konylibrary/konyfabric/kony_fabric_windows_install_guide/Content/Post-Installation_Tasks.htm#ExistingSelf-signedcertificatehttp://docs.kony.com/konylibrary/konyfabric/kony_fabric_windows_install_guide/Content/Post-Installation_Tasks.htm#ExistingSelf-signedcertificate


4. In the standalone.xml, add the following https-listener tag for default-server in the

Subsystem urn:jboss:domain:undertow:3.1 .

2.5.2.6 Configure Port Settings for Multinode Loadbalancer Setups

Before installing Kony Fabric on an application server, for the application server to communicate with a

Web Server properly, youmust open the port 80.

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:


3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_

WITH_AES_256_CBC_SHA, TLS_ECDH_anon_WITH_3DES_EDE_CBC_SHA,TLS_ECDH_

anon_WITH_AES_128_CBC_SHA, TLS_ECDH_anon_WITH_AES_256_CBC_SHA"

verify-client="REQUIRED" security-realm="ApplicationRealm" socket-

binding="connect"/>

2.5.3 WebLogic Prerequisites



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

2.5.3.2 Security Configurations

To add environments to Kony Fabric Console, add the following configuration inside the security-

configuration tag of theconfig.xml file of WebLogic Server.

false

After configuring the security-configuration tag, restart the server fromWebLogic console. In

case ofWebLogic cluster, restart all servers fromWebLogic console.

2.5.3.3 Configure the Log Locations - WebLogic

To specify the log location where the logs for all Kony Fabric components will be generated, youmust

add the following parameter in the JVMarguments present inbin/startWebLogic.cmd( for

Windows) or bin/startWebLogic.sh(for Unix):

-Duser.home=""



2.5.4 WebSphere Prerequisites



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

2.5.4.2 How to Enable TLSv1.2 Protocol

If your Kony Fabric instance onWebSphere that is updated with IBM Java 7 SDK fix pack 7.0.9.60, the

identity fails to log-in to Salesforce. Because the TLSv1.0 protocol is disabled on Kony Fabric and on

the other external sites that Kony Fabric wants to connect - for example, Salesforce. To avoid log-in

issueswith external back-ends, add the -D parameters into JVMArguments.

To add -D parameters in the JVM arguments, follow these steps:

1. Log intoWebSphere Admin Console.

2. Go to Application servers > server1 > Process definition > Java Virtual Machine.

3. Under the Configuration > General Properties > Generic JVM arguments, add the following -

D parameter:

-Dhttps.protocols=TLSv1.1,TLSv1.2 -Dcom.ibm.jsse2.overrideDefaultTLS=true


http://docs.kony.com/konylibrary/konyfabric/resources/websphere_faqs.htm#Heap_WAS


4. Go to Security > SSL certificate and key management > SSL configurations >

NodeDefaultSSLSettings > Quality of protection (QoP) settings.

5. Under General Properties > Protocol, select the TLSv1.1 protocol.

6. If your Kony Fabric is installed onWebSphere with IBM Java 8, add the following parameter to

JVM arguments:

-Dcom.ibm.jsse2.overrideDefaultTLS=true

For more details, refer to Salesforce disabling TLS 1.0


https://help.salesforce.com/articleView?id=000221207&type=1


2.5.4.3 How to Retrieve Server Groups in WebSphere when using Admin Security with TLS v1.2

1. InWebSphere Admin Console, download the default SSL certificate.

2. Import certificate into IBM Java path: {IBM_PATH}/{JAVA}/jre/lib/security/cacerts

For example, /opt/IBM/WebSphere/AppServer/java_1.8_

64/jre/lib/securitykeytool -importcert -keystore cacerts -

storetype jks -file /opt/IBM/WebSphere/AppServer/java_1.8_

64/jre/lib/security/17229154223.crt -alias 172.29.154.223

3. If you are prompted for a password, enter the password:

l Default password: changeit



4. Select the Enable administrative security check box.

5. Set the following JVM arguments:

l Set JVM heap size

l Set JVM generic arguments



6. Restart the application server after setting JVMarguments.

7. Execute the installer with LAX_VM.

For example, KonyMobileFabricInstaller.exe LAX_VM "D:\Program

Files (x86)\IBM\WebSphere\AppServer\java\bin\java.exe"

8. Provide the default path of certs in the installation wizard. For example,

/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/etc

2.5.4.4 SOAP Connector Port details for WebSphere

To see information such as ports, in the Administrative console, select Servers > Server Types >

WebSphere application servers. Select your server and view the Communication > Ports section for a

list of ports being used by your server. In the example port configuration shown in the screen below,

this is port 8880.



Default Port Name Remarks

8880 SOAP_

CONNECTOR_

ADDRESS

Open between all nodes and the deployment manager.

Used for administration of remote nodes and

synchronization. Used for server to server

communication. The Sametime® System Console

accesses the deployment manager SOAP port. This port

number varies, depending on how WebSphere Application

System was installed. The port number can be

determined by looking at AboutThisProfile.txt's SOAP

connector port value in the profile log directory or the

Integrated Solutions Console.

9080 WC_defaulthost Port on SametimeMeeting Server or Sametime Proxy

Server where traffic from theWebSphere HTTP Proxies

is sent.

9443 WC_defaulthost_

secure

Port onMeeting Server or Sametime Proxy Server where

secure traffic from theWebSphere HTTP Proxies is sent.

Note: Ensure that the port number for the SOAP_CONNECTOR_ADDRESS is set to 8880.

By default, the application listens on port 9080. For more information, refer WebSphere

Application Server Ports.

Note: If you are using standaloneWebSphere Server without Load Balancer, ensure that the port

for default host is set to either 9080 or 9443. If you are using a Load Balancer configuration, set the

default host to the fully qualified host name of the Load Balancer.


https://www.ibm.com/support/knowledgecenter/en/SSKTXQ_9.0.1/admin/plan/plan_websphereapplicationserverports.htmlhttps://www.ibm.com/support/knowledgecenter/en/SSKTXQ_9.0.1/admin/plan/plan_websphereapplicationserverports.html


2.5.4.5 Updating the SSL Socket Factory Providers

l See that the SOAP_CONNECTOR_PORT is open.

l If theWAS server is secured, set the following in java/jre/lib/security/java.security:

l ssl.SocketFactory.provider=com.ibm.jsse2.SSLSocketFactoryImpl

(for Java7)

l ssl.ServerSocketFactory.provider=com.ibm.jsse2.SSLServerSocke

tFactoryImpl (for Java8)

Refer Configure SSL for WebSphere.

2.5.4.6 NGINX Load Balancer Configuration

l Following are the URLmappings for the Load Balancer configuration:

l https:///mfconsole -> https:///mfconsole

l https:///accounts -> https:///accounts

l https:///workspace -> https:///workspace

l https:///authService -> https:///authService

l https:///admin -> https:///admin

l https:///services -> https:///services

l https:///middleware -> https:///middleware

l https:///apps -> https:///apps

l https:///metrics -> https:///metrics

l https:///kpns -> https:///kpns

l Visualizer runs on localhost: 5000, by default. Hence it must be allowed. Also allow 8888 if you


https://www.ibm.com/support/knowledgecenter/en/SSFUEU_7.4.0/op_grc_admin/t_adm_update_ssl_socketfactory_providers.html


want to test web applications locally. Set the following HTTP response header X-Frame options

to allow the required localhost:

l add_header X-Frame-Options "ALLOW-FROM localhost:5000";

l add_header X-Frame-Options "ALLOW-FROM localhost:8888";


3. Kony Fabric Topology and Components Kony Fabric Installation Guide - WindowsVersion1.12

3. Kony Fabric Topology and Components

Kony Fabric 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 the Kony Fabric architecture and components follows:



An overview of the Kony Fabric deployment architecture follows:

The following table describes the components of Kony Fabric:



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

API Developer

Portal

Kony Fabric Developer Portal feature lets you create a Portal for exposing

APIs created using Kony Fabric. Developers from internal and external

partner teams can access the portal created to explore and test the APIs

You can directly access your Kony Developer Portal in Kony Fabric Console.


http://docs.kony.com/konylibrary/konyfabric/kony_fabric_user_guide/Default.htm#KonyDevPortal.htm?TocPath=Features|_____16


Convention Description

Environments

(Engagement

Services,

Integration

Services)

This component adds runtime capabilities to apps, such as engagement

services, and integration services.

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

test the services shown in Admin Console. 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 https://docs.kony.com/konylibrary/integration/kmf_

integrationservice_admin_console_userguide/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 when Kony Fabric is integrated. It has same

runtime capabilities as themiddleware.

Note: To use Kony Server with Kony Fabric integrated, you can ignore

themiddleware.war. Similarly when you use only standalone Kony

Server, you can ignore the services.war.

Note:The Kony Fabric components can be configured on one node or separate nodes - for example,

you can use one of the following choices:


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


l Install All Components on one node.

l Install Kony Fabric Console, Identity Services, Integration Services, and Engagement

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 Kony Fabric components in a

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

Installation.

Important: Kony Fabric Installer supports Tomcat, JBoss,WebLogic, andWebSphere.

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

Install Guide.

Kony Fabric Consolidated installer supports JBoss on single node (Standalone Mode) andmulti-

node (Domain Mode).

Important: By default Kony Fabric Consolidated installer supportsmemcached server only in case

of multinode installation.

By default Kony Fabric 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.


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


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.


4. Kony Fabric Installation on Single Node and

Multinode

Kony Fabric Installation Guide -

WindowsVersion1.12

4. Kony Fabric Installation on Single Node and Multinode

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

local environment.

The following table details Kony Fabric installation supported for a single node andmultinode

installations.

Kony Fabric Components can be installed Single Node Multinode

Console

l Workspace

l Accounts

Identity

Integration

l Admin

l Middleware

l Services

l Metrics

API Developer Portal

Engagement Services


5. Pre-Installation Tasks Kony Fabric Installation Guide - WindowsVersion1.12

5. Pre-Installation Tasks

5.1 Download Kony Fabric Installer

DownloadKonyFabricSetup.zip from http://community.kony.com/downloads and extract the

file. To download Kony Fabric 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 Fabric tab.

3. Select the specific release version from the Kony Fabric 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 Fabric 8.0.0 GA installer,

select the 8.0.0 GA version from the drop-down list, and then click the Installer_Windows

link.

TheKonyFabricSetup.zip file contains the following files:

n KonyFabricInstaller-x.x.x.x_GA.exe

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

n README.txt

5.2 Steps before installing (or) upgrading Kony Fabric with the existing

database

Perform the following activities before installing (or) upgrading Kony Fabric with the existing database:

l Take database backup

l Make sure you have previously installed directory


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


l Take a backup of applications deployed at the server level. (Post installation, take backup of the

changes done to the binaries).

l Post installation (or) upgrade process, replace old authService.key, workspaceService.key, and

ACCOUNTS_ENCRYPTION_KEY (applicable only for identity and workspace components).

5.3 Add a User in Local Group Policy (Log on as a Service)

Before installing Kony Fabric in a newWindows node, ensure that you have privileges to log on as a

service. The log on as a service privileges are required to start a service by a user.

When a user name does not have privileges to log on as a service and is tries to install Kony Fabric in

a newWindows box, the system gives the following error:

To grant log on as service to a user, follow these steps:

1. Click Start, and then click Run (Win+R).

2. In the Run box, type gpedit.msc, and then clickOK. The Local Group Policy Editor window

appears.

3. In the left pane, under Local Computer Policy, expand Computer Configuration > Windows

Settings > Security Settings > Local Policies > User Rights Assignment.



4. In the right pane, double-click Log on as service. The Log on as a service Properties window

appears.



5. In the Local security setting tab, double-click Add User or Group to display the Select Users,

Computers, Service Accounts, or Groups window.

6. In the Enter the object names to select text box, enter the user name, clickOK. The system

adds the user name in the Local security setting tab.



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

To install Memcached Server, follow these steps:

1. Download thememcache server.

2. Extract the zip file.

3. From the command prompt, navigate to memcached directory.

4. Run the following command:

memcached.exe -d install

For example, c:/memcached/memcached.exe -d install

5. Start the server from the Services or by running one of the following commands:

l c:/memcached/memcached.exe -d start

l net start memcached Server

Now your memcached server is installed and is listening to port 11211.

6. By default, the server is set to 64MBmemory limit, which is too small. To add the extramemory

allocation, edit the registry to add the information. To increase the default memory size, in the

Windows Runwindows, type Regedit to display the Registry Editor window:



7. In the Registry Editor window, navigate to the following key:

HKEY_LOCAL_

MACHINE/SYSTEM/CurrentControlSet/Services/memcached Server.

8. In the key, change the ImagePath entry with the following:

C:/memcached/memcached.exe -d runservice -m 2048

This way you will use 512MBmemory limit for your server.

If you now go back to the service section you should now seememcached installed, shown

below:



If you are not seeing the above result, restart your computer. You now havememcached

running.

5.5 Configure Load Balancers for Sending Host Information in

Multinode

When user is installing Kony Fabric 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 launch Kony Fabric 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.5.0.1 Configure Hibernate Dialect in WebLogic (only for WebLogic)

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

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

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

5.6 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 .jar 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:


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


1. Go to the Oracle Java SE download

page http://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

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\jre\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.

l Database Pre-Installation Tasks

l Application Servers Pre-Installation Tasks


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


5.7 Database Pre-Installation Tasks

5.7.1 MySQL

5.7.1.1 Increase innodb_log_file_size in my.ini 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 SQL Statement 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 (1 MB) and you try to publish an application

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

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

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

In the my.ini file, increase the innodb_log_file_size =

5.7.2 SQL Server

5.7.3 Windows Authentication Support

To support Kony Fabric Installation usingWindowsAuthentication on SQL Server, follow these steps:

l Download themssql-jdbc-7.0.0.jre8 (sqljdbc_7.0.0.0_enu.tar.gz) artifact from

https://www.microsoft.com/en-US/download/details.aspx?id=57175


https://www.microsoft.com/en-US/download/details.aspx?id=57175


l Extract the artifact onto your local system. For example, the locationmust be like:

D:\Downloads\sqljdbc_7.0.0.0_enu.tar.gz\mssql-jdbc-

7.0.0\enu\auth\x64)

5.7.4 Oracle

5.7.4.1 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 during Kony Fabric Installation.

l Option #2. Run the following scripts on the database to be used for Kony Fabric, 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.

After executing the above steps, execute the following query to check if everything is fine:

Select * from dba_objects where owner='MDSYS' and object_name

like 'SDO%';



Once theOracle locator is installed, run the Installer to setup Kony Fabric. The system should

not throw the error: Invalid Data Type SDO_GEOMETRY

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.7.5 MariaDB

5.7.5.1 Increase the table_definition_cache and table_open_cache values

To increase the values of table_definition_cache and table_open_cache inMariaDB, execute the

following commands or update the ini or cnf file with:

set GLOBAL table_definition_cache=4000; //For table_definition_cache;

4000 is the minimum value

set GLOBAL table_open_cache=2000; //For table_open_cache; 2000 is the

minimum value



5.8 Application Servers Pre-Installation Tasks

5.8.1 JBoss

5.8.1.1 Configure Load Balancer as Proxy in JBoss Multinode Setup (Optional if SSL Offloading at

Load Balancer)

1. Navigate to your Kony Fabric 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.8.1.2 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 existing interfaces xml tag, replace the default content with below details:


configuration.

To secure JacORB you need to setup SSL -->

5.8.1.3 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.8.1.4 How to Configure Connector - JBoss

For importing an app to Kony Fabric 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

5.8.1.5 How to Increase Timeout and Maximum Heap Size Settings - JBoss

Restarting JBoss can cause deployment failures. To avoid these failures, youmust increase the JBoss

timeout andmaximumheap size settings for cluster.

To increase memory and timeout settings in JBoss (pre-configured JBoss), follow these steps:

1. In the standalone.bat or .sh file, add the following properties to Java_opts:

-Djboss.as.management.blocking.timeout=8400

-Xms2048m

-Xmx4096m

2. In the /standalone/configuration/standalone.xml file, add

config deployment-timeout=”8400” in the deployment-scanner subsystem,

shown below:


http://docs.kony.com/konylibrary/konyfabric/kony_fabric_manual_install_guide/Default.htm#Configuring_Connectors_and_WAR_JBoss.htmhttp://docs.kony.com/konylibrary/konyfabric/kony_fabric_manual_install_guide/Default.htm#Configuring_Connectors_and_WAR_JBoss.htm


To increase memory and timeout settings in JBoss Multinode, follow these steps:

1. In the domain.bat or .sh file, add the following properties to Java_opts:

-Djboss.as.management.blocking.timeout=8400

2. Set the heap size for the selected server groups as below in the /domain/configuration/domain.xml.

l Search for tag in the domain.xml and set the heap size in the JVM

settings.

5.8.1.6 How to Configure Engagement Services - JBoss

When Engagement is selected as Fabric Component, based on the selected JBossmode, youmust

add the following parameter in the JVMarguments present instandalone.bat/domain.bat

( for Windows) or standalone.sh/domain.sh(for Unix):

-DKMS_CORE_VERSION=2



5.8.2 WebLogic

5.8.2.1 Increase JVMmemory for WebLogic Server

For a successful deployment of Kony FabricWar files onWebLogic server, increase the PermGen

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

5.8.2.2 Place MS SQL Server Connector JAR in WebLogic Classpath

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

mssql-jdbc-7.0.0.jre8 file in theWebLogic classpath.

Important: To add themssql-jdbc-7.0.0.jre8 file in theWebLogic classpath, perform

the following steps before starting Kony Fabric installation.

To add mssql-jdbc-7.0.0.jre8 file in the WebLogic classpath, follow these steps:

1. Place the mssql-jdbc-7.0.0.jre8 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\mssql-jdbc-

7.0.0.jre8;%JAVA_HOME%\lib\tools.jar;%PROFILE_

CLASSPATH%;%ANT_CONTRIB%\lib\ant-contrib.jar;%CAM_

NODEMANAGER_JAR_PATH%

4. Restart the server.

5.8.2.3 How to Configure Engagement Services - WebLogic

When Engagement is selected as Fabric Component, youmust add the following parameter in the

JVMarguments present indomain-name\StartWebLogic.cmd (for Windows) or

domain-name\StartWebLogic.sh (for Unix):




5.8.3 WebSphere

5.8.3.1 Install Kony Fabric 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 the Kony Fabric Installer.

1. Install IBMWebSphere SDK on a systemwhere you want to run the Kony Fabric Installer.

2. Add the SSL certificate to DMGR. For more information, refer to How to Add an Existing Secure

Sockets Layer (SSL) Certificate.

3. Launch a Command prompt window.

4. Go to the location of the Kony Fabric Installer.

5. Run the Kony Fabric Installer as follows:

KonyFabricInstaller-7.x.exe LAX_VM

5.8.3.2 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.8.3.3 Support Deployment of apiportal.war on WebSphere Server

To support deployment of the apiportal.war onWebSphere, make the following configuration

changes:

l Disable the following option

Go to Servers > Server Types > WebSphere application servers > server_name > Session

management > Enable cookies > Restrict cookies to HTTPS sessions.

l Remove the row matching with domain=*, name=JSESSIONID, path=/ in the

Security > Global Security > Programmatic session cookie configuration.

5.8.3.4 Updating authService.war and accounts.war for WebSphere 9

1. Add the following -D params in the jvm properties:

“com.ibm.websphere.jaxrs.server.DisableIBMJAXRSEngine=true”



2. In the server configuration, expand container services. In the

Default JAXRS provider settings change the JAX-RS Provider to

2.0spec.

5.8.3.5 How to Configure Engagement Services - WebSphere

When Engagement is selected as Fabric Component, youmust add the following parameter in the

Generic JVM arguments section of theWebSphere Administration Console under Application

Servers > serverName > Process Definition > Java Virtual

Machine:



6. Installation Modes - Kony Fabric Kony Fabric Installation Guide - WindowsVersion1.12

6. Installation Modes - Kony Fabric

You can install Kony Fabric 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 Installing Kony Fabric - GUI (for Windows installations)

l Installing Kony Fabric - Silent-mode (for working with limited or no user interaction)



6.1 Installing Kony Fabric - GUI (for Windows installations)

You can install Kony Fabric on Tomcat, JBoss,WebLogic, or WebSphere servers.

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 Installing Kony Fabric on Tomcat (single node)

l Installing Kony Fabric on JBoss

o StandaloneMode (Single Node installation in Bundled JBoss)

o StandaloneMode (Single Node Installation in pre-configured JBoss)

o DomainMode (Multi Node installation in pre-configured JBoss cluster)

l Installing Kony Fabric onWebLogic

l Installing Kony Fabric onWebSphere

6.1.1 Installing Kony Fabric on Tomcat

This section of the document provid

Date post:	22-May-2020
Category:	Documents
Upload:	others
View:	29 times
Download:	0 times