Blackboard

Outdated

IMPORTANT: The content of this page is outdated. Do not rely on the information contained in this page.

Creating a Blackboard Plugin to mimic the behavior of the Moodle "bridge1" plugin was begun in 2008 at the University of Rochester. The connection between the CMS and WeBWorK is minimal.

• Single sign in
  • Students sign in to the CMS. To do their homework they click on a WeBWorK link which automatically signs them in to WeBWorK, creates a homework set instance for them.
• Common grade book
  • When they have completed their homework their homework grades are transferred back to the gradebook in BB. (At first this was triggered by a cron job.)
• Configuration of homework sets is done using WeBWorK tools, not from BlackBoard or Moodle.

History:

Creating a Blackboard Plugin to mimic the behavior of the Moodle "bridge1" plugin was begun in at the University of Rochester. The connection between the CMS and WeBWorK is minimal. Students sign in to the CMS. To do their homework they click on a WeBWorK link which automatically signs them in to WeBWorK, creates a homework set instance for them. When they have completed their homework their homework grades are transferred back to the gradebook in BB. (At first this was triggered by a cron job.)

• Summer, 2008 -- Dan Arnold, supervised by Michael Gage. This was part of the UR summer intern program sponsored by the IT department of the University of Rochester.
• Summer, 2009 -- Martin Georgiev , supervised by Michael Gage and Paula Yandow-Reilley(and others from the UR IT department)
• November,2010 -- code base resurrected and cleaned up -- Paula Yandow-Reilley

• February, 2011 -- Blackboard plugin code base shared with University of Missouri
• Spring, Summer 2011 -- Further development by Srinivasan Devanathan, a student at University of Missouri in conjunction with (MU IT department) and supervised by Jason Aubrey. University of Oregon and University of Calgary are also beta testing and following results.

Learning Tools Interoperability (LTI) Protocol

LTI single sign on and gradebook integration is now included in WeBWorK 2.12.

The WeBWorK side of LTI is configured by editing the configuration file /opt/webwork/webwork2/conf/authen_LTI.conf See the comments in authen.LTI.conf for more information on settings.

More detailed information on LTI Authentication can be found located at LTI-Advanced Authentication

Details are also posted at http://webworkgoehle.blogspot.com/2016/03/webwork-lti-authentication.html Details on LTI Grade Integration is given at http://webworkgoehle.blogspot.com/2016/03/webwork-lti-grading.html

Depreciated: Blackboard Building Block Installation

"The Blackboard building block is being used anywhere anymore, certainly it is not used widely. A good substitute which will give you all or most of the features of the Moodle/WeBWorK wwassignment link is to use LTI which is now supported by most LMSs." http://webwork.maa.org/moodle/mod/forum/discuss.php?d=3860

This article is under construction. Use the information herein with caution until this message is removed.

Prepare WeBWorK

• Enable the webwork webservice. To do so put the following lines in your webwork.apache2-config file. It is very likely that these lines are already in that file waiting to be uncommented.

 PerlModule WebworkSOAP
 <Location /webwork2_rpc>
        PerlHandler Apache2::SOAP
        SetHandler perl-script
        PerlSetVar dispatch_to "WebworkSOAP"
        PerlSetVar options "compress_threshold => 10000"
        Order Allow,Deny
        Allow from All
 </Location>
 <Location /webwork2_wsdl>
        PerlSetVar dispatch_to "WebworkSOAP::WSDL"
        PerlSetVar options "compress_threshold => 10000"
        PerlHandler WebworkSOAP::WSDL
        SetHandler perl-script
        Order Allow,Deny
        Allow from All
</Location>

Note that there are likely other webservice configuration stanzas in your webwork.apache2-config file. The two above are the only ones that need to be active for communication with the Blackboard building block.

After adding or uncommenting these lines, you may check that things are working so far by restarting the webserver and navigating to http://[webwork@your_school].edu/webwork2_wsdl. You should see an XML file which begins something like

<?xml version="1.0" encoding="UTF-8"?> 

• The next step is to change localhost in the above url to the actual base url of your webwork server. To do so edit the file webwork2/lib/WebworkSOAP/WSDL.pm and change the line

use constant RPC_URL => "http://localhost/webwork2_rpc/";

Now if you restart the server and navigate back to the webwork2_wsdl page, the base url in the XML file should be the public url for your server rather than http://localhost/.

• The last thing to do to prepare your webwork installation is to set the SOAP authentication key. This is defined in the file webwork/lib/WebworkSOAP.pm with the line

$WebworkSOAP::SeedCE{soap_authen_key} = "123456789123456789";

You will need to communicate this authentication key to your Blackboard administrator for use when installing the building block into Blackboard.

Warning :

For security purposes, it is strongly recommended that you change this key to something less guessable on production servers.

Install the Building Block

TODO

Configure the Building Block

There are some settings that the Blackboard administrator must set in the administration settings for the building block:

• Enter webserver location: [base url]/WebworkSOAP, e.g. http://webwork.math.missouri.edu/WebworkSOAP
• Enter webserver RPC location: [base url]/webwork2_rpc e.g. http://webwork.math.missouri.edu/webwork2_rpc
• Enter weberver site url location: [base url]/webwork2/ e.g. http://webwork.math.missouri.edu/webwork2/
• Enter the SOAP Authorization Key: SOAP authorization key from WeBWorK (See above)
• Enter the SOAP Classes Permission: Minimum WeBWorK permission level for webservice users. Enter 0 here.
• Enter the SOAP User Status: Required WeBWorK user status for webservice users. Enter C here.