Still in the crusade for trying to have a really generic Windows VM image (and in the Win2003R2-32, Win2003R2-64 and Win2008-64 flavors), my thoughts on a methodology. Anyone wish to comment?
Standard Windows install for modular VMware installs:
virtual disk 1 – c:\ drive – windows
1/ Install base OS (Windows 2003 R2 SP2 both 32- and 64-bit and Windows 2008 SP2 64-bit) + all OS patches
2/ Install base tools on these OSes: Java6, Notepad++, GVIM, Office 2007, DUmeter, Baretail, etc and a yet-to-find open source tool with functionality like Araxis Merge or UltraCompare – ideas?
3/ export registry once all software is installed and configured
virtual disk 2 – d:\ drive – database
virtual disk 3 – e:\ drive – appserver + application directories
virtual disk 2 – f:\ drive – data
4/ create the three virtual disks above
5/ install each of DB2 V9.5, Oracle 10g, and Oracle 11g and an initial (empty) application database one at a time (the database CAREFULLY installed on the f:\ drive in an appropriately named directory, ie. f:\database\db2v95\DBNAME_versionname or f:\database\ora10g\DBNAME_versionname or f:\database\ora11g\DBNAME_versionname)
– perform registry export each time – preferable using a tool that captures the delta between the registry export from step 3
The purpose here is that we could have 3 versions of the d:\ drive (one for each database) with one base OS where we have all three registry variations imported but all Windows services in Manual mode. This allows us to run any of the installed database (installed meaning I mounted one of the three d:\ drives with the corresponding database)
6/ install both Tomcat (no registry values here) and WebSphere on the e:\ drive and export the registry (for the WebSphere mods as above for the databases
Now we have a structure for any DB or AppServer.
7/ In the e:\ drive, we install the panapoly of “basic” application software
8/ We now do the war/ear deployment, etc
9/ Start application and setup ALL the external file store locations to be on the f:\ drive under f:\store\versionX\
In deploying the VMs, we use host-only networking and IP port-forwarding to avoid and necessity to change hostnames when running under VMware Workstation.
For the various demo environments, we just need to a DB2 or Oracle export and place the external file stores in the f:\ drive in the appropriate directories.
Now we have a modular environment for the AppServer and Database.
For 3rd party apps -> into a separate VMware.
Note also that with this structure, you replace the e:\ drive with a dummy vdisk and now the installation is a database server and you can separate the DB and AppServers.