Open topic with navigation

KMF Integration Service - Manual Upgrade: Upgrading Kony MobileFabric Integration Service > JBoss > Upgrading JBoss Manually 6.0.x / 6.5.x to 7.0.x

Upgrade JBoss Manually from 6.x / 6.5.x to 7.x

This section provides you the steps to upgrade Kony MobileFabric Integration Service manually from 6.x to 7.x on JBoss single node setup.

Prerequisites

The following table displays the prerequisites for upgrading Kony MobileFabric Integration Service. Assuming that you have already installed Kony MobileFabric Integration Service and have setup the required Databases (Reports and Admin).

Artifacts Type Purpose

Respective Database and Flyway scripts

  • Scripts to migrate from 6.x to 6.5.x
  • Scripts to migrate from 6.5.x to 7.x
 Database Scripts To setup the required schema
  • admin.war
  • middleware.war
  • services.war
  • metrics.ear (applicable only for metrics)
 WAR files To be deployed to Application Server
  • Flyway tool
 version 3.2.1 https://flywaydb.org/getstarted/download.html

Backup

  1. Stop JMS and JBoss Middleware server.
  2. Take a backup of the following files. These file are available at <jboss_install-location>/jboss/instance/standalone/deployments
    1. .WAR files
      • middleware.war
      • admin.war
      • services.war
    2. metrics.ear from <jboss-install-location>/jboss62_jms/standalone/deployments (applicable only for metrics).
  3. After taking the backup, delete or uninstall the above files.

Execute Database Scripts

  1. Stop the application server.
  2. Download the respective database scripts of 7.0. Following scripts are downloaded for migrating Admin DB and Reports DB.
    • konyreports-sqlserver-upg-6.0.3-6.0.3.1.sql

    • konyadmin-sqlserver-upg-6.0.3-6.0.3.1.sql

  3. Execute the upgrade database scripts of 7.0
  4. Verify the Admin and Reports schema created in the database. It should display the last executed scripts.

    5. Note: You have to run the scripts in the sequential order. Replace the name of the konyadmin and konyreports schema name to your respective schemas.

    Important: Executing the database scripts is applicable only if you are migrating from 6.x to 7.x.

Migrating Database from 6.5.x to 7.0.x

Migrating database from 6.5.x to 7.0.x is done using flyway tool.

Migrating Admin Database

To migrate admin DB, follow these steps:

  1. Open V3_konyadmin-xxxx-7.0.0.0.sql. xxxx is the type of DB you are using.

    2. Example: MS-SQL V3__konyadmin-sqlserver-7.0.0.0.sql. Similarly for My SQL, V3__konyadmin-mysql-7.0.0.0.sql etc.

  2. In the V3_konyadmin-xxxx-7.0.0.sql, replace all KONY_SERVER place holders with the actual values from your middleware.properties file.

    3. Example: ‘${KONY_SERVER_RICH_CLIENT_DEPLOY}' => ‘corresponding_value_in_your_middleware.properties’

    Note: If no values are assigned in middleware.properties, set those values to null in the SQL files.
    Example: In middleware.properties, if you have
    #Memcache configuration=
    #memcache.cluster=
    Then in SQL files, set the placeholders value as null.

    Important: For null values, remove the colon ' '.

  3. After editing, the V3-xxx.sql script, place all the scripts into SQL folder in flyway installation directory.

    Example: \flyway-commandline-3.2.1-windows-x64\flyway-3.2.1\sql

  4. Executing the scripts– Before executing the scripts, configure flyway to your database.

  5. Open flyway.conf from \flyway-commandline-3.2.1-windows-x64\flyway-3.2.1\conf
  6. Edit the following variables. Un-comment them after editing

    • flyway.url=<your jdbc URL> example for MySQL, it is flyway.url=jdbc:mysql://<IP>:<PORT>.

    • flyway.driver=<SQL DRIVER>

    • flyway.user

    • flyway.password

    • flyway.schemas= <your admin Database name>

    • flyway.baselineVersion=3

  7. Open the command line and type cd to \flyway-commandline-3.2.1-windows-x64\flyway-3.2.1.

  8. Execute the command flyway repair followed by flyway migrate. Below the expected output after executing flyway repair and flyway migrate commands:

  9. You admin database is now migrated to 7.0.

Migrating Reports Database

To migrate your reports database, follow these steps:

  1. Download the flyway scripts with respect to the type of database you are using (Oracle, MySQL, SQL) of 7.0.

  2. Place the downloaded scripts in \flyway-commandline-3.2.1-windows-x64\flyway-3.2.1\sql.

  3. Open flyway.conf from \flyway-commandline-3.2.1-windows-x64\flyway-3.2.1\conf.

  4. Edit the following variables. Un-comment them after editing and save the file.

    • flyway.url=<your jdbc URL> example for MySQL, it is flyway.url=jdbc:mysql://<IP>:<PORT>.

    • flyway.driver=<SQL DRIVER>

    • flyway.user

    • flyway.password

    • flyway.schemas= <your Reports Database name>

    • flyway.baselineVersion=3

  5. Execute the flyway repair followed by flyway migrate as you have done with Admin Database.

  6. Your Reports database in now migrated to 7.0.

Migrating WAR files

  1. Download admin.war, middleware.war and services.war of 7.0.

  2. Remove the data present in deployments folder from <install_location>\jboss\instance1\standalone\ after taking the backup.

  3. Place the 7.0 war files admin.war, middleware.war, services.war in <install_location>\jboss\instance1\standalone\deployments.

  4. Delete the Kony folder from <install_location>\jboss\instance1\modules\system\layers\base\com.

  5. Open standalone.xml from <install_location>\jboss\instance1\standalone\configuration.

  6. Delete com.kony.middleware entry from <global-modules>.

  7. Add two entries in the global-modules related to JMS as below and save the file.

    <module name="org.jboss.remote-naming" slot="main"/>

    <module name="org.hornetq" slot="main"/>

  8. Delete the data present in tmp folder. Location of tmp folder is <install_location>\jboss\instance1\standalone\tmp.

Migrating Metrics

If you are using metrics in 6.0.x / 6.5.x and would like to update the same to 7.0.x, follow the below steps:

  1. Download metrics.ear of 7.0.

  2. Open metrics.ear in a ZIP editor and rename metricsJAR-0.0.1-SNAPSHOT.jar present inside it to metrics.jar.

Verification

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

To verify the upgrade process  

  1. Start JMS server by clicking startjboss.bat from <jboss-install-location>/ jboss62_jms/bin.

  2. Start JBoss middleware server by clicking standalone.bat from <jboss-install-location>/jboss/instance/bin.
  3. Access the URL http://ipaddress:port/middleware/version.html in a browser.
  4. Navigate to the URL http://ipaddress:port/admin/version.html and look for server version.
  5. 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.

  6. Navigate to Settings and click Configuration.

    Note: Access to Reporting Queue will be green only if you have configured metrics and the JMS server is up and running.

 

 

Copyright © 2013 Kony, Inc. All rights reserved.

Open topic with navigation