kony mobilefabric manual installation guide

Kony MobileFabric

Manual Installation Guide

On-Premises

Release 7.0Document 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.

2014 by Kony, Inc. All rights reserved 1 of 316

Manual Installation GuideVersion1.0

Copyright 2014 by Kony, Inc.

All rights reserved.

April, 2016

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

Modeler, and Kony Visualizer are trademarks of Kony, Inc. MobileFabric is a registered trademark of

Kony, Inc. Microsoft, theMicrosoft logo, Internet Explorer, Windows, andWindowsVista are

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

Objective-C, Safari, Apple Pay, AppleWatch, and Xcode are trademarks or registered trademarks of

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

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

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

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

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

property of their respective owners.



Revision History

Date Document Version Description of Modifications/Release

04/26/2016 1.2 Document Updated for Release 7.0.1

02/29/2016 1.0 Document Updated for Release 7.0



Table of Contents

1. Preface 12

1.1 Purpose 13

1.2 Intended Audience 13

1.3 Formatting Conventions 13

1.4 Related Documents 15

1.5 Contact Us 15

2. Prerequisites 16

2.1 Software Requirements 16

2.2 Hardware Requirements 16

2.3 DB2 JNDI Datasource Setup 16

2.4 Heap and PermGen Settings 17

3. MobileFabric Topology and Components 18

4. Preinstallation Tasks 22

4.1 Prerequisites for MobileFabric with Oracle 22

4.2 Configure Deployment of mbaasportal.war File for Multi-Node 26

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

4.4 Install Memcached Server 30

4.5 Increase JVMmemory for WebLogic Server 32

4.6 PlaceMS SQLServer Connector JAR inWebLogic Classpath 32

4.7 Configure JMS for Metrics in DomainMode for WebLogic or JBoss 33



4.8 Configure Load Balancers for Sending Host Information inMultinode 39

4.9 Configure Hibernate Dialect inWebLogic (only for WebLogic) 40

4.10 Update Listen Interfaces in host.xml for JBossCluster 40

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

Cluster 41

4.12 Increase innodb_log_file_size in my.ini file 42

4.13 Create Locator Component for Oracle Database 42

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

at Load Balancer) 44

4.15 ConfigureManager User for Tomcat 45

4.16 Configuring FlywayCommand-line Tool 45

5. Installing MobileFabric on WebSphere with DB2 57

6. Configuring Database for MobileFabric 61

6.1 Configuring Kony Identity (Auth) ServicesDatabase 62

6.1.1 MySQL 62

6.1.2 Oracle 62

6.1.3 SQL Server 63

6.1.4 DB2 64

6.2 Configuring KonyWorkspace ServicesDatabase 67

6.2.1 MySQL 67

6.2.2 Oracle 67

6.2.3 SQL Server 68



6.2.4 DB2 69

6.3 Configuring Kony Accounts ServicesDatabase 72

6.3.1 MySQL 72

6.3.2 Oracle 72

6.3.3 SQL Server 73

6.3.4 DB2 74

6.4 Configuring Kony Admin Database 78

6.5 Configuring KonyReports Database 88

6.6 Configuring KonyDevice Database 91

7. Configuring Flyway Command-line Tool 94

8. Creating Shared Library Folders for MobileFabric - WebSphere 105

8.1 Creating Shared Library Folders - WebSphere 105

8.2 Mapping Shared Library Folders References toWAR Files - WebSphere 110

9. Creating Data Source for MobileFabric Console - WebSphere 117

9.1 Creating Data Source for MobileFabric Console Schema (MySQL) 117

9.1.1 Creating a JAAS J2C Authentication 118

9.1.2 Creating a JDBC Provider 121

9.1.3 Creating a Data Source 129

9.1.4 Setting CustomProperties of Data Source 144

9.2 Creating Data Source for MobileFabric Console Schema (Oracle) 149







9.3 Creating Data Source for MobileFabric Console Schema (SQL Server) 165





9.4 Creating Data Source for MobileFabric Console Schema (DB2) 181




9.5 Configuring Data Source for Integration Service 193

10. Creating Data Source for MobileFabric Components Schema - WebLogic 194

11. Configuring Installation Mode 195

11.1 How to Configure InstallationModes - Tomcat 195

11.1.1 How to Configure Tomcat Multinode Installation 195

11.2 How to Configure InstallationModes - JBoss 197

11.2.1 How to Configure JBoss for Singlenode Installation 197

11.2.2 How to Configure JBoss for Multinode Installation 197

11.3 How to Configure InstallationModes - WebSphere andWebLogic 197



12. Configuring JNDI for a Database 199

12.1 How to Configure JNDI - Tomcat 199

12.1.1 For MySQL 199

12.1.2 Configure JNDI for Middleware.war and Services.war 202

12.2 How to Configure JNDI - JBoss 203

12.2.1 For MySQL 203

13. Configuring Connectors and WAR Deployment 211

13.1 How to Configure Connectors - Tomcat 211

13.1.1 How to Configure Batch Files 212

13.2 How to Configure Connectors - JBoss 213

13.2.1 How to Configure enable-welcome-root Value 213

13.2.2 How to Configure Connector 214

14. Configuring Properties Files in WAR Files 215

14.1 How ToConfigure Properties Files inWAR Files - Tomcat and JBoss 215

14.1.1 accountsAPI.war 215

14.1.2 authService.war 217

14.1.3 mbaasportal.war 218

14.1.4 workspaceService.war 219

14.1.5 How To Set Middlware Home - Tomcat 220

14.1.6 How To Set Middlware Home - JBoss 221

14.2 How ToConfigure Properties Files inWAR Files - WebSphere 222







14.2.5 How to Configure KonyMobileFabric Integration Services 227

14.3 How ToConfigure Properties Files inWAR Files - WebLogic 236





14.3.5 KonyMobileFabric Integration Services (middleware) 242

15. Configuring JMS Server and JMSModule for Integration Server (Metrics) -

WebSphere 243

15.1 Configure JMS 243

16. Configuring JMS Server and JMSModule for Integration Server (Metrics) - WebLogic 258

16.1 Configure JMS Server for Managed Server (Optional) 258

16.1.1 Create JMS Server 258

16.1.2 Create JMSModule 259

16.1.3 Create Connection Factory under JMSModule 259

16.1.4 Create Topic under JMSModule 260

17. Configuring Metrics.ear 262



18. Deploying WAR Files 263

18.1 DeployingWAR Files to Tomcat and JBoss 263

18.2 DeployingWAR Files toWebSphere 264

18.2.1 DeployingMetrics.ear toWebSphere 280

18.3 DeployingWAR Files toWebLogic 292

19. Configuring Kony MobileFabric as a Service 295

20. Starting Kony MobileFabric Console 296

20.1 Tomcat 296

20.2 JBoss 296

20.2.1 For Single Node 296

20.2.2 For Multinode 297

21. Post-Installation Tasks 298

21.1 Configuring Secure Sockets Layer (SSL) Certificate 298

21.1.1 How to Add an Installer Generated Self-Signed SSLCertificate to Cacerts 298

21.1.2 How to Add an Existing SSLCertificate to Cacerts 299

21.2 JDK Version Compatibility 300

21.3 How to Switch between JDK Versions 300

21.4 How to ConfigureMemcached for Integration Service 301

21.5 How to Change Default Artifact Size inWorkspace - DB2 302

22. FAQs and Troubleshooting 304

22.1 How to Configure JBossCluster 309



22.2 How to Configure a Custom JAR File onWebLogic 309

22.3 How to Configure Heap and PermGen Size 310

22.3.1 Configuring Heap and PermGen Size for Tomcat 310

22.3.2 Configuring Heap and PermGen Size for JBoss 310

22.3.3 Configuring Heap and PermGen Size for WebLogic 311

22.4 How to ConfigureMobileFabric Behind a Reverse Proxy 311

22.5 How to Configure Frontend HTTPS to Tomcat HTTP Redirection 312

22.6 WebSphere FAQs 313

22.7 How to Change Log Levels 313

22.8 How to Change Log Levels 313


1. Preface Manual Installation GuideVersion1.0

1. Preface

KonyMobileFabric is aMobile Backend as a Service (MBaaS) provider that helps developers build

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

apps for iOS, Android, and HTML5-based apps for modern browsers. MobileFabric ensures that

developers build mobile applications quickly by focusing on core areas and obtaining secured back

end services instantly. MobileFabric hasmultiple features that can be used - Identity, Integration,

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

centralized console.

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

recommends that you install the followingMobileFabric features on premises:

l KonyMobileFabric Identity and Console

l KonyMobileFabric Integration

l KonyMobileFabric Engagement Services

l KonyMobileFabric Sync

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

l Identity: This feature allows you to define the type of authentication that grants access to your

application. MobileFabric supports the following authentication services: Microsoft Active

Directory, Salesforce, Security AssertionMarkup Language (SAML), Kony SAP Gateway,

Facebook, and KonyUser Repository.

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

You can define the service in XML, SOAP, JSON, Java, Salesforce, and Kony SAP Gateway.

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

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

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



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

application. Sync supports onlyWeb Services, except SAP Sky.

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

services for your application.

Important: Kony recommends using theMobileFabric Installer for deployingMobileFabric 7.0

onwards.

If you are required to install MobileFabricmanually due to your business rules and polices, please

contact [email protected] for approval and to obtain access to theMobileFabricmanual

install artefacts. Manual installs not approved by Konywill not be supported.

1.1 Purpose

This document explains how to install and configure KonyMobileFabric Console.

1.2 Intended Audience

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

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

applications in aWindows or Linux environment.

1.3 Formatting Conventions

The following formatting conventions are used throughout the document:


mailto:[email protected]


Convention Explanation

Monospace n User input text, system prompts, and responses

n File path

n Commands

n Program code

n File names

Italic n Emphasis

n Names of books and documents

n New terminology

Bold n Windows

n Menus

n Buttons

n Icons

n Fields

n Tabs

URL Active link to a URL

Note:Provides helpful hints or additional information

Important:Highlights actions or information that might cause problems to systems or

data



1.4 Related Documents

Document Purpose

Kony MobileFabric

User Guide

This guide helps you understand how to create a Kony MobileFabric

account, add services, and publish apps.

1.5 Contact Us

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

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

contact [email protected].


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

2. Prerequisites Manual Installation GuideVersion1.0

2. Prerequisites

Ensure that the following prerequisites aremet:

The following sections explain the software and hardware required to install KonyMobileFabric

Console.

2.1 Software Requirements

For software system requirements, refer to Software Requirements by KonyMobileFabric

2.2 Hardware Requirements

Component Requirement

Processor Quad-core processor

Memory 16GB

Internal Storage 150GB

Network 100Mbps Ethernet interface card

2.3 DB2 JNDI Datasource Setup

1. Download the following DB2 driver JARs from IBM.

l db2jcc4.jar (Minimum version 4.19.26)

l db2jcc4_license_cu.jar

l db2jcc4_license_cisuz.jar


http://docs.kony.com/konylibrary/general/mobilefabric_supported_devices_os_browsers/Default.htm#MobileFabric.htm?TocPath=Kony%2520MobileFabric|_____0http://www-01.ibm.com/support/docview.wss?uid=swg21363866

2. Prerequisites Manual Installation GuideVersion1.0

2. Place these JARs under a folder that you can reference while creating DB2 JDBC provider.

For example, for WebSphere, place these JARs under \AppServer\konylib\databaseConnectors folder. For more details refer to

Creating Shared Library Folders for MobileFabric - WebSphere

2.4 Heap and PermGen Settings

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

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

l Tomcat heap and PermGen settings

l JBoss heap and PermGen settings

l WebLogic heap and PermGen settings

l WebSphere heap settings


http://docs.kony.com/konylibrary/mobilefabric/resources/websphere_faqs.htm

3. MobileFabric Topology and Components Manual Installation GuideVersion1.0

3. MobileFabric Topology and Components

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

identity services, developer environment, and production environment.

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

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

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

An overview of theMobileFabric architecture and components follows:



An overview of theMobileFabric deployment architecture follows:

The following table describes the components of MobileFabric:



Convention Description

Identity This component validates user accounts and applications for authentication

and authorization.

l Authentication identifies log-on credentials of a user.

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

role.

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

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

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

environments, and publish apps to an environment.

This component uses auth service for authorizing requests based on user

roles.

Workspace

(WaaS)

Workspace configures MBaaS services (applications, identity, integration,

orchestration, synchronization, and engagement services). After these

services are configured, these services must be published to respective

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

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

application.

Environments

(Engagement

Services, Sync,

Integration

Service)

This component adds runtime capabilities to apps, such as engagement

services, synchronization services, and integration services.



Convention Description

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 http://docs.kony.com/konylibrary/integration/kony_

mobilefabric_integration_service_admin_console_user_guide/Default.htm

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

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

fetches the response from the backend and provides the required information

to the device in the JSON format.

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

same runtime capabilities as themiddleware.

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

themiddleware.war. Similarly when you use only standalone Kony

Server, you can ignore the services.war.

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

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

example, you can use one of the following choices:

-Install All Components on one node.

- Install KonyMobileFabric Console, Kony Identity Service, and Kony Integration Service on

separate nodes.


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

4. Preinstallation Tasks Manual Installation GuideVersion1.0

4. Preinstallation Tasks

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

l MySQL 5.6/5.7, Oracle 12c (12.1.0), MS SQLServer 2012 R2, or IBMDB2 9.7/10.1/10.5

database server should be accessible.

l A database user should be granted all permissions.

4.1 Prerequisites for MobileFabric with Oracle

l For installingMobileFabric Database for Oracle, complete the following steps:

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

Database setup in order to successfully complete theMobileFabric database deployment.

Oracle softwaremust be installed and basic databasemust be created before to continue

with MobileFabric database schema setup.

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

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

set as AL32UTF8 and National character set as AL16UTF16.

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

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

logs.

A dedicated user must be granted with privileges, shown in the following section.

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

new privileges loaded to the user.



l Create a dedicated database user.

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

JDBC.

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

CREATE USER

IDENTIFIED BY

DEFAULT TABLESPACE USERS

TEMPORARY TABLESPACE TEMP

PROFILE DEFAULT;

GRANT TO with admin option;

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

-

CREATE JOB, CREATE PROCEDURE, CREATE SEQUENCE, CREATE

SESSION,

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

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

ALTER TABLESPACE, ALTER USER

Important: Ensure that a dedicated database user must not be an application user

(for example, konydevicedb) for installation of database. A dedicated user gets logged

into audit logs.

A dedicated user must be granted with privileges, shown in the following section.

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

get the new privileges loaded to the user.

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

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

Database Connectivity (JDBC) authentication.



Alter session set container = PDB ;

CREATE USER

IDENTIFIED BY

DEFAULT TABLESPACE USERS

TEMPORARY TABLESPACE TEMP

PROFILE DEFAULT CONTAINER=CURRENT;

GRANT TO with admin

option CONTAINER=CURRENT;

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

CREATE JOB, CREATE PROCEDURE, CREATE SEQUENCE, CREATE

SESSION,

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

CREATE USER, CREATE VIEW, CREATE PLUGGABLE DATABASE,

CREATE SESSION, ALTER SESSION, ALTER TABLESPACE, ALTER USER

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

below options based on your Oracle database version.

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

PDB in the JDBC URL such as pdborclorpdbmfdb

jdbc:oracle:thin:@:1521:pdbmfdb

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

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

JDBC URLsuch asorcl or mfdb.

jdbc:oracle:thin:@:1521/mfdb

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

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

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



the page size of the default tablespace. Additionally you need to create three tablespaces: one

for tables and data, one for index, and the other tablespace for Large objects (LOBs). For

creating tablespace, the details are provided int he below sections.

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

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

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

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

tablespace with big pagesize of 32k.

-- Replace with your actual database name.

CONNECT TO ;

CREATE BUFFERPOOL BIGBUFFERPOOL IMMEDIATE ALL DBPARTITIONNUMS

SIZE AUTOMATIC NUMBLOCKPAGES 100 BLOCKSIZE 100 PAGESIZE 32K;

COMMIT;

-- To create a tablespace for tables and Data

CREATE LARGE TABLESPACE IN DATABASE PARTITION

GROUP IBMDEFAULTGROUP

PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 32 PREFETCHSIZE

AUTOMATIC

BUFFERPOOL BIGBUFFERPOOL OVERHEAD 7.5 TRANSFERRATE 0.06 AUTORESIZE YES

INITIALSIZE 32M NO FILE SYSTEM CACHING;

COMMIT;

-- To create an index tablespace




AUTOMATIC





COMMIT;

-- To create a LOB tablespace




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;

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.

l WindowsServer 2012 R2 is recommended if you are installing onWindows environment.

4.2 Configure Deployment of mbaasportal.war File for Multi-Node

OnceMobileFabric installation succeeds, theMobileFabric Console will not be displayed as the

enable-welcome-root value is set true in the domain.xml file.

To configure mbaasportal.war, follow these steps:



1. In themaster node, open the domain.xml file from

JBOSSDIR\domain\configuration, and search for enable-welcome-root="true."

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

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

Before installingMobileFabric 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 MobileFabric

in a newWindows box, the system gives the following error:

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

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

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

appears.

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

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



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

appears.



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

Computers, Service Accounts, or Groups window.

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

adds the user name in the Local security setting tab.



4.4 Install Memcached Server

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

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

To install Memcached Server, follow these steps:

1. Download thememcache server.

2. Extract the zip file.

3. From the command prompt, navigate tomemcached directory.

4. Run the following command:

memcached.exe -d install

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

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

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

l net start memcached Server

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

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

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

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



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

HKEY_LOCAL_

MACHINE/SYSTEM/CurrentControlSet/Services/memcached Server.

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

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

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

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

below:



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

running.

4.5 Increase JVM memory for WebLogic Server

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

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

4.6 Place MS SQL Server Connector JAR in WebLogic Classpath

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

sqljdbc4.jar file in theWebLogic classpath.



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

steps before startingMobileFabric installation.

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

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

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

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

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

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

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

4. Restart the server.

4.7 Configure JMS for Metrics in Domain Mode for WebLogic or JBoss

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

cluster.

l For WebLogic: While installingWebLogic cluster, user should select both admin server and

cluster options.

l For JBoss, To deploymetrics in domainmode, follow these steps:

a. Create Application User and add to JMS role: To create an application user, go to

JBOSS/bin folder and run theadd-users.bat file.



b. With JBossManagement User credentials, log in to JBossManagement Console using

themanagement port specified in master'shost.xml file.



c. After login to JBoss, navigate to Configuration > Messaging > Destinations and click

View.



d. Navigate to Queues/Topics, create JMS topic with below details:

l Topic Name: KonyMetricsTopic

l JNDI Name: java:jboss/exported/jms/KonyMetricsTopic

e. In the Security Settings tab, create a role for jms pattern #, and select Send and

Consume check boxes.



f. In the Connection Factories tab, create connection factory with the below details:

l Name: KonyConnectionFactory

l JNDI Name: java:jboss/exported/jms/KonyConnectionFactory

l Connector: netty



g. Navigate to Container > EE >Global Modules, and add below modules:

l org.jboss.as.remoting

l org.hornetq

l org.jboss.remote-naming



h. Restart JBoss and verify the configuration to access admin health check. The system

should show all pass including Access to Reporting Queuemainly.

You have successfully configured themetrics.

4.8 Configure Load Balancers for Sending Host Information in

Multinode

When user is installingMobileFabric onmultinode environment, the user should checkwhether

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

send host in the headers.

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

Users cannot launchMobileFabric Console.

The above configuration is based on the loadbalancer.

For example:



l For Apache: preserveHost On

l For HAProxy: preserve host flag is not required.

4.9 Configure Hibernate Dialect in WebLogic (only for WebLogic)

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

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

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

4.10 Update Listen Interfaces in host.xml for JBoss Cluster

For JBoss domainmode installation, configure the following interface address.

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

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



4.11 Comment the javax-persistence-module for Kony Engagement

Services on JBoss Cluster

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

below persistencemodule in thedomain.xml file.

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

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

domain.xml file.



4.12 Increase innodb_log_file_size in my.ini file

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

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

application size.

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

- Modify the SQLStatement toSet global max_allowed_

packet=10*1024*1024.

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

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

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

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

application.

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

In the my.ini file, increase the innodb_log_file_size =

4.13 Create Locator Component for Oracle Database

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

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

component.



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

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

Verify if the locator component is already installed

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

Select comp_name, version, status from dba_registry where upper

(comp_name) like '%MEDIA';

Select username from dba_users where username = 'MDSYS'

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

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

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

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

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

create Oracle database. Use the same database duringMobileFabric Installation.

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

locator is not installed.

i. Connect as SYSDBA

sqlplus "/as sysdba"

ii. CreateMDSYS User if not exists:

Create user mdsys identified by secret default tablespace

sysaux



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

creation.

iii. Run the below SQL to grant the privileges:

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

iv. Connect to MDSYS user:

Conn mdsys/secret

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

creation.

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

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

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

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

not throw the error: Invalid Data Type SDO_GEOMENTRY

Note: For license reference, refer to https://docs.oracle.com/database/121/SPATL/sdo_

locator.htm#SPATL340

4.14 Configure Load Balancer as Proxy in JBoss Multinode Setup

(Optional if SSL Offloading at Load Balancer)

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


https://docs.oracle.com/database/121/SPATL/sdo_locator.htm#SPATL340https://docs.oracle.com/database/121/SPATL/sdo_locator.htm#SPATL340


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

proxy-port details.

For example,

4.15 Configure Manager User for Tomcat

Manager User for Tomcat is required for publishing application tomiddleware. Configure themanager

user by adding the following entry under in the tomcat-user.xml file in

tomcat->conf folder.

Sample location to tomcat-user.xml file: \apache-tomcat-7.0.52-windows-x64\apache-tomcat-7.0.52\conf

4.16 Configuring Flyway Command-line Tool

After configuring Database for MobileFabric, you need to execute the SQL scripts for your database.

The following section explains how to configure properties in theflyway.conf file and execute

SQL scripts for your database.



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

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

flyway-commandline--. You can download

the FlywayCommand-line Tool specific to your Operating System. Minimum supported version is

Flyway 3.2.1.

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

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

flyway.conf file.

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

# --------

# Most drivers are included out of the box.

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

manually

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

# Derby :

jdbc:derby:

# H2 : jdbc:h2:

# Hsql : jdbc:hsqldb:file:

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

# MariaDB :

jdbc:mariadb://:/?=&=

...

# MySQL :

jdbc:mysql://:/?=&=...

# Oracle* :

jdbc:oracle:thin:@//:/


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


# PostgreSQL :

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

# solidDB* :

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

# SQL Azure* :

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

=

# SQL Server :

jdbc:jtds:sqlserver://:/

# SQLite : jdbc:sqlite:

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

#Flyway URL for MySQL

flyway.url=jdbc:mysql://:

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

schema name for the current module

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

The following table details schema names to be provided for each of the components:

Schema Name ForComponents

Provide current schema - for example:

l authglobaldb

Identity



Schema Name ForComponents


l waasglobaldb

Workspace


l accountsdb

Accounts


l konyadmindb

Admin


l mfreportsdb

Reports

# Fully qualified classname of the jdbc driver (autodetected by

default based on flyway.url)

flyway.driver=

# For DB2, user the following driver

flyway.driver=com.ibm.db2.jcc.DB2Driver

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

flyway.user=

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

)

flyway.password=

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



schema names are case-sensitive.

# (default: The default schema for the datasource connection)

# Consequences:

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

the default one during the migration.

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

containing the metadata table.

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

flyway.schemas=

# Kony Identity Services Database, replace the following

placeholders

# in SQL migrations for your database

flyway.placeholders.KONY_AUTH_LOG_LOCATION=C:MobileFabric/logs

flyway.placeholders.KONY_AUTH_LOG_OPTION=logfile

flyway.placeholders.KONY_AUTH_LOG_LEVEL=INFO

# Kony Workspace Services Database, replace the following

placeholders


flyway.placeholders.KONY_WAAS_LOG_LOCATION=C:MobileFabric/logs

flyway.placeholders.KONY_WAAS_LOG_LEVEL=INFO

flyway.placeholders.KONY_WAAS_LOG_OPTION=logfile

# For Kony Accounts Services Database, replace the following

placeholders


flyway.placeholders.KONY_ACCOUNTS_LOG_LOCATION=/logs

flyway.placeholders.WAAS_BASE_URL=/workspace



flyway.placeholders.KONY_ACCOUNTS_LOG_LEVEL=INFO

flyway.placeholders.KONY_ACCOUNTS_LOG_OPTION=logfile

flyway.placeholders.KONY_ACCOUNTS_LOGGER_JNDI= same as

# For AdminDB (konyadmindb), replace the following placeholders

in SQL migrations for your database

In case of DB2, the following placeholders values need to be

specified based on your Database

settings

flyway.placeholders.KONY_SERVER_CACHEID_TRANSPORT=""

flyway.placeholders.KONY_SERVER_JMS_INITIAL_CONTEXT_FACTORY=""

flyway.placeholders.KONY_SERVER_JMS_PROVIDER_URL=""

flyway.placeholders.KONY_SERVER_JMS_USER_NAME=""

flyway.placeholders.KONY_SERVER_JMS_USER_PASSWORD=""

flyway.placeholders.KONY_SERVER_KEYSTORE_LOCATION=""

flyway.placeholders.KONY_SERVER_LOG_LOCATION=""

flyway.placeholders.KONY_SERVER_MEMCACHED_COUNT=""

flyway.placeholders.KONY_SERVER_MEMCACHE_CLUSTER=""

flyway.placeholders.KONY_SERVER_RICH_CLIENT_DEPLOY=""

flyway.placeholders.KONY_SERVER_TRUSTSTORE_LOCATION=""

flyway.placeholders.KONY_SERVER_TRUSTSTORE_PASSWORD=""

flyway.placeholders.KONY_SERVER_LOG_OPTION="logfile"

flyway.placeholders.KONY_SERVER_SSL_SOCKETFACTORY_

PROVIDER=com.ibm.websphere.ssl.protocol.SSLSocketFactory

flyway.placeholders.KONY_SERVER_SSL_SERVERSOCKETFACTORY_

PROVIDER=com.ibm.websphere.ssl.protocol.SSLServerSocketFactory



flyway.placeholders.KONY_SERVER_LOGGER_JNDI_

NAME=jdbc/konyadmindb

# For ReportsDB (mfreportsdb), replace the following

placeholders in SQL migrations for your database

flyway.placeholders.KONY_METRICS_LOGGER_JNDI=jdbc/konyreports

flyway.placeholders.KONY_METRICS_LOG_LEVEL=INFO

flyway.placeholders.KONY_METRICS_LOG_OPTION=logfile

flyway.placeholders.KONY_METRICS_LOG_LOCATION=

3. Save theflyway.conf file.

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

commandlinetool\drivers.

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

KonyMobileFabric_Plugins folder and paste them to theFlyway SQL folder of the Flyway

Command-line Tool.

The following tables details the SQL files paths for each of the components in

KonyMobileFabric_Plugins folder:

For MySQL

MySQL- Path for SQL files in the KonyMobileFabric_Pluginsfolder

Component

\KonyMobileFabric_

Plugins\scripts\dbmigrations\commondbscripts

Identity



MySQL- Path for SQL files in the KonyMobileFabric_Pluginsfolder

Component

\KonyMobileFabric_

Plugins\scripts\waasdbmigrations\commondbscri

pts

Workspace

\KonyMobileFabric_

Plugins\scripts\accountsdbmigration

Accounts

\KonyMobileFabric_Plugins\middleware\admindb_

admindb_mysql

Admin DB

\KonyMobileFabric_

Plugins\middleware\reportsdb_reportsdb_mysql

Reports

\KonyMobileFabric_Plugins\sync\syncconsole-

mysql

Sync

Services

\KonyMobileFabric_Plugins\scripts\mysql-kpns-

migrations

Engageme

nt Services

For Oracle

Oracle- Path for SQL files in the KonyMobileFabric_Pluginsfolder

Component

\KonyMobileFabric_Plugins\scripts\migrations-

auth-oracle\commondbscripts

Identity



Oracle- Path for SQL files in the KonyMobileFabric_Pluginsfolder

Component

\KonyMobileFabric_

Plugins\scripts\mmigrations-waas-

oracle\commondbscripts

Workspace


accounts-oracle

Accounts


admindb_oracle

Admin DB

\KonyMobileFabric_

Plugins\middleware\reportsdb_reportsdb_oracle

Reports


oracle

Sync

Services

\KonyMobileFabric_Plugins\scripts\oracle-

kpns-migrations

Engagement

Services

For SQL Server

SQL Server - Path for SQL files in the KonyMobileFabric_Plugins folder

Component


auth-sqlserver\commondbscripts

Identity



SQL Server - Path for SQL files in the KonyMobileFabric_Plugins folder

Component


waas-sqlserver\commondbscripts

Workspace


accounts-sqlserver

Accounts


admindb_sqlserver

Admin DB

\KonyMobileFabric_

Plugins\middleware\reportsdb_reportsdb_mssql

Reports


sqlserver

Sync

Services

\KonyMobileFabric_Plugins\scripts\mssql-kpns-

migrations

Engagement

Services

For DB2

DB2 - Path for SQL files in the KonyMobileFabric_Plugins folder Component


auth-db2\commondbscripts

Identity



DB2 - Path for SQL files in the KonyMobileFabric_Plugins folder Component


waas-db2\commondbscripts

Workspace


accounts-db2

Accounts


admindb_db2

Admin DB

\KonyMobileFabric_

Plugins\middleware\reportsdb_reportsdb_db2

Reports


db2

Sync

Services

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

l For DB2, execute the SQL scripts with the following Flywaymigrate command along with

the following placeholder parameters: _DATA_TABLESPACE,

_INDEX_TABLESPACE, and_LOB_TABLESPACE

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

names for tablespace, index space and lob space If same name is given, that name

will need to be passed for all these parameters.



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

(identity services) with separate tablespace names:

flyway migrate -placeholders.AUTH_DATA_

TABLESPACE="TS32K" -placeholders.AUTH_INDEX_

TABLESPACE="IDX32K" -placeholders.AUTH_LOB_

TABLESPACE="LOB32K"

l For MySQL, Oracle, and SQL Server, execute the following Flywaymigrate command:

flyway migrate

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

or /opt/flyway/sql.or specific to your storage file path.


5. Installing MobileFabric on WebSphere with DB2 Manual Installation GuideVersion1.0

5. Installing MobileFabric on WebSphere with DB2

The following steps helps you how tomanually configureMobileFabric components (Identity,

Workspace, Accounts, and Integration Services) onWebSphere with DB2.

Note: For SyncManual Installation steps, refer to http://docs.kony.com/konylibrary/mf_manual_

install.htm

Note: For Engagement ServicesManual Installation steps, refer to

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

1. Prerequisites

l Requirements for MobileFabric with DB2: Create a big tablespace with big bufferpool of

32K page size as follows:

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

(DBA) or equivalent DB user will have access to create database with default tablespace with

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

LargeObject (CLOB) are used, you need to have the database created with default tablespace as

well as default temp tablespace with big pagesize of 32k.


CONNECT TO ;



COMMIT;


CREATE LARGE TABLESPACE IN DATABASE

PARTITION GROUP IBMDEFAULTGROUP


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


PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 32

PREFETCHSIZE AUTOMATIC

BUFFERPOOL BIGBUFFERPOOL OVERHEAD 7.5 TRANSFERRATE 0.06

AUTORESIZE YES


COMMIT;







AUTORESIZE YES


COMMIT;







AUTORESIZE YES


COMMIT;

CREATE SYSTEM TEMPORARY TABLESPACE "BIGTEMP" IN DATABASE

PARTITION GROUP IBMTEMPGROUP



PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE USING STOGROUP

IBMSTOGROUP EXTENTSIZE 1M


COMMIT;

CONNECT RESET;

l Software Requirements

l Hardware Requirements

l DB2 JNDI Datasource Setup

2. Configuring Database for MobileFabric

l Configuring Kony Identity (Auth) ServicesDatabase

l Configuring KonyWorkspace ServicesDatabase

l Configuring Kony Accounts ServicesDatabase

l Configuring Kony Admin Database

l Configuring KonyReports Database

l Configuring Device Database

l Configuring FlywayCommand-line Tool

3. Creating Shared Library Folders for MobileFabric - WebSphere

4. Creating Data Source for MobileFabric Console - WebSphere

5. Configuring Properties Files inWAR Files - WebSphere

6. Configuring KonyMobileFabric Integration Services

7. Configuring Integration Services (Server) Console Properties

8. DeployingWARFiles



For any issues related toWebSphere, refer toWebSphere FAQs


6. Configuring Database for MobileFabric Manual Installation GuideVersion1.0

6. Configuring Database for MobileFabric

The following section explains how to configure Database for KonyMobileFabric Identity service,

Console, Workspace, and Integration services.

l Configuring Kony Identity ServicesDatabase

l Configuring KonyWorkspace ServicesDatabase

l Configuring Kony Accounts ServicesDatabase

l Configuring Kony Admin Database

l Configuring KonyReports Database

l Configuring FlywayCommand-line Tool



6.1 Configuring Kony Identity (Auth) Services Database

6.1.1 MySQL

To configure Kony Identity Services Database, follow these steps:

1. Create two databases for authglobaldbandauthconfig with custom names along with

prefix and suffix. Prefix and suffix are optional. For example, database name is

authglobaldb.

Important: For identity services, you can create databaseswith custom names instead the

default databases such asauthglobaldbandauthconfig.

If you have created an identity services database with a custom name (for example,

authglobaldb), replace the custom database name in all

SQLscripts in the\KonyMobileFabric_

Plugins\scripts\dbmigrations\commondbscripts folder.


authconfig), replace the custom database name in all


Plugins\scripts\dbmigrations\commondbscripts folder.

2. Execute all SQL scripts by using the steps provided at Configuring FlywayCommand-line Tool

Kony Identity Service database is created.

6.1.2 Oracle

To configure Identity Services Database, follow these steps:



1. Create two schemas for authglobaldb and authconfig with custom names along with

prefix and suffix. Prefix and suffix are optional. For example, schema name is

authglobaldb.

Important: For identity services, you can create schemaswith custom names instead the

default schemas such asauthglobaldbandauthconfig.

If you have created an identity services schemawith a custom name (for example,

authglobaldb), replace the custom schema name in all

SQLscripts in the\KonyMobileFabric_Plugins\scripts\migrations-

auth-oracle\commondbscripts folder.

If you have created an identity services schemawith a custom name (for example,

authconfig), replace the custom schema name in all


auth-oracle\commondbscripts folder.

2. Execute all SQL scripts by using the steps provided at Configuring FlywayCommand-line Tool.

Kony Identity Service schema is created.

6.1.3 SQL Server

To configure Identity Services Database, follow these steps:

1. Create two databases for authglobaldb and authconfig with custom names along with

prefix and suffix. Prefix and suffix are optional. For example, database name is

authglobaldb.



Important: For identity services, you can create databaseswith custom names instead the

default databases such asauthglobaldbandauthconfig.


authglobaldb), replace the custom database name in all


auth-sqlserver\commondbscripts folder.


authconfig), replace the custom database name in all


auth-sqlserver\commondbscripts folder.


Kony Identity Service database is created.

6.1.4 DB2

To configure Kony Identity Services Database, follow these steps:

1. Create necessary tablespaces as follows:







CONNECT TO ;





COMMIT;





AUTOMATIC



COMMIT;





AUTOMATIC



COMMIT;





AUTOMATIC



COMMIT;




GROUP IBMTEMPGROUP


EXTENTSIZE 1M


COMMIT;

CONNECT RESET;

2. Create two schemas for authglobaldb and authconfig with custom names along with

prefix and suffix. Prefix and suffix are optional. For example, schema name is

authglobaldb.

Important: For identity services, you can create schemaswith custom names instead the

default schemas: authglobaldbandauthconfig.

If you have created a schemawith a custom name for authglobaldb (for example,

authglobaldb), replace the custom schema name for

authglobaldb in all SQLscripts in the\KonyMobileFabric_

Plugins\scripts\migrations-auth-db2\commondbscripts folder.

If you have created a schemawith a custom name for authconfig (for example,

authconfig), replace the custom schema name for

authconfig in all SQLscripts in the\KonyMobileFabric_

Plugins\scripts\migrations-auth-db2\commondbscripts folder.


Kony Identity Service schema is created.



6.2 Configuring Kony Workspace Services Database

6.2.1 MySQL

To configure Kony Workspace Services Database, follow these steps:

1. Create two databases for workspacesglobaldbandwaasglobaldbwith custom names

along with prefix and suffix. Prefix and suffix are optional. For example, database name is

waasglobaldb.

Important: For workspace, you can create databaseswith custom names instead the

default databases such asworkspacesglobaldbandwaasglobaldb.

For example, if you have created workspace databaseswith a custom names (

workspacesglobaldb and

waasglobaldb), replace one of these custom database

names in all SQLscripts in the\KonyMobileFabric_

Plugins\scripts\waasdbmigrations\commondbscripts folder.


KonyWorkspace database is created.

6.2.2 Oracle

To configure Workspace Service Database, follow these steps:

1. Create two schemas for workspacesglobaldbandwaasglobaldbwith custom names

along with prefix and suffix. Prefix and suffix are optional. For example, schema name is

waasglobaldb.



Important: For workspace, you can create one custom schema instead the default

schemas: workspacesglobaldbandwaasglobaldb.

For example, if you have created workspace schemawith a custom names (


waasglobaldb), replace one of these custom schema names

in all SQLscripts in the\KonyMobileFabric_

Plugins\scripts\mmigrations-waas-oracle\commondbscripts

folder.


KonyWorkspace schema is created.

6.2.3 SQL Server

To configure Workspace Service Database, follow these steps:

1. Create two databases for workspacesglobaldbandwaasglobaldbwith custom names

along with prefix and suffix. Prefix and suffix are optional. For example, database name is

waasglobaldb.

Important: For workspace, you can create databaseswith custom names instead the

default databases such asworkspacesglobaldbandwaasglobaldb.

For example, if you have created workspace databaseswith a custom names (




waasglobaldb), replace one of these custom database

names in all SQLscripts in the\KonyMobileFabric_

Plugins\scripts\migrations-waas-sqlserver\commondbscripts

folder.


KonyWorkspace database is created.

6.2.4 DB2

To configure Kony Workspace Database, follow these steps:








CONNECT TO ;



COMMIT;







AUTOMATIC



COMMIT;





AUTOMATIC



COMMIT;





AUTOMATIC



COMMIT;


GROUP IBMTEMPGROUP


EXTENTSIZE 1M


COMMIT;

CONNECT RESET;



2. Create two schemas for workspacesglobaldbandwaasglobaldbwith custom names

along with prefix and suffix. Prefix and suffix are optional. For example, schema name is

waasglobaldb.

Important: For workspace, you can create schemaswith custom names instead the default

schemas such asworkspacesglobaldbandwaasglobaldb.

For example, If you have created two schemaswith a custom name for

workspacesglobaldband waasglobaldb (


waasglobaldb), replace one of these custom schema names

in all SQLscripts in the\KonyMobileFabric_

Plugins\scripts\migrations-waas-db2\commondbscripts folder.


KonyWorkspace schema is created.



6.3 Configuring Kony Accounts Services Database

6.3.1 MySQL

To configure Kony Accounts Services Database, follow these steps:

1. Create a database with prefix and suffix for accounts. Prefix and suffix are optional. You can

create a database with a custom name. For example, database name is

accountsdb.

Important: If you have created an accounts database with a custom name (for example,

accountsdb), prepend the statement use

accountsdb in all SQLscripts in the beginning of every file in

\KonyMobileFabric_Plugins\scripts\accountsdbmigration

folder.

Important: For accounts, you can create a database with a custom name instead the

default database such asaccountsdb.

If you have created an accounts database with a custom name (for example,

accountsdb), replace the custom database name in all


Plugins\scripts\accountsdbmigration folder.


Kony Accounts database is created.

6.3.2 Oracle

To configure Kony Accounts Database, follow these steps:



1. Create a schemawith prefix and suffix for accounts. Prefix and suffix are optional. You can

create a schemawith a custom name. For example, database name is

accountsdb.

Important: If you have created an accounts schemawith a custom name (for example,


accountsdb in all SQLscripts in the beginning of every file in the

\KonyMobileFabric_Plugins\scripts\migrations-accounts-

oracle folder.

Important: For accounts, you can create a schemawith a custom name instead the default

schema such asaccountsdb.

If you have created an accounts schemawith a custom name (for example,

accountsdb), replace the custom schema name in all


accounts-oracle folder.


Kony Accounts schema is created.

6.3.3 SQL Server

To configure Kony Accounts Database, follow these steps:

1. Create a database with prefix and suffix for accounts. Prefix and suffix are optional. You can

create a database with a custom name. For example, database name is

accountsdb.



Important: If you have created an accounts database with a custom name (for example,


accountsdb in all SQLscripts in the beginning of every file in the

\KonyMobileFabric_Plugins\scripts\migrations-accounts-

sqlserver folder.






accounts-sqlserver folder.


Kony Accounts database is created.

6.3.4 DB2

To configure Kony Accounts Services Database, follow these steps:










CONNECT TO ;



COMMIT;





AUTOMATIC



COMMIT;





AUTOMATIC



COMMIT;





AUTOMATIC





COMMIT;


GROUP IBMTEMPGROUP


EXTENTSIZE 1M


COMMIT;

CONNECT RESET;

2. Create a schemawith prefix and suffix for identity services. Prefix and suffix are optional. You

can create a schemawith a custom name. For example, schema name is

accountsdb.

Important: If you have created a schemawith a custom name for accountsdb (for example,


accountsdb in all SQLscripts in the beginning of every file in

the\KonyMobileFabric_Plugins\scripts\migrations-accounts-

db2 folder.






accounts-db2 folder.




Kony Accounts schema is created.



6.4 Configuring Kony Admin Database

To configure Kony Admin Database, follow these steps:

1. Create a database with prefix and suffix for admin. Prefix and suffix are optional. You can create

a database with a custom name. For example, database name is

konyadmindb.

For MySQL sample query:

CREATE DATABASE konyadmindb;

For Oracle sample query:

CREATE USER konyadmindb identified by default

TABLESPACE USERS PROFILE default; ALTER USER konyadmindb QUOTA

UNLIMITED ON USERS;

GRANT CONNECT, RESOURCE TO konyadmindb;

For SQL Server sample query:

CREATE DATABASE konyadmindb;

For DB2, to create necessary schema for Admin, follow these steps:

l Prerequisites: create tablespaces as follows:

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

(DBA) or equivalent DB user will have access to create database with default tablespace with

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

LargeObject (CLOB) are used, you need to have the database created with default tablespace as

well as default temp tablespace with big pagesize of 32k.




CONNECT TO ;



COMMIT;







AUTORESIZE YES


COMMIT;







AUTORESIZE YES


COMMIT;









AUTORESIZE YES


COMMIT;

CREATE SYSTEM TEMPORARY TABLESPACE "BIGTEMP" IN DATABASE

PARTITION GROUP IBMTEMPGROUP

PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE USING STOGROUP

IBMSTOGROUP EXTENTSIZE 1M


COMMIT;

CONNECT RESET;

l DB2 sample query:

CREATE SCHEMA konyadmindb AUTHORIZATION ;

2. Configure the following properties in the V3__konyadmin--7.0.0.0.sql file

located in the\KonyMobileFabric_Plugins\middleware\admindb_

folder.



No.

Property name Placeholder

Example value

1 richclient.deploy ${KON

Y_

SERVE

R_

RICH_

CLIEN

T_

DEPLO

Y}

lib/apps (Directory where the rich client binaries will

be downloaded. Used by adminmodule)

2 memcache.cluster ${KON

Y_

SERVE

R_

MEMC

ACHE_

CLUST

ER}

10.10.10.10:21201 (: wherememcache

cluster is running)

3 memcache.no.of.c

lients

${KON

Y_

SERVE

R_

MEMC

ACHE

D_

COUN

T}

1



No.


Example value

4 cacheid.transport ${KON

Y_

SERVE

R_

CACH

EID_

TRANS

PORT}

Null

(Specify the transfer mode through below property.

Valid values are PARAM_ONLY, COOKIE_ONLY,

EITHER (Default) or null if memcache is not used)

5 ssl.trustStore ${KON

Y_

SERVE

R_

TRUST

STOR

E_

LOCAT

ION}

C:/programfiles/java/jdk1.7/lib/security/cacerts

(cacerts Location)

6 ssl.keyStore ${KON

Y_

SERVE

R_

KEYST

ORE_

LOCAT

ION}

C:/programfiles/java/jdk1.7/lib/security/cacerts

(cacerts Location)



No.


Example value

7 ssl.trustStorePass

word

${KON

Y_

SERVE

R_

TRUST

STOR

E_

PASS

WORD}

changeit

8 ssl.keyStorePass

word

${KON

Y_

SERVE

R_

TRUST

STOR

E_

PASS

WORD

changeit



No.


Example value

9 metrics.initialCont

extFactoryName

${KON

Y_

SERVE

R_

JMS_

INITIA

L_

CONT

EXT_

FACTO

RY}

l forWebLogic:

weblogic.jndi.WLInitialContex

tFactory

l forWebSphere:

com.ibm.websphere.naming.WsnI

nitialContextFactory

l if jboss_jms is used:

org.jboss.naming.remote.clien

t.InitialContextFactory

l if activemq is used:

org.apache.activemq.jndi.Acti

veMQInitialContextFactory

1

0

metrics.providerU

RL

${KON

Y_

SERVE

R_

JMS_

PROVI

DER_

URL}

l ForWebLogic: t3://:

l ForWebSphere: iiop://:

l For Tomcat/JBoss:

remote://:



No.


Example value

1

1

metrics.securityPri

ncipalName

${KON

Y_

SERVE

R_

JMS_

USER_

NAME}

Weblogic

(weblogic admin username)

1

2

metrics.securityCr

edentials

${KON

Y_

SERVE

R_

JMS_

USER_

PASS

WORD}

Weblogic123

(weblogic admin password)

1

3

metrics.userName ${KON

Y_

SERVE

R_

JMS_

USER_

NAME}

Weblogic

(weblogic admin username)



No.


Example value

1

4

metrics.password ${KON

Y_

SERVE

R_

JMS_

USER_

PASS

WORD}

Weblogic123

(weblogic admin password)

1

5

SERVER_LOG_

LOCATION

${KON

Y_

SERVE

R_

LOG_

LOCAT

ION}

C:/konymflogs/

(Log location for middleware log)

1

6

SERVER_

LOGGER_JNDI_

NAME

${KON

Y_

SERVE

R_

LOGGE

R_

JNDI_

NAME}

jdbc/konyadmindb


The location for SQL scripts is\KonyMobileFabric_

Plugins\middleware\admindb_.



Kony admin database is created.

4. In case ofWebSphere with DB2 only, add the additional rows in the mobilefabric_

configuration table of konyadmindb. To add these rows, execute the following SQL

query using DB2 SQLEditor.

insert into currentSchema.mobilefabric_configuration(prop_name,

prop_value, created_date , updated_date) values(' management_

server_host_name, server_host_ip/name ', CURRENT_