⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 readme.htm

📁 开源的e-learning系统。Java环境
💻 HTM
📖 第 1 页 / 共 2 页
字号:
the Path of the context which you defined in the previous step.  Find
the definition     of parameter <i> CourseContent</i><i>DocumentBase</i>
and replace the existing value with    the value of the <i>Document Base</i>
parameter of the context you defined in the previous step<i>. &nbsp;</i>The
entries    should read something like this:</li>
                                       
  <pre>      	&lt;!-- Parameters for interacting with webapp context for course content data. --&gt;<br>	&lt;context-param&gt;<br>			&lt;param-name&gt;CourseContentContextPath&lt;/param-name&gt;<br>			&lt;param-value&gt;/Courses&lt;/param-value&gt;				<br>	&lt;/context-param&gt;		<br>	&lt;context-param&gt;<br>			&lt;param-name&gt;CourseContentDocumentBase&lt;/param-name&gt;<br>			&lt;param-value&gt;C:\LMS\Courses&lt;/param-value&gt;				<br>	&lt;/context-param&gt;<br></pre>
          	<li>Under the <i>%CATALINA_HOME%\webapps\Flimsy\WEB-INF\config</i> 
  directory    you will find a properties file called <i>log4j.properties</i>. 
  &nbsp;Find   the definition  of property <i>log4j.appender.consoleLogFile.File 
      </i>and   replace the existing value with  the directory where you want
  the log files   to go. For example <i>c:\LMS\logs</i>. Do the same thing
 for the properties       <i>log4j.appender.modelLogFile.File</i> and   
 <i>log4j.appender.configLogFile.File</i>.     Note you must create any directories
that you specify but not the actual     log files themselves.     <br>
          Save the file and copy it to the directory you specified in CATALINA_OPTS 
    above.</li>
                       	<li>This step is only if you changed the name of
the   war   file in <u>step 4</u>. &nbsp;Assuming you are using the name
    <i>AEL            </i>for your context, then you must now perform the
following steps:</li>
                                           
  <ol>
                            <li>In the file <i>lms\LMSFrame.jsp</i> find
the   definition for   the        <i>com.rubecula.flimsy.scorm.APIAdapterApplet</i>
 and replace              <i>Flimsy </i>by <i>AEL </i>in each of five occurrences:</li>
                                                                 
    <ol>
                 <li><i>codebase </i>(should now read: <i>&lt;param  name 
=  "codebase"    value = "/AEL/lms" &gt;</i>)<br>
                   </li>
                 <li><i>context </i>(should now read: <i>&lt;param  name
=  "context"    value = "/AEL" &gt;</i>)</li>
                 <li><i>codebase </i>(should now read: <i>codebase="/AEL/lms"</i>)</li>
                 <li><i>src </i>(should now read: <i>src="/AEL/lms"</i>)</li>
                 <li><i>context</i> (should now read: <i>&lt;param  name
=  "context"    value = "/AEL" &gt;</i>)</li>
                                                                 
    </ol>
               <li>In <u>step 23</u>, ensure that the bookmark that you create
   will  actually point to <i>http://localhost:8080/AEL/lms/LMSMain.htm</i>
   instead  of the default value.</li>
         <li>If you made changes according to <u>step 11</u>,  and want to
 arrange for logging to go to different places, you must change  the<i> log4j.properties</i>
 file as appropriate.<br>
         </li>
                                           
  </ol>
             <li>Now unpack <i>hsqldb_1_7_2_4.zip</i> into either the top-level 
  or  the       <i>\LMS </i>directory. In your System Environment, set up
 the environment variable DB_HOME to have the appropriate value,  for   
example,      <i>DB_HOME=c:\LMS\hsqldb</i>. </li>
                  <li><font color="#ff0000"> Put the six components of  the 
release into the LMS directory (see above under <b>Installation of Server</b> 
for details of the six), unzipping as necessary [or you may put them in some 
other place].</font><br>
              </li>
       <li>Startup the HSQLDB Server as follows (note  that if you want 
 multiple   copies of the server running on different ports,  you must edit 
the <i>startDb   </i>script appropriately; see also <a
 href="http://hsqldb.sourceforge.net/doc/hsqlAdvancedGuide.html"><i>http://hsqldb.sourceforge.net/doc/hsqlAdvancedGuide.html</i></a>).: 
                                                                     
    <pre>    \LMS\bin\startDb.bat   </pre>
               </li>
               <li>Startup the HSQLDB Manager as follows:               
                                                 
    <pre>    cd %DB_HOME%<br>    java -cp lib\hsqldb.jar org.hsqldb.util.DatabaseManager<br></pre>
               When the program starts up, choose the third connection type 
 "HSQL    Database  Engine Server" and leave the other parameters unchanged. 
 &nbsp;Click    OK.</li>
              <li> Depending on whether this is  an upgrade or a new install,
 you  will choose different options:</li>
                               
  <ol>
            <li>If this is a new install (i.e. you have no current data to
 save):    &nbsp;load the four scripts from the database directory (see <u>step
 14</u>)   in the following order: <i>CreateTables.sql, CreateViews.sql,
Model.sql,    PopulateTables.sql</i>.  &nbsp;If this is not your first attempt
at a new    install and thus you have existing tables which you need to delete, 
you  should  first drop all tables and views using the scripts <i>DropViews.sql</i> 
 and        <i>DropTables.sql</i>.</li>
            <li>If you are upgrading from version 1.2 to 1.3: then only load
  one  script: &nbsp;<i>Model.sql </i>(do NOT drop any tables or views as
this  will  result in lost data).</li>
        <li>If you are upgrading from any version to 1.4,  the note that
you  must be using HSQLDB 1.7.2.4 and the upgrade procedure is quite complex
(see        <a href="files/Flimsy_1_4_Upgrade.html">Flimsy_1_4_Upgrade.html</a>).</li>
    <li>In fact, it's always safe to perform a <i>DropView.sql</i> followed
by <i>CreateViews.sql</i>. &nbsp;Sometimes, there is no true model change,
but yet views might have changed so it's a good idea to do this always.<br>
    </li>
                               
  </ol>
              <li>Now create an empty directory called <i>Courses </i>in
    <i>%CATALINA_HOME%\webapps\Flimsy</i>       (note that this directory
will have been created by Tomcat itself when    you  first started it up.</li>
              <li>If necessary, create a directory called <i>"c:\Temp\Upload"</i>
 (this  will be used by the   course upload command) <font
 color="#ff0000">[you can vary this directory in the next step, substep 9).</font></li>
         <li>[Optional step: only if you need to change  the  configuration
 from its defaults]: &nbsp;As possibly in <u>steps 10 and  12</u>, open 
the      <i>%CATALINA_HOME%\webapps\Flimsy\WEB-INF\web.xml</i> file  in a
text  editor (or, better, an XML editor such as XMLSpy). &nbsp;The following
 configurations   are currently available:</li>
                           
  <ol>
           <li><i>UseridMode</i>: &nbsp;(default: "implicit") &#8211; if you want
 a field on the AddUser form to allow you to specify an explicit   id for
your users, then change this value to "explicit";</li>
           <li><font color="#ff0000"><i>adminDebug</i>:&nbsp; &#8211; no longer 
used.</font></li>
                   <li><i>DriverName</i>: &nbsp;(default: "org.hsqldb.jdbcDriver")
 &#8211; change this if your database is not HSQLDB;</li>
           <li><i>ConnectionURL</i>:&nbsp; (default: "jdbc:hsqldb:hsql://localhost:9001/lmsdb") 
 &#8211; change this to point to the correct database;</li>
           <li><i>UserID</i>: &nbsp;(default: "sa") &#8211; this  allows you to 
explicitly set the name of the system administrator account   for the database;</li>
           <li><i>Password</i>: &nbsp;(default: &lt;empty&gt;)   &nbsp;&#8211;
this  allows you to explicitly set the password of the system administrator
  account  for the database;</li>
      <li><font color="#ff0000"><i>CourseLifetime: </i>(default: 0) &#8211; this
 allows you to explicitly set the default lifetime of a newly added course;</font></li>
      <li><font color="#ff0000"><i>MaxUploadBytes: </i>(default: -1)  &#8211; this
 allows you to explicitly set the maximum size of an upload in bytes (-1
denotes  no limit - be careful you don't suffer a denial-of-service attack);</font></li>
      <li><font color="#ff0000"><i>UploadLocation: </i>(default: <i>/Temp/Upload</i>, 
which is equivalent on a Windows machine to: <i>c:\Temp\Upload</i>)  &#8211; this 
allows you to explicitly set the directory into which uploads will be copied 
(see step 19);</font><br>
      </li>
                           
  </ol>
              <li>If you plan to print "diplomas" for students then you will
 have to edit other parameters in <i>web.xml </i>(see previous step):</li>
           
  <ol>
       <li><i>CompanyName: </i>the name of the Company;</li>
       <li><i>GrantorName: </i>the name of the grantor of diplomas;</li>
       <li><i>GrantorTitle: </i>the title of the grantor of diplomas;</li>
       <li><i>CompanyLogo: </i>the image file to used for the company logo
 (for example:<i> images/CompanyLogo.gif</i>);</li>
       <li><i>GrantorSignature: </i>the image file to used for the grantor's
 signature (for example:<i> images/GrantorSignature.jpg</i>).<br>
       </li>
           
  </ol>
     <li>Finally, go back to your tomcat command window and once again  
start    it up (see <u>step 6</u>).<br>
              </li>
               <li>Now open the following file (using <i>File/Open</i> or 
    <i>ctrl-o</i>):           <i>%CATALINA_HOME%\webapps\Flimsy\files\Flimsy.html</i> 
and then  click    on the link contained therein. Make a bookmark (favorite). 
Alternative:    instead   of opening the file, clicking and making a bookmark, 
you could   just import   the file as a bookmark (favorites) file. Now whenever 
you want  to open the   LMS, you can just click on the link. </li>
                         
</ol>
                                  
<p>The installation should now be complete. </p>
                         
<h2>Running </h2>
                         
<p>Flimsy is run as a web application via a browser. Although Flimsy itself
      will run under Netscape, you will not be able to launch the TRA content
    unless  you use Internet Explorer as your browser. Once you have followed
    the link  you should see the Login screen. Enter your first and last
names     and your  password. You should now be taken to a screen whose contents
 will   vary according  to the roles you play in the LMS. Managers and Administrators
    get more permissions  than Students, for example.<br>
            <br>
            As an administrator, you may add courses. &nbsp;The data for
a  course may exist either on the server or in a zip file on your client
system.  &nbsp;In the former case, click on <i>Add   course</i>, in the latter
case,  click on <i>Upload course. </i>&nbsp; There   must be a preexisting
curriculum  for you to associate with the new course.   &nbsp;If uploading,
then first  upload the zip file (use the Browse button   to find it &#8211; the
upload can take some time) then associate it with the curriculum.  &nbsp;If
referencing data already on the server, enter the pathname of the  manifest
file and the curriculum name.<br>
             </p>
                         
<p>If you are a self-registering student and you want  to register for a course,
click on <i>Register  for Course</i>. Follow the  instructions. &nbsp;Otherwise, 
   you must request your manager (or an administrator)  to register you for 
  a course. </p>
                         
<p>In order to play a course unit, click on <i>View registered courses</i>. 
      You will see a list of courses you are registered for. Click on the 
<i>View      Units</i>link next to the course you want to work on. Now you 
will be  presented   with a list of units. Click on the <i>Launch</i> button 
next to the unit  you wish to launch. You can take the units in any order, 
but they will be  shown in the recommended sequence. The unit (also known 
as a SCO) will now  play. </p>
                         
<p> </p>
                         
<h3>Creating reports for Excel </h3>
                         
<p>You can create reports for Excel if you are an administrator or manager.
      Simply click on the <i>Export</i> button and choose  which table you
 wish  to export.  The resulting file which will be downloaded  to your own
 machine  is in CSV format can be opened by  Excel or loaded into  another
 database  that accepts <i>csv</i> files.  Note that these are raw files
from  the various  tables/views.  </p>
             
<h2></h2>
     	  	                 
<h2>Known Bugs and Limitations</h2>
                         
<p>Bugs are now tracked by Bugzilla. If you are on the TRA network, you can 
   access the bug list <a
 href="http://10.12.1.49/bz/buglist.cgi?short_desc_type=allwordssubstr&amp;short_desc=&amp;product=Open+LMS&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;emailassigned_to1=1&amp;emailtype1=substring&amp;email1=&amp;emailassigned_to2=1&amp;emailreporter2=1&amp;emailqa_contact2=1&amp;emailcc2=1&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;changedin=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">here</a>.
     </p>
                 <br>
          <br>
       <br>
      <br>
     <br>
    <br>
   <br>
  <br>
 <br>
</body>
</html>

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -