kony fabric installation guide â€“ windows

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

copy 2020 by Kony Inc All rights reserved 1 of 393

Kony Fabric Installation Guide - WindowsVersion112

Copyright copy 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 SAPreg and SAPreg Business Suitereg 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 ModificationsRelease

01262020 112 Document published for adding Upgrading Custom

Metrics Component

10182019 111 Document published for adding Upgrade from Kony

Fabric 82

09262019 110 Document published for adding Prerequisites for

Upgrade fromMobileFabric 7x to Kony Fabric 8x

08052019 19 Document published after modifying the -DKMS_

CORE_VERSION for JBoss WebLogic and

WebSphere

08052019 18 Document published after modifying Application

Servers Pre-installation Tasks for JBoss WebLogic

andWebSphere

06202019 17 Document published after modifying Corporate Firewall

Settings - Engagement Services

04182019 16 Document Published for V8 SP4 FP1HF1

02272019 15 Document Published for V8 SP4 FP1

09242018 14 Document Published for V8 SP3



09192017 10 Document Published for V8GA





Table of Contents

1 Preface 13

11 Purpose 14

12 Intended Audience 14

13 Formatting ConventionsUsed in ThisGuide 15

14 Related Documents 16

15 Contact Us 16

2 Prerequisites 17

21 Software Requirements 17

22 Hardware Requirements 17

23 Network Settings 18

231 Corporate Firewall Settings - Engagement Services 18

232 Proxy Settings for Integration Service 21

233 Network Settings - Licensing 22

24 Database Prerequisites 23

241 Prerequisites for Kony Fabric with Oracle 23

242 Prerequisites for Kony Fabric with DB2 25

243 Prerequisites for Kony Fabric with SQL Server 27

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

245 Prerequisites for Kony Fabric with MySQL 29

2451 Applicable for Engagement Services 29



2452 Applicable for Identity Services 30

25 Application Servers Prerequisites 31

251 Tomcat Prerequisites 31

2511 How to DisableWeakCiphers 31

2512 Heap and PermGen Settings 32

252 JBoss Prerequisites 32


2522 Configuration of Database Driver Module 32

2523 Configure the Standalone Existing JBoss 33

2524 Configure the Log Locations - JBoss 35

2525 Configure the Standalone Existing JBosswith Self-Signed Certificate (JBoss 71) 35

2526 Configure Port Settings for Multinode Loadbalancer Setups 36

253 WebLogic Prerequisites 37


2532 Security Configurations 37

2533 Configure the Log Locations - WebLogic 37

254 WebSphere Prerequisites 38


2542 How to Enable TLSv12 Protocol 38

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

TLS v12 40



2544 SOAP Connector Port details for WebSphere 42

2545 Updating the SSL Socket Factory Providers 45

2546 NGINX Load Balancer Configuration 45

3 Kony Fabric Topology and Components 47

31 Developer Environment 52

32 Production Environment 53

4 Kony Fabric Installation on Single Node and Multinode 54

5 Pre-Installation Tasks 55

51 Download Kony Fabric Installer 55

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

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

54 Install Memcached Server 59

55 Configure Load Balancers for Sending Host Information inMultinode 61

5501 Configure Hibernate Dialect inWebLogic (only for WebLogic) 62

56 Download and Install the Unrestricted JCE Policy Files 62

57 Database Pre-Installation Tasks 64

571 MySQL 64

5711 Increase innodb_log_file_size in myini file - MySQL 64

572 SQL Server 64

573 WindowsAuthentication Support 64

574 Oracle 65



5741 Create Locator Component for Oracle Database 65

575 MariaDB 67

5751 Increase the table_definition_cache and table_open_cache values 67

58 Application Servers Pre-Installation Tasks 68

581 JBoss 68

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

Offloading at Load Balancer) 68

5812 Update Listen Interfaces in hostxml for JBossCluster 68

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

JBossCluster 69

5814 How to Configure Connector - JBoss 70

5815 How to Increase Timeout andMaximumHeap Size Settings - JBoss 70

5816 How to Configure Engagement Services - JBoss 71

582 WebLogic 72

5821 Increase JVMmemory for WebLogic Server 72

5822 PlaceMS SQLServer Connector JAR inWebLogic Classpath 72

5823 How to Configure Engagement Services - WebLogic 72

583 WebSphere 73

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

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

5833 Support Deployment of apiportalwar onWebSphere Server 75

5834 Updating authServicewar and accountswar for WebSphere 9 75



5835 How to Configure Engagement Services - WebSphere 76

6 Installation Modes - Kony Fabric 77

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

611 Installing Kony Fabric on Tomcat 78

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

6121 Installing Kony Fabric on a StandaloneMode in Bundled JBoss 117

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

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

configured JBoss cluster) 184

613 Installing Kony Fabric onWebLogic 218

614 Installing Kony Fabric onWebSphere 252

62 Installing Kony Fabric - Silent-mode 287

7 How to Stop and Start Kony Fabric 289

71 Tomcat Server 289

72 JBoss Server 289

721 For Multinode - JBoss 289

73 WebLogic Server 289

74 WebSphere Server 290

741 Windows - To stop and start WebSphere Server 290

8 Upgrading Kony Fabric 291

81 Prerequisites for Upgrade fromMobileFabric 7x to Kony Fabric 8x 291



82 Upgrading Kony Fabric using installer 293

83 Prerequisites 294

84 Upgrading Kony Fabric to V8 SP4 304


85 Upgrade fromKony Fabric V8 SP2 to V8 SP4 313

86 Upgrading CustomMetrics Component 314

9 Installing Hot Fix Archives for Kony Fabric - Windows 316

91 Patch Installer GA Versions 316


10 Uninstalling Kony Fabric 324

11 Post-Installation Tasks 330

111 Configuring Secure Sockets Layer (SSL) Certificate 330

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

1112 How to Add an Existing SSLCertificate to Cacerts 331

112 JDK Version Compatibility 332

113 How to Update Security Configuration in Configxml (Required in case ofWebLogic

installation) 333

114 How to ConfigureMemcache for Integration Services 334

115 Configure Deployment of mbaasportalwar File for Multi-Node 336

116 Remote Installation Pre-requisites 336

1161 Installing Kony Fabric Remotely 336



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

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

DomainMode 337

119 Health CheckURL 338

1110 Steps to enable SAPJCo 339

11101 Steps for Tomcat 339

11102 Steps for JBoss 340

111021 JBoss - Standalone (Bundled) 340

111022 JBoss - Standalone(Pre-configured)Domainmode 340

11103 Steps for Weblogic 341

11104 Steps for Websphere 342

12 FAQs and Troubleshooting 343

121 HostnamePort changes for Tomcat Application Server 362

122 HostnamePort changes for JBoss Application Server 362

123 How to Configure JBossCluster 363

124 How to Configure a Custom JAR File onWebLogic 363

125 How to Configure Heap and PermGen Size 364

1251 Configuring Heap and PermGen Size for Tomcat 364

1252 Configuring Heap and PermGen Size for JBoss 364

1253 Configuring Heap and PermGen Size for WebLogic 365

1254 Configuring Heap and PermGen Size for WebSphere 365



126 How to Configure Kony Fabric Behind a Reverse Proxy 365

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

128 How to Configure Frontend HTTPS to Tomcat HTTP Redirection 368

129 WebSphere FAQs 368

1210 How to Change Log Levels 368

1211 Context Root-path 371

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

12112 Approach 2 Changing Context Root usingManual Install Steps 380

12113 Accessing Context Based Root Kony Fabric Instance through Visualizer

Enterprise 392


1 Preface Kony Fabric Installation Guide - WindowsVersion112

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 20 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 Nodejs 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

11 Purpose

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

12 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



13 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

NoteProvides helpful hints or additional information




ImportantHighlights actions or information that might cause problems to

systems or data

14 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

15 Contact Us

Wewelcome your feedback on our documentation Email us at techpubskonycom

For technical questions suggestions and comments or to report problems on Konys product line

contact supportkonycom


2 Prerequisites Kony Fabric Installation Guide - WindowsVersion112

2 Prerequisites

The following sections explain the software and hardware required to install Kony Fabric Console

21 Software Requirements

For software system requirements click here

22 Hardware Requirements

Component Requirement

Processor Quad-core processor

Memory 16GB

Internal Storage 150GB

Network 100Mbps Ethernet interface card



23 Network Settings

231 Corporate Firewall Settings - Engagement Services

Source Destination Ports Protocol

Direction

Action

Description

Engage

ment

Server

httpsapipushapplecom4433device 443 TCP Both Allow Allow the

Engagem

ent Server

to access

Apple

APNS

HTTP2

production

URL

Engage

ment

Server

httpsapijpushcnv3push 443 TCP Outbou

nd

Allow Allow the

Engagem

ent Server

to access

the JPush

notificatio

n server

URL

Engage

ment

Server

httpsapidevelopmentpushapplecom

4433device

443 TCP Both Allow Allow the

Engagem

ent Server

to access

Apple

APNS

HTTP2

developm

ent URL




Direction

Action

Description

Engage

ment

Server

httpsfcmgoogleapiscom 443 TCP Outbou

nd

Allow Allow the

Engagem

ent Server

to access

Firebase

Cloud

Messagin

g (FCM)

service

Engage

ment

Server

feedbackpushapplecom

feedbacksandboxpushapplecom

170008 (17001 to 17255255254)

2196 TCP Outbou

nd

Allow Allow the

Engagem

ent Server

to access

APNS

feedback

service

Engage

ment

Server

gatewaypushapplecom

gatewaysandboxpushapplecom

170008 (17001 to 17255255254)

2195 TCP Outbou

nd

Allow Allow the

Engagem

ent Server

to access

Apples

APNS

Engage

ment

Server

All subdomains of

pushapievalblackberrycom Sample

Push URL

httpscpxxxxxxxxxxxxxxxxxxxxxx

pushapievalblackberrycommssPD_

pushRequest

443 TCP Outbou

nd

Allow Allow

connect to

Blackberr

y Cloud

through

this port




Direction

Action

Description

Engage

ment

Server

httpsn1notifylivenet 443 TCP Outbou

nd

Allow Allow

connect to

Windows

Cloud

(MPNS)

through

this port

Engage

ment

Server

httpsloginlivecom 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 Googles ASN of

15169 Reference link for the IP

Addresses httpbgphenetAS15169

5228

52295

230

TCP

HTTP

HTTP

S

UDP

Both Allow Android

devices

will

connect to

GCM

through

this port

Internal

Corporat

eWiFi

router for

iOS

Devices

gatewaypushapplecom




170008 (17001 to 17255255254)

5223 TCP Both Allow Apple

devices

connect to

APNS

servers

through

this port




Direction

Action

Description

Internal

Corporat

eWiFi

router for

iOS

Devices

axinititunesapplecom ocspapplecom 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 httpwwwmicrosoftcomen-

usdownloaddetailsaspxid=44238

TCP

HTTP

HTTP

S

UDP

Both Allow Windows

devices

will

connect to

WNS

through

this port

Internal

Corporat

eWiFi

router for

Window

Devices


MPNS URL

httpswwwmicrosoftcomen-


TCP

HTTP

HTTP

S

UDP

Both Allow Windows

devices

will

connect to

MPNS

through

this port

232 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 DkonyhttpproxyHost= 100429

l DkonyhttpproxyPort= 2080

l DkonyhttpproxyUser= websphere

l DkonyhttpproxyPassword= 3MqGU9e5nv3B

233 Network Settings - Licensing

The on-premises server should allow outbound requests to httpsmanagekonycom and allow

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

customerrsquos 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

httpskonyfabricmycompanycomauthService)

Cloud license activation flow appends ldquoaccountsrdquo to the Identity URL (For example

httpskonyfabricmycompanycomauthServiceaccounts) The URLmust be accessible on the public

internet for license activation to work The response of the URL should be ldquoWelcome to Test Auth

Servicerdquo

Communication fromKonys License servers will originate from the following IP addresses which can

be whitelisted in an organizations firewall configuration

l 5420819284

l 54208192248



24 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

241 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 ltDATA_FILE_PATHgt with actual data file path on the Oracle database server

CREATE TABLESPACE MF_DATA DATAFILE ltDATA_FILE_PATHgtMF_DATA_01DBF SIZE

2048M AUTOEXTEND ON NEXT 100M MAXSIZE 5120M CREATE TABLESPACE MF_INDEX

DATAFILE ltDATA_FILE_PATHgtMF_INDEX_01DBF SIZE 2048M AUTOEXTEND ON NEXT

100M MAXSIZE 5120M CREATE TABLESPACE MF_LOB_DATA DATAFILE ltDATA_FILE_

PATHgtMF_LOB_DATA_01DBF 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 ltinstall-usergt IDENTIFIED BY ltpasswordgt DEFAULT

TABLESPACE MF_DATA TEMPORARY TABLESPACE TEMP PROFILE DEFAULT

GRANT DBA TO ltinstall-usergt

ALTER USER ltinstall-usergt QUOTA UNLIMITED ON MF_DATA

ALTER USER ltinstall-usergt QUOTA UNLIMITED ON MF_INDEX

ALTER USER ltinstall-usergt 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 = PDBltMF_DBgt

CREATE USER ltdedicated-database-local-usergt IDENTIFIED BY

ltpasswordgt DEFAULT TABLESPACE MF_DATA TEMPORARY TABLESPACE TEMP

PROFILE DEFAULT CONTAINER=CURRENT

GRANT DBA TO ltinstall-local-usergt CONTAINER=CURRENT

ALTER USER ltinstall-local-usergt QUOTA UNLIMITED ON MF_DATA



CONTAINER=CURRENT

ALTER USER ltinstall-local-usergt QUOTA UNLIMITED ON MF_INDEX

CONTAINER=CURRENT

ALTER USER ltinstall-local-usergt 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

jdbcoraclethinltDatabase_Host_IPgt1521pdbmfdb

For example jdbcoraclethin192168121521pdbmfdb

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

jdbcoraclethinltDatabase_Host_IPgt1521mfdb

For example jdbcoraclethin192168121521mfdb

242 Prerequisites for Kony Fabric with DB2

Important Download the following DB2 JARs from IBM download site

- IBMDB2 Type 4 Driver (db2jcc4jar)

- DB2 JDBC Driver licence (db2jcc_license_cujar)

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 hereCreate 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

pagesizebufferpool 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 ltDatabase_namegt with your actual database name

CONNECT TO ltDatabase_namegt

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 ltData_Tablespace_Namegt IN DATABASE PARTITION GROUP

IBMDEFAULTGROUP

PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 32 PREFETCHSIZE

AUTOMATIC

BUFFERPOOL BIGBUFFERPOOL OVERHEAD 75 TRANSFERRATE 006 AUTORESIZE YES

INITIALSIZE 32M NO FILE SYSTEM CACHING

COMMIT

-- To create an index tablespace

CREATE LARGE TABLESPACE ltIndex_Tablespace_Namegt IN DATABASE PARTITION GROUP

IBMDEFAULTGROUP




AUTOMATIC



COMMIT

-- To create a LOB tablespace

CREATE LARGE TABLESPACE ltLOB_Tablespace_Namegt IN DATABASE PARTITION GROUP

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

243 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 gt 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 loggingevents 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 loggingevents 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 organizations defined backup and retention policies for

Backup strategies for your database

244 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



245 Prerequisites for Kony Fabric with MySQL

2451 Applicable for Engagement Services

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

Also ensure that youmodify the mycnf or myini with the following parameters

[client]

default-character-set = utf8

[mysql]


[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

mysqlgt 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 (000 sec)

mysqlgt show variables like char

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


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

| 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 | usrsharemysqlcharsets |

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

2452 Applicable for Identity Services

If you are using any lower versions of MySQL 57 such as v5712 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__

DeleteDuplicateAcsUserIdProviderGuidRowsAddUniqueConstraintsql failed

l SQL State HY000

l Error Code 1093

l Error Message You cant specify target table users for update in FROMclause

l Location ltLocation where the installation is donegt

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



25 Application Servers Prerequisites

251 Tomcat Prerequisites

2511 How to Disable Weak Ciphers

To disable weak ciphers modify the SSLConnector container attribute inside the serverxml with

the required https connector tag details The serverxml is located in the ltInstall_

Drivegttomcatconf folder

Add the following is a sample details to SSL connector tag

SSLEnabled=true sslEnabledProtocols=TLSv12 ciphers=TLS_ECDHE_

RSA_WITH_AES_128_CBC_SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHATLS_

ECDHE_RSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_

SHATLS_ECDHE_RSA_WITH_RC4_128_SHA TLS_RSA_WITH_AES_128_CBC_

SHA256TLS_RSA_WITH_AES_128_CBC_SHATLS_RSA_WITH_AES_256_CBC_SHA256

TLS_RSA_WITH_AES_256_CBC_SHASSL_RSA_WITH_RC4_128_SHA

For example the following is a samplemodified https connector tag

ltconnector port=443 maxhttpheadersize=8192 address=127001

enablelookups=false disableuploadtimeout=true acceptCount=100

scheme=https secure=true clientAuth=false SSLEnabled=true

sslEnabledProtocols=TLSv12 ciphers=TLS_ECDHE_RSA_WITH_AES_128_

CBC_SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHATLS_ECDHE_RSA_WITH_

AES_256_CBC_SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHATLS_ECDHE_

RSA_WITH_RC4_128_SHA TLS_RSA_WITH_AES_128_CBC_SHA256TLS_RSA_WITH_

AES_128_CBC_SHATLS_RSA_WITH_AES_256_CBC_SHA256 TLS_RSA_WITH_AES_

256_CBC_SHASSL_RSA_WITH_RC4_128_SHA keystoreFile=mydomainkey

keystorePass=password truststoreFile=mytruststoretruststore

truststorePass=passwordgt

Note Upgrade the SSLCipher list to the latest available versions



2512 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

252 JBoss Prerequisites



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


servers

2522 Configuration of Database Driver Module

1 Extract the comzip file

The unzipped folder structure will becommysqlmain

2 Stop the JBoss Application Server

3 For JBoss configured in the standalonemode copy the extractedcomzip folder and place it

in the JBOSS_HOMEmodules path For the domainmode place the unzipped

comzip folder (commysqlmain) in theJBOSS_HOMEmodules path for

each of themasterslavemachines

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



For example domainxml in the domainmode andstandalone-fullxml in the

standalonemode These files are available at JBOSS_HOME

domainconfiguration andJBOSS_HOME

standaloneconfiguration folders respectively

5 Search for the ltsubsystem xmlns=urnjbossdomainee40gt tag and add the

appropriate globalmodule based on the database selected

For example add the following code for the domainmode

ltglobal-modulesgt

ltmodule name=commysql slot=maingt

ltglobal-modulesgt

6 Save the changes

7 Start the JBoss Server

2523 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 standalonexml from the ltJBoss_Homegtstandaloneconfiguration

2 Configure HostnameIP in the standalonexml file for JBoss as below

ltinterfacesgt

ltinterface name=managementgt

ltinet-address value=127001gt

ltinterfacegt

ltinterface name=publicgt

ltinet-address value=ltmyHostNamegtgt



ltinterfacegt

ltinterfacesgt

3 Configure JBoss to listen for remotemanagement requests as below

l Add ltsocket-binding name=management-native

interface=management

port=$jbossmanagementnativeport9999gt under the ltsocket-binding-groupgt

l Add following section under the ltmanagement-interfacesgt

ltnative-interface security-realm=ManagementRealmgt

ltsocket-binding native=management-nativegt

ltnative-interfacegt

4 For Engagement Services to work remove the following subsystem

ltsubsystem xmlns=urnjbossdomainjpa11gt

ltjpa default-datasource= default-extended-persistence-

inheritance=DEEPgt|

ltsubsystemgt

5 In case of installing all the Kony Fabric components follow these steps to increase heap size by

setting the JAVA_OPTS in the ltJBOSS_DIRgtstandalonebinstandaloneshbat

l standalonebat

set JAVA_OPTS= -server -Xms2048m -Xmx2048m



l standalonesh

JAVA_OPTS=-server -Xms1024M -Xmx1024M

2524 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 instandalonebatdomainbat

( for Windows) or standaloneshdomainsh(for Unix)

-Duserhome=ltlog locationgt

2525 Configure the Standalone Existing JBoss with Self-Signed Certificate (JBoss 71)

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 ltJBoss_Homegtstandaloneconfiguration folder

3 Modify thestandalonexml by adding the following security-realm in the

security-realms section

ltsecurity-realm name=WebSocketRealmgt

ltserver-identitiesgt

ltsslgt

ltkeystore path=ltKeystore_file_

namegt relative-to=jbossserverconfigdir keystore

password=ltKeystore_passwordgtgt

ltsslgt


ltsecurity-realmgt

Here ltKeystore_file_namegt = Name of the keystore file (for example keystorejks)

ltKeystore_passwordgt = Password of keystore file



4 In the standalonexml add the following https-listener tag for default-server in the

Subsystem urnjbossdomainundertow31

lthttps-listener name=https max-post-size=262144000

security-realm=WebSocketRealm socket-binding=httpsgt

2526 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 subsystemundertow for

example ltsubsystem xmlns=urnjbossdomainundertow31gt

For example the following is a sample for https connector tag

lthttps-listener name=https socket-binding=connect security-

realm=ApplicationRealm verify-client=REQUIREDgt


lthttps-listener name=https enabled-

protocols=TLSv1TLSv11TLSv12 enabled-cipher-suites=SSL_RSA_

WITH_3DES_EDE_CBC_SHASSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA TLS_RSA_

WITH_AES_128_CBC_SHATLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_DHE_RSA_

WITH_AES_128_CBC_SHATLS_RSA_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_

AES_256_CBC_SHATLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_ECDH_ECDSA_

WITH_3DES_EDE_CBC_SHATLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA TLS_ECDH_

ECDSA_WITH_AES_256_CBC_SHATLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA

TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHATLS_ECDHE_ECDSA_WITH_AES_256_

CBC_SHA TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHATLS_ECDH_RSA_WITH_AES_

128_CBC_SHA TLS_ECDH_RSA_WITH_AES_256_CBC_SHATLS_ECDHE_RSA_WITH_



3DES_EDE_CBC_SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHATLS_ECDHE_RSA_

WITH_AES_256_CBC_SHA TLS_ECDH_anon_WITH_3DES_EDE_CBC_SHATLS_ECDH_

anon_WITH_AES_128_CBC_SHA TLS_ECDH_anon_WITH_AES_256_CBC_SHA

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

binding=connectgt

253 WebLogic Prerequisites



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

2532 Security Configurations

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

configuration tag of theconfigxml file of WebLogic Server

ltenforce-valid-basic-auth-credentialsgtfalseltenforce-valid-basic-auth-

credentialsgt

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

case ofWebLogic cluster restart all servers fromWebLogic console

2533 Configure the Log Locations - WebLogic


add the following parameter in the JVMarguments present inbinstartWebLogiccmd( for

Windows) or binstartWebLogicsh(for Unix)




254 WebSphere Prerequisites



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

2542 How to Enable TLSv12 Protocol

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

identity fails to log-in to Salesforce Because the TLSv10 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 gt server1 gt Process definition gt Java Virtual Machine

3 Under the Configuration gt General Properties gt Generic JVM arguments add the following -

D parameter

-Dhttpsprotocols=TLSv11TLSv12 -Dcomibmjsse2overrideDefaultTLS=true



4 Go to Security gt SSL certificate and key management gt SSL configurations gt

NodeDefaultSSLSettings gt Quality of protection (QoP) settings

5 Under General Properties gt Protocol select the TLSv11 protocol

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

JVM arguments

-Dcomibmjsse2overrideDefaultTLS=true

For more details refer to Salesforce disabling TLS 10



2543 How to Retrieve Server Groups in WebSphere when using Admin Security with TLS v12

1 InWebSphere Admin Console download the default SSL certificate

2 Import certificate into IBM Java path IBM_PATHJAVAjrelibsecuritycacerts

For example optIBMWebSphereAppServerjava_18_

64jrelibsecuritykeytool -importcert -keystore cacerts -

storetype jks -file optIBMWebSphereAppServerjava_18_

64jrelibsecurity17229154223crt -alias 17229154223

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 KonyMobileFabricInstallerexe LAX_VM DProgram

Files (x86)IBMWebSphereAppServerjavabinjavaexe

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

optIBMWebSphereAppServerprofilesAppSrv01etc

2544 SOAP Connector Port details for WebSphere

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

WebSphere application servers Select your server and view the Communication gt 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 Sametimereg 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 AboutThisProfiletxts 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



2545 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 javajrelibsecurityjavasecurity

l sslSocketFactoryprovider=comibmjsse2SSLSocketFactoryImpl

(for Java7)

l sslServerSocketFactoryprovider=comibmjsse2SSLServerSocke

tFactoryImpl (for Java8)

Refer Configure SSL for WebSphere

2546 NGINX Load Balancer Configuration

l Following are the URLmappings for the Load Balancer configuration

l httpsltdomaingtmfconsole -gt httpsltServer iphostportgtmfconsole

l httpsltdomaingtaccounts -gt httpsltServer iphostportgtaccounts

l httpsltdomaingtworkspace -gt httpsltServer iphostportgtworkspace

l httpsltdomaingtauthService -gt httpsltServer iphostportgtauthService

l httpsltdomaingtadmin -gt httpsltServer iphostportgtadmin

l httpsltdomaingtservices -gt httpsltServer iphostportgtservices

l httpsltdomaingtmiddleware -gt httpsltServer iphostportgtmiddleware

l httpsltdomaingtapps -gt httpsltServer iphostportgtapps

l httpsltdomaingtmetrics -gt httpsltServer iphostportgtmetrics

l httpsltdomaingtkpns -gt httpsltServer iphostportgtkpns

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



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 localhost5000



3 Kony Fabric Topology and Components Kony Fabric Installation Guide - WindowsVersion112

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 users

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

cloudsenvironments so that the services are available for run-time use

ConsolePortal The consoleportal 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




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 httpsdocskonycomkonylibraryintegrationkmf_

integrationservice_admin_console_userguideDefaulthtm

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

themiddlewarewar Similarly when you use only standalone Kony

Server you can ignore the serviceswar

NoteThe 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 Identity Services Integration Services and Engagement

Services on separate nodes

For frequently asked questions and troubleshooting refer to FAQs and Troubleshooting

31 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 JBossWebLogic 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



32 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 -

WindowsVersion112

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 - WindowsVersion112

5 Pre-Installation Tasks

51 Download Kony Fabric Installer

DownloadKonyFabricSetupzip from httpcommunitykonycomdownloads and extract the

file To download Kony Fabric installer from the community portal follow these steps

1 Log in to httpcommunitykonycomdownloads 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 800 GA installer

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

link

TheKonyFabricSetupzip file contains the following files

n KonyFabricInstaller-xxxx_GAexe

n installerproperties - This file is required for silent installation

n READMEtxt

52 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



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 authServicekey workspaceServicekey and

ACCOUNTS_ENCRYPTION_KEY (applicable only for identity and workspace components)

53 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 gpeditmsc and then clickOK The Local Group Policy Editor window

appears

3 In the left pane under Local Computer Policy expand Computer Configuration gt Windows

Settings gt Security Settings gt Local Policies gt 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



54 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

memcachedexe -d install

For example cmemcachedmemcachedexe -d install

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

l cmemcachedmemcachedexe -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_

MACHINESYSTEMCurrentControlSetServicesmemcached Server

8 In the key change the ImagePath entry with the following

Cmemcachedmemcachedexe -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

55 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

5501 Configure Hibernate Dialect in WebLogic (only for WebLogic)

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

setDomainEnvcmd and run thesetDomainEnvcmd before starting theWebLogic server

-Dhibernatedialect=orghibernatedialectOracle10gDialect

56 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_policyjar

l US_export_policyjar

To Configure Unrestricted JCE Policy Files for WebSphere follow these steps

For WebSphere follow the steps provided in the link

httpswwwibmcomsupportknowledgecenterSS8JFY_

750comibmlmt75doccomibmlicensemgmtsecuritydoclmt_scr_downloading_installing_jce_

policyfileshtml

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



1 Go to the Oracle Java SE download

page httpwwworaclecomtechnetworkjavajavasedownloadsindexhtml

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

UnlimitedJCEPolicyJDKltVersiongtzip

4 Extract the downloaded zip file TheUnlimitedJCEPolicyJDKltVersiongtzip file

contains the following files

l local_policyjar


l READMEtxt

5 Copy the jar files (local_policyjar and US_export_policyjar) toltJAVA_

HOMEgtjrelibsecurity

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



57 Database Pre-Installation Tasks

571 MySQL

5711 Increase innodb_log_file_size in myini 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=1010241024

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 myini file increase the innodb_log_file_size = ltvalue should be greater than 10 of

max_allowed_packetgt

572 SQL Server

573 Windows Authentication Support

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

l Download themssql-jdbc-700jre8 (sqljdbc_7000_enutargz) artifact from

httpswwwmicrosoftcomen-USdownloaddetailsaspxid=57175



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

DDownloadssqljdbc_7000_enutargzmssql-jdbc-

700enuauthx64)

574 Oracle

5741 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

SQLgtmdadminmdprivssql

iv Connect to MDSYS user

Conn mdsyssecret

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

creation

v Run the below SQL to create the locator objects

SQLgtmdadmincatmdlocsql

All the abovesql 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 (121) 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 10668371 - Oracle Spatial andOracle Locator Licensing Information

575 MariaDB

5751 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



58 Application Servers Pre-Installation Tasks

581 JBoss

5811 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 thedomainxml file

2 In thedomainxml update all the http connector tags to include the scheme and

proxy-port details

For example

ltconnector name=http protocol=HTTP11 scheme=https

socket-binding=http proxy-name=loadbalancer hostname

proxy-port=443 secure=truegt

5812 Update Listen Interfaces in hostxml for JBoss Cluster

For JBoss domainmode installation configure the following interface address

1 Go toltJBOSS EAP dirgtdomainconfigurationhostxml

2 In place of existing interfaces xml tag replace the default content with below details

ltinterfacesgt


ltany-ipv4-addressgt

ltinterfacegt



ltinterfacegt

ltinterface name=unsecuregt

lt-- Used for IIOP sockets in the standard



configuration

To secure JacORB you need to setup SSL --gt


ltinterfacegt

ltinterface name=anygt


ltinterfacegt

ltinterfacesgt

5813 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 thedomainxml file



1 Go toltJBOSS EAP dirgtdomainconfigurationdomainxml

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

domainxml file

lt-- ltsubsystem xmlns=urnjbossdomainjpa11gt

ltjpa default-datasource= default-extended-

persistence-inheritance=DEEPgt

ltsubsystemgt --gt

5814 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 thestandalonexml file For more details refer to Configure Connectors -

JBoss

5815 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 standalonebat or sh file add the following properties to Java_opts

-Djbossasmanagementblockingtimeout=8400

-Xms2048m

-Xmx4096m

2 In the ltJBoss_Homegtstandaloneconfigurationstandalonexml file add

config deployment-timeout=rdquo8400rdquo in the deployment-scanner subsystem

shown below



ltsubsystem xmlns=urnjbossdomaindeployment-scanner20gt

ltdeployment-scanner path=deployments relative-

to=jbossserverbasedir scan-interval=5000 deployment-

timeout=rdquo8400rdquo runtime-failure-causes-

rollback=$jbossdeploymentscannerrollbackonfailurefalse

gt

ltsubsystemgt

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

1 In the domainbat or sh file add the following properties to Java_opts


2 Set the heap size for the selected server groups as below in the ltJBoss_

Homegtdomainconfigurationdomainxml

l Search for ltserver-groupsgt tag in the domainxml and set the heap size in the JVM

settings

ltheap size=2048m max-size=4096mgt

5816 How to Configure Engagement Services - JBoss

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



-DKMS_CORE_VERSION=2



582 WebLogic

5821 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

5822 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-700jre8 file in theWebLogic classpath

Important To add themssql-jdbc-700jre8 file in theWebLogic classpath perform

the following steps before starting Kony Fabric installation

To add mssql-jdbc-700jre8 file in the WebLogic classpath follow these steps

1 Place the mssql-jdbc-700jre8 in the ltWL_HOMEgtserverlib folder

2 Edit the commEnvcmdsh script in the ltWL_HOMEgtoracle_commoncommonbin

3 Prepend your JAR file to theWEBLOGIC_CLASSPATH environment variable like set

WEBLOGIC_CLASSPATH=WL_HOMEserverlibmssql-jdbc-

700jre8JAVA_HOMElibtoolsjarPROFILE_

CLASSPATHANT_CONTRIBlibant-contribjarCAM_

NODEMANAGER_JAR_PATH

4 Restart the server

5823 How to Configure Engagement Services - WebLogic

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

JVMarguments present indomain-nameStartWebLogiccmd (for Windows) or

domain-nameStartWebLogicsh (for Unix)




583 WebSphere

5831 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-7xexe LAX_VM ltfully qualified path to IBM

java executablegt

5832 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 gt Server Types gt 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_

WebSphereWebSphereAppServerprofilesAppSrv02logskonymflogs

5833 Support Deployment of apiportalwar on WebSphere Server

To support deployment of the apiportalwar onWebSphere make the following configuration

changes

l Disable the following option

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

management gt Enable cookies gt Restrict cookies to HTTPS sessions

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

Security gt Global Security gt Programmatic session cookie configuration

5834 Updating authServicewar and accountswar for WebSphere 9

1 Add the following -D params in the jvm properties

ldquocomibmwebspherejaxrsserverDisableIBMJAXRSEngine=truerdquo



2 In the server configuration expand container services In the

Default JAXRS provider settings change the JAX-RS Provider to

20spec

5835 How to Configure Engagement Services - WebSphere


Generic JVM arguments section of theWebSphere Administration Console under Application

Servers gt serverName gt Process Definition gt Java Virtual

Machine



6 Installation Modes - Kony Fabric Kony Fabric Installation Guide - WindowsVersion112

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)



61 Installing Kony Fabric - GUI (for Windows installations)

You can install Kony Fabric on Tomcat JBossWebLogic or WebSphere servers




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

611 Installing Kony Fabric on Tomcat

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

Fabric components on a single node For multi-node installations refer the Deployment Checklist and

Example Case Studies

Important You need the required hardware and access to the supporting software asmentioned

in the Prerequisites section andmust perform the steps noted in the Pre-installation Tasks section

Make sure that you have proper administrative rights to install Kony Fabric on your computer



The ltInstall Locationgt directory contains the log files documenting each invocation of the installer or

uninstaller Tomake problem identification easier provide these log files to Konywhen reporting an

issue

To install Kony Fabric on Tomcat using the installer follow these steps

1 Unzip theKonyFabricSetupzip file

2 Double-clickKonyFabricInstaller-xxxx_GAexe to launch the installer

The InstallAnywhere dialog appears The InstallAnyWhere dialog displays information about

the progress of the software installation at run time

A dialog with the Kony logo appears



3 TheWelcome to Kony Fabric windows appears

Read the instructions carefully before installing Kony Fabric Console



4 Read the instructions carefully and click Next

The LICENSE AGREEMENTwindow appears

5 Scroll until end of the screen and select the I accept the terms of the License Agreement

option

Note To activate the License Agreement option read carefully the whole agreement text



6 Click Next The Install Components window appears with the following supported installation

types

l Development for singlemachine instance

l Non-Production for larger environments like QA or UAT

l Production for the production instance

Installation environment is set to Development by default



7 Choose one of the appropriate install type based on your license - for example Development

Non-Production or Production

8 Select the Send usage data anonymously check box Allows Kony to collect product usage

information tomake your Kony Fabric experience better Kony does not save any of your private

or application data By default this check box is selected



9 Click Next The Choose components to install window appears

10 Select one or more check boxes for the supported components By default the Console

Identity Services Integration Services Developer Portal and Engagement Services check

boxes are selected

l Console - To install Kony Fabric Console select the Console check box

The system creates the following databases ltprefixgtmfconsoledbltsuffixgt

ltprefixgtmfaccountsdbltsuffixgt and ltprefixgtmfreportsdbltsuffixgt

o Click here for Accounts schema diagram

o Click here for Workspace schema diagram

o Click here for ReportsDB (Metrics) schema diagram



l Identity Services - To install Kony Identity Services select the Identity Services check

box

The system creates the following database ltprefixgtidconfigdbltsuffixgt

o Click here for Identity schema diagram

l Integration Services - To install Kony Fabric Integration Services select the Integration

Services check box

The system creates the following databases konyadmindb and mfreportsdb

o Click here for Admin DB schema diagram


l API Developer Portal - To install developer portal select the API Developer Portal

check box

Note During installation if you have selected API Developer Portal the API

Developer Portal is created You can directly access your KonyDeveloper Portal in

Kony Fabric Console

l Engagement Services - To install Kony Fabric Engagement Services select the

Engagement Services check box

The system creates the following database ltprefixgtkpnsdbltsuffixgt

o Click here for Engagement Server schema diagram

Reports DatabaseThe reports database is used for configuring reports

The Installer creates themfreportsdb if you are installing the following Kony Fabric

components

l Console without Integration Services (with or without Engagement Services)

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



l Integration Services without Console (with or without Engagement Services)

Important If you try to install Integration and Console in different nodes ensure that you

point to the same reports database tomake reports feature work properly

Reports Database for Integration on a Separate Node

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

reports database during the integration installation

For example

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

asltgtmfreportsdbltgt along with theltgtmfconsoledbltgt and

ltgtmfaccountsdbltgt For example your report database name is konymfreportsdb1

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

Engagement Services) on a separate node the installer displays the Reports Database Name

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

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

Details window gt Reports Database Name field Refer to the Database Details window

Refer to creating a reports database for example ltprefixgtmfreportsltsuffixgt

11 Click Next The Install Folder window appears The selected path appears in theWhere would

you like to install field



12 Click Choose to browse the required folder from your system

13 Click Next The Application Server window appears asking you to choose the application

server By default the Application Sever is set to Tomcat



14 In the Application Server window click Tomcat

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 lttomcat-usersgt tag in tomcat-

usersxml

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

the database password follow these stepsmentioned 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

ltDatabasePrefixgtadmindbltDatabaseSuffixgt database in the server_

configuration table

15 Click Next

The HTTP or HTTPS window appears asking you to choose the HTTP or HTTPS By default

this option is set to HTTP

a In HTTP or HTTPS if you select HTTP the following window appears Enter the

HostnameIP Address and HTTP Port Click Next



Note In case of Tomcat enter shutdown port

b In HTTP or HTTPS if you select HTTPS the following window appears Enter the

HostnameIP Address HTTP Port and HTTPS Port Click Next




Important After installing Kony Fabric import your SSL certificate (for example

domainsubdomaincrt) into your Kony Fabric Installers JRE trusted

certificate authority (CA) certificates file - for example ltINSTALL_

DIRgtjrelibsecuritycacerts

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

peer not authenticated

For details refer to Troubleshoot with SSLCertificate Issues

Based on the inputs provided in the previous HTTP or HTTPS gt a or HTTP or HTTPS

gt b one of the following error messages appears



l If you provide an invalid hostnameIP address an alert displays

l If a port is in use an alert displays

l If you provide an invalid Port an alert displays



l If you provide the same port numbers for HTTP and HTTPS an alert displays

16 After you configure the application server details in the HTTP or HTTPS window click Next

The SSL Configuration for HTTPS Communication option appears only if you select HTTPS

By default the Generate a self-signed certificate option is selected Choose one of the

following two options

a To generate a self-signed certificate clickGenerate a self-signed certificate and click

Next The Details for self-signed SSLCertificate window appears

Important To add an existing SSL certificate to a cacerts file refer to How to Add

Your Existing SSLCertificate





Note The path for a self-signed certificate is in this location ltinstall

foldergtkeystorejks

i Enter details for the following fields

l Organization Unit Enter your business unit name

l Host Name Enter your domain name - for example konylabsnet

l Company Enter your company name

l City Enter your city name

l State Enter your state name

l Country Enter your country name



l Keystore Password Enter the password for the JKS file that the installer

will generate

l If you enter invalid details the following error message is displayed

b To use an existing SSL certificate click Use existing certificate and click Next The SSL

Certificate window appears





Note Provide path for jks file as input

i In the SSL Configuration window enter the file path for keystore file and password

details

l If you enter invalid certificate details the following error message is

displayed



17 Click Next to display the Service Details window

18 Click Next The Database Details window appears From the Database Choice drop-down

choose one of the databases to display database details and fill the details By default this

option is set to MySQL



l Enter the following database details for MySQL

o Database Server HostnameIP Enter the DB server HostnameIP to be used to

create a database of selected components of Kony Fabric By default the server

HostnameIP is set as localhost

o Database Port Enter the database port of theMySQLServer By default this field

is set to 3306 for MySQL

o Database User Enter the user name used while creating the database user - for

example dbclient

o Database Password Enter the user password used while creating the database

user



o Database Name Prefix Enter the valid prefix databases - for example Kony

o Database Name Suffix Enter the valid suffix for all databases - for example 1

l Enter the following database details for Oracle




o Database Port Enter the database port of the Oracle Server By default this field

is set to 1521 for oracle



o Service ID Service Name Enter Oracle service ID or service name Service ID

is unique alias given to an instance name of Oracle DB

o Select the tablespace for Oracle database

Important If tablespaceswere already created the DBAmust grant quota

(permissions) on these tablespaces to the installer with admin option

The DBA alsomust include grant quota on the schemas from installer login

n Default Tablespace If selected the database schema and SQL scripts

migration happen automatically to the default tablespace for example

USERS

n User Defined Tablespace If selected enter the tablespaces for the

following

l Data Tablespace

Enter the name for Data tablespace

This is amandatory field If the Data tablespace field empty the

installer displays the error message

If the Data tablespace (for example SampleData) does not exist the




l Index Tablespace Enter the name of Index tablespace

If the input for Index Tablespace is not provided then the value will be

set to the provided Datatable space value

l LOB Tablespace Enter the name for LOB tablespace

If the input for LOB Tablespace is not provided then the value will be


o Database System User Enter the user name used while creating the database

user - for example dbclient

o Database System Password Enter the user password used while creating the

database user

o Database Name Prefix Enter the valid prefix databases - for example jboss


l Enter the following database details for SQL Server

ImportantIf you want to enableWindowsAuthentication Support on SQL Server run the



following command to start the installation process after extracting the artefact

KonyFabricInstaller-8201_GAexe -

Dpropjavalibrarypath=ltlocation of sqljdbc_authdllgt

Note If you choose to enableWindowsAuthentication support on SQL Server you

do not need to provide the Database System User and Database System

Password






o Database Port Enter the database port of the SQL Server By default this field is

set to 1433 for SQL



o Instance Name (optional) Enter the instance name for the database This

information is optional


database user



If a database faces connection issues the system displays an error message For

example

Important Follow the below steps only if you want install Kony Fabric on Tomcat with

Microsoft Azure SQL Server database



l For Microsoft Azure (MSSQL) If you want to install Kony Fabric V8 on Tomcat

with Microsoft Azure SQL youmust edit the authServicexml file from the

existing Tomcat with Microsoft SQL Server install location For more details refer

the following section on how to configure identity to work onMicrosoft Azure SQL

Configure Identity on Tomcat with Microsoft Azure SQL Server

To run identity on Tomcat with Microsoft Azure SQL youmust edit the

authServicexml file from the existing Tomcat with MSSQL install location

1 Open theauthServicexml file from the existing Tomcat with MSSQL install

location

Sample Location for authServicexml from Tomcat with MSSQL install folder

ltLocalDrivegtKonyFabricInstallerV8tomcatconf

CatalinalocalhostauthServicexml

2 Modify the following theauthServicexml file

ltxml version=10 encoding=utf-8 gt

lt-- The contents of this file will be loaded for each

web application --gt

ltContextgt

ltResource auth=Container

driverClassName=commicrosoftsqlserverjdbcSQLServerD

river

factory=orgapachetomcatjdbcpoolDataSourceFactory

initialSize=5 jmxEnabled=true logAbandoned=true

maxActive=10 maxIdle=5 maxWait=10000

minEvictableIdleTimeMillis=30000 minIdle=2

name=jdbcauthglobaldb password=ltPasswordgt

removeAbandoned=true removeAbandonedTimeout=600



testOnBorrow=true testOnReturn=false

testWhileIdle=true

timeBetweenEvictionRunsMillis=30000

type=javaxsqlDataSource

url=jdbcsqlserver

ltDBServerIPPORTgtdatabasename=ltauth database

namegtsendStringParametersAsUnicode=true

username=ltUser_Namegt validationInterval=30000

validationQuery=SELECT 1gt



rivefactory=orgapachetomcatjdbcpoolDataSourceFact

ory initialSize=5 jmxEnabled=true

logAbandoned=true maxActive=10 maxIdle=5

maxWait=10000 minEvictableIdleTimeMillis=30000

minIdle=2 name=jdbcauthconfig password=ltPasswordgt



testWhileIdle=true



url=jdbcsqlserver





ltContextgt



l Enter the following database details for MariaDB




o Database Port Enter the database port of theMariaDB By default this field is set

to 3306 for MariaDB

o Database User Enter the user name used while creating the database user


user



Important The Reports Database Name filed appears only if you have

selected the Console Identity and Integration during Install Components



19 After entering database server details click Next

If a database exists the system displays the warningmessage One or more databases

already exist Do you want to use existing databases If yes then

the schema may be upgraded shown below

Important If you are installing Kony Fabric V8 on an application server using the existing

database and in case if there is a change in server details youmust update the

management_server details in the admin database with the application server instance

details for theWebAapp publish to work Youmust update the following fields in the

server_configuration table of the admin DB

- management_server_host_name ltapplication_instance hostnamegt

- management_server_port ltsoap port of application_instancegt

- management_server_user ltapplication_instance admin usernamegt

- management_server_password ltapplication_instance admin passwordgt

- management_server_groups ltapplication_instance groups detailsgt



20 Click Next The Administrator Account Configuration window appears

The Administrator Account Configuration window helps you to configure your super

administrator account

The Administrator Account Configuration window appears only while installing Console and

Identity Services along with one or all other Kony Fabric components such as Integration

Services and Engagement Services on Tomcat on a single node You can select the

components at Install Components

Note During installation if you have configured your super administrator account you can

directly log in to Kony Fabric Console



21 Select the Create Kony Fabric Administrator Account now check box and enter the following

details to create the super administrator account

l Public URL The URL field is filled with required details for example ltHostnameIP

addressgtltportgt Change these details if required

l First Name Enter the first name of the user

l Last Name Enter the last name of the user

l Email Enter the email address of the user It can include alphanumeric and special

characters that follow standard email address form

l Password Enter the password for the user It can be a combination of alphanumeric and

special characters

l Confirm Password Retype the password to ensure the users identity



22 Enter the databases details and click Next The Pre-Installation Summary window appears



23 Click Install The Installing Kony Fabric window appears

Note Sometimes even after showing 100 installation progress Kony Fabric Installer

takes around 20moreminutes to complete installation onWindows

Once the installation completes the Install Complete window appears with the confirmation

message



24 Click Done to close the window

Important After installing Kony Fabric import your SSL (for example

domainsubdomaincrt) into your Kony Fabric Installers JRE trusted certificate

authority (CA) certificates file - for example CKony

Fabricjrelibsecuritycacerts

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

example peer not authenticated




Note You can now access Kony Fabric Console by using the URLs For more details refer

to Accessing Kony Fabric Console - On-premises

During installation if you have configured your super administrator account you can directly

log in to Kony Fabric Console by using the Console URL



612 Installing Kony Fabric on JBoss GUI (for Windows installations)

You can install Kony Fabric on JBoss by any of the followingmodes




Kony Fabric Installer supports JBoss on single node (Standalone Mode) andmultinode (Domain

Mode)

l Single Node Installation (StandaloneMode installation in Bundled JBoss)

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

l DomainMode (Multi node Installation in pre-configured JBoss cluster)



6121 Installing Kony Fabric on a Standalone Mode in Bundled JBoss

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

Fabric components onmultinode






issue

To install Kony Fabric on bundled JBoss using the installer follow these steps


2 Double-clickKonyFabricInstaller-xxxxx_GAexe to launch the installer













option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example



















14 In the Application Server window click JBoss and click Next The Installation Mode window

appears asking you to choose themode By default this option is set to Standalone Mode

l Standalone Mode (Single Node installation in Bundled JBoss) To install Kony Fabric

on single node on JBoss that is bundled with the Kony Fabric installer click (Single Node

installation in Bundled JBoss)

l Standalone Mode (Single Node installation in pre-configured JBoss) To install Kony

Fabric on single node on JBoss that is installed on your machine click Standalone Mode

(Single Node installation in pre-configured JBoss) For more details on how to install

Kony Fabric on the existing JBoss refer to Installing Kony Fabric on a pre-configured

standalone JBoss - (Single Node)



l Domain Mode (Multi node installation in pre-configured JBoss) To install Kony Fabric

on JBossmultinode click Domain Mode Before installing domainmode ensure that the

JBoss cluster is configured on your install system For more details on how to install Kony

Fabric on Domainmode refer to Multi-Node Installation Procedure

l

Important Before installing Kony Fabric on domainmode ensure that the JBoss

cluster is configured on your install system

15 Click the Standalone Mode (Single Node installation in Bundled JBoss)

16 Click Next



TheHTTP or HTTPS window appears asking you to choose the HTTP or HTTPS By default








































foldergtkeystorejks











will generate










details


displayed
















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example








to 3306 for MariaDB



user











ImportantIf you are installing Kony Fabric V8 on an application server using the existing database and

in case if there is a change in server details youmust update the management_server

details in the admin database along with the application server instance details for the

WebAapp publish to work Youmust update the following fields in the server_

configuration table of the admin DB

l management_server_host_name ltapplication_instance hostnamegt

l management_server_port ltsoap port of application_instancegt

l management_server_user ltapplication_instance admin usernamegt

l management_server_password ltapplication_instance admin passwordgt



l management_server_groups ltapplication_instance groups detailsgt






Services and Engagement Services on JBoss on a single node You can select the















special characters











message





















Log Location for Single Node Installation

For Tomcat

If you select the single node in the InstallationModewindow the logs folder will be created at the

following locations

l For Kony Fabric ltUserInstallDirectorygtlogs

o If you install Console the ltUserInstallDirectorygtlogs folder has three log files They

are mbaasportallog (for mbaas portal) accountsServicelog (for

accounts) andworkspaceServicelog (for workspace)

o If you install Identity Service the ltUserInstallDirectorygtlogs folder has one log file -

authServicelog (for authentication)

l For Kony Fabric Integration ltUserInstallDirectorygtlogs

o If you install Integration Service the ltUserInstallDirectorygtlogs folder has five log

files They are adminlog (for admin) datasource-payloadlog (for

datasource) device-payloadlog (for device) downloadlog (download)

andmiddlewarelog (middleware)

Note Based on the combination of components selected during installation the

ltUserInstallDirectorygtlogs folder will have log files for each component

l For Kony Fabric Engagement Services ltUserInstallDirectorygtlogs folder contains these log

files kmslog and kms-messageslog

l To check Tomcat Server logs refer to the following location

ltKonyFabric_Install_DIRgttomcatlogs

For JBoss


following locations


















l To check JBoss Server logs refer to the following location

ltJBOSS_DIRgtstandalonelogs

For WebLogic


following locations

l For Kony Fabric ltUSERHOMEgtkonymflogs

o If you install Console the ltUSERHOMEgtkonymflogs folder has three log files They





o If you install Identity Service the ltUSERHOMEgtkonymflogs folder has one log file -


o If you install Integration Service the ltUSERHOMEgtkonymflogs folder has five log




n For example onWindows if an admin installed Kony Fabric as a User1 product

logs are located at CUsersUser1konymflogs


ltUSERHOMEgtkonymflogs folder will have log files for each component

l For Kony Fabric Engagement Services ltUSERHOMEgtkonymflogs folder contains these log


l For WebLogic Server logs by default the server log file is located below the server instances

root directory root-directoryserver-nameserver-namelog

For example if you created a domain in the cuser_projectsdomainsMyDomain directory and

you used the cuser_

projectsdomainsMyDomainstartWebLogicServercmd script to start the

server then by default the log file is located in cuser_

projectsdomainsMyDomainMyServerMyServerlog

If the Server File Name field contains only a filename the log file is located in the root-

directoryserver-name directory

For more details refer to httpdocsoraclecomcdE13222_

01wlsdocs81ConsoleHelplogginghtml1045661



For WebSphere


following locations

l For Kony Fabric ltInstallDrivegtkonymflogs

o If you install Console the ltInstallDrivegtkonymflogs folder has three log files They are

mbaasportallog (for mbaas portal) accountsServicelog (for accounts)

andworkspaceServicelog (for workspace)

o If you install Identity Service the ltInstallDrivegtkonymflogs folder has one log file -


o If you install Integration Service the ltInstallDrivegtkonymflogs folder has five log files

They are adminlog (for admin) datasource-payloadlog (for



n For example on CentOS if an admin installed Kony Fabric as a User1 product

logs are located at konymflogs

n For example onWindows if an admin installed Kony Fabric in C drive product

logs are located at Ckonymflogs


ltInstallDrivegtkonymflogs folder will have log files for each component

l For Kony Fabric Engagement Services ltInstallDrivegtkonymflogs folder contains these log


l For WebSphere Server logs refer to the following location

ltWAS_INSTALL_DIRgtAppServerprofilesltprofileNamegtlogsSystemOutlog



6122 Installing Kony Fabric on a Standalone Mode in a Pre-configured JBoss

Kony Fabric can be installed on a pre-configured standalone (single node) JBoss Before installing

ensure that you configure the existing standalone JBoss by using themanual steps provided in the

Prerequisites gt Configure the pre-configured Standalone JBoss


in the Prerequisites section

Youmust perform the steps noted in the Pre-installation Tasks section




issue

To install Kony Fabric on a pre-configured JBoss follow these steps


2 Double-clickKonyFabricInstaller-xxxxGAexe to launch the installer













option





types
















Identity Services Integration Services and Engagement Services check boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example



















14 Click JBoss

15 Click Next The Installation Mode window appears asking you to choose themode By default

this option is set to Standalone Mode (Single Node)



Important To install Kony Fabric on single node on JBoss that is installed along with the

Kony Fabric Installer click Standalone Mode (Single Node) For more details refer to

StandaloneMode (Single Node) Installation

To install multinode click Domain Mode Before installing domainmode ensure that the

JBoss cluster is configured on your install system For more details refer to Multi-Node

Installation Procedure

16 Click Standalone Mode (Existing) and then click Next The The Application Server Details

window will appear with the following details



17 Enter the following details

o Fully Qualified Public URL of Kony Fabric Enter load balancer URL to use public

communication For example lthttphttpsgtlthostnamegtlthttphttps

portgt

o HostnameIP Address Enter public HostnameIP of JBossmaster node Ensure that

you have access to JBossmaster node from your installation system

o Management Port Enter native port of JBoss node

o HTTPHTTPS Port Enter port of Kony Fabric Console



o User Enter the user that you configured in themaster node of the JBoss cluster

o User Password Enter the password that you configured in the node of the JBoss













example dbclient


user



















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL








database user




example






to 3306 for MariaDB



user




























Services and Engagement Services on Tomcat or JBoss on a single node You can select the


Note During Kony Fabric installation if you have configured your super administrator

account you can directly log in to Kony Fabric Console












special characters











message






authority (CA) certificates file - for example

CKonyFabricjrelibsecuritycacerts












6123 Installing Kony Fabric on a Domain Mode (Multi node installation in pre-configured JBoss

cluster)





Installation Tasks section

Important Before installing Kony Fabric on domainmode ensure that the JBoss cluster is

configured on your install system

To install the Kony Fabric console using the installer follow these steps








3 TheWelcome To Kony Fabric windows appears






5 Scroll down and select the I accept the terms of the License Agreement option

Note To activate the License Agreement option read carefully the entire text




types


























box




Services check box





check box



Kony Fabric Console





Reports Database

The reports database is used for configuring reports

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









For example



















14 In the Application Server window click JBoss and then click Next

15 The Installation Mode window appears asking you to choose themode By default this option

is set to Standalone Mode Click Domain Mode (Multinode) and then click Next



Important To install Kony Fabric on single-node on JBoss that is bundled with the Kony

Fabric installer choose 1- Standalone Mode (Single Node) For more details refer to

Installing Kony Fabric on JBoss - Single Node

To install Kony Fabric on single node on a pre-configured JBoss choose 2- Standalone

Mode (Existing) For more details refer to Installing Kony Fabric on Existing JBoss



l The Application Server Details window will appear with the following details

Enter the following details

o Fully Qualified Public URL of Kony Fabric Enter load balancer URL to use

public communication

o Master Node HostnameIP Address Enter public HostnameIP of JBossmaster

node Ensure that you have access to JBossmaster node from your installation

system

o Master Node Management Port Enter native port of JBossmaster node

o Master Node HTTPHTTPS Port Enter port of Kony Fabric Console




o Master Node User Password Enter the password that you configured in the

master node of the JBoss cluster

16 Click Next The Server Groups window appears

17 Enter server groups separated by commas - for example 1 2 shown above Click Next The

system displays the selected groups in the Selected Server Group window shown below





18 Click Next TheMemcached Server window appears


choose one of the databases to display database details By default this option is set to MySQL










example dbclient


user



o Database Name Prefix Enter valid prefix databases - for example jboss

For example the following databases are created for all components

jbossglobaldb54 jbossconfigdb54 jbossconsoledb54 jbossaccountsdb54

jbossmfreportsdb54 jbossadmindb54 and jbossmfreportsdb54

o Database Name Suffix Enter valid suffix for all databases - for example 54













(permissions) on these tablespaces to installer with admin option



migration happens automatically to the default tablespace for example

USERS


following

l Data Tablespace



installers displays the error message





l Index Tablespace Enter the name for Index tablespace

If input for Index Tablespace is not provided then the value will be set

to the provided Datatable space value


If input for LOB Tablespace is not provided then the value will be set







database user

o Database Name Prefix Enter valid prefix databases - for example Kony



example










Password





set to 1433 for SQL








database user




example






to 3306 for MariaDB





user





















21 After entering database server details click Next The Administrator Account Configuration

window appears





Services and Engagement Service on Tomcat or JBoss on a single node You can select the

















special characters


23 Click Next The Pre-Installation Summary window appears



24 Click Install The Installing Kony Fabric Console window appears


message




Important After installing Kony Fabric import your SSL certificate in ltJAVA_

HOMEgtjrelibsecuritycacerts of all nodes of the JBoss cluster

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

not authenticated












Log Location for Multinode Installation

For Tomcat

If you select domainmode (multinode) in the InstallationMode option the logs folder will be created at

the following locations





o If you install Identity Services the ltUSERHOMEgtkonymflogs folder has one log file -


l For Kony Fabric Integration ltUSERHOMEgtkonymflogs

o If you install Integration Services the konymflogs folder has five log files They are

adminlog (for admin) datasource-payloadlog (for datasource)

device-payloadlog (for device) downloadlog (download) and

middlewarelog (middleware)



l For Kony Fabric Engagement Services ltUSERHOMEgtkmslogs log folder contains these log




For JBoss

If you select domainmode (multi node) in the InstallationMode option the logs folder will be created at

















l For Kony Fabric Engagement Services ltUSERHOMEgtkonymflogs log folder contains these

log files kmslog and kms-messageslog


ltJBoSS_Install_DIRgtstandalonelog

For WebLogic
























you used the cuser_










For WebSphere







o If you install Identity Services the ltInstallDrivegtkonymflogs folder has one log file -








n For example onWindows if an admin installed Kony Fabric in C Drive product




l For Kony Fabric Engagement Services ltInstallDrivegtkonymflogs log folder contains these






613 Installing Kony Fabric on WebLogic


Fabric components






issue

To install Kony Fabric on WebLogic using the installer follow these steps















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example



















14 In the Application Server window select WebLogic




16 In the Service Details window enter your current system log-in details

17 Click Next Enter the details

a The following window will appear only if you select all the check boxes at Install

Components



l Fully Qualified Public URL of Kony Fabric Console Enter load balancer URL

to use public communication

l HostnameIP Address of WebLogic Administrator Server Enter IP

AddressHostname of theWebLogic Administrator Server

l WebLogic Administrator Port Enter native port of WebLogic Administrator

Server

l WebLogic Administrator Server User Enter the log-in username for WebLogic

Administrator Server



l WebLogic Administrator Server Password Enter the log-in password for

WebLogic Administrator Server

b Click Next The Server Groups window appears

c Enter server groups separated by commas - for example 1 2 shown in the previous

step Click Next The system displays the selected groups in the Selected Server Group

window shown below



d Click Next The following screen appears for WebLogic connector Jar

l If you want to install Kony Fabric onWebLogic with MS SQL youmust place the

SQL connector jar ( mssql-jdbc-700jre8 ) in theWebLogic Server

path

Please read before continuing

To use Kony Fabric withWebLogic Server in combination with MS SQL database place

the SQL connector jar ( mssql-jdbc-700jre8 ) in theWebLogic Server

Perform the following steps to complete pre-requisites before continuing with installation -

a Copy themssql-jdbc-700jre8 from your Kony Fabric Installation

folder ndash rootKony Fabric location



b Paste themssql-jdbc-700jre8 into the ltWL_HOMEgtserverlib

folder

c Go to the ltWL_HOMEgtoracle_commoncommonbin and edit the commEnv file

l ForWindows commEnvcmd

l For Linux commEnvsh

d Prepend your JAR file to theWEBLOGIC_CLASSPATH environment variable

For Example

set WEBLOGIC_CLASSPATH=WL_HOMEserverlib

mssql-jdbc-700jre8 JAVA_

HOMElibtoolsjarPROFILE_CLASSPATHANT_

CONTRIBlibant-contribjarCAM_NODEMANAGER_JAR_

PATH

e Restart the server



l If you want to install Kony Fabric onWebLogic with DB2 youmust place the DB2

connector jar (db2jcc4jar) in theWebLogic Server path


To use Kony Fabric withWebLogic Server in combination with DB2 database place the DB2

connector jar (db2jcc4jar) in theWebLogic Server


a Copy the db2jcc4jar and paste it into the ltWL_HOMEgtserverlib folder



b Go to the ltWL_HOMEgtoracle_commoncommonbin and edit the commEnv file



c Prepend your JAR file to theWEBLOGIC_CLASSPATH environment variable

For Example

set WEBLOGIC_CLASSPATH=WL_

HOMEserverlibdb2jcc4jarJAVA_



PATH

d Restart the server

Note ltWL_HOMEgt is the folder whereWebLogic is installed















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example



l Enter the following database details for DB2




o Database Port Enter the database port of the DB2 By default this field is set to

5000 for DB2



o Provide tablespace for DB2 database

n Default Tablespace If selected the database schema and SQL

scriptsmigration happen automatically to the default tablespace for

example USERSPACE1


following

l Data Tablespace




If the Data tablespace (for example SampleData) does not

exist the installer displays the error message




If the input for Index Tablespace is not provided then the value

will be set to the provided Datatable space value


If the input for LOB Tablespace is not provided then the value


o Instance Name Enter the instance name for the database



user








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

DB2Database version

o DB2 JDBC Driver Path Click Choose and select the path for the IBMDB2 Type 4

Driver (db2jcc4jar) that you downloaded

Note Provide the complete path of the database jar file For example ltpath

of the database jar locationgtdb2jcc4jar

o DB2 JDBC Driver License Path Click Choose and select the path for the DB2

JDBC Driver license (db2jcc_license_cujar) that you downloaded

Note Provide the complete path of the database license file For example

ltpath of the database license locationgtdb2jcc_

license_cujar


example








to 3306 for MariaDB



user






























message



















614 Installing Kony Fabric on WebSphere


Fabric components






issue

To install Kony Fabric Console on WebSphere using the installer follow these steps















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example



















14 In the Application Server window select WebSphere

15 Click Next In the Service Details window enter the details for WebSphere

Important While installing Kony Fabric onWebSphere if you face any issues refer to

httpdocskonycomkonylibraryKony Fabricresourceswebsphere_faqshtm


Components Enter the following details



l Fully Qualified Public URL of Kony Fabric Enter load balancer URL to use


If you are using standaloneWebSphere Server without Load Balancer ensure that

the port for default host is set to either 9080 For examplehttpltdomaingt9080

l HostnameIP Address of WebSphere Administrator Server Enter IP

AddressHostname of theWebSphere Administrator Server

l WebSphere SOAP Connector Port Enter SOAP connector port of WebSphere

Server



Port details for a particular server can be contained from the Server Configuration

page as shown in the following

l WebSphere Administrator Server User Enter the log-in username for

WebSphere Administrator Server

l WebSphere Administrator Server Password Enter the log-in password for


b Click Next The Keystore and Truststore details window appears Enter the following

details Keystore and Truststore details of your preconfiguredWebSphere Server These

details are needed to create the remote connection to your WebSphere Server



l Enter the location for Keystore file location

l Enter the password for Keystore file location

l Enter the location for Truststore file location

l Enter the password for Truststore file location



c Click Next The Server Groups window appears

d Enter server groups separated by commas - for example 1 2 shown in the previous


window shown below

WebSpherecell=KH2013Node01Cellnode=KH2013Node01serve

r=server1



If the JVMHeap size is less than 6GB when all the components are selected the

following warning is displayed



Note You can choose to continue with the installation by clicking OK to avoid roll

back during installation due to the OutofMemory warning



e Click Next The Shared Lib window appears

Important

Requiredmanual step Before proceeding further with this installation please do the

followingmanual steps

1 Copy konylib folder from ltUSER_INSTALL_DIRgt to your ltWebsphere_Install_

DirgtAppServer This is required for the configuration of shared libraries and

successful deployment of applications



For more information and FAQonWebSphere installation refer to














example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example








5000 for DB2






example USERSPACE1


following

l Data Tablespace

















user









DB2Database version









license_cujar


example








to 3306 for MariaDB



user























18 Click Next The Shared Lib window appears

Important




DirgtAppServer This is required for the configuration of shared libraries and successful

deployment of applications












message



















62 Installing Kony Fabric - Silent-mode

Kony Fabric can also be installed through UnattendedSilent Installation process

Note If a user installs Kony Fabric Console on a partition different from the users home directory

the user must have readwrite execute permissions


Fabric Console




Make sure you have proper administrative rights to install Kony Fabric on your computer

You also need a user where Kony Fabric will be installed



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

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

To install Kony Fabric UnattendedSilent Installation follow these steps

1 DownloadKonyFabricSetupzip file from httpcommunitykonycomdownloads and

extract the file

2 Open a DOS window (Command Prompt) and navigate to the location where the installer is

located

3 Open the installerproperties file and provide inputs for the required properties You

can follow the comments in the properties file for more details

4 Save the installerproperties file

5 At the prompt type KonyFabricInstaller-8xxx_GAexe -i silent -f

installerproperties and press Enter

Note If the file name is installerproperties and is in the same location as KonyFabricInstaller-

7xxxGAexe file then the option -f is not required in the silent installation But if the file name is

changed to other than installerproperties then youmust use -f option irrespective of file location


7 How to Stop and Start Kony Fabric Kony Fabric Installation Guide - WindowsVersion112

7 How to Stop and Start Kony Fabric

After you install Kony Fabric youmust restart your application server to take effect all installed

configurations

71 Tomcat Server

To stop and start Tomcat Server follow these steps

1 Stop server AppServer Locationtomcatbin gt shutdownbat

2 Start server AppServer Locationtomcatbin gt startupbat

72 JBoss Server

To stop and start JBoss Server follow these steps

1 Stop server Restart Windows service from servicesmsc

2 Start server AppServer Locationjbossbin gt startjbossbat

721 For Multinode - JBoss

Start the services for the appropriate service groups that you have configured through the JBoss

Management Console from themaster node

For more detailed information on administration of the app server refer to the JBoss Server

Documentation

73 WebLogic Server

To stop and start WebLogic Server follow these steps



1 Stop server WebLogic InstallationUser Projectsdomain_

namebingtstopWebLogiccmd

2 Start server WebLogic InstallationUser Projectsdomain_

namegtstartWebLogiccmd

For more detailed information on administration of the app server refer to theWebLogic Server

documentation

74 WebSphere Server

To stop and start WebSphere Server follow these steps

741 Windows - To stop and start WebSphere Server

1 Stop server WebSphere Instalaltion

AppServerprofilesAppSrvltnumbergtbingtstopServerbat

2 Start server WebSphere Instalaltion

AppServerprofilesAppSrvltnumbergtbingtstartServerbat

For more detailed information on administration of the app server refer to theWebSphere Server

documentation


8 Upgrading Kony Fabric Kony Fabric Installation Guide - WindowsVersion112

8 Upgrading Kony Fabric

This section explains upgrading Kony Fabric Components through the installer For upgrade to work

minimum installation version should be KonyMobileFabric 652GA

l Prerequisites for Upgrade fromMobileFabric 7x to Kony Fabric 8x While upgrading

MobileFabric 7071 to Kony Fabric V8x for any selected database youmust remove the

version_rank column from the schema_version table in the authglobaldb before the upgrade

l Upgrading Kony Fabric using V8 Installer You can upgrade an existing Kony Fabric instance in

the following two ways

l Upgrade the existing instance

l Install Kony Fabric afresh with connecting to the existing database

l Upgrading Kony Fabric to V8 SP3 FromKony Fabric V8 SP3 the upgrade support is not

available You can install Kony Fabric afresh with connecting to the existing database

81 Prerequisites for Upgrade from MobileFabric 7x to Kony Fabric 8x

While upgrading fromMobileFabric 7x to Kony Fabric V8x Follow these steps

Remove the version_rank column from the schema_version table in the authglobaldb by

passing the following queries before the upgrade

l Oracle

DROP INDEX schema_version_ir_idx

DROP INDEX schema_version_vr_idx

ALTER TABLE schema_version DROP constraint schema_version_

pk drop index

ALTER TABLE schema_version DROP COLUMN version_rank

ALTER TABLE schema_version modify(version null)



ALTER TABLE schema_version add constraint schema_version_pk

primary key(installed_rank)

l MySQL

ALTER TABLE schema_version DROP INDEX schema_version_vr_idx

ALTER TABLE schema_version DROP INDEX schema_version_ir_idx

ALTER TABLE schema_version DROP PRIMARY KEY


ALTER TABLE schema_version CHANGE version version VARCHAR(50)

ALTER TABLE schema_version ADD PRIMARY KEY (installed_rank)

l DB2



ALTER TABLE schema_version DROP CONSTRAINT schema_version_

pk

ALTER TABLE schema_version drop column version_rank

ALTER TABLE schema_version ALTER COLUMN version DROP NOT

NULL

REORG TABLE schema_version

ALTER TABLE schema_version ADD CONSTRAINT SCHEMA_VERSION_PK

PRIMARY KEY(installed_rank)


l MS SQL Server

DROP INDEX [schema_version_ir_idx] ON [dboschema_version]

GO

DROP INDEX [schema_version_vr_idx] ON [dboschema_version]

GO



ALTER TABLE [dboschema_version] DROP CONSTRAINT [schema_

version_pk]

GO

ALTER TABLE [dboschema_version] DROP COLUMN [version_rank]

GO

ALTER TABLE [dboschema_version] ADD CONSTRAINT [schema_

version_pk] PRIMARY KEY CLUSTERED ([installed_rank])

GO

ALTER TABLE [dboschema_version] ALTER COLUMN version nvarchar

(50) NULL

GO

82 Upgrading Kony Fabric using installer



l If you are upgrading fromKony MobileFabric 652GA the installer supports

upgrading of Console Identity services and Integration services only

l If you are upgrading fromKony MobileFabric 70GA or higher the installer supports

upgrading of Console Identity services Integration services and Engagement Services

Important The Installer does not support automatic backups of database and other artifacts The

Installer does not support rollback in case of a failure during the upgrade

- Youmust take backup of your database and other artifacts before upgrading

- After the upgrade republish your Kony Fabric applications



issue



Important You need to upgrade Kony Fabric installation from themaster node

83 Prerequisites

l You can download the Kony Fabric Installer 80 from httpcommunitykonycomdownloads

with your credentials

l Ensure that KonyFabricInstallerexe (xx) file has execute permission

To upgrade Kony Fabric Console using the installer follow these steps


2 Double-clickKonyFabricInstallerGAexe to launch the installer

The InstallAnywhere dialog appears The InstallAnywhere dialog displays information about









Note For Kony Products Installers documentation click here




option




6 Click Next The Install Components window appears with two options New Installation and

Upgrade



7 Choose the Upgrade option for upgrading the existing installation

8 Click Next The Install Folder window appears The default install location appears in Location

of the existing install field



9 Provide the location of the existing Kony Fabric component that you wish to upgrade to this

version Click Install The Pre-Installation Summary window appears





10 Click Install The installation starts

11 ClickOK to continue if the error message Error in stopping services appears

while upgrading Kony Fabric



12 The Backup completed dialog appears The installer has taken backup of the current install

folder The backup folder will have a suffix of _previous_installed_version Click

OK to complete the upgrade




message

13 The Application Server startup status warning dialog appears ClickOK

The installation of Kony Fabric is finished In case of any errors during the installation refer to

the installation log for details Installation log is located at below location For exampleltLocalDrivegtKonyFabricInstallFolder



14 Click Done to complete the installation

84 Upgrading Kony Fabric to V8 SP4





Important The new Kony Fabric Upgrade processworks by upgrading the current database to

the latest version and by installing fresh application server artifacts

l For bundled Tomcat or Standalone JBoss - Stop the running application server A new

application server will be configured as a fresh installation Ensure that you provide the

same prefix suffix Hostname and IP ports as of the previous install

l For remote servers like Pre-Configured JBoss Multi-Node JBossWeblogic or

WebSphere - Delete the existing Applications and Datasources

Additionally for WebSphere youmust also delete the database provider and shared

library







- Youmust back up of your database and other artifacts before upgrading




issue




841 Prerequisites

l You can download the Kony Fabric Installer from httpcommunitykonycomdownloadswith

your credentials


l Ensure that you have the path of your Previous Installation Directory

To upgrade Kony Fabric using the installer follow these steps

1 Ensure that you stop the application server of your existingMobileFabricKony Fabric instance

which you want to upgrade

2 Unzip theKonyFabricSetupzip file that you downloaded for upgrading


l To upgrade the Installer using LAX_VMonWebSphere App Server refer LAX_VM

l To useWindowsAuthentication onMSSQL refer WindowsAuthentication Support

The InstallAnywhere dialog appears The InstallAnyWhere dialog displays information

about the progress of the software installation at run time



4 Continue the installation until you reach the Choose Database Provider screen

Note Upgrade steps for Kony Fabric until the Choose Database Provider section are

same that as a fresh installation

For more details on how to install Kony Fabric components on an application server with a

database refer InstallationModes - Kony Fabric




6 Enter the database server details such as hostname port user and password

7 Enter the prefix and suffix of an existing Kony Fabric database



8 After entering the prefix and suffix of the database click Next






9 Click Yes Use existing The following screen appears

Provide the path of your Previous Installation Directory

If you choose to skip providing the keys go to your upgraded Kony Fabric install location and

paste the following details that you copied from the previousMobileFabric install folder

l authServicekey

l workspaceServicekey

l ACCOUNTS_ENCRYPTION_KEY

Restart or redeploy the war components after you update the keys




11 Clear the Create Kony Fabric administrator account now check box

While installing Kony Fabric using an existing database youmust not configure your super

administrator account again

Note You can directly log in to Kony Fabric Console using the existing credentials after a

successful upgrade


Note The existing schemas and upgraded for the new instance The databases for the

selected components are created based on the prefix and suffix that you provided









message




15 You can now access Kony Fabric Console by using the new URLs For more details refer to

Accessing Kony Fabric Console - On-premises

85 Upgrade from Kony Fabric V8 SP2 to V8 SP4

Before upgrading to V8 SP4 run the following scripts for your database

l Oracle

delete from ltadmindbgtschema_version where script = V621__

konyadmin-oracle-8200sql



l MySQL


konyadmin-mysql-8200sql

l DB2


konyadmin-db2-8200sql

l MS SQL Server



86 Upgrading Custom Metrics Component

FromV9 onwards the custom_metrics_master table has beenmade independent by adding the

application related columns in the custom_metrics_master table itself for better performance These

columns are available as part of themiddleware_requests tableTo have the data for these new fields

for the existing records in the custom_metrics_master table migrate the data from themiddleware_

requests table To do so follow these steps

1 Connect to reports DB and check if theMIGRATEDATATOCMMTABLE procedure is created

It is created when Kony Fabric V9 is installed or upgraded to V9

2 Execute the following procedures for the Fabric database that you have installed

l MySQL CALLMIGRATEDATATOCMMTABLE()

l Oracle EXECUTEMIGRATEDATATOCMMTABLE

l SQL Server EXEC MIGRATEDATATOCMMTABLE



This proceduremigrates the data for new columns of existing rows in the custom_metrics_

master table To do this it creates an intermediate table

3 After the procedure is executed for one of the rows in the custom_metrics_master table check if

the data is populated for the new columns

Note You can now create the custom reports by pulling the columns from the CustomMetrics

view itself If you do not migrate the data the data for the new columnswill not be available

For more information about custommetrics refer to CustomMetrics


9 Installing Hot Fix Archives for Kony Fabric -

Windows


WindowsVersion112

9 Installing Hot Fix Archives for Kony Fabric - Windows

The Kony Fabric Patch Installer can be used to apply patches (software updates) to Kony Fabric

components for a specific GA release The Patch Installer supports applying patches fromKony

MobileFabric 701 (GA) onwards

For example

To apply any701x patches to versions below 701 GA (KonyMobileFabric 70 GA or 65x) you

need to upgrade fromV 65x or V 70GA to 701 GA by using the installer and then

apply701x patches

The Patch Installer uses hotfix archives and applies the software updates to an existing Kony Fabric

Installation A hotfix archive (which is azip file) file can have artifacts for one or more components

While installing hotfix archives all components in the zip are installed to your existing Kony Fabric

installation

91 Patch Installer GA Versions

The followingGA versions are supported for patch installer and hotfix archives

l 701 GA

l 71 GA

l 72 GA

l 73 GA

l V8

l V8 SP2

l V8 SP3 FP1



Windows


WindowsVersion112

92 Prerequisites

l Ensure that you have a previous version of Kony Fabric GA installed on your system at an

accessible network location

Important If you are required to install hotfix archives to a set of components for a specific

release youmust have the supported Kony Fabric GA version (for example Kony

MobileFabric 701) with required components installed on your system

For example if you are required to install hotfix archive for Console version V 701 you

must have the KonyMobileFabric 701 GA with Console installed on your system

l Download thepatchinstaller(binary) andhotfix archives from

httpcommunitykonycomdownloadsmanual with your credentials

l Ensure that KonyFabricPatchInstallerexe file has execute permission

Click here for more details on How to download patch installer and hotfix archives

To download Kony Fabric Patch Installer and hotfixes follow these steps

1 Log in to httpcommunitykonycomdownloadsmanual You can obtain a user name and

password from your sales representative or partner

2 Navigate to the Kony Fabric section

3 From the Kony Fabric Patch Installer select the specific release from the Version drop-down

list and then click on the specific release related files you want to download based on your

platform (Windows or Linux)

For example if you want to downloadKony Fabric Patch Installer 80 GA

select the80 GA version from the drop-down list and then click the Installer_Windows link

4 For the required hotfix components select the specific release from the Version drop-down list

and then click Download The following is a sample screen

To install Kony Fabric patch using the installer follow these steps



Windows


WindowsVersion112

1 Unzip theKonyFabricSetup-8xxGAzip file and navigate to the KonyFabric_

Patch_Installer_Windows folder

2 Double-clickKonyFabricPatchInstaller-8xxGAexe to launch the installer

The InstallAnywhere dialog appears and displays the progress of the launching the installer




Windows


WindowsVersion112

3 Next the Introduction window appears asking for following details Enter the details to proceed

with the upgrade

l Please provide the location of the patch file Provide the patch file location of the Kony

Fabric component that you wish to install to current version For example

samplezip

l Please provide the location of existing installation The default install location appears

in this field

Provide the location of existing Kony Fabric installation that you wish to upgrade with the

selected patch version



Windows


WindowsVersion112


The installer takes backup of the current install folder The backup folder will have a suffix of _

Patch_File_Name For example if the hotfix name is KPNSXXX then the suffix of the

backup folder will be _KPNSXXX

Important The Installer does not support automatic backups of database and other

artifacts The Installer does not support rollback in case of a failure during the upgrade





Windows


WindowsVersion112

5 Click Install The Installing Kony Fabric window appears and the installation starts

Once the installation completes the Installation window appears with the confirmation

message



Windows


WindowsVersion112


the installation log for details Installation log is located at below location For exampleCKonyFabric7705



Windows


WindowsVersion112

6 Click Done to complete the installation After the installation is completed the installer creates

logs in the install folder



For troubleshooting tips to resolve problems that youmay encounter during installation refer to the

following

l FAQs and Troubleshooting

l FAQs and Troubleshooting (WebSphere)


10 Uninstalling Kony Fabric Kony Fabric Installation Guide - WindowsVersion112

10 Uninstalling Kony Fabric

The instructions given below explains how to uninstall Kony Fabric

To uninstall the Kony Fabric using the installer follow these steps

1 Click Start menu and then select Computer

2 Find and click Hard Disk Drive where Kony Fabric is installed

3 Click Kony Fabric Install folder

The Install folder opens and displays the inner Uninstallexe



4 Double-click theUninstallexe

A dialog with Kony logo appears

The Uninstall Kony Fabric window appears



TheUninstall Kony Fabric window informs a user that InstallAnywhere will remove features

that were installed during product installation Files and folders created after installation are not

removed from the Install directory

5 Click Next to continue

The Delete Database choice window displays the alert message asking if you want to delete

the database

6 Select the option button asDelete all data or Retain all data By default Retain all data is

selected



Note If you select the Delete all data option the database is deleted from your system If

you select the Retain all data option then database is not deleted and you can access it for

future use

7 Click Uninstall to continue

The Uninstall Kony Fabric window displays list of features and informs a user that the

uninstaller removes the following features



Once the uninstallation is complete the Uninstall Complete window appears It informs that all

items are successfully uninstalled





11 Post-Installation Tasks Kony Fabric Installation Guide - WindowsVersion112

11 Post-Installation Tasks

111 Configuring Secure Sockets Layer (SSL) Certificate

You can troubleshoot trusted certification issues

Important Apples App Transport Security (ATS) mandatesHTTPS for all communication and

requires the use of TLS v12 or higher for all SSL certificates and load balancers

For Apple apps to work properly and adhere to App Store guidelines youmust enable your Kony

Fabric on-premises instance with SSL and configure your network infrastructure to use TLS

version 12 or higher For more information please refer the following

httpcommunitykonycomblogsmadpapp-transport-security-ats-compliance

After installing Kony Fabric on HTTPS import your SSL certificate (for example

domainsubdomaincrt) into your Kony Fabric Installers JRE trusted certificate authority

(CA) certificates file - for example ltINSTALL_DIRgtjrelibsecuritycacerts

If your SSL certificate is not configured the system displays an error - peer not authenticated For

details refer to Troubleshoot with SSLCertificate Issues

To enable communication between Kony Fabric Console and other products such as Kony

Fabric Integration Services and Kony Fabric Engagement Services follow these steps

l import each products certificate (Kony Fabric Integration and Kony Fabric Engagement

Services) into the Kony Fabric console (for example ltINSTALL_

DIRgtjrelibsecuritycacerts)

l import console cert into the product boxes cacerts such as Kony Fabric Sever Kony Fabric

Engagement Services and Kony FabricManagement

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

To add an installer generated self-signed certificate to cacerts follow these steps



1 From your Kony Fabric installed system open theWindows command prompt and run the

following command to generate anintermediatecrt file from the keystore

ltUSERINSTALLDIRgtjrebinkeytool -export -alias ltHOST_URL_SSL_

CONFgt -file ltUSERINSTALLDIRgtintermediatecrt -keystore

ltUSERINSTALLDIRgtkeystorejks -storepass ltPassword_of_keystoregt

Based on the hostname and keystore password provided at the SSL Certificate window the

preceding command exports the required certificate from the source keystore with the given

name - for example intermediatecrt

2 Run the following command to import theintermediatecrt certificate file into your

Kony Fabric Installers JRE trusted certificate authority (CA) certificates file

ltUSERINSTALLDIRgtjrebinkeytool -import -noprompt -trustcacerts -

alias ltHOST_URL_SSL_CONFgt -file

ltUSERINSTALLDIRgtintermediatecrt -keystore

ltUSERINSTALLDIRgtjrelibsecuritycacerts -storepass changeit

1112 How to Add an Existing SSL Certificate to Cacerts

If Java does not identify a certificate issuer by default you need to import an SSL into your cacerts

To add an existing SSL certificate to cacerts follow these steps

Use the following steps to import your existing certificate to cacerts with the proper value of alias

keystore location and keystore password


following command to add anintermediatecrt file from the keystore

ltUSERINSTALLDIRgtjrebinkeytool -export -alias ltyourcertificate_

domaingt -file ltUSERINSTALLDIRgtintermediatecrt -keystore

ltkeystore_locationgt-storepass ltPassword_of_keystoregt






alias ltyourcertificate_domaingt -file



112 JDK Version Compatibility

In case if you upgrade your JDK version in your middleware server to enable JDK version

compatibility make the appropriate changes in an app servers middlewareproperties file

located in your middleware server installation folder

For example When you upgrade JDK V 16 to JDK V 17 (vice-versa) you can still run your

middleware server Kony Fabrics run-time apps cannot be accessed If you try to access any apps at

runtime the system throws an error message due to JDK version incompatibility

1 In your middleware server installation folder open the middlewareproperties file

located at the below path

l for JBoss ltinstaller foldergtmiddleware_

homemiddlewaremiddleware-bootconfigl for Tomcat ltinstaller foldergtmiddleware_

homemiddlewaremiddleware-bootconfig

2 Make the following changes in the middlewareproperties file

l ssltrustStore=ltjava_homegtjrelibsecuritycacerts

l sslkeyStore=ltjava_homegtjrelibsecuritycacerts



113 How to Update Security Configuration in Configxml (Required in

case of WebLogic installation)

When you install Kony Fabric onWebLogic with default configuration in theWebLogics configxml

file Kony Fabric fails to register with environments

To update security configuration in the configxml file in WebLogic follow these steps

1 Go to ltweblogic profile foldergtconfig folder

2 Open the configxml and add below line under the ltnode-manager-password-

encryptedgt tag

ltenforce-valid-basic-auth-credentialsgtfalseltenforce-valid-

basic-auth-credentialsgt

For example

ltdefault-realmgtmyrealmltdefault-realmgt

ltcredential-encryptedgtAES

rGucYtN8zScvbfvJtHyHlwhWg1Av2yLPQmQ3vdAVwACiJ+k8zTKQBTKf8TRcT

LWPWFZkunUyllbSvLJ8P07GCgJf4v6egFUlVVdfOpgYrbkohlp49S7KVMTgRkhL

79ltcredential-encryptedgt

ltnode-manager-usernamegtweblogicltnode-manager-usernamegt

ltnode-manager-password-encryptedgtAES

R2P+dzOm5y1ODB8e3aMj6spUrJet6h6aUv91umUe5q4=ltnode-manager-

password-encryptedgt





114 How to Configure Memcache for Integration Services

l For KonyFabric version 73 or above you can configure thememcache fromAdmin console

To configure memcache in MobileFabric 73 or above versions follow these steps

1 Open Admin console (httpsltserver-hostgtltserver-portgtadmin)

2 In the left pane go to the Settings tab

3 Under the Runtime Configuration tab expand theMemcache Configuration key

4 In theMemcache Cluster field provide your memcache hostnameIP and port details

separated with a colon For example lthostnameIPgtltPortgt

5 Save the changes

l For below MobileFabric 73 you can configure thememcache using queries on konyadmindb

To configure memcache in below MobileFabric 73 follow these steps



Since UI is not available in version below 73 youmust update the property value in the server_

configuration table of KONYADMINDB database

Note Name of the KONYADMINDB depends on the suffix and prefix provided which you

provided during the installation

1 Execute the following steps

UPDATE ltKONYADMINDBgtserver_configuration set prop_value =

ltmemcache_hostnamegtrsquorsquoltmemcache_portgtrsquo created_date =

CURRENT_TIMESTAMP updated_date

= CURRENT_TIMESTAMP WHERE prop_name = memcachecluster

Verification To verify whether thememcache configuration is successfully done go to

the Health Check page and look for Access to Cache entry

Note It may take up to 5minutes for the healthcheck to reflect the cache status If you

are still unable to find the particular entry in the Health Check page try clearing the

healthcheck cache using the following URL

httpsltserver-hostgtltserver-portgtadminhealthcheckoutput=json



115 Configure Deployment of mbaasportalwar File for Multi-Node

Once Kony Fabric installation succeeds the Kony Fabric Console will not be displayed as the enable-

welcome-root value is set true in the domainxml file

To configure mbaasportalwar follow these steps

1 In themaster node open the domainxml file from

JBOSSDIRdomainconfiguration and search for enable-welcome-root=true

2 Replace enable-welcome-root=true with enable-welcome-root=false

116 Remote Installation Pre-requisites

After you have installed Kony Fabric youmust retain the Installation folder for upgradesWhile

upgrading the Kony Fabric installer requires the installvariablesproperties file under the

ltUSER_INSTALL_DIRgt_Kony Fabric_installation folder

1161 Installing Kony Fabric Remotely

You can install Kony Fabric remotely on the following supported application servers

l JBossMulti-node

l JBoss Standalone Existing

l WebLogic

l WebSphere

117 How to Turn off the Send usage data anonymously feature

AllowsKony to collect product usage information tomake your Kony Fabric experience better



1 Go to the Accounts database configured for the Kony Fabric installation

2 Open the account_configurations table

3 Find the row entry in the name columnwith name as analyticsEnabled

4 Modify it to truefalse

5 Refresh Kony Fabric Console

You should be able to figure out if analytics data that is sentout by trying to check in the Network

tab in the Browser Developer Tools

118 Configuring Datasource for performance improvements for JBoss

pre-existing and Domain Mode

While using pre-configured JBoss or JBoss in DomainMode add the following snippet to the

datasource to improve the performance

ltpoolgt

ltmin-pool-sizegt10ltmin-pool-sizegt



ltmax-pool-sizegt30ltmax-pool-sizegt

ltflush-strategygtIdleConnectionsltflush-strategygt

ltpoolgt

Note For the bundled version the installer will add the default size to the datasources

119 Health Check URL

The following is the Component Health CheckURL if the initial setup is successful

lthttphttpsgtltDomainnamegtltportgtmfconsolehealth_checkall

workspacepassedaccountspassedportalpassed

lthttphttpsgtltDomainnamegtltportgtauthServicev1managecheckhealth

Passed

lthttphttpsgtltDomainnamegtltportgtadminhealthcheckoutput=json

healthCheckPASSEDhealthDetail

Access to Reporting QueuePASSEDAccess to Admin

DBPASSEDAccess to Reports DBPASSEDAccess to Storage

DBPASSED

versionV8 SP2 FP1 HF1

lthttphttpsgtltDomainnamegtltportgtserviceshealthcheckoutput=json

healthDetail

appIDservicesAccess to Reporting QueuePASSEDAccess to

Admin DBPASSEDAccess to Storage DBPASSED

applicationHealthCheckPASSEDversionMiddleware

VersionKonyFabricInstaller-GA-8211

lthttphttpsgtltDomainnamegtltportgtkpnsservicehealthcheckjson


Quartz jobsPASSEDAccess to Database

ServerPASSEDSecurity CredentialsPASSED

version8211_GA



1110 Steps to enable SAPJCo

The installer provides the following artifacts

1 SapJCoDestinationProviderjar

2 Modulexml (for JBoss)

You can download the other artifacts libsapjco3so (for Linux) or sapjco3dll (for Windows) and

sapjco3jar from httpswebsmp204sap-agdeconnectors

The SapJCoDestinationProviderjar can be located at

l ltUSER_INSTALL_DIRgtIntegrationsapjcomain - for JBoss

l ltUSER_INSTALL_DIRgt Integration - for Weblogic andWebSphere

TheModulexml can be located at

l ltUSER_INSTALL_DIRgtIntegrationsapjcomain

11101 Steps for Tomcat

1 Navigate toltUSER_INSTALL_DIRgttomcatlib and add the following files

l sapjco3jar

l libsapjco3sosapjco3dll

Note The SapJCoDestinationProviderjar is already placed in theltUSER_INSTALL_

DIRgttomcatlib by the installer




11102 Steps for JBoss

For Windows Place the sapjco3dll in the jbossbin folder or CUsersltUSER_NAMEgtSystem32

folder

For Linux Place the libsapjco3so in the usrbin folder or any location on themachine and append

the path to the $LD_LIBRARY_PATH variable

111021 JBoss - Standalone (Bundled)

1 Navigate toltUSER_INSTALL_DIRgtjbossmodulesorgsapjcomain and

add the following files

l sapjco3jar

l SapJCoDestinationProviderjar

2 Navigate toltUSER_INSTALL_DIRgtjbossmodulesorgsapjcomain

l Inmodulexml under the ltresourcesgt tag add ltresource-root

path=sapjco3jargt

l Instandalone-fullxml under the ltglobal-modulesgt tag add ltmodule

name=orgsapjco slot=maingt

111022 JBoss - Standalone(Pre-configured)Domain mode

1 Navigate toltJBOSS_DIRgtmodulesorgsapjcomain and add the following

files

l sapjco3jar


2 Navigate toltJBOSS_DIRgtmodulesorgsapjcomain


path=sapjco3jargt



l Instandalonexml or domainxml in the subsystem add ltsubsystem

xmlns=urnjbossdomainee40gt Add the following tag

ltglobal-modulesgt

ltmodule name=orgsapjco slot=maingt

ltglobal-modulesgt

11103 Steps for Weblogic

1 Navigate to ltWL_HOMEgtwlserverserverlib and add the following files

l sapjco3jar



2 Go toltWL_HOMEgtuser_projectsdomainsbase_domainbin and edit the

startWeblogic script file using one of the following commands

l For Windows startWeblogiccmd

l For Linux startWeblogicsh

3 Prepend your JAR files to the SAVE_CLASSPATH environment variable

For example in startWeblogicsh add

SAVE_CLASSPATH=$WL_HOME

serverlibSapJCoDestinationProviderjar$WL_HOME

serverlibsapjco3jar$WL_HOME

serverliblibsapjco3so$CLASSPATH




11104 Steps for Websphere

1 Navigate toltWAS_LOCATIONgtAppServerlib and add the following files

l sapjco3jar


2 Navigate toltWAS_LOCATIONgtAppServerbin and add the

libsapjco3sosapjco3dll file



12 FAQs and Troubleshooting Kony Fabric Installation Guide - WindowsVersion112

12 FAQs and Troubleshooting

This section lists the troubleshooting tips to resolve problems that youmay encounter during

installation and post installation

l Issue

The upgrade installation is rolling backwith Validate failed from 8213

Workaround

Before Upgrade execute below SQL statement from admin database

For MySQL

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



For SQLServer

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


konyadmin-sqlserver-8200sql

For Oracle

----------



For DB2

--------





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

JBoss servers

l Issue

If you upgrade the integration service or install on new server using the existing database but

with a different server details like fully qualified URL port and when you publish an app the app

publish fails

Workaround

Youmust updatemanagement server details in the server_configuration table in admin

database

l Issue

If you upgradeMobileFabric 73 or older version on JBoss (Standalone existing JBoss or pre-

configured JBoss) to Kony Fabric V8 the upgrade gets completed with errors for JBoss

Workaround

Youmust remove the database connector jar from the JBoss deployments

l How to change the HostnameIP address and port details of an existing Kony Fabric

Server

After the installation of Kony Fabric if you want to change the existing HostnameIP address

that was used during the installation of Kony Fabric follow these steps

1 Go to yourKony Fabric install folder



2 Go toscripts folder - for example ltMFinstallfoldergtscripts The

scripts folder contains a sql file for the database type that you selected while

installing Kony Fabric

3 Open thesql file in a text editor

Important If you want to access Kony Fabric Console with a new port change the

value for the NEW_PORT with the new value Otherwise assign the value of the OLD_

PORT to the NEW_PORT variable

Important If you want to access Kony Fabric Console with a hostnameIP address

change the value for the NEW_HOST with the new value Otherwise assign the value

of the OLD_HOST to the NEW_HOST variable

4 Change the values for the following variables

l For MySQL MariaDB DB2 and SQL Server replace the values for the NEW_

HOST and the NEW_PORT with new values

l For Oracle replace all the occurrences of the NEW_HOST and the NEW_PORT with

new values

Important If you have selected your database asDB2 follow the steps provided in

the sql file in theltMFinstallfoldergtscripts folder

5 Run the SQL script on the database where you have installed Kony Fabric

l How to change the Engagement Async Core version of an existing Kony Fabric Server

running on Tomcat



From the Installer you create a service having JVMparams The service gets registered in the

WINDOWSRegistry To override any -D paramswe need to either change the registry entry or

update the service To change the Engagement AsyncCore version in your Kony Fabric server

running on Tomcat withWindowsOS do the following

l Change the service inWindowsRegistry

l Modify the JVMparams by using Regedit

l Issue

If the javasql BatchUpdateException Prepared statement needs to be

re-prepared error is logged in the Identity service logs or if certain operations fail to work

properly when an identity service is invoked do the following

Workaround

Add the following server variable in MariaDB ini file located in theMariaDB installation folder

table_open_cache=64

Path for MariaDB ini file ltUSER_INSTALL_DIRgtMariaDB 101datamyini

l Issue

If you face the error dialogue Windows error 2 occurred while loading the

Java VM while launching the Kony Fabric Patch Installer because of the following

Kony Fabric Patch Installer runswith your systems default Java If an user machine has Java 8

installed then check if themachinesSystem Environment Path for Java or

JAVA_HOME is set to cprogramdataoraclejavajavapath

Workaround



1 Remove the current path fromJAVA_HOME and set the new path as CProgram

Files (x86)Javajre180_40bin

2 Launch the Kony Fabric Patch Installer

3 After the installation completed reset themachines System Environment

Path for Java or JAVA_HOME path to its original path For example

cprogramdataoraclejavajavapath

l Issue

If your service providers certificate is not configured the system displays an error - peer not

authenticated

Workaround

For trusted certification issues refer to Service Providers Certificate Issues

l Issue - MySQL DB error

If you use a common database for multiple tasks such as installing Kony Fabric or accessing a

service from a device the system throws theMySQLDB error -- prepared statement needs to

be re-prepared-- in logs

Workaround

To avoid this error increaseTABLE_DEFINITION_CACHE TABLE_OPEN_CACHE

and MAX_CONNECTIONS of your MySQL

Kony recommends a dedicatedMySQLDB Server for Kony Fabric



l Issue - App publishing error

If your app publish fails the system displays an error message

When IDE app publish fails with Error MessageInternal

server error occurred while publishing application More Details

null

ResponseHTTP11 500 Internal Server Error 500 Internal server

error more details null

Workaround

Restart middleware server and re-publish the app

l Issue

In case of Tomcat when you update the JRE_HOME in the catalinabat file and restart

Windows service Kony Fabric Console runs on older Java version

Workaround

To run Kony Fabric Console with the updated JRE launch the startupbat file

l Issue - Latest Kony Fabric does not support old DB configured with lower versions of Kony

Fabric

In Multinode environment user should add new node with same version of Kony Fabric and do

the additional settings related to key

Workaround



1 Configure additional nodes into the existing environment by using the existing database

that is setup with Kony Fabric

2 Replace the following key values in the new node with the key values in the existing

configuration

o In theaccountsproperties file theACCOUNTS_ENCRYPTION_KEY

value should be configured with the same value as in all nodes

Path for theaccountsproperties file

ltInstaller FoldergttomcatwebappsaccountsWEB-

INFclasses

o TheAuthservicekey should be configured with the same value in all nodes

Path for the authservicekey file

ltInstaller FoldergttomcatwebappsauthServiceWEB-

INFclasses

o Theworkspaceservicekey value should be configured with the same

value in all nodes

Path for theworkspaceservicekey file

ltInstaller FoldergttomcatwebappsworkspaceWEB-

INFclasses

l Issue - Kony Engagement Services fails to start after installation with Oracle DB

Hibernate Dialect needs to be set manually For more details refer to Configuring Hibernate

Dialect inWebLogic (only for WebLogic)

Workaround






configuration





INFclasses




INFclasses


value in all nodes



INFclasses

l Issue - During design time of your app the system throws errors due to several reasons

For example

Caused by

commysqljdbcexceptionsjdbc4MySQLSyntaxErrorException The

size of BLOBTEXT data inserted in one transaction is greater than

10 of redo log size Increase the redo log size using innodb_log_

file_size

Workaround

Increase the innodb_log_file_size For more details refer to Increase innodb_log_file_size in

themyini file



l Issue

When customer wants to install Kony Fabric with Oracle as database type the system throws

the error Invalid Data Type SDO_GEOMENTRY

Workaround

Install Oracle locator which is required for Kony Fabric installation For more details refer to

Pre-installation Tasks gt Create Locator Component for Oracle Database

l Issue

Upgrading fromKonyMobileFabric 652 701 or 711 with MS SQLServer fails Installer is

rolling back as the schema version table is not migrating properly while upgrade

Workaround

To avoid this issue follow this step

Remove the version_rank column from schema_version table in each schema by

following queries before upgrade

drop index schema_version_vr_idx on masterltSCHEMA_

NAMEgtschema_version

alter table masterltSCHEMA_NAMEgtschema_version drop column

version_rank



l Issue

Uninstallation of Kony Fabric onWebLogic with Oracle does not drop createdOracle

databases If a user tries to uninstall and selects Delete All Data during installation datasource

are not getting deleted fromWebLogic instance aswell as databases are not getting dropped

from oracle

Workaround

l Delete databases fromWebLogic Console

l Drop all schemas crated in Database related to Kony Fabric installer

l Issue

Installer fails to upgrade admindb scripts as admindb name is not available in

installvariablesproperties file

Workaround

Update the below propertyinstallvariablesproperties

From ADMIN_DB=$CONSOLE_SERVER_DB_1$ to ADMIN_DB=ltactual db namegt

l Issue

Auth (Kony Identity Service) datasources are not created when upgraded fromKony Fabric

652GA to 72GA

Workaround

Create datasource for authconfigdb and authglobaldb For more details refer to

Configuring_JNDI_for_Database gt Data Source for Single Node and Multinode gt Kony

Identity Service Data Source section



l Issue

If you have installedMobileFabric 73 or older and when you use the existing database for Kony

Fabric V8 on JBoss theWeb Application publish fails

Workaround

Update the management_server_port in the server_configuration table of

admindb with the jbossmanagementhttpport in the ltUSER_INSTALL_

DIRgtjbossstandaloneconfigurationstandalonexml

l Issue

If you do not want to use a DB user with DBA role or Equivalent privileges for the Kony Fabric

installation onORACLE database follow these steps

Workaround

Manual Steps

1 Create Component Users (schema) with the required grants as below

CREATE USER ltprefixgtMFCONSOLEDBltsuffixgt identified by ltpasswordgt

default tablespace ltdataTablespacegt profile default

ALTER USER ltprefixgtMFCONSOLEDBltsuffixgt QUOTA UNLIMITED ON USERS

GRANT CONNECTRESOURCECREATE VIEW TO ltprefixgtMFCONSOLEDBltsuffixgt

GRANT CREATE JOB TO ltprefixgtMFCONSOLEDBltsuffixgt

GRANT MANAGE SCHEDULER TO ltprefixgtMFCONSOLEDBltsuffixgt

CREATE USER ltprefixgtMFACCOUNTSDBltsuffixgt identified by ltpasswordgt


ALTER USER ltprefixgtMFACCOUNTSDBltsuffixgt QUOTA UNLIMITED ON USERS



GRANT CONNECTRESOURCECREATE VIEW TO

ltprefixgtMFACCOUNTSDBltsuffixgt

GRANT CREATE JOB TO ltprefixgtMFACCOUNTSDBltsuffixgt

GRANT MANAGE SCHEDULER TO ltprefixgtMFACCOUNTSDBltsuffixgt

CREATE USER ltprefixgtMFREPORTSDBltsuffixgt identified by ltpasswordgt


ALTER USER ltprefixgtMFREPORTSDBltsuffixgt QUOTA UNLIMITED ON USERS

GRANT CONNECTRESOURCECREATE VIEW TO ltprefixgtMFREPORTSDBltsuffixgt

GRANT CREATE JOB TO ltprefixgtMFREPORTSDBltsuffixgt

GRANT MANAGE SCHEDULER TO ltprefixgtMFREPORTSDBltsuffixgt

CREATE USER ltprefixgtIDCONFIGDBltsuffixgt identified by ltpasswordgt


ALTER USER ltprefixgtIDCONFIGDBltsuffixgt QUOTA UNLIMITED ON USERS

GRANT CONNECTRESOURCECREATE VIEW TO ltprefixgtIDCONFIGDBltsuffixgt

GRANT CREATE JOB TO ltprefixgtIDCONFIGDBltsuffixgt

GRANT MANAGE SCHEDULER TO ltprefixgtIDCONFIGDBltsuffixgt

GRANT CREATE TABLE TO ltprefixgtIDCONFIGDBltsuffixgt

GRANT CREATE ANY INDEX TO ltprefixgtIDCONFIGDBltsuffixgt

GRANT ALTER ANY TABLE TO ltprefixgtIDCONFIGDBltsuffixgt

CREATE USER ltprefixgtADMINDBltsuffixgt identified by ltpasswordgt


ALTER USER ltprefixgtADMINDBltsuffixgt QUOTA UNLIMITED ON USERS

GRANT CONNECTRESOURCECREATE VIEW TO ltprefixgtADMINDBltsuffixgt

GRANT CREATE JOB TO ltprefixgtADMINDBltsuffixgt

GRANT MANAGE SCHEDULER TO ltprefixgtADMINDBltsuffixgt

CREATE USER ltprefixgtKPNSDBltsuffixgt identified by ltpasswordgt


ALTER USER ltprefixgtKPNSDBltsuffixgt QUOTA UNLIMITED ON USERS

GRANT CONNECTRESOURCECREATE VIEW TO ltprefixgtKPNSDBltsuffixgt

GRANT CREATE JOB TO ltprefixgtKPNSDBltsuffixgt

GRANT MANAGE SCHEDULER TO ltprefixgtKPNSDBltsuffixgt



2 Create a non DBA user with the below grants This user will be given to the Installer

CREATE USER ltINSTALLER_USERgt IDENTIFIED BY ltpasswordgt

GRANT CREATE SESSION TO ltINSTALLER_USERgt WITH ADMIN OPTION

GRANT SELECT ANY DICTIONARY TO ltINSTALLER_USERgt

ALTER USER ltINSTALLER_USERgt QUOTA UNLIMITED ON ltdataTablespacegt

ALTER USER ltINSTALLER_USERgt QUOTA UNLIMITED ON ltindexTablespacegt

ALTER USER ltINSTALLER_USERgt QUOTA UNLIMITED ON ltlobTablespacegt

Note The password for the component users and the installer user have to be same

l Issue

For storage services to work change the following storagedb entries in the admindb

Workaround

Manual Steps

storage_database_type - oracle

storage_database_hostname - Database hostnameIP

storage_database_port - Database Port

storage_database_username - DBA username

storage_database_password - DBA Password

storage_database_instance - service IDservice name

storage_data_tablespace - Data Tablespace name

storage_index_tablespace - Index Tablespace name

storage_lob_tablespace - Lob Tablespace name



l Issue


installation onMSSQL follow these steps

Workaround

Manual Steps

Create database ltprefixgtmfreportsdbltsuffixgt

Create database ltprefixgtmfaccountsdbltsuffixgt

Create database ltprefixgtmfconsoledbltsuffixgt

Create database ltprefixgtadmindbltsuffixgt

Create database ltprefixgtkpnsdbltsuffixgt

Create database ltprefixgtidconfigdbltsuffixgt

CREATE LOGIN loginId WITH PASSWORD = loginpwd

GO

use msdb

GO

create user userId from LOGIN loginId

GO

EXEC sp_addrolemember SQLAgentUserRole userId

EXEC sp_addrolemember SQLAgentReaderRole userId

EXEC sp_addrolemember SQLAgentOperatorRole userId

GO

use ltprefixgtmfreportsdbANltsuffixgt

GO


GO

GRANT ALTER ANY DATABASE DDL TRIGGER TO userId

GO

GRANT CREATE TABLECREATE TYPECREATE

PROCEDURESELECTUPDATEDELETEINSERTEXECUTEREFERENCESCREATE



VIEWALTERVIEW Definition TO userId

GO

use ltprefixgtmfaccountsdbltsuffixgt

GO


GO


GO




GO

use ltprefixgtmfconsoledbltsuffixgt

GO


GO


GO




GO

use ltprefixgtadmindbltsuffixgt

GO


GO



VIEWALTER TO userId

GO

use ltprefixgtkpnsdbltsuffixgt

GO



CREATE SCHEMA ltprefixgtkpnsdbltsuffixgt

GO


GO



VIEWALTER TO userId

GO

use ltprefixgtidconfigdbltsuffixgt

GO


GO



VIEWALTER TO userId

GO

Note The whole script must be run at once

Note The loginId and passwordmust be the same as used for Kony Fabric Installation

Note The ltprefixgt and ltsuffixgt providedmust be the same across the script andmust also

be provided at the time of the Kony fabric Installation

Note You can use the same loginId and userId to avoid confusion

Note The userIdmust be same across the script



l Issue


installation on IBM DB2 follow these steps

Workaround

Manual Steps

Important Only DB2 database administrator (DBA) or equivalent DB user will have access

to a create database

1 Create a user based on your Operating System level

l Refer for linux Creating group and user IDs for a DB2 database installation (Linux

and UNIX)

l Refer for Windows Creating a dedicated DB2 user (Windows)

2 Create databases by logging as Admin with following queries

CREATE SCHEMA ltprefixgtADMINDBltsuffixgt AUTHORIZATION userid

CREATE SCHEMA ltprefixgtMFCONSOLEDBltsuffixgt AUTHORIZATION

userid

CREATE SCHEMA ltprefixgtMFACCOUNTSDBltsuffixgt AUTHORIZATION

userid

CREATE SCHEMA ltprefixgtMFREPORTSDBltsuffixgt AUTHORIZATION

userid

CREATE SCHEMA ltprefixgtKPNSDBltsuffixgt AUTHORIZATION userid

CREATE SCHEMA ltprefixgtIDCONFIGDBltsuffixgt AUTHORIZATION userid

3 Grant database level permissions to the user



GRANT CREATEINALTERINDROPIN ON SCHEMA

ltprefixgtADMINDBltsuffixgt TO userid


ltprefixgtMFCONSOLEDBltsuffix TO userid


ltprefixgtMFACCOUNTSDBltsuffixgt TO userid


ltprefixgtMFREPORTSDBltsuffixgt TO userid


ltprefixgtKPNSDBltsuffixgt TO userid


ltprefixgtIDCONFIGDBltsuffixgt TO userid

4 Grant schema level permissions to the user

GRANT createtabCONNECTDATAACCESSIMPLICIT_SCHEMAACCESSCTRL

ON database TO USER userid




l Issue

Authmigrations fail with the following AccessDenied error

ERRORmainactionLogFlywayJavaMigrations17installCoreERROR

Unable to obtain Jdbc connection from DataSource

(jdbcmariadbodc3dmv-mf-

db01indcgov3306relaxAutoCommit=true) for user madmin



Could not connect Access denied for user madminodc3dmv-mf-

web02indcgov (using password YES)

Workaround

The password used for the Authmigrationsmust not contain exclamationmarks ()

l Issue

If you are using any lower versions of MySQL 57 such as v5712 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





l SQL State HY000

l Error Code 1093



l Workaround

To resolve this issue refer Prerequisites for Kony Fabric with MySQL- Applicable for Identity

Services



121 HostnamePort changes for Tomcat Application Server

Kony Fabric On-Premises Installer provides a script to change the Hostname or Port of the installed

Kony Fabric instance In your installed Tomcat Application Server youmust also perform the following

changes

In tomcatwebappsapiportalWEB-INFclassesconfigproperties

replace the existing URLwith the new URL in the following fields

l KONY_ACCOUNT_API_BASE_URL=

l KONY_DEVELOPER_PORTAL_BASE_URL=

In tomcatwebappsmfconsoleWEB-INFclassesconfigproperties

replace the existing URLwith the new URL in the KONY_ACCOUNT_API_BASE_URL= field

In tomcatconfserverxml replace the port number with the new port number in the

ltConnector server=Kony port= field

In tomcatwebappsaccountsWEB-INFclassesaccountsproperties

replace the port number with the new port number in the following fields

l KONY_INTEGRATION_SERVICE_PORT=

l KONY_MESSAGING_SERVICE_PORT=

122 HostnamePort changes for JBoss Application Server


Kony Fabric instance The script can be found in the installation folder In your installed JBoss

Application Server youmust follow the instructions in the script and also perform the following steps

1 In the standalonexml file replace the IP addressport number with the new IP addressport

number



2 InmfconsolewarWEB-INFclassesconfigproperties replace the

existing URLwith the new URL in the KONY_ACCOUNT_API_BASE_URL= field

3 InapiportalwarWEB-INFclassesconfigproperties replace the

existing URLwith the new URL in the following fields



4 InaccountswarWEB-INFclassesaccountsproperties replace the

port number with the new port number in the KONY_INTEGRATION_SERVICE_PORT= field

123 How to Configure JBoss Cluster

l Refer to httpsaccessredhatcomsolutions218053 to setup EAP in Domainmode

l Refer to httpsdocsjbossorgmod_cluster110htmlQuick_Start_Guidehtml to configure the

mod_cluster

l Refer to httpsaccessredhatcomsolutions2332111 to integrate themod_cluster with

JBoss

124 How to Configure a Custom JAR File on WebLogic

When an administrator installs only integration services onWebLogic and would like to use it as a

standalone server (without integrating to Kony Fabric) for Kony Studio apps then app serviceswhich

use custom code for pre-processor and post-processor will fail For these services to work properly

add the custom code jar file to middlewarewar and redeploy

To add custom jar to middlewarewar after installation follow these steps

1 Uninstall themiddlewarewar file fromWebLogic Console gt Deployments tab

2 Go to your Kony Integration Server install location and Deployments folder

3 Open themiddlewarewar file and do the following



4 In themiddlewarewar file go toWEB-INFlib folder and add custom jar file

5 Save the middlewarewar file

6 Deploy the middlewarewar file back to server

125 How to Configure Heap and PermGen Size

1251 Configuring Heap and PermGen Size for Tomcat

By default the heap settings for Tomcat allocated areMin -Xms1024m Max - Xmx2048m and default

permgen settings are -XXPermSize=1024m -XXMaxPermSize=1024m

For better performance in case of several publishes update the following heap and permgen settings

in the file Installation directorytomcatbincatalinabat

l heap settings Min -Xms1024m Max - Xmx1024m

Important While installing Kony Fabric Components including Integration services set the

heap settings to Min -Xms2048m Max - Xmx2048m

l permgen settings -XXPermSize=1024m -XXMaxPermSize=2048m

1252 Configuring Heap and PermGen Size for JBoss

In case of multinode do the following

l Configure theMin -Xms2048m Max - Xmx4096m heap settings in the file Server

directory domainconfigurationhostxml


directory domainconfigurationdomainxml




In case of single node configure the settings in Install directory

jbossstandaloneconfigurationstandalonexml

1253 Configuring Heap and PermGen Size for WebLogic

Configure theMin -Xms2048m Max - Xmx4096m heap settings in the file Server directory

user_projectsdomainsbinsetDomainEnvcmd

Configure permgen settings -XXPermSize=1024m -XXMaxPermSize=2048m

1254 Configuring Heap and PermGen Size for WebSphere

For configuring Heap Size inWebSphere click How to Configure Heap Size - WebSphere

126 How to Configure Kony Fabric Behind a Reverse Proxy

If you want to access everything via a proxyURL including Kony Fabric Console (for example design

time for your app developers) and authService and integration services (for example runtime from

users using your apps) follow these steps

1 Install Kony Fabric with internal details like your internal IP and HTTP port

2 After installation stop Kony Fabric Console (without configuring authservice details) and update

the below properties files

a In the accountswarWEB-INFclasses folder open the

accountsproperties file and update theWAAS_BASE_URL=ltPUBLIC_

URL_OF_YOUR_APACHEgtworkspace property with a public URL instead of the

private URL By default the private URL is set during installation

Examples of proxyURLs

l WAAS_BASE_URL=httptestkonycomworkspace

l WAAS_BASE_URL=httpstestkonycom8443workspace



l WAAS_BASE_URL=httptestkonycom8080workspace

b Following are the changes to bemade in the war for each App Server

l Tomcat In mfconsolewarWEB-INFclasses open the

configproperties file and update the KONY_ACCOUNT_API_BASE_

URL=ltPUBLIC_URL_OF_YOUR_APACHEgtaccountsapiv1_0 property

with a public URL instead of the private URL that was generated during

installation

l JBoss - Standalone (Bundled JBoss) In

Standalonedeploymentsmfconsolewar open the




installation

l JBoss - Pre-configured and Domain mode Take a backup of the existing war

Undeploymfconsolewar In mfconsolewarWEB-INFclasses open

theconfigproperties file update the KONY_ACCOUNT_API_BASE_



installation and re-deploy the war file

l WebSphere Take a backup of the existing war Undeploymfconsolewar In

mfconsolewarWEB-INFclasses open theconfigproperties

file update the KONY_ACCOUNT_API_BASE_URL=ltPUBLIC_URL_OF_YOUR_

APACHEgtaccountsapiv1_0 property with a public URL instead of the

private URL that was generated during installation and re-deploy the war file

l WebLogic In mfconsolewarWEB-INFclasses open the






installation

3 Start Kony Fabric Console

4 Launch your Kony Fabric Console in browser by usingltPUBLIC_URL_OF_YOUR_

APACHEgtmfconsole The auth setup page appears

5 Enter the auth URLwith public URL likeltPUBLIC_URL_OF_YOUR_

APACHEgtauthService If you provide an internal IP here appconfig will show internal

IPs

6 Also after log in to Kony Fabric Console while registering server provide thePUBLIC_URL to

register integration server Now all the URLswill have the public hostnames

If you want to give public access only to runtime services like authservice and integration

services you can skip step 2 and step 3 from the above procedure This will make sure service

docwill have all public URLs

Note Proxy configuration should have preserver host directive for Kony Fabric to work

correctly after start up

For example in case of apache proxy use ProxyPreserveHost On

and in case of NGINX use proxy_set_header Host $host (For more

information refer Passing request headers)

127 Preserving Proxy if Load Balancer or Proxy Server is Configured

When you use a load balancer or a proxy server inWebSphere the port number on which the web

application server is listening is added to an incoming request This addition redirects the load balancer

to the load balancer host It also adds the default port number (Port Number 9443) to the request

To stop the load balancer from redirecting to the load balancer host add the following properties in

Application Servers gt Server name gt Web Container Settings gt Custom Properties



l comibmwswebcontainerextractHostHeaderPort

l trusthostheaderport

For more information you can refer to IBMSupport

128 How to Configure Frontend HTTPS to Tomcat HTTP Redirection

If you are installing Kony Fabric on Tomcat on HTTP and wants to route requests via HTTPS apache

or loadbalancer add a connector in thetomcatserverxml with the following attributes

proxyName=ltProxyHostgt proxyPort=ltProxyPortgt scheme=https secure=true

Example

ltConnector server=KonyTEST port=8080 protocol=HTTP11

proxyName=mbaastest10konylabsnet proxyPort=443 scheme=https

secure=true maxHttpHeaderSize=8192 maxThreads=150

enableLookups=false acceptCount=25 disableUploadTimeout=true

tcpNoDelay=true compression=on

compressableMimeType=textcsstextjavascripttexthtml

connectionTimeout=20000 URIEncoding=UTF-8gt

129 WebSphere FAQs

Refer toWebSphere FAQs

1210 How to Change Log Levels

Kony Fabric Console contains three components portal accounts and workspace

For console log files by default log level value is set toINFO



l The following are the log file names for the console components

o mbaasportallog (for mbaas portal)

o accountsServicelog (for accounts)

o andworkspaceServicelog (for workspace)

l For Identity services the log file isauthServicelog The default log level for identity

services is set toINFO

l For Integration services the log file ismiddlewarelog The default log level for integration


l For Engagement Services the log file iskmslog The default log level for Engagement

Service is set toINFO

To change log levels for mbaasportallog follow these steps

1 Go toltKony Fabric install

directorygtdeploymentsmfconsolewarWEB-INFclasses and open

theconfigproperties file

2 Change the log level to the required value


To change log levels for accountsServicelog follow these steps

1 Go toaccountsdb -gt accounts_configurations table search for key

KONY_ACCOUNTS_LOG_LEVEL


To change log levels for workspaceServicelog follow these steps



1 Go toltmfconsoledb -gt property table search for key LOG_LEVEL


To change log levels for authServicelog follow these steps


directorygtdeploymentsauthServicewarWEB-INFclasses and

open theauthServiceproperties file


3 Redeploy theauthServicewar file

To change log levels for middleware logs follow these steps

1 Go toadmin db gt server_configuration table and search for ltKony

Fabric install diSERVER_LOG_LEVEL


To change log levels for metricslog follow these steps

1 Go toreportsdb -gt metrics_configuration search for keyKONY_

METRICS_LOG_LEVEL


To change log levels for Engagement Services logs follow these steps


directorygtdeploymentskpnswarWEB-INF and open the kms-

log4j2xml file





For more details on Logs in Kony Fabric refer to

httpcommunitykonycomblogskonyfabricaccessing-logs-kony-konyfabric-premise-install

1211 Context Root-path

A context root identifies aWeb application archive (WAR) file in an application server The context root

of aWeb application determineswhich URLs application server will delegate to your web application

When Kony Fabric installed the required components WARs are deployed to an app server By

default a default context path based on the name of the deployment is usedWhen you reinstall Kony

Fabric on the same app server the newly installed instance overrides the first instance

With context root configuration for Kony Fabric you can install multiple sets of Kony Fabric instances

on one app server such as for Dev_Instance QA_Instnace andProd_Instance

A context root for eachWebmodule of Kony Fabric (for example mfconsolewar

accountswar workspacewar adminwar serviceswar

middlewarewar andkpnswar) is defined in the application deployment descriptor during

application assembly

You can use this field to assign a different context root to aWebmodule The context root is combined

with the defined servlet mapping (from theWAR file) to compose the full URL that users type to access

the servlet For example if the context root is myapphome and the servlet mapping is

MyFirstPage then the URL is httphostportmyapphomeMyFirstPage

For example You have installed the Kony Fabric Console and the integration services on one app

server AppServer1 And you are required to install Kony Fabric Components (console identity

services integration services and engagement services) to the same AppServer1 You can install

multiple instances of Kony Fabric on the AppServer1 app server by configuring the context root-path

for each instance separately The following sections help you configure context root path for Kony

Fabric



l Approach 1 Changing Context Root Path after the installation using the Installer

l Approach 2 Changing Context Root usingManual Install Steps

l Accessing Context Based Root Kony Fabric Instance through Visualizer Enterprise (after you

setup context root path as above you can also access context based root Kony Fabric in

Visualizer)

12111 Approach 1 Changing Context Root Path after the installation using the

Installer

1 Install Kony Fabric using the Installer

Important During Kony Fabric installation or after installation is completed you should not

configure details in the Administrator Account Configuration window

2 Rename the war files for required components

l For Tomcat standalone and JBoss standalonemodes rename theWARs directly from proper

install location

l For WebLogic andWebSphere and JBoss domainmode follow these steps to rename

WARs

i Rename the requiredWARs from the installation location

ii Go to Console

iii DeleteWARs for those you have renamed

iv Redeploy the renamedWARs to the Console

The following table details the list of installedWAR files and installation locations for Kony Fabric

Components



Component

File Name RenamedWAR files

Path for installed WAR files forKony Fabric

Consol

e

workspacewa

r

workspace

1war

l Tomcat (standalonemode)

ltKony Fabric Install

Pathgttomcatwebapps

l JBoss (standalonemode) ltKony

Fabric Install

Pathgtjboss gt

standalonedeployments

l WebLogic

ltUserInstallDirectorygt

deployments

l WebSphere lt

UserInstallDirectorygt

deployments



Component



mfconsolewar mfconsole

1war

accountswar accounts

1war

Identity authServicew

ar

authServic

e1war

Integra

tion

Admin

Server

l middle

warew

ar

l service

swar

l admin

war

l mid

dlew

are

1

war

l serv

ices

1

war

l adm

in

1

war

Engag

ement

Service

s

kpnswar kpns1war



3 Update WAAS_BASE_URL in the accounts_configurations table by using the following

SQL query

For example ltprefixgtmfaccountsdbltsuffixgt

Sample query for UPDATE STATEMENT

l MySQL

UPDATE accounts_configurations SET value=lthttp or

httpsgtltserver_hostgtltserver_portgtworkspace1 WHERE

name=WAAS_BASE_URL

l Oracle



name=WAAS_BASE_URL

l SQLServer



name=WAAS_BASE_URL

l DB2



name=WAAS_BASE_URL

Note FromV8 SP4 FP1HF1 onwards DB2 is not supported for bundled Tomcat

and JBoss servers



4 Open the renamed mfconsole1war and do the following

a Update the following property in the configproperties file

l KONY_ACCOUNT_API_BASE_URL=lthttp or httpsgtltserver_

hostgtltserver_portgtaccounts1apiv1_0

The location for configproperties mfconsole1warWEB-INFclasses

Note AWAR file location varies based on an app server - for example for

Tomcat WARs are found at ltINSTALL_DIRgttomcatwebapps

b Add the following properties in the configproperties file

l KONY_ACCOUNTS_HEALTHCHECK_URL=lthttp or

httpsgtltserver_hostgtltserver_portgtaccounts1health_

check

l KONY_WORKSPACE_HEALTHCHECK_URL=lthttp or

httpsgtltserver_hostgtltserver_

portgtworkspace1apiv1healthcheck

5 Update the following property in the KONY_SERVER_SERVICES_CONTEXT_PATH in the

admindb configuration table

KONY_SERVER_SERVICES_CONTEXT_PATH=services1

For example ltprefixgtadmindbltsuffixgt


l MySQL

UPDATE server_configuration SET prop_value =services1 WHERE

prop_name = KONY_SERVER_SERVICES_CONTEXT_PATH



l Oracle



l SQLServer



l DB2



Note If the property does not exist create KONY_SERVER_SERVICES_

CONTEXT_PATH

6 Configure the following settings for application server as follows

l For Tomcat In case you have renamed a war modify the following datasource file

names as per the respective renamedwar files

Path for datasource files

ltINSTALL_DIRgtltApp_ServergtconfCatalinalocalhost

l Rename accountsxml to account1xml

l Rename workspacexml to workspace1xml

l Rename authServicexml to authService1xml

l Rename adminxml to admin1xml

l For JBoss update serviceswarWEB-INFjboss-webxml with the new

serviceswar name



For example if services is renamed to services1 then services1warWEB-

INFjboss-webxml

From

ltcontext-rootgtservicesltcontext-rootgt

To

ltcontext-rootgtservices1ltcontext-rootgt

l For WebLogic update the new context path in the mfconsole1warWEB-

INFweblogicxmlwith the new serviceswar name

For example If mfconsole is renamed to mfconsole1 then

mfconsole1warWEB-INFweblogicxml

From

ltcontext-rootgtmfconsoleltcontext-rootgt

To

ltcontext-rootgtmfconsole1ltcontext-rootgt

l For WebSphere while deployingWARs toWebSphere enter the context root values for

renamedWARs as required

For more details on deployment of WARs inWebSphere refer to DeployingWAR Files

toWebSphere

7 Restart your app server

8 Launch Kony Fabric Console with new context path and do the registration using the new auth

service URL formatlthttp or httpsgtltserver_hostgtltserver_portgtltnew mfconsole

context pathgt



For example lthttp or httpsgtltserver_hostgtltserver_

portgtltmfconsole1gt

Note You will need to launch Kony Fabric through a browser and complete the registration

for the context based root instance

For more details refer to How to Get StartedWith Kony Fabric Console

Note After you complete registration you can now also launch a context based root Kony

Fabric through Visualizer Enterprise Refer to Access Kony Fabric Instance through

Visualizer Enterprise

9 After you logged in to Console create an environment with the new URLs

To create server feature with new context path the URL format is lthttp or

httpsgtltserver_hostgtltserver_portgtltnew admin context pathgt

If admin is renamed to admin1 then the sample URL format is as follows

lthttp or httpsgtltserver_hostgtltserver_portgtadmin1

10 Update service_url after an environment is registered in the accountsdb table as

follows

Sample query for UPDATE STATEMENT (for MySQLOracleMSSQLDB2)

l UPDATE features SET service_url = lsquolthttp or httpsgtltserver_

hostgtltserver_portgtadminservices1rsquo WHERE type = server


hostgtltserver_portgtkpns1rsquo WHERE type = kpns

Note You can now use Kony Fabric Console with new context paths for your app

development

11 Create an app in Kony Fabric Console



12 Publish the app

12112 Approach 2 Changing Context Root using Manual Install Steps

1 Install Kony Fabric usingmanual steps provided in Kony FabricManual Installation Guide


l For Tomcat standalone and JBoss standalonemodes rename theWARs directly from

proper install location


WARs


ii Go to Console



The following table details the list of installedWAR files and installation locations for Kony

Fabric Components



Component

File Name RenamedWARfiles


Conso

le

workspace

war

workspac

e1war



Pathgttomcatwebapps

l JBoss (standalonemode)


Pathgtjboss gt

standalonedeploymen

ts

l WebLogic

ltUserInstallDirector

ygtdeployments

l WebSphere lt

UserInstallDirectory

gtdeployments



Component



mfconsolew

ar

mfconsole

1war



Component



accountswa

r

accounts

1war



Component



Identit

y

authService

war

authServi

ce1war

Integr

ation

Admin

Server

l middl

eware

war

l servic

eswa

r

l admin

war

l mi

ddl

ew

are

1

w

ar

l ser

vic

es

1

w

ar

l ad

mi

n1

w

ar

Engag

ement

Servic

es

kpnswar kpns

1war




SQL query



l MySQL



name=WAAS_BASE_URL

l Oracle



name=WAAS_BASE_URL

l SQLServer



name=WAAS_BASE_URL

l DB2



name=WAAS_BASE_URL


and JBoss servers













check









l MySQL





l Oracle



l SQLServer



l DB2




CONTEXT_PATH


and JBoss servers



6 Configure the following properties with the customized JNDI names

Component

File Name File Name Properties to beaddedupdated

authS

ervice

authServiceproper

ties

authServicewar

WEB-INFclasses

l WEBSPHERE_

AUTHCONFIGDB_

JNDI_

NAME=jdbcauthconfig

l WEBSPHERE_

AUTHGLOBALDB_

JNDI_

NAME=jdbcauthglobal

db

Works

pace

workspaceService

properties

WorkspacewarW

EB-INFclasses

l WEBSPHERE_

WAASGLOBALDB_

JNDI_

NAME=jdbcworkspac

esglobaldb

l WEBSPHERE_

WORKSPACESDB_

JNDI_

NAME=jdbcworkspac

esglobaldb



Component


Accou

nts

accountspropertie

s

AccountswarWE

B-INFclasses

l ACCOUNTS_DB_

JNDI_

NAME=jdbckonyacco

unts REPORTS_DB_

JNDI_

NAME=jdbckonyreport

s

Integr

ation

Admin

Server

serverconsoleprop

erties

adminwarWEB-

INFmiddlewarem

iddleware-

bootconfigadmin

l admindbjndiname=jdb

ckonyadmindb

l reportsdbjndiname=jd

bckonyreports













serviceswar name


INFjboss-webxml

From


To






From


To





toWebSphere






context pathgt







Fabric through Visualizer Enterprise refer to Access Kony Fabric Instance through








follows







development




13 Publish the app

12113 Accessing Context Based Root Kony Fabric Instance through Visualizer Enter-

prise

After you complete registration for a context based root for a Kony Fabric instance by using the

installer or manual steps you can now also launch the context based Kony Fabric through Visualizer

Enterprise

To access a context based root Kony Fabric instance through Visualizer follow these steps

1 Add the below keys in the eclipseini file as follows

a Navigate to the folder where Kony Visualizer is installed

For example ltVisualizerEnterpriseInstallFoldergt_KonyVisualizer_installation

b Open the eclipseini file and add the following keys at the end of the file

-Dkonymfconsolecontext=ltnew mfconsole context pathgt For

example mfconsole1

-Dkonymfaccountscontext=ltnew accounts context pathgt For

example accounts1

-Dkonymfworkspacecontext=ltnew workspace context pathgt

For example mfworkspace1

-Dkonymfidentitycontext=ltnew identity context pathgt For

example mfidentity1

2 Save the eclipseini file

3 Launch Visualizer Enterprise



4 Configure Kony Fabric in Kony Visualizer

For more details refer to Configure Kony Fabric in Kony Visualizer

You can now access context based root Kony Fabric Console through Visualizer

5 Configure the HeadlessBuildproperties file for contexts that you have configured for

Kony Fabric as follows

a Open the HeadlessBuildproperties file Refer to Configure the

HeadlessBuildproperties File

b In the HeadlessBuildproperties file add the required contexts at the end of the

file

For example

l For console the URL contextpathconsole=console1

l For identity the URL contextpathidentity=identity1

l For workspace the URL contextpathworkspace=workspace1

l For accounts the URL contextpathidentity=accounts1

Note The headless-buildproperties configuration is required only for CI

build

6 Save the file

7 Launch Kony Fabric Console through Visualizer You can now build apps using new context

based Kony Fabric instance

For more details on how to add applications refer to Kony Fabric User Guide

For more details on designing an app adding actions and skins and building apps using

Visualizer refer to Kony Visualizer User Guide


1 Preface

11 Purpose




15 Contact Us

2 Prerequisites



23 Network Settings








































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



55 Configure Load Balancers for Sending Host Information in Multinode




571 MySQL


572 SQL Server


574 Oracle


575 MariaDB



581 JBoss

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






582 WebLogic

5821 Increase JVM memory for WebLogic Server



583 WebSphere












6123 Installing Kony Fabric on a Domain Mode (Multi node installation in pre-configured JBoss cluster)





71 Tomcat Server

72 JBoss Server


73 WebLogic Server

74 WebSphere Server





83 Prerequisites


841 Prerequisites





92 Prerequisites







113 How to Update Security Configuration in Configxml (Required in case of WebLogic installation)






118 Configuring Datasource for performance improvements for JBoss pre-existing and Domain Mode






















129 WebSphere FAQs



12111 Approach 1 Changing Context Root Path after the installation using the Installer


12113 Accessing Context Based Root Kony Fabric Instance through Visualizer Enterprise


Copyright copy 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 SAPreg and SAPreg Business Suitereg 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



Metrics Component


Fabric 82





WebSphere



andWebSphere













Table of Contents

1 Preface 13

11 Purpose 14




15 Contact Us 16

2 Prerequisites 17




































TLS v12 40



















571 MySQL 64


572 SQL Server 64


574 Oracle 65




575 MariaDB 67



581 JBoss 68





JBossCluster 69




582 WebLogic 72




583 WebSphere 73





















72 JBoss Server 289

























installation) 333









DomainMode 337






























Enterprise 392



1 Preface


















andOAuth Provider


Yahoo













services They are



met


Objects







11 Purpose












l File path

l Commands

l Program code

l File names

Italic l Emphasis


l New terminology

Bold l Windows

l Menus

l Buttons

l Icons

l Fields

l Tabs







systems or data


Document Purpose

Kony Fabric User

Guide



15 Contact Us






2 Prerequisites







Memory 16GB





23 Network Settings



Direction

Action

Description

Engage

ment

Server


Engagem

ent Server

to access

Apple

APNS

HTTP2

production

URL

Engage

ment

Server


nd

Allow Allow the

Engagem

ent Server

to access

the JPush

notificatio

n server

URL

Engage

ment

Server


4433device


Engagem

ent Server

to access

Apple

APNS

HTTP2

developm

ent URL




Direction

Action

Description

Engage

ment

Server


nd

Allow Allow the

Engagem

ent Server

to access

Firebase

Cloud

Messagin

g (FCM)

service

Engage

ment

Server



170008 (17001 to 17255255254)

2196 TCP Outbou

nd

Allow Allow the

Engagem

ent Server

to access

APNS

feedback

service

Engage

ment

Server

gatewaypushapplecom


170008 (17001 to 17255255254)

2195 TCP Outbou

nd

Allow Allow the

Engagem

ent Server

to access

Apples

APNS

Engage

ment

Server

All subdomains of


Push URL



pushRequest

443 TCP Outbou

nd

Allow Allow

connect to

Blackberr

y Cloud

through

this port




Direction

Action

Description

Engage

ment

Server


nd

Allow Allow

connect to

Windows

Cloud

(MPNS)

through

this port

Engage

ment

Server


nd

Allow Allow

connect to

Windows

Cloud

(WNS)

through

this port

Internal

Corporat

eWiFi

router for

Android

Mobile

Devices






5228

52295

230

TCP

HTTP

HTTP

S

UDP

Both Allow Android

devices

will

connect to

GCM

through

this port

Internal

Corporat

eWiFi

router for

iOS

Devices

gatewaypushapplecom




170008 (17001 to 17255255254)


devices

connect to

APNS

servers

through

this port




Direction

Action

Description

Internal

Corporat

eWiFi

router for

iOS

Devices


devices

will

connect to

public

Apple

OCSP

and

iTunes

service

through

this port

Internal

Corporat

eWiFi

router for

Window

Devices




TCP

HTTP

HTTP

S

UDP

Both Allow Windows

devices

will

connect to

WNS

through

this port

Internal

Corporat

eWiFi

router for

Window

Devices


MPNS URL



TCP

HTTP

HTTP

S

UDP

Both Allow Windows

devices

will

connect to

MPNS

through

this port


























Servicerdquo



l 5420819284

l 54208192248








use
















objects













5120M





















CONTAINER=CURRENT


CONTAINER=CURRENT


CONTAINER=CURRENT
















version


servers












big pagesize of 32k





COMMIT



IBMDEFAULTGROUP


AUTOMATIC



COMMIT



IBMDEFAULTGROUP




AUTOMATIC



COMMIT



IBMDEFAULTGROUP


AUTOMATIC



COMMIT


IBMTEMPGROUP


EXTENTSIZE 1M


COMMIT

CONNECT RESET


























both editions








collation support







[client]


[mysql]


[mysqld]|






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


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




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



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


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











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




database





l SQL State HY000

l Error Code 1093










































servers






servers



















ltglobal-modulesgt


ltglobal-modulesgt

6 Save the changes




JBoss



ltinterfacesgt



ltinterfacegt





ltinterfacegt

ltinterfacesgt












inheritance=DEEPgt|

ltsubsystemgt



l standalonebat




l standalonesh
















ltsslgt




ltsslgt


ltsecurity-realmgt




































binding=connectgt









credentialsgt























D parameter








JVM arguments


















l Set JVM heap size














this is port 8880






8880 SOAP_

CONNECTOR_

ADDRESS













is sent


secure















(for Java7)










































and authorization



role






roles

Workspace

(WaaS)






application

API Developer

Portal








Environments

(Engagement

Services

Integration

Services)































Installation



Install Guide


node (Domain Mode)














Multinode


WindowsVersion112



local environment


installations


Console

l Workspace

l Accounts

Identity

Integration

l Admin

l Middleware

l Services

l Metrics


Engagement Services














link




n READMEtxt


database


















appears






appears





























HKEY_LOCAL_






below




running


Multinode



in the headers






For example













l local_policyjar






policyfileshtml












l local_policyjar


l READMEtxt













571 MySQL




application size



packet=1010241024








572 SQL Server









700enuauthx64)

574 Oracle




component


















i Connect as SYSDBA

sqlplus as sysdba



sysaux


creation




Conn mdsyssecret


creation






like SDO














edition licensing



575 MariaDB







minimum value




581 JBoss


Load Balancer)



proxy-port details

For example








ltinterfacesgt



ltinterfacegt



ltinterfacegt





configuration



ltinterfacegt



ltinterfacegt

ltinterfacesgt








domainxml file




ltsubsystemgt --gt




JBoss







-Xms2048m

-Xmx4096m



shown below








gt

ltsubsystemgt







settings









582 WebLogic

























583 WebSphere











java executablegt









Custom Properties














changes













20spec





Machine




































issue
















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example























usersxml








configuration table

15 Click Next











































foldergtkeystorejks











will generate










details


displayed
















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example













location








ltContextgt



river










testWhileIdle=true



url=jdbcsqlserver














testWhileIdle=true



url=jdbcsqlserver





ltContextgt








to 3306 for MariaDB



user











































special characters











message

























Mode)














issue
















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example



































l




16 Click Next











































foldergtkeystorejks











will generate










details


displayed
















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example








to 3306 for MariaDB



user











































special characters











message






















For Tomcat


following locations


















For JBoss


following locations




















For WebLogic


following locations






















you used the cuser_










For WebSphere


following locations

































issue
















option





types


























box




Services check box





check box



Kony Fabric Console







components











For example



















14 Click JBoss


















portgt





















example dbclient


user



















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL








database user




example






to 3306 for MariaDB



user











































special characters











message




















cluster)



























types


























box




Services check box





check box



Kony Fabric Console





Reports Database











For example





































system



























example dbclient


user
























USERS


following

l Data Tablespace



















database user




example










Password





set to 1433 for SQL








database user




example






to 3306 for MariaDB





user






















window appears






















special characters







message







not authenticated













For Tomcat




















For JBoss






















For WebLogic
























you used the cuser_










For WebSphere



























Fabric components






issue
















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example


























Components








Server










window shown below






path










folder





For Example





PATH

















For Example





PATH

















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example








5000 for DB2






example USERSPACE1


following

l Data Tablespace

















user









DB2Database version









license_cujar


example








to 3306 for MariaDB



user






























message





















Fabric components






issue
















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example


































Server























window shown below


r=server1












Important






















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example








5000 for DB2






example USERSPACE1


following

l Data Tablespace

















user









DB2Database version









license_cujar


example








to 3306 for MariaDB



user
























Important

















message
























Fabric Console












extract the file


located













configurations

71 Tomcat Server




72 JBoss Server








Documentation

73 WebLogic Server









documentation

74 WebSphere Server








documentation



















l Oracle




pk drop index







l MySQL







l DB2




pk



NULL





l MS SQL Server


GO


GO




version_pk]

GO


GO



GO


(50) NULL

GO














issue




83 Prerequisites




















option





Upgrade

























message




















library











issue




841 Prerequisites


your credentials




































l authServicekey











successful upgrade












message








l Oracle





l MySQL



l DB2



l MS SQL Server


























Windows


WindowsVersion112





For example



apply701x patches




installation



l 701 GA

l 71 GA

l 72 GA

l 73 GA

l V8

l V8 SP2

l V8 SP3 FP1



Windows


WindowsVersion112

92 Prerequisites


























Windows


WindowsVersion112








Windows


WindowsVersion112


with the upgrade



samplezip


in this field





Windows


WindowsVersion112











Windows


WindowsVersion112



message



Windows


WindowsVersion112





Windows


WindowsVersion112






following
























the database


selected





future use






























































































encryptedgt tag



For example






















5 Save the changes



































l JBossMulti-node


l WebLogic

l WebSphere
















ltpoolgt






ltpoolgt







Passed





DBPASSED



healthDetail









version8211_GA
















l sapjco3jar









folder






l sapjco3jar




path=sapjco3jargt





files

l sapjco3jar




path=sapjco3jargt





ltglobal-modulesgt


ltglobal-modulesgt



l sapjco3jar


















l sapjco3jar










l Issue


Workaround


For MySQL

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



For SQLServer

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



For Oracle

----------



For DB2

--------






JBoss servers

l Issue



publish fails

Workaround


database

l Issue



Workaround



Server




















new values





running on Tomcat









l Issue




Workaround


table_open_cache=64


l Issue






Workaround









l Issue


authenticated

Workaround






Workaround










null



Workaround


l Issue



Workaround



Fabric



Workaround






configuration





INFclasses




INFclasses


value in all nodes



INFclasses




Workaround






configuration





INFclasses




INFclasses


value in all nodes



INFclasses


For example

Caused by




file_size

Workaround


themyini file



l Issue



Workaround



l Issue



Workaround







version_rank



l Issue




from oracle

Workaround



l Issue



Workaround



l Issue


652GA to 72GA

Workaround






l Issue



Workaround




l Issue



Workaround

Manual Steps






















































l Issue


Workaround

Manual Steps












l Issue



Workaround

Manual Steps








GO

use msdb

GO


GO




GO


GO


GO


GO






GO


GO


GO


GO




GO


GO


GO


GO




GO


GO


GO



VIEWALTER TO userId

GO


GO




GO


GO



VIEWALTER TO userId

GO


GO


GO



VIEWALTER TO userId

GO









l Issue



Workaround

Manual Steps





and UNIX)





userid


userid


userid
























l Issue










Workaround


l Issue








l SQL State HY000

l Error Code 1093



l Workaround


Services






changes


















number














mod_cluster


JBoss
































































installation






installation


















installation






IPs


























Example








129 WebSphere FAQs












































METRICS_LOG_LEVEL





log4j2xml file




























Fabric







Visualizer)


Installer






install location


WARs


ii Go to Console




Components



Component



Consol

e

workspacewa

r

workspace

1war



Pathgttomcatwebapps


Fabric Install

Pathgtjboss gt


l WebLogic


deployments

l WebSphere lt


deployments



Component




1war


1war


ar

authServic

e1war

Integra

tion

Admin

Server

l middle

warew

ar

l service

swar

l admin

war

l mid

dlew

are

1

war

l serv

ices

1

war

l adm

in

1

war

Engag

ement

Service

s

kpnswar kpns1war




SQL query



l MySQL



name=WAAS_BASE_URL

l Oracle



name=WAAS_BASE_URL

l SQLServer



name=WAAS_BASE_URL

l DB2



name=WAAS_BASE_URL


and JBoss servers













check









l MySQL





l Oracle



l SQLServer



l DB2




CONTEXT_PATH











serviceswar name




INFjboss-webxml

From


To






From


To





toWebSphere




context pathgt

















follows







development




12 Publish the app







WARs


ii Go to Console




Fabric Components



Component



Conso

le

workspace

war

workspac

e1war



Pathgttomcatwebapps



Pathgtjboss gt

standalonedeploymen

ts

l WebLogic


ygtdeployments

l WebSphere lt


gtdeployments



Component



mfconsolew

ar

mfconsole

1war



Component



accountswa

r

accounts

1war



Component



Identit

y

authService

war

authServi

ce1war

Integr

ation

Admin

Server

l middl

eware

war

l servic

eswa

r

l admin

war

l mi

ddl

ew

are

1

w

ar

l ser

vic

es

1

w

ar

l ad

mi

n1

w

ar

Engag

ement

Servic

es

kpnswar kpns

1war




SQL query



l MySQL



name=WAAS_BASE_URL

l Oracle



name=WAAS_BASE_URL

l SQLServer



name=WAAS_BASE_URL

l DB2



name=WAAS_BASE_URL


and JBoss servers













check









l MySQL





l Oracle



l SQLServer



l DB2




CONTEXT_PATH


and JBoss servers




Component


authS

ervice

authServiceproper

ties

authServicewar

WEB-INFclasses

l WEBSPHERE_

AUTHCONFIGDB_

JNDI_

NAME=jdbcauthconfig

l WEBSPHERE_

AUTHGLOBALDB_

JNDI_

NAME=jdbcauthglobal

db

Works

pace

workspaceService

properties

WorkspacewarW

EB-INFclasses

l WEBSPHERE_

WAASGLOBALDB_

JNDI_

NAME=jdbcworkspac

esglobaldb

l WEBSPHERE_

WORKSPACESDB_

JNDI_

NAME=jdbcworkspac

esglobaldb



Component


Accou

nts

accountspropertie

s

AccountswarWE

B-INFclasses

l ACCOUNTS_DB_

JNDI_

NAME=jdbckonyacco

unts REPORTS_DB_

JNDI_

NAME=jdbckonyreport

s

Integr

ation

Admin

Server

serverconsoleprop

erties

adminwarWEB-

INFmiddlewarem

iddleware-

bootconfigadmin


ckonyadmindb


bckonyreports













serviceswar name


INFjboss-webxml

From


To






From


To





toWebSphere






context pathgt















follows







development




13 Publish the app


prise



Enterprise







example mfconsole1


example accounts1




example mfidentity1













file

For example






build

6 Save the file







1 Preface

11 Purpose




15 Contact Us

2 Prerequisites



23 Network Settings















































571 MySQL


572 SQL Server


574 Oracle


575 MariaDB



581 JBoss







582 WebLogic




583 WebSphere

















71 Tomcat Server

72 JBoss Server


73 WebLogic Server

74 WebSphere Server





83 Prerequisites


841 Prerequisites





92 Prerequisites



































129 WebSphere FAQs







Revision History



Metrics Component


Fabric 82





WebSphere



andWebSphere













Table of Contents

1 Preface 13

11 Purpose 14




15 Contact Us 16

2 Prerequisites 17




































TLS v12 40



















571 MySQL 64


572 SQL Server 64


574 Oracle 65




575 MariaDB 67



581 JBoss 68





JBossCluster 69




582 WebLogic 72




583 WebSphere 73





















72 JBoss Server 289

























installation) 333









DomainMode 337






























Enterprise 392



1 Preface


















andOAuth Provider


Yahoo













services They are



met


Objects







11 Purpose












l File path

l Commands

l Program code

l File names

Italic l Emphasis


l New terminology

Bold l Windows

l Menus

l Buttons

l Icons

l Fields

l Tabs







systems or data


Document Purpose

Kony Fabric User

Guide



15 Contact Us






2 Prerequisites







Memory 16GB





23 Network Settings



Direction

Action

Description

Engage

ment

Server


Engagem

ent Server

to access

Apple

APNS

HTTP2

production

URL

Engage

ment

Server


nd

Allow Allow the

Engagem

ent Server

to access

the JPush

notificatio

n server

URL

Engage

ment

Server


4433device


Engagem

ent Server

to access

Apple

APNS

HTTP2

developm

ent URL




Direction

Action

Description

Engage

ment

Server


nd

Allow Allow the

Engagem

ent Server

to access

Firebase

Cloud

Messagin

g (FCM)

service

Engage

ment

Server



170008 (17001 to 17255255254)

2196 TCP Outbou

nd

Allow Allow the

Engagem

ent Server

to access

APNS

feedback

service

Engage

ment

Server

gatewaypushapplecom


170008 (17001 to 17255255254)

2195 TCP Outbou

nd

Allow Allow the

Engagem

ent Server

to access

Apples

APNS

Engage

ment

Server

All subdomains of


Push URL



pushRequest

443 TCP Outbou

nd

Allow Allow

connect to

Blackberr

y Cloud

through

this port




Direction

Action

Description

Engage

ment

Server


nd

Allow Allow

connect to

Windows

Cloud

(MPNS)

through

this port

Engage

ment

Server


nd

Allow Allow

connect to

Windows

Cloud

(WNS)

through

this port

Internal

Corporat

eWiFi

router for

Android

Mobile

Devices






5228

52295

230

TCP

HTTP

HTTP

S

UDP

Both Allow Android

devices

will

connect to

GCM

through

this port

Internal

Corporat

eWiFi

router for

iOS

Devices

gatewaypushapplecom




170008 (17001 to 17255255254)


devices

connect to

APNS

servers

through

this port




Direction

Action

Description

Internal

Corporat

eWiFi

router for

iOS

Devices


devices

will

connect to

public

Apple

OCSP

and

iTunes

service

through

this port

Internal

Corporat

eWiFi

router for

Window

Devices




TCP

HTTP

HTTP

S

UDP

Both Allow Windows

devices

will

connect to

WNS

through

this port

Internal

Corporat

eWiFi

router for

Window

Devices


MPNS URL



TCP

HTTP

HTTP

S

UDP

Both Allow Windows

devices

will

connect to

MPNS

through

this port


























Servicerdquo



l 5420819284

l 54208192248








use
















objects













5120M





















CONTAINER=CURRENT


CONTAINER=CURRENT


CONTAINER=CURRENT
















version


servers












big pagesize of 32k





COMMIT



IBMDEFAULTGROUP


AUTOMATIC



COMMIT



IBMDEFAULTGROUP




AUTOMATIC



COMMIT



IBMDEFAULTGROUP


AUTOMATIC



COMMIT


IBMTEMPGROUP


EXTENTSIZE 1M


COMMIT

CONNECT RESET


























both editions








collation support







[client]


[mysql]


[mysqld]|






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


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




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



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


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











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




database





l SQL State HY000

l Error Code 1093










































servers






servers



















ltglobal-modulesgt


ltglobal-modulesgt

6 Save the changes




JBoss



ltinterfacesgt



ltinterfacegt





ltinterfacegt

ltinterfacesgt












inheritance=DEEPgt|

ltsubsystemgt



l standalonebat




l standalonesh
















ltsslgt




ltsslgt


ltsecurity-realmgt




































binding=connectgt









credentialsgt























D parameter








JVM arguments


















l Set JVM heap size














this is port 8880






8880 SOAP_

CONNECTOR_

ADDRESS













is sent


secure















(for Java7)










































and authorization



role






roles

Workspace

(WaaS)






application

API Developer

Portal








Environments

(Engagement

Services

Integration

Services)































Installation



Install Guide


node (Domain Mode)














Multinode


WindowsVersion112



local environment


installations


Console

l Workspace

l Accounts

Identity

Integration

l Admin

l Middleware

l Services

l Metrics


Engagement Services














link




n READMEtxt


database


















appears






appears





























HKEY_LOCAL_






below




running


Multinode



in the headers






For example













l local_policyjar






policyfileshtml












l local_policyjar


l READMEtxt













571 MySQL




application size



packet=1010241024








572 SQL Server









700enuauthx64)

574 Oracle




component


















i Connect as SYSDBA

sqlplus as sysdba



sysaux


creation




Conn mdsyssecret


creation






like SDO














edition licensing



575 MariaDB







minimum value




581 JBoss


Load Balancer)



proxy-port details

For example








ltinterfacesgt



ltinterfacegt



ltinterfacegt





configuration



ltinterfacegt



ltinterfacegt

ltinterfacesgt








domainxml file




ltsubsystemgt --gt




JBoss







-Xms2048m

-Xmx4096m



shown below








gt

ltsubsystemgt







settings









582 WebLogic

























583 WebSphere











java executablegt









Custom Properties














changes













20spec





Machine




































issue
















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example























usersxml








configuration table

15 Click Next











































foldergtkeystorejks











will generate










details


displayed
















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example













location








ltContextgt



river










testWhileIdle=true



url=jdbcsqlserver














testWhileIdle=true



url=jdbcsqlserver





ltContextgt








to 3306 for MariaDB



user











































special characters











message

























Mode)














issue
















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example



































l




16 Click Next











































foldergtkeystorejks











will generate










details


displayed
















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example








to 3306 for MariaDB



user











































special characters











message






















For Tomcat


following locations


















For JBoss


following locations




















For WebLogic


following locations






















you used the cuser_










For WebSphere


following locations

































issue
















option





types


























box




Services check box





check box



Kony Fabric Console







components











For example



















14 Click JBoss


















portgt





















example dbclient


user



















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL








database user




example






to 3306 for MariaDB



user











































special characters











message




















cluster)



























types


























box




Services check box





check box



Kony Fabric Console





Reports Database











For example





































system



























example dbclient


user
























USERS


following

l Data Tablespace



















database user




example










Password





set to 1433 for SQL








database user




example






to 3306 for MariaDB





user






















window appears






















special characters







message







not authenticated













For Tomcat




















For JBoss






















For WebLogic
























you used the cuser_










For WebSphere



























Fabric components






issue
















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example


























Components








Server










window shown below






path










folder





For Example





PATH

















For Example





PATH

















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example








5000 for DB2






example USERSPACE1


following

l Data Tablespace

















user









DB2Database version









license_cujar


example








to 3306 for MariaDB



user






























message





















Fabric components






issue
















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example


































Server























window shown below


r=server1












Important






















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example








5000 for DB2






example USERSPACE1


following

l Data Tablespace

















user









DB2Database version









license_cujar


example








to 3306 for MariaDB



user
























Important

















message
























Fabric Console












extract the file


located













configurations

71 Tomcat Server




72 JBoss Server








Documentation

73 WebLogic Server









documentation

74 WebSphere Server








documentation



















l Oracle




pk drop index







l MySQL







l DB2




pk



NULL





l MS SQL Server


GO


GO




version_pk]

GO


GO



GO


(50) NULL

GO














issue




83 Prerequisites




















option





Upgrade

























message




















library











issue




841 Prerequisites


your credentials




































l authServicekey











successful upgrade












message








l Oracle





l MySQL



l DB2



l MS SQL Server


























Windows


WindowsVersion112





For example



apply701x patches




installation



l 701 GA

l 71 GA

l 72 GA

l 73 GA

l V8

l V8 SP2

l V8 SP3 FP1



Windows


WindowsVersion112

92 Prerequisites


























Windows


WindowsVersion112








Windows


WindowsVersion112


with the upgrade



samplezip


in this field





Windows


WindowsVersion112











Windows


WindowsVersion112



message



Windows


WindowsVersion112





Windows


WindowsVersion112






following
























the database


selected





future use






























































































encryptedgt tag



For example






















5 Save the changes



































l JBossMulti-node


l WebLogic

l WebSphere
















ltpoolgt






ltpoolgt







Passed





DBPASSED



healthDetail









version8211_GA
















l sapjco3jar









folder






l sapjco3jar




path=sapjco3jargt





files

l sapjco3jar




path=sapjco3jargt





ltglobal-modulesgt


ltglobal-modulesgt



l sapjco3jar


















l sapjco3jar










l Issue


Workaround


For MySQL

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



For SQLServer

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



For Oracle

----------



For DB2

--------






JBoss servers

l Issue



publish fails

Workaround


database

l Issue



Workaround



Server




















new values





running on Tomcat









l Issue




Workaround


table_open_cache=64


l Issue






Workaround









l Issue


authenticated

Workaround






Workaround










null



Workaround


l Issue



Workaround



Fabric



Workaround






configuration





INFclasses




INFclasses


value in all nodes



INFclasses




Workaround






configuration





INFclasses




INFclasses


value in all nodes



INFclasses


For example

Caused by




file_size

Workaround


themyini file



l Issue



Workaround



l Issue



Workaround







version_rank



l Issue




from oracle

Workaround



l Issue



Workaround



l Issue


652GA to 72GA

Workaround






l Issue



Workaround




l Issue



Workaround

Manual Steps






















































l Issue


Workaround

Manual Steps












l Issue



Workaround

Manual Steps








GO

use msdb

GO


GO




GO


GO


GO


GO






GO


GO


GO


GO




GO


GO


GO


GO




GO


GO


GO



VIEWALTER TO userId

GO


GO




GO


GO



VIEWALTER TO userId

GO


GO


GO



VIEWALTER TO userId

GO









l Issue



Workaround

Manual Steps





and UNIX)





userid


userid


userid
























l Issue










Workaround


l Issue








l SQL State HY000

l Error Code 1093



l Workaround


Services






changes


















number














mod_cluster


JBoss
































































installation






installation


















installation






IPs


























Example








129 WebSphere FAQs












































METRICS_LOG_LEVEL





log4j2xml file




























Fabric







Visualizer)


Installer






install location


WARs


ii Go to Console




Components



Component



Consol

e

workspacewa

r

workspace

1war



Pathgttomcatwebapps


Fabric Install

Pathgtjboss gt


l WebLogic


deployments

l WebSphere lt


deployments



Component




1war


1war


ar

authServic

e1war

Integra

tion

Admin

Server

l middle

warew

ar

l service

swar

l admin

war

l mid

dlew

are

1

war

l serv

ices

1

war

l adm

in

1

war

Engag

ement

Service

s

kpnswar kpns1war




SQL query



l MySQL



name=WAAS_BASE_URL

l Oracle



name=WAAS_BASE_URL

l SQLServer



name=WAAS_BASE_URL

l DB2



name=WAAS_BASE_URL


and JBoss servers













check









l MySQL





l Oracle



l SQLServer



l DB2




CONTEXT_PATH











serviceswar name




INFjboss-webxml

From


To






From


To





toWebSphere




context pathgt

















follows







development




12 Publish the app







WARs


ii Go to Console




Fabric Components



Component



Conso

le

workspace

war

workspac

e1war



Pathgttomcatwebapps



Pathgtjboss gt

standalonedeploymen

ts

l WebLogic


ygtdeployments

l WebSphere lt


gtdeployments



Component



mfconsolew

ar

mfconsole

1war



Component



accountswa

r

accounts

1war



Component



Identit

y

authService

war

authServi

ce1war

Integr

ation

Admin

Server

l middl

eware

war

l servic

eswa

r

l admin

war

l mi

ddl

ew

are

1

w

ar

l ser

vic

es

1

w

ar

l ad

mi

n1

w

ar

Engag

ement

Servic

es

kpnswar kpns

1war




SQL query



l MySQL



name=WAAS_BASE_URL

l Oracle



name=WAAS_BASE_URL

l SQLServer



name=WAAS_BASE_URL

l DB2



name=WAAS_BASE_URL


and JBoss servers













check









l MySQL





l Oracle



l SQLServer



l DB2




CONTEXT_PATH


and JBoss servers




Component


authS

ervice

authServiceproper

ties

authServicewar

WEB-INFclasses

l WEBSPHERE_

AUTHCONFIGDB_

JNDI_

NAME=jdbcauthconfig

l WEBSPHERE_

AUTHGLOBALDB_

JNDI_

NAME=jdbcauthglobal

db

Works

pace

workspaceService

properties

WorkspacewarW

EB-INFclasses

l WEBSPHERE_

WAASGLOBALDB_

JNDI_

NAME=jdbcworkspac

esglobaldb

l WEBSPHERE_

WORKSPACESDB_

JNDI_

NAME=jdbcworkspac

esglobaldb



Component


Accou

nts

accountspropertie

s

AccountswarWE

B-INFclasses

l ACCOUNTS_DB_

JNDI_

NAME=jdbckonyacco

unts REPORTS_DB_

JNDI_

NAME=jdbckonyreport

s

Integr

ation

Admin

Server

serverconsoleprop

erties

adminwarWEB-

INFmiddlewarem

iddleware-

bootconfigadmin


ckonyadmindb


bckonyreports













serviceswar name


INFjboss-webxml

From


To






From


To





toWebSphere






context pathgt















follows







development




13 Publish the app


prise



Enterprise







example mfconsole1


example accounts1




example mfidentity1













file

For example






build

6 Save the file







1 Preface

11 Purpose




15 Contact Us

2 Prerequisites



23 Network Settings















































571 MySQL


572 SQL Server


574 Oracle


575 MariaDB



581 JBoss







582 WebLogic




583 WebSphere

















71 Tomcat Server

72 JBoss Server


73 WebLogic Server

74 WebSphere Server





83 Prerequisites


841 Prerequisites





92 Prerequisites



































129 WebSphere FAQs









Table of Contents

1 Preface 13

11 Purpose 14




15 Contact Us 16

2 Prerequisites 17




































TLS v12 40



















571 MySQL 64


572 SQL Server 64


574 Oracle 65




575 MariaDB 67



581 JBoss 68





JBossCluster 69




582 WebLogic 72




583 WebSphere 73





















72 JBoss Server 289

























installation) 333









DomainMode 337






























Enterprise 392



1 Preface


















andOAuth Provider


Yahoo













services They are



met


Objects







11 Purpose












l File path

l Commands

l Program code

l File names

Italic l Emphasis


l New terminology

Bold l Windows

l Menus

l Buttons

l Icons

l Fields

l Tabs







systems or data


Document Purpose

Kony Fabric User

Guide



15 Contact Us






2 Prerequisites







Memory 16GB





23 Network Settings



Direction

Action

Description

Engage

ment

Server


Engagem

ent Server

to access

Apple

APNS

HTTP2

production

URL

Engage

ment

Server


nd

Allow Allow the

Engagem

ent Server

to access

the JPush

notificatio

n server

URL

Engage

ment

Server


4433device


Engagem

ent Server

to access

Apple

APNS

HTTP2

developm

ent URL




Direction

Action

Description

Engage

ment

Server


nd

Allow Allow the

Engagem

ent Server

to access

Firebase

Cloud

Messagin

g (FCM)

service

Engage

ment

Server



170008 (17001 to 17255255254)

2196 TCP Outbou

nd

Allow Allow the

Engagem

ent Server

to access

APNS

feedback

service

Engage

ment

Server

gatewaypushapplecom


170008 (17001 to 17255255254)

2195 TCP Outbou

nd

Allow Allow the

Engagem

ent Server

to access

Apples

APNS

Engage

ment

Server

All subdomains of


Push URL



pushRequest

443 TCP Outbou

nd

Allow Allow

connect to

Blackberr

y Cloud

through

this port




Direction

Action

Description

Engage

ment

Server


nd

Allow Allow

connect to

Windows

Cloud

(MPNS)

through

this port

Engage

ment

Server


nd

Allow Allow

connect to

Windows

Cloud

(WNS)

through

this port

Internal

Corporat

eWiFi

router for

Android

Mobile

Devices






5228

52295

230

TCP

HTTP

HTTP

S

UDP

Both Allow Android

devices

will

connect to

GCM

through

this port

Internal

Corporat

eWiFi

router for

iOS

Devices

gatewaypushapplecom




170008 (17001 to 17255255254)


devices

connect to

APNS

servers

through

this port




Direction

Action

Description

Internal

Corporat

eWiFi

router for

iOS

Devices


devices

will

connect to

public

Apple

OCSP

and

iTunes

service

through

this port

Internal

Corporat

eWiFi

router for

Window

Devices




TCP

HTTP

HTTP

S

UDP

Both Allow Windows

devices

will

connect to

WNS

through

this port

Internal

Corporat

eWiFi

router for

Window

Devices


MPNS URL



TCP

HTTP

HTTP

S

UDP

Both Allow Windows

devices

will

connect to

MPNS

through

this port


























Servicerdquo



l 5420819284

l 54208192248








use
















objects













5120M





















CONTAINER=CURRENT


CONTAINER=CURRENT


CONTAINER=CURRENT
















version


servers












big pagesize of 32k





COMMIT



IBMDEFAULTGROUP


AUTOMATIC



COMMIT



IBMDEFAULTGROUP




AUTOMATIC



COMMIT



IBMDEFAULTGROUP


AUTOMATIC



COMMIT


IBMTEMPGROUP


EXTENTSIZE 1M


COMMIT

CONNECT RESET


























both editions








collation support







[client]


[mysql]


[mysqld]|






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


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




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



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


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











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




database





l SQL State HY000

l Error Code 1093










































servers






servers



















ltglobal-modulesgt


ltglobal-modulesgt

6 Save the changes




JBoss



ltinterfacesgt



ltinterfacegt





ltinterfacegt

ltinterfacesgt












inheritance=DEEPgt|

ltsubsystemgt



l standalonebat




l standalonesh
















ltsslgt




ltsslgt


ltsecurity-realmgt




































binding=connectgt









credentialsgt























D parameter








JVM arguments


















l Set JVM heap size














this is port 8880






8880 SOAP_

CONNECTOR_

ADDRESS













is sent


secure















(for Java7)










































and authorization



role






roles

Workspace

(WaaS)






application

API Developer

Portal








Environments

(Engagement

Services

Integration

Services)































Installation



Install Guide


node (Domain Mode)














Multinode


WindowsVersion112



local environment


installations


Console

l Workspace

l Accounts

Identity

Integration

l Admin

l Middleware

l Services

l Metrics


Engagement Services














link




n READMEtxt


database


















appears






appears





























HKEY_LOCAL_






below




running


Multinode



in the headers






For example













l local_policyjar






policyfileshtml












l local_policyjar


l READMEtxt













571 MySQL




application size



packet=1010241024








572 SQL Server









700enuauthx64)

574 Oracle




component


















i Connect as SYSDBA

sqlplus as sysdba



sysaux


creation




Conn mdsyssecret


creation






like SDO














edition licensing



575 MariaDB







minimum value




581 JBoss


Load Balancer)



proxy-port details

For example








ltinterfacesgt



ltinterfacegt



ltinterfacegt





configuration



ltinterfacegt



ltinterfacegt

ltinterfacesgt








domainxml file




ltsubsystemgt --gt




JBoss







-Xms2048m

-Xmx4096m



shown below








gt

ltsubsystemgt







settings









582 WebLogic

























583 WebSphere











java executablegt









Custom Properties














changes













20spec





Machine




































issue
















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example























usersxml








configuration table

15 Click Next











































foldergtkeystorejks











will generate










details


displayed
















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example













location








ltContextgt



river










testWhileIdle=true



url=jdbcsqlserver














testWhileIdle=true



url=jdbcsqlserver





ltContextgt








to 3306 for MariaDB



user











































special characters











message

























Mode)














issue
















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example



































l




16 Click Next











































foldergtkeystorejks











will generate










details


displayed
















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example








to 3306 for MariaDB



user











































special characters











message






















For Tomcat


following locations


















For JBoss


following locations




















For WebLogic


following locations






















you used the cuser_










For WebSphere


following locations

































issue
















option





types


























box




Services check box





check box



Kony Fabric Console







components











For example



















14 Click JBoss


















portgt





















example dbclient


user



















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL








database user




example






to 3306 for MariaDB



user











































special characters











message




















cluster)



























types


























box




Services check box





check box



Kony Fabric Console





Reports Database











For example





































system



























example dbclient


user
























USERS


following

l Data Tablespace



















database user




example










Password





set to 1433 for SQL








database user




example






to 3306 for MariaDB





user






















window appears






















special characters







message







not authenticated













For Tomcat




















For JBoss






















For WebLogic
























you used the cuser_










For WebSphere



























Fabric components






issue
















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example


























Components








Server










window shown below






path










folder





For Example





PATH

















For Example





PATH

















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example








5000 for DB2






example USERSPACE1


following

l Data Tablespace

















user









DB2Database version









license_cujar


example








to 3306 for MariaDB



user






























message





















Fabric components






issue
















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example


































Server























window shown below


r=server1












Important






















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example








5000 for DB2






example USERSPACE1


following

l Data Tablespace

















user









DB2Database version









license_cujar


example








to 3306 for MariaDB



user
























Important

















message
























Fabric Console












extract the file


located













configurations

71 Tomcat Server




72 JBoss Server








Documentation

73 WebLogic Server









documentation

74 WebSphere Server








documentation



















l Oracle




pk drop index







l MySQL







l DB2




pk



NULL





l MS SQL Server


GO


GO




version_pk]

GO


GO



GO


(50) NULL

GO














issue




83 Prerequisites




















option





Upgrade

























message




















library











issue




841 Prerequisites


your credentials




































l authServicekey











successful upgrade












message








l Oracle





l MySQL



l DB2



l MS SQL Server


























Windows


WindowsVersion112





For example



apply701x patches




installation



l 701 GA

l 71 GA

l 72 GA

l 73 GA

l V8

l V8 SP2

l V8 SP3 FP1



Windows


WindowsVersion112

92 Prerequisites


























Windows


WindowsVersion112








Windows


WindowsVersion112


with the upgrade



samplezip


in this field





Windows


WindowsVersion112











Windows


WindowsVersion112



message



Windows


WindowsVersion112





Windows


WindowsVersion112






following
























the database


selected





future use






























































































encryptedgt tag



For example






















5 Save the changes



































l JBossMulti-node


l WebLogic

l WebSphere
















ltpoolgt






ltpoolgt







Passed





DBPASSED



healthDetail









version8211_GA
















l sapjco3jar









folder






l sapjco3jar




path=sapjco3jargt





files

l sapjco3jar




path=sapjco3jargt





ltglobal-modulesgt


ltglobal-modulesgt



l sapjco3jar


















l sapjco3jar










l Issue


Workaround


For MySQL

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



For SQLServer

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



For Oracle

----------



For DB2

--------






JBoss servers

l Issue



publish fails

Workaround


database

l Issue



Workaround



Server




















new values





running on Tomcat









l Issue




Workaround


table_open_cache=64


l Issue






Workaround









l Issue


authenticated

Workaround






Workaround










null



Workaround


l Issue



Workaround



Fabric



Workaround






configuration





INFclasses




INFclasses


value in all nodes



INFclasses




Workaround






configuration





INFclasses




INFclasses


value in all nodes



INFclasses


For example

Caused by




file_size

Workaround


themyini file



l Issue



Workaround



l Issue



Workaround







version_rank



l Issue




from oracle

Workaround



l Issue



Workaround



l Issue


652GA to 72GA

Workaround






l Issue



Workaround




l Issue



Workaround

Manual Steps






















































l Issue


Workaround

Manual Steps












l Issue



Workaround

Manual Steps








GO

use msdb

GO


GO




GO


GO


GO


GO






GO


GO


GO


GO




GO


GO


GO


GO




GO


GO


GO



VIEWALTER TO userId

GO


GO




GO


GO



VIEWALTER TO userId

GO


GO


GO



VIEWALTER TO userId

GO









l Issue



Workaround

Manual Steps





and UNIX)





userid


userid


userid
























l Issue










Workaround


l Issue








l SQL State HY000

l Error Code 1093



l Workaround


Services






changes


















number














mod_cluster


JBoss
































































installation






installation


















installation






IPs


























Example








129 WebSphere FAQs












































METRICS_LOG_LEVEL





log4j2xml file




























Fabric







Visualizer)


Installer






install location


WARs


ii Go to Console




Components



Component



Consol

e

workspacewa

r

workspace

1war



Pathgttomcatwebapps


Fabric Install

Pathgtjboss gt


l WebLogic


deployments

l WebSphere lt


deployments



Component




1war


1war


ar

authServic

e1war

Integra

tion

Admin

Server

l middle

warew

ar

l service

swar

l admin

war

l mid

dlew

are

1

war

l serv

ices

1

war

l adm

in

1

war

Engag

ement

Service

s

kpnswar kpns1war




SQL query



l MySQL



name=WAAS_BASE_URL

l Oracle



name=WAAS_BASE_URL

l SQLServer



name=WAAS_BASE_URL

l DB2



name=WAAS_BASE_URL


and JBoss servers













check









l MySQL





l Oracle



l SQLServer



l DB2




CONTEXT_PATH











serviceswar name




INFjboss-webxml

From


To






From


To





toWebSphere




context pathgt

















follows







development




12 Publish the app







WARs


ii Go to Console




Fabric Components



Component



Conso

le

workspace

war

workspac

e1war



Pathgttomcatwebapps



Pathgtjboss gt

standalonedeploymen

ts

l WebLogic


ygtdeployments

l WebSphere lt


gtdeployments



Component



mfconsolew

ar

mfconsole

1war



Component



accountswa

r

accounts

1war



Component



Identit

y

authService

war

authServi

ce1war

Integr

ation

Admin

Server

l middl

eware

war

l servic

eswa

r

l admin

war

l mi

ddl

ew

are

1

w

ar

l ser

vic

es

1

w

ar

l ad

mi

n1

w

ar

Engag

ement

Servic

es

kpnswar kpns

1war




SQL query



l MySQL



name=WAAS_BASE_URL

l Oracle



name=WAAS_BASE_URL

l SQLServer



name=WAAS_BASE_URL

l DB2



name=WAAS_BASE_URL


and JBoss servers













check









l MySQL





l Oracle



l SQLServer



l DB2




CONTEXT_PATH


and JBoss servers




Component


authS

ervice

authServiceproper

ties

authServicewar

WEB-INFclasses

l WEBSPHERE_

AUTHCONFIGDB_

JNDI_

NAME=jdbcauthconfig

l WEBSPHERE_

AUTHGLOBALDB_

JNDI_

NAME=jdbcauthglobal

db

Works

pace

workspaceService

properties

WorkspacewarW

EB-INFclasses

l WEBSPHERE_

WAASGLOBALDB_

JNDI_

NAME=jdbcworkspac

esglobaldb

l WEBSPHERE_

WORKSPACESDB_

JNDI_

NAME=jdbcworkspac

esglobaldb



Component


Accou

nts

accountspropertie

s

AccountswarWE

B-INFclasses

l ACCOUNTS_DB_

JNDI_

NAME=jdbckonyacco

unts REPORTS_DB_

JNDI_

NAME=jdbckonyreport

s

Integr

ation

Admin

Server

serverconsoleprop

erties

adminwarWEB-

INFmiddlewarem

iddleware-

bootconfigadmin


ckonyadmindb


bckonyreports













serviceswar name


INFjboss-webxml

From


To






From


To





toWebSphere






context pathgt















follows







development




13 Publish the app


prise



Enterprise







example mfconsole1


example accounts1




example mfidentity1













file

For example






build

6 Save the file







1 Preface

11 Purpose




15 Contact Us

2 Prerequisites



23 Network Settings















































571 MySQL


572 SQL Server


574 Oracle


575 MariaDB



581 JBoss







582 WebLogic




583 WebSphere

















71 Tomcat Server

72 JBoss Server


73 WebLogic Server

74 WebSphere Server





83 Prerequisites


841 Prerequisites





92 Prerequisites



































129 WebSphere FAQs



























TLS v12 40



















571 MySQL 64


572 SQL Server 64


574 Oracle 65




575 MariaDB 67



581 JBoss 68





JBossCluster 69




582 WebLogic 72




583 WebSphere 73





















72 JBoss Server 289

























installation) 333









DomainMode 337






























Enterprise 392



1 Preface


















andOAuth Provider


Yahoo













services They are



met


Objects







11 Purpose












l File path

l Commands

l Program code

l File names

Italic l Emphasis


l New terminology

Bold l Windows

l Menus

l Buttons

l Icons

l Fields

l Tabs







systems or data


Document Purpose

Kony Fabric User

Guide



15 Contact Us






2 Prerequisites







Memory 16GB





23 Network Settings



Direction

Action

Description

Engage

ment

Server


Engagem

ent Server

to access

Apple

APNS

HTTP2

production

URL

Engage

ment

Server


nd

Allow Allow the

Engagem

ent Server

to access

the JPush

notificatio

n server

URL

Engage

ment

Server


4433device


Engagem

ent Server

to access

Apple

APNS

HTTP2

developm

ent URL




Direction

Action

Description

Engage

ment

Server


nd

Allow Allow the

Engagem

ent Server

to access

Firebase

Cloud

Messagin

g (FCM)

service

Engage

ment

Server



170008 (17001 to 17255255254)

2196 TCP Outbou

nd

Allow Allow the

Engagem

ent Server

to access

APNS

feedback

service

Engage

ment

Server

gatewaypushapplecom


170008 (17001 to 17255255254)

2195 TCP Outbou

nd

Allow Allow the

Engagem

ent Server

to access

Apples

APNS

Engage

ment

Server

All subdomains of


Push URL



pushRequest

443 TCP Outbou

nd

Allow Allow

connect to

Blackberr

y Cloud

through

this port




Direction

Action

Description

Engage

ment

Server


nd

Allow Allow

connect to

Windows

Cloud

(MPNS)

through

this port

Engage

ment

Server


nd

Allow Allow

connect to

Windows

Cloud

(WNS)

through

this port

Internal

Corporat

eWiFi

router for

Android

Mobile

Devices






5228

52295

230

TCP

HTTP

HTTP

S

UDP

Both Allow Android

devices

will

connect to

GCM

through

this port

Internal

Corporat

eWiFi

router for

iOS

Devices

gatewaypushapplecom




170008 (17001 to 17255255254)


devices

connect to

APNS

servers

through

this port




Direction

Action

Description

Internal

Corporat

eWiFi

router for

iOS

Devices


devices

will

connect to

public

Apple

OCSP

and

iTunes

service

through

this port

Internal

Corporat

eWiFi

router for

Window

Devices




TCP

HTTP

HTTP

S

UDP

Both Allow Windows

devices

will

connect to

WNS

through

this port

Internal

Corporat

eWiFi

router for

Window

Devices


MPNS URL



TCP

HTTP

HTTP

S

UDP

Both Allow Windows

devices

will

connect to

MPNS

through

this port


























Servicerdquo



l 5420819284

l 54208192248








use
















objects













5120M





















CONTAINER=CURRENT


CONTAINER=CURRENT


CONTAINER=CURRENT
















version


servers












big pagesize of 32k





COMMIT



IBMDEFAULTGROUP


AUTOMATIC



COMMIT



IBMDEFAULTGROUP




AUTOMATIC



COMMIT



IBMDEFAULTGROUP


AUTOMATIC



COMMIT


IBMTEMPGROUP


EXTENTSIZE 1M


COMMIT

CONNECT RESET


























both editions








collation support







[client]


[mysql]


[mysqld]|






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


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




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



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


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











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




database





l SQL State HY000

l Error Code 1093










































servers






servers



















ltglobal-modulesgt


ltglobal-modulesgt

6 Save the changes




JBoss



ltinterfacesgt



ltinterfacegt





ltinterfacegt

ltinterfacesgt












inheritance=DEEPgt|

ltsubsystemgt



l standalonebat




l standalonesh
















ltsslgt




ltsslgt


ltsecurity-realmgt




































binding=connectgt









credentialsgt























D parameter








JVM arguments


















l Set JVM heap size














this is port 8880






8880 SOAP_

CONNECTOR_

ADDRESS













is sent


secure















(for Java7)










































and authorization



role






roles

Workspace

(WaaS)






application

API Developer

Portal








Environments

(Engagement

Services

Integration

Services)































Installation



Install Guide


node (Domain Mode)














Multinode


WindowsVersion112



local environment


installations


Console

l Workspace

l Accounts

Identity

Integration

l Admin

l Middleware

l Services

l Metrics


Engagement Services














link




n READMEtxt


database


















appears






appears





























HKEY_LOCAL_






below




running


Multinode



in the headers






For example













l local_policyjar






policyfileshtml












l local_policyjar


l READMEtxt













571 MySQL




application size



packet=1010241024








572 SQL Server









700enuauthx64)

574 Oracle




component


















i Connect as SYSDBA

sqlplus as sysdba



sysaux


creation




Conn mdsyssecret


creation






like SDO














edition licensing



575 MariaDB







minimum value




581 JBoss


Load Balancer)



proxy-port details

For example








ltinterfacesgt



ltinterfacegt



ltinterfacegt





configuration



ltinterfacegt



ltinterfacegt

ltinterfacesgt








domainxml file




ltsubsystemgt --gt




JBoss







-Xms2048m

-Xmx4096m



shown below








gt

ltsubsystemgt







settings









582 WebLogic

























583 WebSphere











java executablegt









Custom Properties














changes













20spec





Machine




































issue
















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example























usersxml








configuration table

15 Click Next











































foldergtkeystorejks











will generate










details


displayed
















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example













location








ltContextgt



river










testWhileIdle=true



url=jdbcsqlserver














testWhileIdle=true



url=jdbcsqlserver





ltContextgt








to 3306 for MariaDB



user











































special characters











message

























Mode)














issue
















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example



































l




16 Click Next











































foldergtkeystorejks











will generate










details


displayed
















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example








to 3306 for MariaDB



user











































special characters











message






















For Tomcat


following locations


















For JBoss


following locations




















For WebLogic


following locations






















you used the cuser_










For WebSphere


following locations

































issue
















option





types


























box




Services check box





check box



Kony Fabric Console







components











For example



















14 Click JBoss


















portgt





















example dbclient


user



















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL








database user




example






to 3306 for MariaDB



user











































special characters











message




















cluster)



























types


























box




Services check box





check box



Kony Fabric Console





Reports Database











For example





































system



























example dbclient


user
























USERS


following

l Data Tablespace



















database user




example










Password





set to 1433 for SQL








database user




example






to 3306 for MariaDB





user






















window appears






















special characters







message







not authenticated













For Tomcat




















For JBoss






















For WebLogic
























you used the cuser_










For WebSphere



























Fabric components






issue
















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example


























Components








Server










window shown below






path










folder





For Example





PATH

















For Example





PATH

















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example








5000 for DB2






example USERSPACE1


following

l Data Tablespace

















user









DB2Database version









license_cujar


example








to 3306 for MariaDB



user






























message





















Fabric components






issue
















option





types

















boxes are selected










box




Services check box





check box



Kony Fabric Console







components











For example


































Server























window shown below


r=server1












Important






















example dbclient


user





















USERS


following

l Data Tablespace

















database user












Password







set to 1433 for SQL






database user




example








5000 for DB2






example USERSPACE1


following

l Data Tablespace

















user









DB2Database version









license_cujar


example








to 3306 for MariaDB



user
























Important

















message
























Fabric Console












extract the file


located













configurations

71 Tomcat Server




72 JBoss Server








Documentation

73 WebLogic Server









documentation

74 WebSphere Server








documentation



















l Oracle




pk drop index







l MySQL







l DB2




pk



NULL





l MS SQL Server


GO


GO




version_pk]

GO


GO



GO


(50) NULL

GO














issue




83 Prerequisites




















option





Upgrade

























message




















library











issue




841 Prerequisites


your credentials




































l authServicekey











successful upgrade












message








l Oracle





l MySQL



l DB2



l MS SQL Server


























Windows


WindowsVersion112





For example



apply701x patches




installation



l 701 GA

l 71 GA

l 72 GA

l 73 GA

l V8

l V8 SP2

l V8 SP3 FP1



Windows


WindowsVersion112

92 Prerequisites


























Windows


WindowsVersion112








Windows


WindowsVersion112


with the upgrade



samplezip


in this field





Windows


WindowsVersion112











Windows


WindowsVersion112



message



Windows


WindowsVersion112





Windows


WindowsVersion112






following
























the database


selected





future use






























































































encryptedgt tag



For example






















5 Save the changes



































l JBossMulti-node


l WebLogic

l WebSphere
















ltpoolgt






ltpoolgt







Passed





DBPASSED



healthDetail









version8211_GA
















l sapjco3jar









folder






l sapjco3jar




path=sapjco3jargt





files

l sapjco3jar




path=sapjco3jargt





ltglobal-modulesgt


ltglobal-modulesgt



l sapjco3jar


















l sapjco3jar










l Issue


Workaround


For MySQL

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



For SQLServer

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



For Oracle

----------



For DB2

--------






JBoss servers

l Issue



publish fails

Workaround


database

l Issue



Workaround



Server




















new values





running on Tomcat









l Issue




Workaround


table_open_cache=64


l Issue






Workaround









l Issue


authenticated

Workaround






Workaround










null



Workaround


l Issue



Workaround



Fabric



Workaround






configuration





INFclasses




INFclasses


value in all nodes



INFclasses




Workaround






configuration





INFclasses




INFclasses


value in all nodes



INFclasses


For example

Caused by




file_size

Workaround


themyini file



l Issue



Workaround



l Issue



Workaround







version_rank



l Issue




from oracle

Workaround



l Issue



Workaround



l Issue


652GA to 72GA

Workaround






l Issue



Workaround




l Issue



Workaround

Manual Steps






















































l Issue


Workaround

Manual Steps












l Issue



Workaround

Manual Steps








GO

use msdb

GO


GO




GO


GO


GO


GO






GO


GO


GO


GO




GO


GO


GO


GO




GO


GO


GO



VIEWALTER TO userId

GO


GO




GO


GO



VIEWALTER TO userId

GO


GO


GO



VIEWALTER TO userId

GO









l Issue



Workaround

Manual Steps





and UNIX)





userid


userid


userid
























l Issue










Workaround


l Issue








l SQL State HY000

l Error Code 1093



l Workaround


Services






changes


















number














mod_cluster


JBoss
































































installation






installation


















installation






IPs


























Example








129 WebSphere FAQs












































METRICS_LOG_LEVEL





log4j2xml file




























Fabric







Visualizer)


Installer






install location


WARs


ii Go to Console




Components



Component



Consol

e

workspacewa

r

workspace

1war



Pathgttomcatwebapps


Fabric Install

Pathgtjboss gt


l WebLogic


deployments

l WebSphere lt


deployments



Component




1war


1war


ar

authServic

e1war

Integra

tion

Admin

Server

l middle

warew

ar

l service

swar

l admin

war

l mid

dlew

are

1

war

l serv

ices

1

war

l adm

in

1

war

Engag

ement

Service

s

kpnswar kpns1war




SQL query



l MySQL



name=WAAS_BASE_URL

l Oracle



name=WAAS_BASE_URL

l SQLServer



name=WAAS_BASE_URL

l DB2



name=WAAS_BASE_URL


and JBoss servers













check









l MySQL





l Oracle



l SQLServer



l DB2




CONTEXT_PATH











serviceswar name




INFjboss-webxml

From


To






From


To





toWebSphere




context pathgt

















follows







development




12 Publish the app







WARs


ii Go to Console




Fabric Components



Component



Conso

le

workspace

war

workspac

e1war



Pathgttomcatwebapps



Pathgtjboss gt

standalonedeploymen

ts

l WebLogic


ygtdeployments

l WebSphere lt


gtdeployments



Component



mfconsolew

ar

mfconsole

1war



Component



accountswa

r

accounts

1war



Component



Identit

y

authService

war

authServi

ce1war

Integr

ation

Admin

Server

l middl

eware

war

l servic

eswa

r

l admin

war

l mi

ddl

ew

are

1

w

ar

l ser

vic

es

1

w

ar

l ad

mi

n1

w

ar

Engag

ement

Servic

es

kpnswar kpns

1war




SQL query



l MySQL



name=WAAS_BASE_URL

l Oracle



name=WAAS_BASE_URL

l SQLServer



name=WAAS_BASE_URL

l DB2



name=WAAS_BASE_URL


and JBoss servers













check









l MySQL





l Oracle



l SQLServer



l DB2




CONTEXT_PATH


and JBoss servers




Component


authS

ervice

authServiceproper

ties

authServicewar

WEB-INFclasses

l WEBSPHERE_

AUTHCONFIGDB_

JNDI_

NAME=jdbcauthconfig

l WEBSPHERE_

AUTHGLOBALDB_

JNDI_

NAME=jdbcauthglobal

db

Works

pace

workspaceService

properties

WorkspacewarW

EB-INFclasses

l WEBSPHERE_

WAASGLOBALDB_

JNDI_

NAME=jdbcworkspac

esglobaldb

l WEBSPHERE_

WORKSPACESDB_

JNDI_

NAME=jdbcworkspac

esglobaldb



Component


Accou

nts

accountspropertie

s

AccountswarWE

B-INFclasses

l ACCOUNTS_DB_

JNDI_

NAME=jdbckonyacco

unts REPORTS_DB_

JNDI_

NAME=jdbckonyreport

s

Integr

ation

Admin

Server

serverconsoleprop

erties

adminwarWEB-

INFmiddlewarem

iddleware-

bootconfigadmin


ckonyadmindb


bckonyreports













serviceswar name


INFjboss-webxml

From


To






From


To





toWebSphere






context pathgt















follows







development




13 Publish the app


prise



Enterprise







example mfconsole1


example accounts1




example mfidentity1













file

For example






build

6 Save the file







1 Preface

11 Purpose




15 Contact Us

2 Prerequisites



23 Network Settings















































571 MySQL


572 SQL Server


574 Oracle


575 MariaDB



581 JBoss







582 WebLogic




583 WebSphere

















71 Tomcat Server

72 JBoss Server


73 WebLogic Server

74 WebSphere Server





83 Prerequisites


841 Prerequisites





92 Prerequisites



































129 WebSphere FAQs




