Replikwando/Installation
From ISoft Wiki
< Replikwando
Jump to navigationJump to search
Revision as of 11:45, 19 August 2009 by Daytonlowell (talk | contribs)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
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
- Connect to server thru VNC
- Create Replikwando account on Replikwando Records website
- Update Kungfu to show the new HTP account informatoin
- Download Replikwando Install pack from dl.isoftdata.com
- Copy certificates over to C:\Program Files\Isoft Data Systems\Certificates
- Run "install as service" bat file
- Edit Replication.ini file
- Check sqlyog that the following matches the clients:
- Use frontend to check the username and password
- [fromServer]
- Host
- Database
- Username
- Password
- 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
- Set database = product code (Can be found Replikwando Records)
- Set prefix = company name
- Copy company name from certs, everything before -cert
- Ex. for ARA-Truck-Parts-cert prefix=ARA-Truck-Parts
- Check sqlyog that the following matches the clients:
- Edit my.ini file (C:\Program Files\MySQL\MySQL server 5.1\my.ini)
- Add the following under [mysqld]:
- log-bin
- expire-logs-days=10
- Add the following under [mysqld]:
- Stop and Start the MySQL service
- Either
- Restart service in control panel -> Admin tools -> services
- in command prompt:
- net stop mysql
- net start mysql
- 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
- 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.