h2. LAMS Integration with Sakai
h3. Source Installation
1. Follow the instructions in the [Install Guide|http://confluence.sakaiproject.org/confluence/display/DOC/Install+Guide+%282.4%29] for Sakai 2.4. For those using Sakai 2.3.x, please follow the previous [Installation Guide|http://source.sakaiproject.org/release/2.3.1/install-overview.html].
2. Checkout the sakai-lamstwo project from the cvs repository.
Configure your cvs client as follows :
access method: *pserver*
user name: *anonymous*
server name: *lamscvs.melcoe.mq.edu.au*
location: */usr/local/cvsroot*
You will need to place the project under the sakai-src folder. This is required since the project references the master/project.xml file.
3. Add the following lines to the build.properties files. This file should be located in your home directory.
maven.test.failure.ignore=true
4. From the sakai-lamstwo directory, run the command
maven bld dpl
5. Add the following lines in the sakai.properties file. This is located in the CATALINA_HOME/sakai directory.
lamstwo.serverId = <server id>
lamstwo.serverKey = <server key>
lamstwo.serverAddr = <lams server address>
lamstwo.requestSrc = <request source>
Substitute <server id>, <server key>, <lams server address> and <request source> with appropriate values
6. Start Tomcat and check for any start up errors.
h3. In the LAMS side
1. login in LAMS as a sysadmin (the user that you created at installation time)
\\
\\
2. Select the *"Sys Admin"* link.
\\
\\
3. Select "*Maintain Integrated Servers*".
\\
4. Setup the fields as appropriate.
* *Id:* this is the server identification string that we will use to individually identify the LMS server that will be "talking" to LAMS.
* *Key:* this is the secret key that both systems will be used to encrypt the hash when doing authentication. *Make sure you keep your server key private*
* *Name:* the server name
* *Description:* a meaningful server description
* *Prefix:* the prefix that the usernames will have in LAMS. (usually just one or two letters will do)
* *Organisation:* Either use an existing Group within LAMS (from the Group Adminstration screens) or create a new Group.
* *User Information URL*: This is the callback userinfo URLthat is used by LAMS to retrieve personal information about the user from the LMS.
* *Timeout URL*: A webpage that should be displayed if the LAMS/Sakai timeout trying to talk to each other.
* *User Data URL:* If you run sakai using "http://<sakai server>/portal/" then the URL is
http://<sakai server>/sakai-lamstwo-tool/servlet/UserDataServlet?username=%username%×tamp=%timestamp%&hash=%hash%
!LAMSMaintainIntegratedServers.JPG!
h3. Source Installation
1. Follow the instructions in the [Install Guide|http://confluence.sakaiproject.org/confluence/display/DOC/Install+Guide+%282.4%29] for Sakai 2.4. For those using Sakai 2.3.x, please follow the previous [Installation Guide|http://source.sakaiproject.org/release/2.3.1/install-overview.html].
2. Checkout the sakai-lamstwo project from the cvs repository.
Configure your cvs client as follows :
access method: *pserver*
user name: *anonymous*
server name: *lamscvs.melcoe.mq.edu.au*
location: */usr/local/cvsroot*
You will need to place the project under the sakai-src folder. This is required since the project references the master/project.xml file.
3. Add the following lines to the build.properties files. This file should be located in your home directory.
maven.test.failure.ignore=true
4. From the sakai-lamstwo directory, run the command
maven bld dpl
5. Add the following lines in the sakai.properties file. This is located in the CATALINA_HOME/sakai directory.
lamstwo.serverId = <server id>
lamstwo.serverKey = <server key>
lamstwo.serverAddr = <lams server address>
lamstwo.requestSrc = <request source>
Substitute <server id>, <server key>, <lams server address> and <request source> with appropriate values
6. Start Tomcat and check for any start up errors.
h3. In the LAMS side
1. login in LAMS as a sysadmin (the user that you created at installation time)
\\
\\
2. Select the *"Sys Admin"* link.
\\
\\
3. Select "*Maintain Integrated Servers*".
\\
4. Setup the fields as appropriate.
* *Id:* this is the server identification string that we will use to individually identify the LMS server that will be "talking" to LAMS.
* *Key:* this is the secret key that both systems will be used to encrypt the hash when doing authentication. *Make sure you keep your server key private*
* *Name:* the server name
* *Description:* a meaningful server description
* *Prefix:* the prefix that the usernames will have in LAMS. (usually just one or two letters will do)
* *Organisation:* Either use an existing Group within LAMS (from the Group Adminstration screens) or create a new Group.
* *User Information URL*: This is the callback userinfo URLthat is used by LAMS to retrieve personal information about the user from the LMS.
* *Timeout URL*: A webpage that should be displayed if the LAMS/Sakai timeout trying to talk to each other.
* *User Data URL:* If you run sakai using "http://<sakai server>/portal/" then the URL is
http://<sakai server>/sakai-lamstwo-tool/servlet/UserDataServlet?username=%username%×tamp=%timestamp%&hash=%hash%
!LAMSMaintainIntegratedServers.JPG!