Open topic with navigation

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

Upgrade JBoss Manually from 6.0.x to 6.5.x

This section provides you the steps to upgrade Kony MobileFabric Integration Service manually from 6.x to 6.5.x (JBoss).

Prerequisites

The following table displays the prerequisites for upgrading Kony MobileFabric Integration Service.

Refer to http://community.kony.com/archive/downloads/manual to download the following artifacts:

Artifacts Type Purpose
Respective Database scripts Database Scripts To setup the required schema
  • admin.war
  • middleware.war
  • appdownload.war
  • metrics.ear (applicable only for metrics)
 WAR files To be deployed to Application Server
  • libraries-MIDDLEWARE-GA-ver.tar
  • middleware-bootconfig.tar
 TAR files  
JAR files  

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
      • appdownload.war
    2. middleware-bootconfig directory from <jboss-install-location>/install/middleware
    3. metrics.ear from <jboss-install-location>/jboss62_jms/standalone/deployments (applicable only for metrics)

    4. middleware JAR files from <jboss-install-location>/install/lib/middleware.

  3. After taking the backup, delete or uninstall the above files.

Execute Database Scripts

  1. Stop the application server.
  2. Execute the upgrade database scripts from 6.x to 6.5.x from http://community.kony.com/archive/downloads/manualand verify the Admin and Reports schema created in the database.

    3. Note: You have to run the scripts in the given order. While executing in this order, exclude the 6.x scripts.
    Replace the name of the konyadmin and konyreports schema name to your respective schemas.

Add New and Update Existing Property Files

  1. Extract themiddleware-bootconfig.tar to the <jboss_install-location>/install/middleware directory.
  2. Retain the properties of admin-log4j.properties and deployment-config.properties under middleware-bootconfig/admin folder from the previous version (which are already backed up).
  3. Retain the changes made to the middleware.properties and middleware-log4j.properties in middleware-bootconfig folder from the previous version (which are already backed up).

  4. Open middleware-log4j.properties and edit the below path for device-payload.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 under the middleware-bootconfig of older version to the new middleware-bootconfig in <jboss_install-location>/install/middleware folder.

  6. If metrics is not used, open middleware.properties in the middleware-bootconfig folder and mark the property under metrics.logging as false.

    Note: If metrics is used, set the property as true.

    Note: This property was introduced in 6.0.3.2.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 we set metrics.logging property to false, call the kony.license.disableMetricReporting() API in app init to disable “Maximum Offline Sessions Exceeded” alert.

  7. Retain the properties in metrics-log4j.properties in middleware-bootconfig/admin folder and serverconsole.properties in middleware-bootconfig folder from the same respective files of previous version (applicable only for metrics).
  8. Open standalone.xml file of Standalone JBoss (Not the JMS JBoss) available at <jboss-install-location>/jboss/instance/standalone/configuration and add these two entries under <global-modules>:
    <module name="org.jboss.remote-naming" slot="main"/>
<module name="org.hornetq" slot="main"/>

Deploy Latest Artifacts

  1. Copy the latest admin.war, middleware.war and appdownload.war to <jboss-install-location>/jboss/instance/standalone/deployments.
  2. Extract and copy the jars from libraries-MIDDLEWARE-GA-<version>.tar to <jboss-install-location>/install/lib/middleware.
  3. Add the thin client jars to <jboss-install-location>/install/lib/middleware , if the user is using thin client apps and add the jar entries to module.xml.
  4. If the user wants to use mobilefabric , follow the below steps :

    1. Open konyadmindb and go to mobilefabric_configuration table.

    2. Add the below two entries in the table.

      • First entry should have prop_name as management_server_host_name and prop_value is the jboss.bind.address.management provided in the standalone.xml file available in <jboss_install-location>/jboss/instance/standalone/configuration.
      • Similarly, the second entry should have prop_name as management_server_port and prop_value as the jboss.management.native.port given in the same standalone.xml.

  5. Copy the metrics.ear to <jboss-install-location>/jboss62_jms/standalone/deployments (applicable only for metrics).

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

  5. Navigate to Settings and click Configuration.

Copyright © 2013 Kony, Inc. All rights reserved.

Open topic with navigation