Replikwando/Installation

From ISoft Wiki
< Replikwando
Revision as of 16:14, 31 August 2009 by 192.168.5.1 (talk)
Jump to navigationJump to search

Windows Server

Service version of Replikwando, which will backup database in case of hard drive failure in addition to updating inventory on heavytruckparts.net automatically.

-Need SSL keys from Brian

  1. Connect to server thru VNC
  2. Create Replikwando account on Replikwando Records website
    Update Kungfu to show the new HTP account informatoin
  3. Download Replikwando Install pack from tools.isoftdata.com
  4. Copy certificates over to C:\Program Files\Isoft Data Systems\Certificates
  5. Run "install as service" bat file
  6. Edit Replication.ini file
    1. Check sqlyog that the following matches the clients:
      Use frontend to check the username and password
      [fromServer]
      Host
      Database
      Username
      Password
    2. Set Username and Password for [toDatabase] with same account info setup on Replikwando Records
      Use Frontend to convert pass to hash
      Add "Z" in front of hash
    3. Set database = product code (Can be found Replikwando Records)
    4. Set prefix = company name
      Copy company name from certs, everything before -cert
      Ex. for ARA-Truck-Parts-cert prefix=ARA-Truck-Parts
  7. Edit my.ini file (C:\Program Files\MySQL\MySQL server 5.1\my.ini)
    1. Add the following under [mysqld]:
      log-bin
      expire-logs-days=10
  8. Stop and Start the MySQL service
    Either
    1. Restart service in control panel -> Admin tools -> services
    2. in command prompt:
      net stop mysql
      net start mysql
  9. Set up Task Schedule to run Replikwando once after business hours.
    Only need to set up schedule if installing during business hours so that you don't lock up clients database
  10. Tell Brian user and Product code so he can set up triggers on HTP.net
  • Note: Replikwando will lock up the entire database during the initial push, so it may be a good idea to run it at the end of the work day.

Linux Sever

Replikwando on Linux using Wine

  1. Connect to the customer's server using sftp (it's a *nix app, may need to install Cygwin-X)
    Do `put “Replikwando with Wine.tar.gz” .` to put the install files on their server
    You can also put the customer's key and cert now, as well
  2. Connect to the customer's server using SSH/putty
    Extract the files using `tar -zxf “Repikwando with Wine.tar.gz”`
    If that fails, use `gunzip “Replikwando with Wine.tar.gz”`, `tar -xf “Replikwando with Wine.tar”
  3. You will now have two new files in your directory, replikwando_install.sh and ISoft/*
    Type ./replikwando_install.sh
    Depending on the system configuration, several prompts may show up. Just read them and follow what they tell you to do.
    The script will tell you when it is done running.
  4. Navigate to ~/.wine/drive_c/Program\ Files/Replikwando
    This directory will contain the error logs, sqlite file, and so on.
    Put in the required values for replication.ini
  5. Type ~/replikwando_startup.sh to start Replikwando for the first time.
    Confirm that Replikwando is running correctly using the error logs here
    Type `vi <filename>` to open the file in an editor to read it. Type :q<enter> to quit.
  6. To connect to the mysql server, type `mysql -utestuser -hlocalhost -p`
    You'll have to type a 'use <database>' command before running queries
  7. Once Replikwando is confirmed running, type `sudo vi /etc/rc.local` and place the following lines just above the last line that says 'exit 0':
  8. start replikwando
  9. sudo -H -u isoft /home/isoft/replikwando_startup.sh
  10. Done!

Some quick tips: Quick linux commands: ls : shows you what is in the directory sudo : lets you run powerful & dangerous commands (requires password) cd : change directory rm : deletes a file (use rm -r to delete a folder) deletes cannot be undone! You can't open Replikwando's UI to see if it's pushing data, so you have to rely on the error logs and test database changes. All normal Replikwando caveats apply (initial push db lock, query error logs, so on so forth)

If you have any additional questions, ask Justin.