Yes, it is true that WebSphere records the hostname into its config files upon installation. There is a helpful doc that explains which files you need to modify if you plan on changing the hostname:
http://www-1.ibm.com/support/docview.wss?uid=swg27005391&aid=1 You can either modify each of the files manually as described in the doc above, or you can automate it using the procedure Edmund MacKenty provided (we had a homegrown shell script that did this). You basically want to make a global change in /opt/WebSphere/AppServer to the new hostname (excluding binaries). We've just finished a test where we migrated middleware such as WAS v5.1/DB2 on SLES 8 31bit to WAS v5.1.1/DB2 on SLES 9 64bit. We are also in the process of publishing the results from the test in a customer report. From our experience, cloning DB2 Connect should be straight forward, once its cloned, you should simply change /etc/hostname to the new hostname and it should start. We recommend using the backup routines provided by the middleware: DB2 Connect - run the Configuration Assistant (CA) to export your client profiles and connections - your catalog entries. WAS - run the backupConfig.sh script to backup your config and application data. I'm not sure how much time you're really allowed, but we do suggest you do this in stages, and verify each clone works...even if it requires a slight outtage. Regards, Philip Chan [EMAIL PROTECTED] James Melin <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 09/27/2005 10:10 AM Please respond to Linux on 390 Port To [email protected] cc Subject Migrating a SLES-8 31 bit system to a SLES-9 64 bit system 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. 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. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
