 |
|
|
|
|
 |
|
|
|
|
|
|
|
|
|
|
Xtential has significant experience in integrating and migrating Web sites to existing sites and Web infrastructures. We were the primary vendor in charge of integrating Cascade Communication's Internet, Intranet and Extranet sites with Ascend's systems infrastructure including database systems, application servers and Web sites. In addition, we are part of the integration team for Ascend and Lucent's recent merger.
Xtential will address version control, site rollback, server deployment and asset tracking. Using our experience, process, methodology and enterprise development platform along with Interwoven's TeamSite and OpenDeploy products, Xtential delivers enterprise site migration solutions. Xtential is the NY professional services division for Interwoven. In addition, Xtential uses Teamsite for its own Enterprise Development Platform. Further details can be viewed at http://www.interwoven.com.
General Procedure
1. Site Analysis
- Determine platform dependencies. For example, Active Server Pages on NT, JavaServer Pages on Solaris, Microsoft IIS and Netscape Enterprise-specific search functions and/or database content.
- Determine general functionality (non-platform specific). For example, Web-based forms that call a Perl script for processing and emailing. This is important for consolidating script usage across sites.
- Develop functional specification documents for platform and non-platform specific functionality, so that these functions can be replicated on the target platform or platforms.
2. Content Aggregation
- Perform orphan analysis for each site, to "clean up" unused content
- Archive each site up individually, preserving file structure
3. Target Servers Set-up
- Assumes environment of staging and production servers
- Install and configure TeamSite application (if used)
- Prepare file systems for incoming content
- Set up hardware or software virtual servers for each document root and/or domain name
4. Content Migration
- If version control system used, unpack and import files into system
- Create a branch for each site
- Create an edition for each site (read only snapshot of current site)
- Deploy to production servers
- If version control system not used, transfer tar files and unpack in appropriate directories
- Deploy (ftp or copy) to production servers
- Replicate Web authentication schemes (if any exist)
- Set up access control lists
- Password-protect directories
- Replicate functionality
- Set-up common scripts and secure CGI directories
- Implement functionality to meet functional specification documents
- Set-up search engines and re-index content
5. Quality Control
- Run link checkers and HTML syntax checkers across every site
- Test every site from the platforms and browsers to be used
- Check for browser compatibility of HTML, JavaScript, etc.
- Check for correct authentication.
The exact procedure may differ depending on client's existing and target infrastructure, requirement for modifying and updating the content, and/or porting the content to different platform.
|
|
|
|
|
|
|
|
|
|
