Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Moving IW environment from 1 network to another?
System
Hello, i am really in need of some help here. due to performance issues with our architecture (long story), we need to move our whole IW production environment from 1 network to another in a very short time.
1) what is the best practice for this?
2) what all will need to be changed?
3) what issues should we look out for?
The server aliases should not be changing although their IP addresses & names will.
i.e. asnwsp03.fiasn.com
becomes
asnwsp03.fisn.com
i dont think IW uses hardcoded IPs anywhere throughout the config files or setup does it?
thanks in advance!
---------------------
Eric B.
Federated Investors
AOL IM: arthas76
Find more posts tagged with
Comments
Adam Stoller
There are a number of places within the iw.cfg and potentially in other configuration files, where hostnames and IP addresses might be used interchangeably - you're best bet is to rummage through ALL the files to find any occurrances of the hostname and/or ip address you are concerned about. If you're on Unix - a simple: find iw-home -type f -print | xargs egrep -n "hostname|ip\.add\.re\.ss" should work. If you're on Windows you can probably use Find (if you don't have Cygwin or similar installed).
I'd suggest expectations of at least 1 full day down-time and would recommend scheduling the switch-over to occur on a weekend if possible (assuming you get some credit for working over a weekend)
--fish
Strolling Prime Minister of no fixed address
BreakOnChange.dcpackage.zip
outputl.pdf
Migrateduser
fish you are the man, thanks. we are windows 2k so im stuck with the MS search (lame as it is)
so besides the hostnames and IPs there shouldnt be any other major issues or fail points when we switch networks? im most worried about our workflow which involves OD & DD
consultants set this all up for us thats why im a bit iffy...im sure you will be hearing more from me in the next couple days if/when we do the move.
thanks again...and unfortunately, no overtime fer us
---------------------
Eric B.
Federated Investors
AOL IM: arthas76
Adam Stoller
If the server name changes, I'm positive, but you may have some issues with local disk accounts (like Administrator and TSIMP_hostname) - but these should be fairly easy to resolve
--fish
Strolling Prime Minister of no fixed address
Migrateduser
This is a related article that might have useful tidbits, it also has references to other articles:
https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=2257
lissa
Migrateduser
we will be making the big move friday so hopefully you guys will be ready for some questions if/when we have problems!
---------------------
Eric B.
Federated Investors
AOL IM: arthas76
sourceSSD_XML.zip
978.pdf
ela
Hi, we'll move the disk to another server on friday, so it would be useful to hear if you experienced any problems with your move.
Many thanks in advance!
Eldbjørg
Migrateduser
yes we did...all users on domain did not come over correctly (which was to be expected)
after changing all the config files correctly, we still got an error trying to restart the teamsite service...
something none of the IW ppl mentioned to us was that we had to regenerate our license key!
RESOLUTION:
•License key in iw.cfg needed to be regenerated since it is domain-specific
Since the license key is domain and machine specific, any change in hardware will require a new license key for TeamSite to function. re-hosting will require a new license key - replacing Ethernet may require a new license key
When you run the TeamSite install program, you will generate a file called tslicinfo.log. You will find this file in your <iw-home>/install directory. Open this file.
**Note: If you are regenerating a license due to a validation failure, Please run the tslicinfo command located in <iw-home>/bin to create a new tslicinfo.log file. The full command is C:\iw-home\bin>tslicinfo -s -f c:\iw-home\install\tslicinfo.log
•Rebooted server
•ran iwreset-a, which automatically updated Apache config file
---------------------
Eric B.
Federated Investors
AOL IM: arthas76
OMR.png
ela
Thanks Eric, it confirmed what I expected! Hopefully I won't run into unexpected problems, then. That would be like X-Mas eve!;-)
Have a nice week!
Best regards,
Eldbjørg
ela
Had to update the list with:
/app/teamsite/iw-home/iwopenapi/openapi.cfg
Forgot to change the hostnames there, and searched a long while before figuring it out, but I'm happy now!