Kony Mobilefabric Sync Weblogic Installation

Kony MobileFabric™ Sync Installation - Manual - WebLogic On-Premises

Release 7.2

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.

October, 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.

Revision History

Date Document Description of Modifications/Release Version

10/19/2016 1.3 Document updated for release 7.2

07/13/2016 1.2 Appended new topic Upgrading WebLogic Manually from 7.0.x to 7.1.x.

Document release for 7.1.

05/12/2016 1.1 Removed Download files section in Deploying Kony Sync Server and Upgrade sections.

02/26/2016 1.0 Document for Release 7.0. Appended steps for Upgrading WebLogic manually from 6.0.x / 6.5.x to 7.0.x.

Table of Contents

1. Preface 6

1.1 Purpose 6

1.2 Intended Audience 6

1.3 Formatting conventions used in this guide 6

1.4 Contact Us 8

2. Prerequisites 9

2.1 Hardware Requirements (per physical instance) 9

2.2 Software System Requirements (per physical instance) 10

2.3 Create a WebLogic Domain 10

2.4 Configure MobileFabric Sync Middleware Home 10

3. Deploying Kony MobileFabric Sync Server 11

3.1 Create SyncConsole Database 11

3.2 Setting up Sync Home Directory 12

3.3 Adding Messages Factory Class (Linux) 14

3.4 Creating Data Source for SyncConsole 14

3.5 Configuring Connection Pool Settings for SyncConsole DataSource 22

3.6 Configuring Sync Console JNDI and Hibernate Dialect 26

3.7 Deploying SyncConsole WAR File 29

3.8 Deploying SyncService WAR File 36

4. Upgrading WebLogic Manually from 5.5.x / 5.6.x to 6.5.x 44

4.1 How to Upgrade Kony MobileFabric Sync 44

5. Upgrading WebLogic Manually from 6.x / 6.5.x to 7.x 47

5.1 How to Upgrade Kony MobileFabric Sync 47

6. Upgrading WebLogic Manually from 7.0.x to 7.1.x 50

6.1 How to Upgrade Kony MobileFabric Sync 50

7. Appendix: Upgrading the WebLogic Server to Support Java 1.8 59

8. Appendix: Setting Up Multiple Sync Home Directories 61

1. Preface

Kony MobileFabric Sync product has two important components - Kony MobileFabric Sync Management Console and Kony MobileFabric Sync Services. These two applications and corresponding database schema run on various platforms such asTomcat Apache, WebLogic and WebSphere and the database such as MS SQL Server, Oracle, MySQL, and PostgreSQL.

Important: Kony recommends using the MobileFabric Installer for deploying MobileFabric 7.0 onwards.

If you are required to install MobileFabric manually due to your business rules and policies, please contact [email protected] for approval and to obtain access to the MobileFabric manual install artifacts. Manual installs not approved by Kony will not be supported.

1.1 Purpose

This document provides instructions for installing and configuring Kony MobileFabric Sync Server using WebLogic.

1.2 Intended Audience

This document is intended for Administrators and Developers responsible for installing and configuring Kony MobileFabric Sync Server. It is assumed that the reader of this document is familiar with deploying software on Java application servers/WebLogic application server and installing database software

1.3 Formatting conventions used in this guide

The following formatting conventions are used throughout the document:

Convention Explanation

Monospace n User input text, system prompts and responses

n File Path

n Commands

n Program Code

n File Names

Italic n Emphasis

n Names of Books and Documents

n New Terminology

Bold n Windows

n Menus

n Buttons

n Icons

n Fields

n Tabs

URL Active link to a URL

Note: Provides helpful hints or additional information

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

1.4 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 product line, contact [email protected].

2. Prerequisites

Read this section to understand the system requirements before installing and configuring Kony MobileFabric Sync Server. You need to ensure that the below software is installed on the machine on which you want to install Kony MobileFabric Sync.

2.1 Hardware Requirements (per physical instance)

Component Specification per Instance

Standard Standard QA or Standard Development Certification Production Environment Environment Environment

Windows Windows Server 2008 Windows Server 2008 Windows Server 2008 Operating / Windows 8 / Windows 8 / Windows 8 System Professional / Professional / Professional / Windows 7 Windows 7 Windows 7 Professional, 64 bit, 4 Professional, 64 bit, 4 Professional, 64 bit, 4 Cores Cores Cores

Linux Red Hat Linux Red Hat Linux Red Hat Linux Operating Enterprise 6.0, 64 bit, Enterprise 6.0, 64 bit, Enterprise 6.0, 64 bit, System 4 Cores 4 Cores 4 Cores

Minimum 8 GB or more 16 GB or more 32 GB or more Recommended RAM

Minimum 40 GB or more 40 GB or more 80 GB or more Recommended Hard Disk Space

For detailed information on hardware requirements, refer to Kony MobileFabric Sync Server Installation Options section of Kony MobileFabric Sync On-Premises Server Planning Guide.

2.2 Software System Requirements (per physical instance)

For software system requirements, click here.

2.3 Create a WebLogic Domain

Create a new domain using WebLogic Configuration Wizard or use default domain (base_domain) to deploy Kony MobileFabric Sync Server.

2.4 Configure MobileFabric Sync Middleware Home

Configuring the MobileFabric Sync Middleware home on WebLogic where MobileFabric (with integrated server) installed, includes the following steps:

1. Deploy the MobileFabric Sync on same WebLogic where Kony MobileFabric (with integrated server) installed.

2. Configure -D parameter for sync middleware home pointing to the existing MobileFabric middleware home created while installing MobileFabric.

For example: Add the -Dsync.home= parameter for sync middleware home.

3. Deploying Kony MobileFabric Sync Server

You have to perform the following procedures to deploy Kony MobileFabric Sync Server:

1. Creating SyncConsole Database

2. Setting up Sync Home Directory

3. Adding Messages Factory Class (Linux)

4. Creating Data source for SyncConsole

5. Configuring Connection Pool Setting for SyncConsole Datasource

6. Configuring Sync Console JNDI and Hibernate Dialect

7. Deploying synconsole.war

8. Deploying syncservice.war

3.1 Create SyncConsole Database

Run the downloaded Sync Console script file for each database from your server. It creates syncconsole database.

For example

l For MS SQL Server: console-schema-sqlserver.sql

l For My SQL Server: console-schema-mysql.sql

l For Oracle Server: console-schema-oracle.sql

l For Postgre SQL Server: console-schema-postgresql.sql

l For DB2 Server: console-schema-db2.sql

To execute database scripts using flyway command-line tool, refer Configuring Flyway Command-line Tool section in the MobileFabric Manual Install Guide.

3.2 Setting up Sync Home Directory

Note: To setup multiple sync home versions on the same directory skip the below steps and refer Setting Up Multiple Sync Home Directories.

To set up Sync home directory, follow these steps:

1. Create a folder in your directory structure (For example: D:\Kony\KonySync in Windows, /Kony/KonySync in Linux) and assume it as sync.home.

2. Create a conf directory under it.

3. Extract the PropertyFiles.zip to the conf directory. The following files appear:

l console-log4j.properties

l services-log4j.properties

l synclicense.properties

l syncconsole.properties

l syncservice.properties

4. Create the directory structure, middleware/middleware-bootconfig under sync.home, and place an empty file with name middleware.properties.

5. Configure sync.home and middleware.home as JVM argument below including memory settings.

l Windows:

Add the below line in startWebLogic.cmd under the bin directory of your WebLogic domain

(For Example: C:\Oracle\Middleware\user_projects\domains\base_ domain\bin) as follows:

(Approx Line No: 171)

set JAVA_OPTIONS=%JAVA_OPTIONS% - Dsync.home="D:\Kony\KonySync" -Dmiddleware.home="D:\Kony\KonySync" -Xms512m -Xmx1024m - XX:PermSize=256m -XX:MaxPermSize=256m

l Linux:

Add the below line in startWebLogic.sh under the bin directory of your WebLogic domain

(For Example: /opt/Oracle/Middleware/user_projects/domains/base_ domain/bin) as follows:

(Approx Line No: 171)

set JAVA_OPTIONS=$JAVA_OPTIONS -Dsync.home="/Kony/KonySync" -Dmiddleware.home="/Kony/KonySync" -Xms512m -Xmx1024m - XX:PermSize=256m -XX:MaxPermSize=256m

l WebLogic Managed Servers:

For managed servers, you should configure sync.home and middleware.home from WebLogic console shown in the below tab.

3.3 Adding Messages Factory Class (Linux)

You must add the following parameter in startWeblogic.sh file for WebLogic in Linux environment.

(Approx Line No: 172) - after sync.home parameters line,

JAVA_OPTIONS="$JAVA_OPTIONS - Djavax.xml.soap.MessageFactory=weblogic.xml.saaj.MessageFactoryImpl"

Note: You need the above workaround to resolve the below error in WebLogic with Kony MobileFabric Sync war files.

"java.lang.UnsupportedOperationException: This class does not support SAAJ 1.1"

3.4 Creating Data Source for SyncConsole

You must create a data source for Sync console.

To create a data source for Sync Console, follow these steps:

1. Start WebLogic for your domain.

2. Go to WebLogic Administration Console > Services > Data Sources.

3. Click New > select Generic Data Source.

The Create a New JDBC Source page appears.

4. Type name of the data source and jdbc/ConsoleDB as JNDI name.

For example:

l For MS SQL Server, select MS SQL Server as Database type

l For Oracle, select Oracle as Database type

l For DB2, select DB2 as Database type

l For MySQL, select MySQL as Database type

l For PostgreSQL, select PostgreSQL as Database type

5. Click Next to select Database Driver.

l For MS SQL Server, select Oracle’s MS SQL Server Driver (Type 4) Versions:Any driver

l For Oracle Server, select Oracle's Driver (Thin) for Instance Connections: Versions: Any driver

l For DB2 Server, select Oracle’s DB2 Driver (Type 4) Versions:Any driver

l For MySQL Server, select MySQL’s Driver (Type 4) Versions:using com.mysql.jdbc.Driver driver

l For PostgreSQL Server, select PostgreSQL’s Driver (Type 4) Versions:Any driver

6. Click Next and retain the default values.

7. Click Next and provide SyncConsole database details.

8. Click Next. The Test Configuration dialog appears.

9. Click Test Configuration to test syncconsole database connection.

10. Click Next and select the AdminServer check box.

11. Click Finish. A successful message appears.

3.5 Configuring Connection Pool Settings for SyncConsole DataSource

You must configure connection pool settings for Sync console data source.

To configure connection pool settings, follow these steps:

1. Open WebLogic Administration Console.

2. Go to Services > Data Sources > click ConsoleDS. The Data source Settings screen appears.

3. Click the Configuration tab > Connection Pool tab. The Connection pool details appear.

4. Modify the Initial Capacity, Maximum Capacity and Minimum Capacity values as per requirement .

Note: The points 5,6 and 7 are applicable only if you are using Oracle as Console DB and provide SYSTEM as database name in Creating Datasource for SyncConsole.

5. Click Advanced option. The Advanced details section appears.

6. Enter the following code in Init SQL textbox.

SQL ALTER SESSION SET CURRENT_SCHEMA=syncconsoleweblogic

Where syncconsoleweblogic is the syncconsole name provided during the setup of Console DB.

7. Click Save to update the changes.

8. Restart the server for the changes to take effect.

3.6 Configuring Sync Console JNDI and Hibernate Dialect

Configure SyncConsole data source JNDI name and Hibernate dialect class name in synccosole.properties under \conf directory.

l The JNDI name must match the JNDI name that you created in Creating Datasource for SyncConsole.

l You must configure the dialect name for SQL Server as below:

#Sync Console configuration properties file

############################################################### ###### #Hibernate Dialect related properties. # # # #For SQL Server#

#hibernate.dialect=com.kony.sync.console.dialect.CustomSQLServe rDialect # # # #For MySQL #

#hibernate.dialect=com.kony.sync.console.dialect.CustomMySQLDia lect# # # #For Oracle thin driver #

#hibernate.dialect=com.kony.sync.console.dialect.CustomOracleDi alect#

############################################################### ######

hibernate.dialect= com.kony.sync.console.dialect.CustomSQLServerDialect

#SyncConsole JNDI Name syncconsole.jndi.name=jdbc/ConsoleDB

############################################################### ########## #LDAP settings ldap.enabled=false #Open Ldap connection settings open.ldap.url=ldap://10.10.18.55:389/dc=maxcrc,dc=com open.ldap.userDn=cn=manager,dc=maxcrc,dc=com

open.ldap.password= #ADS connection settings ads.ldap.url=ldap://platformtest.kony.internal:389/

ads.ldap.url.doamin=ldap://platformtest.kony.internal:389/DC=pl atformtest,DC=kony, DC=internal ads.ldap.domain=platformtest.kony.internal [email protected] ads.ldap.password= ads.ldap.referral=follow

############################################################### ###### ##hibernate c3p0 properties connection.provider_ class=org.hibernate.connection.C3P0ConnectionProvider hibernate.c3p0.min_size=5 hibernate.c3p0.max_size=20 hibernate.c3p0.timeout=300 hibernate.c3p0.max_statements=50 hibernate.c3p0.idle_test_period=3000

############################################################### ######

l Retain other properties with default values.

3.7 Deploying SyncConsole WAR File

You must deploy the Syncconsole.war file.

To deploy the syncconsole.war file, follow these steps:

1. Go to WebLogic Admin Console > Deployments > click Install to deploy sync console application.

The Install Application Assistant appears.

2. Click upload your file (s) link.

3. Browse to select the syncconsole.war as the deployment archive and click Next.

4. Select the uploaded syncconsole.war option and click Next.

5. Select the Install this deployment as an application option and click Next.

6. Retain the default application name as syncconsole and click Next.

7. Retain the default values and click Finish.

8. Review syncconsole deployment details and click the Testing tab to test the deployment of the war file.

9. Click default url to view the syncconsole application. The Kony MobileFabric Sync Management Console login page appears.

3.8 Deploying SyncService WAR File

You must deploy syncservice.war file.

To deploy syncservice.war file, follow these steps:

1. Go to WebLogic Admin Console > Deployments > click Install to deploy syncservice application.

The Install Application Assistant appears.

2. Click upload your file (s) link. The Upload a Deployment to the admin server page appears.

3. Browse to select syncservice.war as deployment archive and click Next.

4. Select the uploaded syncservice.war and click Next.

5. Select the Install this deployment as an application option and click Next.

6. Retain the application name as syncservice and click Next.

7. Retain the default values and click Finish.

8. Review the syncservice deployment details and click the Testing tab.

9. Click the default URL to test and view the syncservice application. The Sync Services Test Page appears.

4. Upgrading WebLogic Manually from 5.5.x / 5.6.x to 6.5.x

Kony MobileFabric Sync Framework is a comprehensive synchronization platform that enables developers to add synchronization capabilities to mobile applications. Assume that you have prior installation of Kony MobileFabric Sync. This topic talks about manually upgrading Kony MobileFabric Sync Framework without an installer.

4.1 How to Upgrade Kony MobileFabric Sync

The manual upgrade of Kony MobileFabric Sync includes the following steps:

1. Upgrade Sync Console Database

2. Upgrade Property Files

3. Upgrade WAR Files

4. Verify MobileFabric Sync Version

4.1.1 Upgrade Sync Console Database

1. Extract the alter_scripts zip file.

2. The extracted folder contains the alter scripts for the respective databases used.

For example: If you are using MS SQL Server, use script file names such as console- schema-alter –sqlserver-x.x.x.sql, the version of the script is x.x.x.

4.1.1.1 Executing Alter Script Files

If you are upgrading MobileFabric Sync Server from x to y (excluding version x scripts), execute all available alter scripts from x to y in ascending order. If there are no alter scripts in between two versions, then there is no need to upgrade the database.

Example:

1. If you are upgrading Sync Server from version 6.0 to 6.5, use the following alter scripts, if there are any.

l console-schema-alter-mysql-6.0.1.sql

l console-schema-alter-mysql-6.0.2.sql

l console-schema-alter-mysql-6.0.3.sql

l console-schema-alter-mysql-6.0.5.sql

4.1.2 Upgrade Property Files

To upgrade property files in MobileFabric Sync Server, follow these steps:

1. Extract the properties zip file.

2. Navigate to \conf directory, and compare the existing syncconsole.properties file with downloaded property files.

l If there are any modifications in the files, copy the modifications to the existing property files.

Note: Do not change any path in existing property files installed as per the earlier setup (for example, logs file path in log4j properties files).

4.1.3 Upgrade WAR Files

To upgrade the WAR files:

1. Setup a backup of old WAR files.

2. Uninstall the existing WAR file and install the new WAR files.

4.1.4 Verify MobileFabric Sync Version

To verify if you have upgraded Kony MobileFabric Sync version correctly, log on to Sync Console and click Configuration. The Configuration Details screen appears.

The MobileFabric Sync version upgrade details will be updated against the property value of Kony MobileFabric Sync version.

5. Upgrading WebLogic Manually from 6.x / 6.5.x to 7.x

5.1 How to Upgrade Kony MobileFabric Sync

The manual upgrade of Kony MobileFabric Sync includes the following steps:

1. Upgrade Sync Console Database

2. Upgrade Property Files

3. Upgrade WAR Files

4. Verify MobileFabric Sync Version

5.1.1 Upgrade Sync Console Database

1. Extract the alter_scripts zip file.

2. The extracted folder contains the alter scripts for the respective databases used.

For example: If you are using MS SQL Server, use script file names such as console- schema-alter –sqlserver-x.x.x.sql, the version of the script is x.x.x.

5.1.1.1 Executing Alter Script Files

Example:

1. If you are upgrading Sync Server from version 6.5 to 7.0, use the following alter scripts, if there are any.

l console-schema-alter-mysql-6.5.sql

l console-schema-alter-mysql-7.0.sql

5.1.2 Upgrade Property Files

To upgrade property files in MobileFabric Sync Server, follow these steps:

1. Change the following DB related parameters in upgrade scripts and run the script.

l replicadatabase.host

l replicadatabase.port

l replicadatabase.instance

l replicadatabase.user

l replicadatabase.password

l uploaddatabase.host

l uploaddatabase.port

l uploaddatabase.instance

l uploaddatabase.user

l uploaddatabase.password

l org.quartz.jobStore.driverDelegateClass

l syncservices.jndi.prefix

2. Extract the properties zip file.

3. Navigate to \conf directory, and compare the existing syncconsole.properties file with downloaded property files.

l If there are any modifications in the files, copy the modifications to the existing property files.

Note: Do not change any path in existing property files installed as per the earlier setup. Make sure the same JNDI file name in old properties is present in updated properties file.

5.1.3 Upgrade WAR Files

To upgrade the WAR files:

1. Setup a backup of old WAR files.

2. Uninstall the existing WAR file and install the new WAR files.

5.1.4 Verify MobileFabric Sync Version

To verify if you have upgraded Kony MobileFabric Sync version correctly, log on to Sync Console and click Configuration. The Configuration Details screen appears.

The MobileFabric Sync version upgrade details will be updated against the property value of Kony MobileFabric Sync version.

6. Upgrading WebLogic Manually from 7.0.x to 7.1.x

Kony MobileFabric Sync Framework is a comprehensive synchronization platform that enables developers to add synchronization capabilities to mobile applications. This topic talks about manually upgrading Kony MobileFabric Sync Framework on WebLogic server from 7.0.x to 7.1.x without an installer.

6.1 How to Upgrade Kony MobileFabric Sync

The manual upgrade of Kony MobileFabric Sync includes the following steps:

1. Downloading the Required Files

2. Upgrade MobileFabric Sync Console Database

3. Upgrade Property Files

4. Upgrade WAR Files

5. Verifying the MobileFabric Sync Version

Note: You must stop the WebLogic server before you start upgrading Kony MobileFabric Sync.

6.1.1 Download the Required Files

If you are required to install/upgrade MobileFabric manually due to your business polices, please contact [email protected] for approval and to obtain access to the MobileFabric manual install artefacts.

Important: Manual installs not approved by Kony will not be supported.

6.1.2 Upgrade the MobileFabric Sync Console Database

1. Extract the syncconsole- zip file. For information on Downloading DB_scripts, refer section Download the Required Files

2. The extracted folder contains the upgrade scripts for the respective databases used.

6.1.2.1 Executing Upgrade Script Files

If you are upgrading Sync Server from its current version to newer version, execute all available upgrade scripts between two versions in ascending order.The extracted upgrade scripts will be used to update the sync console schema from 7.0.x GA to 7.1.0.x GA. They are to be run using flyway software. For updating the extracted scripts, follow these steps:

1. Download the flyway software from http://flywaydb.org/getstarted/download.html

2. Extract the flyway folder (flyway-commandline-4.0.1-windows-x64.zip) to find flyway-4.0.1.

3. Copy the scripts from sync-7.0.x\sync\syncconsole- to flyway-4.0.1/sql folder.

4. Set the following properties in flyway configuration file flyway.conf under flyway-

4.0.1/conf.

a. Set the below properties based on the syncconsole db machine.

flyway.url= flyway.user= flyway.password= flyway.schemas=

flyway syntax: MSSQL flyway.url=jdbc:sqlserver://;databaseName= flyway.user= flyway.password= If you don’t specify schema name, by default DBO will be considered as schema name.

MYSQL flyway.url=jdbc:mysql://: flyway.user= flyway.password= flyway.schemas=

Oracle flyway.url=jdbc:oracle:thin:/ flyway.user= flyway.password= flyway.schemas=

DB2

flyway.url=jdbc:db2://:/ flyway.user= flyway.password= flyway.schemas=

b. We have to set the 7.0.0 schema as baseline for flyway. To do that set the below flyway properties:

flyway.baselineVersion=7.0.0 flyway.baselineDescription=V7_0_0__syncconsole-.sql flywaybaselineOnMigrate=true

c. Set the placeholder value for SYNC_LOG_LOCATION (With this, you will be able to generate the logs at specified location).

flyway.placeholders.KONY_SYNC_LOG_LOCATION=

d. Set the placeholder value for SYNC_LOG_OPTION. It will have two values.

l logfile - logs will get stored into files

l database - logs will get stored into database

flyway.placeholders.KONY_SYNC_LOG_OPTION=

5. Open command prompt under flyway folder flyway-4.0.1 and run the below commands:

l flyway baseline

l flyway migrate

6.1.2.2 Creating a Table space

1. If you are using DB2 as syncconsole database then you need to create a tablespace before running the 7.1.0 script.

a. Create the Big tablespace with big bufferpool of 32K page size. Only DB2 database administrator (DBA) or equivalent DB user will have access to create database with default tablespace with particular pagesize/bufferpool. In DB2, whenever Binary Large Object (BLOB) and Character Large Object (CLOB) are used, you need to have the database created with default tablespace as well as default temp tablespace with big pagesize of 32k.

b. To create a LOB tablespace

CREATE LARGE TABLESPACE IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 32

PREFETCHSIZE AUTOMATIC BUFFERPOOL BIGBUFFERPOOL OVERHEAD 7.5 TRANSFERRATE 0.06 AUTORESIZE YES INITIALSIZE 32M NO FILE SYSTEM CACHING; COMMIT;

CREATE SYSTEM TEMPORARY TABLESPACE "BIGTEMP" IN DATABASE PARTITION GROUP IBMTEMPGROUP PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE USING STOGROUP IBMSTOGROUP EXTENTSIZE 1M PREFETCHSIZE AUTOMATIC BUFFERPOOL BIGBUFFERPOOL; COMMIT; CONNECT RESET;

c. To create an index tablespace

CREATE LARGE TABLESPACE IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 32 PREFETCHSIZE AUTOMATIC BUFFERPOOL BIGBUFFERPOOL OVERHEAD 7.5 TRANSFERRATE 0.06 AUTORESIZE YES INITIALSIZE 32M NO FILE SYSTEM CACHING; COMMIT;

d. To create a tablespace for tables and Data

CREATE LARGE TABLESPACE IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 32

PREFETCHSIZE AUTOMATIC BUFFERPOOL BIGBUFFERPOOL OVERHEAD 7.5 TRANSFERRATE 0.06 AUTORESIZE YES INITIALSIZE 32M NO FILE SYSTEM CACHING; COMMIT;

e. Replace with your actual database name.

CONNECT TO ; CREATE BUFFERPOOL BIGBUFFERPOOL IMMEDIATE ALL DBPARTITIONNUMS SIZE AUTOMATIC NUMBLOCKPAGES 100 BLOCKSIZE 100 PAGESIZE 32K; COMMIT;

2. If you are using ORACLE as syncconsole database, follow the below steps:

a. Create the following three tablespaces. These tablespaces will be used to move already created MF database objects which were placed in default USERS tablespace

l Tables and data tablespace: MF_DATA

l Index tablespace: MF_INDEX

l Lob tablespace: MF_LOB_DATA

b. You can create these 3 tablespaces in the following way:

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

l Replace the with actual data file path on the Oracle database server.

l Create three tablescapes (MF_DATA, MF_INDEX, and MF_LOB_DATA) by

executing the command below (you need to grant create tablespace privilege to ).

CREATE TABLESPACE MF_DATA DATAFILE '/MF_DATA_01.DBF' SIZE 2048M AUTOEXTEND ON NEXT 100M MAXSIZE 5120M; CREATE TABLESPACE MF_INDEX DATAFILE '/MF_INDEX_01.DBF' SIZE 2048M AUTOEXTEND ON NEXT 100M MAXSIZE 5120M; CREATE TABLESPACE MF_LOB_DATA DATAFILE '/MF_LOB_DATA_01.DBF' SIZE 2048M AUTOEXTEND ON NEXT 100M MAXSIZE 5120M;

l Provide quota on all the above 3 tablespaces (MF_DATA, MF_INDEX and MF_ LOB_DATA tablespaces) to MF database user. Map the with all the 3 tablespaces by executing the command below.

ALTER USER QUOTA UNLIMITED ON MF_ DATA; ALTER USER QUOTA UNLIMITED ON MF_ INDEX; ALTER USER QUOTA UNLIMITED ON MF_LOB_ DATA;

6.1.3 Upgrade Property Files

Note: You need to stop the WebLogic server before you start upgrading Kony MobileFabric Sync.

To upgrade property files in Sync Server, follow these steps:

1. Extract the Properties zip file that is downloaded in the section Download the Required Files.

2. Navigate to \conf directory, and replace the existing property files with downloaded property files.

Note: Make sure you are retain the property syncservices.jndi.prefix from the old syncconsole.properties file.

6.1.4 Upgrade WAR Files

To upgrade the WAR files, follow these steps:

1. Take the syncconsole.war and syncservice.war from the downloaded artifacts.

2. Take the backup of old WAR files.

3. Uninstall the existing WAR fileas from Home\weblogic\standalone\deployments and install the new WAR files syncconsole.war and syncservice.war.

4. Start the WebLogic server and perform sync sanity on the upgraded server.

6.1.5 Verify MobileFabric Sync Version

To verify if you have upgraded Kony MobileFabric Sync version correctly, log on to Sync Console, and click Configuration. The Configuration Details screen appears.

The MobileFabric Sync version upgrade details will be updated against the property value of Kony MobileFabric Sync version.

7. Appendix: Upgrading the WebLogic Server to Support Java 1.8

To upgrade the WebLogic Server to support JDK 1.8, follow these steps:

1. Install Oracle 12.1.3, and point JAVA_HOME to JDK 1.8.

Note: The Oracle version must be 12.1.3 or higher to support JDK1.8 during installation.

2. Set JAVA_HOME to JDK 1.8 in environment variables.

1. Go to the domain in which deployments are done.

Example: %WL_HOME%\wls12130\user_projects\domains\base_ domain\bin\setDomainEnv (.cmd file for Windows, .sh for Linux).

3. Edit the setDomainEnv file,

l If the Java vendor is JRockit, search for BEA_JAVA_HOME and set to Java 1.8.

l If the Java vendor is Sun, search for SUN_JAVA_HOME and set to Java 1.8.

l If the Java vendor is Oracle, search for JAVA_HOME and set to Java 1.8.

l Run the WebLogic server.

8. Appendix: Setting Up Multiple Sync Home Directories

MobileFabric Sync can now run multiple Sync versions on the same application server.

To set up multiple sync home directories, follow these steps:

1. Set the sync.home as an app-level variable instead of JVM parameter(-D).

For more information on setting the Sync home in a JVM parameter, refer Configuring Sync Home as JVM Property.

2. Add sync.home in the context parameter of the web.xml file by entering the following code:

Sample Context param in web.xml: sync home path sync.home C:/Kony/KonySync

Note: This preceding code should be entered in the web.xml file of the syncconsole.WAR and syncservice.WAR files, and manually deployed. For more information on deploying the WAR files, refer to Deploying SynConsole WAR File and Deploying SyncService WAR Files.