Skip to main content
pdf?stylesheet=default
Blackboard Help

Conduct Full Installation

You can use the Console Mode or GUI installation.

Console Mode Installation

Follow the steps below to invoke the installer 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 setup program for your environment by running 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

    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 Installation

Follow the steps below to perform a GUI installation of Blackboard Collaborate.

  1. Launch the appropriate setup program:

    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)

    On Solaris

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

    ./setupSolarisSparc.sh

    On Linux

    Open a terminal window and navigate to Setup/Linux and run one of the following executables:

    ./setupLinux32.sh (for any processor)

    ./setupLinux64.sh (for a 64-bit processor)

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

    If there is an existing Blackboard Collaborate Suite 12.5.4 installation on your machine, you will get an error and the installation will be terminated:

    App_Already_Installed.png

  3. Read and accept the license agreement.

  4. The Blackboard Collaborate software needs to be installed in a directory on the system. Either accept the default directory or browse to a different directory. The default locations are as follows:

    Windows:

    C:\Program Files\ElluminateLive

    Linux & Solaris

    /opt/ElluminateLive

  5. If you uninstalled a previous installation of ELM and did not delete the application directory, you will be prompted to confirm whether or not to put this new installation into that existing directory.

    Select No and then back up your recordings and backup folders (if desired), delete the old application directory and restart the installer.

    If you select Yes you may have difficulty creating your Root instance.

  6. Select the components you would like installed.

    Select_Components.png

    The panels that follow will vary depending on what components you select here. The steps below assume you have selected all three components. The only Blackboard Collaborate component that can be installed on multiple machines is the Blackboard Collaborate server.

  7. (Windows only) Specify into which Start Menu folder you would like the program shortcut for ELM to be placed. If you don’t want a program shortcut, select the option Don’t create a Start Menu folder.

    Start_Menu.png

  8. (Linux & Solaris only) Specify the directory into which you would like to install the symlinks. If you don’t want any symlinks, select the option Don’t create symlinks.

    Unlike with the Windows Start Menu, you cannot specify a name for the program group in the Application/Launch menu – it is automatically assigned by your operating system. You can specify only the directory into which to place the symlinks.

    If using a command line to launch the Blackboard Collaborate Server, ELM or the License Manager, you can use the symlink in this directory rather than the application in the installation directory.

  9. Define the Blackboard Collaborate Server addresses and port numbers for the services being installed. The fields that are present in this panel will depend on which components you are installing. In the example below, the Blackboard Collaborate Server and ELM (not the License Manager) are being installed and all fields are displayed in the Server details panel.

    Server_Details.png

    • Server Address – The hostname or IP address where you are installing your Blackboard Collaborate Server. The address can be in either an IP format (192.168.1.100) or DNS format (mycompany.com).
    • License Manager Address – The hostname or IP address where you are installing the Blackboard Collaborate License Manager.
    • License Manager Port – The port number for the Blackboard Collaborate License Manager. The default port number is 2186.
    • ELM Port – ELM uses Tomcat (on a default port of 80) to serve up pages to the web clients. You may change this port, but you must ensure that this port number can pass through all firewalls between the web browser and ELM. If you plan on running Blackboard Collaborate Server on this same machine on port 80, you’ll need to make some decisions on how to host both services and on which ports. Generally, ports 80 and 443 can be specified to deal with limitations imposed by some firewalls.
    • Tomcat Control Port –This is the port on which Tomcat receives messages to shut down. The default port number is 8005.
    • Blackboard Collaborate Admin Port – The Blackboard Collaborate Admin Console connects to the Blackboard Collaborate Server on the server’s TCP/IP Control Port. This Control Port must pass through all firewalls between the Admin Console host and the server. The default port number is 2188.
    • Blackboard Collaborate Client Port – The Blackboard Collaborate Client connects to the Blackboard Collaborate classroom server on the server’s TCP/IP Conference Port(s). The Blackboard Collaborate Server can listen on a number of Conference Ports. To be accessible, these port numbers must pass through all firewalls between the client and the server. The single default port number is 2187, but alternate or additional ports (generally ports 80 and 443) can be specified to deal with limitations imposed by some firewalls. Enter a single port number or a comma-separated list of port numbers.

      Note: You need to ensure that firewalls allow Blackboard Collaborate Clients to connect through the conference port you have defined.

    • Ignore Port Check – By default, the installer runs a check on the defined ports. This test is used to ensure that the Blackboard Collaborate Server does not conflict with other services on those ports. In order to proceed to the next installation panel, there must be no services listening on the ports (with the exception described below in A Note on the License Manager Port Check).

      Ignore checking a port if you have a service currently running on that port and you will be closing that service after the installation.

      Ignore checking the License Manager port if you will be installing the License Manager in the future. See A Note on Checking the License Manager Port below for details.

      A Note on Checking the Port

      Normally, the port check tries to verify that a port is not busy. There is one exception: if you are not installing the License Manager at this time, the installer will assume that you have already installed it on another machine (identified in the License Manager Address field). A port check will check to verify the specified port is busy (the License Manager on the other machine is listening on that port).

      It is advisable to conduct a port check on the License Manager port if you have already installed the License Manager on another machine (identified in the License Manager Address field). If you entered the correct License Manager port number, you will proceed to the next installation panel. If you entered the wrong License Manager port number, you will get an error and will have to enter the correct number before being able to proceed to the next installation panel. (Note: if the port number is correct, check that you entered the correct value in the License Manager Address field.)

      Ignore checking the License Manager port if you will be installing the License Manager in the future – otherwise, the port check will produce an error and you will not be able to proceed to the next installation panel.

      The installer verifies the information you entered in the Server Details panel.

  10. The Blackboard Collaborate software requires a license file to operate. Select a license type and, if you already have a license, browse to it.

    If the license you select is expired, you will receive an error and will not be able to proceed with the installation until you enter a valid license. If the license you select is to expire within the next 30 days, you will receive a warning but will still be able to proceed with the installation.

    When installing multiple Blackboard Collaborate Servers, you must use the same license file for all of your servers.

    • If don't already have a license, select Demo License from the License Type drop-down menu.

      License_Details_Demo.png

    • If you have a license, select Have License from the License Type drop-down menu, browse to select your license file or drag and drop your .lic or .lm file from your file browser into the License File field. The license file is examined and the License Details are automatically filled in.

  11. Define the Blackboard Collaborate Server settings.

    If you are not installing the Blackboard Collaborate Server, you will not see this panel.

    Server.png

    • Name – The display name for the server when seen from ELM.
    • Estimated Max Connections – The number of concurrent Blackboard Collaborate users that you believe can be supported on the Blackboard Collaborate Server. Refer to the minimum system requirements for guidelines on the server capacity (based on CPU, RAM, processor type, etc.).
    • Bandwidth Utilization – The maximum combined bandwidth that the Blackboard Collaborate Server has available for all connected Blackboard Collaborate Clients. (The default is Unlimited.)
    • Other Bandwidth (b/s) – The desired bandwidth utilization (in bits per second) value if Bandwidth Utilization set to Other.
  12. Define the ELM Instance Management Tool settings.

    If you are not installing ELM, you will not see this panel.

    Instance_Management_Tool.png

    • System Administrator User Name – The user name required to log in to the ELM Instance Management Tool as a System Administrator. (Maximum of 32 characters. Invalid characters are | # " & < and >.)

      System Administrators can perform all available functions in the ELM Instance Management Tool.

    • System Administrator User Password – The password required to log in to the ELM Instance Management Tool as a System Administrator. (Maximum of 128 characters. Invalid characters are | # " & < and >.)
    • Application Administrator User Name – The user name required to log in to the ELM Instance Management Tool as an Application Administrator. (Maximum of 32 characters. Invalid characters are | # " & < and >.)

      Application Administrators can perform all available functions in the ELM Instance Management Tool except creating and editing system messages and restoring instance data (both of which must be done by the System Administrator).

    • Application Administrator User Password – The password required to log in to the ELM Instance Management Tool as an Application Administrator. (Maximum of 128 characters. Invalid characters are | # " & < and >.)
  13. (Windows only. See next step for Linux & Solaris.) Define the runtime options (system memory). Allocate the maximum available server heap size for the Blackboard Collaborate License Manager, Server and Manager.

    Keep the default values, unless instructed otherwise by Blackboard Collaborate Technical Support. These values should be sufficient for a standard installation.

    Runtime_Options.png

    • License Manager – The memory allocated to the JVM for the License Manager.
    • Blackboard Collaborate Server – The memory allocated to the JVM for the Blackboard Collaborate Server.
    • ELM – The memory allocated to the JVM for ELM.
    • ELM (Max Perm) – The maximum permanent generation, which is the memory allocated to the JVM for multiple instances of ELM. The default of 128 MB is sufficient to support up to eight to ten instances. Allocate additional space it you want to support more instances.

    It is recommended that you allocate no less than 64 MB for maximum permanent generation.

  14. (Linux & Solaris only) Configure the Blackboard Collaborate Server daemon runtime options and define the system memory.

    Linux_Runtime_Options.png

    Define the following for the Server daemon runtime options:

    • Run as root – Specifies whether or not the daemon scripts should be run as the root user. If you set this to No, the Run as user field becomes enabled. (Default is yes.)

      Root must be used if the Blackboard Collaborate Server is going to use a port number less than 1025 (these port numbers are restricted by the OS).

    • Run as user – If not running as the root user, specify the user account (login name) under which the scripts will be run.

      The installer does not verify that the given account is valid, so take care in providing the correct value.

    • Run levels – The run levels under which the server daemons will run. (Default is 3 and 5.)

      When the system changes to a run level that is not selected here, the daemon scripts will be stopped.

    • Kill delay – The amount of time (in seconds) to wait for clean termination before forcing a stop or restart of a service.

    Define the following system memory values. Allocate the maximum available server heap size for the Blackboard Collaborate License Manager, Server and Manager.

    Keep the default values, unless instructed otherwise by Blackboard Collaborate Technical Support. These values should be sufficient for a standard installation.

    • License Manager – The memory allocated to the JVM for the License Manager.
    • Blackboard Collaborate Server – The memory allocated to the JVM for the Blackboard Collaborate Server.
    • ELM – The memory allocated to the JVM for ELM.
    • ELM (Max Perm) – The maximum permanent generation, which is the memory allocated to the JVM for multiple instances of ELM. The default of 128 MB is sufficient to support up to eight to ten instances. Allocate additional space it you want to support more instances.

    It is recommended that you allocate no less than 64 MB for maximum permanent generation.

  15. Select the directories in which you wish to store the log files and recordings on the Blackboard Collaborate server. Either accept the default directories or browse to different directories.

    The default locations are as follows:

    Windows

    C:\Program Files\ElluminateLive\common\logs

    C:\Program Files\ElluminateLive\common\recordings

    Linux

    If you selected “run as root” on the previous panel:

    /var/log/elluminate

    /opt/ElluminateLive/common/recordings

    If not running as root, the recordings directory is the same (as root) but the log directory is different:

    /opt/ElluminateLive/common/logs

    /opt/ElluminateLive/common/recordings

    Beneath the recordings folder will be a sub-folder for each ELM instance you create. All un-transitioned recordings associated with an instance will be stored in its sub-folder.

    • If you are not installing the Blackboard Collaborate Server, you will be prompted for the Log Directory only.
    • If you are installing both the Blackboard Collaborate Server and ELM, you will be prompted for the Log Directory only.

      Folders_Log_Only.png

    • If you are installing the Blackboard Collaborate Server but not installing ELM, in addition to specifying the Log Directory, you will need to map the recordings folder so ELM will be able to find it on the Blackboard Collaborate Server.

      Folders_Log_%26_Recordings.png

    • Log Directory – The directory into which the Blackboard Collaborate Server saves log files.
    • Classroom Server Export Directory – The directory into which the Blackboard Collaborate Server saves recordings.
    • ELM Import Directory – Is used by ELM to retrieve the recordings from the server.

    How you map the recordings folder will vary, depending on your system architecture.

    The recordings folder on the Blackboard Collaborate Server should be shared so that ELM can see and read from the directory.

    For example, when ELM and the Blackboard Collaborate Server are installed on different machines, a drive mapping has to be established so that both ELM and Blackboard Collaborate Server can have access to the same physical directory. For performance reasons, this temporary recording folder should be stored on the same machine as the Blackboard Collaborate Server.

    Once a recording is complete, ELM automatically moves the recording from this temporary folder to a permanent storage folder from which the recordings can be accessed by users. This permanent storage location is defined in the ELM Instance Management Tool.

  16. Review the summary information. Click Next.The installation will begin.

  17. (Optional) Select the option Launch Instance Management Tool automatically when installer exits to open the Instance Management Tool in your browser when installation is complete.

    If you are not installing ELM, you will not see this panel.

    Your installation is now complete. You now need to create your Root instance of ELM using the ELM Instance Management Tool.

  18. Click Finish to exit the installer.

    When the Instance Management Tool opens in your browser, bookmark the URL for easy access next time you want to make a configuration change to an instance or add an additional instance.