James Melin writes:
>My intent is to clone the SLES-9 image that we have running using the
>techniques spelled out in the 'LPAR to virtual servers in 2 days'
book. ...
I've automated this very thing for WebSphere, and you're right: it buries
the hostname, the IP address and your domain name in various configuration
files. It also uses your hostname as a directory name a few times. You
can find all the configuration files with egrep(1), like so:
egrep -ril '111\.222\.111\.223|rayon|domain.com' /opt/WebSphere
and you can find all the directories with find(1) and egrep, like this:
find /opt/WebSphere -print | egrep -i 'rayon$'
You can do all this on the new system before you touch the production box,
and redirect the output to files so that you have lists of everything that
has to be changed. You then just edit all the files that first egrep
command listed, and rename the directories that find pipe listed. One
caveat: I know that this works for a just-installed WebSphere, I have not
tested this on a WebSphere that has applications set up within it. I would
expect that the applications would rely on the WebSphere configuration to
obtain host/IP data, but you never know.
> ... My
>specific situation is that I must take existing production systems, and
>create them as SLES-9 64 bit. The problem being is that I am not going to
>be allowed to incur much downtime. So If the production systems have an IP
>address of (for example - not real) 111.222.111.222 and a DNS name of
>Spandex and my new system for the sake of example, has a temporary IP
>address of 111.223.111.223 and a DNS name of rayon, it seems to me that I
>can do the cloning, test the base system. Where I come to some confusion is
>the best way to install things like, DB2 Connect and WebSphere. These have
>a tendency to record such things as the 'name' of the system and I think
>WebSphere even buries IP information in there some where.
>
>Has anyone managed to install WebSphere or DB2 Connect on a Linux guest
>with one IP address and system name/DNS entry and then change the server to
>a new IP address/System name/DNS name or is it best to migrate the base
>clone to the 'production' name and IP address during scheduled down time
>and do the software installation then? I think CVS will be relatively
>immune to these concerns.
If you want to get fancy, you can write a couple of Linux shell scripts
that take those lists as input, and do the editing and renaming for you.
With those, you could test the changes to make sure WebSphere still works
correctly after changing those files. For example, you could rename your
system to "nylon" at IP address 111.222.111.224, and then make sure that
WebSphere comes up properly at that name. You would then be able to
quickly rename it to Spandex using those same scripts, minimizing your
production down-time.
- MacK.
-----
Edmund R. MacKenty
Software Architect
Rocket Software, Inc.
Newton, MA USA
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
