Kony Pre-Install Guide (On-Premise Only)

Kony Management Pre-installation Guide - Linux

On-Premises

Release V8

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.

November, 2017

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

Revision History

Date Document Version Description of Modifications/Release

10/09/2017 1.0 Document published for V8 GA

Table of Contents

1. Preface 6

1.1 Purpose 6

1.2 Intended Audience 6

1.3 Formatting Conventions 6

1.4 Supported Platforms 8

1.5 Contact Us 8

2. EMM Architecture and Components 9

3. EMM Disaster Recovery (DR) Architecture 13

3.1 DR Setup 13

3.2 DR Synchronization 14

4. System Requirements 15

4.1 Hardware Requirements 15

4.2 Software Requirements 18

4.3 Database Requirements 23

4.4 Linux Server Requirements 26

4.5 Linux User Requirements 29

4.6 Network-Related Prerequisites 40

4.7 Exchange Server Prerequisites 56

5. Windows 2008/2012 Server Setup 59

5.1 Setup SCEP and CA Server 60

5.2 Kony Exchange Service Setup 103

5.3 Kony Windows Mobile 6.x Group Policy service installation 105

5.4 Windows Server for Windows Phone App Wrapping 109

6. Apple Server for App Wrapping 114

6.1 Software Requirements 114

6.2 Install Xcode and iOS Simulators 114

6.3 Active SSH Access for Users after MAC OS Upgrade 116

6.4 Installing dos2Unix 116

7. Certificate Requirements 118

7.1 SSL Certificates 118

7.2 Device Certificates 119

8. Third-Party Systems 121

8.1 Google Maps API 121

8.2 Admin Email Settings 121

8.3 Active Directory Integration 121

8.4 Package Family Name (PFN) for Windows Notification Service (WNS) 122

9. Windows Mobile 6.x - SCMDM 2008 123

1. Preface

Enterprise Mobility Management (EMM) software is a policy configuration and management tool for hand-held mobile devices and corresponding applications on smartphones and tablets. EMM helps enterprises to manage complex communications between mobile devices by supporting security, network services, and software and hardware management across multiple OS platforms.

EMM also supports bring your own device (BYOD) initiatives that has become the focus of many enterprises. It can support corporate and personal devices, and helps to support a more complex and heterogeneous environment. EMM supports Mobile Content Management.

1.1 Purpose

The Pre-Installation Guide provides a list of resources that are to be kept ready prior to installation. Having these in place ensures a smooth installation process and easy deployment of Kony EMM.

Details of installation of third-party software required shall not be provided in the document. Whereever applicable, links to appropriate resources are provided.

Some elements described in this Guide will be configured / consumed after successful installation and start-up.

1.2 Intended Audience

This document is intended for engineers or system administrators who will install and configure Kony EMM Console and Kony Enterprise Store. We assume that the reader of this document is familiar with deploying software on Red Hat Linux servers and installing a database on a Red Hat Linux Enterprise server.

1.3 Formatting Conventions

The following formatting conventions are used throughout the document:

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.

Note Provides helpful hints or additional information.

Important Highlights actions or information that might cause problems to systems or data.

1.4 Supported Platforms

Supported Platforms are iOS, iPad, Android, Android Tablet, and Windows Phone 8.1. Other Device Operating Systems are not supported.

1.5 Contact Us

We welcome your feedback on our documentation. Write to us at [email protected]. For technical questions, suggestions, comments or to report problems on Kony's product line, contact [email protected].

2. EMM Architecture and Components

An overview of the EMM Architecture and Components is shown below:

The following table describes components in more detail.

Component Description

Mobile Devices Mobile Devices with Launchpad application installed communicate with EMM and Tablets server over HTTPS. Also EMM console can be accessed on HTTPS port which is meant for Administrator use. Currently EMM supports iPhones, iPads, Android devices, Windows 6.x and Windows Phone 8 devices.

Load Balancer SSL certificate needs to be installed on Load Balancer VIP for SSL offload. It and SSL is recommended to install “VeriSign Secure Site Pro” SSL which has the maximum device compatibility.

Apache Server Apache servers will host static content, rewrite rules, maintain session affinity for backend Tomcat server based on cookies. Optionally, additional SSL certificates can be installed on Apache servers for an end to end SSL solution. Apache server allows to download binaries from device/web based on secure/encrypted URL. Encrypted URL is valid for particular amount of time (e.g. 3 minutes)

NFS Server & To provide common mount solution, you need NFS server. Common mount NFS mount hosts app binaries and other static data. Common mount is attached to both Apache servers and Tomcat servers for multi-node environments. For high availability, a backup NFS server can be configured.

User uploads App binaries in the Management console and Tomcat server stores these App binaries on common mount. Apache server serves App binaries from common mount to the device.

Tomcat and Tomcat is the web server on which EMM is deployed. EMM app is a J2EE Memcached Web archive. Memcached is used for caching database queries.

MAC Server MAC server is required to wrap and sign iOS apps. EMM server moves iOS apps on NFS mount to MAC on port 22 via SSH and performs wrap and sign /sign only actions. Signed apps are then placed on NFS mount and available for download via Apache server. This is mandatory to support App Management on iOS devices.

Component Description

Exchange Server Exchange server is required to send notification emails to users. EMM has the ability to use both SMTP port 25 and SMTPS port 465 over SMTP authentication. These ports need to be opened accordingly in the firewall. Using Kony Exchange service, you can block or unblock emails (clients). Blacklisted email clients cannot communicate with the Exchange server from your device.

Active Directory EMM has the ability to import users and groups. User authentication is Server performed on Active Directory only. Please note that EMM just imports users but not their passwords. LDAP port 389 or LDAPS port 636 can be used for EMM server to connect AD server. These ports need to be opened accordingly in the firewall.

Windows Server Windows Mobile 6.x devices communicate with Windows Server 2003 on 2003 HTTP/HTTPS using ports 80, 443, 8443. EMM server connects to Window Server 2003 to get device information. Windows 2003 server will also connect to the Windows Server 2008/2012 for Group policy management service.

Windows Server SCEP server must be installed on Windows Server 2008/2012. Interaction 2008/2012 with SCEP server is mandatory in order to enroll iOS devices to EMM. Devices communicate SCEP over 443 port and EMM server will also l SCEP communicate the SCEP server on the same port. Server Using Kony Exchange service, you can block or unblock emails (accounts). l Kony The blacklisted email clients cannot communicate with the Exchange server Exchange from your device. Service In order to support Windows 6.x devices, Group Policy Management l Windows component must be installed. The Windows Server 2003 [mobile device 6.x MDM manager component] and Windows Server 2008/2012 both reside in the same Group network and the communication is carried over HTTP(S) on port 7777. Policy

Component Description

GCM EMM uses Google messaging cloud to send push notifications to Android devices. Respective ports and host names need to be opened in the firewall from EMM server.

If the devices are behind corporate networks / Wi-Fi’s, the required URL’s ports need to be allowed in inbound rules. Please refer Push notification firewall prerequisites.

Apple Push EMM also uses APNS cloud to send push notifications to iOS devices. Notification Respective ports and Apple host names need to be opened in the firewall from Service (APNS) EMM server.

If the devices are behind corporate networks / Wi-Fi’s, the required URL’s ports need to be allowed in inbound rules. Please refer Push notification firewall prerequisites.

Cluster virtual For production EMM environments any of this database OS level cluster REDHAT or solution can be integrated for EMM database on MySQL, which will have VERITAS cluster active and passive nodes along with heartbeat service and SAN as a suite database shared mount. This will have a cluster IP on top of DB services and all EMM Tomcat nodes can use the same for JDBC. The default MySQL port is 3306.

3. EMM Disaster Recovery (DR) Architecture

Global Traffic Manager (GTM) can be configured and used as Active Passive load balancing. Currently EMM is not supported with Active-Active setup. Instead of GTM you can also manage primary and DR sites by changing DNS record.

An overview of the EMM DR Architecture is shown below:

3.1 DR Setup

Secondary data center (DR) should have replica of below components from Primary data center. It is recommended to have initial replica along with file system backups from the running state from primary data center.

l Windows Server 2008 / 2012 (SCEP, Exchange Service, Group Policy Service, and Windows Wrapping)

l Windows Server 2003

l MAC server

l Firewall and Load balancer rules

l NFS server

l EMM tomcat and memcached instances

l Redhat or Veritas Cluster suite setup

Take Windows Server 2003 backups and recover the system by following Microsoft Technet documentation. More details are available at – http://technet.microsoft.com/en- us/library/dd261892.aspx

3.2 DR Synchronization

The secondary data center should have the content replica from AD server domain, email server connectivity, GCM, APNS, WNS and MPNS cloud connectivity similar to primary data center.

l All tomcat contents, including emm_config application contents

l Konyemmmaster database full backup – Recommended to take a backup and restore this sql files manually on DR setup on daily basis

l docroot contents from any one NFS mount need to be synchronized in DR at least one time whenever a new apps are added and wrapped

l Apache server configuration and static contents

4. System Requirements

Kony EMM has specific system requirements for installation and operation. Before installing Kony EMM, verify that you meet the following requirements:

l Hardware Requirements

l Software Requirements

l Database Requirements

l Linux Server Requirements

l User Requirements

l Network Related Prerequisites

l Exchange Server Prerequisites

Note: Ensure you have a valid Kony license key from your sales representative, the developer portal, or partner. Without a valid license, you cannot install EMM.

4.1 Hardware Requirements

The following sections explain the hardware requirements for application server, apple server, and database server.

4.1.1 Hardware Requirements for Application Server (per physical instance)

Component Requirement

Processor Quad-Core 3.6 GHz

Memory 16 GB

Internal Storage 300 GB (15K SAS 3.5") with 2 Drives (Raid 1)

Component Requirement

Network 2 Gigabit Ethernet Ports

Operating System Linux Red Hat Enterprise License 5.4 to 6.6 (64-bit) or CentOS 5.4 to 6.5.

4.1.2 Hardware Requirements for Database Server (MySQL and Oracle)

Component Requirement

Processor Quad-Core 3.6 GHz

Memory 32 GB

Internal Storage 300 GB (15K SAS 3.5") with 3 Drives (Raid 5)

Network 2 Gigabit Ethernet Ports

Operating System Linux Red Hat Enterprise License 5.4 to 6.6 (64-bit) or CentOS 5.4 to 6.5.

4.1.3 Hardware Requirements for Database Server (Microsoft SQL Server)

Component Requirement

Processor Quad-Core 3.6 GHz

Memory 32 GB

Internal Storage 300 GB (15K SAS 3.5") with 3 Drives (Raid 5)

Network 2 Gigabit Ethernet Ports

Operating System Windows Server 2008 Enterprise or Datacenter Edition

4.1.4 Hardware Requirements for Windows 2008/2012 Server

SCEP Server (iOS MDM enrollment), Windows 6.x MDM group policy and Kony Exchange Service (block and unblock email clients from devices) use Windows 2008/2012 Server.

Note: For Windows app wrapping, to manage Windows Phone 8.1 enterprise apps, deploy Windows Server 2012 (x64).

Component Requirement

Processor 1.6 GHz (x64 processor)

Memory 4 GB

Internal Storage 40 GB

4.1.5 Hardware Requirements for Apple Server

The Apple server (for example, Mac Mini server) is used to dynamically wrap the policy framework on iOS applications.

Important: During installation Apple server setup should be completed and SSH user name, password and connection details should be available.

Note: The hardware requirements mentioned below are needed only if iOS devices are targeted within your project.

Component Requirement

Processor 2.5 GHz Dual-Core Intel Core i5 (Turbo Boost up to 3.1 GHz) with 3 MB L3 cache

Component Requirement

Memory 4 GB (two 2 GB) of 1600 MHz DDR3 memory

Internal Storage 500 GB (5400-RPM) hard drive

Network 10/100/1000 BASE-T Ethernet (RJ-45 connector)

Operating Apple OS X Version: 10.9.4 (13E28) System

4.1.6 Hardware Requirements for Windows 2003 Server

Applicable only if you have Windows 6.x devices.

Component Requirement

Processor 1.4 GHz (64 bit)

Memory 1 GB. For computers with more than 4 GB of RAM, be sure to confirm hardware compatibility by clicking the appropriate link in Support resources.

Internal 40 GB Storage

Operating Windows Server 2003 Standard x64 Edition with SP2 System

4.2 Software Requirements

Software requirements matrix

Requirement Device OS Operating System

iOS Android Windows Windows Windows Linux 6.x Phone 8.x

Java Runtime Yes Yes Yes Yes Yes Yes Environment

Database Oracle Yes Yes Yes Yes Yes Yes 11g

Database Microsoft Yes Yes Yes Yes Yes Yes SQL Server 2008 R2 / 2012

Database MySQL Yes Yes Yes Yes Yes Yes 5.5/5.6

Linux 64-bit Yes Yes Yes Yes No Yes

Android SDK TAR No Yes No No No No file

Mac OS Yes No No No No No

Xcode Yes No No No No No

Windows Server Yes No No No Yes No 2008

Windows Server Yes No No No Yes No 2012

Windows Server Yes No Yes No No No 2003

Requirement Device OS Operating System

iOS Android Windows Windows Windows Linux 6.x Phone 8.x

Exchange Server Yes Yes No Yes No No

Exchange Service Yes Yes No No No No

SCEP Server Yes No No No No No

CA Server Yes No No No No No

Windows Mobile No No Yes No No No 6.x Group Policy Service

Verisign Secure Yes No No Yes No No SSL

GoDaddy Secure Yes No No No No No SSL

Wildcard Yes No No No No No Distribution Certificate

Wildcard Mobile Yes No No No No No Provisioning Profile

Launchpad Push Yes No No No No No Certificate

Launchpad Yes No No No No No Provisioning Profile

Requirement Device OS Operating System

iOS Android Windows Windows Windows Linux 6.x Phone 8.x

Apple Push Yes No No No No No Certificate for MDM

Keystore certificate No Yes No No No No

GCM Key No Yes No No No No

Google MAPS v2 No Yes No No No No Key

Google Maps API No Yes No No No No

Symantec No No No Yes No No Enterprise Mobile Code Signing Certificate

Package Family No No No Yes No No Name

The software requirements for installing EMM console are:

Component Version

Java Oracle Enterprise License JDK 1.8.0_xx Runtime Environment Important: Java 7 is not supported by Kony Management from V8 GA release.

Component Version

Database Oracle 11g

Microsoft SQL Server 2008 R2 / 2012 /2014

MySQL 5.5/5.6

For MySQL database, set the event_scheduler = ON, socket = /var/lib/mysql/mysql.sock in /etc/my.cnf (or) /etc/mysql/my.cnf under the " [mysqld]" section.

The global event_scheduler = ON System variable determines whether the Event Scheduler is enabled and running on the server, which is required for scheduling EMM jobs.

Linux 64-bit Choose one of the following operating systems:

l CentOS 6.4

l Red Hat Enterprise License 6.4

l Oracle Linux 6.3

Android SDK Download from Kony Developer Portal. Navigate to the Kony Management section TAR file and click on the specific release related files you want to download. For example, if you want to download Kony Management 3.0, click on the Kony v3.0 GA tab. http://community.kony.com/downloads/manual

Mac OS OS X Version: Yosemite (10.10)

Xcode XCode Version: 7.3 If you upgraded Xcode, open Xcode at least once after the upgrade to install all dependent components.

Windows Windows Server 2008 or 2012 operating system. For the Windows app wrapping, 2008/2012 you need Windows Server 2012.

Component Version

Visual Visual Studio Express Edition Update 3 (Prerequsite for Windows app wrapping) Studio

Microsoft Microsoft Silverlight Runtime 5.0 (Prerequsite for Windows app wrapping) Silverlight Runtime

Microsoft Microsoft Silverlight SDK 5.0 (Prerequsite for Windows app wrapping) Silverlight

Cygwin Cygwin (32 bit) 2.850. (Prerequsite for Windows app wrapping)

Windows Windows Server 2003 operating system 2003

Note: The InstallAnyWhere software that creates the EMM installer does not allow a dollar sign ($) in passwords.

4.3 Database Requirements

The following are the database requirements for Kony Management.

l MySQL requirements

l Oracle requirements

l MSSQL requirements

4.3.1 MySQL Requirements

l Only a qualified MySQL database administrator should handle the MySQL database setup.

l Supported versions are MySQL 5.5 and MySQL 5.6

l Configure your database with unicode character set as UTF8

l Modify my.cnf or my.ini files with the following parameters:

[client] default-character-set = utf8 [mysql] default-character-set = utf8 [mysqld] character-set-client-handshake = FALSE character_set_server='utf8'

l Restart your MySQL service

l To verify that your changes are applied correctly, verify the database variables by running the following query:

4.3.2 Oracle Requirements

l Only a qualified Oracle database administrator should handle the Oracle database setup.

l Supported versions is Oracle 11g

l While creating the Oracle database, configure your database with unicode character set. AL32UTF8 for Database characterset and AL16UTF16 for National characterset.

l Create the following three tablespaces. These tablespaces will be used to create EMM database objects.

l Tables and data tablespace: emm_data

l Index tablespace: emm_index

l Lob tablespace: emm_lob_data

l Create a database user with default tablespaces (emm_data) and grant quota to two other tablespaces (emm_index and emm_lob_data tablespaces).

l If the Oracle database is of version 11g without pdb, then you can use the normal user for JDBC authentication.

l Grant the following permissions to the user.

l For versions below Oracle 11g without pdb option: Grant connect, resource, create view, create procedure.

l Usage of the database service name.

l For versions below Oracle 11g without pdb option: Use ORACLE_SID in the JDBC URL.

4.3.3 MSSQL Requirements

Prerequisites for Kony Management with SQL Server

l Database User security role: Create a database login dbclient using SQL server authentication with server roles as sysadmin and public

l Database and schema access: Installer will make use of the above login to create necessary databases and schemas required for the selected Kony Management components.

l Database Growth sizing: Refer to Kony Fabric Deployment Guide > Database Growth Sizing

l Database Transaction log size: Allocate sufficient space for the Transaction log file based on all the transactions activity of all the Kony Management components installed and as per your database backup policy. Because transaction log sizing is linked to database backup. If additional application logging/events are enabled in multiple components of Kony Management , then you may need to consider additional size for the transaction log.

l Temp Database and temp log: This is based on usage of all the databases on the server instance, by all applications connecting to these databases. In case of Kony Management, for sizing of the temp database, consider auto growth with increment size should be of 100MB and with maximum size to 10GB. But if application logging/events are enabled in multiple components of Kony Management, then the maximum size should be increased upto 20GB. This size will get reclaimed as and when the DB is restarted.

l Database versions: You can use SQL Server Standard Edition or SQL Server Enterprise Edition database for installing Kony Management. Kony Management is compatible with these editions. There are no prerequisites specific to these editions as Kony Management uses features common to both editions.

l Backup plan: You must use your organization's defined backup and retention policies for Backup strategies for your database.

4.4 Linux Server Requirements

There are several elements that should be ready and part of the Linux Server.

4.4.1 Utilities

1. Ensure GCC utility is installed. To check the version, type: gcc --version.

2. Ensure to install 32-bit libstdc++.i686, glibc.i686 and libzip.i686 operating systems packages by running the following commands as per the operating system.

# yum install libstdc++* glibc* libzip* # yum install libstdc++.so.6

3. Check the iptables if ports for App Server, Web Server, Memcache, Kony EMM Server and other Servers are configured properly. Alternatively, you may choose to shut down iptables.

Enter the command to see the iptable status: /etc/init.d/iptables status

# /etc/init.d/iptables status Firewall is stopped.

4. If selinux is running, ensure to configure selinux to allow communication among servers. We recommend to shut down selinux. To see the status, type the command: sestatus.

To shut down selinux, follow these steps:

a. Type the command: setup. The Choose a tool dialog appears.

b. In the Choose a Tool options, select the Firewall configurations.

c. Select Security Level as Disabled and then select SELinux as Disabled.

d. Click OK and then from the Choose a Tool dialog, select Quit.

e. Restart the Linux machine.

5. Download and install the dos2unix software on Linux.

Note: Ensure that the time zone is same across database server and app server.

4.5 Linux User Requirements

It is recommended that two users be created on the Linux Server for EMM Installation.

l Linux Installation User

l Database User

These users must have required permissions to perform the installation process.

When a root user installs the application and if the root user is hacked, there exists a risk of security flaws to the files on the server. To avoid these threats, an installation user needs to be created.

4.5.1 Linux Installation User

To create an installation user, follow these steps:

1. Log in as root user.

2. Create a user user1 and map the home directory of the user to /home/user1.

useradd passwd

3. Assign sudo access to start / stop the Apache server, and the commands: make, gcc, chmod, and chown., type the commands.

# visudo

i. In the last line, add the user1 to the sudo list to run apachectl start / stop as shown below:

%user1 ALL=(ALL) NOPASSWD:/home/user1/KonyEMM/apache/bin/apachectl %user1 ALL=(ALL) NOPASSWD:/usr/bin/make %user1 ALL=(ALL) NOPASSWD:/usr/bin/gcc %user1 ALL=(ALL) NOPASSWD:/bin/chmod %user1 ALL=(ALL) NOPASSWD:/bin/chown

Sudo entries for make, gcc, chmod, and chown must be commented or removed from sudoers list after installation.

ii. Save the changes and quit the visudo.

Note: In the above example, "/home/user1/KonyEMM" is used as the EMM installation location. If this folder path is different in your case, use the appropriate path.

4. Log in as user1 and then type the command: sudo -l

# su - user1 $ sudo -1 Matching Defaults entries for user1 on this host: requiretty, env_reset, env_keep="COLORS DISPLAY HOSTNAME HISTSIZE INPUTRC KDEDIR LS_COLORS MAIL PS1 PS2 QTDIR USERNAME LANG LC_ADDRESS LC_CTYPE LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES LC_ MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME LC_ALL LANGUAGE LINGUAS _XKB_CHARSET XAUTHORITY"

User user1 may run the following commands on this host:

(ALL) NOPASSWD: /home/user1/KonyEMM/apache/bin/apachectl (ALL) /usr/bin/make

(ALL) /usr/bin/gcc

(ALL) NOPASSWD: /bin/chmod

(ALL) NOPASSWD: /bin/chown

5. Ensure to increase the Open File descriptor and max user process for user1.

If the current value for any parameter is higher than the value listed in this installation document, then do not change the value of that parameter.

To change the Open File descriptor and max user process, follow these steps:

a. Log in as root.

b. Open the /etc/security/limits.conf file in vi editor by executing the command:

$ vi /etc/security/limits.conf

c. Append the following lines at the end of the line:

@user1 hard nofile 65535 @user1 soft nofile 4096 @user1 hard nproc 16384 @user1 soft nproc 2047

d. Save and quit the vi editor.

e. Restart the system after making changes. You can validate the above changes with the command "ulimit -a" running from user1 system login.

6. Ensure that Java is installed. To install Java, follow the procedure:

a. Create a directory /data/downloads

mkdir /data/downloads

b. Download Java version JDK 1.8.0_xx or latest. Also create another directory /usr/java. Download Java 8 from Oracle website. If the internet is available on the current server, execute the following command:

#curl -L --cookie "gpw_e24=http%3A%2F%2Fwww.oracle.com" http://download.oracle.com/otn-pub/java/jdk/7u51-b13/jdk- 7u51-linux-x64.tar.gz -o /tmp/jdk-7u51-linux-x64.tar.gz

c. Log in as root and run the following commands:

# cd /data/downloads mkdir -p /usr/java # cp jdk-7u51-linux-x64.tar.gz /usr/java # cd /usr/java/ # tar -xvzf jdk-7u51-linux-x64.tar.gz

d. Update the bash profile. For example, user1.

vi /home/user1/.bash_profile

e. Go to the end of the bash profile file and append the following Java path :

export JAVA_HOME=/usr/java/jdk1.7.0_51 export JRE_HOME=/usr/java/jdk1.7.0_51 export PATH=$JAVA_HOME/bin:$PATH

f. To verify, log in as user1 and execute the following command:

java -version

7. Ensure Android SDK is installed. To download the Android SDK, use the following link. Navigate to the Kony Management section and click on the specific release related files you want to download. For example, if you want to download Kony Management 3.0, click on the Kony v3.0 GA tab.

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

a. Extract android-sdk-linux.tar.gz in /data folder. (The size is approximately 5 GB) For your reference the installation folder name is provided.

$ su - user1 $ cd /data $ tar –xvzf android-sdk-linux.tar.gz $ md5sum android-sdk-linux.tar.gz

b. Add Android SDK variables to .bash_profile as shown below:

$ vi /home/user1/.bashrc Example: Assuming that Android SDK is available in /data directory export PATH=/data/android-sdk-linux:$PATH export PATH=/data/android-sdk-linux/platform-tools:$PATH

Important: If you want to update your existing Android SDK, navigate to /tools and execute command ./android update sdk --no-ui. The system prompts you to accept the Google license agreement. Enter 'Y' to continue. Android updates. Go to step d to confirm Android SDK availability.

c. To verify aapt, execute the o command aapt.

$ aapt Android Asset Packaging Tool Usage: aapt l[ist] [-v] [-a] file.{zip,jar,apk} List contents of Zip-compatible archive. aapt d[ump] [--values] WHAT file.{apk} [asset [asset Android Asset Packaging Tool Usage: aapt l[ist] [-v] [-a] file.{zip,jar,apk} List contents of Zip-compatible archive. aapt d[ump] [--values] WHAT file.{apk} [asset [asset ...]] badging Print the label and icon for the app declared in APK. permissions Print the permissions from the APK. resources Print the resource table from the APK. configurations Print the configurations in the APK. xmltree Print the compiled xmls in the given assets. xmlstrings Print the strings of the given compiled xml assets. aapt p[ackage] [-d][-f][-m][-u][-v][-x][-z][-M AndroidManifest.xml] \ [-0 extension [-0 extension ...]] [-g tolerance] [-j jarfile] \

[--debug-mode] [--min-sdk-version VAL] [--target-sdk-version VAL] \ [--app-version VAL] [--app-version-name TEXT] [--custom- package VAL] \ [--rename-manifest-package PACKAGE] \ [--rename-instrumentation-target-package PACKAGE] \ [--utf16] [--auto-add-overlay] \ [--max-res-version VAL] \ [-I base-package [-I base-package ...]] \

[-A asset-source-dir] [-G class-list-file] [-P public- definitions-file] \ [-S resource-sources [-S resource-sources ...]] \ [-F apk-file] [-J R-file-dir] \ [--product product1,product2,...] \ [-c CONFIGS] [--preferred-configurations CONFIGS] \ [raw-files-dir [raw-files-dir] ...] \ [--output-text-symbols DIR]

------output truncated------

d. To confirm Android SDK availability for user1, execute the command aaptas shown below:

cd /data/android-sdk-linux/platform-tools ln -s ../build-tools/18.0.0/aapt aapt ln -s ../build-tools/18.0.0/dx dx Where 18.0.0 refers to the latest SDK. Change the number for newer versions.

4.5.2 Database User

A database user should exist with DBA privileges for your Database (MySQL/Oracle/Microsoft SQL server).

Provide user the privilege to create another user. You can revoke this privilege once the installtaion is done. For more information on how to create DB users and how to provide privileges to them, contact your database administrator.

l MySQL

l Microsoft SQL Server

l Oracle

4.5.2.1 MySQL Database

This user is leveraged by the installer to run scripts relating to EMM. After a successful EMM installation, you may revoke these super user privileges.

To create a MySQL database user for installer, follow these steps:

1. Use MySQL client tool to create a database user (for your reference it is termed as DB Client. Use this username while providing inputs for the JDBC installer) with MySQL root user. For example, on a linux shell, invoke MySQL client tool with following command:

mysql -h localhost -u root -p

Example output:

# mysql -h localhost -u root -p

Enter password:

Welcome to the MySQL monitor. Commands end with ; or \g.

Your MySQL connection id is 3

Server version: 5.5.32 MySQL Community Server (GPL)

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective

owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql>

2. Grant all the privileges to create EMM databases and its respective objects (Tables, Indexes, Views, Procedures, Sequences, and Triggers).

CREATE USER 'dbclient'@'' IDENTIFIED BY ''; grant all on *.* to 'dbclient'@'' identified by '';

Note: The should be based on your standards. Installer machine IP has to be granted access to MySQL server with above statements.

4.5.2.2 Microsoft SQL Database

The steps to follow before running the database scripts packaged along with the installer for EMM are mentioned below:

1. Microsoft SQL Server database version 2008 or 2012 needs to be installed with basic setup on the intended machine (use this machine's IP address while providing inputs for the JDBC installer).

2. Use SQL Server Management Studio to enable database server authentication to SQL Server and Windows authentication mode.

3. Use SQL Server Configuration Manager and set the SQL Browser service start mode to automatic or manual, and then start the service.

4. In TCP/IP properties, enable TCP/IP protocols for a port in both Protocol/IP Addresses tabs (use this port on the installer while providing inputs for the JDBC installer) of the database server to accept the database connections.

Note: For installer, it is suggested that the database should be on a remote server or separated from Middleware server (also installer machine). Middleware should be able to communicate to database through TCP/IP.

5. Use SQL Server Management Studio to create a database user with SQL server authentication to connect to SQL Server instance with server role as dbcreator,public. At this point of time no databases are created and installer will create necessary databases, schemas and all other objects. The created user owns all of KonyOne databases and schemas. The user is privileged to create databases and schemas, Tables, Indexes, Views, Procedures, Sequences, Trigger and can also provide the respective grants. For example: dbclient. Use this user while providing inputs for the JDBC installer.

Note: The can be as per your standards.

Make sure to provide all the above values in the respective parameters of the installer.

4.5.2.3 Oracle Database

As part of prerequisites for Oracle database, you need to create tablescape, create a user with some privilages and map the created user with tablespace.

To perform Oracle prerequsites,

1. Using an SQLPlus or another Database client, connect to you Oracle database as Sysdba.

2. Create three tablescape (emm_data, emm_index, and emm_lob_data) by executing the command below

CREATE TABLESPACE EMM_DATA DATAFILE '/emm_ data.dbf' SIZE 2048M AUTOEXTEND ON NEXT 100M MAXSIZE 5120M;

CREATE TABLESPACE EMM_INDEX DATAFILE '/emm_ index.dbf' SIZE 2048M AUTOEXTEND ON NEXT 100M MAXSIZE 5120M;

CREATE TABLESPACE EMM_LOB_DATA DATAFILE '/emm_ lob_data.dbf' SIZE 2048M AUTOEXTEND ON NEXT 100M MAXSIZE 5120M;

3. Create a new user with DBA privilages by executing the command below

CREATE USER

IDENTIFIED BY

DEFAULT TABLESPACE EMM_DATA

TEMPORARY TABLESPACE TEMP

PROFILE DEFAULT;

GRANT CREATE SESSION,RESOURCE,CREATE USER TO with admin option;

Note: In case your organization does not want to provide DB privilages to this user, provide the user, Create Session, Connect (a role), and Create User privilages.

4. Map the user with tablespaces by execuitng the command below

ALTER USER QUOTA UNLIMITED ON EMM_DATA;

ALTER USER QUOTA UNLIMITED ON EMM_INDEX;

ALTER USER QUOTA UNLIMITED ON EMM_LOB_DATA;

4.6 Network-Related Prerequisites

4.6.1 Port Configurations

We recommend the following firewall settings for a successful EMM installation.

4.6.1.1 Firewall Settings required for EMM Server

Firewall settings of EMM Server are defined in the tabular format given below: