Child pages
  • Installation & Upgrade instructions
Skip to end of metadata
Go to start of metadata

Table of Contents


1. Meet requirements

1.1 Apply SAK-10801 - Add contextId (siteId) field to Event Closed (Sakai 2.5.x only)
  • You can follow these instructions for applying SAK-10801 - Add contextId (siteId) field to Event Closed to your Sakai installation. Depending on your DB size, this operation can take several time.
1.2 Upgrade to EntityBroker 1.3.9 or higher (Sakai 2.5.x and Sakai 2.6.x only)
  • Option 1 (source): change in Sakai source code:
  1. Remove {tomcat_folder}/shared/lib/entitybroker*
  2. Remove {tomcat_folder}/components/entitybroker*
  3. Remove {tomcat_folder}/webapps/entitybroker*
  4. Change <sakai.entitybroker.version> property in master/pom.xml to 1.3.9 (or higher)
  5. Checkout EntityBroker 1.3.9 (or higher), compile and deploy:

    svn co https://source.sakaiproject.org/svn/entitybroker/tags/entitybroker-1.3.9/

    cd entitybroker-1.3.9

    mvn -Dmaven.tomcat.home={tomcat_folder} clean install sakai:deploy

  6. Change <module> property in full profile on ./pom.xml to entitybroker-1.3.9 (or higher)
  • Option 2 (binary): replace EntityBroker binaries in Tomcat:
  1. Remove {tomcat_folder}/shared/lib/entitybroker*
  2. Remove {tomcat_folder}/components/entitybroker*
  3. Remove {tomcat_folder}/webapps/entitybroker*
  4. Unzip EntityBroker 1.3.9 assembly to {tomcat_folder}
1.3 Upgrade Maven to 2.2.1 or higher
  • Maven 2.2.1+ is required to properly compile the project.
    Lower versions can fail with the error message "Failed to validate POM for project".


2. Install BigBlueButton Sakai Meeting Tool

  1. Download the tool source code from the Download section of the Home page
    For version 1.0.7 and Up

    git clone git://github.com/blindsidenetworks/bigbluebutton-sakai.git

    For version 1.0.6

    svn co https://source.sakaiproject.org/contrib/bigbluebutton/tags/bbb-1.0.6/

  2. Compile & deploy to Tomcat:

    mvn -Dmaven.tomcat.home={tomcat_folder} clean install sakai:deploy

  3. Add/review the following entries to the end of your sakai.properties file

    bbb.url=http://<server>/bigbluebutton
    bbb.salt=<salt>

    To determine these values for your BigBlueButton, enter the command

    bbb-conf --salt


    If you want to use the public test server for BigBlueButton, use the following settings

    bbb.url=http://test-install.blindsidenetworks.com/bigbluebutton
    bbb.salt=8cd8ef52e8e101574e400365b55e11a6

    (see Configuration section of the Home page)

  4. Create the database schema
    For version 1.0.7 and up run the schema creation script that corresponds to your database (MySQL or Oracle)
    For version 1.0.6 run the schema creation script that corresponds to your database (MySQL or for Oracle)
    For testing purposes, schema can be automatically created by setting auto.ddl=true in sakai.propertie

  5. Restart Sakai

    {tomcat_folder}/bin/shutdown.sh

    {tomcat_folder}/bin/startup.sh


3. Upgrade BigBlueButton Sakai Meeting Tool

From version 1.0.6 to version 1.0.7

  1. Download the tool source code from the Download section of the Home page

    git clone git://github.com/blindsidenetworks/bigbluebutton-sakai.git

  2. Remove BigBlueButton Sakai Meeting Tool binaries in Tomcat

    rm -rvf {tomcat_folder}/shared/lib/bbb*

    rm -rvf {tomcat_folder}/components/bbb*

    rm -rvf {tomcat_folder}/webapps/bbb*

  3. Compile & deploy to Tomcat:

    mvn -Dmaven.tomcat.home={tomcat_folder} clean install sakai:deploy

  4. Update the database schema
    Run the schema creation script that corresponds to your database (MySQL or Oracle)
    For testing purposes, schema can be automatically updated by setting auto.ddl=true in sakai.propertie

  5. Restart Sakai

    {tomcat_folder}/bin/shutdown.sh

    {tomcat_folder}/bin/startup.sh


4. Sakai setup

  • Adding to site: the tool can be added as usual via a Sakai site: Site Info > Edit tools > [x] Meetings
  • Permissions: can be set in the tool
  • No labels

1 Comment

  1. Hi 

    The upgrade scripts for ORCALE is incorrect there is no INT type in ORACLE for the RECORDING_DURATION and DELETED

    We ran it as:

    ALTER TABLE BBB_MEETING ADD (recording_duration  NUMBER(10) DEFAULT 0);

    ALTER TABLE BBB_MEETING ADD (deleted  NUMBER(10) DEFAULT 0);

    Cheers