|
Size: 4983
Comment:
|
Size: 5019
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 10: | Line 10: |
| 1. cp -r /u/cc/std/adm /u/cc.<B>/std/ | |
| Line 48: | Line 49: |
| # drcont drcont: error while loading shared libraries: XXXXX.so.XX: cannot open shared object file: No such file or directory }}} |
# drcont drcont: error while loading shared libraries: XXXXX.so.XX: cannot open shared object file: No such file or directory }}} |
| Line 65: | Line 64: |
| * For BODY conversion to rel 13 run catrep to set all current Cats "On Web" flag to n for OLBIS conversion check manually tacont page 2 tax no 14 |
* For BODY conversion to rel 13 run catrep to set all current Cats "On Web" flag to n for OLBIS conversion check manually tacont page 2 tax no 14 |
Procedure for upgrading a customer site
To upgrade a customer from Release<A> to Release<B>
Note: Release<A> should be Release<B> - 1. Never skip over a Release. If you have to, repeat the procedures for each release.
Create a test environment. In the event a test environment is not practial/feasible refer to AllphonesRel9UpgradePlan.
mkdir /u/cc.<B>/
mkdir /u/cc.<B>/TEST<B>
cp /u/cc/<CUSTOMER>/*.* /u/cc.<B>/TEST<B>
cp -r /u/cc/adm /u/cc.<B>
cp -r /u/cc/std/adm /u/cc.<B>/std/
Create a new user called test<B>.
Edit test<B>'s .bash_profile to export CCDIR=/u/cc.<B>
- Perform upgrade on test environment.
- Setup auto-posting for test environment
- Ask customer to test the test environment.
- When customer is happy with test environment, arrange time to perform upgrade. Preferably overnight.
- Notify customer of upgrade and hope nothing went horribly wrong !!
To upgrade data and programs from Release<A> to Release<B>
Send all Release<B> programs, customised Release<B> programs, libraries, Release<B> standard company, the upgra<A> script and the upgra<B> script. Do NOT install. Place in a convienent location.
- Disable all cron jobs (remember which ones so you can distinguish it later from those already disabled).
- Ensure that all stores are fully synchronized with head office via polling.
- Disable polling at store and head office.
- Backup existing data and programs.
Send and install the latest Release<A> utitliy and update programs.
Check that running the upgra<A> script will not be a problem and run. If running the whole script may cause problems, manually run the appropriate steps. To check if the script will cause problems, check /u/ccr.A/std/update.log and /u/ccr.A/std/update.txt.
- Check that the data is okay. Some functionalitiy may not work correctly due to changes in data updates.
- Backup the company. This can useful if the following steps fail.
- Backup the current programs.
Install new Release<B> programs, libraries and standard company. Make sure they have Read Write and Execute permissions.
Run the upgra<B> script.
Run mencmp /u/ccr.A/standard /u/ccr.B/<compdir>. This shows the differences between their menus and the standard. You may need to print this one out.
- Save a copy of their menu.dat and copy a new one from standard.
- Run meaad and manually port over their special changes to the new standard menu.
- Transfer their terminal settings manually for every terminal they use.
- Perform basic checks (eg. run sieat, run an aad program, etc.) on each company (conset into each one). Also run checkdb to confirm correct db structure.
- Set permissions of data files to be writable by ALL users. For rel 11 and above set "Convert to upper case" to "n" in cocont
- Run /u/cc/binl/link_cntrl
- Re-enable and test polling
- Re-enable all cron jobs you disabled earlier.
- For conversion to rel 12 make sure to check parameters in tacont page 2 relating to tax included in the sale price.
- For conversion to rel 13 make sure rounding parameters in prcont are correct.
- When CSCART is used make sure prcont pricing level are "Price" IT WON'T WORK IF CUSTOMER USES DISCOUNT .
- Test the programs extensively. Both functionally, and make sure it does not look like crap.
Common Problems
- Missing library files. You will typically see an error message like this:
# drcont drcont: error while loading shared libraries: XXXXX.so.XX: cannot open shared object file: No such file or directory
To fix this:- Find the RPM package that contains the required library file and install. In Fedora Core 3 onwards, use Yum.
- Copy the file libupgrade_sam.tgz from Sam and extract to $CCDIR/lib/. Be careful as it will overwrite existing library files.
- Edit the LD_LIBRARY_PATH variable in $CCDIR/usr/common.sh to include $CCDIR/lib/
- Incorrect version of libstdc++.so.6 To fix this:
- Edit the LD_LIBRARY_PATH variable in $CCDIR/usr/common.sh to use library files in $CCDIR/lib/ first
- Edit the LD_LIBRARY_PATH variable in $CCDIR/usr/common.sh to use library files in $CCDIR/lib/ last
Release 13 specific notes
- Make sure you copy the latest version of postcode.idx and put it in $CCDIR/adm/ (contains mixed case suburbs, etc).
- Make sure you go into terminal settings and change blank number of copies to 1 (blank means 0 or do not print) use setprno.sh script
- Make sure to run sturep and convert slash to dash and inform customer slashes are no longer allowed
- Make sure their statistical temporary column is properly separated.
- ssarep may not produce results - you may have to reindex caaad again.
Check & populate if required the allowable company prefix in employee record
- For BODY conversion to rel 13 run catrep to set all current Cats "On Web" flag to n for OLBIS conversion check manually tacont page 2 tax no 14
