Manual Installation Guide - Linux

Kony MobileFabric™
Kony MobileFabric Messaging

Manual Installation Guide - Linux
On-Premises
Release 6.5
Document 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.
© 2015 by Kony, Inc. All rights reserved 1 of 121

Kony MobileFabric Messaging Manual Installation Guide - Linux
Version 3.0
Copyright © 2015 Kony, Inc.
All rights reserved.
March, 2016
This document contains information proprietary to Kony, Inc., is bound by the Kony license
agreements, and may not be used except in the context of understanding the use and methods of
Kony, Inc., software without prior, express, written permission. Kony, Empowering Everywhere, Kony
Modeler, and Kony Visualizer are trademarks of Kony, Inc. MobileFabric is a registered trademark of
Kony, Inc. Microsoft, the Microsoft logo, Internet Explorer, Windows, and Windows Vista are
registered trademarks of Microsoft Corporation. Apple, the Apple logo, iTunes, iPhone, iPad, OS X,
Objective-C, Safari, Apple Pay, Apple Watch, and Xcode are trademarks or registered trademarks of
Apple, Inc. Google, the Google logo, Android, and the Android logo are registered trademarks of
Google, Inc. Chrome is a trademark of Google, Inc. BlackBerry, PlayBook, Research in Motion, and
RIM are registered trademarks of BlackBerry. SAP® and SAP® Business Suite® are registered
trademarks of SAP SE in Germany and in several other countries. All other terms, trademarks, or
service marks mentioned in this document have been capitalized and are to be considered the
property of their respective owners.

Version 3.0
Revision History
Date Document Description of Modifications/Release

Version
03/07/2016 3.0 Updated the Software System Requirements (per physical

instance) link
01/20/2016 2.0 Updated Install and Configure KPNS section
06/17/2015 1.0 Document Release for Kony MobileFabric Messaging Manual

Installation for Linux 6.5 GA

Version 3.0
Table of Contents
1. Preface 7
1.1 Purpose 7
1.2 Intended Audience 7
1.3 Formatting Conventions 7
1.4 Contact Us 9
2. Introduction 10
2.1 Advantages of Using Kony MobileFabric Messaging 10
2.2 How Kony Push Notifications Works 11
3. Prerequisites 13
3.1 Hardware Requirements (per physical instance) 13
3.2 Software System Requirements (per physical instance) 13
3.3 Database System Requirements (per physical instance) 13
4. Corporate Firewall Settings 15
4.1 Installation Note 20
5. Install and Configure Kony MobileFabric Messaging 21
5.1 Installation Tasks 21
5.2 Database Setup 21
5.3 Download Kony MobileFabric Messaging Files 25
5.4 Setup Kony MobileFabric Messaging 28
6. Kony MobileFabric Messaging Upgrade 42

Version 3.0
6.1 Database Upgrade 42
6.2 Kony MobileFabric Messaging Upgrade 52
7. Configure Jboss 5.1 Server 53
7.1 Configure JBoss Server 53
7.2 Configure Datasource 55
7.3 Deploy KPNS 58
8. Configure Jboss 6.2 Server 59
8.1 Configure JBoss Server 59
8.3 Deploy Kony MobileFabric Messaging 71
9. Configure WebSphere Server 72
9.1 Configure the Application Server 72
9.2 Configure Database 74
9.3 Configure Shared Libraries for WebSphere 8 and 8.5 85
9.5 Configure WebSphere Network Deployment (7.0 and 8.5) - Multi-node 91
10. Configure WebLogic Server 98
10.1 Create New Domain 98
10.2 Create Cluster 99
10.3 Configure Application Server 103

Version 3.0
10.5 Start the Cluster 107
10.6 Deploy Application Web Archive File 110
11. Configure Tomcat Server 115
11.1 Database 116

1. Preface Kony MobileFabric Messaging Manual Installation Guide - Linux
Version 3.0
1. Preface
MobileFabric has multiple features that can be used - Identity, Integration, Orchestration, Sync, and
Messaging. 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 following MobileFabric features on premises:
l Kony MobileFabric Identity and Console
l Kony MobileFabric Integration
l Kony MobileFabric Messaging
l Kony MobileFabric Sync
Kony MobileFabric Messaging provides a generic push notifications service that allows you to send
push notifications to multiple platforms (for example, iPhone, Android, BlackBerry, and Windows)
using a single interface. KPN also manages the requirements of individual platforms for example,
formatting, status query, retry on failure and so on.
1.1 Purpose
This document describes how to install and use Kony push notifications.
1.2 Intended Audience
The intended audience for this document are the developers who want to have an understanding of
Kony push notifications.
1.3 Formatting Conventions
The following are the formatting conventions used throughout the document:

Version 3.0
Conventions Explanation
Monospace l User input text, system prompts, and responses
l File path
l Commands
l Program code
l File names.
Italic l Emphasis
l Names of books and documents
l New terminology.
Bold l Windows
l Menus
l Buttons
l Icons
l Fields
l Tabs
l Folders.
URL Active link to a URL.
Provides helpful hints or additional information.

Note:
Highlights actions or information that might cause problems

Import-
to systems or data.
ant:

Version 3.0
1.4 Contact Us
We welcome your feedback on our documentation. Write to us at techpubs@kony.com. For technical

questions, suggestions, comments, or to report problems on Kony's product line, contact
productsupport@kony.com.

2. Introduction Kony MobileFabric Messaging Manual Installation Guide - Linux
Version 3.0
2. Introduction
KPN also allows you to send push notifications to customer specific IDs (for example, email
addresses) that a customer provides.You can also query the status of the messages.
2.1 Advantages of Using Kony MobileFabric Messaging
The advantages of using Kony MobileFabric Messaging include:
l Ease of use: You can use a single interface to send push notifications to numerous devices
running on various platforms. You can also choose to send push notifications to custom IDs
instead of identifiers received from the push notification service providers.
l No platform specific formatting: Kony MobileFabric Messaging allows you to leverage all the
features available on individual platforms (features available on iPhone, Android, BlackBerry,
and Windows) without any platform specific formatting requirements.
l Reliable: Automatically performs a specified number of retries on push failure.
l Extensible: Kony MobileFabric Messaging supports all the platforms that support Push
Notifications (Apple, BlackBerry, Android and Windows). Provision is made to support any new
feature with a negligible upgrade impact.
l Scalable: Kony MobileFabric Messaging supports clustering to handle a large number of

requests.
l Robust: Kony MobileFabric Messaging performs multiple levels of validations and reduces the
resource utilization for invalid or improper requests.
l Ease of integration: Kony MobileFabric Messaging accepts requests in XML, and JSON (only
for Messaging) format and thereby offers an easy integration.
l Modular: Kony MobileFabric Messaging is divided into Subscription, and Messaging and
Query. These modules can be used independently and are not interdependent. This allows
modular integration with ease.

Version 3.0
2.2 How Kony Push Notifications Works
To send push notifications using KPN is a two-stage process:
l Stage 1: Subscription
l Stage 2: Messaging
Stage 1 involves the following process:
1. The mobile application subscribes or registers for push notifications service with a provider. If
the subscription is successful, the push notifications service provider returns a unique identifier
to the mobile application.
The following is the list of platforms and corresponding push notifications service providers, and
the unique identifiers they return:
Platform Push Notifications Service Unique Identifier
Android Android Google Cloud Messenger (GCM) Registration ID
BlackBerry BlackBerry Infrastructure Device ID
Apple Apple Push Notification Service (APNS) DeviceToken
Windows Phone Windows Push Notification Service (WNS) Unique URL
Kony Platform provides APIs that you can use to enable push notifications for an application on a
device and also an API to deregister from the push notification service.
2. The mobile application sends a subscription request along with the unique identifier to the Kony
Push Notifications Server (KPNS), which in turn sends a Kony Subscription ID to the mobile
application.
Stage 2 involves the following process:

Version 3.0
1. The message you send to the subscriber is first sent to the KPNS in a Kony specific format.
The KPNS immediately sends a response containing a unique Kony Message Identifier (can be
used for status queries).
2. The KPNS processes the message and sends it to the push notifications service provider
(Apple, BlackBerry, Android, or Windows).
3. The push notification service provider, then sends the push notifications to the device.
The following image illustrates the two stages involved in KPNS:

3. Prerequisites Kony MobileFabric Messaging Manual Installation Guide - Linux
Version 3.0
3. Prerequisites
The following sections provide you the information to understand the hardware and software required
to install Kony MobileFabric Messaging.
3.1 Hardware Requirements (per physical instance)
Component Requirement
Processor Quadra Core 2.2 MHz
memory 16 GB
Internal Storage 146 GB (15K RPM) with 2 Drives (Raid 1)
Network 2 Gigabit Ethernet Ports
IP Configuration Statically assigned IP addressing
Operating System Windows 7 / 8 64 bit
3.2 Software System Requirements (per physical instance)
For software system requirements, click here
3.3 Database System Requirements (per physical instance)
Processor Dual Core Processor
memory 16 GB

3. Prerequisites Kony MobileFabric Messaging Manual Installation Guide - Linux
Version 3.0
Internal Storage 73 GB (15K RPM) with 4 Drives (Raid 5)
External Storage 200 GB (RAID 5 + HS) SAN Storage with HA Fiber HBA Connection
Network 2 Gigabit Ethernet Ports
Operating System Windows Server 2008

4. Corporate Firewall Kony MobileFabric Messaging Manual Installation Guide -
Settings Linux
Version 3.0
4. Corporate Firewall Settings
The following firewall settings need to be configured for successful Kony MobileFabric Messaging
installation.
Source Destination Ports Protocol Direc Act Descri

tion ion ption
Kony android.apis.google.co 443 TCP Both All Allow

Mobile m, o the
Fabric android.googleapis.com w Kony
Messa Mobile
ging Fabric
Server Messa
ging
Server
to
access
Google
's cloud
Messa
ging
servic
e.

Settings Linux
Version 3.0

tion ion ption
Kony feedback.push.apple.co 2196 TCP Both All Allow

Mobile m, o the
Fabric feedback.sandbox.push. w Kony
Messa apple.com, 17.0.0.0/8 Mobile
ging (17.0.0.1 to Fabric
Server 17.255.255.254) Messa
ging
Server
to
access
Apple's
APNs
service
Kony gateway.push.apple.co 2195 TCP Both All Allow

Mobile m, o the
Fabric gateway.sandbox.push. w Kony
Messa apple.com, 17.0.0.0/8 Mobile
ging (17.0.0.1 to Fabric
Server 17.255.255.254) Messa
ging
server
to
access
Apple's
APNs
servic
e.

Settings Linux
Version 3.0

tion ion ption
Kony All subdomains of 443 TCP Both All Allow

Mobile pushapi.eval.blackberry. o connec
Fabric com Sample Push URL: w t to
Messa https://cpxxxxxxxxxxxx Blackb
ging xxxxxxxxxx. erry
Server pushapi.eval.blackberry. Cloud
co m/mss/PD_ through
pushRequest this
port
Kony http://sn1.notify.live.net 443 TCP Both Allow

Mobile All connec
Fabric o t to
Messa w Windo
ging ws
Server Cloud
(WPN
S)
through
this
port
Kony https://login.live.com 443 TCP Both All Allow

Mobile o connec
Fabric w t to
Messa Windo
ging ws
Server Cloud
(WNS)
through
this
port

Settings Linux
Version 3.0

tion ion ption
Internal Allow your firewall to 5228, TCP, HTTP, Both All Android
Corpor accept outgoing 5229, HTTPS, o device
ate connections to all IP 5230 UDP w s will
WiFi addresses contained in connec
router the IP blocks listed in t to
for Google's ASN of 15169. GCM
Androi Reference link for the IP through
d Addresses this
Mobile http://bgp.he.net/AS151 port.
Device 69
s
Internal gateway.push.apple.co 5223 TCP Both All Apple

Corpor m, o device
ate feedback.push.apple.co w s
WiFi m, connec
router gateway.sandbox.push. t to
for iOS apple.com, APNs
Device feedback.sandbox.push. servers
s apple.com, 17.0.0.0/8 through
(17.0.0.1 to this
17.255.255.254) port.

Settings Linux
Version 3.0

tion ion ption
Internal ax.init.itunes.apple.com, 80, TCP Both All Apple

ocsp.apple.com 443 o device
Corpor w s will
ate connec
WiFi t to
router public
for iOS Apple
Device OCSP
s and
iTunes
service
through
this
port.
Internal Add the list IPs specified TCP,HTTP, Both All Windo
Corpor in the following WNS HTTPS, o ws
ate URL UDP w device
WiFi http://www.microsoft.co s will
router m/en- connec
for us/download/details.asp t to
Windo x?id=44238 WNS
w through
Device this
s port.
APNS works only with SOCKS proxy type. It is because of the current technical limitation from Apple
to communicate the below push notification ports when a proxy server is in place between Kony
MobileFabric Messaging server and the firewall.

Settings Linux
Version 3.0
l TCP port 2195 (used to send notifications to the APNs)
l TCP port 2196 (used by the APNs feedback service)
Alternatively, as a workaround, to communicate with the above ports, the system on which the Kony
MobileFabric Messaging server is installed should bypass the proxies and communicate with the
firewall directly.
4.1 Installation Note
The domain/server/configuration names mentioned in this document are used for the convenience of
this document. You may use any name suitable for your installation needs.
Make sure that each resource type within a domain must have a name and a JNDI name that is unique
for all configuration objects in the domain. Within a domain, each server, machine, cluster, and JDBC
connection pool, and any other resource type must be named uniquely and must not use the same
name as the domain. Therefore, the name you provide for the Managed Server, Cluster, JMS Server,
JMS Topic, or any other resource should be unique in that domain. The JNDI name provided for JMS
resources and JDBC resources must be unique.

5. Install and Configure Kony Kony MobileFabric Messaging Manual Installation
MobileFabric Messaging Guide - Linux
Version 3.0
5. Install and Configure Kony MobileFabric Messaging
This section of the document provides you with the instructions for installing and configuring the Kony
MobileFabric Messaging. Make sure that you have the required hardware and access to the
supporting software mentioned in the Prerequisites section.
Important: The configurations and examples in this document provide a better understanding of
the concepts. We encourage you not to copy-paste them for your installation and execution as
they may not match your settings. For example, user names, passwords, and IP addresses.
5.1 Installation Tasks
You need to perform the following tasks to install Kony MobileFabric Messaging successfully.
l Database Setup
l Configure_JBoss
l Setup Kony MobileFabric Messaging
l Configure JBoss Server or Configure WebSphere or Configure WebLogic
5.2 Database Setup
Before you proceed with the Installation of Kony Push Notification Server, ensure that you install the
Kony Databases. For further information on Kony Database Setup, following are the databases
supported by Kony MobileFabric Messaging.
5.2.1 MySQL
Follow these steps to execute MySQL DB scripts:

Version 3.0
1. Create a database with a name "kpnsdb" with character set as "utf8" and collate as
"utf8_unicode_ci" using following command
-> CREATE DATABASE kpnsdb CHARACTER SET utf8 COLLATE utf8_unicode_

ci;
2. Execute the scripts in below order:
i. MYSQL_KPNSDB_Create.sql
ii. MYSQL_KPNSDB_View.sql
iii. MYSQL_MASTER_DATA.sql
iv. MYSQL_STORED_FUNCS.sql
v. MYSQL_STORED_PROCS.sql
5.2.2 Oracle
Follow these steps to execute Oracle DB scripts:
1. Create a user / schema with a name "kpnsdb" and provide below grants to "KPNSDB"
schema.
Note: Below grants commands need to be executed with role "sysdba" from SQL*Plus.
GRANT CONNECT,RESOURCE,CREATE VIEW TO KPNSDB;

GRANT CREATE JOB to KPNSDB;
GRANT MANAGE SCHEDULER to KPNSDB;
i. ORACLE_KPNSDB_Create.sql
ii. ORACLE_KPNSDB_View.sql

Version 3.0
iii. ORACLE_MASTER_DATA.sql
iv. ORACLE_STORED_FUNCS.sql
v. ORACLE_STORED_PROC.sql
5.2.3 DB2
Follow these steps to execute DB2 DB scripts:
1. Create a database with a name KPNS.
2. Execute the below script to create tablespace <tablespace-name>

DB2_CREATE-BIG-TABLESPACE.sqlcommand > db2 -td';' -vf DB2_CREATE-
BIG-TABLESPACE.sql > kpns_tbs.log
3. Create the required (kpnsdb) schemas in KPNS database using the below script:
DB2_CREATE_USERS.SQL
command > db2 -td';' -vf DB2_CREATE_USERS.SQL > kpns_create_

users.log
i. DB2_KPNSDB_Create.sql
command > db2 -td';' -vf DB2_KPNSDB_Create.sql > kpnsdb_

create.log
ii. DB2_KPNSDB_View.sql
command > db2 -td';' -vf DB2_KPNSDB_View.sql > kpnsdb_view.log

Version 3.0
iii. DB2_MASTER_DATA.sql
command > db2 -td';' -vf DB2_MASTER_DATA.sql > kpnsdb_master_

data.log
iv. DB2_STORED_FUNCS.sql
command > db2 -td':' -vf DB2_STORED_FUNCS.sql
v. DB2_STORED_PROCS
command > db2 -td':' -vf DB2_STORED_PROCS.sql
5. Update DB2_KPNSDB_JOB_SCHEDULE.sql with the database userid and the password.
6. Use DB2_kpns_job.sh to configure a scheduled job to run at 02:00 AM every day. Refer
DB2_crontab-schedule.txt file for configuring the schedule job.
5.2.4 Microsoft SQL
Follow these steps to execute MS SQL Server DB scripts:
1. Execute the below command to create a database with name as KPNS and schema with name
as KPNSDB.
SQL_Server_CREATE_DB_SCHEMAS.SQL
i. SQL_Server_KPNSDB_Create.sql
ii. SQL_Server_KPNSDB_View.sql
iii. SQL_Server_MASTER_DATA.sql

Version 3.0
iv. SQL_Server_STORED_FUNCS.sql
v. SQL_Server_STORED_PROCS.sql
3. Use SQL_KPNSDB_JOB_SCHEDULE.sql to configure the schedule job that should run at

02:00 AM every day.
5.3 Download Kony MobileFabric Messaging Files
To download Kony MobileFabric Messaging files, follow these steps:
1. To download the files, go to the link: http://community.kony.com/downloads/manual
The Downloads Manual Installers page appears.

Version 3.0
2. Click Kony MobileFabric tab to navigate to Kony MobileFabric section.
3. Based on your requirement, select the version under Kony MobileFabric header.
4. Click the Download button to download the files. The kms-x.x.x.x files are downloaded in a zip
format. Kony provides the following files for Kony MobileFabric Messaging:
l kpns.war file that is deployed on the application server.
l WebSphere 8x file

Version 3.0
l kpns-resources.tar- An extracted kpns-resources.tar archive

contains the following files:
o jboss - This folder contains the datasource and JMS XML configurations.
o schema - This folder contains the XML schema definitions for subscription and
messaging.
o configResource.properties - An XML file containing the configuration

properties.
o kpns-log4j.properties - This file is used to control the application

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

application and for User Management configuration.
l Database scripts - There are folders for the following database scripts for creating and
dropping the schema.
Database Script File Name
MySQL mysql.tar
Oracle oracle.tar
Microsoft SQL sqlserver.tar
DB2 db2.tar
Copy configResource.properties, database.properties and

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

Version 3.0
5.4 Setup Kony MobileFabric Messaging
The Kony MobileFabric Messaging setup consists of configuring the

configResource.properties, kpns-log4j.properties
and database.properties files.
For the Kony MobileFabric Messaging setup, you must copy the files to a location (for example
/home/core/kpns-config) and provide the location of the files to the KPNS in the
kpns.configLocation system property.
5.4.1 ConfigResource.properties
This file contains the configuration properties, the available services (AndroidService, iPhoneService
and so on), and the node identifier to identify the current node among other nodes in the cluster.
The following is an example of a configResource.properties file:
####################################################################
########################
# KMS Configuration Properties
# -----------------------------------
####################################################################
########################
##############################################################
# TrustStore Configuration
##############################################################
# Enable the below properties to configure TrustStore path
# truststore.path=

Version 3.0
# truststore.passphrase=
# truststore.type=
##############################################################
##############################################################
# HTTP Proxy Configuration
##############################################################
# Enable below properties and provide HTTP Proxy details.
# If configured, HTTP Proxy will be used for Android, Blackberry,

Windows Clouds connectivity.
# httpproxy.host=
# httpproxy.port=
# httpproxy.user=
# httpproxy.pwd=
##############################################################
##############################################################
# SOCKS Proxy Configuration
##############################################################
# Enable below properties and provide SOCKS proxy details.
# If configured, SOCKS proxy will be used for Apple Cloud

connectivity.
# socksproxy.host=

Version 3.0
# socksproxy.port=
# socksproxy.user=
# socksproxy.pwd=
##############################################################
##Security####################################################
#One time configurable, default is SHA-256. Allowed values : SHA-

256, BCRYPT
#securekey.encoder=SHA-256
##############################################################
##############################################################
# Apple Cloud Configuration
##############################################################
apple.notification.keystore.type=PKCS12
# Enable below properties for Tomcat, Weblogic and JBoss Servers.
apple.notification.keymanager.algorithm=sunx509
apple.notification.trustmanager.algorithm=sunx509
# Enable below properties for IBM WebSphere Application Server.
# apple.notification.keymanager.algorithm=ibmX509
# apple.notification.trustmanager.algorithm=ibmPKIX
# Configure below properties for Apple Production Cloud Connectivity
apple.notification.server.host=gateway.push.apple.com

Version 3.0
apple.notification.server.port=2195
apple.feedback.server.host=feedback.push.apple.com
apple.feedback.server.port=2196
# Configure below properties for Apple Sandbox Cloud Connectivity
apple.dev.notification.server.host=gateway.sandbox.push.apple.com
apple.dev.notification.server.port=2195
apple.dev.feedback.server.host=feedback.sandbox.push.apple.com
apple.dev.feedback.server.port=2196
##############################################################
##############################################################
# Android Cloud Configuration
##############################################################
# Configure below property for Android C2DM Cloud Connectivity
# Note: Android C2DM support is stopped by Google.
android.notification.server.url=https://android.apis.google.com/c2dm
/send
# Configure below property for Android GCM Cloud Connectivity
android.notification.server.gcm.url=https://android.googleapis.com/g
cm/send
##############################################################
##############################################################

Version 3.0
# Blackberry Cloud Configuration
##############################################################
# Configure below property for Blackberry Cloud Connectivity
blackberry.notification.server.url=https://pushapi.eval.blackberry.c
om/mss/PD_pushRequest
blackberry.acknowledgement.listener.port=8888
# Note: Possible values for black berry quality of service

[CONFIRMED,PREFERCONFIRMED,UNCONFIRMED,NOTSPECIFIED]
blackberry.qualityofservice=UNCONFIRMED
##############################################################
##############################################################
# Windows Cloud Configuration
##############################################################
# Configure below property for Windows Cloud Connectivity
windows8.authentication.url=https://login.live.com/accesstoken.srf
##############################################################
##############################################################
# KMS Push Configuration
##############################################################
varchar.size=4000
# Push Message Job Thread Pool properties

Version 3.0
threadCount.minimum=1
threadCount.maximum=10
thread.ttl=5000
# Push Message Job configuration properties
push.character.encode=UTF-8
push.attempts.maximum=10
fetch.size=1500
batchUpdate.size=500
# Push Message Job interval in 'Seconds'
monitor.schedule=15
# Stale Message job internal in 'Seconds'
job.stalemessages.schedule=18000
# Feedback Job interval in 'Hours'
feedback.execution.hour=24
#http client connection configuration
http.connection.timeout=60000
http.max.connections=30
http.pool.max.threads=20
http.idle.connection.timeout=30000
# Auditing for Subscription. Possible Values [true, false]

Version 3.0
audit.enabled=false
##############################################################
# SMPP Configuration
##############################################################
#Nexmo keep alive job frequency in 'Seconds'
smpp.nexmo.enquiretask.interval = 20
#Clickatell keep alive job frequency in 'Seconds'
smpp.clickatell.enquiretask.interval = 55
#Expiration job frequency in 'Minutes' - one hour
smpp.expirationtask.interval = 60
#Request expiration time in 'Minutes' - one hour
smpp.request.expirationTime = 60
#SMPP Request throttle delay in seconds
smpp.request.throttleDelay = 10
Important: Enable below properties for IBM WebSphere Application Server:

apple.notification.keymanager.algorithm=ibmX509
apple.notification.trustmanager.algorithm=ibmPKIX
Disable the below properties:

apple.notification.keymanager.algorithm=sunx509
apple.notification.trustmanager.algorithm=sunx509

Version 3.0
Note: For Security, one time configurable values are as follows:

Default: SHA – 256
Allowed Values: SHA-256, BCRYPT
5.4.2 kpns-log4j.properties
To control the application logging, you can edit the kpns-log4j.properties file.
The following is an example of the kpns-log4j.properties file:
# Root logger option
log4j.rootLogger=INFO
#LOGGER FOR INDIVIDUAL PACKAGES
log4j.logger.com.kony.kms.commons=INFO, file
log4j.logger.com.kony.kms.eventmessage.handler=INFO, file
log4j.logger.com.kony.kms.feedback.processor=INFO, file
log4j.logger.com.kony.kms.message.builder=INFO, file
log4j.logger.com.kony.kms.message.handler=INFO, file
log4j.logger.com.kony.kms.message.processor=INFO, messages
log4j.logger.com.kony.kms.quartz=INFO, file
log4j.logger.com.kony.kms.service=INFO, file
log4j.logger.com.kony.kms.subscription.handler=INFO, file
log4j.logger.com.kony.kms.utility=INFO, file
log4j.logger.com.kony.kms.validators=INFO, file

Version 3.0
log4j.logger.com.kony.kms.oauth=INFO, file
log4j.logger.com.kony.kms.ui.controller=INFO, file
log4j.logger.com.kony.kms.web.controller=INFO, file
log4j.logger.com.kony.kms.mbaas=INFO, file
log4j.logger.com.kony.kms.web.filters=INFO, file
log4j.logger.com.kony.kms.web.listeners=INFO, file
log4j.logger.com.kony.kms.web.servlets=INFO, file
log4j.logger.com.kony.kms.sms=INFO, file
log4j.logger.com.kony.kms.mail=INFO, file
log4j.logger.com.kony.kms.passkit=INFO, file
log4j.logger.com.kony.api=INFO, file
log4j.logger.com.kony.kms.exception.controller=INFO, file
# Direct log messages to file
log4j.appender.file=org.apache.log4j.RollingFileAppender
log4j.appender.file.maxFileSize=10240KB
log4j.appender.file.maxBackupIndex=10
log4j.appender.file.File=${catalina.base}/logs/kms.log
log4j.appender.file.threshold=DEBUG
log4j.appender.file.layout=org.apache.log4j.PatternLayout

Version 3.0
log4j.appender.file.layout.ConversionPattern=%d{dd MMM yyyy

HH:mm:ss,SSS} %5p %t-%c{2}:%L - %m%n
#Log file for all the messages sent
log4j.appender.messages=org.apache.log4j.RollingFileAppender
log4j.appender.messages.maxFileSize=10240KB
log4j.appender.messages.maxBackupIndex=10
log4j.appender.messages.File=${catalina.base}/logs/kms-messages.log
log4j.appender.messages.threshold=DEBUG
log4j.appender.messages.layout=org.apache.log4j.PatternLayout
log4j.appender.messages.layout.ConversionPattern=%d{dd MMM yyyy

HH:mm:ss,SSS} %5p %t-%c{2}:%L - %m%n
5.4.3 database.properties
Database properties configures database details for KPNS application. Provide respective database
schema names, database driver class, database hibernate dialect and JDBC connection parameters
for quartz. Allowed values are provided in the sample properties file.
####################################################################
########################
# Database Properties
# -------------------------
# database.dialect -- Should point to Hibernate Dialect of

respective database.
# database.defaultSchema -- Provide schema name of the KPNS database

Version 3.0
####################################################################
########################
# MySQL -- org.hibernate.dialect.MySQLDialect
# Oracle -- org.hibernate.dialect.Oracle10gDialect
# DB2 -- org.hibernate.dialect.DB2Dialect
# MS SQLServer -- org.hibernate.dialect.SQLServerDialect
database.dialect=org.hibernate.dialect.MySQLDialect
database.defaultSchema=kpnsdb
#Quartz database delegate
# MYSQL -- org.quartz.impl.jdbcjobstore.StdJDBCDelegate
# Oracle -- org.quartz.impl.jdbcjobstore.StdJDBCDelegate
# DB2 -- org.quartz.impl.jdbcjobstore.StdJDBCDelegate
# SQL Server - org.quartz.impl.jdbcjobstore.MSSQLDelegate
database.quartz.delegateClass=org.quartz.impl.jdbcjobstore.StdJDBCDe
legate
####################################################################
########################
# Cache Configuration
####################################################################
########################
cache.enable=true

Version 3.0
Important: Do not use any other database or schema names apart from the ones provided in the
SQL scripts.
Important: Note that the schema names and the database names are case sensitive in MySQL.
5.4.4 Additional Configuration with Multiple Nodes
1. Create a file with name as pns-ehcache.xml.
2. Place the following content in the above mentioned xml file.
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>
<ehcache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://ehcache.org/ehcache.xsd"
updateCheck="false" dynamicConfig="false">
<diskStore path="java.io.tmpdir/pnsCache"/>

<cacheManagerPeerProviderFactory
class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderF
actory"
properties="peerDiscovery=manual,
rmiUrls=//<node>:40001/pnsCache" />

Version 3.0

<cacheManagerPeerListenerFactory
class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerF
actory"
properties="hostName=localhost, port=40001,
socketTimeoutMillis=120000" />
<defaultCache
maxEntriesLocalHeap="10000"
eternal="false"
timeToIdleSeconds="120"
timeToLiveSeconds="120"
diskSpoolBufferSizeMB="30"
maxEntriesLocalDisk="10000000"
diskExpiryThreadIntervalSeconds="120"
memoryStoreEvictionPolicy="LRU"
statistics="false">
<persistence strategy="distributed"/>
</defaultCache>
<cache name="pnsCache"
maxEntriesLocalHeap="10000"

Version 3.0
maxEntriesLocalDisk="10000000"
diskSpoolBufferSizeMB="20"
timeToIdleSeconds="300"
timeToLiveSeconds="86400"
memoryStoreEvictionPolicy="LRU"
transactionalMode="off">
<cacheEventListenerFactory
class="net.sf.ehcache.distribution.RMICacheReplicatorFactory"
properties="replicateAsynchronously=true, replicatePuts=true,
replicateUpdates=true,
replicateUpdatesViaCopy=false, replicateRemovals=true" />
<bootstrapCacheLoaderFactory
class="net.sf.ehcache.distribution.RMIBootstrapCacheLoaderFacto
ry" />
<persistence strategy="distributed"/>
</cache>
</ehcache>

6. Kony MobileFabric Messaging Kony MobileFabric Messaging Manual Installation
Upgrade Guide - Linux
Version 3.0
6. Kony MobileFabric Messaging Upgrade
The process of upgrading Kony MobileFabric Messaging Database includes understanding system
considerations and requirements and troubleshooting various issues before actually performing the
upgrade steps. Before you upgrade Kony MobileFabric Messaging Database, you must become
familiar with the new features .This section provides the latest upgrade information to help you to
understand requirements and complete upgrade tasks.
6.1 Database Upgrade
Refer section Install and Configure Kony MobileFabric Messaging > Database Setup to setup
database and upgrade database versions
6.1.1 MySQL DB Upgrade
To update Kony MobileFabric Messaging versions, execute below scripts.
6.1.1.1 Steps to Upgrade KPNS from 5.0.5 to 6.5.0
upgrade_from_5.0.5_to_5.5.sql
upgrade_from_5.5.4_to_5.6.0.sql
upgrade_from_6.0_to_6.0.1.sql
upgrade_from_6.0.3_to_6.5.0.beta.sql
upgrade_from_6.5.0.beta_to_6.5.0.sql
6.1.1.2 Steps To Upgrade KPNS from 5.0.6 to 6.5.0

Version 3.0
6.1.1.3 Steps to Upgrade KPNS from 5.5 to 6.5.0

Version 3.0
6.1.1.5 Steps to Upgrade KPNS from Kony 5.6.1 to 6.5.0

Version 3.0
6.1.2 Oracle DB Upgrade
6.1.2.1 Steps to Upgrade KPNS From 5.0.5 to 6.5.0
Below grants commands need to be executed with role "sysdba" from SQL*Plus

Execute below scripts on "kpnsdb" schema.

Version 3.0
6.1.2.2 Steps to Upgrade KPNS From 5.0.6 to 6.5.0
Below grants commands need to be executed with role "sysdba" from SQL*Plus

Execute below scripts on "kpnsdb" schema.

Version 3.0

Version 3.0
6.1.3 DB2 Upgrade
To update KPNS from 5.0.5 to 6.5 execute below scripts.

Version 3.0
6.1.4 Microsoft SQL Upgrade
upgrade_from_5.0.5_to_5.5_i18n.sql

Version 3.0

Version 3.0
pgrade_from_6.5.0.beta_to_6.5.0.sql
6.1.4.10 To Upgrade KPNS from 6.0.3 to 6.5.0

Version 3.0
6.2 Kony MobileFabric Messaging Upgrade
The Kony MobileFabric Messaging Upgrade section shows the location of the KPNS configuration
files that you need to copy from the Kony developer portal. You need to have the required login
information to download files.You must download the kpns.war file, sharedlib.tar, and
the kpns-resource –tar files.
Refer to Install and Configure KPNS > Download KPNS Files section to download Kony
MobileFabric Messaging artifacts.
Refer to Install and Configure KPNS > Setup KPNS section to setup Kony MobileFabric Messaging
application.
To configure Kony MobileFabric Messaging application on following servers, see:
l Configure JBoss Server 5.1
l Configure JBoss Server 6.2
l Configure WebSphere Server
l Configure WebLogic Server

7. Configure Jboss 5.1 Kony MobileFabric Messaging Manual Installation Guide -
Server Linux
Version 3.0
7. Configure Jboss 5.1 Server
This section is applicable if you are using JBoss as the J2EE Web container for the setup. Before you
begin, you must configure the JBoss Server with the configuration that provides Datasource services
or continue with the default configuration provided out of the box.
After you configure the JBoss server, you must perform these operations:
l Configure JBoss Server
l Configure Datasources
l Deploy Kony MobileFabric Messaging
7.1 Configure JBoss Server
You must configure the JBoss Server to provide the memory arguments and the location of the Kony
MobileFabric Messaging configuration files.
To configure the JBoss server, follow these steps:
1. Navigate to <JBoss Install Directory>/bin.
2. Modify run.sh file with the following parameters:
Parameters (for Require Description

JVM) d
-Xmx2048m Yes Minimum Heap size: 2GB
-Xms2048m Yes Maximum Heap size: 2GB

Server Linux
Version 3.0

JVM) d
- Yes One fourth of the main Heap memory assigned

XX:MaxPermSize=51
2m
-XX:UseParallelGC Yes This is a recommended setting
-Dkpns.configLocation Yes This is the directory where the

configResource.properties,
database.properties, and kpns-
log4j.properties files must be placed.
For example, if the location is /data/kpns-
config, then you must specify the property as -
Dkpns.configLocation=/data/kp
ns-config
-Dhibernate.dialect Enables Oracle= org.hibernate.dialect.

you to Oracle10gDialect
connect
to the
databas
e. JDBC
has to be
configure
d on the
AppServ
er level.
3. -Xms2048m –Xmx2048m -Dkpns.configLocation=/data/kpns-config
4. Save the configuration.

Server Linux
Version 3.0
5. Remove the default quart and mail lib from the following path (quartz.jar,
mail.jar).
<JBoss Install Directory>/common/lib
7.2 Configure Datasource
To configure the datasource, follow these steps:
1. Navigate to the location where you have extracted the kpns-resources.tar file.
2. From the jboss folder, copy <name>-ds.xmlfile to <JBoss Install

Directory>/server/<configuration>/deploy/. If required you can rename
this file.
3. Modify the attributes of <name>-ds.xmlfile with the values which are appropriate as per
your database configuration.
For Oracle, DB2, and MySQL, the <name>-ds.xmlfile has the following attributes:
Attribute Required Description
ndi-name Yes Specifies the JNDI name (schema name) under, which
the Datasource should be bound
connection-url Yes Specifies the JDBC driver connection url string
driver-class Yes Specifies the JDBC driver class implementing

java.sql.Driver
DatabaseName Yes Specifies the name of the database

Server Linux
Version 3.0
user-name Yes Specifies the username used when establishing the

connection
password Yes Specifies the password used when establishing the

connection
type-mapping Yes This element defines a default type mapping for a data
source
For Microsoft SQL Server, the <<name>>-ds.xml file has the following attributes:
ndi-name Yes Specifies the JNDI name (schema name) under which
the Datasource should be bound
connection-url Yes Specifies the JDBC driver connection URL string
driver-class Yes Specifies the JDBC driver class implementing

java.sql.Driver
DatabaseName Yes Specifies the name of the database.
user-name Yes Specifies the username used when establishing the

connection
password Yes Specifies the password used when establishing the

connection
type-mapping Yes This element defines a default type mapping for a data
source.

Server Linux
Version 3.0
Example Snippets:
Important: The configurations and examples in this document are provided for a better
understanding of the concepts. We encourage you not to copy-paste them for your
installation execution as they may not match your settings. For example, user names,
passwords, IP addresses, and port numbers.
<datasources>
<local-tx-datasource>
<jndi-name>kpnsdb</jndi-name>
<use-java-context>false</use-java-context>

<connection-url>jdbc:sqlserver://<ipaddress>;
DatabaseName=KPNSDB</connection-url>


<driver-
class>com.microsoft.sqlserver.jdbc.SQLServerDriver
</driver-class>

<user-name>dbclient</user-name>
<password>kony@123</password>

<pool>
<min-pool-size>5</min-pool-size>
<max-pool-size>50</max-pool-size>
</pool>

Server Linux
Version 3.0
<idle-timeout-minutes>20</idle-timeout-minutes>
<statement>
<track-statements>false</track-statements>
</statement>
<metadata>
<type-mapping>mySQL</type-mapping>

</metadata>
</local-tx-datasource>
</datasources>
To enable the push configure maintain <<name>>-ds.xmlfile.
Note: Database schema name should be in capital letters like KPNSDB.
Note: The Database driver must be placed in the JBoss Server lib directory.
Note: For Jboss with Oralce database, use ojdbc14.jar as db driver
5. Remove the default quartz.jar located in the following path
<jboss_intstall_dir>\common\lib
7.3 Deploy KPNS
1. To deploy KPNS on the JBoss Server, copy kpns.war file to the following location:
<JBoss Install Directory>/server/<configuration>/deploy/
2. After you deploy KPNS, complete the KPNS setup and start the JBoss Server.

Server Linux
Version 3.0
8. Configure Jboss 6.2 Server
This section is applicable if you use JBoss as the J2EE Web container for the setup. Before you begin,
you must configure the JBoss server with the configuration that provides Datasource services or
continue with the default configuration provided out of the box.
After you configure the JBoss server, you must perform these operations:
l Configure JBoss Server
l Configure Datasources
8.1 Configure JBoss Server
You must configure the JBoss Server to provide the memory arguments and the location of the Kony
MobileFabric Messaging configuration files.
To configure the JBoss server, follow these steps:
1. Navigate to <JBoss Install Directory>/bin.
2. Modify run.sh file with the following parameters:

JVM) d

Server Linux
Version 3.0

JVM) d

XX:MaxPermSize=51
2m

ns-config

connect
to the
databas
e. JDBC
has to be
configure
d on the
AppServ
er level.
3. -Xms2048m –Xmx2048m -Dkpns.configLocation=/data/kpns-config

Server Linux
Version 3.0
You can configure dabases for the following databases:
l MySQL
l Microsoft SQL
l Oracle
l DB2
To configure the datasource, follow these steps:
8.2.1 MySQL
1. Create a new module for MySQL driver.
i. Create a folder hierarchy with path $JBOSS_HOME/modules
$JBOSS_HOME/modules/com/mysql/main
ii. Copy mysql-connector-java-5.1.26-bin.jar to $JBOSS_

HOME/modules/com/mysql/main
iii. Create module.xml file.
iv. Add the following content.
<module xmlns="urn:jboss:module:1.1" name="com.mysql">
<properties>
<property name="jboss.api" value="unsupported"/>
</properties>

Server Linux
Version 3.0
<resources>
<resource-root path="mysql-connector-java-5.1.26-bin.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.transaction.api"/>
<module name="javax.servlet.api" optional="true"/>
</dependencies>
</module>
2. Configure data source in $JBOSS_

HOME/standalone/configuration/standalone.xml
i. Add the following configuration with in <datasources>
<datasource jndi-name="java:/jdbc/kpnsdb" pool-

name="kpnsds" enabled="true" use-java-context="true">
<connection-url>kpns db connection url</connection-url>
<driver>mysql</driver>
<security>
<user-name>kpns db username</user-name>
<password>kpns db password</password>
</security>

Server Linux
Version 3.0
<new-connection-sql>SELECT 1</new-connection-sql>
<validation>
<validate-on-match>true</validate-on-match>
<check-valid-connection-sql>SELECT 1</check-valid-
connection-sql>
</validation>
</datasource>
ii. Add driver with in <drivers>
<driver name="mysql" module="com.mysql"/>
3. Disable default JPA in jboss 6.2 $JBOSS_

i. Remove the following tag:
<subsystem xmlns="urn:jboss:domain:jpa:1.1">
<jpa default-datasource="" default-extended-persistence-

inheritance="DEEP"/>
</subsystem>

Server Linux
Version 3.0
8.2.2 Microsoft SQL
1. Create a new module for microsoft driver.
ii. $JBOSS_HOME/modules/com/microsoft/main
iii. Copy sqljdbc4.jar to $JBOSS_HOME/modules/com/microsoft/main
iv. Create module.xmlfile.
v. Add the following content:
<module xmlns="urn:jboss:module:1.1" name="com.microsoft">
<properties>
</properties>
<resources>
<resource-root path="sqljdbc4.jar"/>
</resources>
<dependencies>
</dependencies>

Server Linux
Version 3.0
</module>

HOME/standalone/configuration/standalone.xml.

<driver>microsoft</driver>
<security>
</security>
<new-connection-sql>SELECT 1</new-connection-sql>
<validation>
<check-valid-connection-sql>SELECT 1</check-valid-
connection-sql>
</validation>
</datasource>

Server Linux
Version 3.0
<driver name="microsoft" module="com.microsoft"/>

i. Remove the following tag:

</subsystem>
8.2.3 Oracle
1. Create a new module for oracle driver.
i. Create a folder hierarchy with path $JBOSS_HOME/modules.
ii. $JBOSS_HOME/modules/com/oracle/main
iii. Copy ojdbc6_g.jar to $JBOSS_HOME/modules/com/oracle/main
iv. Create module.xml file.
<module xmlns="urn:jboss:module:1.1" name="com.oracle">
<properties>

Server Linux
Version 3.0
</properties>
<resources>
<resource-root path="ojdbc6_g.jar"/>
</resources>
<dependencies>
</dependencies>
</module>


<driver>oracle</driver>
<security>

Server Linux
Version 3.0
</security>
<new-connection-sql>select 1 from dual</new-connection-sql>
<validation>
<check-valid-connection-sql>select 1 from dual</check-

valid-connection-sql>
</validation>
</datasource>
<driver name="oracle" module="com.oracle"/>

4. Remove the following tag:

</subsystem>

Server Linux
Version 3.0
8.2.4 DB2
1. Create a new module for db2 driver.
ii. $JBOSS_HOME/modules/com/db2/main
iii. Copy db2jcc4.jar to $JBOSS_HOME/modules/com/db2/main
iv. Create module.xml file.
<module xmlns="urn:jboss:module:1.1" name="com.db2">
<properties>
</properties>
<resources>
<resource-root path="db2jcc4.jar"/>
</resources>
<dependencies>
</dependencies>

Server Linux
Version 3.0
</module>


<driver>db2</driver>
<security>
</security>
<new-connection-sql>select 1 from sysibm.sysdummy1</new-

connection-sql>
<validation>
<check-valid-connection-sql>select 1 from
sysibm.sysdummy1</check-valid-connection-sql>
</validation>
</datasource>

Server Linux
Version 3.0
<driver name="db2" module="com.db2"/>
iii. Disable default JPA in jboss 6.2 $JBOSS_

iv. Remove the following tag:

</subsystem>
8.3 Deploy Kony MobileFabric Messaging
1. To deploy Kony MobileFabric Messaging on the JBoss Server, copy kpns.war file to the
following location:
<JBoss Install Directory>/standalone/deployments/
2. After you deploy Kony MobileFabric Messaging, complete the Kony MobileFabric Messaging
setup and start the JBoss server.

9. Configure WebSphere Kony MobileFabric Messaging Manual Installation Guide -
Server Linux
Version 3.0
9. Configure WebSphere Server
This section is applicable if you use WebSphere as the J2EE Web container for the setup.
After making the necessary modifications to Kony MobileFabric Messaging files, configure
Websphere. Perform the following tasks using Websphere Administration Console. You need to log in
to the Administration Console to perform these operations
l Configure the Application Server
l Configure Database
l Configure Shared Libraries for WebSphere 8 and 8.5 versions
l Configure WebSphere Network Deployment (7.0 and 8.5) - Multi-node
9.1 Configure the Application Server
You need to log in to the Websphere Administration Console to perform these operations.
To configure the server, follow these steps:
1. Log in to Websphere Administration Console.
2. Select Servers > Application Servers from the left menu.
3. Click Server1 link and select the Configuration tab.
4. Navigate to Server Infrastructure section and click Java and Process Management >
Process Definition.
5. On Additional Properties, click Java Virtual Machine.
6. Select the Configuration tab.

Server Linux
Version 3.0
7. In the Generic JVM arguments field, enter the system properties as mentioned below:
Parameters Required Description
-Xms2048m Yes Minimum heap size: 2GB
-Xms2048m Yes Maximum heap size: 2GB
-XX:UseParallelGC No Recommended setting
- Yes This is the directory where the

Dkpns.configLocatio ConfigResource.properties,
n database.properties and
kpnslog4j.properties files must be
placed.

config, then you must specify the property as
-
Dkpns.configLocation=/data/kpn
s-config
-Dhibernate.dialect Enable
hibernate
dialet Oracle= org.hibernate.dialect.Oracle10gDialect
configuratio
n for Oracle
database.
Sample arguments for a server would look like:
-Xms2048m -Xmx2048m -Dkpns.configLocation=/data/kpns-config.
8. Click OK and save the configuration.

Server Linux
Version 3.0
9.2 Configure Database
9.2.1 Setup MySQL database driver
Ignore this section if the database driver is already configured. The assumption is that you use MySQL
database.
To setup MySQL database driver, follow these steps:
1. In the Administration Console, select Resources > JDBC > JDBC Provider from the left
menu.
2. On the right pane, click New, to navigate to configure new JDBC provider.
3. Select the following information:
a. Database type: User-defined.
b. Implementation class name:
com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource
c. Name: Enter a name for the resource, for example MySQL_JDBC_Provider.
4. Click Next.
5. Provide the classpath for the driver library. For example, enter the value${WAS_INSTALL_
ROOT}/lib if the MySQL connector jar is placed here.
6. Copy mysql-connector-java-5.1.26-bin.jar to the aforesaid path.
7. Click Finish and Save the configuration.

Server Linux
Version 3.0
9.2.2 Setup Oracle database driver
Ignore this section if the database driver is already configured. The assumption is that you use an
Oracle database.
To setup Oracle database driver, follow these steps:
1. In the Administration Console, select Resources> JDBC>JDBC Provider from the left menu.
a. Database type: Oracle.
b. Provider type = Oracle JDBC Driver
c. Implementation type: Connection pool data source
4. Click Next.
5. Provide the absolute path to the JDBC driver library. For example, enter the value${ORACLE_
JDBC_DRIVER_PATH} if the ojdbc6.jar is placed here.
6. Click Next and verify the Summary.
9.2.3 Setup DB2 database driver
Ignore this section if the database driver is already configured. The assumption is that you use a DB2
database.
To setup a DB2 driver, follow these steps:

Server Linux
Version 3.0
1. In the Administration Console, select Resources > JDBC > JDBC Providers from the left
menu.
2. On the right pane, select the scope as cell.
3. Click New, to navigate to configure the new JDBC provider.
a. Database Type: DB2
b. Provider Type: DB2 Using IBM JCC Driver
c. Implementation Type: Connection pool data source
d. The Name field is populated as DB2 Using IBM JCC Driver(Optional) by default.
5. Click Next.
6. In the Directory location for "db2jcc4.jar, db2jcc_license_cisuz.jar"

that is saved as WebSphere variable ${DB2UNIVERSAL_JDBC_DRIVER_PATH}
field, provide the path where the DB2 driver files are located.For example, /opt/db2jars.
Note: Ensure that the following DB2 driver files db2jcc4.jar, db2jcc_license_
cisuz.jar and db2jcc_license_cu.jar are downloaded and copied to the file
system - /opt/db2jars.
7. Click Next.
8. Verify the implementation class name and click Finish.
9.2.4 Setup Microsoft SQL database driver
Ignore this section if the database driver is already configured. The assumption is that you use a
Microsoft SQL database.
To setup Microsoft SQL database driver, follow these steps:

Server Linux
Version 3.0
1. In the Administration Console, select Resources > JDBC > JDBC Provider from the left
menu.
a. Database type: SQL Server
b. Provider Type: Microsoft SQL Server JDBC Driver
c. Implementation type: Connection pool data source
4. Click Next.
5. Provide the absolute path to the JDBC driver library. For example, enter the
value${MICROSOFT_JDBC_DRIVER_PATH} and ${MICROSOFT_JDBC_DRIVER_
NATIVEPATH}.
6. Click Next and verify the Summary.
9.2.5 Configure Datasource for MySQL
Execute the following steps to configure Datasource.
To configure the J2C Authentication entry, follow these steps:
1. In the Administration Console, select Security > Global Security from the left menu.
2. In the right side pane, under Authentication, click Java Authentication and Authorization
Service > J2C authentication data.

Server Linux
Version 3.0
3. Click New and enter the following properties:
a. Alias: Enter Alias. This is an alias name for the authentication entry, for example
MySQLAdmin.
b. User ID: Enter the username to connect to the database.
c. Password: Enter the password for the entered username.
4. Click Apply and Save the configuration.
To create a Datasource, follow these steps:
1. In the Administration Console, select Resources > JDBC > Data sources from the left menu.
2. In the right side pane, click New to create a new datasource.
3. In the Step-1 of Create a datasource wizard, enter the following:
a. Data source name: Enter the datasource name, for example kpnsdb.
b. JNDI Name: jdbc/kpnsdb (For push notifications)
4. Click Next.
5. In Step-2 of the wizard, choose Select an existing JDBC provider and select the driver
created using a Setup MySQL database driver, from the drop-down.
6. Click Next.
7. Click Next with default configurations in Step-3 of the wizard.
8. In Step-4, Setup security aliases, select the J2C Authentication entry created above.
To complete the configuration of the created datasource, follow these steps:

Server Linux
Version 3.0
2. Select the datasource just created (kpnsdb).
3. Select Additional Properties > Custom properties.
4. Edit the following properties and set the appropriate values:
a. serverName: Provide the hostname or IP address of the database host.
b. port: Enter the port number to be used to connect to the database.
c. databaseName: Enter the name of the database to be used.
Name Custom Properties
databaseName KPNSDB
port User-defined. For MySQL the port number is 3306
serverName URL of the MySQL Server
9.2.6 Configure Datasource for Oracle

Server Linux
Version 3.0
a. Alias: Some alias name for the authentication entry, for example client1
credentials.
In the page that appears, click New. Enter the following information:
l Create Data source name as: kpnsdb
l JNDI Name: jdbc/kpnsdb (For push notifications)
l Click Next.
2. In the page that appears:
l Choose Select an existing JDBC provider and select an Oracle driver from the drop-
down.
l Click Next.
l Enter the following information:

o url: jdbc:oracle:thin:@[ip address]:[Oracle port
(1521)]:[Oracle database name (orcl)]
o Data store helper class name: Oracle 10g data store helper.
o Proceed to the next page.

Server Linux
Version 3.0
o In the page that appears, for the fields Component-managed authentication alias
and Container-managed authentication alias, select kpnsdbAuth. Here
kpnsdbAuth will be pre-appended with node name.
o Click Next and click Finish.
o Save the configuration.
l In the Data source page, click kpnsdb.
l Select Connection Pool properties and change the values:

o 30 for maximum connections
o 10 for minimum connections
l Click OK and save the configuration. You are directed to the Data source page.
l Select kpnsdb and click Test Connection to ensure data source setup is correct.
l Click Save to save configurations.
9.2.7 Configure Datasource for Microsoft SQL
a. Alias: Some alias name for the authentication entry, for example client1
credentials.

Server Linux
Version 3.0
To create a Datasource, follow these steps
In the page that appears, click New. Enter the following information:
l Data source name: kpnsdb
l JNDI Name: jdbc/kpnsdb(For push notifications).
l Click Next.
l Choose Select an existing JDBC provider and select a Microsoft SQL Server JDBC
Driver for Microsoft SQL from the drop-down menu.
l Click Next.
3. In the page that appears,enter the following information:
l Database Name: kpnsdb
l Server Name: <Name of the server>
l Port Number: 1433
l Click Next.
l In the Security Aliases page, select the Global J2C authentication alias. A new window
for J2C authentication window appears.

Server Linux
Version 3.0
o Component-managed authentication alias: User-defined
o Container-managed authentication alias: User-defined
o Click Next and Finish.
l Click the name of the created datasource in the main pane.
l In the left pane, navigate to Connection pool properties, select Connection Pool
properties and change the values:
o 30 for maximum connections.
o 10 for minimum connections.
l Select the Microsoft SQL data source and go to >Custom Properties >New ,then enter
name as sendStringParametersAsUnicode and value as true.
9.2.8 Configure Datasource for DB2
i. Alias: Some alias name for the authentication entry, for example client1 credentials.
ii. User ID: Enter the username to connect to the database.
iii. Password: Enter the password for the entered username.

Server Linux
Version 3.0
2. In the page that appears, click New. Enter the following information:
Data Description
Data source name kpnsdb
JNDI Name jdbc/kpnsdb(For push notifications).
3. Click Next.
4. In the page that appears,select an existing JDBC provider and select a DB2 Using IBM JCC
Driver from the drop-down menu.
5. Click Next..
6. In the page that appears,enter the following information:
Data Description
Driver type 4
Database Name <DB2 databasename>
Server Name <Server hostname/ip>
Port number <port>
7. Click Next.
8. In the Security Aliases page, select the Global J2C authentication alias. A new window for J2C
authentication window appears.

Server Linux
Version 3.0
l Component-managed authentication alias: User-defined
l Container-managed authentication alias: User-defined
9. Click Next and finish.
10. Click the name of the created datasource in the main pane.
l 30 for maximum connections.
l 10 for minimum connections.
11. Select the DB2 data source and go to Custom Properties >New.
12. Create following two properties if they do not exist:
l currentSchema
l progressiveStreaming
13. Set currentSchema value as KPNSDB (case sensitive)
14. Set progressiveStreaming value as 2.
9.3 Configure Shared Libraries for WebSphere 8 and 8.5
These steps are mandatory to configure shared libraries for WebSphere 8 and 8.5 versions.
1. Extract all libraries from sharedlib.tar to your local system.
2. Create a directory path in the server with the name sharedlib/lib. For example,
/home/core/install/kpns_sharedlib
3. Copy the JAR files from the Step 1 to /home/core/install/kpns_sharedlib

location.
4. Login to the IBM console and stop and un-install kpns.war if already exists.

Server Linux
Version 3.0
5. Login to the Websphere Admin Console.
a. Click Environment in the left pane to view sections. Click Shared libraries. Shared
Libraries section appears in the right pane.
b. Based on your environment, choose the specific scope or Node under Shared libraries
section.
c. Click the New button.
6. A shared Libraries page appears. Enter the following details:
a. Name: kpns-shared-lib
b. Description: isolated jar files are from kpns.war file
c. Classpath: /home/core/install/kpns_sharedlib
7. Select the Use an isolated class loader for this shared library check box.
8. Click Ok and save the changes.
9. Click Save to apply the changes to the master configuration.
To deploy Kony MobileFabric Messaging, follow these steps:
1. In the Administration Console, navigate to Applications > Install New

Application.
2. From the right side, select the kpns.war to install.
3. Click Next. The Install New Application wizard appears
4. Click Next and finish the deployment.
5. Save the configuration and start the application.

Server Linux
Version 3.0
6. Click on kpns link in Applications. KPNS Application Configuration page appears.
7. Click the Shared library reference link under References, and select the KPNS Application
Configuration page.
8. On Shared library references page, check kpns.war/ WEB-INF/web.xml.
9. Click the Reference Shared Libraries button.
10. Select the added shared library from the Available list box and use the single arrow icon to move
it to Selected list box.
11. Click OK to save the changes.The Reference Shared Libraries list view appears.
12. Click OK.
14. Restart the server.
9.4.1 Post Installation Validation
1. For post installation validation, do the following:
i. Check the SystemOut.log file for the successful kpns validation message. If the log
displays FATAL ERRORS, verify the setup.
ii. Check the kpns.log file. It should show a successful license validation message.
iii. Open the browser and enter– http://<ipaddress> or <hostname>:<port>/kpns. It should

display log in page with a username as admin and a password as admin.

Server Linux
Version 3.0
9.4.2 Websphere Unrestricted JCE Policy JAR Files for iPhone Push
Notifications and Nexmo SMS gateway configuration
While sending a push message for iPhone, if it results with a push failure, you see the following
exception.
"java.io.IOException: Error in loading the keystore: Private

key decryption
error: (java.security.InvalidKeyException: Illegal key size)"
Or while sending SMS with Nexmo provider, if it results with a SMS failure, you see the
following exception.
IO Exception occurred
javax.net.ssl.SSLPeerUnverifiedException: peer not

authenticated
at com.ibm.jsse2.SSLSessionImpl.getPeerCertificates
(SSLSessionImpl.java:79)
at org.apache.http.conn.ssl.AbstractVerifier.verify
(AbstractVerifier.java:126)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket
(SSLSocketFactory.java:572)
at
org.apache.http.impl.conn.DefaultClientConnectionOperator.openC
onnection

Server Linux
Version 3.0
To fix this exception, you need to use the unrestricted policy files: local_policy.jar,
US_export_policy.jar by replacing the existing jar files in %WAS_
HOME%\java\jre\lib\security location, and then restart your Websphere.
Note: The unrestricted policy files provided here will work with all IBM Java SDKs version
1.4.2 and higher.
You can download the unrestricted.zip file with your IBM login credentials:
https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=jcesdk
Contact Kony technical support for any technical questions.
9.4.3 Troubleshoot GCM Connectivity Issues
KPNS connects to GCM server using HTTPS connectivity. During this connection, KPNS
downloads required certificates into "cacerts" file.
However, if KPNS fails to download the required certificates from GCM cloud, you will not able
to send Push notifications. You may encounter below exception in kpns.log file.
22:12:04,155 ERROR MessagingThread - Push Id:

7507098635507597314 type:
AndroidGCMPushService-MessageExecutor:31 - The push task failed
to execute.
java.lang.NullPointerException
at com.kony.pns.commons.HttpConnectionManager.executeRequest
(HttpConnectionManager.java:109)
at
com.kony.pns.service.message.processor.AndroidGCMPushService.pu
sh(AndroidGCMPushService.java:99)
at

Server Linux
Version 3.0
com.kony.pns.service.message.processor.MessageProcessorChain.pr
ocess(MessageProcessorChain.java:61)
at com.kony.pns.beans.monitor.MessageExecutor$MessageTask.run
(MessageExecutor.java:463)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask
(ThreadPoolExecutor.java:908)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:931)
at java.lang.Thread.run(Thread.java:773)
To resolve this error, follow the command to import GCM certificate manually to cacerts
file:
$ openssl s_client -connect android.googleapis.com:443 | sed -

ne '/-BEGIN CERTIFICATE-/,
/-END CERTIFICATE-/p'
depth=3 /C=US/O=Equifax/OU=Equifax Secure Certificate Authority
verify return:1
depth=2 /C=US/O=GeoTrust Inc./CN=GeoTrust Global CA
verify return:1
depth=1 /C=US/O=Google Inc/CN=Google Internet Authority G2
verify return:1
depth=0 /C=US/ST=California/L=Mountain View/O=Google
Inc/CN=*.googleapis.com
verify return:1
Copy the certificate starting from "-----BEGIN CERTIFICATE-----" to -----END CERTIFICATE-

---- without giving any additional spaces and save in to a file called gcmcert.crt
Now import the cert in to cacerts as shown in the below example commands.

Server Linux
Version 3.0
[root@plqa1was-1 tmp]#
/data/bharath/IBM/WebSphere/AppServer/java/bin/keytool -import
-alias
"gcmcert" -keystore
/data/bharath/IBM/WebSphere/AppServer/java/jre/lib/security/cac
erts -file
/tmp/gcmcert.crt
Enter keystore password:
Owner: CN=*.googleapis.com, O=Google Inc, L=Mountain View,
ST=California, C=US
Issuer: CN=Google Internet Authority G2, O=Google Inc, C=US
Serial number: 66a0f2f133449076
Valid from: 10/23/13 8:49 PM until: 10/23/14 5:30 AM
Certificate fingerprints:
MD5: 88:6E:93:FB:BE:43:B7:75:6E:ED:7B:ED:DF:A3:44:E9
SHA1:
2E:36:85:62:B7:A6:0B:97:D2:65:6A:70:B6:0E:FB:20:B0:9A:87:85
Trust this certificate? [no]: yes
Certificate was added to keystore
Restart Websphere and retry to send push notifications.
9.5 Configure WebSphere Network Deployment (7.0 and 8.5) - Multi-

node
Configure WebSphere ND, before you proceed with the necessary modifications to Kony Server files.
Perform the following tasks using WebSphere Administration Console. You need to log in to the
Administration Console to perform these operations.
l Configure Cluster in WebSphere Application Server
l Deploy kpns.war
l Start or stop the cluster

Server Linux
Version 3.0
9.5.1 Configure Cluster in WebSphere Application Server
Configuring Vertical Cluster
You can enable multiple appservers on a single machine to increase the capacity of your
installation.
Vertical clustering is only supported within the WebSphere Application Server environment. The
following parameters must be met:
l The names of all the other WebSphere Application Server app server and virtual host
components must be unique. The WebSphere Application Server appserver and virtual
host components are installed in the same cell on the same node.
l Must configure app servers with separate ports.
l You can create app server nodes by running the Profile Management tool (pmt.sh)
Federating app server nodes to the Network Deployment Manager
1. Log in to the remote server with SSH and navigate to profiles/AppServer01/bin

directory.
2. To add to the DMGR cluster, ensure that you execute ./addNode.sh script as shown below:
Syntax:
./addNode.sh deployment_manager_host deployment_manager_SOAP_port

-username <userID_for_authentication> -password <password_for_
authentication> -localusername <localuserID_for_authentication> -
localpassword <localpassword_for_authentication>
For example:
#./addNode.sh dmgrmachine1 8879 -username wasadm -password kony123

Server Linux
Version 3.0
Note: Before you run the above command to federate, ensure that the node is up.
3. Restart Node Agent with the below command by navigating to

../profiles/AppServer01/bin location
Note: Avoid starting node agent if the new profile node and DMGRare on the same physical
box and there is already an attached profile running along with node agent.
If during the fresh installation only DMGR is installed, then Restart the node is mandatory
for each profile node.
# ./startNode.sh
4. Restart DMGR to view the newly added servers in the DMGR profile.
Configuring Horizontal Cluster
Horizontal clusters are meant for multiple app server nodes, which are deployed on remote machines
to increase the capacity of your system installation, and also to achieve high availability.
Once you create profiles on remote machines by using profile management tool, go to the each
AppServer bin directory and run the below command as shown example:
Ensure that you are using hostnames instead of IP address of the DMGR node. If the hostnames are
not available, you can edit /etc/hosts file until the node federation is completed.
You need to repeat the above steps for each app server node to federate to DMGR.
To create a cluster, follow these steps:

Server Linux
Version 3.0
1. Create a cluster definition.
a. Log in to WebSphere Administration Console.
b. Select the Servers from the left menu and then select the Clusters.
c. Select the WebSphere application server clusters. The WebSphere application server
clusters screen appears in the right pane.
2. Create cluster members.
a. Click the New button from the right pane. The Create a new cluster screen appears.
b. Enter cluster name as KonyCluster.
c. Click Next. The Create first cluster member screen appears.
Note: During this process:

You can use the Previous button to navigate to previous screens, if you wish to make
any changes.
Click the Cancel button if you wish to ignore the process.
d. Enter the details about the cluster members in the Member name field as cl_
appsevrer1.
e. Define the node on which the cluster member resides from the Select Node drop-down
list.
f. Define whether the server to be generated is based on a server template by selecting the
Generate unique HTTP ports check box.
g. Click the Next button. The Create additional cluster members screen appears.

Server Linux
Version 3.0
3. Follow below steps to create an additional cluster members to the cluster.
a. Enter the cluster member name in the Member name field as cl_appsevrer2, cl_
appsevrer3 and so on
b. Click the Add Member button. The newly created member is added to the grid.
c. Define the node on which the cluster member resides from the Select Node drop-down
list.
d. Click the Next button. The Summary screen appears.
e. Click the Finish button. The system displays the WebSphere application server
clusters screen including newly created clusters.
Note: Once the cluster is created successfully, the cluster is in unavailable (stopped) state
by default. You can change the status to Started if required.
4. Start the node agent.
a. Go to the System administration > Node agents from left panel.
b. Check the Status from the right panel.
c. If the node agent is not started, execute the below script to start the same.
WAS_HOME/profiles/YOUR_PROFILE_NAME/bin/startNode.sh
5. Start the cluster.
a. From the left panel, select the Servers > Clusters > WebSphere application server
clusters. The WebSphere application server clusters screen appears in the right pane.
b. Select the appropriate cluster check box.
c. Click the Start button. The system changes the status of the cluster as Started.

Server Linux
Version 3.0
9.5.2 Deploy Kpns.war
To deploy kpns.war, follow these steps:
1. In WebSphere Administration Console, go to Application > New Application.
2. In the New Application page that appears, click the NewEnterprise Applications.
Path to the new application pane appears.
3. Select Local file system and browse for kpns.war file. Click Next.
We assume that the kpns.war file is located on the local file system.
4. In the How do you want to install the application? pane that appears, select the Fast Path and
click the Next.
5. Once you reach the Map modules to the servers page, under the Clusters and servers, select
WebSphere:Cell=localhostCell01,cluster=KonyCluster,then select the check box for Push
Notification Server, and then click the Apply button.
6. Click Next until you proceed to the Summary page.
7. Verify the information and click the Finish.
8. Click Save to save the configuration to the master configuration.
9. Click on kpns link in Applications. The KPNS Application Configuration page appears.
10. Click the Shared library reference link under References, and select the KPNS Application
Configuration page.
11. On Shared library references page, check kpns.war/ WEB-INF/web.xml.
12. Click the Reference Shared Libraries button.

Server Linux
Version 3.0
13. Select the added shared library from the Available list box and use the single arrow icon to
move.it to the selected list box.
14. Click OK to save the changes.The Reference Shared Libraries list view appears.
15. Click OK.
18. If you notice any synchronization errors, log in to the machines with SSH, navigate to each app
server node bin directory and run following commands to make force deployment and
configuration synchronization between node and cell.
Note: Before running syncNode.sh, ensure that the node agent must be stopped.
# ./stopNode.sh
# ./syncNode.sh dmgrmachine1 8879 -username wasadm -password
kony123
9.5.3 Start or stop the cluster
1. From the left panel, select the Servers > Clusters > WebSphere application server clusters.
The WebSphere application server clusters screen appears in the right pane.
2. If the cluster already started, you can stop and start the cluster to apply the new configuration.
Click the Start button. The system changes the status of the cluster as Started.

10. Configure WebLogic Kony MobileFabric Messaging Manual Installation Guide -
Server Linux
Version 3.0
10. Configure WebLogic Server
This section is applicable if you are using WebLogic as the J2EE Web container for the setup. After
making necessary modifications to Kony MobileFabric Messaging files, you must configure WebLogic
server. Perform the following tasks using WebLogic Administration Console. You need to log in to the
l Create New Domain
l Create Cluster
l Configure Application Server
l Configure Datasource
l Start the Cluster
l Deploy Application Web Archive File
10.1 Create New Domain
To create a new domain, follow these steps:
1. Start the Configuration wizard. You can start the configuration wizard by executing
config.sh under WL_HOME/common/bin.
2. Choose Create a new WebLogic domain option and click Next.
3. In the Select Domain Source window, choose the default option and click Next.
4. Specify the domain name as KonyPushNotification, and click Next.
5. Configure the Administrator Username as weblogic and Password as a required value.
6. Click Next.
7. Configure the Server startup mode as development or production.

Server Linux
Version 3.0
8. Under JDK Selection pane, select JDK and click Next.
9. By default, Administration server is created on port number 7001. If you want to modify the port
number, perform these steps. If you do not want to make any changes, skip to step 9.
i. Check Administration Server in the option and click Next.
ii. Enter a port (for example,7110) that is not in use in the Listen port field.
10. Click Next.
11. Click Create.
10.2 Create Cluster
A WebLogic Server cluster consists of multiple WebLogic server instances running simultaneously
and working together to provide increased scalability and reliability. A Cluster configuration is setup on
one of the physical servers on which you want to configure the cluster. The Administration server will
be running on this machine only as shown below:
Note: Each server instance in a cluster must run the same version of WebLogic Server.

Server Linux
Version 3.0
10.2.1 Step 1: Create a Cluster
1. In the left pane of the Administration Console, expand Environment and select Clusters.
2. Click New, and select the New.
3. On the Create a New Cluster > Cluster Properties page, enter following details:
i. Name: Enter the name of the cluster as KPNCluster.
ii. Messaging Mode: Select Unicast (default).
iii. Click OK.
10.2.2 Step 2: Create Managed Servers
On a physical server, to setup the Administration server and the Cluster, start the Administration
server and open the Administration Console. On this server create the planned number of managed
servers. For instance, for a Cluster architecture cited in the above figure, you need nine managed
servers. So, you need to create nine managed servers as described in the steps given below:
To create a Managed Server in an existing domain, follow these steps:
1. In the left pane of the Administration Console, select Environment > Servers.
2. In the Servers table, click New.
3. On the Create a New Server > Server Properties page:
i. Name: Enter the name of the server as KPNSrv1.
ii. Server Listen Address: Suppose the physical machine has multiple IP addresses, and
you want to restrict the machine to listen particular IP address, then provide the particular
IP address or DNS name here. If you do not enter any value, then by default WebLogic
configures the server to listen on all the addresses. Considering the example in the figure
above, you need to create three managed servers listening to the address of machine

Server Linux
Version 3.0
one, three listening on the address of machine two and three listening on the address of
Machine three. All the nine managed servers are created on the physical machine on
which the cluster is configured.
iii. Server Listen Port: Enter the port number that is not in use, for instance 8001, from
which you want to access the server instance.
iv. Under Should this server belong to a cluster?
i. Select Yes, make this server a member of an existing cluster.
ii. Select a cluster: Choose the cluster created earlier.
v. Click Next.
vi. Click Finish.
4. Repeat steps 1 to 3 to create multiple managed servers, with a unique name and port, on this
domain.
10.2.3 Step 3: Start the Node Manager
Node Manager is a stand-alone Java program provided with each WebLogic server installation. You
use it to start, stop, and suspend server instances, and to automatically restart servers that fails. Node
Manager must run on each computer that hosts WebLogic Server instances that you want to control
with the Node Manager.
You can manually start the node manager by executing startNodeManager script. For
WebLogic 11g you can find the script file under <WL_INSTALL_
DIR>/Middleware/wlserver/server/bin.
10.2.4 Step 4: Create Machines
To start a managed server from the cluster for each computer hosting a set of managed servers, a
machine needs to be configured on the server where you want to create the cluster.
To create a Machine, follow these steps:

Server Linux
Version 3.0
1. In the left pane of the Administration Console, expand Environment and select Machines.
2. Click New.
3. On Create a New Machine > Machine Properties page, enter the following details:
l Name: Enter the name of the machine as machine1.
4. Repeat steps 1 to 3 to create multiple machines, with a unique name, on this domain.
10.2.5 Step 5: Configure Machines
Configure the machine to listen to the local or remote Node Manager and add the servers the machine
controls.
To configure Machines, follow these steps:
2. Select the machine created earlier.
3. Select Configuration > Node Manager tab:
i. Type: Select the Node Manager type from the drop-down list. By default the type of the
Node Manager is SSL. It is recommended to go with the default type.
ii. Listen Address: Enter the DNS name or the IP address on which the Node
Manager listens this physical server. You can enter localhost, if the Node Manager runs
on the same box.
iii. Listen Port: This is the port where the Node Manager listens for incoming requests. By
default,Node Manager listens on port 5556.
iv. Click Save.

Server Linux
Version 3.0
4. Select Configuration > Servers tab:
i. Click Add.
ii. Under Add a Server to Machine > Identify Server
l Select a Server: Select the managed server created earlier.
iii. Repeat steps i and ii to add multiple servers.
5. These steps should be repeated for each machine created.
10.3 Configure Application Server
Provide JVM parameters using the Administration Console. You need to log in to the WebLogic
To configure the server, follow these steps:
1. Log in to WebLogic Administration Console.
2. Select Environment > Servers from the left menu.
3. Click the server on which you need to set the JVM parameters.

Server Linux
Version 3.0
4. Select the Server Start tab.
5. In the Arguments field, enter the system properties as described below:
Parameters (for Requir Description

JVM) ed
-Xmx2048m (Sun) Yes Minimum Heap size: 2GB
-Xmx:2048m
(JRockit)
-Xms2048m (Sun) Yes Maximum Heap size: 2GB
-Xms:2048m
(JRockit)
- Yes This is a recommended setting.

XX:UseParallelGC
(SUN)
-Xgcprio:throughput
(JRockit)

XX:MaxPermSize=
512m

Server Linux
Version 3.0
Parameters (for Requir Description

JVM) ed
- Yes This is the directory where the

Dkpns.configLocati configResouce.properties,
on
database.properties,
kpnslog4j.properties and pns-
ehcache.xml files must be placed. Example: if
the location is /data/kpnsconfig , then you
must specify the property as
Dkpns.configLocation=/data/kpns
config
Dhibernate.dialect Enable DB2=

s you to org.hibernate.dialect.DB2Dialec
t- per database
connect
to the SQL=
databa
org.hibernate.dialect.SQLServer
se.
JDBC
Dialect
has to
Oracle=
be
org.hibernate.dialect.Oracle10g
configu
red on Dialect
the
MYSQL=
AppSer
ver org.hibernate.dialect.MySQLDial
level. ect
Sample arguments for Managed Server1 would look like:
-Xms2048m –Xmx2048m -Dkpns.configLocation=/data/kpnsconfig

Server Linux
Version 3.0
8. Perform steps number two to seven for all the managed servers on which Kony Application
Server needs to be deployed.
To configure datasource, follows these steps:
10.4.1 Setup Datasource
1. In Administration Console, select Services > Data Sources from the left menu.
2. Click New, and select Generic Data Source.
3. Provide the following information:
l Data source name: kpnsdb
l JNDI Name: jdbc/kpnsdb
l Database Type: Select the database type.
4. Click Next to continue.
l Select the database driver.

o Oracle:If the selected database type is Oracle, the default driver selected is a two
phase commit driver. For setting up database drivers for KPNS, we recommend
you to use Oracle Driver (Thin) for Instance Connections.
o MySQL: If the selected database type is MySQL, the default selected driver is the
recommended database driver.

Server Linux
Version 3.0
o DB2: If the selected database type is DB2, select the database driver as:Oracle's
DB2 Driver XA
i. Oracle's DB2 Driver Non-XA
ii. Oracle's DB2 Driver Non-XA
o Microsoft SQL Server: If the selected database type is Microsoft SQL Server,
select the database driver as, Oracle's MS SQL Server Driver Non-XA.
l Click Next.
l Enter connection properties like Database Name, Host Name, Port, Database User
Name and Password.
Note: For DB2, database schema name should be in capital letters like KPNSDB.
6. Click Next to continue.
7. Select the cluster created earlier, as the target for the data source
8. Click Finish to create a datasource for the given details.
10.5 Start the Cluster
You must first complete the above configurations and complete the KPNS setup before starting the
cluster.
To start the cluster, follow these steps:
10.5.1 Step 1: Create the Managed Server Configuration
The domain configuration currently exists in the machine hosting the Administration server. You have
to copy the domain configuration on each machine. These copies of the domain configuration will be
used by the managed servers. Run the following commands to create a template of the domain
configuration.

Server Linux
Version 3.0
1. Navigate to the common/bin directory of the WebLogic Home.
cd <WL_HOME>/common/bin
2. Run the pack command to generate the template.
pack.sh -managed=true -domain=<Weblogic_Install_Dir>/user_

projects/domain/<domain_name> -template=<Location_to_store_
generated_template>/<template_name>.jar -template_name=”<template_
name>”
A template is created based on which you create domain on the other physical servers.
10.5.2 Step 2: Copy the Managed Server Configuration
Copy the template created in the above step to a temporary location on each physical machine. Make
sure you installed same version of WebLogic Server on each physical machine. Execute the below
command to create the domain on each physical server.
1. Navigate to the common/bin directory of the WebLogic Home.
cd <WL_HOME>/common/bin
2. Run the unpack command to create the domain configuration.
unpack.sh -domain=<Weblogic_Install_Dir>/Middleware/user_
projects/domain/<domain_name>-template=<location_of_the_copied_
template>
A domain is created with the provided domain name.
10.5.3 Step 3: Enroll the Node Manager
Enroll the Node Manager to make the managed servers on the domain to be accessible. On each
machine, which is a part of the cluster, perform the following steps:

Server Linux
Version 3.0
1. Navigate to WL_HOME/common/bin.
2. Execute wlst.sh. This action opens a console to execute the commands required for
enrolling the Node Manager.
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell Type

help() for help on available commands wls:/offline>
3. Enter connect('<username>','<password>','t3://<Admin
Host>:<Admin Port>'), where the username and password are the credentials
required to connect to the Administration Server.
4. Below is the sample command:
wls:/offline>connect
('weblogic','weblogic1','t3://KonyServer:8080')
5. Enter nmEnroll('<Domain Dir>', '<Node Manager Home>'), where

domain directory in our case is <Weblogic_Install_Dir>/Middleware/user_
projects/domain/<domain_name> and Node Manager home is usually WL_
HOME/common/nodemanager.wls:/KonyMiddleware/serverConfig>nm
Enroll('<Weblogic_Install_Dir>/Middleware/user_
projects/domain/<domain_name>', 'WL_
HOME/common/nodemanager')
Restart the Node Managers on all the machines after performing this step.
10.5.4 Step 4: Start the cluster
2. Select the cluster you created.
3. On the Control page, select all the servers and click Start.

Server Linux
Version 3.0
This starts the Managed Servers on all physical servers. The remote start is done through the Node
Manager.
This completes the cluster setup. Configure a hardware Load Balancer to complete the load
balancing.
10.6 Deploy Application Web Archive File
Deploy Kony MobileFabric Messaging after you start the Cluster. Download or copy kpns.war
and place it on your local machine.
To deploy Application Web Archive file, follow these steps:
1. In the left pane of WebLogic Administration Console, select Deployments.
2. Click Install.
3. In the Install Application Assistant, select the kpns.war by using the folder navigation
provided.
4. Let the Target style be the default (Application type deployment) and click Next.
5. In the Select deployment targets pane, select the cluster created and click Next.
6. Go to Source accessibility section of the Optional Settings pane and choose Copy this
application onto every target for me.
7. Click Finish. The deployment has been completed successfully.
8. To access the kpns console, navigate to http://<Host Name or IP address>/kpns.
Note: If Kony MobileFabric Messaging security is enabled, the Weblgic basic authentication
security has to be disabled.
To disable the Weblgic basic authentication security, modify the security-configuration tag in
the config.xml file located in the config folder of Weblogic server

Server Linux
Version 3.0
<?xml version='1.0' encoding='UTF-8'?>

<domain xmlns="http://xmlns.oracle.com/weblogic/domain"
xmlns:sec="http://xmlns.oracle.com/weblogic/security"
xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/x
acml
http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd
http://xmlns.oracle.com/weblogic/security/providers/passwordval
idator
http://xmlns.oracle.com/weblogic/security/providers/passwordval
idator/1.0/passwordvalidator.xsdhttp://xmlns.oracle.com/weblogi
c/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd
http://xmlns.oracle.com/weblogic/security
http://xmlns.oracle.com/weblogic/1.0/security.xsd
http://xmlns.oracle.com/weblogic/security/wls
http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
<name>plt1</name>
<domain-version>10.3.5.0</domain-version>
<security-configuration>
<name>plt1</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-
authenticatorType
"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-
asserter Type">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>

Server Linux
Version 3.0
<sec:role-mapper
xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml"
xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer
xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml"
xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-
adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-
mapperType">
</sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-
providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-
builder>
<sec:name>myrealm</sec:name>
<sec:password-validator
xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/
passwordvalidator" xsi:type="pas:system-password-
validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-
speci
al-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{AES}

Server Linux
Version 3.0
ojAgdYBG3tN2+X/c52RaQbhB6hCRrlFlKKqz/4joVzQUtk+WEdm0MbvIGgPusmc
fhcKHQLaYwnhtnUWvkMZ7NTxoXv1hQjlNKBRbnhMat8ti0KFaN46QT
bd4AmW3qczp</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>{AES}
dbeIf/S+jYhL1Uyj1rS33ZJf3G3oi9n4Bi9RdJwWv8w=</node-manager-
password-encrypted>
<enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>
</security-configuration>
<server>
<name>AdminServer</name>
<listen-address></listen-address>
<server-start>
<arguments>-Xms1024m -Xmx1024m -
Dkpns.configLocation=/data/kpns-config -
Dhibernate.dialect=org.hibernate.dialect.Oracle10gDialect -
Xdebug -Xnoagent -Xrunjdwp:transport=dt_
socket,address=4000</arguments>
<username>weblogic</username>
<password-encrypted>{AES}
EZZ/aAqiz+8goecXlWC+jaWOcVOijjUY3KXjM3EHHHw
=</password-encrypted>
</server-start>
</server>
<embedded-ldap>
<name>plt1</name>
<credential-encrypted>{AES}
C6eItmd8OAAirP/G/TIQur8boApKvb1sICBHGFuvafr
RWCRg/pUfxjTceh2s7mGO</credential-encrypted>
</embedded-ldap>

Server Linux
Version 3.0
<configuration-version>10.3.5.0</configuration-version>
<app-deployment>
<name>kpns</name>
<target>AdminServer</target>
<module-type>war</module-type>
<source-path>servers/AdminServer/upload/kpns.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<admin-server-name>AdminServer</admin-server-name>
<jdbc-system-resource>
<name>kpnsdb</name>
<target>AdminServer</target>
<descriptor-file-name>jdbc/kpnsdb-jdbc.xml</descriptor-file-
name>
</jdbc-system-resource>
</domain>

11. Configure Tomcat Server Kony MobileFabric Messaging Manual Installation Guide - Linux
Version 3.0
11. Configure Tomcat Server
To configure the Tomcat server, follow these steps:
1. Navigate to <Tomcat Installation Directory>/bin
2. Modify startup.sh with following parameters:

JVM) d

XX:MaxPermSize=51
2m

ns-config

Version 3.0

JVM) d

connect
to the
databas
e. JDBC
has to be
configure
d on the
AppServ
er level.
3. Configure the following JVM parameters:

-Xms2048m –Xmx2048m -Dkpns.configLocation=<path of the kpns
config location extracted from kpns-resources.tar>
5. Configure the datasource.
11.1 Database
11.1.1 MySQL
1. Copy mysql-connector-java-5.1.26-bin.jar to <Tomcat

installation directory>/lib
2. Navigate to <Tomcat installation directory>/conf

Version 3.0
3. Add datasource context.xml as given below:

<Resource name="jdbc/kpnsdb" auth="Container"
type="javax.sql.DataSource" scope="Shareable"
factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"
maxActive="50" minIdle="1" maxIdle="10" testWhileIdle="true"
maxWait="10000" initialSize="10" testOnBorrow="true"
validationQuery="SELECT 1" removeAbandoned="false"
removeAbandonedTimeout="180" logAbandoned="false"
username="username" password="password"
driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://<host>:<port>/<database>?autoReconnect=tru
e&useUnicode=yes&characterEncoding=UTF-
8&cachePrepStmts=true&cacheCallableStmts=true&ca
cheServerConfiguration=true&useLocalSessionState=true&am
p;elideSetAutoCommits=true&alwaysSendSetIsolation=false&
amp;enableQueryTimeouts=false&rewriteBatchedStatements=t
rue&max_allowed_packet=104857600 "/>
4. Replace the values given below in above configuration.
Configuration Value Description
host Database server IP/name
port Database server port
username Database user name
password Database password
database Database name

Version 3.0
11.1.2 Oracle
1. Copy ojdbc6.jar to <Tomcat installation directory>/lib

type="javax.sql.DataSource" scope="Shareable"
factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"
maxActive="30" minIdle="1" maxIdle="10" testWhileIdle="true"
maxWait="10000" initialSize="10" testOnBorrow="true"
validationQuery="select 1 from dual" removeAbandoned="false"
driverClassName="oracle.jdbc.driver.OracleDriver"
url="jdbc:oracle:thin:@host:port:sid"/>
4. Replace the value given below in the above configuration.
sid Oracle service id/name

Version 3.0
11.1.3 DB2
1. Copy db2jcc4.jar to <Tomcat installation directory>/lib

type="javax.sql.DataSource"
scope="Shareable"factory="org.apache.tomcat.jdbc.pool.DataSo
urceFactory" maxActive="30" minIdle="1" maxIdle="10"
testWhileIdle="true" maxWait="10000" initialSize="10"
testOnBorrow="true" validationQuery="select 1 FROM
SYSIBM.SYSDUMMY1"
removeAbandoned="false" removeAbandonedTimeout="180"
logAbandoned="false" username="username" password="password"
driverClassName="com.ibm.db2.jcc.DB2Driver"
url="jdbc:db2://host:port/database:currentSchema=schemaname;
progressiveStreaming=2;"/>
4. Replace the values given below in the above configuration.

Version 3.0
schemaname Schema name
11.1.4 SQLServer
1. Copy sqljdbc4.jar to <Tomcat installation directory>/lib
3. Add datasource context.xml as given below.

type="javax.sql.DataSource"
scope="Shareable"factory="org.apache.tomcat.jdbc.pool.DataSo
urceFactory" maxActive="50" minIdle="1" maxIdle="10"
testWhileIdle="true" maxWait="10000" initialSize="10"
testOnBorrow="true" validationQuery="SELECT 1"
removeAbandoned="false"
driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDrive
r"
url="jdbc:sqlserver://host:port;databaseName=database;user=u
sername;password=password;sendStringParametersAsUnicode=tru
e;"/>

Version 3.0
4. Replace the value given below in above configuration.
1. To deploy Kony MobileFabric Messaging on Tomcat Server, copy kpns.war file to the
following location:
<Tomcat installation directory>/webapps/
2. After you deploy Kony MobileFabric Messaging, complete the Kony MobileFabric Messaging
setup and start the Tomcat Server.

Manual Installation Guide - Linux

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual Installation Guide - Linux

Uploaded by

Copyright:

Available Formats

Kony MobileFabric™

Kony MobileFabric Messaging

© 2015 by Kony, Inc. All rights reserved 1 of 121

Copyright © 2015 Kony, Inc.

All rights reserved.

© 2015 by Kony, Inc. All rights reserved 2 of 121

Date Document Description of Modifications/Release

03/07/2016 3.0 Updated the Software System Requirements (per physical

01/20/2016 2.0 Updated Install and Configure KPNS section

06/17/2015 1.0 Document Release for Kony MobileFabric Messaging Manual

© 2015 by Kony, Inc. All rights reserved 3 of 121

1.2 Intended Audience 7

1.3 Formatting Conventions 7

2.1 Advantages of Using Kony MobileFabric Messaging 10

2.2 How Kony Push Notifications Works 11

3.1 Hardware Requirements (per physical instance) 13

3.2 Software System Requirements (per physical instance) 13

3.3 Database System Requirements (per physical instance) 13

4. Corporate Firewall Settings 15

4.1 Installation Note 20

5. Install and Configure Kony MobileFabric Messaging 21

5.1 Installation Tasks 21

5.2 Database Setup 21

5.3 Download Kony MobileFabric Messaging Files 25

5.4 Setup Kony MobileFabric Messaging 28

6. Kony MobileFabric Messaging Upgrade 42

© 2015 by Kony, Inc. All rights reserved 4 of 121

6.1 Database Upgrade 42

6.2 Kony MobileFabric Messaging Upgrade 52

7. Configure Jboss 5.1 Server 53

7.1 Configure JBoss Server 53

7.2 Configure Datasource 55

7.3 Deploy KPNS 58

8. Configure Jboss 6.2 Server 59

8.1 Configure JBoss Server 59

8.2 Configure Datasource 61

8.3 Deploy Kony MobileFabric Messaging 71

9. Configure WebSphere Server 72

9.1 Configure the Application Server 72

9.2 Configure Database 74

9.3 Configure Shared Libraries for WebSphere 8 and 8.5 85

9.4 Deploy Kony MobileFabric Messaging 86

9.5 Configure WebSphere Network Deployment (7.0 and 8.5) - Multi-node 91

10. Configure WebLogic Server 98

10.1 Create New Domain 98

10.2 Create Cluster 99

10.3 Configure Application Server 103

10.4 Configure Datasource 106

© 2015 by Kony, Inc. All rights reserved 5 of 121

10.5 Start the Cluster 107

10.6 Deploy Application Web Archive File 110

11. Configure Tomcat Server 115

11.1 Database 116

11.2 Deploy Kony MobileFabric Messaging 121

© 2015 by Kony, Inc. All rights reserved 6 of 121

l Kony MobileFabric Identity and Console

l Kony MobileFabric Integration

l Kony MobileFabric Messaging

l Kony MobileFabric Sync

1.2 Intended Audience

1.3 Formatting Conventions

© 2015 by Kony, Inc. All rights reserved 7 of 121

Monospace l User input text, system prompts, and responses