kony fabric manual installation guidemanual installation guide ... 4.6.1 prerequisites for kony...

Kony Fabric

Manual Installation Guide

On-PremisesKony recommends using the Kony Fabric (MobileFabric) Installer for deploying MobileFabric 7.0 onwards.

If you want to install Kony Fabric manually due to your business rules and policies, please contact

[email protected] for approval and to obtain access to the Kony Fabric manual install artifacts.

Manual installs not approved by Kony will not be supported.

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.

© 2019 by Kony, Inc. All rights reserved 1 of 633

mailto:[email protected]

Manual Install GuideVersion1.5

Copyright © 2014 by Kony, Inc.

All rights reserved.

December, 2019

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

agreements, and may not be used except in the context of understanding the use and methods of

Kony, Inc., software without prior, express, written permission. Kony, Empowering Everywhere, Kony

Fabric, Kony Nitro, and Kony Visualizer are trademarks of Kony, Inc. MobileFabric is a registered

trademark of Kony, Inc. Microsoft, the Microsoft logo, Internet Explorer, Windows, and Windows Vista

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

X, Objective-C, Safari, Apple Pay, Apple Watch, and Xcode are trademarks or registered trademarks

of Apple, Inc. Google, the Google logo, Android, and the Android logo are registered trademarks of

Google, Inc. Chrome is a trademark of Google, Inc. BlackBerry, PlayBook, Research in Motion, and

RIM are registered trademarks of BlackBerry. SAP® and SAP® Business Suite® are registered

trademarks of SAP SE in Germany and in several other countries. All other terms, trademarks, or

service marks mentioned in this document have been capitalized and are to be considered the

property of their respective owners.



Revision History

Date Document Version

Description of Modifications/Release

04/18/2019 1.5 Document Published for V8 SP4 FP1 HF1

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

09/24/2018 1.3 Document Published for V8 SP3

04/19/2018 1.2 Document updated for V8 SP2

09/19/2017 1.0 Document Published for V8 GA



Table of Contents

1. Preface 11

1.1 Purpose 12

1.2 Intended Audience 12

1.3 Formatting Conventions 12

1.4 Related Documents 13

1.5 Contact Us 14

2. Kony Fabric Topology and Components 15

3. Kony Fabric Installation on Single Node and Multinode 20

4. Prerequisites 21

4.1 Software Requirements 22

4.2 Hardware Requirements - Console, Identity, and Integration Services 22

4.3 Hardware Requirements - Engagement Services 22

4.4 Database System Requirements (per physical instance) - Engagement Services 23

4.4.1 Corporate Firewall Settings - Engagement Services 24

4.5 Proxy Settings for Integration Service 29

4.6 Database Prerequisites 31

4.6.1 Prerequisites for Kony Fabric with Oracle 31

4.6.2 Prerequisites for Kony Fabric with MSSQL- Applicable for Engagement Services 35

4.6.3 Prerequisites for Kony Fabric with MySQL 36

4.6.4 Prerequisites for Kony Fabric with DB2 38



4.6.5 Increase innodb_log_file_size in my.ini file (For Engagement Services) 40

4.6.6 Prerequisites for Kony Fabric with MariaDB 41

4.7 Required Setup Files 42

4.7.1 Required Setup Files - Kony Fabric Console, Accounts, and Workspace 42

4.7.2 Required Setup Files - Identity Services 43

4.7.3 Required Setup Files - Integration Services 43

4.7.4 Required Setup Files - Engagement Services 44

4.7.5 Database JARs 46

4.8 Encrypt Passwords 47

4.9 Pre-Installation Tasks - Database 48

4.9.1 Configuring Flyway Command-line Tool 48

4.10 Preinstallation Tasks - App Servers 54

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

4.10.2 Download and Install the Unrestricted JCE Policy Files 57

4.10.3 Setting JVM arguments for WebSphere 58

4.10.4 Setting JVM arguments for Salesforce Services 58

4.10.5 Configure Middleware Home 61

4.11 Configuring Installation Modes - App Servers 72

4.11.1 How to Install Tomcat Server 72

4.11.2 How to Install JBoss Server 79

4.11.3 How to Configure Installation Mode - WebLogic Server 93



4.11.4 How to Configure Installation Mode - WebSphere Server 94

4.11.5 Install Memcached Server - Windows 102

4.11.6 Install Memcached Server - Linux 105

5. How to Install Kony Fabric 107

5.1 How to Install Kony Fabric on Tomcat 107

5.1.1 Installing Console in Tomcat 107

5.1.2 Installing Identity on Tomcat 126

5.1.3 Installing Integration Services on Tomcat 137

5.1.4 Installing Developer Portal on Tomcat 158

5.1.5 Installing Engagement Services on Tomcat 160

5.1.6 How to Configure Kony Fabric on Tomcat Multinode 179

5.2 How to Install Kony Fabric on JBoss 180

5.2.1 Installing Console on JBoss 180

5.2.2 Installing Identity on JBoss 198

5.2.3 Installing Integration Services on JBoss 207

5.2.4 Installing Developer Portal on JBoss 231

5.2.5 Installing Engagement Services on JBoss 233

5.3 How to Install Kony Fabric on WebLogic 257

5.3.1 Installing Console on WebLogic 257

5.3.2 Installing Identity on WebLogic 277

5.3.3 Installing Integration Services on WebLogic 290



5.3.4 Installing Developer Portal on WebLogic 318

5.3.5 Installing Engagement Services on WebLogic 322

5.4 How to Install Kony Fabric on WebSphere 350

5.4.1 Installing Console on WebSphere 351

5.4.2 Installing Identity Services on WebSphere 435

5.4.3 Installing Integration Services on WebSphere 466

5.4.4 Installing Developer Portal on WebSphere 512

5.4.5 Installing Engagement Services on WebSphere 526

6. Installing Kony Fabric on IBM AIX 572

6.1 Prerequisites 572

6.2 Download Kony Fabric installers for AIX platform 572

6.3 Installing Kony Fabric on IBM AIX 573

6.4 Post Installation 573

6.5 Upgrading Kony Fabric 574

7. How to Stop and Start Kony Fabric 576

7.1 Tomcat Server 576

7.1.1 Windows - To stop and start Tomcat Server 576

7.1.2 Linux - To stop and start Tomcat Server 576

7.2 JBoss Server 576

7.2.1 Windows - To stop and start JBoss Server 576

7.2.2 Linux - To stop and start JBoss Server 577



7.3 WebLogic Server 577

7.3.1 Windows - To stop and start WebLogic Server 577

7.3.2 Linux - To stop and start WebLogic Server 577

7.4 WebSphere Server 577

7.4.1 Windows - To stop and start WebSphere Server 578

7.4.2 Linux - To stop and start WebSphere Server 578

8. How to Log in to Kony Fabric Console 579

9. Upgrading Kony Fabric Manually 582

9.1 Upgrading Integration Services 582

9.2 Upgrading Engagement Services 582

10. Post-Installation Tasks 583

10.1 Configuring Secure Sockets Layer (SSL) Certificate 583

10.1.1 How to Add an Installer Generated Self-Signed SSL Certificate to Cacerts 583

10.1.2 How to Add an Existing SSL Certificate to Cacerts 584

10.2 JDK Version Compatibility 585

10.3 How to Switch between JDK Versions 586

10.4 How to Change Default Artifact Size in Workspace - DB2 586

10.5 Configure Deployment of mbaasportal.war File for Multi-Node - JBoss 587

10.6 Log Locations for Kony Fabric 587

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

Domain Mode 589



10.8 Steps to enable SAPJCo 590

10.8.1 Steps for Tomcat 590

10.8.2 Steps for JBoss 591

10.8.3 Steps for Weblogic 592

10.8.4 Steps for Websphere 593

10.9 Setting Custom -D Parameters 593

10.10 How to change the Hostname and Port 593

11. FAQs and Troubleshooting 595

11.1 Hostname/Port changes for Tomcat Application Server 603

11.2 How to Configure JBoss Cluster 603

11.3 How to Configure a Custom JAR File on WebLogic 604

11.4 How to Configure Kony Fabric Behind a Reverse Proxy 604

11.5 Preserving Proxy if Load Balancer or Proxy Server is Configured 607

11.6 How to Configure Frontend HTTPS to Tomcat HTTP Redirection 607

11.7 WebSphere FAQs 608

11.8 How to Change Log Levels 608

11.9 How to Change Log Levels 608

11.10 Context Root-path 611

11.10.1 Approach 1: Changing Context Root Path after the installation using the Installer 612

11.10.2 Approach 2: Changing Context Root using Manual Install Steps 620



11.10.3 Accessing Context Based Root Kony Fabric Instance through Visualizer

Enterprise 631


1. Preface Manual Install GuideVersion1.5

1. Preface

Kony Fabric is a Mobile Backend 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 native mobile 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 has multiple 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 Kony Fabric Integration Services

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 that grants access to your

application. Kony Fabric supports the following authentication services: Microsoft Active

Directory, Salesforce, Security Assertion Markup Language (SAML), Kony SAP Gateway,

Facebook, and Kony User 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:

o Composite: You can run two or more services concurrently or sequentially.

o Looping: You can run a single service in a loop until the loop ends or an exit criteria is met.

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

services for your application.



Important: Kony recommends using the Kony Fabric (MobileFabric) Installer for deploying

MobileFabric 7.0 onwards.

If you are required to install Kony Fabric manually due to your business rules and policies, please

contact [email protected] for approval and to obtain access to the Kony Fabric manual install

artifacts. Manual installs not approved by Kony will not be supported.

1.1 Purpose

This document helps you install and configure Kony Fabric manually.

1.2 Intended Audience

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

configuring Kony Fabric. It is assumed that the reader of this document is familiar with installing

applications in a Windows or Linux environment, and deploying software on Java application servers

and installing database software.

1.3 Formatting Conventions

The following formatting conventions are used throughout the document:

Convention Explanation

Monospace n User input text, system prompts, and responses

n File path

n Commands

n Program code

n File names


mailto:[email protected]?subject=Request to obtain access to the MobileFabric manual install artifacts.


Convention Explanation

Italic n Emphasis

n Names of books and documents

n New terminology

Bold n Windows

n Menus

n Buttons

n Icons

n Fields

n 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 Fabric

User Guide

This guide helps you understand how to create a Kony Fabric account, add

services, and publish apps.



1.5 Contact Us

We welcome 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. Kony Fabric Topology and Components Manual Install GuideVersion1.5

2. 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 apps with services, and publish them to a developer environment. After

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

environment. Authorized users can access apps on mobile devices from a production environment.

Note: From Kony Fabric V8 SP4 release Sync Services have been deprecated.

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.

Environments

(Engagement

Services,

Integration

Service)

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 using metrics

module. This is an optional component.

For more details, refer to Integration Service - App Services User Guide

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

receives a request from a mobile 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.


https://docs.kony.com/konylibrary/integration/kmf_integrationservice_admin_console_userguide/Default.htm



Services Services component is used only when Kony Fabric is integrated. It has

same runtime capabilities as the middleware.

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

the middleware.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:

l Install All Components on one node.

l Install Kony Fabric Console, Kony Identity Service, and Kony Integration Service on

separate nodes.


3. Kony Fabric Installation on Single Node and Multinode Manual Install GuideVersion1.5

3. Kony Fabric Installation on Single Node and Multinode

You can install Kony Fabric in a domain mode (multinode) or a standalone mode (single node) on a

local environment.

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

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

Engagement Services


4. Prerequisites Manual Install GuideVersion1.5

4. Prerequisites

Before you install Kony Fabric, you must perform the following pre-installation tasks:

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

l Windows Server 2012 R2 is recommended if you are installing on Windows environment.

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

use.

l To install in domain mode, the JBoss cluster should be pre-configured.

l MySQL 5.6/5.7, Oracle 12c (12.1.0), MS SQL Server 2012/2014/2016, or IBM DB2

9.7/10.1/10.5 database should be accessible.

Before you install Kony Fabric, you must perform the following pre-installation tasks:

l Software Requirements

l Hardware Requirements

l Hardware Requirements - Console, Identity, and Integration Services

l Hardware Requirements - Engagement Services

l Database System Requirements - Engagement Services

l Corporate Firewall Settings - Engagement Services

l Proxy Settings for Integration Service

l Database Prerequisites

l Required Setup Files

l Encrypt Passwords

l Kony Fabric Installation on Single Node and Multi-node



l Pre-installation Tasks - App Servers

l Configuring Installation Modes - App Servers

4.1 Software Requirements

For software system requirements, refer to Kony Fabric > Software Requirements

4.2 Hardware Requirements - Console, Identity, and Integration Ser-

vices

Component Requirement

Processor Quad-core processor

Memory 16 GB

Internal Storage 150 GB

Network 100 Mbps Ethernet interface card

4.3 Hardware Requirements - Engagement Services


Processor Quadra Core 2.2 MHz

memory 16 GB

Internal Storage 146 GB (15K RPM) with 2 Drives (Raid 1)


https://docs.kony.com/konylibrary/general/konyfabric_supported_devices_os_browsers/Default.htm#Introduction.htm



Network 2 Gigabit Ethernet Ports

IP Configuration Statically assigned IP addressing

Operating System Windows 7 / 8 64 bit

4.4 Database System Requirements (per physical instance) - Engage-

ment Services


Processor Dual Core

Processor

memory 16 GB

Internal Storage 73 GB (15K

RPM) with 4

Drives (Raid

5)

External Storage 200 GB (RAID

5 + HS) SAN

Storage with

HA Fiber HBA

Connection

Network 2 Gigabit

Ethernet Ports

Operating System Windows

Server 2008



4.4.1 Corporate Firewall Settings - Engagement Services

The following firewall settings need to be configured for successful Kony Fabric Engagement Services

installation.

Source Destination Ports Protocol Direction

Action

Description

Engag

ement

Server

https://fcm.googleapis.c

om

443 TCP Outb

ound

Al

lo

w

Allow

the

Engag

ement

Server

to

access

Fireba

se

Cloud

Messa

ging

(FCM)

service

Engag

ement

Server

feedback.push.apple.co

m,

feedback.sandbox.push

.apple.com, 17.0.0.0/8

(17.0.0.1 to

17.255.255.254)

2196 TCP Outb

ound

Al

lo

w

Allow

the

Engag

ement

Server

to

access

APNS

feedba

ck

service




Action

Description

Engag

ement

Server

gateway.push.apple.co

m,

gateway.sandbox.push.

apple.com, 17.0.0.0/8

(17.0.0.1 to

17.255.255.254)

2195 TCP Outb

ound

Al

lo

w

Allow

the

Engag

ement

Server

to

access

Apple'

s

APNS

feedba

ck

service

Engag

ement

Server

All subdomains of

pushapi.eval.blackberry

.com Sample Push

URL:

https://cpxxxxxxxxxxxx

xxxxxxxxxx.

pushapi.eval.blackberry

.co m/mss/PD_

pushRequest

443 TCP Outb

ound

Al

lo

w

Allow

conne

ct to

Blackb

erry

Cloud

throug

h this

port




Action

Description

Engag

ement

Server

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

ound

Al

lo

w

Allow

conne

ct to

Windo

ws

Cloud

(MPN

S)

throug

h this

port

Engag

ement

Server

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

ound

Al

lo

w

Allow

conne

ct to

Windo

ws

Cloud

(WNS)

throug

h this

port




Action

Description

Interna

l

Corpor

ate

WiFi

router

for

Androi

d

Mobile

Device

s

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/AS151

69

5228,

5229,

5230

TCP, HTTP,

HTTPS,

UDP

Both Al

lo

w

Androi

d

device

s will

conne

ct to

GCM

throug

h this

port

Interna

l

Corpor

ate

WiFi

router

for iOS

Device

s

gateway.push.apple.co

m,

feedback.push.apple.co

m,

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 Al

lo

w

Apple

device

s

conne

ct to

APNS

server

s

throug

h this

port


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



Action

Description

Interna

l

Corpor

ate

WiFi

router

for iOS

Device

s

ax.init.itunes.apple.co

m, ocsp.apple.com

80,

443

TCP Both Al

lo

w

Apple

device

s will

conne

ct to

public

Apple

OCSP

and

iTunes

service

throug

h this

port

Interna

l

Corpor

ate

WiFi

router

for

Windo

w

Device

s

Add the list IPs

specified in the following

WNS URL

http://www.microsoft.co

m/en-

us/download/details.asp

x?id=44238

TCP,HTTP,

HTTPS,

UDP

Both Al

lo

w

Windo

ws

device

s will

conne

ct to

WNS

throug

h this

port


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



Action

Description

Interna

l

Corpor

ate

WiFi

router

for

Windo

w

Device

s

Add the list IPs

specified in the following

MPNS URL:

https://www.microsoft.c

om/en-

us/download/details.asp

x?id=44535

TCP,HTTP,

HTTPS,

UDP

Both Al

lo

w

Windo

ws

device

s will

conne

ct to

MPNS

throug

h this

port

APNS works only with SOCKS proxy type. It is because of the current technical limitation from Apple

to communicate the below push notification ports when a proxy server is in place between Kony Fabric

Engagement server and the firewall.

l TCP port 2195 (used to send notifications to the APNs)

l TCP port 2196 (used by the APNs feedback service)

Alternatively, as a workaround, to communicate with the above ports, the system on which the Kony

Fabric Engagement server is installed should bypass the proxies and communicate with the firewall

directly.

4.5 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:

l Dkony.http.proxyHost= 10.0.4.29

l Dkony.http.proxyPort= 2080


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


l Dkony.http.proxyUser= websphere

l Dkony.http.proxyPassword= 3MqGU9e5nv3B

4.5.0.1 Installation Note

The domain/server/configuration names mentioned in this document are used for the convenience of

this document. You may use any name suitable for your installation needs.

Make sure that each resource type within a domain must have a name and a JNDI name that is unique

for all configuration objects in the domain. Within a domain, each server, machine, cluster, and JDBC

connection pool, and any other resource type must be named uniquely and must not use the same

name as the domain. Therefore, the name you provide for the Managed Server, Cluster or any other

resource should be unique in that domain.



4.6 Database Prerequisites

4.6.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 database must 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.

Note: Ensure that these grants are required for all the schemas/tables of all Kony Fabric

components.

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 the Oracle 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 database user with default tablespaces (MF_DATA) and grant quota to two other tablespaces

(MF_INDEX and MF_LOB_DATA tablespaces).

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

o Before you create a user, first, you should identify the default temporary tablespace value

for your database. Run the following query.

SQL> SELECT PROPERTY_VALUE FROM DATABASE_PROPERTIES

WHERE PROPERTY_NAME = 'DEFAULT_TEMP_TABLESPACE';

PROPERTY_VALUE

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

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

TEMPTS

For example, the output of the above query is TEMPTS, and this value should be passed to

the following placeholder.

Important: The default temporary tablespace value is required while creating users

with PDB in Oracle database.



CREATE USER IDENTIFIED BY DEFAULT

TABLESPACE MF_DATA TEMPORARY TABLESPACE 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 TABLE, CREATE VIEW, CREATE SEQUENCE, CREATE TRIGGER, CREATE

PROCEDURE, CREATE TYPE, CREATE JOB,

CREATE USER, ALTER USER,

CREATE SESSION, ALTER SESSION,

CREATE TABLESPACE, ALTER TABLESPACE,

CREATE ANY TABLE, SELECT ANY TABLE, ALTER ANY TABLE, INSERT ANY

TABLE, LOCK ANY TABLE, DELETE ANY TABLE, UPDATE ANY TABLE, DROP

ANY TABLE,

CREATE ANY INDEX, ALTER ANY INDEX, DROP ANY INDEX,

CREATE ANY SEQUENCE, SELECT ANY SEQUENCE, DROP ANY SEQUENCE,

CREATE ANY VIEW, DROP ANY VIEW,

CREATE ANY PROCEDURE, EXECUTE ANY PROCEDURE, DROP ANY PROCEDURE,

CREATE ANY TYPE, DROP ANY TYPE,

CREATE ANY TRIGGER, DROP ANY TRIGGER,

MANAGE SCHEDULER, CREATE ANY JOB

n To create a user based on your Oracle 12c with PDB, then create a local user inside PDB,

which will be used in the Java Database Connectivity (JDBC) authentication.

o Before you create a user, first, you should identify the default temporary tablespace value

for your database. Run the following query.

SQL> SELECT PROPERTY_VALUE FROM DATABASE_PROPERTIES

WHERE PROPERTY_NAME = 'DEFAULT_TEMP_TABLESPACE';

PROPERTY_VALUE



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

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

TEMPTS

For example, the output of the above query is TEMPTS, and this value should be passed to

the following placeholder.

Important: The default temporary tablespace value is required while creating users

without PDB in Oracle database.

Alter session set container = PDB ;

CREATE USER IDENTIFIED BY

DEFAULT TABLESPACE MF_DATA TEMPORARY TABLESPACE

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 TABLE, CREATE VIEW, CREATE SEQUENCE, CREATE TRIGGER, CREATE

PROCEDURE, CREATE TYPE, CREATE JOB,

CREATE USER, ALTER USER,

CREATE SESSION, ALTER SESSION,

CREATE TABLESPACE, ALTER TABLESPACE,

CREATE ANY TABLE, SELECT ANY TABLE, ALTER ANY TABLE, INSERT ANY

TABLE, LOCK ANY TABLE, DELETE ANY TABLE, UPDATE ANY TABLE, DROP

ANY TABLE,

CREATE ANY INDEX, ALTER ANY INDEX, DROP ANY INDEX,

CREATE ANY SEQUENCE, SELECT ANY SEQUENCE, DROP ANY SEQUENCE,



CREATE ANY VIEW, DROP ANY VIEW,

CREATE ANY PROCEDURE, EXECUTE ANY PROCEDURE, DROP ANY PROCEDURE,

CREATE ANY TYPE, DROP ANY TYPE,

CREATE ANY TRIGGER, DROP ANY TRIGGER,

MANAGE SCHEDULER, CREATE ANY JOB

l If you are using the Kony Fabric installer to set up the 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 or pdbmfdb

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 use ORACLE_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

4.6.2 Prerequisites for Kony Fabric with MSSQL- Applicable for Engagement Ser-

vices

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.



4.6.3 Prerequisites for Kony Fabric with MySQL

4.6.3.1 Applicable for Engagement Services

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

Also ensure that modify 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 the MySQL 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/ |

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

4.6.3.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, you may

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

database.

For more information, refer MySQL Bugs

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 FROM clause

l Location:

To resolve this error, run the following commands in the MySQL Server:

1. Execute the following command before running the installer:

SET GLOBAL optimizer_switch = 'derived_merge=off';

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

SET GLOBAL optimizer_switch = 'derived_merge=on';


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


4.6.4 Prerequisites for Kony Fabric with DB2

For IBM DB2, while creating a 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 to modify the page size

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

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

details are provided int the 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 a database with default tablespace with particular

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

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

big pagesize of 32k.

Database collation has to be set for database. This is possible while creating a database needed for Kony Fabric

Engagement Services with UTF-8 code set. The UTF-8 code set is applicable for Engagement Services only.

-- 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, you must verify the following settings:

db2set DB2_COMPATIBILITY_VECTOR=ORA

db2set DB2_DEFERRED_PREPARE_SEMANTICS=YES



SQL files paths for Kony Accounts DB in KonyFabric_Plugins folder:

Path for SQL files in the KonyFabric_Plugins folder Database Component

\KonyFabric_Plugins\scripts\accountsdbmigration MySQL Accounts

\KonyFabric_Plugins\scripts\migrations-accounts-oracle Oracle Accounts

\KonyFabric_Plugins\scripts\migrations-accounts-sqlserver SQL

Server

Accounts

\KonyFabric_Plugins\scripts\migrations-accounts-db2 DB2 Accounts

4.6.5 Increase innodb_log_file_size in my.ini file (For Engagement Services)

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

occurs. Ensure the variable max_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 to Set 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

from Kony Visualizer of 2048-Kilobytes(2 MB) an error appears while publishing. Increase

the size of server database to a value more 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 =

Note: When uploading larger files will get an error Packets larger than max_allowed_

packet are not allowed.

4.6.6 Prerequisites for Kony Fabric with MariaDB

4.6.6.1 Increase the table_definition_cache and table_open_cache values

To increase the values of table_definition_cache and table_open_cache in Maria DB, 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



4.7 Required Setup Files

Download KonyFabric_Plugins (WAR files and DB scripts).

If you want to install Kony Fabric manually due to your business rules and policies, please contact

[email protected] for approval and to obtain access to the Kony Fabric manual install

artifacts. Manual installs not approved by Kony will not be supported.

4.7.1 Required Setup Files - Kony Fabric Console, Accounts, and Workspace

Path for WAR Files: \KonyFabric_Plugins\war

Files Types File Name Location

WAR mbaasportal.war \KonyFabric_Plugins\war

accountsAPI.war \KonyFabric_Plugins\war

workspaceService.war \KonyFabric_Plugins\war

DB Scripts

and

Migrations

Scripts for

Kony

Workspace

Service

l waasdbmigrations.zip

l migrations-waas-oracle.zip

l migrations-waas-db2.zip

l migrations-waas-sqlserver.zip

\KonyFabric_Plugins\scripts

DB Scripts

and

Migrations

Scripts for

Kony

Accounts

Service

l accountsdbmigration.zip

l migrations-accounts-db2.zip

l migrations-accounts-oracle.zip

l migrations-accounts-sqlserver.zip



mailto:[email protected]


4.7.2 Required Setup Files - Identity Services

Files Types

File Name Location

WAR authService.war \KonyFabric_Plugins\war

DB

Scripts

and

Migratio

ns

Scripts

for Kony

Identity

Service

l migrations.jar

o KonyFabric_

Plugins\scripts\javamigrations-

auth\com\kony\auth\migrations\db2

o KonyFabric_


auth\com\kony\auth\migrations\mys

ql\

o KonyFabric_


auth\com\kony\auth\migrations\orac

le

o KonyFabric_


auth\com\kony\auth\migrations\sqls

erver

\KonyFabric_

Plugins\scripts\javamigratio

ns-auth

4.7.3 Required Setup Files - Integration Services

Path for WAR files: \KonyFabric_Plugins\middleware




WAR middleware.war \KonyFabric_Plugins\middleware

services.war

admin.war

apps.war

DB Scripts

and

Migrations

Scripts for

Kony

Integration

Services

l install.zip

l admindb_db2.zip

l admindb_mysql.zip

l admindb_oracle.zip

l admindb_sqlserver.zip

l reportsdb_db2.zip

l reportsdb_mssql.zip

l reportsdb_mysql.zip

l reportsdb_oracle.zip

\KonyFabric_Plugins\middleware

4.7.4 Required Setup Files - Engagement Services

The kms-x.x.x.x files are downloaded in a zip format. Kony provides the following files for Kony Fabric

Engagement Services:

Path for KMS files: \KonyFabric_Plugins\kpns




WAR kpns.war \KonyFabric_Plugins\kpns

DB Scripts

and

Migrations

Scripts

l mssql-kpns-migrations.zip

l mysql-kpns-migrations.zip

l oracle-kpns-migrations.zip

l db2-kpns-migrations.zip


Resources,

JARs, TARs

l sharedlib.tar

l kpns-resources.zip

\KonyFabric_Plugins\kpns

l kpns.war file that is deployed on the application server.

l WebSphere 8x file

l kpns-resources.tar- An extracted kpns-resources.tar archive contains the

following files:

o schema - This folder contains the XML schema definitions for subscription and

messaging.

o configResource.properties - An XML file containing the configuration

properties.

o kms-log4j2.properties - This file is used to control the application logging.

o database.properties - This file is used to control the security of the application

and for User Management configuration.

l Database scripts - There are folders for the following database scripts for creating and dropping

the schema.



Database Script File Name

MySQL mysql.tar

Oracle oracle.tar

Microsoft SQL sqlserver.tar

DB2 db2.tar

Copy configResource.properties, database.properties and kms-

log4j2.properties to /data/kpns-config folder.

4.7.5 Database JARs

Download the following jars required for your database.

Database JARs

DB2 l db2jcc4.jar (Downloaded from IBM,

minimum version 4.19.26)

l db2jcc4_license_cu.jar

l db2jcc4_license_cisuz.jar

MySQL l mysql-connector-java-5.1.44.jar

Oracle l ojdbc6_g.jar

MS SQL l mssql-jdbc-7.0.0.jre8


http://www-01.ibm.com/support/docview.wss?uid=swg21363866


4.8 Encrypt Passwords

To encrypt a value, follow these steps:

1. Create a Java class.

2. Add konyserver-utils.jar to your class path.

Path for konyserver-utils.jar: /KonyFabric_

Plugins/middleware/konyserver-utils.jar

3. Call the method EncryptDecryptText.encryptText().

This will return encrypted value.

Important: Ensure that you encrypt the following placeholder values for Admin before

executing Flyway migration.

For Admin:

- KONY_SERVER_TRUSTSTORE_PASSWORD

- KONY_SERVER_STORAGE_DATABASE_PASSWORD

4. Add dependency jars to the Library.

l commons-io-2.4.jar can be found at

https://mvnrepository.com/artifact/commons-io/commons-io/2.4

l log4j-api-2.8.2.jar can be found at

https://mvnrepository.com/artifact/org.apache.logging.log4j/log4j-api/2.8.2

To encrypt a Tomcat value, follow these steps:


https://mvnrepository.com/artifact/commons-io/commons-io/2.4https://mvnrepository.com/artifact/org.apache.logging.log4j/log4j-api/2.8.2


1. Create a Java class.

2. Add serverdeployer.jar to your class path.

Path for konyserver-utils.jar: /KonyFabric_

Plugins/middleware/serverdeployer.jar

3. Call the method CryptoUtils.encrypt(. This will return

encrypted value.

4. Add/Update the password field of the user in the tomcat-users.xml file, located in the

tomcat_Install_dir/conf folder. Set the role name to manager.

For example:

4.9 Pre-Installation Tasks - Database

4.9.1 Configuring Flyway Command-line Tool

The following section helps you configure placeholders and properties in the flyway.conf file and

execute SQL scripts for your database. The details that are required to configure flyway properties for

a component's database are available in the database sections of an app server in the document.



Note: Before configuring flyway properties for your database, download the Flyway Command-

line Tool from https://flywaydb.org/getstarted/download.html to your local system, and unzip the

flyway-commandline--. You can download

the Flyway Command-line Tool specific to your Operating System. The supported version is

Flyway 4.0.3.

1. Go to the \flyway\conf folder and open the flyway.conf file.

2. Configure your database properties for the current module with relevant data in the

flyway.conf file.

The following is a sample for configuring properties in the flyway.conf file.

# --------

# Most drivers are included out of the box.

# * = driver must be downloaded and installed in /drivers

manually

# DB2* : jdbc:db2://:/

# H2 : jdbc:h2:

# Hsql : jdbc:hsqldb:file:

# Google Cloud SQL* : jdbc:google:mysql://:/

# MariaDB :

jdbc:mariadb://:/?=&

=...

# MySQL :

jdbc:mysql://:/?=&=<

value2>...

# Oracle* :

jdbc:oracle:thin:@//:/

# PostgreSQL :


https://flywaydb.org/getstarted/download.html


jdbc:postgresql://:/?=&=...

# solidDB* :

jdbc:solid://:?=&=...

# SQL Azure* :

jdbc:sqlserver://.database.windows.net;databaseName

=

# SQL Server :

jdbc:jtds:sqlserver://:/

# SQLite : jdbc:sqlite:

# Vertica* : jdbc:vertica://:/

#Flyway URL for MySQL

flyway.url=jdbc:mysql://:

#Flyway URL for MSSQL

flyway.url=jdbcjdbc:sqlserver://:/:currentSchema=;

#Flyway URL for DB2, provide the DB IP and port details, and

schema name for the current module

flyway.url=jdbc:db2://:/:currentSchema=;

# Fully qualified class name of the JDBC driver (autodetected

by default based on flyway.url)

# flyway.driver=

# User to use to connect to the database (default: )

flyway.user=



# Password to use to connect to the database (default:

)

flyway.password=

# Comma-separated list of schemas managed by Flyway. These

schema names are case-sensitive.

# (default: The default schema for the data source connection)

# Consequences:

# - The first schema in the list will be automatically set as

the default one during the migration.

# - The first schema in the list will also be the one

containing the metadata table.

# - The schemas will be cleaned in the order of this list.

flyway.schemas=

Note: For Identity services, the schema name should be

.

# Replace placeholders for Kony Fabric Components

Placeholders for Console: Accounts, Workspace Services

Placeholders for Identity Services

Placeholders for Integration Services: Admin Server, Reports

Placeholders for Engagement Services

Placeholders for mfaccountsdb

Placeholders for mfconsoledb

Placeholders for idconfig

Placeholders for admindb (admindb for Tomcat)

Placeholders for reportsdb (reportsdb for Tomcat)



Placeholders for kpnsdb

3. Save the flyway.conf file.

4. Add your database driver into the Flyway drivers folder. For example, flyway-

4.0.3\drivers.

The following jars are required for your database.

Database JARs

DB2 l db2jcc4.jar (Downloaded from IBM,

minimum version 4.19.26)

l db2jcc4_license_cu.jar

l db2jcc4_license_cisuz.jar

MySQL l mysql-connector-java-5.1.44.jar

Oracle l ojdbc6_g.jar

MS SQL l mssql-jdbc-7.0.0.jre8

5. To execute your database SQL scripts, copy all required database SQL files from Kony

Fabric_Plugins folder and paste them to the Flyway SQL (For example,

C:\flyway\sql or /opt/flyway/sql depending on Windows or Linux) folder of

the Flyway Command-line Tool.


http://www-01.ibm.com/support/docview.wss?uid=swg21363866


6. For only identity services, to execute your database SQL scripts, do the following:

a. Copy the migrations.jar from the KonyFabric_

Plugins\scripts\javamigrations-auth\ folder.

b. Paste the migrations.jar to the C:\flyway\jars\, for example,

C:\flyway\jars\migrations.jar.

c. Go to the \flyway\conf folder and open the flyway.conf file.

d. Add the following database class path: flyway.locations=com.kony.auth.migrations.

7. From the command line, execute the SQL scripts for your database:

l For DB2 or Oracle, execute the SQL scripts with the following Flyway migrate command

along with the following placeholder parameters: _DATA_

TABLESPACE, _INDEX_TABLESPACE, and _LOB_TABLESPACE

Note: While creating databases in DB2 or Oracle, you can provide one name or

separate names for tablespace, index space and lob space. If the same name is

given, that name will need to be passed for all these parameters.

For example, the following is the flyway command to execute SQL scripts for AUTH

(identity services) with separate tablespace names:

flyway migrate -placeholders.AUTH_DATA_

TABLESPACE="TS32K" -placeholders.AUTH_INDEX_

TABLESPACE="IDX32K" -placeholders.AUTH_LOB_

TABLESPACE="LOB32K"

l For MySQL and SQL Server, execute the following Flyway migrate command:

flyway migrate



The SQL files will be executed in the Flyway SQL folder. For example, C:\flyway\sql

or /opt/flyway/sql depending on Windows or Linux, or specific to your storage file

path.

4.10 Preinstallation Tasks - App Servers

The following section explains preinstallation steps required before installing your application server:

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

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

service. The log on as a service privileges is 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 new Windows 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 click OK. 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, click OK. The system

adds the user name in the Local security setting tab.



4.10.2 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, you must download the following bundled encryption policy .jar files and replace them with 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/

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

1. Go to the Oracle Java SE download page http://www.oracle.com/

2. Scroll down to the 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. The UnlimitedJCEPolicyJDK.zip file

contains the following files:

l local_policy.jar

l US_export_policy.jar

l README.txt


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.htmlhttp://www.oracle.com/technetwork/java/javase/downloads/index.html


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 them with 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.

4.10.3 Setting JVM arguments for WebSphere

Before installing Kony Fabric on WebSphere, you must add the following -D parameters and custom

properties in WebSphere:

1. Add the following -D parameter at Application Server -> -> Java and

Process Management -> Process Definition -> Java Virtual Machine -> Generic JVM

arguments.

-Dcom.ibm.websphere.jaxrs.server.DisableIBMJAXRSEngine=true

4.10.4 Setting JVM arguments for Salesforce Services

Configure TLSV1.2 protocol as JVM parameter because Salesforce disabled TLS 1.0 protocol.

Configuring TLS protocol that enables Kony Fabric to work with Salesforce services.



l For WebSphere:

1. In the WebSphere Administration Console, select Servers.

2. Expand Server Type and select WebSphere application servers

3. Click on the name of your server.

4. Expand Java and Process Management and select Process Definition.

5. Under the Additional Properties section, click Java Virtual Machine.

6. In the Generic JVM arguments text box, enter the value: -Dttps.protocols=TLSv1.2

Once changes are made and saved to the master configuration, the JVM requires a

restart for the arguments to take effect.



l For Tomcat:

1. Go to your Tomcat install location and open the \bin folder.

Location for bin folder: \apache-tomcat-

8.5.32\bin

2. Open the catalina.bat file from the bin folder.

Note: For Windows, open the catalina.bat file.

For Linux, open the catalina.sh file.

3. Add the value -Dhttps.protocols=TLSv1.2 to JAVA_OPTS.

4. Save the catalina file. Once changes are made and saved to the master configuration,

the JVM requires a restart for the arguments to take effect.

l For JBoss:

1. Go to your JBoss install location and open the \bin folder.

2. Location for bin folder: \JBossInstallDir>\bin

3. Open the standalone.bat file from the bin folder.

Note: For Windows, open the standalone.bat file.

For Linux, open the standalone.sh file.

4. Add the value -Dhttps.protocols=TLSv1.2 to JAVA_OPTS.

5. Save the standalone file. Once changes are made and saved to the master

configuration, the JVM requires a restart for the arguments to take effect.



l For WebLogic:

1. In the WebLogic Domain Structure pane, expand the Servers node.

2. Click the name of the server that you want to configure.

3. In the right pane, click Server Start.

4. Select Lock & Edit.

5. In the Arguments text box, provide the JVM options.

Once changes are made and saved to the master configuration, the JVM requires a

restart for the arguments to take effect.

4.10.5 Configure Middleware Home

APPLICABLE FOR ALL APPLICATION SERVERS

Extract the middleware_home.zip from the KonyMobileFabric_

Plugins\middleware\middleware_home.zip, and place the unzipped middleware_

home folder in your install directory.



Modify the variables in the following files:

l middleware_home/middleware/middleware-bootconfig/admin/serverconsole.properties

l middleware_home/middleware/middleware-bootconfig/middleware.properties

l middleware_home/middleware/middleware-bootconfig/oscache.properties

l middleware_home/middleware/middleware-bootconfig/admin/deployment-config.properties

4.10.5.1 Set Middleware Home - Tomcat

1. Go to the artifacts you downloaded from Kony. For example, \KonyFabric_Plugins

2. Go to your Tomcat install location and open the conf folder.

Location for conf folder: \TomcatInstallerFolder>\apache-tomcat-

8.5.32-windows-x64\apache-tomcat-8.5.32\conf

3. Open the Catalina.properties file from the conf folder.

4. Set the following path for middleware home property in the Catalina.properties file.

middleware.home=:/InstallerAssests/Manual/Tomca

t/install/middleware_home

5. Go to /middleware_

home/middleware/middleware-bootconfig/admin folder, edit

serverconsole.properties file and make the following changes based on your

database type

#Server Console configuration properties file

###############################################################

##########



#Hibernate Dialect related properties.

###############################################################

##########

#For SQL Server

#konyadmindb.dialect=com.kony.console.admin.dialect.CustomSQLSe

rverDialect

#

#For MySQL

#konyadmindb.dialect=com.kony.console.admin.dialect.CustomMySQL

Dialect

#

#For Oracle thin driver

#konyadmindb.dialect=com.kony.console.admin.dialect.CustomOracl

eDialect

#

#For DB2

#konyadmindb.dialect=com.kony.console.admin.dialect.CustomDB2Di

alect

#

###############################################################

##########

konyadmindb.dialect=com.kony.console.admin.dialect.CustomMySQLD

ialect



###############################################################

##########

#Admin and Report Database JNDI Names

###############################################################

##########

admindb.jndi.name=jdbc/konyadmindb

reportsdb.jndi.name=jdbc/konyreportsdb

###############################################################

##########

#Database Type (mysql/oracle/sqlserver/db2)

###############################################################

##########

admindb.dbtype=mysql

reportsdb.dbtype=mysql

###############################################################

##########

6. In the middleware_home/middleware/middleware-bootconfig folder,

rename the middleware_single.properties file as middleware.properties.

7. In the middleware_home/middleware/middleware-bootconfig/admin

folder, rename the deployment-config_tomcat.properties file as deployment-

config.properties.





deployment-config.properties file and make the following changes

Note: Replace the variables enclosed in $_$ with values based on your configuration.

For example, replace $SERVER_CHOICE$ with TOMCAT.

config.usersdb.validation=false

config.wap-default.type=$SERVER_CHOICE$

config.wap-default.host=$HOST_IP$

config.wap-default.port=$HTTPS_PORT$

config.wap-default.deploy.URL=$COM_PROTOCOL$://$HOST_

IP$:$HTTPS_PORT$/manager/text

config.wap-default.deploy.managerPWD=m@n@g3r123

config.sms-default.type=$SERVER_CHOICE$

config.sms-default.host=$HOST_IP$

config.sms-default.port=$HTTPS_PORT$

config.sms-default.deploy.URL=$COM_PROTOCOL$://$HOST_

IP$:$HTTPS_PORT$/manager

config.sms-default.deploy.managerPWD=m@n@g3r123

config.sms-default.deploy.dir=$USER_INSTALL_DIR$/middleware_



home/apps

config.rc-default.type=$SERVER_CHOICE$

config.rc-default.host=$HOST_IP$

config.rc-default.port=$HTTPS_PORT$

config.rc-default.deploy.dir=$USER_INSTALL_DIR$/middleware_

home/lib/apps

app.store.location=$USER_INSTALL_DIR$/middleware_

home/appstore

4.10.5.2 Set Middleware Home - JBoss


2. Create a lib directory, and inside that create a database directory in your middleware home, For

example, $MIDDLEWARE_HOME\lib\database. Place your respective database

connector jar along with module.xml and its contents in MIDDLEWARE_

HOME\lib\database\.

3. Go to your JBoss install location and open the \bin folder.

Location for bin folder: \JBossInstallDir>\bin

4. Open the standalone.bat file from the bin folder. In case of Linux, standalone.sh



5. Set the JAVA_OPTS variable in the standalone.bat file, shown below:

set "JAVA_OPTS= -server -Xms2048m -Xmx2048m -XX:NewSize=512m -

XX:MaxNewSize=256m -XX:PermSize=512m -XX:MaxPermSize=1024m -

XX:+CMSClassUnloadingEnabled -Djava.awt.headless=true -

Djava.net.preferIPv4Stack=true -

Dsun.rmi.dgc.client.gcInterval=3600000 -

Dsun.rmi.dgc.server.gcInterval=3600000 -XX:+UseConcMarkSweepGC -

XX:+CMSClassUnloadingEnabled -XX:+CMSIncrementalMode -

XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/logs/heapdumps -Dmiddleware.home=-

Dnet.spy.log.LoggerImpl=net.spy.memcached.compat.log.Log4JLogger -

Djboss.as.management.blocking.timeout=1200"


1. Rename the middleware_single.properties file as

middleware.properties for Bundled JBoss.

2. Rename the middleware_remote.properties file as

middleware.properties for Pre-Configured or MultiNode JBoss.

7. In the middleware_home/middleware/middleware-bootconfig/admin

folder, rename the deployment-config_jboss.properties file as deployment-

config.properties.



deployment-config.properties file and make the following changes

Note: Replace the variables enclosed in $_$ with values based on your configuration.

For example, replace $SERVER_CHOICE$ with JBoss.



config.usersdb.validation=false

config.wap-default.type=$SERVER_CHOICE$

config.wap-default.host=$HOST_IP$

config.wap-default.port=$HTTPS_PORT$

#config.wap-default.deploy.URL=__config.wap-

default.deploy.URL__

#config.wap-default.deploy.managerID=manager

#config.wap-default.deploy.managerPWD=m@n@g3r123

#config.wap-default.deploy.dir=$USER_INSTALL_

DIR$/jboss/standalone/deployments

#config.sms-default.type=Tomcat

#config.sms-default.host=localhost

#config.sms-default.port=80

#config.sms-default.deploy.URL=__config.sms-

default.deploy.URL__

#config.sms-default.deploy.dir=__config.sms-

default.deploy.dir__

#config.sms-default.deploy.managerID=manager

#config.sms-default.deploy.managerPWD=m@n@g3r123



config.rc-default.type=$SERVER_CHOICE$

config.rc-default.host=$HOST_IP$

config.rc-default.port=$HTTPS_PORT$

config.rc-default.deploy.dir=$USER_INSTALL_

DIR$/jboss/standalone/deployments

app.store.location=$USER_INSTALL_DIR$/middleware_

home/appstore

9. Go to /KonyMobileFabric_

Plugins/middleware/admin.war/WEB-INF folder, edit the web.xml file and

make the following changes

l Search for , and replace it with " ".

10. Go to /KonyMobileFabric_

Plugins/middleware/admin.war/WEB-INF folder, edit the

applicationContext.xml file and make the following changes

l Search for , and replace it with " ".

Important: For ActiveMQ (If INSTALL_MODE=SINGLE; COMP_SERVER_ENABLED =

true or COMP_ALL_ENABLED=true),



l Expand $IA_PROJECT_DIR$\resources\common\server_files\ActiveMQ_jars.zip.

l Execute ANT $IA_PROJECT_DIR$\resources\common\scripts\add-activemq-jar-

to-integration-wars.xml

l Properties file : $IA_PROJECT_DIR$\resources\common\scripts\create-shared-

libs.properties

Important: For Non-JBoss,

l Expand admin.war into admin_temp, and delete $USER_INSTALL_

DIR$$/$KonyMobileFabric_Plugins$/$middleware$/$admin.war

l Delete the following files:

l $USER_INSTALL_DIR$$/$admin_temp$/$WEB-INF$/$jboss-deployment-

structure.xml

l $USER_INSTALL_DIR$$/$admin_temp$/$WEB-INF$/$jboss-web.xml

l Set the following variables:

l $MODIFIED_WAR_FILE$ = $USER_INSTALL_DIR$$/$KonyMobileFabric_

Plugins$/$middleware$/$admin.war

l $WAR_INPUT_DIR$ = $USER_INSTALL_DIR$$/$admin_temp

l Execute ant

l $IA_PROJECT_DIR$\resources\common\server_files\create-war.xml

l Properties file = $IA_PROJECT_DIR$\resources\common\server_

files\create-war.properties

l Delete admin_temp

Note: Replace all the variables enclosed in $_$ with values based on your inputs.



4.10.5.3 Set Middleware Home - WebLogic



rename the middleware_remote.properties file as middleware.properties.

4.10.5.4 Set Middleware Home - WebSphere



rename the middleware_websphere.properties file as middleware.properties.


home/middleware/middleware-bootconfig, edit the

middleware.properties file and make the following changes:

l Search for metrics.userName=, and replace it with #metrics.userName=.

l Search for metrics.password=, and replace it with #metrics.password=.

l Search for ssl.SocketFactory.provider=sun.security.ssl.SSLSocketFactoryI

mpl, and replace it with ssl.SocketFactory.provider=com.ibm.websphere.ssl.protocol.SSL

SocketFactory.

l Search for ssl.ServerSocketFactory.provider=sun.security.ssl.SSLServerSo

cketFactoryImpl, and replace it with ssl.ServerSocketFactory.provider=com.ibm.websphere.ssl.protoc

ol.SSLServerSocketFactory.



l If $USE_MEMCACHE$ is false, search for memcache.cluster= and replace it with

#memcache.cluster=

4.11 Configuring Installation Modes - App Servers

The following sections explain how to set up your application server:

l Tomcat

l JBoss

l WebLogic

l WebSphere

4.11.1 How to Install Tomcat Server

Note: By default Tomcat manager password in used by Kony Fabric for Web Application publish.

To change the default Tomcat manager password, the new password needs to be replaced in the

password value for user manager in tag in tomcat-users.xml.

Now to replace the value in database, the password value should be encrypted. To encrypt the

database password, follow these steps mentioned in the Encrypt Passwords section.

Once the password is encrypted, replace the encrypted value in the prop_value column in the

row where prop_value is management_server_password of

admindb database in the server_

configuration table.

To download and install Tomcat, follow these steps:



1. Download Apache Tomcat v8.5.32 from the following link.

https://archive.apache.org/dist/tomcat/tomcat-8/v8.5.32/bin/

2. Install the apache-tomcat-8.5.32-windows-x64.exe (Windows) or extract the

apache-tomcat-8.5.32.tar.gz (Linux) file and place it in your local folder. Your

Tomcat Server setup is ready now.

Important: Examples in this document refer the as your install

folder. Ensure that you plac