Skip to main content
Top
Review meshIQ Products (G2.com)

Upgrading to meshIQ Track v11.1.1

This article contains two sets of instructions. Choose the instructions that pertain to you:

Upgrade to 11.1 from the 11.0.3 deployment pack (meshIQ_11.0.3_Full_DPackV2.0.tar.Z)

Prerequisites

The following packages are required for Track upgrade:

  • AP11.1_SU01.pkg
  • AP_AIM-11.1.1.pkg
  • DATA_SERVICE-11.1.1.pkg
  • JOB_SCHEDULER-11.1.1.pkg
  • ds-db-utils-11.1.1.tar.gz
  • ds-api-11.1.1.tar.gz
  • track-11.1.1.tar.gz

Upgrade procedure

  1. Stop the Web, CEP, and Domain services.
  2. Go to /opt/meshiq/misc/dbapi and run the command: unlink current
  3. Run the following:  
tar -zxvf ds-db-utils-11.1.1.tar.gz
ln -s  ds-db-utils-11.1.1 current
  1. Navigate to /opt/meshiq/platform/updates.
  2. Place all the files mentioned above (under Prerequisites) in the updates folder.
  3. Go to /opt/meshiq/platform/bin and run the following commands:
./pkgman ../updates/ AP11.1_SU01.pkg
./pkgman ../updates/ AP_AIM-11.1.1.pkg
./pkgman ../updates/ JOB_SCHEDULER-11.1.1.pkg
./pkgman ../updates/ DATA_SERVICE-11.1.1.pkg
  1. After running each command from the above go to /opt/meshiq/sbin folder and run the commands:
./start.sh domain
./stop.sh domain
  1. When the first package AP11.1_SU01.pkg is updated and the domain is started, it won’t start on the first attempt. You need to start it twice for the first package.
  2. Go back to /opt/meshiq/platform/updates and run the following:
tar -zxvf  ds-api-11.1.1.tar.gz
tar -zxvf  track-11.1.1.tar.gz
  1. Move both ds-api.war and track.war files to /opt/meshiq/platform/apache-tomcat/webapps.
  2. Start the Domain, CEP, and Web services one after the other.
  3. Because this is an upgrade, you need to update the database and create Kafka topics.
  4. Stop the Web, CEP, and Domain services.
  5. Determine the value of the zkHost property used by Solr. The format of this property is: 
    <zookeeper-host>:<zookeeper-port><zookeeper-root>

    You can find it in one of the following places:

    1. If you have access to Solr web console:
      • Go to the Dashboard tab for any of the nodes in the cluster, and under the "Args" section, check the value of -zkHost.
        OR
      • Go to the Cloud/ZKStatus tab and check for the "ZK connection string" value.
    2. In global.properties, see if the value for jkool.db.url is NOT a http[s] url. If it is not, then it is the ZooKeeper information that Track is using to connect to Solr.
    3. Go to the installation of Solr on one of the nodes in the cluster, open the file <SOLR_HOME>/bin/solr.in.sh and find the value for environment variable ZK_HOST.
  6. Upgrade the database. The database upgrade must be run on a node that contains a Solr installation (even if Solr is not actually running on that node). The ZooKeeper host, port, and root must match the values from the zkHost property from step 14. To upgrade, go to /opt/nastel/misc/jkool-dbapi/current/bin and run the following, providing the Solr credentials: 
    ./jkool-db-upgrade.sh -pwd <jkql-admin-pwd> [-solr <solr-home>] [-sh <solr-host>] [-sp <solr-port>] [-zh <zookeeper-host>] [-zp <zookeeper-port>] [-zr <zookeeper-root>] [-suser <solr-user> -spwd <solr-pwd>]

    The following example assumes that Solr is running on the local node and is using ZooKeeper that is also on the local node, and uses the default meshIQ platform configuration: 
    ./jkool-db-upgrade.sh -pwd admin -solr /opt/meshiq/xray/solr/current -sh localhost -sp 8983 -zh localhost -zp 2181 -zr /xraysolr

  7. Once the database is upgraded, navigate to /opt/meshiq/platform/jkool/scripts and run the following to create Kafka topics:
./create-kafka-topics.sh
  1. Start the Domain, CEP, and Web services.
  2. Log in to the Track UI.

Upgrading to 11.1 from the v11.0.3 fix pack

Prerequisites

The following packages are required for Track upgrade:

  • AP11.1_SU01.pkg
  • AP_AIM-11.1.1.pkg
  • DATA_SERVICE-11.1.1.pkg
  • JOB_SCHEDULER-11.1.1.pkg
  • ds-db-utils-11.1.1.tar.gz
  • ds-api-11.1.1.tar.gz
  • track-11.1.1.tar.gz

Upgrade procedure

  1. Stop the Web, CEP and Domain services.
  2. Go to /opt/meshiq/misc/jkool-dbapi and run the command: unlink current
  3. Run the following:  
tar -zxvf ds-db-utils-11.1.1.tar.gz
ln -s  ds-db-utils-11.1.1 current
  1. After this navigate to /opt/meshiq/AutoPilotM6/updates
  2. Place all the files mentioned above in the updates folder.
  3. Again go to /opt/meshiq/AutoPilotM6/bin and run the following commands:
./pkgman ../updates/ AP11.1_SU01.pkg
./pkgman ../updates/ AP_AIM-11.1.1.pkg
./pkgman ../updates/ JOB_SCHEDULER-11.1.1.pkg
./pkgman ../updates/ DATA_SERVICE-11.1.1.pkg
  1. After running each command from the above go to /opt/meshiq/sbin folder and run the commands:
./start.sh domain
./stop.sh domain
  1. When the first package AP11.1_SU01.pkg is updated and the domain is started, it won’t start on the first attempt. You need to start it twice for the first package.
  2. Go back to /opt/meshiq/AutoPilotM6/updates and run the following:
tar -zxvf  ds-api-11.1.1.tar.gz
tar -zxvf  track-11.1.1.tar.gz
  1. Move both ds-api.war and track.war files to /opt/meshiq/AutoPilotM6/apache-tomcat/webapps.
  2. Start the Domain, CEP, and Web services one after the other.
  3. Because this is an upgrade, you need to update the database and create Kafka topics.
  4. Stop the Web, CEP, and Domain services.
  5. Determine the value of the zkHost property used by Solr. The format of this property is: 
    <zookeeper-host>:<zookeeper-port><zookeeper-root>

    You can find it in one of the following places:

    1. If you have access to Solr web console:
      • Go to the Dashboard tab for any of the nodes in the cluster, and under the "Args" section, check the value of -zkHost.
        OR
      • Go to the Cloud/ZKStatus tab and check for the "ZK connection string" value.
    2. In global.properties, see if the value for jkool.db.url is NOT a http[s] url. If it is not, then it is the ZooKeeper information that Track is using to connect to Solr.
    3. Go to the installation of Solr on one of the nodes in the cluster, open the file <SOLR_HOME>/bin/solr.in.sh and find the value for environment variable ZK_HOST.
  6. Upgrade the database. The database upgrade must be run on a node that contains a Solr installation (even if Solr is not actually running on that node). The ZooKeeper host, port, and root must match the values from the zkHost property from step 14. To upgrade, go to /opt/nastel/misc/jkool-dbapi/current/bin and run the following, providing the Solr credentials: 
    ./jkool-db-upgrade.sh -pwd <jkql-admin-pwd> [-solr <solr-home>] [-sh <solr-host>] [-sp <solr-port>] [-zh <zookeeper-host>] [-zp <zookeeper-port>] [-zr <zookeeper-root>] [-suser <solr-user> -spwd <solr-pwd>]

    The following example assumes that Solr is running on the local node and is using ZooKeeper that is also on the local node, and uses the default meshIQ platform configuration: 
    ./jkool-db-upgrade.sh -pwd admin -solr /opt/meshiq/xray/solr/current -sh localhost -sp 8983 -zh localhost -zp 2181 -zr /xraysolr

  7. Once the database is upgraded, navigate to /opt/meshiq/AutoPilotM6/jkool/scripts and run the following to create Kafka topics:
 ./create-kafka-topics.sh
  1. Start the Domain, CEP, and Web services.
  2. Log in to the Track UI.