Well, I just got word that my IW servers are being physically moved to a new data center and, gee, would that cause any problems with your application?
This move is going to involve both a change in the servername as well as a change in IP address. I'd like to start a thread to create a check-list for stuff to look out for (both for selfish reasons, as well as to make the world a better place for our Interwoven children).
Here's my first pass of files that will need updating following a machine name change and ip address change:
- Change all the odnodes.xml files on all the FM target servers to "allow in" the new servername
- Get new licenses for the moving servers. . .not sure the old license keys will work
- Change the launch.jsp on IW dev to point to the new servers
- Change the OpenDeploy Administration server configuration to monitor the new names of servers
- ODHOME/etc/odbase.xml
- Client component
----------------
All TFO installations need to be reconfigured
What about launchpad??
- /etc/iw.cfg
----------------
iw.cfg:launchpad_hostname=re2unx113
iw.cfg:host=re2unx113.fhlmc.com
iw.cfg:customer_webserver_host=re2unx113.mydomin.com
iw.cfg:license_key=0251926exxxxxxxxxaa8452a56 * re2unx113 * 5.5.2 * thomas_vaughan@mycompany.com
iw.cfg:mailserver=re2unx113.mydomain.com
- IWHOME/conf/iwwa.cfg
- IWHOME/iwopenapi/openapi.cfg
- mnttab:re2unx113:/iwserver/default /iwmnt/default nfs vers=2,dev=4700003 1043564682
- mnttab:re2unx113:/iwserver/default /.iwmnt/default nfs vers=2,noac,dev=4700004 1043564682
- Documentation
--------------
Go through all documentation and make sure server names are updated
I'm worried about the clients, and I'm worried about any sort of compiled-in hostname that might be invisible to my greps within some jar file or installation directory.
Anyone have any experience with this or have anything to add?
Tom
