We've had an existing site that has been built and deployed to for awhile now, mostly an internal beta site at http://beta.site.com which has been built up with an extended site on http://beta.site.com:81 for Search Crawling. Now the people up above decided that they want to make the site http://www.site.com, which means Search may be moved to http://www.site.com:81. My problem is figuring out the best method to do this. Is it better to do either of the following:
- Rebuild the Web Application with a New URL
- Use Alternate Access Mappings to re-point the locations
Or, is there a better way to handle this? My concern is all the dependencies with the site, the Term Store, the extended site, any underlying URLs that need to be moved (which I believe we have all of). From a few places I have looked there doesn't seem to be a good consensus on how to do this, from How to Change URL Web Application Name the article mentions using AAM to handle the redirects - though its for 2007 it probably will work for 2010. Or in Change the SharePoint URL mentions extending the site, but since I already have it extended that seems overkill. I have a feeling its either going to be do an AAM or rebuild with the new URL.
Does anyone have thoughts or been through this?