1.0 Installation Requirements
To get started, the following items need to be installed (you can skip items already installed).
- Java 1.8
- git
- Maven 3.0 or higher
- Gato 8
Sakai 12.0 was also tested by Quality ControlJava 1.8.0_111,maven-3-2.5 (although maven-3.3.9 should also work),Apache Tomcat 8.5.28
1.1 Check/Install Java 1.8
sun oracleJava SE 8, also known as Java 1.8, is the required version for use with Sakai. Certain files like *.jsp and *.jws need to be compiled, so just downloading and using the runtime environment (JRE 8.0) is not enough.
Run to confirm Java is installed on your system and is the correct version for SakaiJava-Version
from the command line:
Java-Version
If Java is installed, the base version and build information is displayed. Example output:
Java-Version „1.8.0_111“ Java(TM) SE Runtime Environment (Build 1.8.0_31-b13) Java HotSpot(TM) 64-Bit Server VM (Build 25.31-b07, gemischter Modus)
1.1.1 Set Java Environment Variables
Java requires setting various environment variables and associated properties. On UNIX operating systems, you typically change an initialization file such as~/.bash_login
for defining and exporting shell variables, while Mac users usually define and export environment variables in.bash_profile
🇧🇷 Go to in WindowsStart -> Control Panel -> System -> Advanced -> Environment Variables
and establishJAVA_HOME
via the graphical user interface.
Set the JAVA_HOME environment variable to point to the home directory of your Java installation and add the file/Compartment
directory into the PATH environment variable.
If the JRE_HOME variable is already set or you want to use a specific JRE and you have more than one JRE installed on your computer, also set the JRE_HOME variable. JRE_HOME is what Apache Tomcat uses on startup, but by default it uses JAVA_HOME if JRE_HOME is not set. In most cases setting JAVA_HOME should cover both cases sufficiently.
Variable | Unix | Mac | window |
---|---|---|---|
JAVA_HOME |
|
|
|
CAMINO |
|
|
|
Windows: Append a string to the end of
Camino
Systemvariable
Define JAVA_OPTS
The default Java Virtual Machine (JVM) configuration is not sufficient for an application the size of Sakai. As a result, several JVM parameters need to be increased for Sakai to run, while others may need to be tuned for optimal performance.
We recommend configuring these settings in Tomcat
/Compartment
directory in a file namedsetenv.sh
(Unix/Mac) osetenv.bat
(Window). See the Installing Tomcat 8 section below for more details.
Specify a language and regional settings (optional)
You can set the default language/locale when starting Sakai by setting the system properties-duser.language
mi-duser.region
🇧🇷 For supported languages, see the release notes or visit thei18NWorking group room.
-Duser.language=pt -Duser.region=PT
If your locale does not fully support Java (e.g. the Basque or Mongolian languages), you should read this information:
I18n project approved
Specify an HTTP proxy (optional)
In environments where local network policies or firewalls require the use of an upstream HTTP proxy/cache, Sakai should be configured accordingly. Otherwise, components or services that use HTTP requests, such asBasic news service
for RSS feeds in the news tool it is not possible to retrieve data from target URLs. This can be fixed with the followingJAVA_OPTS
Arguments:
-Dhttp.proxyHost=cache.some.domain -Dhttp.proxyPort=8080
1.2 Install Git and/or the local Github client
The Sakai Community uses Githuba's Source Control Management (SCM) system. Use a reasonably recent version of Git to get the source. Alternatively, you can get binary packages for Mac/Linux and Windows (Linux is more popular and gets the majority in QA testing by far). Extract the distribution file to your installation directory.
1.3 Install Maven 3
The Apache Maven project management framework provides Sakai with "a set of build patterns, an artifact repository model, and a software engine that manages and describes projects" (Better Builds, p. 22). As part of the installation process, you use Maven as a build tool to build, test, and deploy Sakai in a servlet container such as Apache Tomcat.
It is recommended to use Maven 3.2.5 to 3.3.9.
You can download Maven from
http://maven.apache.org/download.html
Extract the distribution file to the installation directory of your choice, e.g./usr/local/apache-maven-3.2.2
🇧🇷 Confirm that you have the right version of Maven installed and can start it by typing it outmvn --version
from the terminal At this point, your environment is ready to compile and deploy the Sakai source code.
mvn --version
Apache Maven 3.2.5 (45f7c06d68e745d05611f7fd14efb6594181933e; 2014-06-17T09:51:42-04:00) Maven-Startup: /usr/local/apache-maven-3.2.5 Java-Version: 1.8.0_111, Hersteller: Oracle Corporation Java: /usr/lib/jvm/java-8-openjdk-amd64/jre Standardgebietsschema: en_US, Plattformkodierung: UTF-8OS Name: „linux“, Version: „3.13.0-30-generic“, arch: „amd64“ , Familie: "unix"
1.3.1 Setting Maven Environment Variables
Several environment variables should be set for optimal Maven performance. For UNIX operating systems, a startup file like ~/.bash_login is usually modified to set and export shell variables, while Mac users usually set and export environment variables.bash_profile
🇧🇷 Go to in WindowsStart -> Control Panel -> System -> Advanced -> Environment Variables
and set your maven environment variables via GUI.
put thatMAVEN_HOME
Environment variable to point to the base directory of your Maven installation and add Maven/Compartment
Directory for yourCAMINO
Variable:
Variable | Unix/Mac | window |
---|---|---|
MAVEN_HOME |
|
|
CAMINO |
|
|
Windows: Add a string to the end of
Camino
Systemvariable
MAVEN_OPTS
Maven no LeeJAVA_OPTS
at startup, which occasionally causes "out of memory" errors when compiling Sakai. To ensure sufficient memory allocation during build, you should add oneMAVEN_OPTS
Environment variable as defined below. For UNIX operating systems, a startup file like ~/.bash_login is usually modified to set and export shell variables, while Mac users usually set and export environment variables.bash_profile
🇧🇷 Go to in WindowsStart -> Control Panel -> System -> Advanced -> Environment Variables
and establishMAVEN_OPTS
via the graphical user interface.
exportar MAVEN_OPTS='-Xms512m -Xmx1024m'
1.4 Install Tomcat 8
- Apache tomcat -http://tomcat.apache.org/
- Monitoring:Always do a clean install of Tomcat
- monitoring: For Sakai versions earlier than 11.4, use Tomcat 8.0.34 or earlier. Later versions of Tomcat can cause problems. Example:
SAK-31608-Sakai has boot warnings on Tomcat 8.0.39+Cerrado
- Monitoring:Windows users should ensure that the full tomcat path does not contain spaces as this will cause errors with the JSF tools on Sakai.
BOA:C:\opt\tomcat\, C:\sakaistuff\installa\tomcat\
FOREVER:C:\Programmarchiv\Tomcat\, C:\opt\Apache Tomcat 8.0.43\
- Download Tomcat fromhttp://tomcat.apache.org/
Windows users should get the zip file instead of installing a service
Makes viewing Tomcat logs easier and easier to configure
- Extract to /opt (symlink apache tomcat xyz directory to tomcat after extraction)
Example (assuming you saved the file as /opt/apache-tomcat-8.0.x.tar.gz)
CD / opt
tar xzvf apache-tomcat-
8,0
.x.tar.gz
ln -nsf apache-tomcat-
8,0
.x Cat
(Video) Sakai LTI Briefing 2021-01-14Windows users should rename the directory or, if convenient, create a directory branch with an elevated cmd prompt:
mklink /J C:\apache-tomcat-
8,0
.x C:\kater
- Modify conf/server.xml to support international characters
- Add URIEncoding="UTF-8" to the connector element
- <Socket-Port="8080" URIEncoding="UTF-8" ...
- Add URIEncoding="UTF-8" to the connector element
- Set the environment variable: CATALINA_HOME=/opt/tomcat
- Add $CATALINA_HOME/bin to PATH
Configure the SETENV file in the tomcat/bin directory with JAVA_OPTS (fromInstall Java 1.8).
Fill the database with demo data
Instead of starting with an empty database, you can add the -Dsakai.demo=true flag in addition to the others shown here. When you first start Tomcat, you populate your database with test data (students, courses, etc.). Remove this flag after building the data for subsequent versions of Tomcat. Note that this flag will not be raised in a database that already contains data, so you must select this option during initial setup. It should also be noted that without this flag it will not be possible to create any course pages in Sakai unless the Academic Term, Subject, Course and Section data is manually added to the "cm_" tables in the database added.
Note: Because test users are "provisioned" they do not appear in the user tool. First, log in as "Teacher" with the password "sakai". You can then add multiple lists, including megasections.
Alternatively, the test data can be completed by running Create Test Sites, Users, and Content. in the task scheduler. This generates many sites, but class sizes are smaller, which is less than ideal for performance testing.
We recommend using -Djava.util.Arrays.useLegacyMergeSort=true until this issue is resolved -
SAK-31707-Broken equality comparisons in the grade bookDISSOLVED
Sakai 21 e Interior:
Mac/Linux: Create a file namedsetenv.shwith the following (alternatively you can put this in your.bashrcfile to run automatically):
Tomcat 8Mac/Linuxexport JAVA_OPTS=
"-server -d64 -Xms1g -Xmx2g -Djava.awt.headless=true -XX:+UsarCompressedOops -XX:+UsarConcMarkSweepGC -XX:+DisableExplicitGC"
JAVA_OPTS=
"$JAVA_OPTS-Dhttp.agent=Sakai"
JAVA_OPTS=
"$JAVA_OPTS -Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=falso"
JAVA_OPTS=
"$JAVA_OPTS-Dsakai.security=$CATALINA_HOME/sakai/"
JAVA_OPTS=
"$JAVA_OPTS -Duser.timezone=USA/East"
JAVA_OPTS=
"$JAVA_OPTS -Dsakai.cookieName=SAKAI2SESSIONID"
JAVA_OPTS=
"$JAVA_OPTS -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=8089 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false - Dcom.sun.management.jmxremote.ssl=false"
Windows (PC): Create a file namedsetenv.batwith the following:
Windows Kater 8definir JAVA_OPTS=-servidor -Xmx1028m -XX:MaxMetaspaceSize=512m -Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=
NOT CORRECT
-Djava.awt.headless=
real
-Dcom.sun.management.jmxremote -Dhttp.agent=Sakai -Djava.util.Arrays.useLegacyMergeSort=
real
-Dfile.encoding=UTF8
(Video) Sakai - Free React Admin Template
Sakai 22+ (d.h. hat Java 11)
Mac/Linux: Create setenv.sh with the following:
# Append -Dsakai.demo=
real
as necessary
# Specify -Dsakai.security to specify a location
through
Security.Properties
# Another Sakai configuration
21
and the example above might also be relevant
exportar JAVA_OPTS="-servidor -Xmx1028m -Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=
NOT CORRECT
-Djava.awt.headless=
real
-Dcom.sun.management.jmxremote -Dhttp.agent=Sakai -Dsakai.component.shutdownonerror=
real
\
--add-exports=java.base/jdk.internal.misc=ALLE OHNE NAME \
--add-exports=java.base/sol.nio.ch=ALL WITHOUT NAME\
--add-exports=java.management/com.sun.jmx.mbeanserver=TODO-SIN-NAME \
--add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=TODO SIN NOMBRE \
--add-exports=java.base/sun.reflect.generics.reflexiveObjects=TODOS SIN NOMBRE \
--add-opens jdk.management/com.sun.management.internal=ALLE OHNE NAME \
--illegal access=allow"
- Windows: If you are using Windows, update this document with an appropriate setenv.bat
[OPTIONAL] Remove the default webapps from the webapps directory (note: this may be undesirable: webapps/ROOT contains the favicon, etc.)
rm -rf webapps/*
Improve startup speed
You can greatly improve Tomcat's startup speed by making changesconf/context.xml paraSearch for TLD only in interesting files.
For Sakai 21 and earlier:Add this JarScanFilter block to the <Context>
<Jar-Scanner>
<!-- This is to speed up startup so Tomcat doesn't scan as much -->
<JarScanFilter defaultPluggabilityScan=
"NOT CORRECT"
predeterminadoTldScan=
"NOT CORRECT"
tldScan=
"jsf-impl-*.jar,jsf-widgets-*.jar,myfaces-impl-*.jar,pluto-taglib-*.jar,sakai-sections-app-util-*.jar,spring-webmvc-* .jar,estándar-*.jar,tomahawk*.jar"
/>
</JarScanner>
For Sakai 22 and above: In Java 11, Java EE has been changed to Jakarta EE which includes JSF.Add this JarScanFilter block to the <Context>
<Jar-Scanner>
<!-- This is to speed up startup so Tomcat doesn't scan as much -->
<JarScanFilter defaultPluggabilityScan=
"NOT CORRECT"
predeterminadoTldScan=
"NOT CORRECT"
tldScan=
"jsf*.jar,*cars*.jar,pluto-taglib-*.jar,sakai-sections-app-util-*.jar,spring-webmvc-*.jar,estándar-*.jar,tomahawk*.jar "
/>
</JarScanner>
2.0 Get the Sakai source code
There are two ways to get Sakai source code. You can choose to download a *.zip or *tar.gz file from the Sakai release page, or check out the code directly from our code repository using the Git source control systemGithub als Repository-Hosting-Service.
You can find the Sakai source code in our Github repository. The latest development work has arrivedthe master branch
🇧🇷 Stable versions can be found atlabel
while maintenance and other work is being carried outan 11.x branch.
11 Launch-Tag
To check for a stable release tag, clone the git repository and then check the tag (11.0 in this case):
Clone of git https://github.com/sakaiproject/sakai.gitcd sakai && git checkout 11.0
release information
The latest stable version may be newer than the above version. please take a lookhttp://source.sakaiproject.org/release/or the labelshttps://github.com/sakaiproject/sakai/and use the last tag for best results.
Maintenance branch 11.x
Check our maintenance branches for the latest bug fixes for a specific version. Note that certain maintenance branch fixes require changes to the database schema. You can check the maintenance branch by running the following command in the terminal:
git-Klon https://github.com/sakaiproject/sakai.gitcd sakai && git checkout 11.x
If you have already cloned the repository, skip the previous cloning step.
3.0 Configuring Sakai
1.0 Create onesakai.properties
office hours
Ösakai.properties
is a central configuration file, usually stored in a/ Sakai
Subdirectory relative to tomcat home directory ($CATALINA_HOME
🇧🇷 It's a non-XML text file containing a series of key/value pairs that are read using the load method fromjava.util.properties🇧🇷 Settings onsakai.properties
You handle everything from defining your institution's name to configuring your database. All settings in theresakai.properties
they are read at the beginning; Any changes you make later will not take effect until you restart the web application server. You may want to create a local.properties file in the same directory as sakai.properties. Properties listed in local.properties override sakai.properties.
In a factory installation, the default settingpredeterminado.sakai.properties
file is includedthe settings
Module:
sakai-src/config/configuration/bundles/src/bundle/org/sakaiproject/config/bundle/default.sakai.properties
The container package does not include a
sakai.properties
Procedure. This is a deliberate exclusion; removes the ability to override a locationsakai.properties
File when opening a bin package in an existing Sakai installation.
If you need to override the defaults, you'll need to create your own.sakai.properties
File from scratch or a known working copy, adding new key/value configurations to customize your installation. We encourage you to check them outpredeterminado.sakai.properties
File included with the source installation or the corresponding maintenance branch.
The default location for your locationsakai.properties
the file is$CATALINA_HOME/sakai
🇧🇷 Maven doesn't create this folder during the build and deploy process, so you'll need to create it manually or via a script. You can also store Sakai configuration files outside of the web application server file hierarchy. For example, in a development environment, you can often reinstall Tomcat, and if you don't create a build script to automate the process of installing and configuring Tomcat, you avoid the need to rebuild$CATALINA_HOME/sakai
misakai.properties
every era has its advantages.
To find your properties file outside of the web application server environment, modify the Java startup command or theJAVA_OPTS
environment variable and set a system property calledsakai.casa
🇧🇷 Make sure your web application server can read and write your remote location.
-Dsakai.home=/path/to/desired/sakai/home/
For a list of sakai.properties settings, see the Sakai Properties Reference; for detailed documentation of the entire range of possibilities
sakai.properties
Configuration seesakai_properties.doc
Inside/referencia/docs/arquitectura/sakai_properties.doc
.
2.0 Configuring the Homepage toolset per site
Homepage tools collections can be configured for each site type. However, if thewsetup.home.toolids.*
If the property is not set, the worksite configuration tool uses the following tools for the home page by default:sakai.iframe.site
,sakai.summary.schedule
,sakai.synoptic.announcement
,sakai.synoptic.chat
,sakai.synoptic.messagecenter
🇧🇷 Synoptic tools are added or removed from the homepage depending on whether the linked tool is present on the site or not. To seeSAK-15504-Updated website: Editing "My Workspace" results in a duplication of the home pageCerradomi
SAK-16747-Tools are not automatically added to the Home Tools pageCerradofor more details.
wsetup.home.toolids.count=5wsetup.home.toolids.1=sakai.privacywsetup.home.toolids.2=sakai.iframewsetup.home.toolids.3=sakai.synoptic.announcementwsetup.home.toolids.4=sakai. synoptic.chatwsetup.home.toolids.5=sakai.synoptic.messagecenter
Workplace 3.0 Configuration Group Wizard
A new group helper is enabled by default (seeSAK-13413-Improved party creationCerradofor more details). Site maintainers can now create groups based on sections and roles. To go back to the old 2.5 group wizard (ad hoc only) you need to add the following configuration
sakai.properties
:
wsetup.group.helper.name = sakai-site-manage-group-helper
4.0 Session Timeout Warning
Sakai includes a property calledinactiveInterval@org.sakaiproject.tool.api.SessionManager, which determines the idle time before the user's session expires and allows a session timeout warning to be enabled. Session status is now checked by the Sakai portal. If the remaining session time is less than the warning time (e.g. 10 minutes). When a session expires, all page requests are redirected to the URL specified byUnsubscribe URL
Sakai property. To seeSAK-13987-Session timeout popup with entity broker search dataCerrado
SAK-8152-Sakai must warn a user before the user's session expires and data is accidentally lostCerradofor more details.
To enable the session timeout warning, set the following properties in your regional settingssakai.properties
with a time interval of your choice:
timeoutDialogEnabled=truetimeoutDialogWarningSeconds=600
5.0 Set up email
In order for Sakai to send and receive email, several properties must be setsakai.properties
🇧🇷 To send emails, Sakai needs the address (name or IP) of an external SMTP server that accepts emails from Sakai:
smtp@org.sakaiproject.email.api.EmailService=some.smtp.org
Sakai's SMTP server is Apache James for Sakai 10 and earlier and SubEthaSMTP 11. Most system administrators prefer to run a standard email client like Postfix on port 25 and configure it to forward requests to Sakai will. You may also currently have a mail service running on port 25 (Linux usually runs it by default). Therefore, consider configuring the Sakai SMTP service to run on a different port (e.g. 8025) to avoid conflicts.
In order for Sakai to receive email, you must set the following properties:
# Flag to enable or disable SMTP service for incoming mail (true | false)#Default=false.smtp.enabled=true# DNS addresses used by SMTP service for incoming mail. (only compatible with versions <= Sakai 10) smtp.dns.1=255.255.255.1smtp.dns.2=255.255.255.2# SMTP port on which the incoming SMTP service is listening. # It is recommended to run at 8025 and use a default mail of 25 to forward mail to Sakai. # Default=25.smtp.port=8025
Additional settings can be enabled to add support emails for a variety of tasks.
# Support email address used in incoming email bounce messages.mail.support=address@somedomain# A variation of this used in some places instead of the above! It is better to set bothsupport.email#To change postmaster address to generalsmtpFrom@org.sakaiproject.email.api.EmailService# Email address to send detected portal errors and user error reports to response.portal.error.email = address@somedomain# . Email address used as the "From" address for all emails sent from the Worksite Setup Tool or Site Information Tool.setup.request=address@somedomain# Sends an email to the user when the user is added. from.address# Send or not the real address as msgcntr Notificationsmsgcntr.notification.user.real.from=true (false)
6.0 Configure registration
After installing, configuring, and launching Sakai, you can monitor Sakai by looking at the logs. The log level for both the Sakai standard source code and the demo is set to show information and warnings only. NoteTO WARN:
There will be some "normal" posts at startup and some will likely go unnoticed at runtime, but any warnings might be something you might want to check for.
Log levels can be specified insakai.properties
🇧🇷 This increases and overrides the levels defined in the default configuration file. Example:
log.config.count=3log.config.1 = ALLE.org.sakaiproject.log.impllog.config.2 = AUS.org.sakaiprojectlog.config.3 = DEBUG.org.sakaiproject.db.impl
This uses the established method (albeit odd) of having aName.Number
followed byName.1
,Name.2
etc. to form a string array for the value "Name". In this case, the name is "log.config". The values are from the formLEVEL.register
, and the possible levels are:OFF TRACE DEBUG INFO WARN ERROR FATAL TODO
.
United Stateslog4jfor the record. For more information on configuration when in doubt, refer to the official log4j documentation, but some pointers are compiled below.
To change the record in the source in Sakai, changekernel/kernel-common/src/main/config/log4j.properties
the following property:
log4j.logger.org.sakaiproject=INFO
To enable debug logging for all Sakai, change the INFO value to DEBUG. To enable debug logging for a single Sakai component, add a line like the following example, which leaves most of Sakai in INFO but generates DEBUG-level messages for the SQL service:
log4j.logger.org.sakaiproject=INFOlog4j.logger.org.sakaiproject.component.framework.sql.BasicSqlService=DEBUG
Log controls are part of the LogConfigurationManager implemented as a component in the kernel. If desired, it can be deactivated with an entry insakai.properties
:
enabled@org.sakaiproject.log.api.LogConfigurationManager = false
For Mac and *nix systems, the most important registry is Tomcat'srecords/catalina.out
🇧🇷 It can be instructive to look at this log when launching Tomcat with a launch command like this:
bin/home.sh; tail -f logs/catalina.out
Tomcat on Windows tends to be a little trickier in terms of its logs and contains more, but its default behavior is to opencatalina.out
in a new window once you start Tomcat. If you need more information about logging into Windows, we refer you to the official Tomcat documentation.
The Sakai SMTP server logs are written to the $CATALINA_HOME/sakai/logs directory.
7.0 Manage temporary files
Depending on usage, Sakai can create many large temporary files in the system's temporary file location (e.g. /tmp). It's a good idea to routinely delete temporary files older than a day, especially if you have many users or frequently send emails with attachments. Note that you should not delete all temporary files on a schedule, as some of them may be actively used (be careful when deleting temporary files used by other processes).
3.1 Configure database
Sakai 12 database support details
Be sure to include a MySql plugin wrapper in your CATALINA_HOME/lib.
Create a Sakai database with a default UTF-8 character set. Create a user account to which you assign all permissions.
Use whatever database name and username you want, then update your sakai.properties file (or better yet, create a local.properties file that takes precedence).
In the following example, the database is named "sakaidatabase" and the user account is named "sakaiuser".
Excerpt from sakai.properties
usuario@javax.sql.BaseDataFuente=Sakauer
senha@javax.sql.BaseDataFuente=senha sakai
## MySQL-Konfiguration
proofedor@org.sakaiproject.db.api.SqlService=mysql
driverClassName@javax.sql.BaseDataSource=com.mysql.jdbc.Driver
hibernate.dialect=org.hibernate.dialect.MySQL5InnoDBDialect
url@javax.sql.BaseDataFuente=jdbc:mysql://127.0.0.1:3306/Sakai-Datenbank?useUnicode=true&characterEncoding=UTF-8
validaciónQuery@javax.sql.BaseDataFuente=
defaultTransactionIsolationString@javax.sql.BaseDataSource=TRANSACTION_READ_COMMITTED
mysql -u root -pEnter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL login ID is 272Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved. This software comes with NO WARRANTIES. This is free software and you can modify and redistribute it under the GPL v2 license. Type "help"; or '\h' for help. Type '\c' to clear the current input statement. mysql> create sakai database default character set utf8; Query OK, 1 row affected (0.00 sec) mysql> all on sakai.* grant to sakaiuser@'localhost' identified by 'sakaipassword';Query OK, 0 rows affected (0.00 sec. mysql> all on sakai.* grant to sakaiuser @'127.0.0.1' identified by 'sakaisenha' Query OK, 0 rows affected (0.00 sec) mysql> flush privileges Query OK, 0 rows affected (0.00 sec) mysql> exit
4.0 Build, deploy and launch Sakai on Tomcat
Install the Sakai master project
Sakai uses the Maven project object model to provide an XML representation of basic project information, covering dependency management, build targets, external repositories, issue tracking, mailing lists, plugin reports, developer biographies, and more. A top-level master pom.xml file located in the/Professor
The project acts as a parent for other Sakai pom.xml files. If you are building Sakai for the first time, you must first install the master blueprint by installing thecleaned
miinstall on pc
goals off/Professor
project folder.
cd mastermvn clean installcd ..
Install and deploy Sakai
After creating the master pom, output the following Maven targets from the top-level Sakai source directory:
-Dmaven.tomcat.casa
Specifies the location of Tomcat. -Dsakai.home specifies the location of the Sakai property files in Tomcat. 🇧🇷Djava.net.preferIPv4Stack can help solve problems where Maven crashes when trying to pull from certain repositories. They can be omitted if specified in MavenKonfiguration.xml
(Version 2.x) oder in MAVEN_OPTS (Version 3.x).
mvn clean install sakai: deploy -Dmaven.tomcat.home=/pathto/tomcathome -Dsakai.home=/pathto/tomcathome/sakai -Djava.net.preferIPv4Stack=true
Your first build of Sakai will take some time while Maven downloads and saves your location..m2/Repository
with missing dependencies running build and deployment.guerra
mi.Bottle
Files for Tomcat$CATALINA_HOME/webapps
,$CATALINA_HOME/components
mi$CATALINA_HOME/shared/lib
If during this process Maven reports that the build failed, please read the attached error message carefully to resolve the issue (seeTroubleshootingSection).
You can also exhibitmvn sakai clean install: deploy
from a top-level Sakai project modules folder to build and deploy pieces of Sakai as individual tools.
Maven meta options
There are several other ways to build and deploy Sakai with Maven:
Print debug output
mvn -X clean install sakai: deploy
Build and deploy in offline mode
If your local repository contains all Sakai project dependencies, you can run Maven "offline" by using the-Ö
Possibility:
mvn -o sakai clean install: deploy
Ignore unit tests
There may be times when you want to build and deploy Sakai without running the suite of unit tests that come with many of Sakai's modules. if yes, add-Dmaven.test.skip=true
for the purposes it issues:
mvn clean install -Dmaven.test.skip=true sakai:deploy
Run a "Framework" build
The Frame Build Profile activates a Sakai build without its tool kit.
The build profile -Pframework is no longer supported in Sakai 10.x releases.
mvn -Pframework sakai clean install: deploy
Run a "coffee" build
The Developer Coffee Builder profile is preferred by many developers new to Sakai, as well as those developing or testing new features.
The -Pcafe build profile is no longer supported by Sakai 10.x releases.
mvn -Pcafe clean install sakai: deploy
4.1 Starting/Stopping Tomcat
Start/stop Tomcat from the terminal by running the appropriate start/shutdown script found in$CATALINA_HOME/box
:
Unix/Mac
sh start.shsh deleted.sh
window
startup.batshutdown.bat