© 2007 elluminate, inc. all rights reserved. · 2010-03-18 · elluminate technical support is...

119

Upload: others

Post on 13-Jul-2020

0 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896
Page 2: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

No part of this document may be reproduced or transmitted in any form by any means, electronic or mechanical, including photocopy, recording or using any information retrieval system, without prior written permission. This document contains confidential proprietary information and is protected by law. This document and the information contained in it are intended for the original recipient(s) only. Any dissemination or distribution of the document without prior written permission is strictly prohibited. Elluminate Live!® is a registered trademark of Elluminate, Inc. Java Web Start, Solaris, SPARC, UltraSPARC and the Solaris logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. or other countries. Windows and SQL 2000 Server are trademarks of Microsoft. Mac, Macintosh, the Mac log and OS X are trademarks of Apple Computers, Inc., registered in the U.S. and other countries. SUSE Linux Enterprise Server is a trademark of Novell, Inc. Red Hat Enterprise Linux is a trademark of Red Hat, Inc. Tux, the Linux logo, was created by Larry Ewing using the GNU Image Manipulation Program (GIMP) and generously provided freely to the Linux community. Blackboard and Blackboard Vista and other referenced products and programs of Blackboard are trademarks or registered trademarks of Blackboard Inc. in the United States and/or other countries. All rights are reserved. All other brand or product names are trademarks or registered trademarks of their respective companies or organizations. © 2007 Elluminate, Inc. All Rights Reserved.

Page 3: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Contents Chapter 1 Using This Guide ...........................................1

Audience...................................................................................1 Organization of This Document ................................................1 Contacting Elluminate Technical Support .................................2

Chapter 2 Daemons and Services .................................3 Manual Restart on a Reboot .....................................................3

Windows ...............................................................................3 Linux .....................................................................................4 Solaris ...................................................................................4 Macintosh..............................................................................5

Start, Stop, or Restart the Daemons and Services ...................5 Windows Services.................................................................5 Linux and Solaris Daemons ..................................................6 Macintosh Services ...............................................................6

Chapter 3 Admin Console ..............................................7 Creating Admin Keys ................................................................7

Using the Admin Key Tool.....................................................7 Using the Admin Key Manager..............................................9

Connecting to the Admin Console ..........................................10 The Admin Console User Interface.........................................12

List of Available Commands – Server Level........................12 List of Available Commands – Session Level .....................12 Sending Commands to Running Sessions..........................15

Chapter 4 Elluminate Live! Server ...............................16 General Installation Parameters – elive.conf File....................17

<license> element ...............................................................18 <manager> element ............................................................19 <paths> element .................................................................19 <network> element..............................................................20 <log> element .....................................................................21

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide i

Page 4: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Contents (cont.)

Default Session Parameters - *.tmpl Files.............................. 23<template> element............................................................ 24 <auth> element .................................................................. 25 <services> element ............................................................ 25

Dynamic Session Parameters – ELMdefault.tmpl File ........... 25 <labels> element ................................................................ 27 <auth class> element ......................................................... 27 <services> element ............................................................ 28 <commands> element........................................................ 28

Chapter 5 Elluminate Live! Manager........................... 30 The configuration.xml File ...................................................... 30

AdvancedLDAPDAO .......................................................... 31 daofactory .......................................................................... 33 jdbcdriver............................................................................ 52 configuration....................................................................... 53 backup................................................................................ 62 adapters ............................................................................. 63 encryption........................................................................... 63 scheduler............................................................................ 63 jnlpfactory........................................................................... 64 serverinterface ................................................................... 65 securitymanager................................................................. 65 servertemplatefactory......................................................... 65 codebasemanager.............................................................. 66 mailmanager ...................................................................... 66 proxymanager .................................................................... 67

Date and Time Patterns ......................................................... 67

Chapter 6 Elluminate Live! License Manager............. 69 The .lic File............................................................................. 69 The .lm File ............................................................................ 70 LMStatus Command .............................................................. 70

ii Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 5: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide iii

Chapter 7 Configuring SSL and HTTP Tunneling.......73SSL Guide for a Distributed Configuration ..............................74 Configuring the Elluminate Live! Manager with SSL ...............75 Configuring the Elluminate Live! Server with SSL...................78 SSL Over Shared Network Ports ............................................79 SSL Using a Hardware SSL Accelerator or Appliance............80

Server Configuration ...........................................................80 JNLP Configuration .............................................................80

Configuring HTTP Tunneling ..................................................81 Configuring Tomcat ................................................................82 AES-128 and AES-256 Encryption .........................................84

Prerequisites .......................................................................85 Using AES-128 Encryption..................................................85 Using AES-256 Encryption..................................................85 SSL Cipher Suites List ........................................................86

Chapter 8 Notification Emails ......................................87 Customizing the Notification Email .........................................88

Chapter 9 Configuration of Common Settings ...........91 Changing the Elluminate Live! Manager IP Address ...........92 Changing the Elluminate Live! Server IP Address...............93 Changing the Elluminate Live! License Manager IP

Address........................................................................93 Changing the Elluminate Live! Manager Port ......................94 Changing the Elluminate Live! Server Port .........................95 Changing the Elluminate Live! License Manager Port.........95 Updating the License File....................................................96

Chapter 10 Database Administration ............................98 Supported Databases .............................................................98 Disk Space..............................................................................98 Backups ..................................................................................99

Performing Backups............................................................99 Restoring Data ..................................................................100

Page 6: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Contents (cont.)

Chapter 11 Troubleshooting........................................ 107 The elive.log File.................................................................. 108 The licensemanager.log File ................................................ 109 The wrapper.log File ............................................................ 109 The elm.log File ................................................................... 110 The catalina.out File............................................................. 111 Recovering Un-Transitioned Recordings ............................. 111

List of Tables Table 1: Linux & Solaris Commands to Stop, Start, and Restart the Elluminate Live! Daemons ............. 6

Table 2: Mac Commands to Stop, Start, and Restart the Elluminate Live! Services................................ 6

Table 3: Admin Key Manager Supported Arguments............................................................................. 10

Table 4: Commonly Used Admin Console Commands .......................................................................... 15

Table 5: Parameter Information for <manager> element ....................................................................... 19

Table 6: Parameter Information for <paths> element............................................................................. 19

Table 7: Parameter Information for <network> element......................................................................... 20

Table 8: Log Attributes for Logging Events ............................................................................................ 22

Table 9: configuration.xml - daofactory Parameters............................................................................... 33

Table 10: configuration.xml - configuration Parameters......................................................................... 53

Table 11: Date and Time Patterns ......................................................................................................... 67

Table 12: SLL & HTTP Tunneling Configuration File Locations............................................................. 73

Table 13: Context Map Tokens in Email Notification Template.............................................................. 88

Table 14: Template Object Tokens in Email Notification Template........................................................ 89

Table 15: State Tokens in Email Notification Template.......................................................................... 90

Table 16: Post-Installation Configuration File Locations ........................................................................ 91

Table 17: Log File Locations ................................................................................................................ 107

iv Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 7: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 1 Using This Guide

During installation of Elluminate Live!, you perform basic configuration of the Elluminate Live! Server, Elluminate Live! Manager and Elluminate Live! License Manager. The Advanced Configuration Guide provides all the information necessary to further configure and customize your Elluminate Live! environment.

Refer to the Installation Guide to install the appropriate Elluminate Live! components — Elluminate Live! Server, Elluminate Live! Manager, and Elluminate Live! License Manager.

Audience This guide is intended for anyone responsible for the preparation, installation and administration of Elluminate Live! Servers.

It is assumed that you have a basic working knowledge of the following:

The operating system that will be used to host Elluminate Live! clients and servers:

− Microsoft Windows™

− Apple Macintosh™

− Sun Solaris™

− Red Hat Enterprise Linux™

− SUSE Linux Enterprise Server™

The administration of the Blackboard server version 6.3 or 7.1 (if you are using the Blackboard Adapter).The administration of the Blackboard Vista (formerly WebCT Vista) 3.0, 4.0 or Campus Edition 6.0 servers (if you are using the Blackboard Vista/WebCTAdapter).

Organization of This Document This document is organized into the following chapters:

Chapter 1, Using This Guide — Describes the intended audience, how the manual is organized and how to get technical support.

Chapter 2, Daemons and Services — Describes how to configure the daemons and services to manual restart after a reboot, and how to start, stop, and restart the daemons and services.

Chapter 3, Admin Console — Describes the Admin Console utility, which is installed with the Elluminate Live! Server. The Admin Console is a utility that can be used to obtain and change the status of the Elluminate Live! Server and any running sessions. This chapter describes how to create an Admin Key and use the Admin Console interface.

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 1

Page 8: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 1 – Using This Guide

Chapter 4, Elluminate Live! Server — Provides in-depth details on how to manipulate and/or review the default settings in the elive.conf file and describes the default and dynamic session parameters in the *tmpl and ELMdefault.tmpl files (respectively).

Chapter 5, Elluminate Live! Manager — Provides in-depth information on how to manipulate and/or review the settings in the configuration.xml file, which is used by the Elluminate Live! Manager to set up the sessions and authenticate users against LDAP or Active Directory Servers.

Chapter 6, Elluminate Live! License Manager — Describes the role of the License Manager, the .lm and .lic files and the LMStatus command used to query the License Manager for the set of licenses that it serves. The chapter also describes which servers are connected to use the licenses, and how many license seats are in use and available.

Chapter 7, Configuring SSL and HTTP Tunneling — Describes how to set up secure conferencing.

Chapter 8, Notification Emails — Describes how to customize the notification emails that are sent by the Elluminate Live! Manager to potential attendees of a meeting.

Chapter 9, Post-installation Configuration — Describes how to update some of the more common parameters, such as the Elluminate Live! Manager IP Address.

Chapter 10, Database Administration — Describes how to administer the supported databases. Topics include disk space, backups and data recovery.

Chapter 11, Troubleshooting — Describes the log files that can be used to analyze problems you are encountering with Elluminate Live! The chapter also describes how to recover un-transitioned recordings.

Contacting Elluminate Technical Support Elluminate Technical Support is available through the following channels:

Email [email protected]

Phone 1-403-204-7896 (select option 2)

1-866-388-8674 (select option 4 and then option 2) (Toll Free)

Monday to Friday: 7:00 am – 6:00 pm Mountain (US & Canada)

Fax 1-403-204-7898

URL www.elluminate.com/support

2 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 9: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 2 Daemons and Services

The Elluminate Live! Server, Elluminate Live! Manager and Elluminate Live! License Manager services and daemons are automatically started upon a restart of the server.

This section describes how to configure the daemons and services to prevent their automatic restart and require a manual restart after a reboot. It also discusses how to start, stop, and restart the daemons and services.

Manual Restart on a Reboot To prevent the service from automatically starting on a reboot of the server, set the following services to manual start:

Elluminate Live! License Manager 2.0

Elluminate Live! Manager 2.7

Elluminate Live! Server 8.0

Windows

1. Open the Services window. (Click on Start > Settings> Control Panel, double-click on Administrative Tools, and then double-click on Services.) The Services window appears.

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 3

Page 10: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 2 – Daemons and Services

2. Double-click on the appropriate service. The Properties dialog box for that service will appear. The following is the Elluminate Live! Server 8.0 Properties dialog box.

3. Select Manual from the Startup type pull-down menu.

4. Repeat steps 2 and 3 for each of the Elluminate Live! services that you want to change to a startup type of manual.

Linux Execute the following commands:

chkconfig —del ellm2_0

chkconfig —del elm2_7

chkconfig —del elive8_0

Solaris The following directories are based on the run levels that you selected in the installation:

/etc/rc2.d

/etc/rc3.d

/etc/rc4.d

/etc/rc5.d

4 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 11: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Execute the following commands in each directory associated with the run levels you selected during installation:

unlink ./S85 ellm2_0d

unlink ./S85 elm2_7d

unlink ./S85 elive8_0

Macintosh Delete the following directories:

/Library/StartupItems/ElluminateLiveLicenseManager

/Library/StartupItems/ElluminateLiveManager

/Library/StartupItems/ElluminateLiveServer

Start, Stop, or Restart the Daemons and Services You can manually start, stop, or restart the Elluminate Live! Server, Elluminate Live! Manager and Elluminate Live! License Manager daemons and services.

Windows Services

1. Open the Services window. (Click Start > Settings> Control Panel, double-click on Administrative Tools, and then double-click on Services.) The Services window appears.

2. Right-click on the appropriate service and select the desired action from the pull-down menu.

Looking at the Services window you can see it has columns for Name, Description, Status, Startup Type, and Log On As. Detailed information is available on each service by double-clicking on any of the entries.

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 5

Page 12: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 2 – Daemons and Services

Linux and Solaris Daemons The following table lists the commands used to stop, start, and restart the Elluminate Live! daemons on Linux or Solaris.

The restart command is not supported on Solaris.

Table 1: Linux & Solaris Commands to Stop, Start, and Restart the Elluminate Live! Daemons

Daemons Action Command

Stop ./etc/init.d/ellm2_0d stop

Start ./etc/init.d/ellm2_0d start License Manager

Restart ./etc/init.d/ellm2_0d restart

Stop ./etc/init.d/elm2_7d stop

Start ./etc/init.d/elm2_7d start Manager

Restart ./etc/init.d/elm2_7d restart

Stop ./etc/init.d/elived8_0 stop

Start ./etc/init.d/elived8_0 start Server

Restart ./etc/init.d/elived8_0 restart

Macintosh Services The following table lists the commands used to stop, start, and restart the Elluminate Live! services on the Macintosh.

Table 2: Mac Commands to Stop, Start, and Restart the Elluminate Live! Services

Services Action Command

Stop sudo SystemStarter stop eLiveLicenseManager

Start sudo SystemStarter start eLiveLicenseManager License Manager

Restart sudo SystemStarter restart eLiveLicenseManager

Stop sudo SystemStarter stop eLiveManager

Start sudo SystemStarter start eLiveManager Manager

Restart sudo SystemStarter restart eLiveManager

Stop sudo SystemStarter stop eLiveScheduler8_0

Start sudo SystemStarter start eLiveScheduler8_0 Server

Restart sudo SystemStarter restart eLiveScheduler8_0

Using the sudo command may require you to enter a password. If you don't know the password, consult your System Administrator.

6 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 13: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 3 Admin Console

Elluminate Live! Server 8.0 is installed with an Admin Console utility. The Admin Console is a utility that allows the System Administrator to view a live snapshot of the Elluminate Live! Server.

The Admin Console utility can be used to perform the following functions:

View a list of the running and scheduled sessions.

View a list of connected users in each currently running session.

Remove a user from a currently running session.

Suspend access to any currently running session.

Shut down any currently running session.

Shut down the Elluminate Live! Server (the Admin Console cannot be used to start the server).

Before you can start using the Admin Console to view the sessions/users on the Elluminate Live! Server, you will need to generate a key for the Admin Console. If you will be running in a GUI environment, you can use the Admin Key Tool to do this. If you will be running in console mode, you can use the Admin Key Manager. Both methods are described below.

Creating Admin Keys If you wish to use the Admin Console with a specific server, you must be issued a cryptographic key and password. The Admin Key Tool and the Admin Key Manager are used to generate Admin keys.

Using the Admin Key Tool Open the Admin Key Tool:

Windows

Change to the following directory:

C:\Program Files\ElluminateLive\Server8_0\bin

Run the Admin Key Tool executable file:

AdminKeyTool.exe

or

Click on Start > Programs > Elluminate Live > Tools > Server > Server 8.0 > AdminKeyTool.

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 7

Page 14: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 3 – Admin Console

Linux & Solaris

Change to the following directory:

/opt/ElluminateLive/server8_0/bin

Run the Admin Key Tool bin file:

./AdminKeyTool.bin

Mac

Change to the following directory:

/Applications/ElluminateLive/server8_0/bin

For Mac users, to run any of the Admin Console utilities, you must run as the root user. To run as the root user, you must use the sudo command.

Using the sudo command may require you to enter a password. If you don't know the password, consult your System Administrator.

Run Admin Key Tool command file:

sudo ./AdminKeyTool.command

The Elluminate Live! Admin Key Tool window appears:

When the Admin Key Tool is invoked for the first time, only the key file for the server will be listed. (The server key file, called Master.keys, is created by the installer and is located in the /lib directory under the root of the installed Server8_0 directory.)

Multiple encryption keys may be created with this tool, providing the ability to assign a unique key to each administrator, and permitting easy key revocation.

To create a new key, click on the Create Admin Key button. Follow the on-screen instructions and provide

the name of the key owner;

a password for the administration key file; and

the pathname of the administration key file itself.

8 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 15: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

After the key is created, it will be shown in the list. You may create as many key files as you wish.

To delete a key and, therefore, invalidate the associated key file, select it from the list and click on the Delete Admin Key button.

Changes to the Administrative keys (stored in the Master.keys file) will be picked up by the Elluminate Live! Server immediately and do not require a restart of the server. Deleting Administrative keys will require a restart.

Using the Admin Key Manager Sites running their Elluminate Live! Server without an x display can use the Admin Key Manager to administer their Master.keys and administrative key files.

To start the Admin Key Manager, do one of the following at the command prompt:

Windows

Change to the following directory:

C:\Program Files\ElluminateLive\Server8_0\bin

Run the Admin Key Manager executable file:

AdminKeyManager.exe

Linux & Solaris

Change to the following directory:

/opt/ElluminateLive/server8_0/bin

Run the Admin Key Manager bin file:

./AdminKeyManager.bin

Mac

Change to the following directory:

/Applications/ElluminateLive/server8_0/bin

For Mac users, to run any of the Admin Console utilities, you must run as the root user. To run as the root user, you must use the sudo command.

Using the sudo command may require you to enter a password. If you don't know the password, consult your System Administrator.

Run the Admin Key Manager command file:

sudo ./AdminKeyManager.command

The Elluminate Live! Admin Console window appears.

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 9

Page 16: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 3 – Admin Console

Admin Key Manager is a command-line utility that supports the following arguments.

Table 3: Admin Key Manager Supported Arguments

Argument Description

-add name path Generates a new key with the specified user name and writes it into the administrative key file specified by path. The Admin Key Manager will prompt for the password for this name. It is possible to put multiple –add commands on a single command line. The certificate for this key will be added to the master key file, and the administrative key file generated. Linux Example: will create an Admin Key for Mark called mark.keys in the bin directory. /AdminKeyManager.bin -add Mark /opt/ElluminateLive/server8_0/bin/mark

-cpw path Changes the password associated with the administrative key file found at path. Will prompt for the existing password for this file.

-del name Deletes the administrative key with the specified user name.

-list Lists the master and administrative keys defined for the Elluminate Live! Server Scheduler. This information is derived from the master key file.

-master path Defines the path of the Master.keys file to the Admin Key Manager. This information is required for any operation.

-quit Initializes the master key file and generates the server master key if it does not already exist. This is automatically done whenever one of the other operations is performed, but using –quit allows the master key file to be created without performing any other operation.

Connecting to the Admin Console The Admin Console communicates with the Elluminate Live! Server on a TCP/IP Control Port that is specified in the elive.conf file. By default, it connects through port 2188.

Each user who can access the Admin Console has an administrative key file, created when the user’s administration key is generated with the Admin Key Tool or Admin Key Manager. The user key file contains the user’s administration key and a certificate for the server master key. Each user key file is encrypted with a password.

1. Launch the Admin Console.

Windows

Change to the following directory:

C:\Program Files\ElluminateLive\Server8_0\bin

Run the Admin Console executable file:

AdminConsole.exe

or

Click on Start > Programs > Elluminate Live > Tools > Server > Server 8.0 > AdminConsole.

10 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 17: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Linux & Solaris

Change to the following directory:

/opt/ElluminateLive/server8_0/bin

Run the Admin Console bin file:

./AdminConsole.bin

Mac

Change to the following directory:

/Applications/ElluminateLive/server8_0/bin

For Mac users, to run any of the Admin Console utilities, you must run as the root user. To run as the root user, you must use the sudo command.

Using the sudo command may require you to enter a password. If you don't know the password, consult your System Administrator.

Run Admin Key Tool command file:

sudo ./AdminConsole.command

The Elluminate Live! Admin Console window appears:

2. To connect the console to the Elluminate Live! Server, from the Connection menu select Connect (as show above). The Select Admin Key File dialog box will open.

3. In the Select Admin Key File dialog, select a key file and then enter the key file’s password. Once connected to the Elluminate Live! Server, the Admin Console appears with the >> prompt.

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 11

Page 18: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 3 – Admin Console

The Admin Console User Interface The Admin Console sends and receives messages to the Elluminate Live! Server via a defined protocol. The display in the console area shows the text as it is received from the Elluminate Live! Server. In much the same way as an "ftp" client may act, this creates some apparent idiosyncrasies for the administrative user:

The interface is via a command line.

There are no "Are you Sure?" safety prompts. Use with care.

Each displayed response is prefixed with a message number. Just ignore the first 3-digit number that is at the beginning of each response.

List of Available Commands – Server Level For a list of available commands, at the >> prompt type the help command. The list of commands and their descriptions will be displayed on the Elluminate Live! Admin Console.

List of Available Commands – Session Level To display the list of commands available for a specific session currently running on your Elluminate Live! Server, do the following:

1. At the >> prompt, type the command who. A list of sessions currently running on the server will be listed.

12 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 19: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 13

Page 20: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 3 – Admin Console

2. At the >> prompt, enter the name of your session followed by the help command (e.g., ELMDefault|Math101#1143234886289 help). This will give you a list of commands that may be run on a per session basis.

14 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 21: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Sending Commands to Running Sessions It is possible to send commands directly to a running session by using the file name prefix.

At the >> prompt, type list to see the running sessions. The following example lists one running session called Math.

ELMDefault|Math#140" running "ELMDefault|Math#140

To find out who is in the Math session, at the>> prompt, type the command:

ELMDefault|Math#140 who

Please note that the Admin Console uses the term "room" to refer to a "session".

The following table contains a list of commands that are useful to send to a session.

Table 4: Commonly Used Admin Console Commands

Admin Console Command Description

{room} who Lists all of the participants in {room}.

{room} remove Removes a participant from {room}.

{room} close Closes {room} and ejects all of the participants. The room will stay locked until it is "open"ed.

{room} open Opens {room} and accepts all of the participants. The room will stay open until it is "close"ed.

{room} quit Shuts down {room}. This may be done only to a room that has been "close"d. If the room is scheduled to run, it will automatically be restarted by the server within one minute. If autolaunch is enabled, the room will start again when the next participant joins the room.

{room} help It will list all commands (and their descriptions) that may be used on a per room basis.

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 15

Page 22: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 4 Elluminate Live! Server

The Elluminate Live! Server is an application that runs within the Windows, Linux, Solaris and Mac environments and hosts multiple sessions.

The Elluminate Live! Server runs on a host machine and listens on one or more network ports for connections from clients wishing to join a session. The server checks to see that the client trying to enter a session is a valid user (authentication level) and, if they are, the server then calls the Elluminate Live! License Manager to verify that there are enough licenses available for the user to join the session. If the user is valid and there are enough licenses, the server sends the session configuration information to the Elluminate Live! Manager to create the session (e.g., configure the recording parameters, preload whiteboard files, multimedia files, etc.) and then logs the user into the session as either a Moderator or Participant.

By default, the Elluminate Live! Manager is configured to automatically launch sessions "on demand" within the scheduled time period. If the user is authenticated, and there are enough licenses, the server will start the session. The session will stay running until it has been empty for a preset length of time, after which the session will be terminated.

When you install the Elluminate Live! software, you are prompted to perform some basic configuration tasks:

1. Set the general installation parameters (defined in the elive.conf file).

2. Set Elluminate Live! Manager or Adapter parameters for Elluminate Live! sessions. There are two template files used to set up the sessions:

ELMDefault.tmpl — This file defines the sessions for the Elluminate Live! Manager.

ELMBlackboard.tmpl — This file defines the sessions for the Elluminate Live! Manager when accessed via the Blackboard Learning Management System (installed only if the Blackboard adapter is selected during the installation).

3. Set specific session parameters (in configuration.xml file) including the following:

The session operational schedule

The session participant authentication mechanism

The session "start time" setting

The session recording action

The session bandwidth limit

The session preloaded whiteboard presentation (if any)

The whiteboard protection status

Normally, the general installation parameters do not need to be modified after installation — unless support for secure communications is required or you are making changes to your license file. The

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 16

Page 23: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

definable parameters in the configuration.xml file come with reasonable defaults and are always configured during the installation of the Elluminate Live! software.

As a general rule, the default session parameters defined in the *.tmpl files need to be modified only when you need to define a limit on video quality for the recording, or change the total allowed MB for multimedia file distributions.

All of these installation and operational parameters are stored in editable XML format files. To set or modify a parameter, the appropriate XML file is simply modified in place with an XML editor. Depending on which XML file is modified, the Elluminate Live! Server may have to be stopped and then restarted to pick up the changes.

Use of the elive.conf and ELMDefault.tmpl files is described below. The configuration.xml is described in Chapter 5 — Elluminate Live! Manager and the ELMBlackboard.tmpl file is described in the Adapter Configuration Guide located in the Documentation directory of the installation CD.

General Installation Parameters – elive.conf File The values assigned to the various attributes in the elive.conf file are set during installation and, in most cases, will not need to be modified. However, if you wish to modify any of the general installation parameters, edit the elive.conf XML file. This file is located in the root of the ElluminateLive installation directory. The root directory is chosen during installation and may vary between systems. The default locations of the elive.conf file are as follows:

Windows

C:\Program Files\ElluminateLive\server8_0\elive.conf

Linux & Solaris

/opt/ElluminateLive/server8_0/elive.conf

Mac

/Applications/ElluminateLive/server8_0/elive.conf

To ensure that no extra characters will be saved during the editing of the file, it is recommended that it be edited with a text editor only (e.g., Notepad or emacs).

Any modifications made to the elive.conf file will require a restart of the Elluminate Live! Server. Stopping or restarting the Elluminate Live! Server will immediately terminate all running sessions.

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 17

Page 24: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 4 – Elluminate Live! Server

A typical elive.conf file (on Windows) may look like the following:

<?xml version="1.0" encoding="utf-8"?> <schedulerConfig> <license path="C:\Program Files\ElluminateLive\common\licenses\ QA-Academic.lm" host="192.168.1.124" port="2186" /> <manager> <externalName value="192.168.1.124" /> <elsRecordingFolder value="C:\Program Files\ElluminateLive\ common\recordings" /> <elmRecordingFolder value="C:\Program Files\ElluminateLive\ common\recordings" /> <maxLoad value="50" /> <serverLabel value="192.168.1.124" /> <codeBase value="http://192.168.1.124:8080/lib/8.0" /> <encoding value="UTF-8" /> </manager> <paths sessions="C:\Program Files\ElluminateLive\server8_0\sessions" services="C:\Program Files\ElluminateLive\server8_0\lib\services"/> <network bandwidth="10000000"> <console port="2188" keyFile="C:\Program Files\ElluminateLive \common\licenses\Master.keys"/> <conference port="2187" protocols="jinx"/> </network> <log file="C:\Program Files\ElluminateLive\common\log\elive.log" size="250000"> log.load log.launch log.access </log> </schedulerConfig>

<license> element <license path="C:\Program Files\ElluminateLive\common\licenses\QA-Academic.lm" host="192.168.1.124" port="2186" />

The <license> element tag of the elive.conf file contains a path to the .lm file and a reference to the License Manager host and port. The .lm file identifies the license target (customer/product/serial number) from which to request the license, and authentication data to prove that the Elluminate Live! Server is allowed to have licenses from that target.

You may add/update the license at any time without re-installing the software. For step-by-step instructions on how to change the path, host, and or port attributes, refer to Chapter 9 – Configuration.

18 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 25: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

<manager> element <manager> <externalName value="192.168.1.124" /> <elsRecordingFolder value="C:\Program Files\ElluminateLive\ common\recordings" /> <elmRecordingFolder value="C:\Program Files\ElluminateLive\ common\recordings" /> <maxLoad value="50" /> <serverLabel value="192.168.1.124" /> <codeBase value="http://192.168.1.124:8080/lib/8.0" /> <encoding value="UTF-8" /> </manager>

Table 5: Parameter Information for <manager> element

Parameter Description

externalName The IP Address or DNS of the session server.

elsRecordingFolder The location to which the Elluminate Live! Server will write the vcr file.

elmRecordingFolder The location from where the Elluminate Live! Manager will import the vcr file into its own datastore.

maxLoad The estimated load that this server can take. This value is used for the smart scheduling by Elluminate Live! Manager. If this value is set to 0, then Elluminate Live! Manager will not schedule anything on this server. Refer to the Installation Guide for best practices for loading of the Elluminate Live! Server.

serverLabel A unique identifier for this session server.

codeBase The URL where the codebase (client jars) are to be used for any session scheduled on this server.

<paths> element <paths sessions="C:\Program Files\ElluminateLive\server8_0\sessions" services="C:\Program Files\ElluminateLive\server8_0\lib\services"/>

Modification of the <paths> element section of elive.conf is not recommended.

Table 6: Parameter Information for <paths> element

Parameters Description

sessions The pathname for the directory that contains the *.tmpl files that define default session parameters.

services The services pathname for the directory that contains optional features of the Elluminate Live! Server.

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 19

Page 26: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 4 – Elluminate Live! Server

<network> element <network bandwidth="10000000"> <console port="2188" keyFile="C:\Program Files\ElluminateLive \common\licenses\Master.keys"/> <conference port="2187" protocols="jinx" interface="IPaddress"/> </network>

Table 7: Parameter Information for <network> element

Parameters Description

bandwidth The maximum bandwidth, in bits-per-second, the Elluminate Live! Server should use across all of the running sessions.

The <network> element tag specifies the network ports and resources that are used by the Elluminate Live! Server. The optional bandwidth attribute allows you to specify an upper limit to the bandwidth that will be used by the Elluminate Live! Server (specified in bits-per-second). If it is not supplied, the server will not try to limit aggregate bandwidth. If you installed the server with unlimited bandwidth, then the <network> tag will not have the bandwidth attribute defined. For example, <network>.

The network section has various sub-sections that define the network resources used by the server:

Console Sub-section

The "console" sub-section defines the TCP port and master key file needed to allow remote management of the Elluminate Live! Server using the Admin Console tool.

Some administration operations for the Elluminate Live! Server can be handled from a remote machine through the Admin Console tool. The Elluminate Live! Admin Console connects to the Elluminate Live! Server on its single Control Port number. This number must be unique from all other network services on the host machine and from all Conference port numbers (see below). The Control Port number must be in the range of 1 - 65535.

For UNIX, if a port is selected in the range of 1-1024, the server must be run as root.

This Control Port must pass through all firewalls between the Admin Console and the Elluminate Live! Server. Since some firewalls restrict access to some ports, or only allow access to specific ports, it may be necessary to modify the value of this field. Normally, however, the default Elluminate Live! Control Port number of 2188 is sufficient.

The pathname of the master key file is used by the remote access Admin Console tool to authenticate connections to the console port. The keys in the admin key file are maintained using the Admin Key Tool or Admin Key Manager. Modification of this pathname is not recommended.

Only one instance of the "console" sub-section is allowed.

20 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 27: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Conference Sub-section

A "conference" sub-section defines a port on which the Elluminate Live! Server will accept connections from clients wishing to join a session, and the protocols that can be run on that port.

Elluminate Live! Server must be assigned to at least one TCP Conference Port number. Multiple ports can be provided with multiple instances of this sub-section. The port numbers must be unique from all other network services on the host machine, and from each other, and the console port number (see above). Conference Port numbers must be in the range of 1-65535.

For UNIX, if a port is selected in the range of 1-1024, the server must be run as root.

This Conference Port must pass through all firewalls between the client and the server. Since some firewalls restrict access to some ports, or only allow access to specific ports (for instance, port 80), it may be necessary to configure multiple ports. However, normally the default Elluminate Live! Conference Port number of 2187 is sufficient.

The protocols attribute of a conference port determines whether the port allows and/or requires a secured protocol for connections received on that port. The standard protocol for normal unencrypted conferencing is called jinx, and is configured automatically during installation. The protocols need to be changed only if secure conferencing is being configured. Secure conferencing cannot be configured from within the installation.

The interface attribute can be used to bind the classroom server to particular network card if multiple network cards are installed on the machine.

For a description of how to configure secure conferencing, see Chapter 7 – Configuring SSL and HTTP Tunneling.

SSL Sub-section

A single "ssl" sub-section defines the file and password for the Secure Socket Layer (SSL) encryption keys required for encrypted communication. This section is NOT created during installation and is only required if secure client connections are required.

Please refer to Chapter 7 – Configuring SSL and HTTP Tunneling for further information on SSL configuration.

<log> element <log file="C:\Program Files\ElluminateLive\common\log\elive.log" size="250000"> log.load log.launch log.access </log>

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 21

Page 28: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 4 – Elluminate Live! Server

The <log> element tag specifies the following:

The pathname of the current Elluminate Live! log file.

The maximum size in bytes of the Elluminate Live! log file.

When the log file grows over this maximum size, it is renamed to {prefix}.1.{suffix}. For instance, the default name for this log file is elive.log. When it grows over the maximum size, this file will be renamed to elive.1.log and logging will continue in a new file called elive.log again. Previous log files will have their middle number increased by one. For example, if there already was a file called elive.1.log, it is renamed to elive.2.log. In this way, the current log file is always called elive.log. The previous log file would be called elive.1.log, the next oldest would be called elive.2.log, and so on.

As there is no automatic truncation of the log files and no limit to the number of log files that can be generated, care should be taken to ensure sufficient disk space is available. It may become necessary to delete old log files.

Log file tracking specifications

There are numerous log attributes that may be included. The example above lists three of these attributes – log.load, log.launch, and log.access. The following table lists the supported log attributes and a brief description of each attribute.

Table 8: Log Attributes for Logging Events

Log attributes Description

log.launch Log the launching and shutdown of sessions.

log.access A shortcut for both log.access.grant and log.access.deny (default with installation).

log.access.grant Log users that were granted access to a session (default with installation).

log.access.deny Log users that were denied access to a session.

log.command Log the execution of the startup commands when a session starts.

log.load Log loading of the session and template files (default with installation).

log.memory Log the current java heap usage (current, max since last message, overall maximum) whenever the scheduler runs (generally once-per-minute, but it may be more often if an update is forced).

log.statistics Log statistics when a user leaves or the session shuts down: - When a client leaves: elapsed time in the session, and bytes/packets in and out. - When a session closes: elapsed time open, bytes/packet in and out, max and

average user count.

jinx.hangup Log when a user leaves on purpose (either at their request or the server/moderator).

jinx.disconnection Log when a user connection is terminated due to an error or timeout.

log.transfer.file Log all files loaded into the file transfer library. Each logged event will contain who sent the file, the file name and extension, file size, and the time and date that the file was sent.

22 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 29: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Default Session Parameters - *.tmpl Files Default session parameters for the sessions are provided in XML format files that have a suffix of ".tmpl". The purpose of *.tmpl files is to specify behaviors for sessions that are automatically created when Participants and Moderators connect to the Elluminate Live! Server. These files are used to jump-start the session creation process and identify the location where additional session-specific parameters can be located.

The *.tmpl files contain the following information:

Location from which to request additional session-specific parameters

Default session participant authentication mechanism

Default bandwidth limit for sessions

There are two template files used to set up the sessions:

ELMDefault.tmpl — This file is the basis for sessions scheduled via the Elluminate Live! Manager. Each scheduled meeting can have individual and specific settings as defined at meeting creation time through the Elluminate Live! Manager.

ELMBlackboard.tmpl — This file defines the sessions for the Elluminate Live! Manager when accessed via the Blackboard Learning Management System (only installed if the Blackboard adapter is selected during the installation).

The *.tmpl files are normally located in the sessions directory under the root installation directory. The location of the ElluminateLive and the sessions directories is chosen during installation and may vary between systems. In addition, it is possible to change the name and location of the sessions directory by modifying the general installation parameters in the file elive.conf. See the previous section for more details.

The default locations of the .tmpl files are as follows:

Windows

C:\Program Files\ElluminateLive\server8_0\sessions\*.tmpl

Linux & Solaris

/opt/ElluminateLive/server8_0/sessions/*.tmpl

Mac

/Applications/ElluminateLive/server8_0/sessions/*.tmpl

To ensure that no extra characters will be saved during the editing of files, it is recommended that they be edited with a text editor only (e.g., Notepad or emacs).

Changes to these template files do not require the Elluminate Live! Server to be restarted. The running Elluminate Live! Server checks the "sessions" directory for *.tmpl file changes about once a minute. If any such file has been added, deleted, or updated, the changes are processed and will take effect on all subsequently launched sessions.

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 23

Page 30: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 4 – Elluminate Live! Server

To ensure that any changes were processed successfully, just check the end of elive.log in the installed logs directory. Processing information will appear in this file no more than one minute after changes are saved to a *.tmpl file.

The following is an example of an ELMDefault.tmpl file (for Windows).

<?xml version="1.0" encoding="utf-8"?> <!-- This file provides a default template for Elluminate Live! Manager.--> <template groupName="ELMDefault" autoLaunch="true" launchDirector="http://192.168.1.124:8080/buildtemplate.event"> <!--Room authentication is to be done by Elluminate Live! Manager.--> <auth class="WebAccessManager"> <url string="http://192.168.1.124:8080/authenticate.event? adapter=default"/> </auth> <!-- Enable all classroom functions. --> <services> <all/> </services> </template>

<template> element Only the speed parameter in the <template> element should be modified. Changing any of the other settings may result in the Elluminate Live! Manager being unable to launch a session.

<template groupName="ELMDefault" autoLaunch="true" launchDirector="http://192.168.1.124:8080/buildtemplate.event" speed="28800">

Parameters Description

groupName Identifies the adapter that this template belongs to. This value should not be changed.

autoLaunch Specifies whether scheduled sessions can be automatically launched by the session server (on demand). This value should not be changed.

launchDirector The URL that the Elluminate Live! Server should call to obtain additional session-specific parameters when first starting up the session. This value should not be changed.

24 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 31: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Parameters Description

speed Limits the peak bandwidth of each connection to a session. This may be desirable if the Elluminate Live! Server is hosted on a machine with limited or shared connectivity to the Internet. The peak bandwidth limit options are as follows:

28800 33600 60000 100000 250000

Regardless of this setting, the Elluminate Live! Server will not establish a connection to a client at a peak bandwidth setting that is higher than the maximum specified by the client. By default, the speed= parameter is not included in the ELMDefault.tmpl file. The absence of the speed= parameter allows the Elluminate Live! Server to communicate with each client based solely on each client’s bandwidth settings.

<auth> element The <auth> element specifies the default authorization mechanism that is to be used to validate Participants and Moderators entering a session. User names and passwords are authenticated via a servlet or cgi script that is accessible to the session server by way of a URL.

<auth class="WebAccessManager"> <url string="http://192.168.1.124:8080/authenticate.event? adapter=default"/> </auth>

You are advised not to change these values for ELMDefault.tmpl

If you are using the Blackboard adapter, the access manager used to authenticate Participants and Moderators entering a session is RemoteAccessManager, not WebAccessManager. Therefore, the definition would be <auth class=’RemoteAccessManager’>.

<services> element The <services> element is for internal Elluminate Live! use and should not be modified.

Dynamic Session Parameters – ELMdefault.tmpl File When the Elluminate Live! Server invokes the URL defined by the launchDirector attribute of the <template> element, Elluminate Live! Manager uses the ELMdefault.tmplELMdefault.tmpl file as the template to return additional session parameters.

The ELMdefault.tmplELMdefault.tmpl file contains the following information:

Session name

Session grace period

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 25

Page 32: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 4 – Elluminate Live! Server

Session participant authentication mechanism

Session labels

Session recording mode

Session preloads — whiteboard and multimedia

Default maximum talkers

The default locations of the ELMdefault.tmpl file are as follows:

Windows

C:\Program Files\ElluminateLive\server8_0\sessions\ELMdefault.tmpl

Linux & Solaris

/opt/ElluminateLive/server8_0/sessions/ELMdefault.tmpl

Mac

/Applications/ElluminateLive/server8_0/sessions/ELMdefault.tmpl

The following is the ELMdefault.tmpl file

<?xml version="1.0" encoding="utf-8"?> <!-- This file provides a default template for Elluminate Live! Manager. --> <!-- Allow automatic starting of virtual classrooms and allow for a grace --> <!-- period of 5 minutes after the final participant leaves before --> <!-- shutting down an automatically started room. --> <session conferenceName="#{GROUPNAME}|#{MEETINGNAME}###{MEETINGID}" grace="#{GRACE}" > <!-- Specify that rooms are to be supervised at all times. --> <properties supervised="#{SUPERVISED}" defaultAccess="#{FULLPERMISSIONS}"/> <!--Establish the names for classroom sessions and user roles.--> <labels session="class" Session="Class" sessions="classes" Sessions="Classes" participant="#{userLabel}" Participant="#{userLabel}" participants="#{userLabel}s" Participants="#{userLabel}s" group="breakout room" Group="Breakout Room" groups="breakout rooms" Groups="Breakout Rooms" moderator="#{facilitatorLabel}" Moderator="#{facilitatorLabel}" moderators="#{facilitatorLabel}s" Moderators="#{facilitatorLabel}s"/>

26 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 33: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

<!-- Room authentication is to be done by Elluminate Live! Manager. --> <auth class="#{AUTHENTICATIONCLASS}"> <url string="#{ELMPROTOCOL}://#{ELMADDRESS}/#{CALLBACK}"/> </auth> <!-- Enable all classroom functions. --> <services> <all/> </services> <commands> #{loop:PRELOADS}<setup>#{if:currentRow.getType = media}multimedia load#{end}#{if:currentRow.getType = whiteboard}whiteboard preload#{end} #{ELMPROTOCOL}://#{ELMADDRESS}/ load_resource.event?preloadId=#{currentRow.getKey} #{if:currentRow.getType = media}&amp;displayname= #{currentRow.getName}#{end}</setup> #{if:currentRow.getType = whiteboard}<setup>whiteboard proprietary#{PROTECTEDWHITEBOARD}</setup>#{end} #{end} <setup>startTime set {schedule.start,date,yyyy-MM-dd HH:mm} </setup> <setup>recorder path #{RECORDINGFOLDER}/#{RECORDINGID}.vcr </setup> <setup>recorder options append</setup> <setup>recorder mode #{RECORDINGMODE}</setup> <setup>attendance notify #{ELMPROTOCOL}://#{ELMADDRESS}/ attendance.event</setup> <setup>attendance ping 5</setup> <setup>attendance encoding UTF-8</setup> <setup>audio maxTalkers #{MAXTALKERS}</setup> <setup>hand #{RAISEHANDONENTER}</setup> </commands> </session>

Any item identified by the following sequence #{identifier} is a token. These tokens are dynamically substituted with values defined for the specific session for which the parameter file is being generated.

<labels> element Within the <labels> element you have the option to change the session and group labels. The other labels are dynamically substituted.

<auth class> element The <auth class> element is for internal Elluminate Live! use and should not be modified.

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 27

Page 34: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 4 – Elluminate Live! Server

<services> element The <services> element is for internal Elluminate Live! use and should not be modified.

<commands> element This section is used to send commands to the session server to set up the default session environment.

Within the <commands> element you may set the quota size for the multimedia and whiteboard file limits and specify the video quality used for recordings.

Please note, the commands described below are not included with the default installation and, if required, must be added to the ELMdefault.tmpl file manually after installation.

Multimedia Files Quota

You have the option to specify the maximum allowable quota for multimedia files that may be loaded:

<setup>multimedia quota 55M</setup>

If this command is provided, then the Elluminate Live! Server will not allow a Moderator to load multimedia files that exceed the total quota. This quota applies to the total of all files loaded into the multi-media library at any one time.

The value is an integer with an optional qualifier. When only an integer is present, the quota represents bytes. When the optional qualifier "K" or "M" is appended to the integer value (as in the above example), the quota represents Kilobytes or Megabytes, respectively.

If this command is not provided, there is no default quota value – it is unlimited.

Whiteboard Memory Limit

You have the option to specify a memory limit for whiteboard images:

<setup>whiteboard maxImageCache 15000000</setup>

If this command is provided, then the combined amount of compressed image data that can be present on all public whiteboard screens is limited to the specified number of bytes (15000000 in the above example). If session participants attempt to load images or presentations that will exceed this total value, they will be presented with a dialog box warning them to delete some unused images and/or reduce the number of images in their presentation.

Setting this value can be useful for controlling the overall Elluminate Live! Server memory usage on machines with a limited amount of memory.

If this command is not provided, the default value is 10 Megabytes.

28 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 35: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 29

File Transfer Quota Limit

You have the option to specify the maximum allowable quota for files that may be transferred:

<setup>transfer quota 55M</setup>

If this command is provided, then the Elluminate Live! Server will not allow file transferring that exceeds the total quota. This quota applies to the total of all files loaded into the File Transfer library at any one time. The value is an integer with either the qualifier "K" or "M" appended to the integer value (as in the above example), the quota represents Kilobytes or Megabytes, respectively.

If this command is not provided, the default quota size is 10 Megabytes.

Disable the File Transfer Feature

If this command is provided, then all Moderators and Participants will not be able to load files or load URLs in any Elluminate Live! session. The various buttons, menu options, and the File Transfer window will still be visible in the GUI, but will not function.

<setup>transfer disable</setup>

If the command is not provided, the File Transfer feature will be fully functional.

Recorded Quality Setting

You have the option of specifying the quality of video during recordings:

<setup>video recorderQuality XX</setup>

In order to reduce storage of recordings with video, the above command can be used. If the command is provided, then the recorder will contain a video image only at the defined quality where XX is one of the following:

CG – Course Gray – lowest resolution, lowest storage

CC – Course Color – low resolution, low storage

FG – Fine Gray – higher resolution, more storage

FC – Fine Color – highest resolution, most storage

If the command is not specified, the default is FC – Fine Color.

Page 36: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 Elluminate Live! Manager

The Elluminate Live! Manager is a management console for the Elluminate Live! Server. The Elluminate Live! Manager creates the sessions/meetings and validates the users.

Within the Elluminate Live! Manager, "sessions" are referred to as "meetings".

The configuration.xml File The configuration.xml file contains all of the system-level operational parameters and settings for the Elluminate Live! Manager and is located in the manager directory.

You are strongly advised to make a backup copy of this file prior to editing it.

Changing configuration.xml values should be made only after thorough testing in a development environment or in consultation with Elluminate, Inc.

We recommend restarting all Elluminate Live! services once you have made all the changes to the configuration.xml file.

This file is located in the root of the ElluminateLive installation directory. The root directory is chosen during installation and may vary between systems. The default locations of the configuration.xml file are as follows:

Windows

C:\Program Files\ElluminateLive\manager\tomcat\webapps\ROOT\WEB-

INF\resources\configuration.xml

Linux & Solaris

/opt/ElluminateLive/manager/tomcat/webapps/ROOT/WEB-

INF/resources/configuration.xml

Mac

/Applications/ElluminateLive/manager/tomcat/webapps/ROOT/WEB-

INF/resources/configuration.xml

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 30

Page 37: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

To modify a parameter, edit the appropriate XML file in place with an XML editor. The Elluminate Live! Manager has to be stopped and then restarted to pick up the changes.

Only the parameters that may be modified are listed and described below. Do not modify any other parameters within the configuration.xml file, unless instructed to by Elluminate, Inc.

AdvancedLDAPDAO The AdvancedLDAPDAO allows advanced customization of the Elluminate Live! Manager with LDAP servers including Active Directory Services. Using this DAO allows customers to authorize Elluminate Live! Manager privileges to a defined group or list from the LDAP source.

The example below demonstrates how a group of users from a Windows Active Directory server can be authenticated to log in to the Elluminate Live! Manager and be granted privileges based on their assigned groups.

1. Run the LDAP service on the Active Directory Service. You need to be familiar with the organizational Distinguished Name (DN) and user attributes.

In the above example, the DN is CN=test user,CN=Users,DC=test,DC=elluminate,DC=com.

2. When installing the Elluminate Live! Manager be sure to choose the Custom option.

a. Enable LDAP but do not choose the option "Exclude users where the Elluminate Role is not defined or invalid."

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 31

Page 38: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

b. When selecting fields to map in the installation, make sure that the Elluminate Role ID field is mapped to the field from the Active Directory store that contains the attributes to map to the Elluminate Live! Manager role values (e.g., memberOf or department). This mapping will be used to determine the role that the user will have in the Elluminate Live! Manager:

3. Finish the installation.

4. Stop the Elluminate Live! Manager service/daemon. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

5. Edit the configuration.xml file with an XML editor.

c. Search for the text CustomLDAPDAO and replace it with AdvancedLDAPDAO.

d. For every group or department in Active Directory that requires a defined Elluminate Role, a paired definition must be made in the configuration.xml file. Insert these after the AdvancedLDAPDAO tag.

The generic format is as follows:

<argument> <name>delimiter</name> <value>\n</value> </argument>

The delimiter must be defined identically to what is stored in the ADS field attribute for the user.

Values can be either 0,1,2 or 3, where:

0 = Server Administrator 1 = Administrator 2 = Moderator 3 = User

Example

<argument> <name>role:CN=TestADSGroup,DC=test,DC=elluminate,DC=com</name> <value>0</value> </argument>

In this case, any user who authenticates to Active Directory and belongs to the TestADSGroup will be granted Server Administrator privileges in Elluminate Live! Manager. In this case 'test user' will be granted server administrator rights.

e. Repeat the above procedure for every distinct user group that will use Elluminate Live! Manager. In the event of duplicate entries, where the group is defined more than once in the configuration.xml file, Elluminate Live! Manager will use the lowest value (highest privilege). For example, if there are two entries for TestADSGroup, one with '0' and one with '3', then the value of 0 will be used.

6. Save the file and restart the Elluminate Live! Manager daemon/service.

32 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 39: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 33

daofactory The following table lists the arguments that may be changed for the database that is being used by the Elluminate Live! Manager. Ensure that all table names are changed at the same time.

Table 9: configuration.xml - daofactory Parameters

Parameter Name Description

<class> com.elluminate.data.dao.adapter.CustomJDBCDAO This is the default JDBC class used by Elluminate Live! Manager for Oracle and MS SQL Server databases – another alternative could be test.dao.jdbc.OracleJDBCDAO.

<name> password <value> admin

This is the password for the database userid that acts on behalf of the Elluminate Live! Manager.

<name> user <value> admin

This is the ID of a user in the database userid that acts on behalf of the Elluminate Live! Manager.

<name> jdbcUrl <value> jdbc:mckoi:local://C:/Program Files/ElluminateLive/manager /tomcat/webapps/ROOT/WEB-INF/resources/db.conf

This is the JDBC URL to connect to the database used by the Elluminate Live! Manager – another alternative could be something like this: jdbc:oracle:thin:@localhost:1521:ORCL

<name> roleId <type> INTEGER <default> 3

This is the default roleId (participant) given to users who log into the Elluminate Live! Manager without a roleId value from their datastore.

<name> name <value> Recordings <name> directory <value> C:\Program Files\ElluminateLive\manager\tomcat \webapps\ROOT\WEB-INF\resources\recordings</value>

This is the location where recordings can be found from the database after they have been imported by the Elluminate Live! Manager. The Elluminate Live! Manager does not back up these recording files.

<name>directory</name> <value>C:\Program Files\ElluminateLive\manager\tomcat \webapps\ROOT\WEB-INF\resources\preloads</value> <name>name</name> <value>Preloads</value>

This is the location where preloaded files for a scheduled Elluminate Live! session can be found. The Elluminate Live! Manager does not back up these preload files.

The following is the default daofactory section:

<daofactory> <manager>com.elluminate.data.dao.adapter.CachedDAOManager</manager> <dao> <class>com.elluminate.data.dao.adapter.ViewDAO</class> <argument> <name>builder</name> <value>com.elluminate.data.dao.viewbuilders.impl .SystemPropertiesViewBuilder</value> </argument> <argument> <name>name</name> <value>SystemProperties</value> </argument>

Page 40: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

<definition> <key>propertyName</key> <column> <name>propertyName</name> <type>STRING</type> <size>64</size> </column> <column> <name>propertyValue</name> <type>STRING</type> <size>255</size> </column> </definition> </dao> <dao> <class>com.elluminate.data.dao.adapter.CustomJDBCDAO</class> <argument> <name>password</name> <value>admin</value> </argument> <argument> <name>jdbcDriver</name> <value>com.mckoi.JDBCDriver</value> </argument> <argument> <name>user</name> <value>admin</value> </argument> <argument> <name>jdbcUrl</name> <value>jdbc:mckoi:local://C:/Program Files/ElluminateLive/manager /tomcat/webapps/ROOT/WEB-INF/resources/db.conf</value> </argument> <argument> <name>name</name> <value>Participants</value> </argument> <definition> <key>meetingId,userId</key> <column> <name>meetingId</name> <type>LONG</type> </column> <column> <name>userId</name> <type>STRING</type> <size>64</size> </column> <column> <name>roleId</name> <type>INTEGER</type> </column> </definition> </dao>

34 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 41: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 35

<dao> <class>com.elluminate.data.dao.adapter.ViewDAO</class> <argument> <name>builder</name> <value>com.elluminate.data.dao.viewbuilders.impl .MeetingsViewBuilder</value> </argument> <argument> <name>name</name> <value>MeetingDetails</value> </argument> <definition> <key>meetingId</key> <column> <name>meetingId</name> <type>LONG</type> </column> <column> <name>meetingName</name> <type>STRING</type> <size>64</size> </column> <column> <name>adapter</name> <type>STRING</type> <size>64</size> </column> <column> <name>startDate</name> <type>LONG</type> </column> <column> <name>costCenter</name> <type>STRING</type> <size>64</size> </column> <column> <name>seats</name> <type>INTEGER</type> </column> <column> <name>privateMeeting</name> <type>STRING</type> <size>16</size> </column> <column> <name>endDate</name> <type>LONG</type> </column> <column> <name>firstName</name> <type>STRING</type> <size>32</size> </column>

Page 42: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

<column> <name>lastName</name> <type>STRING</type> <size>32</size> </column> </definition> </dao> <dao> <class>com.elluminate.data.dao.adapter.CustomJDBCDAO</class> <argument> <name>password</name> <value>admin</value> </argument> <argument> <name>jdbcDriver</name> <value>com.mckoi.JDBCDriver</value> </argument> <argument> <name>user</name> <value>admin</value> </argument> <argument> <name>jdbcUrl</name> <value>jdbc:mckoi:local://C:/Program Files/ElluminateLive/manager /tomcat/webapps/ROOT/WEB-INF/resources/db.conf</value> </argument> <argument> <name>name</name> <value>MeetingPreloads</value> </argument> <definition> <key>meetingId,preloadId</key> <column> <name>meetingId</name> <type>LONG</type> </column> <column> <name>preloadId</name> <type>LONG</type> </column> </definition> </dao> <dao> <class>com.elluminate.data.dao.adapter.CustomJDBCDAO</class> <argument> <name>password</name> <value>admin</value> </argument> <argument> <name>jdbcDriver</name> <value>com.mckoi.JDBCDriver</value> </argument> <argument> <name>user</name> <value>admin</value> </argument>

36 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 43: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 37

<argument> <name>jdbcUrl</name> <value>jdbc:mckoi:local://C:/Program Files/ElluminateLive/manager /tomcat/webapps/ROOT/WEB-INF/resources/db.conf</value> </argument> <argument> <name>name</name> <value>Meetings</value> </argument> <definition> <key>meetingId</key> <column> <name>deleted</name> <type>BOOLEAN</type> </column> <column> <name>password</name> <type>STRING</type> <size>16</size> </column> <column> <name>meetingId</name> <type>LONG</type> </column> <column> <name>creatorId</name> <type>STRING</type> <size>64</size> </column> <column> <name>adapter</name> <type>STRING</type> <size>64</size> </column> <column> <name>startDate</name> <type>LONG</type> </column> <column> <name>privateMeeting</name> <type>BOOLEAN</type> </column> <column> <name>endDate</name> <type>LONG</type> </column> <column> <name>name</name> <type>STRING</type> <size>64</size> </column> </definition> </dao>

Page 44: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

<dao> <class>com.elluminate.data.dao.adapter.ViewDAO</class> <argument> <name>builder</name> <value>com.elluminate.data.dao.viewbuilders.impl .SessionsViewBuilder</value> </argument> <argument> <name>name</name> <value>SessionAttendance</value> </argument> <definition> <key>meetingId,loginName</key> <column> <name>meetingId</name> <type>LONG</type> </column> <column> <name>auditTime</name> <type>LONG</type> </column> <column> <name>loginName</name> <type>STRING</type> <size>32</size> </column> <column> <name>type</name> <type>STRING</type> <size>16</size> </column> <column> <name>roleId</name> <type>INTEGER</type> </column> </definition> </dao> <dao> <class>com.elluminate.data.dao.adapter.ViewDAO</class> <argument> <name>builder</name> <value>com.elluminate.data.dao.viewbuilders.impl .RecordingsViewBuilder</value> </argument> <argument> <name>name</name> <value>RecordingDetails</value> </argument> <definition> <key>recordingId</key> <column> <name>recordingSize</name> <type>LONG</type> </column>

38 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 45: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 39

<column> <name>recordingId</name> <type>STRING</type> <size>128</size> </column> <column> <name>meetingName</name> <type>STRING</type> <size>128</size> </column> <column> <name>costCenter</name> <type>STRING</type> <size>64</size> </column> <column> <name>creationDate</name> <type>LONG</type> </column> <column> <name>firstName</name> <type>STRING</type> <size>32</size> </column> <column> <name>lastName</name> <type>STRING</type> <size>32</size> </column> </definition> </dao> <dao> <class>com.elluminate.data.dao.adapter.CustomJDBCFileDAO</class> <argument> <name>directory</name> <value>C:\Program Files\ElluminateLive\manager\tomcat \webapps\ROOT\WEB-INF\resources\recordings</value> </argument> <argument> <name>password</name> <value>admin</value> </argument> <argument> <name>jdbcDriver</name> <value>com.mckoi.JDBCDriver</value> </argument> <argument> <name>user</name> <value>admin</value> </argument> <argument> <name>dao</name> <value>com.elluminate.data.dao.adapter.CustomJDBCDAO</value> </argument>

Page 46: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

<argument> <name>jdbcUrl</name> <value>jdbc:mckoi:local://C:/Program Files/ElluminateLive/manager /tomcat/webapps/ROOT/WEB-INF/resources/db.conf</value> </argument> <argument> <name>name</name> <value>Recordings</value> </argument> <definition> <key>recordingId</key> <column> <name>creationTime</name> <type>STRING</type> <size>4</size> </column> <column> <name>meetingId</name> <type>LONG</type> </column> <column> <name>recordingSize</name> <type>LONG</type> </column> <column> <name>recordingId</name> <type>STRING</type> <size>128</size> </column> <column> <name>meetingName</name> <type>STRING</type> <size>128</size> </column> <column> <name>recordingData</name> <type>BINARY</type> <default>[B@12088db</default> </column> <column> <name>openFlag</name> <type>BOOLEAN</type> </column> <column> <name>creationDate</name> <type>LONG</type> </column> <column> <name>version</name> <type>STRING</type> <size>16</size> </column> </definition> </dao>

40 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 47: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 41

<dao> <class>com.elluminate.data.dao.adapter.CustomJDBCDAO</class> <argument> <name>password</name> <value>admin</value> </argument> <argument> <name>jdbcDriver</name> <value>com.mckoi.JDBCDriver</value> </argument> <argument> <name>user</name> <value>admin</value> </argument> <argument> <name>jdbcUrl</name> <value>jdbc:mckoi:local://C:/Program Files/ElluminateLive/manager /tomcat/webapps/ROOT/WEB-INF/resources/db.conf</value> </argument> <argument> <name>name</name> <value>AuditLogAttributes</value> </argument> <definition> <key>auditTime,attributeName</key> <column> <name>attributeName</name> <type>STRING</type> <size>32</size> </column> <column> <name>auditTime</name> <type>LONG</type> </column> <column> <name>attributeValue</name> <type>STRING</type> <size>128</size> </column> </definition> </dao> <dao> <class>com.elluminate.data.dao.adapter.ViewDAO</class> <argument> <name>builder</name> <value>com.elluminate.data.dao.viewbuilders.impl .ActiveMeetingsViewBuilder</value> </argument> <argument> <name>name</name> <value>ActiveMeetingDetails</value> </argument> <definition> <key>meetingId</key> <column> <name>meetingId</name>

Page 48: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

<type>LONG</type> </column> <column> <name>meetingName</name> <type>STRING</type> <size>64</size> </column> <column> <name>adapter</name> <type>STRING</type> <size>64</size> </column> <column> <name>startDate</name> <type>LONG</type> </column> <column> <name>costCenter</name> <type>STRING</type> <size>64</size> </column> <column> <name>seats</name> <type>INTEGER</type> </column> <column> <name>privateMeeting</name> <type>STRING</type> <size>16</size> </column> <column> <name>endDate</name> <type>LONG</type> </column> <column> <name>firstName</name> <type>STRING</type> <size>32</size> </column> <column> <name>lastName</name> <type>STRING</type> <size>32</size> </column> </definition> </dao> <dao> <class>com.elluminate.data.dao.adapter.CustomJDBCDAO</class> <argument> <name>password</name> <value>admin</value> </argument> <argument> <name>jdbcDriver</name> <value>com.mckoi.JDBCDriver</value> </argument>

42 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 49: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 43

<argument> <name>user</name> <value>admin</value> </argument> <argument> <name>jdbcUrl</name> <value>jdbc:mckoi:local://C:/Program Files/ElluminateLive/manager /tomcat/webapps/ROOT/WEB-INF/resources/db.conf</value> </argument> <argument> <name>name</name> <value>Reports</value> </argument> <definition> <key>reportId</key> <column> <name>reportName</name> <type>STRING</type> <size>64</size> </column> <column> <name>parentId</name> <type>LONG</type> <default>-1</default> </column> <column> <name>reportXML</name> <type>BINARY</type> <default>[B@f90137</default> </column> <column> <name>ownerId</name> <type>STRING</type> <size>64</size> </column> <column> <name>reportId</name> <type>LONG</type> </column> <column> <name>roleId</name> <type>INTEGER</type> </column> <column> <name>reportDescription</name> <type>STRING</type> <size>255</size> </column> </definition> </dao> <dao> <class>com.elluminate.data.dao.adapter.CustomJDBCFileDAO</class> <argument> <name>directory</name> <value>C:\Program Files\ElluminateLive\manager\tomcat \webapps\ROOT\WEB-INF\resources\preloads</value>

Page 50: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

</argument> <argument> <name>password</name> <value>admin</value> </argument> <argument> <name>jdbcDriver</name> <value>com.mckoi.JDBCDriver</value> </argument> <argument> <name>user</name> <value>admin</value> </argument> <argument> <name>dao</name> <value>com.elluminate.data.dao.adapter.CustomJDBCDAO</value> </argument> <argument> <name>jdbcUrl</name> <value>jdbc:mckoi:local://C:/Program Files/ElluminateLive/manager /tomcat/webapps/ROOT/WEB-INF/resources/db.conf</value> </argument> <argument> <name>name</name> <value>Preloads</value> </argument> <definition> <key>preloadId</key> <column> <name>fileType</name> <type>STRING</type> <size>16</size> </column> <column> <name>mimeType</name> <type>STRING</type> <size>64</size> </column> <column> <name>preloadId</name> <type>LONG</type> </column> <column> <name>preloadData</name> <type>BINARY</type> <default>[B@1bed3d1</default> </column> <column> <name>preloadName</name> <type>STRING</type> <size>128</size> </column> <column> <name>preloadSize</name> <type>LONG</type> </column>

44 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 51: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 45

<column> <name>ownerId</name> <type>STRING</type> <size>64</size> </column> </definition> </dao> <dao> <class>com.elluminate.data.dao.adapter.CustomJDBCDAO</class> <argument> <name>password</name> <value>admin</value> </argument> <argument> <name>jdbcDriver</name> <value>com.mckoi.JDBCDriver</value> </argument> <argument> <name>user</name> <value>admin</value> </argument> <argument> <name>jdbcUrl</name> <value>jdbc:mckoi:local://C:/Program Files/ElluminateLive/manager /tomcat/webapps/ROOT/WEB-INF/resources/db.conf</value> </argument> <argument> <name>name</name> <value>MeetingParameters</value> </argument> <definition> <key>meetingId</key> <column> <name>meetingId</name> <type>LONG</type> </column> <column> <name>costCenter</name> <type>STRING</type> <size>64</size> </column> <column> <name>raiseHandOnEnter</name> <type>BOOLEAN</type> </column> <column> <name>moderatorNotes</name> <type>STRING</type> <size>1024</size> </column> <column> <name>maxTalkers</name> <type>INTEGER</type> <default>1</default> </column>

Page 52: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

<column> <name>userNotes</name> <type>STRING</type> <size>1024</size> </column> <column> <name>recordingStatus</name> <type>STRING</type> <size>16</size> </column> </definition> </dao> <dao> <class>com.elluminate.data.dao.adapter.CustomJDBCDAO</class> <argument> <name>password</name> <value>admin</value> </argument> <argument> <name>jdbcDriver</name> <value>com.mckoi.JDBCDriver</value> </argument> <argument> <name>user</name> <value>admin</value> </argument> <argument> <name>jdbcUrl</name> <value>jdbc:mckoi:local://C:/Program Files/ElluminateLive/manager /tomcat/webapps/ROOT/WEB-INF/resources/db.conf</value> </argument> <argument> <name>name</name> <value>Groups</value> </argument> <definition> <key>groupId</key> <column> <name>groupId</name> <type>LONG</type> </column> <column> <name>groupName</name> <type>STRING</type> <size>64</size> </column> </definition> </dao> <dao> <class>com.elluminate.data.dao.adapter.CustomJDBCDAO</class> <argument> <name>password</name> <value>admin</value> </argument>

46 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 53: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 47

<argument> <name>jdbcDriver</name> <value>com.mckoi.JDBCDriver</value> </argument> <argument> <name>user</name> <value>admin</value> </argument> <argument> <name>jdbcUrl</name> <value>jdbc:mckoi:local://C:/Program Files/ElluminateLive/manager /tomcat/webapps/ROOT/WEB-INF/resources/db.conf</value> </argument> <argument> <name>name</name> <value>GroupMembers</value> </argument> <definition> <key>groupId,memberId</key> <column> <name>groupId</name> <type>LONG</type> </column> <column> <name>memberId</name> <type>STRING</type> <size>64</size> </column> </definition> </dao> <dao> <class>com.elluminate.data.dao.adapter.ViewDAO</class> <argument> <name>builder</name> <value>com.elluminate.data.dao.viewbuilders.impl .ActiveSessionsViewBuilder</value> </argument> <argument> <name>name</name> <value>CurrentAttendance</value> </argument> <definition> <key>meetingId,loginName</key> <column> <name>meetingId</name> <type>LONG</type> </column> <column> <name>loginName</name> <type>STRING</type> <size>32</size> </column> <column> <name>joinedAt</name> <type>LONG</type> </column>

Page 54: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

<column> <name>leftAt</name> <type>LONG</type> </column> </definition> </dao> <dao> <class>com.elluminate.data.dao.adapter.CustomJDBCDAO</class> <argument> <name>password</name> <value>admin</value> </argument> <argument> <name>jdbcDriver</name> <value>com.mckoi.JDBCDriver</value> </argument> <argument> <name>user</name> <value>admin</value> </argument> <argument> <name>jdbcUrl</name> <value>jdbc:mckoi:local://C:/Program Files/ElluminateLive/manager /tomcat/webapps/ROOT/WEB-INF/resources/db.conf</value> </argument> <argument> <name>name</name> <value>ServerParameters</value> </argument> <definition> <key>meetingId</key> <column> <name>meetingId</name> <type>LONG</type> </column> <column> <name>seats</name> <type>INTEGER</type> </column> <column> <name>boundary</name> <type>INTEGER</type> <default>30</default> </column> <column> <name>permissionsOn</name> <type>BOOLEAN</type> </column> <column> <name>supervised</name> <type>BOOLEAN</type> </column> </definition> </dao>

48 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 55: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 49

<dao> <class>com.elluminate.data.dao.adapter.CustomJDBCDAO</class> <argument> <name>password</name> <value>admin</value> </argument> <argument> <name>jdbcDriver</name> <value>com.mckoi.JDBCDriver</value> </argument> <argument> <name>user</name> <value>admin</value> </argument> <argument> <name>jdbcUrl</name> <value>jdbc:mckoi:local://C:/Program Files/ElluminateLive/manager /tomcat/webapps/ROOT/WEB-INF/resources/db.conf</value> </argument> <argument> <name>name</name> <value>RecordingJournal</value> </argument> <definition> <key>createdOn,meetingId</key> <column> <name>meetingId</name> <type>LONG</type> </column> <column> <name>path</name> <type>STRING</type> <size>255</size> </column> <column> <name>createdOn</name> <type>LONG</type> </column> <column> <name>version</name> <type>STRING</type> <size>16</size> </column> </definition> </dao> <dao> <class>com.elluminate.data.dao.adapter.ViewDAO</class> <argument> <name>builder</name> <value>com.elluminate.data.dao.viewbuilders.impl .RecordingSessionsViewBuilder</value> </argument> <argument> <name>name</name> <value>RecordingSessions</value> </argument>

Page 56: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

<definition> <key>auditTime</key> <column> <name>creator</name> <type>STRING</type> <size>32</size> </column> <column> <name>meetingName</name> <type>STRING</type> <size>64</size> </column> <column> <name>recordingName</name> <type>STRING</type> <size>64</size> </column> <column> <name>auditTime</name> <type>LONG</type> </column> <column> <name>attributeValue</name> <type>STRING</type> <size>128</size> </column> <column> <name>creationDate</name> <type>LONG</type> </column> </definition> </dao> <dao> <class>com.elluminate.data.dao.adapter.CustomJDBCDAO</class> <argument> <name>password</name> <value>admin</value> </argument> <argument> <name>jdbcDriver</name> <value>com.mckoi.JDBCDriver</value> </argument> <argument> <name>user</name> <value>admin</value> </argument> <argument> <name>jdbcUrl</name> <value>jdbc:mckoi:local://C:/Program Files/ElluminateLive/manager /tomcat/webapps/ROOT/WEB-INF/resources/db.conf</value> </argument> <argument> <name>name</name> <value>AuditLog</value> </argument>

50 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 57: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 51

<definition> <key>auditTime</key> <column> <name>auditTime</name> <type>LONG</type> </column> <column> <name>type</name> <type>STRING</type> <size>16</size> </column> <column> <name>message</name> <type>STRING</type> <size>1024</size> </column> </definition> </dao> <dao> <class>com.elluminate.data.dao.adapter.CustomJDBCDAO</class> <argument> <name>password</name> <value>admin</value> </argument> <argument> <name>jdbcDriver</name> <value>com.mckoi.JDBCDriver</value> </argument> <argument> <name>user</name> <value>admin</value> </argument> <argument> <name>jdbcUrl</name> <value>jdbc:mckoi:local://C:/Program Files/ElluminateLive/manager /tomcat/webapps/ROOT/WEB-INF/resources/db.conf</value> </argument> <argument> <name>name</name> <value>Users</value> </argument> <definition> <key>userId</key> <column> <name>deleted</name> <type>BOOLEAN</type> </column> <column> <name>loginPassword</name> <type>STRING</type> <size>128</size> </column> <column> <name>userId</name> <type>STRING</type> <size>64</size>

Page 58: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

</column> <column> <name>loginName</name> <type>STRING</type> <size>32</size> </column> <column> <name>email</name> <type>STRING</type> <size>128</size> </column> <column> <name>roleId</name> <type>INTEGER</type> <default>3</default> </column> <column> <name>firstName</name> <type>STRING</type> <size>32</size> </column> <column> <name>lastName</name> <type>STRING</type> <size>32</size> </column> </definition> </dao> </daofactory>

jdbcdriver We recommend modifying only the <port> parameter in the <jdbcdriver> section. Do not modify any other parameters within the <jdbcdriver> section, unless instructed to by Elluminate, Inc.

The <port> parameter indicates the port on which the Elluminate Live! Manger will accept reporting requests.

<jdbcdriver> <port>5555</port> <password>elluminate</password> <secure>Meetings.password</secure> <secure>Users.loginPassword</secure> </jdbcdriver>

52 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 59: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 53

configuration The parameters listed in the <configuration> section pertain to the Elluminate Live! Manager configuration and were set during the installation of the Elluminate Live! software.

The following table describes the parameters found in the <configuration> section.

Table 10: configuration.xml - configuration Parameters

Parameter Description

administratorLabel The name displayed for the Application Administrator role in Elluminate Live! Manager. The default value is Application Administrator. A System Administrator in Elluminate Live! Manager may modify this parameter in the labelPrefs.html page (Preferences > Labels).

applicationName The name of the application, which is Elluminate Live! Manager.

applicationNameHTML Do not modify

boundaryTime Specifies the number of minutes prior to the scheduled start time of the session/meeting that a user can launch into the session. The possible values are 0, 15, 30, 45, and 60. The default value is 15. A System Administrator in Elluminate Live! Manager may modify this parameter in the generalPrefs.html page (Preferences > General).

calendarProtocol Specifies which calendar protocol your SMTP server will use when sending out email invitations. The options are vCal or iCal. Selecting iCal allows calendar events to be imported by applications on the Mac; however iCal files cannot be imported into MS Outlook. The default and recommended value is vcal.

cleanupDelay Specifies how often (in hours) a check is performed to clean up the preload files (whiteboard and multimedia) on the server. The preload files can be removed from the server when the session has shut down. The default value is 24.

dateFormat The dateFormat parameter specifies the date format displayed in the email message. The default value is MM/dd/yyyy. A System Administrator in Elluminate Live! Manager may modify this parameter in the labelPrefs.html page (Preferences > Labels). Refer to the Date and Time Patterns section in this chapter for a complete list of patterns.

date-format The date-format parameter is used internally and should not be modified.

Page 60: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

Parameter Description

dateTimeFormat Specifies the date and time format that is displayed in the various Elluminate Live! Manager web pages. The date and time is displayed in the

Header for the Meetings, Recordings, Users, and Lists web pages Public and logged-in Meetings page, as the start and end time format of the

session/meetings in the list Public and logged-in Recordings page, as the Date Recorded times of the

recordings in the list Meeting Confirmation page – start date and time, and the end date and time Meeting Login/JNLP Generation page – start date and time, and the end

date and time The default value is MM/dd/yyyy HH:mm z A System Administrator in Elluminate Live! Manager may modify this parameter in the labelPrefs.html page (Preferences > Labels). Refer to the Date and Time Patterns section in this chapter for a complete list of patterns.

defaultFromEmailAddress Email address from which the auto registration email address is set. Default is [email protected].

defaultPassword Default password for a user account created through auto registration, if none provided. Default value is “elluminate”.

defaultReplyToEmailAddress Email address to which an email reply is sent when you hit reply on an auto registration email. Default is [email protected].

defaultRole The default role to assign to users that are created by the auto registration capability. Default is 3 (Participant).

defaultSubject The default subject line in an email invitation. Default is "You're invited to an Elluminate Live! Session".

elmAddress This is the defined IP address and port of the Elluminate Live! Manager within the Local Area Network. Changing this parameter will require a restart of all three services: Elluminate Live! Manager, Elluminate Live! Server and Elluminate Live! License Manager.

encryptionTag This tag is reserved for future expansion of the encryption methodology. The default value should not be changed. The default value is simple.

facilitatorLabel The name displayed for the Facilitator role in Elluminate Live! Manager. The default value is Moderator. A System Administrator in Elluminate Live! Manager may modify this parameter in the labelPrefs.html page (Preferences > Labels).

fullPermissions Indicates whether a user will have the basic privileges or no privileges when they initially join a session/meeting. The possible values are true (user has privileges) or false (no privileges). The default value is true.

54 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 61: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 55

Parameter Description

grace Specifies the number of minutes that an automatically launched session will stay open after the final participant leaves the session. The values are 1, 5, 10, 30, 45, or 60. The default value is 5 minutes. A System Administrator in Elluminate Live! Manager may modify this parameter in the generalPrefs.html page (Preferences > General).

helpUrl The URL that a user’s web browser is redirected to when they click the Help tab in the Elluminate Live! Manager. A System Administrator in Elluminate Live! Manager may modify this parameter in the generalPrefs.html page (Preferences > General).

importDelay Specifies how long (in seconds) after a session has shut down that the recording can be imported. The minimum value is 10 seconds. The default value is 30 seconds.

jinxProtocol Specifies the protocols that are accepted for Elluminate Live! Server connections. The possible values are jinx, jinxssl and ssljinx. The default value is jinx.

kernelVersion The build level of the installed kernel of the Elluminate Live! Manager.

kernelVersion Do not modify

loginType Block: user has no auto registration capabilities. Register: user has to register with the system but a password is automatically created for them. Define: user has to register with the system and provide a password. Default is Block.

maximumReservableSeats The maximum number of seats that can be reserved in any given session. Default is 0.

maxSearchSize The maximum number of entries that may be returned on search requests in Elluminate Live! Manager. The default value is 500 users.

maxTalkers The maximum number of simultaneous talkers allowed in a session. The default value is 1. Session Moderators may modify this value during a session.

meetingDurationCheck The number of minutes that a meeting has to be less than or equal to for it to check seat reservations. 0 disables, meaning every meeting will be checked for reservations. Default is 1440 minutes (24 hours).

minFilterLength The minimum number of characters that need to be entered in the search field before a search can be performed during creation or modification of a session or list. Default is 2.

pageSize The number of list entries displayed at a single time on an Elluminate Live! Manager web page. The default value is 10.

passwordEmailSubject The subject in the email containing the password for the loginType Register. Default is “Elluminate Live! Registration Confirmation”.

Page 62: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

Parameter Description

passwordEmailTemplate Relative link pointing to the template to be used for the password email for a loginType of Register. Default is WEB-INF/resources/templates/email/temp_password_template.txt.

passwordRequired Allows you to define whether all future sessions/meetings require a password to join or not. If set to true, all sessions/meetings will require a password for creation and to be joined; if set to false the sessions/meetings do not require a password. The default setting is false. A System Administrator in Elluminate Live! Manager may modify this parameter in the generalPrefs.html page (Preferences > General). The option to be modified is called "Meetings Require a Room Password."

passwordStrategy Specify the strategy to use when authenticating a user. Possible values are the following:

test.password.DefaultPasswordStrategy test.password.LDAPPasswordStrategy

The DefaultPasswordStrategy will use the passwordTranslation parameter to determine the type of encryption to use to validate the password. The LDAPPasswordStrategy will cause a bind to be made to the LDAP server to authenticate the password. The value defined by the passwordTranslator is ignored. The default value is DefaultPasswordStrategy.

passwordTranslator Specifies the password encryption method that the Elluminate Live! Manager will support for user passwords. The passwords may be retrieved from an LDAP server or stored in the defined Elluminate Live! Manager datastore. Possible values are the following:

PlainPasswordTranslator LDAPDESPasswordTranslator LDAPMD5PasswordTranslator

The default value is PlainPasswordTranslator.

publicPageAvailable Do not modify

recordingDirectory This is the directory location from where Elluminate Live! Manager will import recordings into the database. This value is superseded by the value defined in the elive.conf file.

recordingJNLPExpiryTime Number of minutes before a recording JNLP expires. Valid only if secureRecordingJNLP is set to True. Default is 0.

recordingJNLPIPCheck If set to True, the recordings will be tied to the computer that generated the JNLP. If set to False, the recording will not be tied to the computer that generated the JNLP. Default is False.

recordingJNLPSecret The private portion of the MD5 hash check. Default is "2782-1dashljkgq8dbhc".

56 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 63: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 57

Parameter Description

recordingStatus Specifies the recording default setting for all sessions/meetings. There are three values: on, off, or remote. on – specifies that the sessions/meetings will be automatically recorded. The Moderator cannot control the recording. off – specifies that the session cannot be recorded. remote – specifies that the Moderator can turn the recording on or off during the session. The default value is remote.

reservedSeatCount Specifies how many seats will be automatically reserved for every session/meeting that is created. The default value is 0.

resourceLoaderPath The folder where all of the Elluminate Live! Manager resources can be located.

seatMethod Allows you to turn the seat reservation feature on or off. There are two values that can be used: Preferred – enables the feature. When a session/meeting is created, the value in the seat reservation parameter will be checked to determine if there are enough seats available at the scheduled session/meeting start time. If there are not enough seats available, the session/meeting will not be created. none – disables the feature. No seat availability check is performed when the session/meeting is created. The default value is preferred. A System Administrator in Elluminate Live! Manager may modify this parameter in the generalPrefs.html page (Preferences > General).

secureRecordingJNLP If set to True, recording JNLPs will be secured. If set to False, recording JNLPs will not be secure. Default is False.

serverRestartGracePeriod The number of seconds before any sessions can begin running after the Elluminate Live! Manager has been restarted. This period is used to synchronize the sessions/meetings currently running on any Elluminate Live! Servers with the Elluminate Live! Manager database. This ensures that any new participants joining a currently running session/meeting will be placed on the correct server. The default value is 10 seconds.

supervisedMeeting Allows you to specify the ability of Moderators to see private messages and specify the permission status of the Participants immediately after the last Moderator leaves the session/meeting. If supervisedMeeting is set to true, Moderators will see all private messages and Participants will lose session/meeting permissions when the last Moderator leaves the session/meeting. If supervisedMeeting is set to false, Moderators do not see the private messages and the Participants' permissions are unchanged when the last Moderator leaves the session/meeting. The default setting is true.

systemAdministratorLabel The name displayed for the System Administrator role in Elluminate Live! Manager. The default value is System Administrator. A System Administrator in Elluminate Live! Manager may modify this parameter in the labelPrefs.html page (Preferences > Labels).

Page 64: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

Parameter Description

timeFormat Specifies the time format displayed in the email message.

The default value is HH:mm z Refer to Date and Time Patterns section in this chapter for a complete list of patterns. A System Administrator in Elluminate Live! Manager may modify this parameter in the labelPrefs.html page (Preferences > Labels).

timeZone The time zone in which to display all date and time values. This should be modified only from within the Elluminate Live! Manager application. A System Administrator in Elluminate Live! Manager may modify this parameter in the generalPrefs.html page (Preferences > General).

userLabel The name displayed for the User role in Elluminate Live! Manager. The default value is Participant. A System Administrator in Elluminate Live! Manager may modify this parameter in the labelPrefs.html page (Preferences > Labels).

version The version of the Elluminate Live! Manager user interface.

webguiConfigurationFile The location of the configuration file used by the Elluminate Live! Manager front-end.

webProtocol Specifies the protocols that are accepted for Elluminate Live! Server connections. The possible values are http and https. The default value is http.

The following is the default configuration section:

<configuration> <property> <name>grace</name> <value>1</value> </property> <property> <name>encryptionTag</name> <value>simple</value> </property> <property> <name>recordingJNLPExpiryTime</name> <value>60</value> </property> <property> <name>timeZone</name> <value>America/Denver</value> </property> <property> <name>systemAdministratorLabel</name> <value>System Administrator</value> </property> <property> <name>applicationName</name> <value>Elluminate Live! Manager</value> </property>

58 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 65: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 59

<property> <name>resourceLoaderPath</name> <value>C:/Program Files/ElluminateLive/manager/tomcat/webapps/ ROOT</value> </property> <property> <name>defaultFromEmailAddress</name> <value>[email protected]</value> </property> <property> <name>passwordRequired</name> <value>false</value> </property> <property> <name>passwordEmailSubject</name> <value>Login Name and Password</value> </property> <property> <property> <name>seatMethod</name> <value>preferred</value> </property> <property> <name>recordingJNLPIPCheck</name> <value>true</value> </property> <property> <name>reservedSeatCount</name> <value>0</value> </property> <property> <name>elmAddress</name> <value>192.168.1.126:8080</value> </property> <property> <name>kernelVersion</name> <value>2.7.0.766</value> </property> <property> <name>facilitatorLabel</name> <value>Moderator</value> </property> <property> <name>maximumReservableSeats</name> <value>0</value> </property> <property> <name>passwordStrategy</name> <value>test.password.DefaultPasswordStrategy</value> </property> <property> <name>recordingJNLPSecret</name> <value>89fc83865acf7ea17025d9597203192e/</value> </property>

Page 66: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

<property> <name>importDelay</name> <value>30</value> </property> <property> <name>supervisedMeeting</name> <value>true</value> </property> <property> <name>defaultRole</name> <value>3</value> </property> <property> <name>dateFormat</name> <value>MM/dd/yyyy</value> </property> <property> <name>administratorLabel</name> <value>Application Administrator</value> </property> <property> <name>defaultSubject</name> <value>Elluminate Live! Session Invitation</value> </property> <property> <name>userLabel</name> <value>Participant</value> </property> <property> <property> <name>calendarProtocol</name> <value>vcal</value> </property> <property> <name>webProtocol</name> <value>http</value> </property> <property> <name>dateTimeFormat</name> <value>MM/dd/yyyy HH:mm z</value> </property> <property> <name>pageSize</name> <value>10</value> </property> <property> <name>serverRestartGracePeriod</name> <value>10</value> </property> <property> <name>secureRecordingJNLP</name> <value>true</value> </property>

60 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 67: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 61

<property> <name>recordingDirectory</name> <value>C:/Program Files/ElluminateLive/common/recordings</value> </property> <property> <name>passwordEmailTemplate</name> <value>C:\Program Files\ElluminateLive\manager\tomcat\webapps\ROOT\WEB-INF\resources\templates\email\temp_password_template.txt</value> </property> <property> <name>webguiConfigurationFile</name> <value>C:/Program Files/ElluminateLive/manager/tomcat/webapps/ ROOT/WEB-INF/resources/webgui.xml</value> </property> <property> <name>publicPageAvailable</name> <value>true</value> </property> <property> <name>defaultReplyToEmailAddress</name> <value>[email protected]</value> </property> <property> <property> <name>helpUrl</name> <value>http://192.168.1.126:8080/help/help.help</value> </property> <property> <name>applicationNameHTML</name> <value>Elluminate &lt;i&gt;Live!&lt;/i&gt; Manager</value> </property> <property> <name>defaultPassword</name> <value>elluminate</value> </property> <property> <name>timeFormat</name> <value>HH:mm z</value> </property> <property> <name>meetingDurationCheck</name> <value>24</value> </property> <property> <name>passwordTranslator</name> <value>test.encryption.translators.PlainPasswordTranslator</value> </property> <property> <name>jinxProtocol</name> <value>jinx</value> </property> <property> <name>date-format</name> <value>MM/dd/yyyy</value> </property>

Page 68: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

<property> <name>recordingStatus</name> <value>remote</value> </property> <property> <name>maxTalkers</name> <value>1</value> </property> <property> <name>maxSearchSize</name> <value>500</value> </property> <property> <name>version</name> <value>2.5.0.x</value> </property> <property> <name>boundaryTime</name> <value>15</value> </property> <property> <name>loginType</name> <value>block</value> </property> <property> <name>cleanupDelay</name> <value>24</value> </property> <property> <name>fullPermissions</name> <value>true</value> </property>

<property> <name>minFilterLength</name> <value>2</value> </property>

</configuration>

backup We recommend modifying only the <values> configured for the backupFolder and interval parameters in the <backup> section. Do not modify any other parameters within the <backup> section, unless instructed to by Elluminate, Inc.

The backupFolder <value> indicates the location to which the backup files will be written.

The interval <value> is the number of hours between each full backup.

<backup> <strategy> <class>com.elluminate.backup.impl.StreamingBinaryExclusionBackupStrategy </class> <argument> <name>backupFolder</name> <value>C:\Program Files\ElluminateLive\common\backup\ROOT</value> </argument>

62 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 69: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 63

<argument> <name>excludeBinary</name> <value>Recordings,Preloads</value> </argument> </strategy> <trigger> <class>com.elluminate.backup.impl.CalendarBackupTrigger</class> <argument> <name>interval</name> <value>MON 02:00,TUE 02:00,WED 02:00,THU 02:00,FRI 02:00,SAT 02:00, SUN 02:00</value> </argument> </trigger> </backup>

adapters No parameters in this section should be modified unless instructed to by Elluminate, Inc.

encryption No parameters in this section should be modified unless instructed to by Elluminate, Inc.

scheduler We recommend modifying only the timeOut and poolSize <values> in the <scheduler> section. Do not modify any other parameters within the <scheduler> section, unless instructed to by Elluminate, Inc.

The timeOut <value> indicates the number of milliseconds that a job thread can run without timing out. (Default is 60 seconds.)

The poolSize <value> indicates the number of concurrent job threads that can be run in the Elluminate Live! Manager.

<scheduler> <class> com.elluminate.kernel.impl.AsynchronousScheduler</class> <argument> <name>timeOut</name> <value>60000</value> </argument> <argument> <name>poolSize</name> <value>10</value> </argument> </scheduler>

Page 70: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

jnlpfactory We recommend modifying only the <meeting> and <recording> parameters in the <jnlpfactory> section. Do not modify any other parameters within the <jnlpfactory> section, unless instructed to by Elluminate, Inc.

The <meeting> parameter indicates the jnlp file that is used for a user to join an Elluminate Live! 8.0 meeting (session).

The <recording> parameter indicates the jnlp file that is used for a user to play back an Elluminate Live! 8.0 recording.

<jnlpfactory> <jnlp> <version>8.0</version> <meeting>C:\Program Files\ElluminateLive\manager\tomcat\webapps\ROOT\ WEB-INF\resources\templates\jnlp\join_template.jnlp.v8</meeting> <recording>C:\Program Files\ElluminateLive\manager\tomcat\webapps\ ROOT\WEB-INF\resources\templates\jnlp\ play_recording.jnlp.v8</recording> </jnlp> <jnlp> <version>7.2</version> <meeting>C:\Program Files\ElluminateLive\manager\tomcat\webapps\ROOT\ WEB-INF\resources\templates\jnlp\join_template.jnlp.v7</meeting> <recording>C:\Program Files\ElluminateLive\manager\tomcat\webapps\ ROOT\WEB-INF\resources\templates\jnlp\ play_recording.jnlp.v7</recording> </jnlp> <jnlp> <version>7.0</version> <meeting>C:\Program Files\ElluminateLive\manager\tomcat\webapps\ROOT\ WEB-INF\resources\templates\jnlp\join_template.jnlp.v7</meeting> <recording>C:\Program Files\ElluminateLive\manager\tomcat\webapps\ ROOT\WEB-INF\resources\templates\jnlp\ play_recording.jnlp.v7</recording> </jnlp> <jnlp> <version>6.5</version> <meeting>C:\Program Files\ElluminateLive\manager\tomcat\webapps\ROOT\ WEB-INF\resources\templates\jnlp\join_template.jnlp.v65</meeting> <recording>C:\Program Files\ElluminateLive\manager\tomcat\webapps\ ROOT\WEB-INF\resources\templates\jnlp\ play_recording.jnlp.v65</recording> </jnlp> <jnlp> <version>6.0</version> <meeting>C:\Program Files\ElluminateLive\manager\tomcat\webapps\ROOT\ WEB-INF\resources\templates\jnlp\join_template.jnlp.v6</meeting> <recording>C:\Program Files\ElluminateLive\manager\tomcat\webapps\ ROOT\WEB-INF\resources\templates\jnlp\ play_recording.jnlp.v6</recording> </jnlp>

64 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 71: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 65

<jnlp> <version>5.0</version> <meeting>C:\Program Files\ElluminateLive\manager\tomcat\webapps\ROOT\ WEB-INF\resources\templates\jnlp\join_template.jnlp.v5</meeting> <recording>C:\Program Files\ElluminateLive\manager\tomcat\webapps\ ROOT\WEB-INF\resources\templates\jnlp\ play_recording.jnlp.v5</recording> </jnlp> </jnlpfactory>

serverinterface We recommend modifying only the licenseManagerFile, licenseManagerPort, and licenseManagerAddress values in the <serverinterface> section. Do not modify any other parameters within the <serverinterface> section, unless instructed by Elluminate, Inc.

The licenseManagerFile indicates the path to the license file being used by Elluminate Live! Manager.

The licenseManagerPort is the port on which the License Manager is listening.

The licenseManagerAddress is the IP Address where the License Manager is running.

<serverinterface> <class> com.elluminate.server.impl .LicenseManagerServerInterfaceAdapter</class> <argument> <name>licenseManagerFile</name> <value>C:\Program Files\ElluminateLive\common\licenses\ QA-Academic500.lm</value> </argument> <argument> <name>licenseManagerPort</name> <value>2186</value> </argument> <argument> <name>licenseManagerAddress</name> <value>192.168.1.126</value> </argument> </serverinterface>

securitymanager No parameters in this section should be modified unless instructed to by Elluminate, Inc.

servertemplatefactory We recommend modifying only the <template> parameter in the <servertemplatefactory> section. Do not modify any other parameters within the <servertemplatefactory> section, unless instructed to by Elluminate, Inc.

Page 72: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

The <template> parameter specifies the path to the template that is used for Elluminate Live! Manager meetings (sessions).

<servertemplatefactory> <servertemplate> <version>8.0</version> <template>C:\Program Files\ElluminateLive\manager\tomcat\webapps\ ROOT\WEB-INF\resources\templates\server\ default.tmpl</template>

codebasemanager We recommend modifying only the <url> parameter in the <codebasemanager> section. Do not modify any other parameters within the <codebasemanager> section, unless instructed to by Elluminate, Inc. The URLs defined here are superseded by the values defined in the elive.conf file of the server that the session/meeting is scheduled against.

The <url> parameter is the URL where Elluminate Live! clients can download the client jar files to join an Elluminate Live! 8.0 session (meeting).

<codebasemanager> <codebase> <version>5.0</version> <url>http://192.168.1.126:8080/lib/5.0</url> </codebase> <codebase> <version>6.0</version> <url>http://192.168.1.126:8080/lib/6.0</url> </codebase> <codebase> <version>6.5</version> <url>http://192.168.1.126:8080/lib/6.5</url> </codebase> <codebase> <version>7.0</version> <url>http://192.168.1.126:8080/lib/7.0</url> </codebase> <codebase> <version>7.2</version> <url>http://192.168.1.126:8080/lib/7.0</url> </codebase> <codebase> <version>8.0</version> <url>http://192.168.1.126:8080/lib/8.0</url> </codebase> </codebasemanager>

mailmanager We recommend modifying only the host and port <values> in the <mailmanager> section. Do not modify any other parameters within the <mailmanager> section, unless instructed to by Elluminate, Inc.

The host <value> indicates the address of the SMTP mail server that Elluminate Live! Manager will use to send out email invitations.

66 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 73: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 67

The port <value> indicates the port on which the SMTP is listening.

<mailmanager> <argument> <name>protocol</name> <value>smtp</value> </argument> <argument> <name>host</name> <value>smtp.company.com</value> </argument> <argument> <name>port</name> <value>25</value> </argument> </mailmanager>

proxymanager The Elluminate Live! Manager provides an authentication and authorization subsystem for WebService calls. This subsystem is defined in the <proxymanager> element of the configuration.xml file.

For information on changing <proxymanager> properties, see the WebService Security section of the Elluminate Live! SDK (available from your Elluminate sales representative) or contact Elluminate Customer Support.

Date and Time Patterns Date and time formats are specified by date and time pattern strings. Within date and time pattern strings, unquoted letters from 'A' to 'Z' and from 'a' to 'z' are interpreted as pattern letters representing the components of a date or time string. Text can be quoted using single quotes (') to avoid interpretation. All other characters are not interpreted; they're simply copied into the output string during formatting or matched against the input string during parsing.

The following pattern letters are defined (all other characters from 'A' to 'Z' and from 'a' to 'z' are reserved):

Table 11: Date and Time Patterns

Letter Date or Time Presentation Examples

G Era designator Text AD

y Year Year 1996; 96

M Month in year Month July; Jul; 07

w Week in year Number 27

W Week in month Number 2

D Day in year Number 189

d Day in month Number 10

Page 74: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 5 – Elluminate Live! Manager

Letter Date or Time Presentation Examples

F Day of week in month Number 2

E Day in week Text Tuesday; Tue

a am/pm marker Text PM

H Hour in day (0 – 23) Number 0

k Hour in day (1 – 24) Number 24

K Hour in am/pm (0 – 11) Number 0

h Hour in am/pm (1 – 12) Number 12

m Minute in hour Number 30

s Second in minute Number 55

S Millisecond Number 978

z Time zone General time zone Pacific Standard Time: PST; GMT-08:00

Z Time zone RFC 822 time zone -0800

Pattern letters are usually repeated, as their number determines the exact presentation:

Text: For formatting, if the number of pattern letters is 4 or more, the full form is used; otherwise a short or abbreviated form is used (if available). For parsing, both forms are accepted, independent of the number of pattern letters.

Number: For formatting, the number of pattern letters is the minimum number of digits, and shorter numbers are zero-padded to this amount. For parsing, the number of pattern letters is ignored unless it's needed to separate two adjacent fields

Year: For formatting, if the number of pattern letters is 2, the year is truncated to 2 digits; otherwise it is interpreted as a number.

For more information on the Date and Time Patterns, go to the following web page:

http://java.sun.com/j2se/1.4.2/docs/api/java/text/SimpleDateFormat.html

68 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 75: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 6 Elluminate Live! License Manager

The Elluminate Live! License Manager is responsible for the allocation of licenses. It tracks the Elluminate Live! Server and Elluminate Live! Manager, including from which license files servers consume seats, how many license seats are in use and how many license seats are available.

The license and the management of the license are split into two parts:

the license itself, represented by the .lic file, and the License Manager which controls it; and

consumers of license seats, represented by the .lm file, and the Elluminate Live! Server.

Described earlier in Chapter 4 Elluminate Live! Server (page 16), the elive.conf file contains

a path to the .lm file, which identifies the license target (customer/product/serial number) from which to request the license;

authentication data to prove that this Elluminate Live! Server is allowed to have licenses from that target; and

a reference to the License Manager host and port.

The .lic file and the .lm file are a cryptographic key pair, associated with a product, customer, and serial number. A given .lm file works only with the matched .lic file and vice-versa.

During the installation, the .lic file is installed with the License Manager; the .lm file is installed with Elluminate Live! Server. The Elluminate Live! software can be installed in the following hardware configurations:

Elluminate Live! Server and Elluminate Live! License Manager are installed on the same machine

Elluminate Live! Server is installed alone

Elluminate Live! License Manager is installed alone

The .lic File The .lic file contains the number of seats purchased, and the expiry date (if any).The ElluminateLive\common\licenses directory contains one or more .lic files (and possibly .part files containing persistent partitioning information), which represents the license(s) the License Manager is managing. A single License Manager server may handle multiple licenses (multiple .lic files).

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 69

Page 76: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 6 – Elluminate Live! License Manager

The .lic file is loaded by the License Manager and identifies a specific license that it makes available. The following information is contained in the .lic file:

the license target (product/customer/serial number)

the seat count

the expiry date (if any)

the private authentication key

The .lm File The .lm file is loaded by an Elluminate Live! Server, and identifies a specific license from which it wants to consume seats. The following information is contained in the .lm file:

the license target (/customer/product/serial number)

the public authentication key

The only thing that the .lm file does is allow the client to talk to the License Manager server and authenticate itself as being allowed to consume seats from a specific license. Anyone having the .lm file can request a license seat from the License Manager server from the pool represented by the corresponding .lic file.

This split allows the ability to have multiple servers running from a single license. (e.g., you could have a 100 seat license and run 2 servers, both of which acquire licenses from the common pool).

This split also allows a license to be updated with a new seat count or expiry date and re-issued to a customer, who can then replace the .lic file in the ElluminateLive\common\licenses directory and restart the License Manager, updating the license without having to shut down the Elluminate Live! Server(s) drawing licenses from the License Manager.

LMStatus Command The LMStatus command is a utility for querying the License Manager for the set of licenses that it serves, what servers are connected to consume those licenses, and how many license seats are in use and/or available.

The jar files can be found in the following locations (for default installations):

Windows

C:\Program Files\ElluminateLive\licensemanager\lib\LMStatus.jar

Linux & Solaris

/opt/ElluminateLive/LicenseManager/lib/LMStatus.jar

Mac

/Applications/ElluminateLive/LicenseManager/lib/LMStatus.jar

70 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 77: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 71

The syntax of LMStatus is as follows:

java –jar LMStatus.jar [-lm <host> <port>] [-lic lmFilePath|filters]

action

where:

-lm host port

Allows you to specify the License Manager to which you want to talk. If this is not supplied, the command assumes you are talking to a local License Manager running on the default port.

-lic lmFilePath

Specifies the .lm file identifying the license target you are referring to and provides the authentication data necessary for performing privileged operations (create/delete/change).

filters

Are arguments used to select the license target(s) to which to apply the action. The following filters may be used:

serial serialNumber – select the target with a specific serial number

product productName – select targets with a specific product (e.g., Elluminate Live! Academic Edition)

customer customerName – select targets with a specific customer

action

May be one of the following:

list – lists all of the license targets (possibly limited by filters)

status – reports the status of all the license targets (possibly limited by filters). This includes the partitions, consumers, attributes, and seat counts associated with each target.

Page 78: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 6 – Elluminate Live! License Manager

Example

Show the status of a local license server:

java – jar LMStatus.jar –status

72 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 79: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 7 Configuring SSL and HTTP Tunneling

The Elluminate Live! Server permits secure conferencing using the Secure Sockets Layer (SSL) to encrypt the conference data as it is transmitted between the client and server.

Before setting up secure conferencing, you should evaluate your requirements in this area against the costs, as SSL can place a significant computational load on the Elluminate Live! Server, which increases with the number of secured clients. If you require encryption on most, or all, of your connections, you may need to consider an SSL accelerator or network appliance to handle the encryption.

A number of files are involved in the configuration of SSL and HTTP tunneling. Refer to the table below for the default locations of these files on the various operating systems. Obviously, the location of these files will be different if you did not use the installation defaults.

Table 12: SLL & HTTP Tunneling Configuration File Locations

Filename OS Pathname

Windows C:\Program Files\ElluminateLive\manager\tomcat\ conf\server.xml

Linux & Solaris /opt/ElluminateLive/manager/tomcat/conf/ server.xml

server.xml

Macintosh /Applications/ElluminateLive/manager/tomcat/ conf/server.xml

Windows C:\Program Files\ElluminateLive\manager\tomcat\ webapps\ROOT\WEB-INF\resources\configuration.xml

Linux & Solaris /opt/ElluminateLive/manager/tomcat/webapps/ROOT/WEB-INF/resources/configuration.xml

configuration.xml

Macintosh /Applications/ElluminateLive/manager/tomcat/ webapps/ROOT/WEB-INF/resources/configuration.xml

Windows C:\Program Files\ElluminateLive\server8_0\ sessions\*.tmpl

Linux & Solaris /opt/ElluminateLive/server8_0/sessions/*.tmpl

*.tmpl

Macintosh /Applications/ ElluminateLive/server8_0/ sessions/*.tmpl

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 73

Page 80: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 7 – Configuring SSL and HTTP Tunneling

Filename OS Pathname

Windows C:\Program Files\ElluminateLive\server8_0\ elive.conf

Linux & Solaris /opt/ElluminateLive/server8_0/elive.conf

elive.conf

Macintosh /Applications/ElluminateLive/server8_0/ elive.conf

Windows C:\Program Files\ElluminateLive\manager\tomcat\ webapps\ROOT\WEB-INF\resources\templates\jnlp\ join_template.jnlp.v*

Linux & Solaris opt/ElluminateLive/manager/tomcat/webapps/ ROOT/WEB-INF/resources/templates/jnlp/ join_template.jnlp.v*

join_template .jnlp.v*

Macintosh Applications/ElluminateLive/manager/tomcat/ webapps/ROOT/WEB-INF/resources/templates/jnlp/ join_template.jnlp.v*

Use an XML editor to edit *.xml files. For all other files, to ensure that no extra characters will be saved during editing, it is recommended that they be edited with a text editor only (e.g., Notepad or emacs).

SSL Guide for a Distributed Configuration The instructions contained in this section assume a configuration where the Elluminate Live! Server and Elluminate Live! Manager are installed on the same server.

At this time, Elluminate supports only Apache Certificates purchased from Verisign and Thawte.

1. Determine what and how many servers you are installing for Elluminate Live!, Elluminate Live! Manager and Elluminate Live! License Manager. Also determine where SSL will be used.

2. Complete installation of the Elluminate Live! components.

3. Submit a request for the certificate. To do this, a Customer Service Request (CSR) will need to be made for each server that is housing Elluminate Live!, Elluminate Live! Manager and Elluminate Live! License Manager. To ensure that this process is followed correctly, Elluminate Customer Support will generate the CSR.

74 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 81: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Please send an email with the following information to [email protected].

Customer Service Request – Attn: Elluminate Technical Support Server= Country= State/Province= City= Domain/Common Name= Contact Info Email= Company Name= Password=

If you do not have a DNS name, the server name will need to be provided; IP addresses will not be recognized.

Example

Customer Service Request – Attn: Elluminate Technical Support Server= ELM/ELive ServerCountry= Canada State/Province= Alberta City= Calgary Domain/Common Name=server1.yourdomain.com Contact Info [email protected] Company Name= Your Company Inc. Password=elluminate

4. Once the CSR has been completed by Elluminate Customer Support, the processed Customer Service Request (.csr) will be sent back to you. At that time, you will be able to contact Verisign or Thawte to request the Apache SSL Certificates.

5. Once the Apache SSL Certificates have been purchased, a PKCS12 format file will need to be created. Elluminate Customer Support will need these certificates and the ROOT CA generated by Verisign or Thawte to generate this file. Once created, Elluminate Customer Support will then bundle the ROOT CA, Certificate and Key files into a PKCS12(.p12) format file.

6. Place the .p12 files on each of their corresponding servers.

Configuring the Elluminate Live! Manager with SSL 1. Stop the Elluminate Live! Manager services/daemons. (For instructions, see Start, Stop, or Restart

the Daemons and Services on page 5.)

2. Edit the server.xml file. (See Table 12 on page 73 for the file's pathname.)

a. Replace the following text:

<Connector maxThreads="150" enableLookups="false" acceptCount="100" connectionTimeout="20000" minSpareThreads="25" maxHttpHeaderSize="8192" disableUploadTimeout="true" port="80" maxSpareThreads="75" />

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 75

Page 82: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 7 – Configuring SSL and HTTP Tunneling

with

<Connector port="443"maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" disableUploadTimeout="true" acceptCount="100" scheme="https" secure="true" keystoreFile="[\path\to\my\keystore]" keystorePass="[keystore password]" keystoreType="PKCS12" clientAuth="false" sslProtocol="TLS" />

b. Replace the text [\path\to\my\keystore] with the actual path and replace the text [keystore password] with your keystore password.

<Connector port="443" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" disableUploadTimeout="true" acceptCount="100" scheme="https" secure="true" keystoreFile="\opt\ElluminateLive\common\svr1.elluminate.com.p12" keystorePass="elluminate" keystoreType="PKCS12" clientAuth="false" sslProtocol="TLS" />

3. Edit the configuration.xml file with an XML editor. (See Table 12 on page 73 for the file's pathname.)

a. Find the elmAddress property and change the default port to 443. <property> <name>elmAddress</name> <value> server1.yourdomain.com:443</value> </property>

b. Find the webProtocol property and change the value to https. <property> <name>webProtocol</name> <value>https</value> </property>

c. Find the helpUrl property and change the value from http to https and change the default port to 443.

<property> <name>helpUrl</name> <value>https://server1.yourdomain.com:443/help/help.help</value> </property>

d. Find the <codebasemanager> element tag and change all the URLs from http to https and change the default port to 443.

<codebasemanager> <codebase> <version>8.0</version> <url>https://server1.yourdomain.com:443/lib/8.0</url> </codebase> <codebase>

76 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 83: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 77

<codebase> <version>7.2</version> <url>https://server1.yourdomain.com:443/lib/7.0</url> </codebase> <codebase> <version>7.0</version> <url>https://server1.yourdomain.com:443/lib/7.0</url> </codebase> <codebase> <version>6.5</version> <url>https://server1.yourdomain.com:443/lib/6.5</url> </codebase> <codebase> <version>6.0</version> <url>https://server1.yourdomain.com:443/lib/6.0</url> </codebase> <codebase> <version>5.0</version> <url>https://server1.yourdomain.com:443/lib/5.0</url> </codebase> </codebasemanager>

e. Find the jinxProtocol property and change the value to ssljinx. <property> <name>jinxProtocol</name> <value>ssljinx</value> </property>

4. Edit all the *.tmpl files in the Session folder. (See Table 12 on page 73 for the pathnames.)

a. Find launchDirector and change the path from http to https and change the default port to 443.

b. Find url string, change http to https and change the default port to 443.

<template> groupName="ELMDefault" autoLaunch="true" launchDirector="https://server1.yourdomain.com:443/buildtemplate.event"> <auth class="WebAccessManager"> <url string="https://server1.yourdomain.com:443/authenticate.event? adapter=default"/> </auth>

5. Start the Elluminate Live! Manager services/daemons. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

6. Test the SSL configuration for the Elluminate Live! Manager. Launch a web browser and bring up the Elluminate Live! Manager (e.g., https://server1.yourdomain.com). Seeing this page will confirm a successful installation.

Page 84: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 7 – Configuring SSL and HTTP Tunneling

Configuring the Elluminate Live! Server with SSL 1. Stop the Elluminate Live! Manager services/daemons. (For instructions, see Start, Stop, or Restart

the Daemons and Services on page 5.)

2. Modify the elive.conf file. (See Table 12 on page 73 for the file's pathname.)

a. Find the network section, add a reference to the ssl keyfile and change protocols to ssljinx:

<network bandwidth="4000000"> <console port="2188" keyFile="/opt/ElluminateLive/common/licenses/Master.keys"/> <ssl keyFile="/opt/ElluminateLive/server8_0/lib/svr1.elluminate.com.p12" keyPass="elluminate"/> <conference port="2187" protocols="ssljinx"/> </network>

b. Find the manager section, change the codeBase URL from http to https and change the default port to 443:

<manager> <externalName value="server1.yourdomain.com" /> <elsRecordingFolder value="/opt/ElluminateLive/common/ recordings" /> <elmRecordingFolder value="/opt/ElluminateLive/common/ recordings” /> <maxLoad value="50" /> <serverLabel value="server1.yourdomain.com" /> <codeBase value="https://server1.yourdomain.com:443/lib/8.0" /> <encoding value="UTF-8" /> </manager>

3. Edit the template section of all the *.tmpl files in the Session folder. (See Table 12 on page 73 for the pathnames.)

a. Find launchDirector, change the path from http to https and change the default port to 443.

b. Find url string, change the path from http to https and change the default port to 443:

<template> groupName="ELMDefault" autoLaunch="true" launchDirector="https://192.168.1.177:443/buildtemplate.event"> <auth class="WebAccessManager"> <url string="https://192.168.1.177:443/authenticate.event? adapter=default"/> </auth>

4. Start the Elluminate Live! services/daemons. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

78 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 85: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

5. Test the SSL configuration. Create and launch a session within the Elluminate Live! Manager. Once the session starts, you should see a ‘lock’ icon in the lower left corner of the Elluminate Live! session.

Seeing this icon in the locked position confirms your SSL configuration has been completed successfully.

Please contact the Customer Suppport Team at Elluminate (http://www.elluminate.com/support) for detailed instructions on obtaining these certificates and installing them into Elluminate Live!

SSL Over Shared Network Ports Secure conferencing can be configured to use the same network ports as non-secured conferencing. This is useful when

dealing with clients who may need to use specific ports to pass through one or more firewalls between the client and the server; and

not all connections need to be secured.

It is also possible to designate certain ports as only secure or only non-secure. The default is non-secure.

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 79

Page 86: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 7 – Configuring SSL and HTTP Tunneling

SSL Using a Hardware SSL Accelerator or Appliance SSL can place a significant computational load on a server, particularly if you will be using it for the majority of your users. In this case, you may wish to use a network card or appliance with SSL acceleration. In order to use such a device with Elluminate Live!, it is necessary that the encryption be transparent to the Elluminate Live! Server (i.e., the appliance or card performs all of the SSL negotiation and encryption, and the connection appears to be a simple unencrypted connection from the perspective of the server).

For this to work, the server must be configured to accept normal non-secure jinx connections. The JNLP file used to connect to the server, however, must be configured to use the SSL accelerated port which, in turn, will pass unencrypted data to the Elluminate Live! Server. This is done by specifying the ssljinx protocol in the JNLP.

This is different than the "jinxssl" protocol that is used to talk directly to the Elluminate Live! Server.

Server Configuration Since the SSL protocol is handled by the network card or appliance, the server is unchanged. The conference port protocol needs to handle only the jinx protocol.

JNLP Configuration To configure the JNLP file to use a hardware-accelerated SSL port, you must modify the configuration.xml and the elive.conf files.

Any changes to the elive.conf file will require a restart of the Elluminate Live! Server.

1. Edit the configuration.xml file and set the jinxProtocol value to ssljinx. (See Table 12 on page 73 for the file's pathname.) <property> <name>jinxProtocol</name> <value>ssljinx</value> </property>

2. Edit the elive.conf file and set the conference port to the appropriate value and set the protocols value to ssljinx. (See Table 12 on page 73 for the file's pathname.) Find <network> and change the conference port (if applicable) and the protocols value to ssljinx.

<network > <console port="2188" keyFile="C:\Program Files\ElluminateLive\common\ licenses\Master.keys"/> <conference port="2187" protocols="ssljinx"/> </network>

80 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 87: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

3. Restart all services or daemons. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

Configuring HTTP Tunneling If Elluminate Live! clients are unable to connect to the Elluminate Live! Server 8.0, you may have the option of embedding or tunneling the JINX data through a proxy server. The servers then send the data to the intended destination and forward the responses back to the HTTP-Tunnel client. This forwarding technique effectively bypasses firewalls, permitting the users to successfully use Elluminate Live! client.

All Elluminate Live! 8.0 clients have the option to connect using HTTP tunneling. To define the proxy server address, do the following:

1. Join an Elluminate Live! session.

2. Open the Preferences dialog in one of the following ways:

From the Tools menu, select Preferences… (Windows, Linux & Solaris) From the Elluminate Live! menu, select Preferences (Macintosh)

Enter Control+Comma (Windows, Linux & Solaris) Enter ⌘, (Macintosh)

3. In the left pane of the Preferences dialog, select Proxy Settings under General. The Proxy Settings preferences panel appears.

4. Click on the Method option menu and select the appropriate proxy server from the list.

5. Enter your proxy server IP address in the Server field and enter your proxy serverport number in the Port field.

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 81

Page 88: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 7 – Configuring SSL and HTTP Tunneling

6. To use this from the Elluminate Live! Server 8.0 side, configure each conference port with the following in the elive.conf file:

<conference port="2187" protocols="jinx" tunnel="http"/>

The default value for tunnel is direct, meaning that all attempted connections shall be direct. Refer to the General Installation Parameters – elive.conf section to implement the changes on the Elluminate Live! Server.

Configuring Tomcat

You must have an SSL Certificate that is signed by a trusted Certificate Authority (such as Verisign or Thawte) before you may proceed in configuring Tomcat for SSL.

To get SSL working, execute the following steps:

1. Install Elluminate Live! Manager. For the Elluminate Live! Manager port, choose the SSL port that you are going to use (e.g., 443, 8443).

2. Once installed, verify the Elluminate Live! Manager installation is working. Launch a web browser and bring up the Elluminate Live! Manager using normal HTTP at the port (i.e., http://localhost:443).

3. Stop the Elluminate Live! Manager service. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

4. Edit the server.xml file. (See Table 12 on page 73 for the file's pathname.)

a. Change the following:

<Connector port="443">

to <Connector port="443" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" disableUploadTimeout="true" acceptCount="100" scheme="https" secure="true" keystoreFile="[\path\to\my\keystore]" keystorePass="[keystore password]" keystoreType="[PKCS12]" clientAuth="false" sslProtocol="TLS" />

b. Replace the text [\path\to\my\keystore] with the actual path and replace the text [keystore password] with your keystore password.

<Connector port="443" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" disableUploadTimeout="true" acceptCount="100" scheme="https" secure="true" keystoreFile="\opt\ElluminateLive\common\svr1.elluminate.com.p12" keystorePass="elluminate" keystoreType="PKCS12" clientAuth="false" sslProtocol="TLS" />

82 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 89: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 83

5. Edit the configuration.xml file. (See Table 12 on page 73 for the file's pathname.)

a. Find the elmAddress property and to change the default port to 443.

a. Find the webProtocol property and change the value to https.

b. Find the helpUrl property and change the value from http to https and change the default port to 443.

c. Find the <codebasemanager> element tag and change all the urls from http to https.

d. Find the jinxProtocol property and change the value to ssljinx.

<property> <name>webProtocol</name> <value>https</value> </property> … <property> <name>helpUrl</name> <value>https://server1.yourdomain.com:443/help/help.help</value> </property> <codebasemanager> <codebase> <version>8.0</version> <url>https://server1.yourdomain.com:443/lib/8.0</url> </codebase> <codebase> <version>7.2</version> <url>https://server1.yourdomain.com:443/lib/7.0</url> </codebase> <codebase> <version>7.0</version> <url>https://server1.yourdomain.com:443/lib/7.0</url> </codebase> <codebase> <version>6.5</version> <url>https://server1.yourdomain.com:443/lib/6.5</url> </codebase> <codebase> <version>6.0</version> <url>https://server1.yourdomain.com:443/lib/6.0</url> </codebase> <codebase> <version>5.0</version> <url>https://server1.yourdomain.com:443/lib/5.0</url> </codebase> </codebasemanager> … <property> <name>jinxProtocol</name> <value>ssljinx</value> </property>

Page 90: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 7 – Configuring SSL and HTTP Tunneling

6. Edit the template section of all the *.tmpl files in the Session folder. (See Table 12 on page 73 for the pathname.)

a. Find launchDirector and change the path from http to https and change the default port to 443.

b. Find url string and change the value from http to https and change the default port to 443.

<template> groupName="ELMDefault" autoLaunch="true" launchDirector="https://server1.yourdomain.com:443/buildtemplate.event"> <auth class="WebAccessManager"> <url string="https://server1.yourdomain.com:443/authenticate.event? adapter=default"/>

</auth>

7. Copy the *.tmpl files to where the session files reside on your Elluminate Live! Server; overwrite any of the files that may already exist.

8. Edit the elive.conf file. (See Table 12 on page 73 for the file's pathname.)

a. Find codeBase and change the value from http to https.

b. Edit protocols and change the value to either ssljinx or jinxssl.

<codeBase value="https://192.168.1.162/lib/8.0" /> ... <conference port="2187" protocols="ssljinx" />

9. Restart the Elluminate Live! Manager service/daemon. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

10. Verify the installation is working; bring up Elluminate Live! Manager using HTTPS at the port (e.g., https://localhost:443).

Additional Information on configuring Tomcat with SSL can be found at http://tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html

AES-128 and AES-256 Encryption Elluminate Live! 8.0 uses Sun Microsystems Java Secure Socket Extension (JSSE) software for its SSL support, which includes strong cryptography in the exportable version.

To use either AES-128 or AES-256 encryption, you first must meet the prerequisites. Once you have done so, you can edit the JNLP file to use either AES-128 or AES-256 encryption. You may also further define the order and which specific SSL Cipher Suites you wish to use.

84 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 91: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 85

Prerequisites Elluminate Live! 8.0 will allow you to use either AES-128 or AES-256 encryption, under the following conditions:

You must be running JRE 1.4.2 or later.

The JNLP must be configured to use the ssljinx protocol (in the configuration.xml file, the jinxProtocol property must be set to ssljinx).

The server must be configured to use SSL (in the elive.conf file, the protocols property must be set to ssljinx ).

The SSL certificates must be installed on the Elluminate Live! Server.

Using AES-128 Encryption If you have met all the prerequisites, modify the join_template.jnlp.v* file for the appropriate version. (See Table 12 on page 73 for the file's pathname.)

Search for the string <resources os="Windows Linux SunOS Mac\ OS\ X"> and add the following line after it.

<property name="com.elluminate.net.SSLCipherSuites"

value="TLS_RSA_WITH_AES_128_CBC_SHA"/>

Example

<resources os="Windows Linux SunOS Mac\ OS\ X">

<property name=" com.elluminate.net.SSLCipherSuites"

value="TLS_RSA_WITH_AES_128_CBC_SHA"/>

<property name="apple.laf.useScreenMenuBar" value="true"/>

<property

name="apple.awt.window.position.forceSafeProgrammaticPositioning"

value="false"/>

Using AES-256 Encryption If you want to use AES-256, in addition to meeting the prerequisites listed above, you will need to do the following:

1. Download and install the JCE unlimited strength security policy files from http://java.sun.com/j2se/1.4.2/download.html and install them on both the client and the server.

2. Edit the join_template.jnlp.v* file. (See Table 12 on page 73 for the file's pathname.) Change the property name value (if you were previously using AES-128) to TLS_RSA_WITH_AES_256_CBC_SHA

Page 92: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 7 – Configuring SSL and HTTP Tunneling

Example

<resources os="Windows Linux SunOS Mac\ OS\ X">

<property name=" com.elluminate.net.SSLCipherSuites" value="TLS_RSA_WITH_AES_256_CBC_SHA"/>

Or change the property name value to include both (or any combination of the values listed in http://java.sun.com/j2se/1.4.2/docs/guide/security/jsse/JSSERefGuide.html), in the order of preference and separated by commas.

This assumes you are not using an SSL accelerator at the server. If you are, the client/JNLP requirements are the same and, at the server, you need to be sure your SSL accelerator supports the protocols you specified in the JNLP.

SSL Cipher Suites List The default cipher suite for JSSE includes the following combinations:

SSL_RSA_WITH_RC4_128_MD5

SSL_RSA_WITH_RC4_128_SHA

SSL_RSA_WITH_3DES_EDE_CBC_SHA

SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA

SSL_RSA_WITH_DES_CBC_SHA

SSL_DHE_DSS_WITH_DES_CBC_SHA

SSL_RSA_EXPORT_WITH_RC4_40_MD5

SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA

Since JSSE is running on both ends (unless accelerator hardware or software is in use), the same default cipher suite should exist on both ends.

If you set the system property com.elluminate.jinx.SSLCipherSuites to a comma-separated list of cipher suite names (as listed above), it will use those (in the order you supply) rather than the default list.

For example, if the property name in the JNLP file was set to the following, the two cipher suites named would be enabled:

<property name=" com.elluminate.jinx.SSLCipherSuites"

value="SSL_RSA_WITH_3DES_EDE_CBC_SHA,SSL_RSA_WITH_RC4_128_MD5"/>

86 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 93: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 8 Notification Emails

Email notifications can be sent from Elluminate Live! Manager to Moderators, Participants, and Guests notifying them of a session/meeting. The email_template.txt file contains the message that is sent.

The following is the default email_template.txt file. The text has been formatted with tokens bolded – this is not how it will appear when you open the file up in a text editor.

You have been invited to attend an online Elluminate meeting(s)#{if:MeetingView.getFacilitatorName <> null} created by

#{MeetingView.getFacilitatorName}#{end}: #{SessionTitle}.

#{if:isModerator = true}You have been assigned the #{facilitatorLabel}

role for the meeting(s).#{end}

The meeting(s) are scheduled for the following dates and times: #{loop:Meetings}

Meeting Link: #{ELMURL}/join_meeting.html?#{ParameterNames.getMeetingId}=#{currentRow.g

etMeetingId}

Add to Calendar: #{ELMURL}/build_calendar.event?#{ParameterNames.getMeetingId}=#{currentRo

w.getMeetingId}

Starts: #{currentRow.getFormattedStartDate}

#{currentRow.getFormattedStartTime}

Ends: #{currentRow.getFormattedEndDate}

#{currentRow.getFormattedEndTime}#{end}

#{if:isParticipant = true}Use your Elluminate Live! Manager userid and

login password to join.#{end} #{if:isNonParticipant = true}

Enter your name at the login prompt.#{end} #{if:isClosed = true}

This meeting requires the following password to join: #{MeetingView.getPassword}#{end} #{if:isOpen = true }

This meeting does not require a password to join. Please leave the password field blank.#{end}

To join the meeting, click on the appropriate link above.#{if:ThresholdValue > 0)

You may join the meeting #{ThresholdValue} minutes prior to the start

time.#{end}#{if:isNotes = true}

Additional instructions for teleconferencing are: #{Notes}#{end}

If this is the first time you will be using Elluminate, you may be

prompted to download some software which may take anywhere from 2 to 20

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 87

Page 94: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 8 – Notification Emails

minutes depending upon your Internet connection speed. You can pre-

configure your system with the required software by going to the support page located at: #{ELMURL}/support.html.

Please make sure your computer has a microphone and speakers to be able

to talk and hear while you are in the Elluminate meeting.

Customizing the Notification Email You can customize the default notification message by editing the email_template.txt file.

To ensure that no extra characters will be saved in the email template file, it is recommended that it be edited with a text editor only (e.g., Notepad or emacs).

The email_template.txt file can be found in the following default locations. (Obviously, the location of this file will be different if you did not use the installation default.)

Windows

C:\Program Files\ElluminateLive\manager\tomcat\webapps\ROOT\WEB-

INF\resources\templates\email\email_template.txt

Linux & Solaris

/opt/ElluminateLive/manager/tomcat/webapps/ROOT/WEB-

INF/resources/templates/email/email_template.txt

Mac

/Applications/ElluminateLive/manager/tomcat/webapps/ROOT/WEB-INF/resource

s/templates/email/email_template.txt

To customize the email message, edit the default text and add or remove tokens. The following tables describe the tokens that may be used in the template file.

Table 13 describes the general Elluminate Live! properties that are passed to the template context map for the current email notification.

Table 13: Context Map Tokens in Email Notification Template

Token Description

BOUNDARYTIME The same as ThresholdValue (see below). BOUNDARYTIME is valid, but ThresholdValue is the preferred token.

ELMAddress The IP address of the Elluminate Live! Manager without the HTTP prefix (e.g., 192.168.1.111:8080/QA Institution).

ELMURL The IP address of the Elluminate Live! Manager with the HTTP prefix (e.g., http://192.168.1.111:8080/QA Institution).

88 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 95: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 89

Token Description

facilitatorLabel The name displayed for the Facilitator role in Elluminate Live! Manager. The default value is Moderator. A System Administrator in Elluminate Live! Manager may modify this field in the labelPrefs.html page (Preferences > Labels).

FacilitatorName The User ID of the creator of this session/meeting.

HelpUrl The URL to which a user’s web browser is directed when they click on the Help tab in the Elluminate Live! Manager. A System Administrator in Elluminate Live! Manager may modify this field in the generalPrefs.html page (Preferences > General).

MEETINGID The session/meeting's unique identifier.

MEETINGNAME The same as SessionTitle (see below). MEETINGNAME is valid, but SessionTitle is the preferred token.

Meetings A collection of meetingView objects.

Notes The Participant or Moderator teleconferencing notes.

SessionTitle The name of the session/meeting.

ThresholdValue The number of minutes prior to the scheduled start time that a user can join the session/meeting. A System Administrator in Elluminate Live! Manager may modify this field in the generalPrefs.html page (Preferences > General).

Table 14 describes the objects that are stored in the template context map.

Table 14: Template Object Tokens in Email Notification Template

Token Description

MeetingView.getFacilitatorName The User ID of the creator of this session/meeting.

MeetingView.getPassword The password for the session/meeting.

ParameterNames.getMeetingId The name for the meetingId argument.

currentRow.getFormattedEndDate A date formatted string for the end of the session/meeting (e.g., 01/29/07)

currentRow.getFormattedEndTime A time formatted string for the end of the session/meeting. (e.g., 17:00 MST)

currentRow.getFormattedStartDate A date formatted string for the start of the session/meeting. (e.g., 01/29/07)

currentRow.getFormattedStartTime A time formatted string for the start of the session/meeting. (e.g., 16:00 MST)

currentRow.getMeetingId The session/meeting's unique identifier.

Page 96: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 8 – Notification Emails

Table 15 below describes the state tokens that can be used in the template context map. These tokens are used with conditional tokens (e.g., #{if:isTokenName = true/false}).

Table 15: State Tokens in Email Notification Template

Token Description

isClosed Is this meeting closed?

isOpen Is this meeting open?

isModerator Is this template used for session/meeting Moderators?

isNonParticipant Is this template for non-Elluminate Live! Manager users (no login account)?

isParticipant Is this template used for Elluminate Live! Manager users?

isNotes Are Participant or Moderator teleconferencing notes to be merged into the template?

Example:

#{if:isParticipant = true}Use your Elluminate Live! Manager userid and

login password to join.#{end} #{if:isNonParticipant = true} Enter your

name at the login prompt.#{end}

The email notification for Elluminate Live! Manager users will include the following sentence:

Use your Elluminate Live! Manager userid and login password to join.

The email notification for non-Elluminate Live! Manager users (no login account) will include the following sentence:

Enter your name at the login prompt.

90 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 97: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 9 Configuration of Common Settings

This chapter provides details on how to change some of the more common settings, such as the Elluminate Live! Manager IP Address.

A number of files are involved in post-installation configuration. Refer to the table below for the default locations of these files on the various operating systems. (Obviously, the location of these files will be different if you did not use the installation defaults.)

Table 16: Post-Installation Configuration File Locations

Filename OS Pathname

Windows C:\Program Files\ElluminateLive\manager\tomcat\ webapps\ROOT\ WEB-INF\resources\ configuration.xml

Linux & Solaris /opt/ElluminateLive/manager/tomcat/webapps/ROOT/WEB-INF/resources/configuration.xml

configuration.xml

Macintosh /Applications/ElluminateLive/manager/tomcat/ webapps/ROOT/WEB-INF/resources/configuration.xml

Windows C:\Program Files\ElluminateLive\server8_0\ sessions\*.tmpl

Linux & Solaris /opt/ElluminateLive/server8_0/sessions/*.tmpl

*.tmpl

Macintosh /Applications/ElluminateLive/server8_0/sessions/ *.tmpl

Windows C:\Program Files\ElluminateLive\server8_0\ elive.conf

Linux & Solaris /opt/ElluminateLive/server8_0/elive.conf

elive.conf

Macintosh /Applications/ElluminateLive/server8_0/ elive.conf

Windows C:\Program Files\ElluminateLive\manager\tomcat\ conf\server.xml

Linux & Solaris /opt/ElluminateLive/manager/tomcat/conf/ server.xml

server.xml

Macintosh /Applications/ElluminateLive/manager/tomcat/ conf/server.xml

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 91

Page 98: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 9 – Configuration of Common Settings

Filename OS Pathname

Windows C:\Program Files\ElluminateLive\common\licenses\ *.lic

Linux & Solaris /opt/ElluminateLive/common/licenses/*.lic

*.lic

Macintosh /Applications/ElluminateLive/common/licenses/ *.lic

Windows C:\Program Files\ElluminateLive\common\licenses\ *.lm

Linux & Solaris /opt/ElluminateLive/common/licenses/*.lm

*.lm

Macintosh /Applications/ElluminateLive/common/licenses/ *.lm

Use an XML editor to edit *.xml files. For all other files, to ensure that no extra characters will be saved during editing, it is recommended that they be edited with a text editor only (e.g., Notepad or emacs).

Changing the Elluminate Live! Manager IP Address

1. Edit the configuration.xml file with an XML editor. (See Table 16 on page 91 for the file's pathname.)

a. Search for elmAddress and update the IP Address within the <value> element.

<property> <name>elmAddress</name> <value>192.168.1.124:8080</value> </property>

b. Search for helpUrl and update the IP Address within the <value> element.

<property> <name>helpUrl</name> <value>192.168.1.124:8080/help.html</value> </property>

c. Search for <url>http: and change the URL IP address for the each codebase within the <url> element

<codebase> <version>8.0</version> <url>http://192.168.1.124:8080/lib/8.0</url> </codebase>

d. Save and Exit the file.

92 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 99: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 93

2. Edit the ELMDefault.tmpl file. (See Table 16 on page 91 for the file's pathname.)

a. Search for launchDirector= and change the IP Address.

launchDirector="http://192.168.1.124:8080/buildtemplate.event"

b. Search for url string= and change the IP Address.

<url string="http://192.168.1.124:8080/

authenticate.event?adapter=default"/>

3. Restart all three services/daemons: Elluminate Live! Server, Elluminate Live! Manager and Elluminate Live! License Manager. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

Changing the Elluminate Live! Server IP Address 1. Edit the elive.conf file. (See Table 16 on page 91 for the file's pathname.)

a. Search for externalName and change the IP Address.

<externalName value="192.168.1.126" />

b. Save and Exit the file.

2. Restart the Elluminate Live! Server and Elluminate Live! Manager services/daemons. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

Changing the Elluminate Live! License Manager IP Address 1. Edit the configuration.xml file with an XML editor. (See Table 16 on page 91 for the file's

pathname.)

a. Search for licenseManagerAddress and change the IP Address within the <value> element.

<argument> <name>licenseManagerAddress</name> <value>192.168.1.124</value> </argument>

b. Save and Exit the file.

2. Edit the elive.conf file. (See Table 16 on page 91 for the file's pathname.)

a. Search for host= and change the IP Address.

<license path="C:\Program Files\ElluminateLive\common\licenses\demo.lm" host="192.168.1.124" port="2186" />

b. Save and Exit the file.

3. Restart all three services/daemons: Elluminate Live! License Server, Elluminate Live! Manager and Elluminate Live! Manager. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

Page 100: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 9 – Configuration of Common Settings

Changing the Elluminate Live! Manager Port

1. Edit the server.xml file with an XML editor. (See Table 16 on page 91 for the file's pathname.)

a. Search for Connector port= and change the port number.

<Service name="Elluminate Live! Manager 2.7">

<Connector port="8080" />

b. Search for codebasemanager and change the port number.

c. Save and Exit the file.

2. Edit the configuration.xml file with an XML editor. (See Table 16 on page 91 for the file's pathname.)

a. Search for elmAddress and change the port number.

<property> <name>elmAddress</name> <value>192.168.1.124:8080</value> </property>

b. If tomcat is serving up your codebase, then you must also update the port number for all the URLs within the <codebasemanager> section. Search for <codebasemanager> and update the port numbers for all the urls.

<codebasemanager> <codebase> <version>8.1</version> <url>http://192.168.1.124:8080/lib/8.0</url> </codebase> <version>7.2</version> <url>http://192.168.1.124:8080/lib/7.0</url> </codebase> <codebase> <version>7.0</version> <url>http://192.168.1.124:8080/lib/7.0</url> </codebase> <codebase> <version>6.5</version> <url>http://192.168.1.124:8080/lib/6.5</url> </codebase> <codebase> <version>6.0</version> <url>http://192.168.1.124:8080/lib/6.0</url> </codebase> <codebase> <version>5.0</version> <url>http://192.168.1.124:8080/lib/5.0</url> </codebase> </codebasemanager>

c. Save and Exit the file.

94 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 101: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 95

3. Edit the elive.conf file. (See Table 16 on page 91 for the file's pathname.)

a. Search for codeBase and change the port number.

<codeBase value="http://192.168.1.124:8080/lib/8.0" />

b. Save and Exit the file.

4. Edit the ELMDefault.tmpl file. (See Table 16 on page 91 for the file's pathname.)

a. Search for launchDirector= and change the port number.

launchDirector="http://192.168.1.124:8080/buildtemplate.event

b. Search for url string= and change the port number.

auth class="WebAccessManager"> <url string="http://192.168.1.124:8080/authenticate.event? adapter= default"/> </auth>

c. Save and Exit the file.

5. Restart all three services/daemons: Elluminate Live! Server, Elluminate Live! Manager and Elluminate Live! License Manager. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

Changing the Elluminate Live! Server Port

1. Edit the elive.conf file. (See Table 16 on page 91 for the file's pathname.)

a. Search for conference port= and change the port number.

<conference port="2187" protocols="jinx"/>

b. Save and Exit the file.

2. Restart the Elluminate Live! Server and Elluminate Live! Manager services/daemons. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

Changing the Elluminate Live! License Manager Port

1. Edit the elive.conf file. (See Table 16 on page 91 for the file's pathname.)

a. Search for port= and change the License Manager port number.

<license path="C:\Program Files\ElluminateLive\common\licenses\ demo.lm" host="192.168.1.124" port="2186" />

b. Save and Exit the file.

Page 102: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 9 – Configuration of Common Settings

2. Edit the configuration.xml file with an XML editor. (See Table 16 on page 91 for the file's pathname.)

a. Search for licenseManagerPort and change the License Manager port number value.

<argument> <name>licenseManagerPort</name> <value>2186</value>

b. Save and Exit the file.

3. (Windows only) Edit the licensemanager.conf file (pathname below).

Windows

C:\Program Files\ElluminateLive\common\wrapper\licensemanager.conf

a. Search for wrapper.app.parameter.5= and change the port number.

wrapper.app.parameter.5=2186

b. Save and Exit the file.

4. (Linux/Solaris only) Edit the ellmd file (pathname below).

Linux & Solaris

/opt/ElluminateLive/licensemanager/bin/ellmd

a. Search for port= and change the port number.

port=2186

b. Save and Exit the file.

5. Restart all three services/daemons: Elluminate Live! License Manager, Elluminate Live! Server and then Elluminate Live! Manager. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

Updating the License File

1. Stop the Elluminate Live! Server and Elluminate Live! License Manager services/daemons. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

2. Copy the *.lic and *.lm files you received from Elluminate and put them in the appropriate location Licenses folder. (See Table 16 on page 91 for the full pathname.)

3. Edit the elive.conf file to verify the License Manager path. (See Table 16 on page 91 for the file's pathname.)

a. Search for path= and update the path.

<license path="C:\Program Files\ElluminateLive\common\licenses\demo.lm"

b. Save and Exit the file.

96 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 103: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 97

4. Restart the Elluminate Live! License Manager 2.0 and Elluminate Live! Server 8.0 services/daemons. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

Page 104: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 10 Database Administration

Database administration serves a number of important functions, from improving the performance of your database to avoiding a disaster that could result in lost data or costly system downtime. There are two key practices that will help improve database performance and prevent a loss of data or costly system downtime:

Monitor and manage your available disk space.

Implement a comprehensive backup and maintenance plan.

Supported Databases During a default installation of Elluminate Live!, Mckoi will be the database installed along with Elluminate Live! Manager 2.7. The Mckoi SQL Database is an SQL (Structured Query Language) database management system that was written for the Java platform.

Other databases that can be used with Elluminate Live! Manager version 2.7 are Oracle 9, SQL 2000, or any other JDBC-compliant database.

Disk Space Running out of disk space in the middle of an operation can cause serious database corruption. Follow the best practices listed below to ensure that you do not run out of disk space when running Elluminate Live!:

Ensure that you have carefully assessed the minimum server requirements that are outlined in the Installation Guide. The 400 MB of free disk space that is recommended does not include the space that is required for extended log files and session recordings.

Trim Elluminate Live! log files periodically. They can grow exponentially, depending on the level of activity on the server.

Consistently monitor the disk space of the recordings directory. The recordings directory has the potential to grow very large in a very short time, depending on the components that are used in the session (e.g., multimedia, video, application sharing, etc.). As the server administrator, you can’t control the size of the recordings, but this directory should be carefully monitored. You may also consider having this recordings directory reside on a separate partition.

Manage your backups. The Elluminate Live! Manager data is backed up on your server daily at 2:00 am (default setting) and this can accumulate over time depending on the size of the data file. A good practice is to monitor these files on a regular basis.

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 98

Page 105: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Backups

Performing Backups Backing up your database regularly is the single most important factor in preventing a data loss disaster resulting from a network, application or hardware failure.

As with any production data storage repository, it is important to have a comprehensive backup and maintenance plan. The frequency of backups can vary based upon the frequency of modifications, or additions of policies and rules. Consult with your database administrator, who should already have a backup plan in place.

It is highly recommended that you keep your backup files on a separate partition or server to avoid any corruption.

It is stongly recommended that you make a backup immediately after upgrading to Elluminate Live! Manager r. Elluminate, Inc. does not support the restoration of backups made with versions of Elluminate Live! Manager earlier than version 2.5.

With a default installation, the data from the Elluminate Live! Manager is set to back up daily at 2:00 a.m. This backup interval may be modified, if necessary, by following these steps:

1. Stop the Elluminate Live! Manager service/daemon. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

2. Edit the configuration.xml file with an XML editor. (See Table 16 on page 91 for the file's pathname.)

a. Search for CalendarBackupTrigger and modify the <value> of the interval.

<trigger> <class>com.elluminate.backup.impl.CalendarBackupTrigger</class> <argument> <name>interval</name> <value>MON 02:00,TUE 02:00,WED 02:00,THU 02:00, FRI 02:00,SAT 02:00,SUN 02:00</value> </argument>

The time interval is based on a 24-hour clock and, by default, is set to run a backup at 2 in the morning.

If you do not want the database to be automatically backed up, set the <value> to 0.

<value>0</value>

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 99

Page 106: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 10 – Database Administration

3. Restart the Elluminate Live! Manager service/daemon to pick up the changes. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

It is highly recommended that you consider performing your own backup of the database at regular intervals.

Restoring Data You may find it necessary to perform a backup recovery of your Elluminate Live! Manager database as a result of a corruption of your database or a need to restore the data from an earlier time. The Backup Manager utility allows you to restore a specific backup file to a specific instance.

Elluminate, Inc. does not support the restoration of backups made with versions of Elluminate Live! Manager earlier than version 2.5.

If you are running Elluminate Live! Manager 2.7 and try to restore a Elluminate Live! Manager 2.0 backup, for example, the Restore Manager will hang and your data will be corrupted.

Using the Backup Manager Utility in GUI Mode

1. Stop the Elluminate Live! Manager service/daemon. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

2. Launch the Backup Manager Utility:

Windows

Change to the following directory:

C:\Program Files\ElluminateLive\common\Restore

Execute the Backup Manager Utility jar file:

backupUtility.jar

Linux & Solaris

Change to the following directory:

/opt/ElluminateLive/common/Restore

Execute the Backup Manager Utility jar file:

/opt/ElluminateLive/_jvm/bin/java –jar backupUtility.jar

100 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 107: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Mac

Change to the following directory:

/Applications/ElluminateLive/common/Restore

Execute the Backup Manager Utility jar file:

sudo java –jar backupUtility.jar

The Backup Manager Utility window will open with the Choose Install Directory panel.

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 101

Page 108: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 10 – Database Administration

3. Click on the Choose Install Directory button and select the Elluminate Live! installation folder location. The folder location will appear in the textbox.

4. Click on the Next button. The Select an Instance panel will appear. From the Select Instance list, select the Instance to which you are restoring the backup.

102 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 109: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

5. Click on the Next button. Select the backup file you wish to restore. In the example below, note that there are both automatic (THU0200) and manual (manual_20070226_020240) backups.

6. Click on the Start Restore button. A Confirmation dialog box appears:

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 103

Page 110: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 10 – Database Administration

7. Click on the Yes button to continue with the operation. The message "Restoration in progress" will appear in the status bar.

The following confirmation message will appear upon a successful operation.

8. Click on the No button to close the utility. Click on the Yes button to perform another backup. If you selected Yes, you will be returned to the Chose Install Directory page. Go back to step 3.

104 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 111: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 105

Using the Backup Manager Utility in Console Mode

There are cases where the Backup Manager application will have to be launched through the command line – such as if you are running a headless server.

1. Stop the Elluminate Live! Manager service/daemon. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

2. Launch the Backup Manager Utility:

Windows

Change to the Restore folder. The default location is

C:\Program Files\ElluminateLive\common\Restore

Run the following command:

“C:\Program Files\ElluminateLive\_jvm\bin\java”

-cp backupUtility.jar;jdom.jar com.elluminate.elm.backup.BackupManager

-restore -dir=”INSTALL_DIR” -instance=INSTANCE -file=BACKUP_FILE

-console

Example

“C:\Program Files\ElluminateLive\_jvm\bin\java”

-cp backupUtility.jar;jdom.jar

com.elluminate.elm.backup.BackupManager -restore

-dir="C:\Program Files\ElluminateLive" -instance=ROOT

-file=manual_20061201_091639.backup -console

Linux & Solaris

Change to the Restore directory. The default location is

/opt/ElluminateLive/common/Restore

Run the following command:

/opt/ElluminateLive/_jvm/bin/java -cp backupUtility.jar:jdom.jar

com.elluminate.elm.backup.BackupManager -restore -dir=INSTALL_DIR

-instance=INSTANCE -file=BACKUP_FILE -console

Example

/opt/ElluminateLive/_jvm/bin/java -cp backupUtility.jar:jdom.jar

com.elluminate.elm.backup.BackupManager -restore

-dir=/opt/ElluminateLive/ -instance=ROOT

-file=manual_20070226_122016.backup -console

Page 112: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 10 – Database Administration

Mac

Change to the Restore directory. The default location is

/Applications/ElluminateLive/common/Restore

Run the following command:

sudo java -cp backupUtility.jar:jdom.jar

com.elluminate.elm.backup.BackupManager -restore -dir=INSTALL_DIR

-instance=INSTANCE -file=BACKUP_FILE -console

Example

sudo java -cp backupUtility.jar:jdom.jar

com.elluminate.elm.backup.BackupManager –restore

-dir=/Applications/ElluminateLive -instance=ROOT

-file=manual_20061201_091639.backup -console

In all cases, you will receive confirmation via the command console that your restore has completed successfully.

106 Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide

Page 113: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 11 Troubleshooting

If a problem occurs during installation or uninstallation, check the appropriate log file in the log directory. There are five log files, each logging the activity of the three Elluminate Live! components:

The elive.log file shows the status of the Elluminate Live! Server (for all operating systems).

The licensemanager.log file shows the status of the Elluminate Live! License Manager (for all operating systems).

The wrapper.log file shows the status of the Elluminate Live! Manager, including any errors in starting up the Manager (for Windows only).

The elm.log file shows the status of the Elluminate Live! Manager (for Windows only).

The catalina.log file shows the status of the Elluminate Live! Manager (for Linux, Solaris and Macintosh).

The location of the root ElluminateLive directory, and therefore the log files, was chosen during installation and may vary between systems. The default pathnames are listed in Table 17.

Table 17: Log File Locations

OS Component Log File Pathname Server C:\Program Files\ElluminateLive\common\log\

elive.log

License Manager C:\Program Files\ElluminateLive\common\log\ licensemanager.log

Manager C:\Program Files\ElluminateLive\common\wrapper\ wrapper.log

Windows

Manager C:\Program Files\ElluminateLive\common\log\ elm.log

Server /var/log/elive.log Note: this pathname assumes you are running as a root user.

License Manager /var/log/licensemanager.log Note: this pathname assumes you are running as a root user.

Linux & Solaris

Manager /opt/ElluminateLive/manager/tomcat/common/logs/ catalina.out

Server /Applications/ElluminateLive/manager/tomcat/ common/log/elive.log

License Manager /Applications/ElluminateLive/manager/tomcat/ common/log/licensemanager.log

Macintosh

Manager /Applications/ElluminateLive/manager/tomcat/ common/log/catalina.out

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 107

Page 114: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 11 – Troubleshooting

The elive.log File The elive.log file shows the status of the Elluminate Live! Server. Any errors in starting up the server will be displayed here.

In the elive.conf file there are parameters set for the log file output. The default elive.conf file has the following defined for the log file:

<log file="C:\Program Files\ElluminateLive\common\log\elive.log" size="250000"> log.load log.launch log.access </log>

There are a number of parameters that can be added to the elive.conf file to provide you with a better picture of what is happening in a session. (See Table 16 on page 91 for the elive.conf file's pathname.)

The most common parameters are the following:

log.memory

Causes the server to issue JVM heap memory consumption reports approximately once per hour.

jinx.hangup

Causes the server to issue messages when clients are intentionally disconnected from the server, either by leaving the session, being forced out by a Moderator, or pushed out via the admin console tool, server shutdown, etc.

jinx.disconnection

Causes the server to issue messages when clients are disconnected because of I/O problems (timed out on read, network link dropped, etc.).

Any changes done to the elive.conf file require a restart of the Elluminate Live! Server service.

1. Try to reproduce the problem you are trying to troubleshoot. The output of what is occurring on the Elluminate Live! Server will be captured in the elive.log file.

2. If you were able to reproduce the problem, send an email to Elluminate Technical Support with the elive.log file attached. (See Table 17 for the location of this file on your operating system.)

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 108

Page 115: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

The licensemanager.log File The licensemanager.log file shows which license file is being loaded. Any errors in starting up the License Manager will be displayed here.

1. Try to reproduce the problem you are trying to troubleshoot. The output of what is occurring on the Elluminate Live! License Manager will be captured in the licensemanager.log file.

2. If you were able to reproduce the problem, send an email to Elluminate Technical Support with the licensemanager.log file attached. (See Table 17 for the location of this file on your operating system.)

The wrapper.log File The wrapper.log shows the status of the Elluminate Live! Manager on Windows, including any errors in starting up the Manager.

The wrapper.log file exists on Windows only. For debugging the Elluminate Live! Manager on a Solaris, Linux or Macintosh, use the catalina.out file.

To use the wrapper.log file, you must first turn on the debugger. Follow the steps below to enable the Elluminate Live! Manager debugger and try to reproduce the issue.

1. Stop the Elluminate Live! Manager service. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

2. Edit the manager.conf file to turn on the wrapper.log file.

a. Open C:\Program Files\ElluminateLive\common\wrapper\manager.conf

b. Search for wrapper.logfile.loglevel=ERROR and change the line to wrapper.logfile.loglevel=INFO

3. Start the Elluminate Live! Manager service. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

4. Try to reproduce the problem you are trying to troubleshoot. The output of what is occurring on the Elluminate Live! Manager will be captured in the wrapper.log file.

5. If you were able to reproduce the problem, send an email to Elluminate Technical Support with the following file attached:

C:\Program Files\ElluminateLive\common\wrapper\wrapper.log

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 109

Page 116: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 11 – Troubleshooting

The elm.log File The Elluminate Live! Manager log file shows the activity of the Elluminate Live! Manager (commands, error messages, etc.) on Windows. This file must be manually generated using the debugger. Follow the steps below to enable the Elluminate Live! Manager debugger.

The elm.log file is generated on Windows only. For debugging the Elluminate Live! Manager on Linux/Solaris and Macintosh, use the catalina.out file.

1. Stop the Elluminate Live! Manager service. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

2. Edit the manager.conf file:

Program Files\ElluminateLive\common\wrapper\

Set the loglevel assignment for the console and/or log file output to INFO.

a. For console output, the assignment should be the following:

wrapper.console.loglevel=INFO

b. For log file output, the assignment should be the following:

wrapper.logfile.loglevel=INFO

c. Save the file.

3. Edit the elmlogging.properties file:

Program Files\ElluminateLive\manager\tomcat\common\classes

a. Set the global logging level to the following:

level=INFO

b. Set the FileHandler global logging level to the following:

java.util.logging.Filehandler.level=INFO

c. Save the file

4. Restart the Elluminate Live! Manager service. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

5. Try to reproduce the problem you are trying to troubleshoot. The output of what is occurring on the Elluminate Live! Manager will be captured in the elm.log file.

6. If you were able to reproduce the problem, send an email to Elluminate Technical Support with the following file attached:

C:\Program Files\ElluminateLive\common\log\elm.log

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 110

Page 117: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 111

The catalina.out File The catalina.out file shows the activity of the Elluminate Live! Manager (commands, error messages, etc.) on Linux, Solaris and Macintosh.

1. Try to reproduce the problem you are trying to troubleshoot. The output of what is occurring on the Elluminate Live! Manager will be captured in the catalina.out file.

2. If you were able to reproduce the problem, send an email to Elluminate Technical Support with the catalina.out file attached. (See Table 17 for the location of this file on your operating system.)

Recovering Un-Transitioned Recordings If there is a restart of the Elluminate Live! Manager before a recording has migrated from the temporary folder to the permanent folder, the recording will remain in the temporary folder. This means that the recording(s) will not be listed in the Elluminate Live! Manager.

The folders listed below are the defaults provided during installation. If you did not use the defaults during installation, confirm your folder locations from within the Elluminate Live! Manager. Select Server Details from the Preferences page. See Elluminate Live! Server recordings export folder for the location of the temporary folder and Elluminate Live! Manager recordings import folder for the location of the permanent folder.

Windows

Temporary Folder

C:\Program Files\ElluminateLive\common\recordings

Permanent Folder

C:\Program Files\ElluminateLive\manager\tomcat\webapps\ROOT\WEB-

INF\resources\recordings

Linux & Solaris

Temporary Folder

/opt/ElluminateLive/common/recordings

Permanent Folder

/opt/ElluminateLive/manager/tomcat/webapps/ROOT/WEB-

INF/resources/recordings

Page 118: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Chapter 11 – Troubleshooting

Mac

Temporary Folder

/Applications/ElluminateLive/common/recordings

Permanent Folder

/Applications/ElluminateLive/manager/tomcat/webapps/ROOT/WEB-

INF/resources/recordings

Follow the steps below to restore any recording files that are not transitioned.

You will need a database tool to perform these steps.

1. For each recording, import the following information into the Recordings table in your database.

creationTime – this field can be left empty

recordingSize – you can get the size (bytes) from /ElluminateLive/common/recordings

meetingId – this can be found in the meetings table (meetingId)

meetingName – this can be found in the meetings table (Name)

recordingId – this can be found in /ElluminateLive/common/recordings

recordingData – (null)

openFlag – this corresponds to the privateMeeting parameter in the meetings table (if privateMeeting = false, then openFlag = true)

creationDate – this can be found in the Recordings Journal table (createdOn parameter)

version – 8.0

2. Copy the recordings file from the temporary folder to the permanent folder (pathnames listed above).

3. In the permanent folder, rename the recordings with the following naming structure: <recordingId>_recordingData.bin.

For example, rename

1136583279669_1136543285675.vcr

to

1136583279669_1136543285675_recordingData.bin

4. Restart the Elluminate Live! Manager service/daemon. (For instructions, see Start, Stop, or Restart the Daemons and Services on page 5.)

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 112

Page 119: © 2007 Elluminate, Inc. All Rights Reserved. · 2010-03-18 · Elluminate Technical Support is available through the following channels: Email support@elluminate.com Phone 1-403-204-7896

Elluminate Live! 8.0 with Elluminate Live! Manager 2.7 — Advanced Configuration Guide 113

5. Verify that the recordings appear in the Elluminate Live! Manager application.

a. Log in to the Elluminate Live! Manager application with a System Administrator or Application Administrator role.

b. Click on the Recordings tab. The recordings should appear in the list.

c. Click on the Recording link to launch and play back the recording.

6. Clean up the temporary folder and RecordingsJournal table.

a. Delete each appropriate .vcr file in the temporary folder (only those you have transitioned).

b. Delete any appropriate entries in the RecordingsJournal table in the database (only those you have transitioned).