Cloverleaf 5.5 Server Install Files for RedHat

[Max Drown (Infor)]

Where can I get the Cloverleaf 5.5 server install files for RedHat?

-- Max Drown (Infor)

Topic

[Scott Lee]

Just a guess – Quovadx??  😆

Unless you bought it through another vendor, then go to that vendor…

Scott

[Max Drown (Infor)]

Naturally I’m looking for a download location from Quovadx or a contact at Quovadx that can send me the CD’s.

-- Max Drown (Infor)

[Rick Brown]

Max – You will need to contact your customer service rep to get the CD.  You cannot download it unfortunately.

If you are not sure of who your CSR is you can call support and find out quickly.  (972) 361-3004.

Thanks,

Rick

[Max Drown (Infor)]

Thanks, Rick.

-- Max Drown (Infor)

[Max Drown (Infor)]

Is it possible to install Cloverleaf on RedHat w/o putting the CD in the drive? I tried copying the files over and running the install script, but the script crashes w/o error.

-- Max Drown (Infor)

[Steve Carter]

How did you copy the files over?  FTP from Windows maybe?  If so, make sure it’s a binary transfer.  I had problems with this when installing 5.5 on AIX.  I wound up just creating an ISO file and then FTP’d it to the server and installed from the ISO.

Hope this helps.

Steve

[Max Drown (Infor)]

That’s a good idea. I’ll try that. What’s the command to install from an ISO?

-- Max Drown (Infor)

[Steve Carter]

I know it involves mounting the ISO as a filesystem, but our AIX admins did that part.  I can’t be much more help with this piece.

Steve

[Russ Ross]

I run on AIX but I’ve always installed/upgraded Cloverleaf by copying the CD to a hard drive and doing the install from the copy on the hard drive.

So it has definitelty worked at our AIX shop.

I do that because I can easily run the install repeatedly until I’m satisfied it all goes well before I do the real install.

Plus it is easy to tar up and move to another box without having to walk 2 blocks down the street to get to the computer room.

Our method of upgrading is to create a script to do every single step necessary until there is no human intervention required and keep doing practice installs until we have all known issues resolved.

If after a practice upgrade/install testing reveals an issue we blow everything away and modify our upgrade scripts and run them again and continue testing until all goes well.

Then when we feel it is ready we let it rip and next thing you know we are done with no surprises.

This also is very handy to know what we did on a previous upgrade and reuse many of the steps on the next upgrade without having to remeber steps we might otherwise have forgotten.

Here is an example of the script that copies the CD that I ran recently so you will get the idea and can adjust for your situation.

This script is called 521_aix5L_copy_cd.ksh and here it is

Code:

#!/usr/bin/ksh

if [[ “`echo $MDA_UPDIR`” = “” ]]; then
   export MDA_UPDIR=/upgrade
fi

me=`whoami`

if [ “$me” != “root” ]; then
 echo “$0 must be run as root”
 exit 1
fi

echo “”
echo “insert CD-Rom into drive and hit continue”
echo “”
read xyZ

rm -rf $MDA_UPDIR/521_aix5L_copy_of_install_cd
mkdir  $MDA_UPDIR/521_aix5L_copy_of_install_cd

mount -v cdrfs -r /dev/cd0 /cdrom

tar_tar_dir /cdrom $MDA_UPDIR/521_aix5L_copy_of_install_cd

unmount /cdrom

echo “”
echo “remove CD-Rom from drive”
echo “”

Here is the tar_tar_dir script that gets called and is also very handy indeed:

Code:

#!/usr/bin/ksh

# Begin Module Header ==============================================================================
#
#——
# Name:
#——
#
# tar_tar_dir
#
#———
# Purpose:
#———
#
# Copy an entire directory tree with all files and links to another base directory
# using the tar command
#
# Notes:
#——-
#
# This script is nice because it pipes the output of one tar command to another,
# which requires a little bit of temporary memory.
#
# Example of normal usage:
#
# cd $HCIROOT
# tar_tar_dir ./test_picis /3.5.2P_picis
#
#———
# History:
#———
#
# 1999.10.29 Russ Ross
#          – wrote initial version
#
# End of Module Header =============================================================================

(cd $1 && tar -cf – .) | (cd $2 && tar -xBf -)

Russ Ross
RussRoss318@gmail.com

[Max Drown (Infor)]

Russ, I like the way you think.  😀

-- Max Drown (Infor)

[Russ Ross]

Max Drown thanks for those kind words.

Often I ponder sharing all the upgrade/install scripts with others on clovertech because of the amount of well thought out work these scripts encapsulate and how wonderfull this upgrade/install technique has worked.

Unfortunately, there is too much taylored made site specific stuff for me to consider posting them on clovertech thus far.

However, one very usefull technique I can share and have come to love is the use of symbolic links to help keep the order of what needs to be run next straight.

With so many modules needed to do an auto-pilot upgrade I could not keep them straight until I resorted to the use of symbolic links to act as a table of contents.

For example if I look at my most challenging upgrade when I went from 355 to 381 to 521 in one upgrade here is the link listing to help illustrate what I’m talking about.

I got the following list of symbolic links as follows:

alias ll=”ls -al | grep ^l | colrm 1 57″

ll flow_00.00 -> ========== do thes once to prepare for iteration ==========

flow_00.01 -> 352_rmfs.ksh

flow_00.02 -> 381_copy_cd.ksh

flow_00.03 -> 521_aix433_copy_cd.ksh

flow_00.04 -> 521_aix5L_copy_cd.ksh

flow_00.05 -> 355P_at_check_for_gdbm.ksh

flow_00.06 -> 355P_tar_data_dirs.ksh

flow_00.07 -> 355P_link_data_dirs.ksh

flow_00.08 -> 355P_check_data_dirs.ksh

flow_00.09 -> 355P_mkdir_bitmaps.ksh

flow_01.00 -> ========== start of iteration ==========

flow_01.00m -> 355_mda_cloverleaf_IPL_make_scripts.ksh

flow_01.01 -> 355C_at_copy_355P.ksh

flow_01.01c -> 355P_do__check_sites.ksh

flow_01.02_xx -> 355C_mk_fix_proc_dirs.ksh

flow_01.03_xx -> 355C____fix_proc_dirs.ksh

flow_01.04_xx -> 355C_mk_fix_links.ksh

flow_01.05_xx -> 355C____fix_links.ksh

flow_01.06_xx -> 355C_mk_fix_bak_dirs.ksh

flow_01.07_xx -> 355C____fix_bak_dirs.ksh

flow_02.00 -> ==========

flow_02.01 -> 381_install.ksh

flow_02.02 -> 381_hcirootcopy.ksh

flow_02.03 -> 381_at_convert.ksh

flow_02.04_xx -> 381_mk_fix_links.ksh

flow_02.05_xx -> 381____fix_links.ksh

flow_02.06_xx -> 381_mk_fix_bak_dirs.ksh

flow_02.07_xx -> 381____fix_bak_dirs.ksh

flow_02.08_xx -> 381_start_host_server.ksh

flow_02.09_xx -> 381_kill_host_server.ksh

flow_02.10 -> 381_do__check_sites.ksh

flow_03.00 -> ==========

flow_03.01 -> 521_install.ksh

flow_03.02 -> 521_lic_convert.ksh

flow_03.03 -> 521_overwrite_hcisetenv.ksh

flow_03.04 -> 521_overwrite_hciconnstatus.ksh

flow_03.05 -> 521_hcirootcopy.ksh

flow_03.06 -> 521_at_convert.ksh

flow_03.07 -> 521_at_sdiff_tps.ksh

flow_03.08 -> 521_link_data_dirs.ksh

flow_03.08c -> 521_check_data_dirs.ksh

flow_03.09 -> 521_mk_fix_proc_dirs.ksh

flow_03.10 -> 521____fix_proc_dirs.ksh

flow_03.11 -> 521_mk_fix_links.ksh

flow_03.12 -> 521____fix_links.ksh

flow_03.13 -> 521_make_links_for_mda_global_tclprocs.ksh

flow_03.13c -> 521_check_links.ksh

flow_03.14 -> 521_mktclindex.ksh

flow_03.15 -> 521_mk_fix_bak_dirs.ksh

flow_03.16 -> 521____fix_bak_dirs.ksh

flow_03.17 -> 521_restore_stuff_to_keep.ksh

flow_03.18 -> 521_netfix.ksh

flow_03.18s -> 521_do_sdiff_netfix.ksh

flow_03.19 -> 521_at_netcheck.ksh

flow_03.20 -> 521_at_find_standalone_tcl.ksh

flow_03.21 -> 521_do_fix_standalone_tcl.ksh

flow_03.22 -> 521_at_find_standalone_perl.ksh

flow_03.23 -> 521_do_fix_standalone_perl.ksh

flow_03.24 -> 521_install_patch_rev2.ksh

flow_03.24c -> 522_do__check_sites.ksh

flow_03.24h -> 522_do_hide_alerts.ksh

flow_03.24s -> 521_fix_site_shutdown_startup.ksh

flow_03.24t -> 522_rm_standalone.ksh

flow_03.24u -> 521_make_links_for_mda_global_tclprocs.ksh

flow_03.24v -> 521_mktclindex.ksh

flow_03.24z -> 522_hciverify.ksh

flow_03.25 -> 521_start_host_server.ksh

flow_03.26 -> ========== prepare to do anoterh iteration ==========

flow_03.27 -> 521_kill_host_server.ksh

flow_03.28 -> 521_mk_stop_start_scripts_for_all_sites.ksh

flow_03.29 -> 521_shutdown_cloverleaf.ksh

flow_03.30 -> 521_backup_stuff_to_keep.ksh

flow_04.00 -> ==========  might not ever get used ==========

flow_04.01 -> 521_aix5L_install.ksh

flow_04.02 -> 521_aix5L_lic_convert.ksh

flow_04.03 -> 521_aix5L_overwrite_hcisetenv.ksh

flow_04.04 -> 521_aix5L_copy_sites.ksh

flow_05.00 -> ========== go-live switch over ==========

flow_05.01 -> 355_mk_stop_start_scripts_for_all_sites.ksh

flow_05.02 -> 355_shutdown_cloverleaf.ksh

flow_05.03 -> 355_do_hide_alerts.ksh

flow_05.04 -> 522_do_unhide_alerts.ksh

flow_05.05 -> 522_check_alerts_hciguimsg.ksh

flow_05.06 -> 522_check_error_database.ksh

Russ Ross
RussRoss318@gmail.com

[Max Drown (Infor)]

Code:

mount -o loop /data/downloads/QDX_5.5_Linux.iso /mnt/iso/
/mnt/iso/linux.bin -console

Code:

         Initializing Wizard……..
         Launching InstallShield Wizard……..

Environment variable DISPLAY is set to localhost:10.0

——————————————————————————-
Welcome to the InstallShield Wizard for CLOVERLEAF(R) Integration Suite

The InstallShield Wizard will install “CLOVERLEAF Integration Suite” on your
computer.
To continue, choose Next.

“CLOVERLEAF Integration Suite”
Quovadx
http://www.quovadx.com

Press 1 for Next, 3 to Cancel or 5 to Redisplay [1] 1

Script crashes here. I.e., returns to command line. There are no error messages of any sort. It just … exits.

-- Max Drown (Infor)

[Russ Ross]

Okay Max I will go ahead and post my 521_install.ksh script to point out some of the gotchas that might be effecting you.

Remember you will not be able to blindly run the script at your site.

#!/usr/bin/ksh

if [[ “`echo $MDA_UPDIR`” = “” ]]; then
[code]#!/usr/bin/ksh

if [[ “`echo $MDA_UPDIR`” = “” ]]; then

Russ Ross
RussRoss318@gmail.com

[Author]

Replies