|
Ramapo Masters of Science Tools and Concepts of Data Analysis: Dataweb Working Live (home) Overview | Working Live | Publishing a Backup | Messages While Publishing Overview: Working Live In most cases a web site developer creates a web site and then uses ftp to transfer that site to a web server. This is a normal work flow. Those using FrontPage may take advantage of its publishing feature to transfer their sites if the destination directory on the server has been enabled with FrontPage Extensions. This is the method we have been using in this class up to this point. For those sites enabled with FrontPage Server Extensions, a third option exists which has some advantages when working with data collection sites. This method is referred to as "working live." When "working live" a user opens and edits the site directly from the server. There is no need to ftp or publish the work because it is being done on the server. The page must simply be saved and they are available to the world. To help those new to this concept, I ask that they imagine that the cables from their keyboard, mouse, and monitor are very long and plugged directly into the web server instead of their local computer. It is as if they are sitting at the server and creating the site on it. This method of working has several advantages when creating a site that collects data. First, since the way a page functions (ie- submits or displays data) can only be tested on the server, it speeds your ability to view the results of changes you have made. Secondly, since data submitted through a form is entered into the database file on the web server, it can be viewed, edited or deleted by opening it from the server. The copy of the database that may exist on your local machine or flash drive will not contain this data. Finally, additions or changes to the database itself are most easily handled by working in this matter. Working Live Open your FrontPage Web Open your browser and navigate to the root directiory of your site. In our case the folder name will always be "dataweb" so the path will resemble: "http://msetdata.rst2.edu/l/lastname_f/dataweb/". You may include or exclude the final forward slash after dataweb, but the address must end with either dataweb or dataweb/ Sometimes the address will be displayed with a code substituted for the underscore character (http://msetdata.rst2.edu/l/lastname%5ff/dataweb/). This must be corrected before copying the address (http://msetdata.rst2.edu/l/lastname_f/dataweb/).
To make this correction, erase %5f, replace it with
an underscore, hit the enter key
Copy the URL from the address box
Return to FrontPage | File | Open Site ("Open Web" in older versions)
Paste the address into the "site name" box at the bottom of the window | Open
You will be prompted for your username and password - enter them | OK
The site will open. Note the name of the top level directory in the left pain. It will begin with "http://" indicating that it is on a web server.
Publishing a Backup After completing a work session live on the server, it is a good idea to create a backup of your site. This is done using the publish feature we previously used but this time publishing the site from the server to your local computer. With your site open live on the server - File | Publish Site
Select the "File System" option button | Browse | Navigate to folder | Select Folder | Open
OK | Publish Web Site
Messages While Publishing During the publishing process you may receive a number of potentially confusing messages. The destination site is the site to which you are publishing while the local site is the site you have just updated. In virtually all cases you wish to make the destination site identical to the one you are publishing since it is the most recent and correct. The only exception would be if you accidentally deleted important files from your project. In this case you would try to recover them from the destination web before publishing again. Otherwise, the answers to all questions will indicate that you wish to update or overwrite the site destination site. Examples are shown below. If you have previously published the site but made changes to certain pages, the following box may appear asking if you wish to overwrite the old copy. The copy you are publishing should be the most most up-to-date copy. If so, click "Overwrite Remote Files"
This is a generic warning notifying you of the inherent dangers of posting data to the Internet. Click "Ignore and Continue."
This message indicates that these asp pages will not function from the destination to which you are publishing. They are not broken. They were simply not meant to work from a local computer or flash drive (ie - You can not submit data into a database from your local computer). If republished to the web server, they would function correctly.
If you have delete files from the destination site or renamed a file on either site, you may receive this warning. Choose "Yes to All" to make make the destination site identical to the one you are publishing.
Site Designed and Maintained by rsciorra |
