Installation Notes for installing 6.1c.07.06 and higher versions porting set on Unix platform. ============================================================================================= Last Revised: 25st January 2005 ============================================================================================= Introduction The complete porting set is delivered as one, compressed, tar file. For example: PA.2636.tar.Z. (For LINUX porting set the format is PA.XXXX.tar.gz.) The PA-number of the porting set identifies the porting set in an unique way. Each porting set build has it's own unique PA number. Before starting installing this new Porting Set take care that: * Nobody is logged in Baan. * There are no running Baan jobs. Installation of porting set To install the porting set, perform the following steps: 1. Download the porting set compressed tar file, which is applicable for your Operating System, and copy it to your $BSE directory. 2. Log in as root 3. Uncompress the PA.XXXX.tar.Z file by running: compress -d $BSE/PA.XXXX.tar.Z Note: For LINUX porting set, use the following command to uncompress the file: gunzip $BSE/PA.XXXX.tar.gz. 4. Check if all users have logged off. You can do it, by typing the command: "ps -ef | grep bshell |grep -v grep" If no bshell process is found, no one is logged in anymore. 5. Change to directory $BSE/etc and stop Baan/Triton by executing the command: ./rc.stop . 6. Stop the license daemon (if not stopped by the rc.stop, displayed in the "stop-information") by executing the command: licmon6.1 -k . NOTE: this will kill the primary license daemon. 7. Change to directory $BSE and: Copy the $BSE/bin directory to $BSE/bin.old Copy the $BSE/api directory to $BSE/api.old Copy the $BSE/lib directory to $BSE/lib.old Copy the $BSE/java directory to $BSE/java.old Copy the $BSE/shlib directory to $BSE/shlib.old Copy the $BSE/include6.1 directory to $BSE/include6.1.old This is just to make a backup, to make it possible to revert quickly back to the old porting set in case of any problems. Note that you can also do a move (mv) instead of a copy: when doing a copy you will keep components, that will not be installed by the new dump. For example, when having a script, which is executed before the bshell starts. Do not move the lib directory, otherwise you will loose runtime files that will prevent you from using the environment! 8. Install the new porting set files, run: tar xvf PA.XXXX.tar to unpack the file. By running this command the following directories will be unpacked: api, bin, java, include6.1, lib and shlib. So your current contents of these directories will be overwritten now. If you like to check the contents of the tar file first, without installing, run: tar tvf PA.XXXX.tar 9. To ensure that all the permissions are correct you have to run binperm6.1. This script automatically corrects all the permissions. Change to the directory $BSE/bin and execute the command: sh binperm6.1 [ binperm does not chown bsp:bsp $BSE/bin/. (directory itself) ] 10. Generate a new $BSE/lib/shm_param file: (Note that current shm_param file is already saved at step 7, when copying the lib directory to lib.old) Generate a new file: $BSE/bin/shmvalues6.1>$BSE/lib/shm_param chown bsp:bsp $BSE/lib/shm_param 11. Only in case you are using TBASE(TP): Remove the file $BSE/lib/tbase/tbase_open When running $BSE/etc/rc.start a new tbase_open file is created automatically. 12. Remove the files PA.XXXX.tar afterwards, or move it to another location if you would like to keep it. 13. Check permissions of the new installed files by checking $BSE/lib. Look for the user ID of the directories/files and use the number in the following command. Run from $BSE directory: find . -user number -exec chown bsp:bsp {} \; -print Also check if permissions of $BSE/shlib/libjvm2bvm.sl has execute rights, If not: execute chmod a+x libjvm2bvm.sl Only in case you are using TBASE(TP): Check permissions of the file in $BSE/lib/tbase. The owner of these files should be "tbase". 14. Change directory to $BSE/etc and start Baan by executing the command ./rc.start . Now it should work. Do a final test before the system is released to the users! REVERTING BACK TO OLD PORTING SET ================================= In case you have followed the installation instructions as described above, follow these steps to revert to the old porting set: 1. Log in as root 2. Check if all users have logged off. You can do it, by typing the command: "ps -ef |grep bshell" If no bshell process is found, no one is logged in anymore. 3. Change to directory $BSE/etc and stop Baan/Triton by executing the command: ./rc.stop . 4. Stop the license daemon (if not stopped by the rc.stop, displayed in the "stop-information") by executing the command: licmon6.1 -k . NOTE: this will kill the primary license daemon. 5. Change to directory $BSE and: Move the $BSE/bin directory to $BSE/bin.curr (mv $BSE/bin $BSE/bin.curr) Move the $BSE/api directory to $BSE/api.curr Move the $BSE/lib directory to $BSE/lib.curr Move the $BSE/java directory to $BSE/java.curr Move the $BSE/shlib directory to $BSE/shlib.curr Move the $BSE/include6.1 directory to $BSE/include6.1.curr 6. Rever to the old files: Move the $BSE/bin.old directory to $BSE/bin Move the $BSE/api.old directory to $BSE/api Move the $BSE/lib.old directory to $BSE/lib Move the $BSE/java.old directory to $BSE/java Move the $BSE/shlib.old directory to $BSE/shlib Move the $BSE/include6.1.old directory to $BSE/include6.1 7. To ensure that all the permissions are correct you have to run binperm6.1. This script automatically corrects all the permissions. Change to the directory $BSE/bin and execute the command: sh binperm6.1 8. Revert to the old $BSE/lib/shm_param file: Rename the current one: mv shm_param shm_param.curr and revert to the old one: mv shm_param.old shm_param NOTE: In case you upgraded your OS, after you installed the new porting set, do not move the shm_param.old to shm_param, but generate a new one: Generate a new file: $BSE/bin/shmvalues6.1>$BSE/lib/shm_param chown bsp:bsp $BSE/lib/shm_param 9. Only in case you are using TBASE(TP): Remove the file $BSE/lib/tbase/tbase_open When running $BSE/etc/rc.start a new tbase_open file is created automatically. 10. Check permissions of the new installed files by checking $BSE/lib. Look for the user ID of the directories/files and use the number in the following command. Run from $BSE directory: find . -user number -exec chown bsp:bsp {} \; -print Also check if permissions of $BSE/shlib/libjvm2bvm.sl has execute rights, If not: execute chmod a+x libjvm2bvm.sl Only in case you are using TBASE(TP): Check permissions of the file in $BSE/lib/tbase. The owner of these files should be "tbase". 11. Change directory to $BSE/etc and start Baan by executing the command ./rc.start . Now it should work. Do a final test before the system is released to the users!