Publish Web Sites Developed in MS Front-Page


Publish Web-Sites Developed in MS Front-Page
	The Challenge: Publish web sites developed in MS Front Page to IIS or Apache web servers, running on Windows or UNIX platforms, without having to install Front Page Server Extensions on the web server. Front Page _vti_ files and directories should not be copied, as they tend to double the size of the web site and are unnecessary on the published web site. The user should have the ability to schedule the publishing to run unattended, publish only the changed files, in a secured and reliable transfer, monitor the publishing process remotely and avoid server-time-out errors during transfer of very large web sites. Web site development can also take place in a number of places, by more than one developer. In that scenario, publishing the web site will be performed in stages: Transferring the updated files to a staging server Testing the web site at the staging server Publishing the complete web site to the "live" web server. It is required that the whole publishing process will be handled and monitored from any where in the network (either one of the servers involved in the replication or a completely different machine). The Solution: Publish Web Sites using RDS RDS as the publishing tool, overcomes the pit-falls related to publishing via Front Page: _vti_ files are excluded from the replication process Scales to handle very large web sites and huge replication trees Recovers automatically from any error during replication Avoid installing Server Extensions on the web hosting server Publish seamlessly to either IIS or Apache web servers RDS enables fast, scheduled replication and synchronization of files and directories over networks, regardless of content, volume, or production and networking environment, transparently replicating data between Windows and UNIX systems. This allows RDS to replicate Web sites developed in MS Front Page to any web server on any platforms, running IIS, Apache or any other web server. RDS supplies full control over the files being replicated or excluded from the process, ranging from entire volumes, folders, to individual files or file specs. MS Front Page _vti_ files and directories can be excluded from the replication process, thus avoiding corruptions of the published web site, and resulting in a reduced web site size, and therefore reduced transfer time. Using RDS as the publishing tool, Front Page Server Extensions are not needed on the web server, avoiding situations where the web server needs to be re-started. Publishing cycle time is kept to a minimum using RDS's Comparative Snapshot Technology (CST^TM) where only the changes are transferred. Using Differential Transfer options for large files, RDS supports block level updates of large files. RDS guarantees accurate and secured data transfer - encrypted and authenticated. Other features include control over network bandwidth usage, transparent compression of data sent over the network, and rich reporting capabilities. Using a staging server in the replication process, the whole process of collecting data from the development site to the staging server, and then publishing the site to the "live" web server, can be initiated and monitored from a central location. TOP
	RepliWeb, Inc., All Rights Reserved. \| Knowledge Base \| Support \| Home


		More Solutions...

		Web Deployment
		Data Distribution
		Large-scale Data Migration
		Replacing Site Server
		Cross Platform Distribution
		Cascaded Replication
		Content on Demand
		Offsite Backup
		Publish Web-Sites Developed in MS Front Page
		Replicate Oracle Archive Logs
		Scheduled Distribution using Batch Scheduler
		RepliWeb vs. Protocol-Based Solutions
		Consolidating R-1 Jobs
		GlobalSite Replacement using R-1
		Middle-Mile Content Deployment

Publish Web-Sites Developed in MS Front-Page