Website Migration Project



Website Migration Project

Introduction

In order to build Web architecture, move an existing Website with minimal downtime, and provide a disaster recovery solution to ensure the site is always available; we will design a website for our company through system development life cycle. REST attempts to describe architectures that use HTTP or similar protocols by constraining the interface to a set of well-known, standard operations (like GET, POST, PUT, DELETE for HTTP). Here, the focus is on interacting with stateless resources, rather than messages or operations. Clean URLs are tightly associated with the REST concept.

An architecture based on REST (one that is 'RESTful') can use WSDL to describe SOAP messaging over HTTP, can be implemented as an abstraction purely on top of SOAP (e.g., WS-Transfer), or can be created without using SOAP at all.

WSDL version 2.0 offers support for binding to all the HTTP request methods (not only GET and POST as in version 1.1) so it enables a better implementation of RESTful web services. However, support for this specification is still poor in software development kits, which often offer tools only for WSDL 1.1. (Itten 2003 102)

Fig. 1 - New Architecture

Fig 2 - Web Architecture

Problem Statement

Lack of Automated Customer Sign Up and Support

The process between receiving a subscription for a web-hosting/email account and creating the account in the Domain Registry, DNS server, Email Server, FTP server, Web Server and any additional servers or systems is rarely automated. Often a sales rep has to take the customer information over the phone and manually enter it into a system. Next a tech administrator must retrieve the record form that system and manually enter it in each of the above servers (systems). Furthermore, if a customer wishes to modify certain items in his account(s) the same manual process has to be repeated. Such a process is not only time consuming and expensive but is also prone to errors.

Efficient Revenue Collection

Unfortunately, customers are often late with their payments. Furthermore, collecting on late payments is a costly venture involving many man-hours. Suspension of service is the only sure way to get payment from your customers, however, suspending and then re-enabling the services is a long process that often requires highly paid technical personnel to get involved. The Provider is caught in a dilemma: spend valuable resources on trying to collect revenues or give away free services.

How does this work again?

Because WebMerge builds a maximum of two-tiers at a time, it is necessary to work on tier-one first.  Once tier-one is completed, the last two tiers get built (see figure 2 below).

Two Steps - Two Settings Files

Two settings files are required to complete a three-tier design.  Each settings file is used to build one or two tiers, building more than two-tiers requires more settings files.  We start out by having WebMerge work on the Main Category Page, with our first settings file.  After that is complete, we have WebMerge build all of the Category Index Pages, and the Detail Pages with our second settings ...