The LAMS2-SharePoint integration was developed with WSS 3.0. It is also compatible with Microsoft Office SharePoint Services 2007 (MOSS2007).
It is recommended that LAMS and SharePoint be installed on separate servers to account for the heavy memory requirements of SharePoint and LAMS.
Please view the release notes for version update information.
|Want to have a look without installing it?|
Try the LAMS2-SharePoint Demo server
- It is strongly recommended that you use separate servers for LAMS and SharePoint installations to account for heavy CPU usage of the two systems.
- LAMS 2.0.6 +
- WSS 3.0 or MOSS2007
- Download lLamsSharePointIntegration-1.0-Beta.zip from the downloads page to the SharePoint server.
- Extract to a temporary location, package should include:
- InstallSolutionPackage.cmd ~653B
- RemoveSolution.cmd ~380B
- LamsSharePointIntegration.wsp ~55k
- Open the InstallSolutionPackage.cmd in a text editor.
- There should be a line that says:
@SET STSADM="c:\program files\common files\microsoft shared\web server extensions\12\bin\stsadm.exe"
- Make sure that the path points to stsadm.exe, you may need to change this path.
- You must enable the Windows SharePoint Services, goto Control Panel -> Administrative Tools -> Services and start the Windows SharePoint Services Administration services if it has not already started.
- Run InstallSolutionPackage.cmd.
- Make sure that you have properly configured your SharePoint Alternate Access Mappings as the LAMS SharePoint Integration requires this, see this help page for more information on how to do this.
- You should now be able to enable the LamsSharePointIntegration site feature.
Activating the LAMS SharePoint Integration Site Feature
The LAMS integration is a "site feature" in WSS, as opposed to a "site collection feature". This means that it must be activated for each site that you wish to use the integration in.
- Login as site owner or administrator to the site.
- In the Site Actions menu, select Site Settings.
- Select the Site Features link under the Site Administration heading.
- If the LAMS Integration has installed correctly, an item in the Site Feature list should appear, select the activate button next to it.
- To test successful activation, return to the site home page, there should be a link in the Quick Action bar for a LAMS lesson list.
Configuring the Server Mappings
The server mapping configurations are server-wide, it does not matter which site collection these settings are set at.
- Login as administrator to a site collection root page.
- In the Site Actions menu, select Site Settings.
- Select the LAMS Integration settings under the Site Collection Administration heading.
- Enter a server id for the SharePoint server. Remember this, because you will need it to configure the LAMS side.
- Enter a server key for the SharePoint server. Remember this, because you will need it to configure the LAMS side and make sure it is not easy to guess as it will be the basis of the secure communication between the LAMS and SharePoint servers.
- Enter the LAMS server url which takes you to the login page. It should take the form http://<LAMS server name>:<port>/lams/. Make sure you have the backslash "/" at the end.
- Enter the request source, which can be the name of your SharePoint server.
- Click ok, the settings will be save as a server-wide configuration.
- Follow the instructions to install LAMS, it is recommended that you install LAMS and SharePoint on separate servers to account for heavy memory requirements. You can either build LAMS from source or follow the instructions for Window Installers or Unix Installers.
- Login to LAMS as sysadmin.
- Goto Sys Admin->Maintain integrated servers->Add New Server.
- Setup the fields to match those that you put on the SharePoint side
- The id and key should map to the "LAMS SERVER ID" and "LAMS SERVER SECRET KEY" fields respectively on the LAMS Settings page in SharePoint(see above).
- Fill in a description of the SharePoint server.
- The "Prefix" field denotes a prefix that will be added to all users from the SharePoint server, for example if you put SP as the prefix and accessed LAMS with a user called "user", their name in LAMS would be "SP_user".
- The 'disabled' checkbox disables this integration, you can select this later if you wish to disable the connection.
- The User Information URL is not needed for LAMS/SharePoint integrations, so put a dummy URL in.
- You can specify a timeout page that LAMS will go to if there is an error.
And you are done! You can now create and access LAMS content from SharePoint.
|The LAMS-SharePoint source code is available on our CVS server. You can access the source from from cvs by checking out the lams_sharepoint_integration project. The project comes with an ant build script that will compile the code into .jar format, then just follow the installation step to install.
If you have any questions or comments, please post them in the LAMS Community Tech Forums