File:  [LON-CAPA] / doc / build / sles12_install.frag
Revision 1.3: download - view: text, annotated - select for diffs
Thu Jan 7 21:05:12 2021 UTC (16 months, 1 week ago) by raeburn
Branches: MAIN
CVS tags: version_2_12_X, version_2_11_X, version_2_11_4_uiuc, version_2_11_4_msu, version_2_11_4, version_2_11_3_uiuc, version_2_11_3_msu, version_2_11_3, HEAD
- Typo

<h1>Installing LON-CAPA on a minimal SuSE Linux Enterprise Server (SLES) 12</h1>
This document guides you through the process of setting up a new LON-CAPA
server running SuSE Linux Enterprise Server 12 (SLES 12) with a minimum of packages installed.
The computer will be configured solely as a LON-CAPA server and will be
expected to have no other services running.  Your server is expected to have
a reasonably fast connection to the internet.
More information is available at
<a href=""></a>.

<h2>Before you begin</h2>
Installing Linux is straightforward.
You will be required to log in to the machine and execute
some routine Unix commands.  Familiarity with the Apache web server, mod_perl,
perl, and MySQL are not required to install and run LON-CAPA.

<h2>Installation Overview</h2>
The installation process takes the following steps:
  <li><a href="#obt">Obtain SLES 12 installation media</a></li>
  <li><a href="#net">Determine Network Settings</a></li>
  <li><a href="#lin">Install SLES 12</a></li>
  <li><a href="#upd">Update your system</a></li>
  <li><a href="#ilc">Install LON-CAPA</a></li>
  <li><a href="#cdc">Create a Domain Coordinator</a></li>
  <li><a href="#sts">Start/Restart services</a></li>
  <li><a href="#log">Log in to LON-CAPA</a></li>

<h2>1. <a name="obt">Obtain SuSE Linux Enterprise Server 12</a></h2>
SLES12 ISO files can be obtained from the SuSE site: <a href=""></a>.  Download the SLE-12-SP5-Full-x86_64-GM-Media1.iso.

<h2>2. <a name="net">Determine Network Settings</a></h2>
You will need to know the following network settings for your installation.
<b>Note:</b>You must have a static IP address to use LON-CAPA.
DHCP is <em>not</em> supported.
  <li>ip address </li>
  <li>netmask </li>
  <li>hostname </li>
  <li>gateway </li>
  <li>domain name server(s) </li>

<h2>3. <a name="lin">Minimal SLES 12 Install</a></h2>
Installing SuSE Linux Enterprise Server is quite easy if you've installed Linux products
before.  Some documentation is available from
<a href=""></a>.<br><br>
Most of the installation screens are self explanatory.
There are a few steps that require comment and are dealt with below.
<dl style="list-style:square outside none">
   <dt>Installation Language</dt>
   <dd>Use English as your installation language.</dd>

   <dt>Partitioning your Drive</dt>
   <dd>For a LON-CAPA library server (i.e., the main server used
       for permanent storage of course and user data),
       a separate partition is recommended for /home, as this
       simplifies future upgrades of the operating system.
       If you are adding an additional access server to an
       existing LON-CAPA domain, this does not apply as no
       permanent data are stored on an access server.
       As LON-CAPA resource files are stored in the /home directory,
       the majority of the disk space should be allocated here.
       If you have 20 GB of space for SLES12, /home should
       receive at least 10 to 12 GB. Since MySQL uses the /var
       filesystem to store its databases you should have as least
       4 gigs of space available on /var.  Be sure to
       include adequate swap space.  A minimum is 512 MB, but you should
       typically have 1 or 2x as much swap space as you do physical RAM.
   <dt>Network Configuration</dt>
   <dd>LON-CAPA will <b>not</b> work with a machine set up to use a dynamic
       IP address.  When configuring your network card, you should include you static IP address, netmask, host name information (e.g., host name = tmp1, domain =, as well as name servers and gateway.
   <dt>Available Extensions and Modules</dt>
   <dd>Register the system with, and then check boxes for the following<ul>
       <li>SuSE Linux Enterprise Software Development Kit</li>
       <li>SUSE Package Hub</li>
   <dt>System Role</dt>
   <dd>Select: Default System</dd>
   <dt>Software Selection</dt>
   <dd>Customize by clicking "Software" on the Installation Settings screen
       Uncheck the boxes for "GNOME Desktop Environment" and X Window System.<br />
       Check the boxes for the following:<ul>
       <li>Help and Support Documentation</li>
       <li>Base System</li>
       <li>Minimal System (Appliances)  
       <li>YaST2 configuration packages</li>
   <dd>The following should be set on the Installation Settings screen:
     <li>Firewall will be enabled>/li>
     <li>SSH service will be enabled</li>
    If you will need command line access other than via the console, click the link to toggle the setting for the SSH port so it will be open.
Finish installing your server, reboot and log in as root.

<h2>4. <a name="upd">Add software sources for your system</a></h2>
Use zypper to add package repositories for LON-CAPA and the statistics package: R.<br />
zypper addrepo 'LON-CAPA'
zypper addrepo '' 'R-released SLE_12'
zypper refresh
Verify the required repositories are enabled:
zypper lr -E
The list of enabled repos should be as follows:
<table style="border: 0px; border-collapse: collapse;">
<tr><td>R-released SLE_12</td><td>R-released SLE_12</td></tr>
<h2>5. <a name="ilc">Installing LON-CAPA</a></h2>
<h3>Install prerequisites</h3>
<p> Execute: </p>
zypper in LONCAPA-prerequisites
This may take some minutes due to LON-CAPA's large number of dependencies.
<h3>Configure Firewall Settings</h3>
<p>After installing the prerequisites you should start yast, and select Security and Users -> Firewall. At step 2 include the following services: HTTP, HTTP with SSL, and Secure Shell.
<h3>Retrieve and execute LON-CAPA setup program</h3>
Retrieve the LON-CAPA setup with one of the following commands:
Extract the archive with the following command:
tar xf install.tar
This creates a directory named <tt>installation</tt>.  Change to it and
execute the setup script with the following commands:
cd installation
The script is used to prepare a Linux system to run LON-CAPA, and can also be
used to check the configuration of a system on which LON-CAPA has already been installed.  Typically, though, you will run this script only once, when you first install LON-CAPA.
The script will analyze your system to determine which actions are recommended.  The script will then prompt you to choose the actions you would like taken.
Once a choice has been entered for all nine possible actions, required changes will be made.
<p>The possible actions are:
<li>Create the www user/group</li>
<li>Install the package LON-CAPA uses to authenticate users.</li>
<li>Set-up the MySQL database</li>
<li>Set-up MySQL permissions</li>
<li>Configure Apache web server</li>
<li>Configure start-up of services</li>
<li>Check firewall settings</li>
<li>Stop services not used by LON-CAPA,<br>
    e.g., services for a print server: cups daemon</li>
<li>Download LON-CAPA source code in readiness for installation</li>

<h3>Determine LON-CAPA Settings</h3>
LON-CAPA requires a number of identifying parameters to be set in order
for it to function at all.  Below is a list with descriptions.
  <dt>Host Type (library or access)</dt>
  <dd>The server must be designated a 'library' or an 'access' server.  In
      general you should have a library server for your instructors to create
      their course content on and run their courses.  Students should connect
      to access servers.  If you are doing the first install of LON-CAPA at
      your site, or if you are playing with it for your own edification you
      should make your machine a 'library' server.</dd>
  <dt>LON-CAPA domain</dt>
  <dd>Each site or school which installs LON-CAPA needs its own domain.
      Here at MSU we use 'msu'.  You should choose something short but
      meaningful.  <i>Restriction: One word, no hyphens, underscores, or
      special characters.</i>
  <dt>LON-CAPA host id</dt>
  <dd>Each LON-CAPA server requires a unique internal name.  We use names
      such as "msul1" for the first library server. <i>Restriction: One word,
      no hyphens, underscores, or special characters.</i>
  <dt>Host administrator email</dt>
  <dd>The amount of email sent to this address is relatively minimal.  Messages
      are sent every time the system starts up, or if the system is in
      serious trouble. On a laptop, make this <tt>root@localhost</tt>.

<h3>Configuring LON-CAPA</h3>
To configure and install LON-CAPA, execute the following commands:
cd /root/loncapa-X.Y.Z     (X.Y.Z should correspond to a version number like '2.10.0')
You will need to enter the LON-CAPA configuration information you determined
in the previous section.

<h2>6. <a name="cdc">Creating a Domain Coordinator</a></h2>
You will need at least one user at your site who has the role of
'domain coordinator'.  This user creates accounts for other users and
grants them additional privileges.  The script
invoked below requires that you enter the user's password.
Feel free to use the "passwd username" command to change it later.
Replace USERNAME and DOMAIN with an appropriate user name and your domain.
cd /root/loncapa-X.Y.Z/loncom/build

<h2>7. <a name="sts">Start/Restart Services</a></h2>
The LON-CAPA network services take a moment to start.  Most misconfigurations
will be apparent at this step.
/etc/init.d/loncontrol start
/etc/init.d/apache2 start
If you receive warnings when starting the httpd about missing perl modules,
please make sure you followed the instructions in
<b>Installing LON-CAPA Dependencies</b>.  If you still have errors, please
contact the LON-CAPA group.

<h2>8. <a name="log">Log in to your LON-CAPA Machine</a></h2>
Point a web browser at your new machine and log in as the domain
coordinator.  Congratulations!

<h2>If things aren't working right</h2>
If you've followed the steps above and the server doesn't start or you think
there's something wrong, please get in touch with the LON-CAPA group.
You can submit a help request using our web form:<br>
<a href=""></a><br>
If there were errors in installation of the dependency RPMs or during the
automatic setup, please send us as much information as possible.
If some part of this document is unclear please let us know.

FreeBSD-CVSweb <>