TWiki . OpenPortal . ElluminatePortlet

Elluminate Portlet is a JSR-168-compliant portlet than can be deployed in any portal server(container) that supports JSR-168. This portlet lets users of Elluminate Live! server 7.0 to create, join, delete, and schedule meetings. The portlet requires the users to set login name, password, and elluminate server URL before they can communicate with an Elluminate Live Manager(ELM). The Portlet uses JAX-WS 2.0 APIs to communicate with ELM. Once set, these settings are stored in Portlet Preferences, and everytime the user logs into the portal, the portlet logs the user into Elluminate server, without the user entering the credentials, essentially achieving Single Sign On(SSO) like functionality.

The Portlet uses JAX-WS 2.0 APIs to communicate with ELM. The Portlet was tested with HTTP protocol communication between the Portlet and ELM. HTTPS protocol was not tested.

Installation (Deployment by Administrators)

Portlet container. The elluminate war file contains elluminate portlet class files, JSP files, and JAX-WS 2.0 libraries(in WEB-INF/lib directory). Before deploying the war file, some changes need to be made to portlet.xml file, in WEB-INF directory.

portlet.xml file contains the default settings to Elluminate Live! manager. The administrator has to set appropriate values to these settings for users to communicate to Elluminate Live server. Below are the settings that need to be changed.

Init Parameter ELM_URL

ELM_URL is the URL to Elluminate Live Manager to which the users need to connect to.

Init Parameter ELM_WS_URL

ELM_WS_URL is URL to Elluminate Web service. The value of ELM_WS_URL is usually ELM_URL + "/webservice.event".

Portlet Preference ElluminateServerURL^?

Portal server users have the option of connecting to the default Elluminate Server (ELM_URL) or another Elluminate server of their choice. The administrator has to set this to the value of ELM_URL. Users can change this value by using the edit option of Portlet

Once the above changes are made to portlet.xml file, update elluminate.war file with the updated portlet.xml file.

Make sure ElluminateConnectionType^? portlet preference is set to "none", as it is by default. Don't change this.

The portlet(elluminate.war) is now ready to be deployed. Follow Portlet containers instructions on how to deploy a Portlet.

Note: There are no changes needed on ELM side. However, please verify that configuration.xml file of ELM has setParticipantList command included in it. This was a bug with the 7.0 release.

Portlet usage (by Portal users)

Elluminate users can connect to Elluminate server through Elluminate Portlet. Users need to have portal server account before they can communicate with Elluminate server.

Once a user logs into the portal, the user should be able to see Elluminate Portlet. However, the user needs to set username, password, etc., before using the Portlet. This can be achieved by selecting the Edit button for the Portlet.

In the Edit window, the user has the option to select Elluminate Virtual Office communication and/or Elluminate Live Server communication. If Elluminate Live Office option is selected, the user has to enter the values of moderator link, participant link, and the email to CC.

If Elluminate Live Server option is selected, the user has to enter the values for Elluminate user name, password, and server URL . Server URL has default value set by the administrator. This only need to be changed if the user chooses to connect to a different server.

Once done entering the details, the user has to select the 'Finished' button to go back to the view mode of Portlet. If the user-entered details are accurate, the user will be presented with a GUI that, based on the selections made in the edit mode, will let the user show, create, delete, and join meetings and also join a virtual office. From then on, everytime the user logs into the portal server, Elluminate portlet will be available.

Issues

After the Portlet is deployed, the very first time a user selects the edit button of the portlet and enters the user's credentials, the Portlet may not present its GUI, even if the credentials are right. If the user selects the edit button again and enters the credentials, then the GUI should show up. This is an issue with SJS Portal Server's class loader. This only happens for the first user after the Portlet is deployed and doesn't happen again, so it's not a big issue.