KMF Integration Service - Manual Upgrade: Upgrading Kony MobileFabric Integration Service > WebLogic > Upgrade WebLogic Manually from 5.6.x to 6.5.x

Upgrade WebLogic Manually from 5.0.x/5.5.x / 5.6.x to 6.5.x

This section provides you the steps to upgrade Kony MobileFabric Integration Service manually from 5.0.x/5.5.x / 5.6.x to 6.5.x (WebLogic). Assume that you have prior installation of Kony MobileFabric Integration Service.

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 middleware.ear metrics.ear (applicable only for metrics)	WAR and EAR files	To be deployed to Application Server
middleware-bootconfig.tar	TAR files

Backup

To backup files, follow these steps:

Stop the application server.
Take a backup of the following files from your current server installation location.
1. The files:
  - middleware.ear
  - admin.war
  - reports.war
2. middleware-bootconfig directory
  Sample path for middleware -bootconfig <middleware-home>\middleware\middleware-bootconfig>
3. After taking the backup, delete all the above files.

Database Upgrade for Legacy Reports

Download and run the upgrade scripts from http://developer.kony.com/KonyDBScripts to upgrade the database and enable legacy reports.

For example: If your database version is 5.0.3 Oracle, run the schemas in "Oracle_upgrade_5.0.3 to 5.0.6" folder in the numerical order.

Note: To enable the legacy reports, the database should be the latest 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.

Execute Database Scripts

To execute the database scripts downloaded in the prerequisites step, follow these steps:

Execute the database scripts from downloaded artifacts and verify that new Admin and Reports schema created in the database.
Note: This is required for new metrics.
Note: Change the names of Kony Admin and Kony Reports as per your requirements in the SQL files downloaded in the Prerequisites step.
In Konyadmin DB, add the following entries into mobilefabric_configuration table
- management_server_hostname with your WebLogic administration console IP
- management_server_port with WebLogic administration console port
- management_server_username with WebLogic Username
- management_server_password with WebLogic Password
- management_server_groups with the name of the cluster or servers to which the apps should be deployed when published from IDE separated by comma.

Add New and Update Existing Property Files

middleware-bootconfig of 6.5.x is bundled with few additional .properties files compared to earlier versions that are required during the upgrade process. You would also need few .properties files from your backup location.

To add new and update existing property files, follow these steps:

Download and extract the middleware-bootconfig.tar file downloaded in step 2b from Prerequisites section, to the <middleware-home>\middleware directory.
The following new property files extracted are applicable only for metrics
1. metrics-log4j.properties in the middleware-bootconfig folder that is available under middleware home.
2. admin-log4j.properties and serverconsole.properties in the admin folder available under middleware-bootconfig.
Retain deployment-config.properties from your backup location <middleware-bootconfig>\admin to <middleware-home\middleware\middleware-bootconfig\admin>.
Retain the changes made to middleware.properties or middleware-log4j.properties files for previous version.
Update existing property files:
1. Update the middleware.properties file from <middleware-home>\middleware\middleware-bootconfig with the following content as per your requirement.
2. Comment out the JBoss JMS Properties and uncomment the WebLogic JMS Properties.
Copy the appregistry folder of middleware-bootconfig from the previous version to the new extracted middleware-bootconfig folder.

Note: You must replace the credentials and IP addresses according to your environment.

##################################################
#Metrics Topic Configuration (applicable only for metrics)
##################################################

#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

#For JBOSS JMS
metrics.initialContextFactoryName=org.jboss.naming.remote.client.
#InitialContextFactory
#metrics.providerURL=remote://<ipaddress:port>

#For Weblogic JMS
#metrics.initialContextFactoryName=weblogic.jndi.
 WLInitialContextFactory
#metrics.providerURL=remote://<ipaddress:port>

#START- JBoss 6.2 EAP Additional Properties
metrics.securityPrincipalName=admin
metrics.securityCredentials=admin123
metrics.userName=admin
metrics.password=admin123
#END- JBoss 6.2 EAP Additional Properties

#metrics.URLPkgPrefixes=jboss.naming:org.jnp.interfaces 
#NOTE: failoverDuration and failoverRetries introduced for kony middleware 
(not defined by log4j) 
#metrics.FailoverDuration=5000 
#metrics.FailoverRetries=3

Note: From 6.0.3.3 GA, metrics.logging flag is available and by default, it is set to true. Prior to that, below error is displayed (you can ignore this). ERROR-logservice.JMSLogService - Error while look up topic.

Note: If we set metrics.logging property to false, call the kony.license.disableMetricReporting() API in app init to disable “Maximum Offline Sessions Exceeded” alert.

Open serverconsole.properties file and make the following changes based on your database type.

Note: Uncomment the properties according to your database type and comment the else for hibernate Dialect properties. For Database type enter the db type as shown.

#Server Console configuration properties file 
#Hibernate Dialect related properties. 
#For SQL Server
#konyadmindb.dialect=com.kony.console.admin.dialect.CustomSQLServerDialect

#For MySQL
#konyadmindb.dialect=com.kony.console.admin.dialect.CustomMySQLDialect

#For Oracle thin driver
#konyadmindb.dialect=com.kony.console.admin.dialect.CustomOracleDialect

#For DB2
#konyadmindb.dialect=com.kony.console.admin.dialect.CustomDB2Dialect
#konyadmindb.dialect=com.kony.console.admin.dialect.CustomMySQLDialect

#Admin and Report Database JNDI Names
admindb.jndi.name=jdbc/konyadmindb
reportsdb.jndi.name=jdbc/konyreportsdb

#Database Type (mysql/oracle/sqlserver/db2)
admindb.dbtype=mysql
reportsdb.dbtype=mysql

Open middleware-log4j.properties file from middleware-home\middleware\middleware-bootconfig> and edit as following.

Note: You must replace the credentials and IP addresses according to your environment.

jms.logging=true (Change this value to false if old reports and JMS topic is configured or 
to be configured) 

#Enable the below statements if reporting is enabled and JMS topic is configured. 
#log4j.category.com.konylabs.middleware.connectors.logservice=INFO,jms
#log4j.additivity.com.konylabs.middleware.connectors.logservice=FALSE
#Provide the location of the log file to be logged
#LOG4J.appender.file.FILE=<middleware-home>\logs\middleware.log

Update Data Source Configuration (Applicable Only For Metrics)

To update the data source configuration, follow these steps:

Setup Kony Admin Data Source
1. In Administration Console, select Services > Data Sources from the left menu.
2. Click New to add a new data source name.
3. Provide the following information:
  - Data source name: konyadmindb
  - JNDI Name: jdbc/konyadmindb
4. Click Next to continue.
5. Select the database driver.
6. Enter the following connection properties
  - Database name
  - Host Name
  - Port
  - Database Username and Password (Username is the Admin db name created after running the database scripts for new schema).
7. Click Next to continue.
8. Select the appropriate cluster or server as the target of the data source.
9. Click Finish to create a data source for the given details.
Setup Kony Reports data source.
1. In Administration Console, select Services > Data Sources from the left menu.
2. Click New.
3. Enter the following information
  - Data source name: konyreportsdb
  - JNDI Name: jdbc/konyreportsdb
4. Click Next to continue.
5. Select the database driver.
6. Enter the following connection properties
  - Database name
  - Host name
  - Port
  - Database Username and Password (Username is the Reports DB created after running the database scripts for new schema)
7. Click Next to continue.
8. Select the appropriate cluster or server as the target of the data source.
9. Click Finish to create a data source for the given details.

Update JMS Configuration (Applicable Only For Metrics)

Note: If JMS is already configured in the previous version, update the JMS configuration with the below update steps.

To update JMS Configuration, follow these steps:

In Administration Console, select Services > Messaging > JMS Modules from the left menu.
Open the System module created from the previous version.
Click New to create a new JMS System Module Resource.
Select the Topic option and click Next.
Enter the name and JNDI name as KonyMetricsTopic and click Next.
Select the sub-deployment created while configuring the previous version from the drop-down and click Finish.
Repeat the above steps for all the System Modules configured.

Note: To configure JMS Server and Module for Metrics (if not used previously), refer Configure JMS Server.

Deploy the latest .WAR Files

To deploy the latest WAR files, follow these steps:

Deploy the latest admin.war, middleware.ear and metrics.ear (applicable only for metrics) files to the application server from the Deployments tab of WebLogic Administration console and provide the target as the cluster or servers in which Kony MobileFabric Integration Service is configured.
Extract the jar files available in libraries-MIDDLEWARE-QA-ver.tar to this location - \<Installation-location>\install\lib\middleware.

Important: Start the server or cluster from the Servers tab under Environments in the left menu of the Administration Console.

Kony Report Portal Configuration

If you are using the Kony Reporting Portal for tracking sessions and users, then you must make the following changes so that you continue to see the reports in the new Admin Console (under the section Reports > Legacy Reports).

To track sessions and users, follow these steps:

Place the following files in <middleware-home>\Konyreports\home. These files are available in the 5.x installation under reports_config folder:
- DbSpecificProcedureCall.properties
- konyreport.properties
- log4j.properties
In the Server Start tab of the server in WebLogic Administrator console, provide the location where the files are placed-Dkonyreports.home=<The directory location>.

Verification

Verify the upgrade process by logging into the console and look for Server Version and Health Check. Use version.html for verification.

To verify the upgrade process, follow these steps:

Navigate to the URL http://ipaddress:port/middleware/version.html and look for server version.
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.

Navigate to Settings and click Configuration.