Skip to main content
pdf?stylesheet=default
Blackboard Help

Upgrade From ELM 3.6

To upgrade from ELM 3.6 to to 3.7, start running the installation software as you would for a full (clean) install.

The installation software will automatically detect whether or not you have a previous version of Blackboard Collaborate Suite installed on your computer. The upgrade will be applied to all previously installed instances.

If you made custom changes to the JNLPs (e.g., language JARs) in your earlier version of Blackboard Collaborate, these changes will have to be reapplied after the upgrade is complete.

The upgrade process is much simpler than a full installation and very little input is required on your part.

If upgrading from a previous version of Blackboard Collaborate, be sure you back up your data prior to running the installation.

Console Mode Upgrade

Follow the steps below to invoke the upgrade executable in console mode. This is available for Linux and Solaris only.

  1. Navigate to the appropriate OS folder (Linux or Solaris) within the Setup folder.
  2. Execute the appropriate setup program for your environment by entering one of the following commands below. Be sure to include the -c option.

    On Solaris

    ./setupSolarisSparc.sh –c

    On Linux

    ./setupLinux32.sh –c

    ./setupLinux64.sh –c

    If you need to specify a different temp directory, add the
    -Djava.io.tmpdir parameter:

    On Solaris

    ./setupSolarisSparc.sh –c Djava.io.tmpdir=[/other/directory]

    On Linux

    ./setupLinux32.sh –c -Djava.io.tmpdir=[/other/directory]

    ./setupLinux64.sh –c -Djava.io.tmpdir=[/other/directory]

Refer to the GUI installation steps in the next section for a description of the various fields and options you will encounter while installing in console mode.

GUI Upgrade

When conducting an upgrade in console mode, you will see a subset of the panels presented when doing a full (clean) installation.

  1. Launch the appropriate setup program:

    On Windows

    Navigate to the Setup\Windows folder and double-click on one of the following:

    setupWin32.exe (for any processor)

    setupWin64.exe (for a 64-bit processor)

    If you need to specify a different temp directory, open a command prompt, navigate to Setup\Windows and then type one of the following:

    setupWin32.exe -Djava.io.tmpdir=[ D: \other\dir ectory ]

    setupWin64.exe -Djava.io.tmpdir=[ D: \other\dir ectory ]

    On Solaris

    Open a terminal window and navigate to Setup/Solaris and run the appropriate executable:

    ./setupSolarisSparc.sh

    If you need to specify a different temp directory, add the
    -Djava.io.tmpdir parameter:

    ./setupSolarisSparc.sh -Djava.io.tmpdir=[/other/directory]

    On Linux

    Open a terminal window and navigate Setup/Linux and run the following executable:

    ./setupLinux32.sh

    If you need to specify a different temp directory, add the
    -Djava.io.tmpdir parameter:

    ./setupLinux32.sh -Djava.io.tmpdir=[/other/dir ectory ]

    ./setupLinux64.sh -Djava.io.tmpdir=[/other/directory]

  2. The Welcome panel appears. (It may take several seconds.) Click Next > to begin the installation.

    If there is an existing ELM 2.x or 3.0 to 3.3.2 installation on your machine, you will get an error since upgrades from version 2.x and 3.0 to 3.3.2 are not supported. The installation will be terminated.

  3. Read and agree to the license agreement and click Next >.

    You are now presented with a progress bar showing the current status of the upgrade. During this phase, the configuration information from the old instances is read and translated into version 3.7 format. This may take some time, depending on the number of instances you had previously created.

    The instance migration is not yet finished here, but must be completed after in the Instance Management Tool.

  4. Click Finish to exit the installer.

    The installation portion of your upgrade is now complete. There is no need to configure your instances – this will happen automatically.

    If you made custom changes to the JNLPs (e.g., language JARs) in your earlier version of Blackboard Collaborate, these changes will have to be reapplied after the upgrade is complete.

  5. Confirm that your upgrade was successful by examining your instances in the ELM Instance Management Tool.