Novell is now a part of Micro Focus

My Favorites

Close

Please to see your favorites.

Adding the Novell Collaboration Portlets to Teaming

This document (7001209) is provided subject to the disclaimer at the end of this document.

Environment

Products:
Novell Teaming 1.0
Novell Teaming 1.0 Support Pack 1
Novell Teaming 1.0 Support Pack 2
Novell Teaming 1.0 Support Pack 3
Novell Teaming + Conferencing
Novell GroupWise 7 Support Pack 2
Novell GroupWise 7 Support Pack 3
Novell SUSE Linux Enterprise Server 10
Novell SUSE Linux Enterprise Server 10 Support Pack 1
 
Configuration:
Novell Teaming is installed correctly.
Novell Teaming is working on both HTTP and HTTPS ports.

Situation

Purpose:
The purpose of this document is to cover the steps required to add the Novell Collaboration Portlets for Liferay to an existing Novell Teaming 1.0 system.  These portlets give you the ability to add a GroupWise Calendar and GroupWise Mail portlet to Teaming 1.0.

Resolution

The Novell Collaboration Portlest have a dependancy on Sun Jave 1.5 JDK and will not work properly with the IBM Java 1.5 JDK that ships with SLES 10.
 
Also, the Novell Collaboration Portlets for GroupWise have been updated to use the SOAP protocol to access the POA directly to get the calendar and mailbox information.  However, these portlets require that the SOAP protocol be SSL encrypted.
 
1.  Enable the SOAP protocol on the POA.  See the Novell GroupWise Documentation: GroupWise Administration Guide in the section on " Configuring User Access to the Post Office ".  
2.  Add the SSL certificates to the POA and enable SSL on the SOAP port.  See the Novell GroupWise Documentation: GroupWise Administration Guide in the section on " Server Certificates and SSL Encryption ".
3. Download the Novell Collaboration Portlets " NovellCollabPortletsLiferay-1.1.war " file from the developer.novell.com/wiki.
4. Install the Novell Collaboration Portlets into the Teaming 1.0 system by coping the downloaded file NovellCollabPortletsLiferay-1.1.war to the <icecoredata>/liferay/deploy directory.  The <icecoredata> directory varies by installation.  A default install on Linux is /home/icecoredata.  A default install on Windows is c:\icecoredata.
After the file is copied into this directory the Liferay/Teaming server software will automatically pick it up, extract it, and install the various components into the system.  You can verify that the installation is done my monitoring the catalina.out log.
5.  Add the Novell Collaboration Portlets to a users Teaming portal page.  Login as a user to the Teaming system.  Click on the Add Content link on the top right hand of the portal page.  Expand the Novell section and you will see several new portlets that can be added including the GroupWise Calendar and GroupWise Mail portlets.
6.  Once the portlets have been added to the portal page they will need to be customized to add the GroupWise Userid, password, IP address for the POA, SOAP port (usually 7191), and the companies GroupWise Webaccess url.  This is done by clicking on the Preferences icon (looks like a piece of paper and a pencil) in the top right hand corner of the portlet.  Click the OK button and the portlet should connect to the POA, login and retrieve the data.

NOTE:  Default preference settings for the portlets can be set in the portlet.xml file found in the /opt/icecore/liferay-portal-tomcat-5.5-jdk5-4.3.0/webapps/NovellCollabPortletsLiferay-1.1/WEB-INF directory.  However, end users will still have to modify the preferences to add their GroupWise userid and password.

+ Introduction to Novell Teaming

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7001209
  • Creation Date:22-AUG-08
  • Modified Date:27-APR-12
    • NovellGroupWise
      Vibe

Did this document solve your problem? Provide Feedback