Kony MobileFabric Installation Guide Windows

Kony MobileFabric

Installation Guide - Windows

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 174

Kony MobileFabric Installation Guide - WindowsVersion1.3

Copyright 2014 by Kony, Inc.

All rights reserved.

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

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

04/26/2016 1.2 Document updated for 7.0.1

02/29/2016 1.0 Document Released for MobileFabric 7.0 GA



Table of Contents

1. Preface 7

1.1 Purpose 8

1.2 Intended Audience 8

1.3 Formatting ConventionsUsed in ThisGuide 8

1.4 Related Documents 9

1.5 Contact Us 10

2. Prerequisites 11

2.1 Software Requirements 11

2.2 Hardware Requirements 11

2.3 Heap and PermGen Settings 11

3. MobileFabric Topology and Components 12

3.1 Developer Environment 16

3.2 Production Environment 17

4. Preinstallation Tasks 18

4.1 Prerequisites for MobileFabric with Oracle 18

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

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

4.4 Install Memcached Server 26

4.5 Increase JVMmemory for WebLogic Server 28

4.6 PlaceMS SQLServer Connector JAR inWebLogic Classpath 28



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

4.8 Configure Load Balancers for Sending Host Information inMultinode 35

4.9 Configure Hibernate Dialect inWebLogic (only for WebLogic) 36

4.10 Update Listen Interfaces in host.xml for JBossCluster 36

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

Cluster 37

4.12 Increase innodb_log_file_size in my.ini file 38

4.13 Create Locator Component for Oracle Database 38

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

at Load Balancer) 40

5. Installation Modes - Kony MobileFabric 42

5.1 Installing KonyMobileFabric 43

5.1.1 StandaloneMode (Single Node) Installation 43

5.1.1.1 Log Location for Single Node Installation 94

5.1.2 JBossDomainMode (Multinode) Installation 98

5.1.2.1 Log Location for Multinode Installation 128

5.2 Installing KonyMobileFabric - Silent-mode 132

6. Upgrading Kony MobileFabric Components 134

6.1 Prerequisites 134

7. Installing Hotfix Archives for MobileFabric - Windows 144

7.1 Patch Installer GA Versions 144

7.2 Prerequisites 144



8. Uninstalling Kony MobileFabric 153

9. Post-Installation Tasks 159

9.1 Configuring Secure Sockets Layer (SSL) Certificate 159

9.1.1 How to Add an Installer Generated Self-Signed SSLCertificate to Cacerts 159

9.1.2 How to Add an Existing SSLCertificate to Cacerts 160

9.2 JDK Version Compatibility 161

9.3 How to ConfigureMemcached for Integration Services 161

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

installation) 162

10. FAQs and Troubleshooting 164

10.1 How to Configure JBossCluster 170

10.2 How to Configure a Custom JAR File onWebLogic 170

10.3 How to Configure Heap and PermGen Size 171

10.3.1 Configuring Heap and PermGen Size for Tomcat 171

10.3.2 Configuring Heap and PermGen Size for JBoss 171

10.3.3 Configuring Heap and PermGen Size for WebLogic 171

10.4 How to ConfigureMobileFabric Behind a Reverse Proxy 172

10.5 How to Configure Frontend HTTPS to Tomcat HTTP Redirection 173

10.6 WebSphere FAQs 174

10.7 How to Change Log Levels 174


1. Preface Kony MobileFabric Installation Guide - WindowsVersion1.3

1. Preface

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

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

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

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

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

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 used for granting access to

your application. MobileFabric supports the following authentication services: Microsoft Active

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

Kony Facebook, and KonyUser Repository.

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

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

l Orchestration: Allows you to create two types of orchestration services. They are:

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

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

met.



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

application. Sync supports onlyWeb Services, except SAP Sky.

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

services for your application.

This document explains how to install the KonyMobileFabric console.

1.1 Purpose

The document helps you familiarize with procedural information to install KonyMobileFabric console in

your system.

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

1.3 Formatting Conventions Used in This Guide

The following formatting conventions are used throughout the document:

Convention Explanation

Monospace l User input text, system prompts, and responses

l File path

l Commands

l Program code

l File names



Convention Explanation

Italic l Emphasis

l Names of books and documents

l New terminology

Bold l Windows

l Menus

l Buttons

l Icons

l Fields

l Tabs

URL Active link to a URL

Note:Provides helpful hints or additional information.

Important:Highlights actions or information that might cause problems to

systems or data

1.4 Related Documents

Document Purpose

Kony MobileFabric

User Guide

This guide helps you understand how to create a Kony MobileFabric

account, add services, and publish apps.



1.5 Contact Us

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

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

contact [email protected].


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

2. Prerequisites Kony MobileFabric Installation Guide - WindowsVersion1.3

2. Prerequisites

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

Console.

2.1 Software Requirements

For software system requirements, click here.

2.2 Hardware Requirements

Component Requirement

Processor Quad-core processor

Memory 16GB

Internal Storage 150GB

Network 100Mbps Ethernet interface card

2.3 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/general/mobilefabric_supported_devices_os_browsers/Default.htm#MobileFabric.htm?TocPath=Kony%2520MobileFabric|_____0http://docs.kony.com/konylibrary/mobilefabric/resources/websphere_faqs.htm

3. MobileFabric Topology and Components Kony MobileFabric Installation Guide - WindowsVersion1.3

3. MobileFabric Topology and Components

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

identity services, developer environment, and production environment.

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

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

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



An overview of theMobileFabric architecture and components follows:



An overview of theMobileFabric deployment architecture follows:

The following table describes the components of MobileFabric:

Convention Description

Identity This component validates user accounts and applications for authentication

and authorization.

l Authentication identifies log-on credentials of a user.

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

role.

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




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

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

environments, and publish apps to an environment.

This component uses auth service for authorizing requests based on user

roles.

Workspace

(WaaS)

Workspace configures MBaaS services (applications, identity, integration,

orchestration, synchronization, and engagement services). After these

services are configured, these services must be published to respective

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

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

application.

Environments

(Engagement

Services, Sync

Services,

Integration

Services)

This component adds runtime capabilities to apps, such as engagement

services, synchronization services, and integration services.

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

test the services shown 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


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



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

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

fetches the response from the backend and provides the required information

to the device in the JSON format.

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

same runtime capabilities as themiddleware.

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

themiddleware.war. Similarly when you use only standalone Kony

Server, you can ignore the services.war.

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

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

example, you can use one of the following choices:

-Install All Components on one node.

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

Services, and Sync Services on separate nodes.

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

3.1 Developer Environment

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

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

Installation.


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


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

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

Install Guide.

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

multi-node (Domain Mode).

Important: By default KonyMobileFabric Consolidated installer supportsmemcached server only

in case of multinode installation.

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

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

steps provided at How to Install Memcached Server.

3.2 Production Environment

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

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

more details, refer to Multinode Installation.


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

4. Preinstallation Tasks Kony MobileFabric Installation Guide - WindowsVersion1.3

4. Preinstallation Tasks

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

l Ensure access to a database server.

l Ensure that a database user should be granted all permissions.

4.1 Prerequisites for MobileFabric with Oracle

For installingMobileFabric Database for Oracle, complete the following steps:

l

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 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 DownloadKonyMobileFabricSetup.zip file (for release 7.0.1 GA) from

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

installer from the community portal, follow these steps:

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

password from your sales representative or partner.

2. Navigate to the Kony MobileFabric section and click the Kony v7.0 GA version tab.

3. Select the specific release from the Version drop-down list and then click on the specific

release related files you want to download. For example, if you want to download Kony

MobileFabric 7.0.1 GA installer, click the Kony v7.0 GA tab, select the

7.0.1 GA version from the drop-down list, and then click the Download button. The

following is a sample screen.

TheKonyMobileFabricSetup.zip file contains the following files:


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


n KonyMobileFabricInstaller-7.0.1.GA.exe

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

n README.txt

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, shown below:



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, shown below:



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, shown below:



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 Studio of 2048-Kilobytes(2MB) an error appears while publishing. Increase thesize of

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

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

In the my.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,


5. Installation Modes - Kony MobileFabric Kony MobileFabric Installation Guide - WindowsVersion1.3

5. Installation Modes - Kony MobileFabric

You can install MobileFabric by any of the followingmodes:

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

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

installation Tasks section.

l InstallingMobileFabric - GUI (for Windows installations)

l Single Node Installation

l JBossMultinode Installation

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



5.1 Installing Kony MobileFabric

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

MobileFabric components.

The primary purpose of KonyMobileFabric installer user interface is to display information to a user,

prompt the user for information needed to install, and configureMobileFabric components on the

system. KonyMobileFabric installer user interface also displays information about the progress of

system changes as they are installed. This section explains new installation on theWindows platform.

Important: You need the required hardware and access to the supporting software noted 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 KonyMobileFabric in your computer.

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

5.1.1 Standalone Mode (Single Node) Installation

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

1. Unzip theKonyMobileFabricSetup.zip file.

2. Double-clickKonyMobileFabricInstaller-7.0.1.0.GA.exe 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 MobileFabric windows appears.

Read the instructions carefully before installing KonyMobileFabric 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 two options.

7. Choose the New Installation (choose components to install) option for new installation. While

installing, select one or more check boxes for the supported components. By default, the

Console, Identity Services, Integration Services, Engagement Services, and Sync Services

check boxes are selected.



8. In the New Installation (choose components to install), select one or more check boxes:

l Console - To install KonyMobileFabric Console, select the Console check box.

The system creates the following databases: mfconsoledb,

mfaccountsdb, andmfreportsdb.

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

box.

The system creates the following databases: idglobaldb and

idconfigdb.

l Integration Services - To install KonyMobileFabric Integration Services, select the

Integration Services check box.

The system creates the following databases: konyadmindb andkonymfreportsdb.



l Engagement Services - To install KonyMobileFabric Engagement Services, select the

Engagement Services check box.

The system create the following databases: xxxxx and

xxxxxxxxx.

l Sync Services - To install KonyMobileFabric Sync, select the Sync Services check

box.

The system create the following databases: xxxxxxx and

xxxxxxxxxx.

Reports DatabaseThe reports database is used for configuring reports.

The Installer creates themfreportsdb if you are installing the following KonyMobileFabric

components:

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

Services )

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

Services )

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

Services )

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



asmfreportsdb along with themfconsoledb and

mfaccountsdb. For example, your report database name is konymfreportsdb1

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

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

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

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

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

window.

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

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

you like to install field.

10. Click Choose to browse the required folder from your system.



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

server. It can be Tomcat, JBoss,WebLogic, or WebSphere. By default, the Application Sever is

set to Tomcat.

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

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

Manual Install Guide.

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

(Domain Mode).


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


12. In the Application Server window, click the appropriate option and click Next.

l If you select Tomcat, the HTTP or HTTPS window appears.

l If you select JBoss, the InstallationModewindow appears.

l If you select WebLogic 12c, the Application Server Details window for WebLogic

appears.

l If you select WebSphere 8.5.5.5, the Application Server Details window for WebSphere

appears.

13. Click Next. The Installation Mode window appears asking you to choose themode. By default,

this option is set to Standalone Mode.



Important: To install single node on JBoss, click Standalone Mode.

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.

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

Hostname/IP Address, HTTPPort, and JMS Remoting port. Click Next.



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

Hostname/IP Address, HTTPPort, HTTPSPort, and JMS Remoting port. Click Next.



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

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

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

If your SSL certificate is not configured, the systemwill display an error - for example,

"peer not authenticated."

For details, refer to Troubleshoot with SSLCertificate Issues.

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

> b, one of the following error messages appears:



l If you provide an invalid hostname/IP 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:

15. After you configure the application server details in the previous 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: \keystore.jks

i. Enter details for the following fields:

l Organization Unit: Enter your business unit name.

l Host Name: Enter your domain name - for example, konylabs.net

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 .JKSfile 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 SSLConfiguration window, enter the file path for keystore file and password

details.

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

displayed:



16. Click Next to display the Service Details window.

17. In the Service Details window, enter your current system log-in details.

Important: Follow the below step only when you chooseWebLogic 12c in the Application

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

18. If you chooseWebLogic 12c in the Application Server window, only then the following

Application Server Details window will appear.

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

Components:



l Fully Qualified Public URL of MobileFabric Console: Enter load balancer URL

to use public communication.

l Hostname/IP Address of WebLogic Administrator Server: Enter IP

Address/Hostname of theWebLogic Administrator Server.

l WebLogic Administrator Port: Enter native port of WebLogic Administrator

Server.

l WebLogic Java Messaging Service (JMS) Port: Enter WebLogic -JMS port.

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.

Important: To add environments toMobileFabric Console, add the following

configuration inside thesecurity-configuration tag of the

config.xml file of WebLogic Server.

false

After configuring the security-configuration tag, restart the server

fromWebLogic console. In case ofWebLogic cluster, restart all servers from

WebLogic console.

n The following window will appear only if you select the Console check box at

Install Components:



n The following window will appear only if you the Identity Services check box

at Install Components:



n The following window will appear only if you the Integration Services check

box at Install Components:



n The following window will appear only if you the Engagement Services

check box at Install Components:



n The following window will appear only if you the Sync Services check box at

Install Components:



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:



Important: Follow the below step only when you chooseWebSphere 8.5.5.5. in the

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

19. If you chooseWebSphere 8.5.5.5 in the Application Server window, only then the following

Application Server Details window will appear.

Important: While installingMobileFabric onWebSphere, if you face any issues, refer to

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

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

Components. Enter the following details:




l Fully Qualified Public URL of MobileFabric Console: Enter load balancer URL


l Hostname/IP Address of WebSphere Administrator Server: Enter IP

Address/Hostname of theWebSphere Administrator Server.

l WebSphere SOAP Connector Port: Enter SOAP connector port of WebSphere

Server.

l WebSphere Java Messaging Service (JMS) Port: Enter WebSphere-JMS port.

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



WebSphere Administrator Server.

n The following window will appear only if you select the Console check box at

Install Components:

n The following window will appear only if you the Identity Services check box

at Install Components:



n The following window will appear only if you the Integration Services check

box at Install Components:



n The following window will appear only if you the Engagement Services

check box at Install Components:



n The following window will appear only if you the Sync Services check box at

Install Components:



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

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

window, shown below:

WebSphere:cell=KH2013Node01Cell,node=KH2013Node01,serve

r=server1



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 to your /AppServer. This is required for the configuration of shared libraries and

successful deployment of applications.

2. If you are installing Integration Services, please configure JavaMessaging Service

(JMS) using stepsmentioned at below URL:

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


http://docs.kony.com/konylibrary/integration/kmf_installation_websphere/Default.htm#Upgrading_Kony_Server_Manually_WebSphere_5.6_6.0.htm%23Configur?TocPath=Upgrading%2520Kony%2520MobileFabric%2520Integration%2520Service%2520from%25205.6%2520to%25206.0%2520Manually%2520for%2520WebSphere|Upgrading%2520Metrics|_____1


websphere/Default.htm#Upgrading_Kony_Server_Manually_WebSphere_5.6_

6.0.htm#Configur%3FTocPath%3DUpgrading%2520Kony%2520MobileFabric%25

20Integration%2520Service%2520from%25205.6%2520to%25206.0%2520Manua

lly%2520for%2520WebSphere%7CUpgrading%2520Metrics%7C_____1

The installation will not work without the above steps.

For more information and FAQonWebSphere installation, refer to


20. 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 5.7.


http://docs.kony.com/konylibrary/integration/kmf_installation_websphere/Default.htm#Upgrading_Kony_Server_Manually_WebSphere_5.6_6.0.htm%23Configur?TocPath=Upgrading%2520Kony%2520MobileFabric%2520Integration%2520Service%2520from%25205.6%2520to%25206.0%2520Manually%2520for%2520WebSphere|Upgrading%2520Metrics|_____1http://docs.kony.com/konylibrary/integration/kmf_installation_websphere/Default.htm#Upgrading_Kony_Server_Manually_WebSphere_5.6_6.0.htm%23Configur?TocPath=Upgrading%2520Kony%2520MobileFabric%2520Integration%2520Service%2520from%25205.6%2520to%25206.0%2520Manually%2520for%2520WebSphere|Upgrading%2520Metrics|_____1http://docs.kony.com/konylibrary/integration/kmf_installation_websphere/Default.htm#Upgrading_Kony_Server_Manually_WebSphere_5.6_6.0.htm%23Configur?TocPath=Upgrading%2520Kony%2520MobileFabric%2520Integration%2520Service%2520from%25205.6%2520to%25206.0%2520Manually%2520for%2520WebSphere|Upgrading%2520Metrics|_____1http://docs.kony.com/konylibrary/integration/kmf_installation_websphere/Default.htm#Upgrading_Kony_Server_Manually_WebSphere_5.6_6.0.htm%23Configur?TocPath=Upgrading%2520Kony%2520MobileFabric%2520Integration%2520Service%2520from%25205.6%2520to%25206.0%2520Manually%2520for%2520WebSphere|Upgrading%2520Metrics|_____1


l Enter the following database details for MySQL 5.7.

o Database Server Hostname/IP: Enter the DB server Hostname/IP to be used to

create a database of selected components of KonyMobileFabric. By default, the

server Hostname/IP 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 Reports Database Name: Enter the reports database name that is created during

MobileFabric installation. Refer to Install Components.

The system verifies the entered database name - for example,

SampleReportsDatabase. If the reports database name does not exist, the

system displays the warningmessage: Reports databaseSampleReportsDatabase does not exist. Do you want to

create a new database?, shown below:

Click Yes. The system creates the reports database - for example,

SampleReportsDatabase.

Important: If you try to install Integration Services and Console in different

nodes, ensure that you point to the same reports database tomake reports

feature work properly.

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

o Database Name Suffix: Enter valid suffix for all databases - for example, 1.

l Enter the following database details for Oracle 12c.






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

is set to 1521 for oracle.

o Service ID: Enter Oracle service ID. Service ID is unique alias given to an instance

name of Oracle DB.

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.


MobileFabric Installation. Refer to Install Components.










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




l Enter the following database details for SQL Server 2012 R2.




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

set to 1433 for SQL.

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

user - for example, dbclient.

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

information is optional.



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

database user.


MobileFabric Installation. Refer to Install Components.










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




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

example:

21. After entering database server details, 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 components such as Integration Services,

Engagement Services, and Sync Services on Tomcat or JBoss on a single node. You can select

the these components at Install Components.



22. Select the Create MobileFabric 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. :. 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 user's identity.

23. Enter the databases details, and click Next. The Pre-Installation Summary window appears.



24. Click Install. The Installing Kony MobileFabric window appears.

Note: Sometimes, even after showing 100% installation progress, MobileFabric Installer

takes around 20moreminutes to complete installation onWindows.

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

message.



25. Click Done to close the window.

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

domain.subdomain.crt) into your MobileFabric Installer's JRE trusted certificate

authority (CA) certificates file - for example,

C:\KonyMobileFabric\jre\lib\security\cacerts

If your SSL certificate is not configured, the systemwill display an error message - for

example, "peer not authenticated."

For details, refer to Troubleshoot with SSLCertificate Issues.



5.1.1.1 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 KonyMobileFabric: \logs

o If you install Console, the \logs folder has three log files. They

are: mbaasportal.log (for mbaas portal), accountsService.log (for

accounts), andworkspaceService.log (for workspace.)

o If you install Identity Service, the \logs folder has one log file -

authService.log (for authentication.)

l For KonyMobileFabric Integration: \logs

o If you install Integration Service, the \logs folder has five log

files. They are: admin.log (for admin), datasource-payload.log (for

datasource), device-payload.log (for device), download.log (download),

andmiddleware.log (middleware.)

Note: Based on the combination of components selected during installation, the

\logs folder will have log files for each component.

l For KonyMobileFabric Engagement Services: \logs folder contains

these log files: kms.log andkms-messages.log.

l For KonyMobileFabric Sync: \logs log folder contains these log files:

syncconsole.log andsyncservice.log.

l To check Tomcat Server logs, refer to the following location:

\tomcat\logs



For JBoss



l For KonyMobileFabric: \logs

o If you install Console, the \logs folder has three log files. They



o If you install Identity Service, the \logs folder has one log file -


l For KonyMobileFabric Integration: \logs

o If you install Integration Service, the \logs folder has five log





\logs folder will have log files for each component.

l For KonyMobileFabric Engagement Services: \logs folder contains


l For KonyMobileFabric Sync: \logs log folder contains these log files:


l To check JBoss Server logs, refer to the following location:

\standalone\logs



For WebLogic



l For KonyMobileFabric: \konymflogs

o If you install Console, the \konymflogs folder has three log files. They



o If you install Identity Service, the \konymflogs folder has one log file -


o If you install Integration Service, the \konymflogs folder has five log




n For example, onWindows, if an admin installedMobileFabric as a User1, product

logs are located atC:\Users\User1\konymflogs


\konymflogs folder will have log files for each component.

l For KonyMobileFabric Engagement Services: \konymflogs folder contains


l For KonyMobileFabric Sync: \konymflogs log folder contains these log files:


l For WebLogic Server logs, by default, the server log file is located below the server instance's

root directory: root-directory\server-name\server-name.log

For example, if you created a domain in the c:\user_projects\domains\MyDomaindirectory, and



you used thec:\user_

projects\domains\MyDomain\startWebLogicServer.cmdscript to start the

server, then, by default, the log file is located inc:\user_

projects\domains\MyDomain\MyServer\MyServer.log.

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

directory\server-namedirectory.

For more details, refer to http://docs.oracle.com/cd/E13222_

01/wls/docs81/ConsoleHelp/logging.html#1045661

For WebSphere



l For KonyMobileFabric: \konymflogs

o If you install Console, the \konymflogs folder has three log files. They are:

mbaasportal.log (for mbaas portal), accountsService.log (for accounts),

andworkspaceService.log (for workspace.)

o If you install Identity Service, the \konymflogs folder has one log file -


o If you install Integration Service, the \konymflogs folder has five log files.

They are: admin.log (for admin), datasource-payload.log (for



n For example, on CentOS, if an admin installedMobileFabric as a User1, product

logs are located at/konymflogs.

n For example, onWindows, if an admin installedMobileFabric in C drive, product

logs are located atC:\konymflogs.


http://docs.oracle.com/cd/E13222_01/wls/docs81/ConsoleHelp/logging.html#1045661http://docs.oracle.com/cd/E13222_01/wls/docs81/ConsoleHelp/logging.html#1045661



\konymflogs folder will have log files for each component.

l For KonyMobileFabric Engagement Services: \konymflogs folder contains


l For KonyMobileFabric Sync: \konymflogs log folder contains these log files:


l For WebSphere Server logs, refer to the following location:

\AppServer\profiles\\logs\SystemOut.log

5.1.2 JBoss Domain Mode (Multinode) Installation

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

MobileFabric components onmultinode.

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

Preinstallation Tasks section.

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

1. Unzip theKonyMobileFabricSetup.zip file.

2. Double-clickKonyMobileFabricInstaller-7.0.1.0.GA.exe 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 MobileFabric windows appears.

Read the instructions carefully before installing KonyMobileFabric Console.



4. Read the instructions carefully, and click Next.

The LICENSE AGREEMENTwindow 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.



6. Click Next. The Install Components window appears with two options.

7. Choose the New Installation (choose components to install) option for new installation. While

installing, select one or more check boxes for the supported components. By default, the

Console, Identity Services, Integration Services, Engagement Services, and Sync Services

check boxes are selected.



8. In the New Installation (choose components to install), select one or more check boxes:

l Console - To install KonyMobileFabric Console, select the Console check box.

The system creates the following databases: mfconsoledb,

mfaccountsdb, andmfreportsdb.

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

box.

The system creates the following databases: idglobaldb and

idconfigdb.

l Integration Services - To install KonyMobileFabric Integration, select the Integration

Services check box.

The system creates the following databases: konyadmindb andkonymfreportsdb.



l Engagement Services - To install KonyMobileFabric Engagement Services, select the

Engagement Services check box.

The system create the following databases: xxxxx and

xxxxxxxxx.

l Sync Services - To install KonyMobileFabric Sync, select the Sync Services check

box.

The system create the following databases: xxxxxxx and

xxxxxxxxxx.

Reports Database

The reports database is used for configuring reports.

The Installer creates themfreportsdb if you are installing the following KonyMobileFabric

components:

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

Services)

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

Services)

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

Services)

Reports Database for Integration on a Separate Node:

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

reports database during the integration installation.

For example:

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

asmfreportsdb along with themfconsoledb and



mfaccountsdb. For example, your report database name is konymfreportsdb1

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

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

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

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

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

window.

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

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

you like to install field.

10. Click Choose to browse the required folder from your system.



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

server. It can be Tomcat, JBoss,WebLogic, or WebSphere. By default, the Application Sever is

set to Tomcat.

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

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

Tomcat, refer to MobileFabricManual Install Guide.

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

(Domain Mode).

12. In the Application Server window, click JBoss, and then click Next.


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


13. 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 single node, click Standalone Mode.

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

JBoss cluster is configured on your install system.

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

select Console, Identity Services, Integration Services, Engagement Services, and

Sync Services check boxes at Install Components:



Enter the following details:

o Fully Qualified Public URL of MobileFabric Console: Enter load balancer URL


o Master Node Hostname/IP Address: Enter public Hostname/IP 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 HTTP/HTTPS Port: Enter port of MobileFabric Console.

o Master Node Remoting Port: Enter JBoss-JMS port.



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

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

master node of the JBoss cluster.


select Console check box at Install Components:


o Fully Qualified Public URL of MobileFabric Console: Enter load balancer URL



node. Themaster node should be accessible from your installation system.





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

themaster node of the JBoss cluster.


select Identity Services check box at Install Components:


o Fully Qualified Public URL of Identity Services: Enter load balancer URL to use

public communication.










select Integration Services check box at Install Components:


o Fully Qualified Public URL of Integration Services: Enter load balancer URL to

use public communication.






o Master Node HTTP/HTTPS Port: Enter native port of JBossmaster node.

o Master Node Remoting Port: Enter native port of JBossmaster node.


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

master node of the JBoss cluster.


select Engagement Services check box at Install Components:




o Fully Qualified Public URL of Engagement Services: Enter load balancer URL








l The Appl