Upgrading Integration Service on WebSphere. On-Premises

Kony MobileFabric 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. 2016 by Kony, Inc. All rights reserved 1 of 69

Copyright 2014 by Kony, Inc. All rights reserved. January, 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. 2016 by Kony, Inc. All rights reserved 2 of 69

Table of Contents 1. Preface 6 1.1 Deployment Configuration Models 7 1.2 Purpose 7 1.3 Intended Audience 8 1.4 Formatting conventions used in this guide 8 1.5 Related Documents 9 1.6 Contact Us 10 2. Upgrade Manually from 11 2.1 Prerequisites 11 2.2 Backup 11 2.3 Database Upgrade for Legacy Reports 12 2.4 Execute Database Scripts 12 2.5 Upgrading middleware.ear 13 2.6 Upgrading admin.war 21 2.7 Upgrading Metrics (logdaemon) 39 2.8 Verify the Upgrade Process 62 3. Upgrade Manually from 6.x to 6.5.x 64 3.1 Prerequisites 64 3.2 Backup 64 3.3 Execute Database Scripts 65 2016 by Kony, Inc. All rights reserved 4 of 69

1. Preface 1. Preface Kony Platform provides an integrated approach to mobile application design, development and management. This facilitates mobile applications development independent of any specific device, and delivery in different formats that run on all the major device platforms. Kony Platform consists of three main components: Kony Studio: Designs and develops mobile applications. Kony MobileFabric Integration Service: Provides server-side functionality for the applications, common data integration and device support services. Client Runtime: Component for each major device platform that enables the same mobile application to execute directly on each mobile device. Kony MobileFabric Integration Service The application functionality developed and generated by Kony Studio is enabled and delivered using Kony MobileFabric Integration Service. The SMS and Mobile Web channels are hosted on Kony MobileFabric Integration Service and the Native Apps binaries are deployed to the Server, to be downloaded by the mobile device. Kony MobileFabric Integration Service has the following capabilities: A sophisticated device database that enables it to detect and deliver the appropriate binary to the appropriate requesting device. Built-in back-end data services integration capabilities, with out-of-the-box support for Web Services, XML feeds and HTML extraction. Integration with optional third party connector libraries that offers access to a large number of ERP, databases, and legacy systems. Built-in usage tracking and analysis capabilities that provide a wide range of reports on system and application use. 2016 by Kony, Inc. All rights reserved 6 of 69

1. Preface 1.1 Deployment Configuration Models You can use the following Deployment Configuration model for your multi-node environment. This model has multiple Kony Reporting Agents. Note: If Kony reporting is not required then JMS, Kony Reporting Agents and Log Database are not required to be configured. You can go with file logging instead. 1.2 Purpose This document provides upgrading instructions for Kony MobileFabric Integration Service on, and supporting software packages. 2016 by Kony, Inc. All rights reserved 7 of 69

1. Preface 1.3 Intended Audience This document is intended for engineers or system administrators who are responsible for upgrading Kony MobileFabric Integration Service on. It is assumed that the reader of this document is familiar with deploying software on Java application/ application servers. The reader must understand how to install the database software. 1.4 Formatting conventions used in this guide Following are the formatting conventions used throughout the document: Conventions Explanation Monospace User input text, system prompts, and responses File path Commands Program code File names Italic Emphasis Names of books and documents New terminology 2016 by Kony, Inc. All rights reserved 8 of 69

1. Preface Conventions Explanation Bold Windows Menus Buttons Icons Fields Tabs 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.5 Related Documents Document Kony Database Setup Guide (Oracle/MySQL/DB2/MSSQL) Kony Studio Installation Guide Kony Studio User Guide Kony Widget User Guide Kony API Reference Guide Kony MobileFabric Integration Service Troubleshooting Guide 2016 by Kony, Inc. All rights reserved 9 of 69

1. Preface 1.6 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. 2016 by Kony, Inc. All rights reserved 10 of 69

2. Upgrade Manually from 2. Upgrade Manually from This section provides you the steps to upgrade Kony MobileFabric Integration Service manually from 5.6.x to 6.0.x (). Assume that you have prior installation of Kony MobileFabric Integration Service. 2.1 Prerequisites The following table displays the prerequisites for upgrading Kony MobileFabric Integration Service. Refer to http://community.kony.com/downloads/manual to download the following artifacts of <<GA- 6.X.Y.Z>/Middleware/>: Artifacts Type Purpose Respective Database scripts Database Scripts To setup the required schema /admin.war Metrics/metrics.ear WAR and EAR files To be deployed to Application Server middlewarebootconfig.tar TAR files 2.2 Backup To backup the existing files, follow these steps: 1. Take a backup of existing middleware.ear and admin.war files from your current installation server. These files are located at < installation location>/<node cell>. For example, data/ibm//appserver/profiles/appsrv01/installedapps/local 2016 by Kony, Inc. All rights reserved 11 of 69

2. Upgrade Manually from hostnode01cell. 2. Also, take the backup of existing shared-lib and middleware-bootconfig folders. 2.3 Database Upgrade for Legacy Reports Note: This section is applicable only for upgrading from 5.5.x to 6.x. To upgrade the database for legacy reports, follow the below step: 1. Download the upgrade scripts from the http://developer.kony.com/konydbscripts location. 2. Run all the downloaded scripts. Note: To enable the legacy reports, the database should be the 5.0.6. version. If your database is not latest, run the database scripts based on your database and upgrade to 5.0.6 version. For example, if your database version is 5.0.3 Oracle, run the schemas in the Oracle_upgrade_ 5.0.3 to 5.0.6 folder in the numerical order. 2.4 Execute Database Scripts Execute the database scripts and verify the Admin and Reports schema created in the database Note: Change the name of the konyadmin and konyreports database as per your requirements. This is required for metrics. 2016 by Kony, Inc. All rights reserved 12 of 69

2. Upgrade Manually from 2.5 Upgrading middleware.ear 2.5.1 Add New and Update Existing Property Files Extract the middleware-bootconfig.tar file to a temporary location (/home/temp) in your local machine. Here after, /home/temp location is referred as <temp> in this guide. Retain the changes made in middleware.properties and middlewarelog4j.properties files as in 5.6.x for your configuration details. To retain the changes, follow these steps: 1. Open the <middleware-home>/middlewarebootconfig/middleware.properties file of 5.6.x and add the below code at the end of the file. You can also find this code in the middleware.properties file available at the <temp>/middleware-bootconfig. ################################################## #Metrics Topic Configuration ################################################## #To enable/disable metrics #Make it true, if Kony Reports enabled and Metrics Topic is configured metrics.logging=true metrics.topicname=jms/konymetricstopic metrics.topicconnectionfactoryname=jms/konyconnectionfactory ##-- START - Should be enabled only on Websphere JMS Server metrics.initialcontextfactoryname==com.ibm.websphere.naming.wsn InitialContextFactory 2016 by Kony, Inc. All rights reserved 13 of 69

2. Upgrade Manually from metrics.providerur=iiop://localhost:2809 ##-- END - Should be enabled only on Websphere JMS Server #Account ID and Environment ID for Reports KONY_ACCOUNT_ID=Kony ENVIRONMENT_ID=Dev Note: From 6.0.3.3 GA onwards, metrics.logging flag is available and by default, it is set to true. Prior to that, below error statement is displayed. You can skip this. Note: If the metrics.logging property is set to false, call the kony.license.disablemetricreporting() API in app init to disable Maximum Offline Sessions Exceeded alert. ERROR-logservice.JMSLogService - Error while lookup Topic 2. Open <middleware-home>/middleware-bootconfig/middlewarelog4j.properties file of 5.6.x and add the below code at the end of the file. You can also find this code in the middleware-log4j.properties file available at the <temp>/middleware-bootconfig. #-- Start add for service wars deployed log4j.category.com.kony=error,file #-- End log4j.category.com.konylabs=error,file log4j.appender.file=org.apache.log4j.rollingfileappender log4j.appender.file.maxfilesize=10240kb log4j.appender.file.maxbackupindex=5 log4j.appender.file.file=/home/core/install/logs/middleware.log log4j.appender.file.threshold=debug 2016 by Kony, Inc. All rights reserved 14 of 69

2. Upgrade Manually from log4j.appender.file.layout=org.apache.log4j.patternlayout # %L should be used only in dev, its extremely slow #log4j.appender.file.layout.conversionpattern=[%x] %d{absolute} %5p %c{2}:%l - %m%n log4j.appender.file.layout.conversionpattern=[%x][konyserver] [%p][%d{dd MMM yyyy HH:mm:ss,SSS}]-%5p-%c{2} - %m%n #jms.loggging is used for kony reporting validation. Make it true, if kony reporting is enabled and jms topic is configured jms.logging=false Note: Below set of properties are required for 6.5 and above. If your middleware version is prior to 6.5, skip the below steps. log4j.additivity.com.konylabs.middleware.services.logobservers. DevicePayloadLogger=false log4j.logger.com.konylabs.middleware.services.logobservers.devi cepayloadlogger=off,device log4j.appender.device=org.apache.log4j.rollingfileappender log4j.appender.device.maxfilesize=10240kb log4j.appender.device.maxbackupindex=50 log4j.appender.device.file=/home/core/install/logs/devicepayload.log log4j.appender.device.layout=org.apache.log4j.patternlayout log4j.appender.device.layout.conversionpattern=%n[%d{dd MMM yyyy HH:mm:ss,SSS}]:[%x]:%m log4j.additivity.com.konylabs.middleware.services.logobservers. DatasourcePayloadLogger=false log4j.logger.com.konylabs.middleware.services.logobservers.data sourcepayloadlogger=off,datasource log4j.appender.datasource=org.apache.log4j.rollingfileappender log4j.appender.datasource.maxfilesize=10240kb 2016 by Kony, Inc. All rights reserved 15 of 69

2. Upgrade Manually from log4j.appender.datasource.maxbackupindex=50 log4j.appender.datasource.file=/home/core/install/logs/datasour ce-payload.log log4j.appender.datasource.layout=org.apache.log4j.patternlayout log4j.appender.datasource.layout.conversionpattern=%n[%d{dd MMM yyyy HH:mm:ss,SSS}]:[%x]:%m 3. Replace the old <middleware-home>/middlewarebootconfig/tc/devicedetectionlogic.xml file with new one available at the <temp>/middleware-bootconfig. Note: If your environment is Cluster, repeat the above steps for all members of Cluster. For example, if there are three members in Cluster and each member has separate middleware.home; so above steps need to be performed in each middleware.home. 2.5.2 Add or Update the middleware shared libraries This section provides you steps to creating and updating the shared libraries in. After downloading following files of 6.x from community portal to your local machine, extract them. shared-libraries-was.tar shared-libraries-was8.tar 2016 by Kony, Inc. All rights reserved 16 of 69

2. Upgrade Manually from 2.5.2.1 Create Shared Libraries in 1. Open the Websphere Administration console. 2. In the left pane, click Environment>Shared libraries. The Shared Libraries page opens. 3. Under Scope section, select the desired server from the drop-down list. If your environment is Cluster, select scope as cell (cells:plqa1was-1cell03). If your environment is single node, select scope as server (Node=XXXXNode01, Server=server1). 4. Under Preferences, click New. A new page opens to define shared library. 5. In the Name box, type a name for shared library. For example, shared-libraries-was. 6. In the Description box, provide description for the shared library. For example, Shared libraries (Optional). 2016 by Kony, Inc. All rights reserved 17 of 69

2. Upgrade Manually from 7. In the Classpath box, provide the path of the folder where shared-libraries-was.tar is extracted. For example, /data/middleware_installable_dirs/sharedlibraries-was. 8. Do not select the Class Loading check box. 9. Click OK and click Save to save the details in master configuration. 2.5.2.2 Update Shared Libraries in You can update the shared libraries that are already created. For example, as you have already created the shared-libraries-was8.x shared library for HTTP related jars, you can just replace old jars with new set of jars. For this shared library, you need to select the Class Loading check box. It is recommended to create separate shared libraries for each application. For more information on creating shared libraries, see Create Shared Libraries. Note: If your environment is Cluster, make sure that all shared libraries are defined in cell scope. This cell has DMGR configured. 2.5.3 Deploy middleware.ear 1. Open the Websphere Administration console. 2. In the left pane, click Applications>Application Types> enterprise applications. 3. Select the check box of existing middleware application and click Uninstall. If middleware.ear was already uninstalled, skip steps 1 and 2. 2016 by Kony, Inc. All rights reserved 18 of 69

2. Upgrade Manually from 4. Click Install to deploy new middleware.ear. The Preparing for the application installation page opens. 5. Click Local file system and then click Choose File to browse and select the middleware.ear file from local machine. (or) Click Remote file system if middleware.ear was downloaded to remote system and browse for middleware.ear file. 6. Click Next. 7. In the How do you want to install the application section, click Detailed - Show all installation options and parameters and continue clicking Next till you reach Map modules to servers. 8. Select check box and select target. For example, if your environment is Cluster, select target as desired cluster. If your environment is single node, select target as desired server. 2016 by Kony, Inc. All rights reserved 19 of 69

2. Upgrade Manually from 9. Continue clicking Next till you reach Map Shared libraries step. The Install New Application page opens. 10. Select the application, click the shared library references hyperlink. 2016 by Kony, Inc. All rights reserved 20 of 69

2. Upgrade Manually from 11. Map the shared libraries for the selected application and click OK. 12. Continue clicking Next till you reach Summary page. Click Finish and then Save to save the details to master configuration. 2.6 Upgrading admin.war This section provides procedures for following: 2016 by Kony, Inc. All rights reserved 21 of 69

2. Upgrade Manually from Create Datasource for admin Update Existing Property Files Kony Legacy Report Portal Configuration for 6.x Deploy admin.war of 6.x Note: You can skip upgrading admin.war if you are not using admin and metrics. Metrics has to be deployed on single node, which should not be part of Cluster. 2.6.1 Prerequisites For upgrading admin.war, you need to upgrade the database from 5.6.x to 6.x (DB2). You can set up the database by executing the following scripts, which are downloaded from community portal. konyadmin-<db-name>.sql Schema/konyreports-<db-name>.sql After execution of these scripts, spool files are created at script locations. You can use these spool files to verify the smooth execution of the script files. To set up the database, follow these steps: 1. Log on to DB2 Server with appropriate credentials. 2. Test the database connection using the DB2 command line utility: db2 db2=> connect to KONYDB user dbclient using <password> 3. Execute the konyadmin-<db-name>.sql file. This script creates konyadmin database objects in KONYADMIN schema. 2016 by Kony, Inc. All rights reserved 22 of 69

2. Upgrade Manually from cd <Files_location> db2 -td';' -vf konyadmin-<db-name>.sql > 00_konyadmin_spool.log 4. Execute the konyreports-<db-name>.sql file. This script creates konyreports database objects in KONYREPORTS schema. db2 -td';' -vf konyreports-<db-name>.sql > 01_konyreports_ spool.log 2.6.2 Create Datasource for admin and reports (DB2) Creating Datasource process involves following steps: 1. Defining DB2 Provider 2. Configuring datasource 2.6.2.1 Define DB2 Provider 1. Open the Websphere Administration console. 2. In the left pane, click Resources>JDBC> JDBC Provider. The JDBC Provider page opens. 3. Under Scope section, select the desired option from the drop-down list. For example, for Cluster, select scope name as cell(cells:plqa1was-1cell03). In this cell, DMGR is available. For single node, select scope name as node (Node=XXXXNode01). 4. Under Preferences, click New. The Create a new JDBC Provider page opens. 5. Select the following options: Database Type: DB2 Provider Type: DB2 Universal JDBC Driver Provider 2016 by Kony, Inc. All rights reserved 23 of 69

2. Upgrade Manually from Implementation Type: Connection pool data source Note: By default, Name field is populated as DB2 Universal JDBC Driver Provider (Optional). 6. Click Next. Note: If you need to use custom or updated DB2 Jars, then update: DB2UNIVERSAL_ JDBC_DRIVER_PATH and DB2UNIVERSAL_JDBC_DRIVER_ NATIVEPATH 7. Ensure that DB2 driver files, db2jcc.jar and db2jcc_license_cu.jar are downloaded and copied to the file system - /opt/db2jars. 8. Click Next. Verify the implementation class name on Summary page and click Finish. Set up user credentials for JNDI database connection 1. Open the Websphere Administration console. 2. In the left pane, click Security>Global Security. The Global Securitypage opens. 3. In the Authentication section, select Java Authentication And Authorization Service>J2C Authentication Data. 4. In the page that appears, click New. 5. Provide the following details to connect to Oracle database: Alias: konyauth Userid: dbclient Passwd: <Password> 6. Click OK and save the configuration. 2016 by Kony, Inc. All rights reserved 24 of 69

2. Upgrade Manually from 2.6.2.2 Configure Admin and Reports Datasource 1. Open the Websphere Administration console. 2. In the left pane, click Resources>JDBC> Data sources. The Data sourcespage opens. 3. Under Scope section, select the desired option from the drop-down list. For example, for Cluster, select scope name as cell (cells:plqa1was-1cell03). In this cell, DMGR is available. For single node, select scope name as node (Node=XXXXNode01). 4. Under Preferences, click New. The Create a data source page opens. 5. Provide the following details: Datasource Name: konyadmindb JNDI Name: jdbc/ konyadmindb (The same JNDI name should be configured in serverconsole.properties file) 6. Click Next. 7. Select an existing JDBC provider. Here it is DB2 Universal JDBC Driver Provider (created in previous step). 8. Click Next. 9. Provide following details: Database Name: KONYDB (the database is created using schema script initially) Port Number: Type your database port number. For example, 50000 Server Name: Type your database host name or IP address and click Next. The Setup 2016 by Kony, Inc. All rights reserved 25 of 69

2. Upgrade Manually from security aliases page opens. 10. Select JAAS J2C Authentication Data here. 11. Set up security aliases as following: Component-managed authentication alias: XXXNode01/dbclient. Mapping configuration alias: Default Principal Mapping. Container-managed authentication alias: XXXNode01/ dbclient. 12. Click Next, verify the changes and Click Finish. 13. Similarly, add another datasource repeating steps 1-12, but with following details: Name: konyreportsdb JNDI Name: jdbc/konyreportsdb 2016 by Kony, Inc. All rights reserved 26 of 69

2. Upgrade Manually from 15. Under Additional Properties section, click Custom properties>currentschema. The currentschema page opens. 16. In the Value box, type KONYREPORTS and click OK. Note: This value refers to reports schema name. 17. Click Save to save directly to master configuration. 18. Click Resources>JDBC>DataSources. 2016 by Kony, Inc. All rights reserved 28 of 69

2. Upgrade Manually from 20. Under Additional Properties section, click Custom properties>currentschema. The currentschema page opens. 21. In the Value box, type KONYADMIN and click OK. Note: This value refers to admin schema name. 22. Click Save to save directly to master configuration. 23. Restart the Websphere application server to changes take effect. 2016 by Kony, Inc. All rights reserved 30 of 69

2. Upgrade Manually from 2.6.3 Add New and Update Existing Property Files 2.6.3.1 Add serverconsole.properties file 1. Copy the serverconsole.properties file from <temp>/middlewarebootconfig/admin to the existing middleware-bootconfig/admin folder. 2. Update the below properties in the serverconsole.properties file. ############################################################### ########## #Admin and Report Database JNDI Names ############################################################### ########## admindb.jndi.name=jdbc/konyadmindb reportsdb.jndi.name=jdbc/konyreportsdb ############################################################### ########## #Database Type (mysql/oracle/sqlserver/db2) ############################################################### ########## admindb.dbtype=db2 reportsdb.dbtype=db2 #For DB2 konyadmindb.dialect=com.kony.console.admin.dialect.customdb2dia lect 2.6.3.2 Updating admin-log4j.properties file 1. Replace the existing <middleware-home>/middlewarebootconfig/admin/admin-log4j.properties file with the new one. The new admin-log4j.properties file is located at <temp>/middlewarebootconfig/admin. 2016 by Kony, Inc. All rights reserved 31 of 69

2. Upgrade Manually from 2. Open the admin-log4j.properties file and update following property: log4j.appender.file.file=/home/middleware/logs/admin.log 2.6.4 Kony Legacy Report Portal Configuration If you are using the Kony Reporting Portal for tracking sessions and users, you must make the following changes so that you continue to see the reports in the new Admin Console (under Reports > Legacy Reports in admin console). Note: If you have not configured reports home for your server, add D parameter of reports home to your server. For example, DkonyReports.home=/data/config Note: If your environment is Cluster, make sure that you have configured konyreports.home for all members of cluster. 2016 by Kony, Inc. All rights reserved 32 of 69

2. Upgrade Manually from Make sure that following files are available in reports home. For example, /data/config. DbSpecificProcedureCall.properties konyreport.properties log4j.properties Make sure that below property value was set properly in the konyreports.properties file. 2016 by Kony, Inc. All rights reserved 33 of 69

2. Upgrade Manually from #database properties konyadminreports.jndi.name=jdbc/kardb 2.6.5 Deploy admin.war 1. Open the Websphere Administration console. 2. In the left pane, click Application>Application Types> enterprise Applications. The Enterprise Applicationspage opens. 3. Select existing admin application and click Uninstall. Note: If admin.war was already uninstalled, skip step 3. 4. Click Install to deploy new admin.war. 5. Click Local file system and then click Choose File to browse and select the admin.war file from local machine. (or) Click Remote file system if admin.war was downloaded to remote system and browse for admin.war file. 6. Click Next. The Preparing for the application installation page opens. 7. Select Detailed - Show all installation options and parameters and click Next. The Application Security Warnings page opens, click Continue. This opens a page with 11 steps. 2016 by Kony, Inc. All rights reserved 34 of 69

2. Upgrade Manually from 9. Step 2: Map modules to servers, Map the Server Console module to your desired server or cluster and click Next. 10. Step 3: Provide JSP reloading options for Web modules, leave default values and click Next. 11. Step 4: Map shared libraries, map previously created shared library, shared-libraries-was, shared-libraries-was8.x to both Application (admin_war) and Module (Server Console). The 2016 by Kony, Inc. All rights reserved 36 of 69

2. Upgrade Manually from Shared library references page opens. 12. Select application and click Reference shared libraries button. The Shared Library Mapping page opens. 13. Select your shared library from Available box and move it to Selected box using arrow keys provided and click OK. 14. Similarly, Go to Shared Library Mapping page, select module and click Reference shared libraries button, and repeat step 13 to map shared libraries. 2016 by Kony, Inc. All rights reserved 37 of 69

2. Upgrade Manually from Note: You cannot map both application and module simultaneously. 15. Step 5: Map shared library relationships, leave default values and click Next. 16. Step 6: Map virtual hosts for Web modules, map your virtual host (default_host) to module and click Next. 17. Step 7: Map context roots for Web modules, select Context Root value as /admin and click Next till you reach Summary page. 18. Step 11: Summary, review summary and click Finish. 2016 by Kony, Inc. All rights reserved 38 of 69

2. Upgrade Manually from 19. Wait till you get application installed successfully message. 20. Click Save to save to master configuration. 21. Click Applications>Application Types>Websphere enterprise applications. 22. Select the admin_war application and click Start. 2.7 Upgrading Metrics (logdaemon) metrics.ear is a new application developed in 6.x that supports same features as logdaemon and reports of 5.6.x. Note: Stop existing logdaemon process and deploy metrics.ear application for 6.x version. Note: metrics.ear should be deployed only on single server. 2016 by Kony, Inc. All rights reserved 39 of 69

2. Upgrade Manually from 2.7.1 Configure JMS 2.7.1.1 Create bus 1. Open the Websphere Administration console. 2. In the left pane, click Service integration>buses. The Buses page opens. 3. Click New to create new bus. The Create a new Service Integration bus page opens. 4. In the Enter the name for your new bus box, type a name for the bus and click Next. 2016 by Kony, Inc. All rights reserved 40 of 69

2. Upgrade Manually from 2.7.1.2 Adding a new Bus Member 1. Click on previously created bus that is, serverbus. The serverbus page opens. 2. Under the Topology section, click the Bus members link. 3. Click Add to add bus members. The Add a new bus member page opens. 2016 by Kony, Inc. All rights reserved 42 of 69

2. Upgrade Manually from 4. Step 1: Click Server, select desired server (for example, server1) from the drop-down box, and click Next. 5. Step 1.1: Select the type of message store as File Store and click Next. 6. Step 1.2: Configure the file store, do not change the default values and click Next. 7. Step 1.3: Do not change the default heap sizes and click Next. 8. Step 2: Verify the complete summary and click Finish. 2016 by Kony, Inc. All rights reserved 43 of 69

2. Upgrade Manually from 2. Under the Destinations resources section, click the Destination link. The Destinations page opens. 3. Click New. The Create a new destination page opens. 4. Click Topic Space and click Next. The Create new topic space page opens. 2016 by Kony, Inc. All rights reserved 45 of 69

2. Upgrade Manually from 5. In the Identifier box, type KonyMetricsTopic. 6. In the Description box, type description for the new topic space and click Next. The Confirm topic space creation page opens. 7. Verify the details and click Finish. 8. Click Save to save directly to the master configuration. 2016 by Kony, Inc. All rights reserved 46 of 69

2. Upgrade Manually from 2.7.1.4 Creating Topic connection factories 1. Open the Websphere Administration console. 2. In the left pane, click Resources>JMS>Topic connection factories. The Topic connection factories page opens. 3. Click New. 4. Select JMS rosource provider as Default messaging provider and click OK. 5. Provide the following details: Name: KonyMetricsTopicCF Jndi name: jms/konyconnectionfactory 2016 by Kony, Inc. All rights reserved 47 of 69

2. Upgrade Manually from Bus name: serverbus 6. Click Save to save directly to the master configuration. 2.7.1.5 Creating Topic 1. Open the Websphere Administration console. 2. In the left pane, click Resources>JMS>Topics. The Topics page opens. 2016 by Kony, Inc. All rights reserved 48 of 69

2. Upgrade Manually from 3. Click New. 4. Select JMS rosource provider as Default messaging provider and click OK. 5. Provide following details: Name: KonyMetricsTopic Jndi name: jms/konymetricstopic Bus name: serverbus 2016 by Kony, Inc. All rights reserved 49 of 69

2. Upgrade Manually from 6. Click Save to save directly to the master configuration. 2.7.1.6 Creating Activation Specifications 1. Open the Websphere Administration console. 2. In the left pane, click Resources>JMS>Activation specifications. The Activation specifications page opens. 3. Click New. 2016 by Kony, Inc. All rights reserved 51 of 69

2. Upgrade Manually from 4. Select JMS rosource provider as Default messaging provider and click OK. 5. Provide following details: Name: KMT Jndi name: jms/kmt Destination type: Topic Destination JNDI name: jms/konymetricstopic 2016 by Kony, Inc. All rights reserved 52 of 69

2. Upgrade Manually from 2.7.2 Configure middleware.home as JVM Property 1. Open the Websphere Administration console. 2. In the left pane, click Servers>Server Types>Webspere application server. The Activation specifications page opens. 3. Select the application server in which you want to install metrics.ear. The selected application server page opens. 4. Under Server Infrastructure section, click Java and Process Management>Process definition. The Process definition page opens. 5. Under Additional Properties section, click the Java Virtual Machine link. 6. In the Generic JVM arguments box, type the middleware.home property with your middleware home path as below (-D must be prefixed). -Dmiddleware.home=/home/core/install 7. Click OK and then Save to save in the master configuration. 2.7.3 Files required in middleware.home Following files need to be updated: middleware.properties metrics-log4j.properties admin/serverconsole.properties 2.7.3.1 Update middleware.properties file 1. Copy the middleware.properties file from <temp>/middleware-bootconfig/ to <middlewarehome>/middleware-bootconfig/ folder. 2016 by Kony, Inc. All rights reserved 54 of 69

2. Upgrade Manually from 2. Open the middleware.properties file and make sure that following properties set to correct value as shown below. ################################################## #Metrics Topic Configuration ################################################## #To enable/disable metrics #Make it true, if Kony Reports enabled and Metrics Topic is configured metrics.logging=true metrics.topicname=jms/konymetricstopic metrics.topicconnectionfactoryname=jms/konyconnectionfactory ##-- START - Should be enabled only on Websphere JMS Server log4j.appender.jms.initialcontextfactoryname=com.ibm.websphere. naming.wsninitialcontextfactory log4j.appender.jms.providerurl=iiop://localhost:2809 ##-- END - Should be enabled only on Websphere JMS Server #Account ID and Environment ID for Reports KONY_ACCOUNT_ID=Kony ENVIRONMENT_ID=Dev 2.7.3.2 Updating metrics-log4j.properties file 1. Copy the metrics-log4j.properties file from <temp>/middleware-bootconfig/ to <middlewarehome>/middleware-bootconfig/ folder. 2. Open the metrics-log4j.properties file and make sure that following property set to correct value as shown below. log4j.appender.file.file=/home/middleware/logs/metrics.log 2016 by Kony, Inc. All rights reserved 55 of 69

2. Upgrade Manually from 2.7.3.3 Updating serverconsole.properties 1. Copy the serverconsole.properties file from <temp>/middlewarebootconfig/admin to <middlewarehome>/middleware-bootconfig/admin folder. 2. Open the serverconsole.properties file and make sure that following properties set to correct value as shown below. ############################################################### ########## #Admin and Report Database JNDI Names ############################################################### ########## admindb.jndi.name=jdbc/konyadmindb reportsdb.jndi.name=jdbc/konyreportsdb ############################################################### ########## #Database Type (mysql/oracle/sqlserver/db2) ############################################################### ########## admindb.dbtype=db2 reportsdb.dbtype=db2 #For DB2 konyadmindb.dialect=com.kony.console.admin.dialect.customdb2dia lect 2.7.4 Deploy metrics.ear 1. Open the Websphere Administration console. 2. In the left pane, click Application>New Application. The New Application page opens. 3. Click New Enterprise Application. 2016 by Kony, Inc. All rights reserved 56 of 69

2. Upgrade Manually from 4. Click Local file system and then click Choose File to browse and select the metrics.ear file from local machine. (or) Click Remote file system if metrics.ear was downloaded to remote system and browse formetrics.earfile. 5. Click Next. The Preparing for the application installation page opens. 6. Click Detailed - Show all installation options and parameters and click Next. The Application Security Warnings page opens and click Continue. 2016 by Kony, Inc. All rights reserved 57 of 69

2. Upgrade Manually from 7. Step 1: Select installation options, change application name if required, leave default values and click Next. 8. Step 2: Map modules to servers, map the metrics module to your selected desired server (for example, server1) if not mapped by default and click Next. 2016 by Kony, Inc. All rights reserved 58 of 69

2. Upgrade Manually from 9. Step 3 : Map shared libraries, map previously created shared library shared-libraries-was, shared-libraries-was8.x to application (metrics.ear). The Shared library reference page opens. 10. Select the application and click Reference shared libraries. The Shared Map libraries page opens. 2016 by Kony, Inc. All rights reserved 59 of 69

2. Upgrade Manually from 11. Select your shared library from Available box and move to Selected box using arrow keys provided. 12. Click OK. 13. If shared libraries are not defined, perform steps in section "Add or Update the middleware shared libraries" on page 16. 14. Step 4: Map shared library relationships, leave default values and click Next. 2016 by Kony, Inc. All rights reserved 60 of 69

2. Upgrade Manually from 15. Step 5: Bind listeners for message-driven beans, select Activation Specification, specify target resource jndi name as jms/kmtand click Next. 16. Step 6: Metadata for modules, leave default values and continue clicking Next till you reach Summary page. 17. Step 8: Summary, review summary and click Finish. 18. Wait till you get application installed successfully message. 2016 by Kony, Inc. All rights reserved 61 of 69

2. Upgrade Manually from 19. Click Save to save directly to master configuration. 20. Restart the Websphere Application Server to take the changes effect. Maker sure that server is started in following order: Metrics server Clustered Middleware 2.8 Verify the Upgrade Process Verification of admin.war Invoke the http://<ipaddress:port>/admin/version.html URL and check the version. In the URL, replace <ipaddress:port> with proper IP address and port number. Verification of middleware.ear Invoke the http://ipaddress:port/middleware/version.html URL and check the version. In the URL, replace <ipaddress:port> with proper IP address and port number. Verification of environment health 2016 by Kony, Inc. All rights reserved 62 of 69

2. Upgrade Manually from This step is required only when you have admin, middleware and metrics in your environment. 1. Log on to the admin console using the following URL and look for Health Check. http://ipaddress:port/admin (replace <ipaddress:port> with proper IP address and port number). 2. Provide admin credentials (default credentials from SQL script are username: admin and password: admin123) to log on to Server Console. 3. Navigate to Settings and click Health Check and look for Report DB, Admin DB and Reporting Queue. Note that the status should be in PASSED state. 2016 by Kony, Inc. All rights reserved 63 of 69

3. Upgrade Manually from 6.x to 6.5.x 3. Upgrade Manually from 6.x to 6.5.x This section provides you the steps to upgrade Kony MobileFabric Integration Service manually from 6.0.x to 6.5.x (). Assume that you have prior installation of Kony MobileFabric Integration Service. 3.1 Prerequisites The following table displays the prerequisites for upgrading Kony MobileFabric Integration Service. Refer to http://community.kony.com/downloads/archive/manual and click Kony MobileFabric. Click Download for Middleware to download the following artifacts of <<GA-6.X.Y.Z>/Middleware/>: Artifacts Type Purpose Respective Database scripts Database Scripts To setup the required schema admin.war middleware.ear WAR and EAR files To be deployed to Application Server metrics.ear (this is required only if you have metrics) middlewarebootconfig.tar shared-libraries-was TAR files shared-libraries-was8.x 3.2 Backup Before taking the backup, Stop the application server. 2016 by Kony, Inc. All rights reserved 64 of 69

3. Upgrade Manually from 6.x to 6.5.x To backup the existing files, follow these steps: 1. Take a backup of existing shared libraries, shared-libraries-was and sharedlibraries-was8 files from the location where you have defined libraries. 2. Take a backup of middleware-bootconfig located at <middleware-homedirectory>/middleware. Note: After taking the backup, delete all the files from the original location. Uninstall previous admin.war, middleware.war and metrics.ear. metrics.ear only in case if you are using metrics. 3.3 Execute Database Scripts 1. Execute all the database upgrade scripts from 6.0.x to 6.5.x. 2. Run the scripts in the sequence specified at the location from where you downloaded the scripts. Below is the screen shot of the scripts specified in a sequence. Replace the name of the konyadmin and konyreports schema names with your respective schema names. 3. Following are the db upgrade scripts for upgrading from 6.0.3.x to 6.5.0.x. 2016 by Kony, Inc. All rights reserved 65 of 69

3. Upgrade Manually from 6.x to 6.5.x 3.4 Add and Update Properties Files 1. Extract the middleware-bootconfig tar to the <middleware-homedirectory>/middleware location. 2. Retain the properties of the admin-log4j.properties and deploymentconfig.properties files located at middleware-bootconfig/admin folder from the respective files of the previous version, which are already backed up. 3. Retain the properties of the middleware.properties and middlewarelog4j.properties files located at middleware-bootconfig folder from the respective files of the previous version which are already backed up. 4. Open the middleware-log4j.properties file and edit the below paths for devicepayload.log and datasource-payload.log as per your requirement. log4j.appender.device.file=${middleware.home} /../logs/middleware/device-payload.log log4j.appender.datasource.file=${middleware.home} /../logs/middleware/datasource-payload.log 5. Copy the appregistry folder from the previous version of middleware-bootconfig (located at <middleware-home-directory>/middleware) to the new middlewarebootconfig folder. If metrics is not used: 6. Open the middleware.properties file located at the middleware-bootconfig folder and mark the property under Metrics Topic Configuration as false. metrics.logging=false 2016 by Kony, Inc. All rights reserved 66 of 69

3. Upgrade Manually from 6.x to 6.5.x Note: This property was introduced in 6.0.3.3.GA version of middleware. This property enables the metrics. Request and Session data is captured in the database if this property is set to true. Note: If the metrics.logging property is set to false, call the kony.license.disablemetricreporting() API in app init to disable Maximum Offline Sessions Exceeded alert. If metrics is used: 7. Open middleware.properties in the middleware-bootconfig folder and mark the property under Metrics Topic Configuration as true. metrics.logging=true 8. Retain the properties in the metrics-log4j.properties file located at the middlwarebootconfig/admin folder, and the serverconsole.properties file located at the middleware-bootconfig folder from the same respective files of previous version which are backed up. 3.5 Deploy Latest Artifacts 1. Deploy the latest admin.war and middleware.ear. Refer to the Deploy admin.war and Deploy middleware.ear. 2. Deploy the latest metrics.ear. Refer to the Deploy metrics.ear. Note: You can skip the step 2 if you are not using metrics. 2016 by Kony, Inc. All rights reserved 67 of 69

3. Upgrade Manually from 6.x to 6.5.x 3. Replace the downloaded shared libraries ( shared-library-was and shared-librarywas8) with the 6.5.x shared libraries. 3.6 Verification Start the application server. Verification of middleware.ear Invoke the http://ipaddress:port/admin/version.html URL and check the version. In the URL, replace <ipaddress:port> with proper IP address and port number. Verification of environment health This step is required only when you have admin, middleware and metrics in your environment. 1. Log on to the admin console using the following URL http://ipaddress:port/admin (replace <ipaddress:port> with proper IP address and port number). 2. Provide admin credentials to log on to Server Console. 3. Navigate to Settings and click Health Check and look for Report DB, Admin DB and Reporting Queue. Note that the status should be in PASSEDstate. 2016 by Kony, Inc. All rights reserved 68 of 69