Updating to the newest version

Update includes a (1) backup of the current files and (2) moving of all the components, except the configuration files.

In general, all the Java components are installed in the user home directory (e.g.,  /home/java). The web interface components are stored in the web server directory (Document root, see your web-server settings).

Backup existing files

    1. Backup of all web components. For example, in Linux you can do it like this (if all web components are installed in /var/www/):

 # export DATE=$(date +%F)
 # mkdir -p /backups/$DATE 
 # cp -a /var/www /backups/$DATE/
    1. Make database backup (schemes of google and tracking)

You must stop mysqld and copy binary files to backup directory:

# mkdir -p /backups/$DATE/db
# cp -a /var/lib/mysql/tracking  /backups/$DATE/db/
# cp -a /var/lib/mysql/google /backups/$DATE/db/
    1. Make backup of java servers

To backup jar files and its conf files just copy these files into backup directory:

# cp /home/java/api-server /backups/$DATE/
# cp /home/java/tcp-server /backups/$DATE/
# cp /home/java/sms-server /backups/$DATE/

Install new files

    1. Download and unzip archive with updates. For example, in Linux do:

$ unzip -d update-2013-01-01


    1. Change directory to directory where the archive is unzipped (in this example it’s update-2013-01-01)
    2. Replace content of all web of components (pro-ui and panel-v2) in the folders where it installed. For example, in Linux, if the panel is installed in /var/www/panel/, folder you can copy its contents with command:

$ cp -a panel-v2/ /var/www/panel-v2/

Trailing slash after panel-v2 is important.

  1. Copy files api-server.jar and VERSION with replacement from api-server folder to the folder, where api-server is installed api-server. Also update a configuration according to the actual version of documentation (see api-server)
  2. Copy files tcp-server.jar and tcp-server-version.txt with replacement from tcp-server folder to the folder, where tcp-server is installed. Also update a configuration according to the actual version of documentation (see tcp-server)
  3. Copy folder lib and sms-server-version.txt file from sms-server folder to the folder, where sms-server is installed. Also update a configuration according to the actual version of documentation (see sms-server)
  4. Run on your DB (scheme google) files updates.sql, models.sql, plugins_records.sql, panel_rights.sql and quartz_tables_mysql_innodb.sql from db folder for example, in Linux you can do it like this:
     $ cd db
     $ mysql -uroot -p --default-character-set=utf8 google
     > SOURCE updates.sql;
     > SOURCE models.sql;
     > SOURCE plugins_records.sql;
     > SOURCE panel_rights.sql;
     > SOURCE operators.sql;
     > SOURCE codes.sql;
     > SOURCE quartz_tables_mysql_innodb.sql;

    Or you can use db/

     $ cd db
     $ ./ -h
     Usage: [-h] [-H host] [-u user] [-p password]
         -h show this message
         -H db host name (default: localhost)
         -u db user name
         -p db user password
     $ ./ -u root
     Enter mysql user password: 
     Updating db..
     Already updated to 2
     Already updated to 28
     Updated to 29
     Successful finished.
  5. Reboot java servers. For example, you can do it like this:
     # sv t api-server
     $ sv t navixyserver
     $ sv t sms-server
  6. It is necessary to check correct work of the system in the web interface, and if some problems occured, you can read jar files logs, which are in ~/server/log/log.txt, where server is one of the following components api-server, sms-server or tcp-server.

If you have more questions please contact our support team


USA: +1 858 815 9045

Mexico: +52 334 1642158

UK: +44 808 1641499

Germany: +49 1573 5988250

Russia: +7 495 223 0427

Log in