===============================
==  CHALLENGE UPLOAD ROUTINE ==
===============================

"UPLOAD DOCUMENT TEMPLATE" SET-UP

Copy the challenge.dot file into the MS Office /templates directory.
You can now create Word documents based on this template.

CREATE CHALLENGE DOCUMENT IN MS WORD

(1) Launch MS Word and create a new document based on the challenge template.
(2) The document contains default text for all of the challenge data, modify these as required.
(3) Save the document as a Word document if you intend on editting this file in the future.
(4) When finished, save the document as an HTML file ("File | Save as HTML"). Choose any name for it.
    (After you save it, it will reload itself in HTML format- ignore and do not modify the special codes that suddenly appear.
    Furthermore, never load this HTML file into Word, always edit a saved Word document version of the challenge document.)

UPLOAD CHALLENGE ROUTINE

(1) Launch the HyperLearning site and log in as an author.
(2) Choose a course to edit and create a new challenge.
(3) Choose the "offline" upload routine.
(4) Tell the system the path and file name of the HTML file you previously saved and click upload.
(5) The system will respond by echoing the data it was able to extract from the uploaded file.
    You can then choose to edit, or view the challenge.  
    You may need to make further refinements to the challenge that are only available through the on-line editting routine.

=================
==  MIGRATION  ==
=================

These are the steps required to migrate the HL site from one web server machine to another.

(1) Copy the Web+ scripts.  
All of the Web+ scripts are kept in the Web+ logical path "/hl/".  Copy the contents of that directory to a corresponding directory on the new machine.  Be sure that there is either an inherent, or implied mapping from "/hl/" to the physical path where these scripts are kept.

(2) Copy the HTML and image files.
All HL HTML/images files are kept in the web server's "/hl/" logical path.  Copy the contents of that directory to a corresponding location on the new machine.  Be sure that the web server's "/hl/" logical path matches the new physical path.

(3) Add the two data sources to the ODBC manager.
"HL" and "HL_Log" located in the Web+ logical directory as "/hl/hl.mdb" and "/hl/hl_log.mdb" should be added to the ODBC manager as data source names "HL" and "HL_Log" respectively.

(4) Add the two data sources to Web+.
Using the Web+ Server Manager, add the "HL" and "HL_Log" data sources.  Be sure to re-start the Web+ Server.

(5) Edit settings.wml
The setting.wml file, in the logical "/hl/" directory, should be editted.  Set the "rpw" and "wpw" variables to the Web+ read and write password for the logical "/hl/" directory.  Set the "htmlRoot" variable to the phsyical path of the HTML root directory on the new web server.

(6) Add Web+ logical path "/html/".
Add a file I/O mapping in the Web+ server manager such that "/html/" is set to the new web server's physical HTML root directory.

TESTING THE INSTALLATION

(1) Log in as an administrator.
(2) Go to "Admin | Element Maint"
(3) Upload a graphic element (prepend its name with a few "z"s so it always appears at the bottom of the list).
(4) View your new element. If it works, then you can conclude that the database integration, and the upload routine works correctly.
(5) Delete your element.

If the element does not appear in the list after your upload it, the web server may not be handling uploaded files correctly.
If, when trying to view the element, you see a broken image icon, check to see if the actual eXXX.gif file exists in the /elements directory.
        If it does, and if it has the correct file size, check the FILE I/O mapping for /html.
        If it does not, or if it has a file size of 0, the fault may be in the web server's handling of uploaded files.

=================================
==  FIRSTNAME, LASTNAME FIASCO ==
=================================

If the firstName and lastName fields of the Users table is blank, this SQL statement will populate them based on the realname field.

UPDATE users 
SET lastname = RIGHT(realname,DATALENGTH(realname)-CHARINDEX(' ',realname)),
firstname = SUBSTRING(realname,1,CHARINDEX(' ',(realname + SPACE(1)))-1)
WHERE (firstname='' or firstname=NULL) and (lastname='' or lastname=NULL)

==========================
== DUMP TRANSACTION LOG ==
==========================

If the transaction log should fill up, here's the SQL command to dump it without backup.

DUMP TRANSACTION hl WITH NO_LOG