Wednesday, September 26, 2012

Installing IM 2.0 on Vanilla CentOS 6.3

Following up this post, I've decided to go ahead and post the current versions of all my scripts.  I should explain a little about my environment.  I have the VM's setup cloned off a vanilla* CentOS 6.3 64-bit installation.  They each use DHCP to get their IP addresses from a DHCP server that has reservations to they always use the same IP addresses.  On the same network I have a web server that hosts the installers for CAPC, IMDA, & IMDR.  So, I've written scripts that will download the installers, run all the pre-requisites and checks and run the installers.  The scripts are here, here, here, here, here, & here. They are not up to date with the current installer. They will need to be modified to work properly with the current installer.

Here's how I use them: - this is not really a script, just a text file containing the bootstrap commands to kick off all the other scripts.  I copy and paste from this script into the ssh session.  Each section should be clearly commented as to what it does.  The password to get into my server is masked, but it wouldn't work on your network unless your server were a clone of mine anyway.  Modify as you wish.  I couldn't get the PC to talk to the DA without disabling the firewalls, so that's at the top.  I usually disable the firewalls on all of them and will probably build that configuration into my base image in the future. - this script gets everything ready for the Data Repository installation.  These are basically all the commands that are run as root. - this script contains the commands that the dradmin user needs to execute.  This one requires manual intervention at 4 places, so I've documented what I do at each stop. - this one installs the Data Aggregator - this one installs the Data Collector - this one installs Performance Center

I think that might be all.  So i'm going to leave it at that for now.  If you've got any suggestions on how the scripts could be improved, let me know.

*Vanilla=updates applied and startup mode changed to console only
This may be the source of other problems since the linux host file doesn't actually have the IP address in it.