The information in this Readme file pertains to Novell Messenger 2.2.
This release includes updates for the NetWare, Linux, and Windows Messenger software. The NetWare and Windows software is provided in one set of downloads; the Linux software, including the Linux/Mac client, is provided in a separate set of downloads.
The system requirements for Novell Messenger 2.2 are the same as those listed in the Novell Messenger Hardware and Software Requirements
in the Novell Messenger 2.2 Installation Guide.
Download the NetWare/Windows Novell Messenger 2.2 Administration compressed executable file for multi language (nm220_full_nlmwin_multi.zip) or for English only (nm220_full_nlmwin_en.zip) to a temporary directory on your NetWare or Windows server.
Extract the .exe file into a directory at the root of your local drive or to a network server drive that can handle long pathnames.
The compressed file contains directory paths that could exceed DOS limits.
In Windows, click
, then locate the directory where you extracted the administration files.Select the setup.exe file, then click to run the Messenger Installation program.
Click
, then click to accept the license agreement.Select
, then click .Follow the on-screen instructions provided in the Messenger Installation program to update the software.
For additional instructions, refer to the Novell Messenger 2.2 Installation Guide on the Novell Messenger 2.2 Documentation Web site.
In your Web browser, enter the IP address of the Novell Messenger Download page.
This is the IP address and port of the Messaging Agent. By default, the Messaging Agent port is 8300. For example, if you installed to a server with an IP address of 172.16.5.18, the Novell Messenger Download page would be http://172.16.5.18:8300.
Follow the on-screen instructions to download the client.
In Windows, click
to run the Messenger Installation program.Follow the on-screen instructions provided in the Messenger Installation program to install the software.
Download the Novell Messenger 2.2 Administration/Client compressed tar file (nm220_full_linux_multi.tar.gz) to a temporary directory on your Linux server.
The Novell Messenger administration/client RPMs include all languages, so there is no English-only download.
In a terminal window at your Linux server, change to the temporary directory, then use the following command to uncompress and untar the downloaded file:
tar -xz nm220_full_linux_multi.tar.gz
The result is a directory named nm220_full_linux_multi.
Change to the nm220_full_linux_multi directory.
Become root by entering su - and then the root password.
Use the following command to start the Novell Messenger Installation program:
./install.sh
Follow the on-screen instructions to create or update your Messenger system.
For additional instructions, refer to the Novell Messenger 2.2 Installation Guide on the Novell Messenger 2.2 Documentation Web site.
In your Web browser, enter the IP address of the Novell Messenger Download page.
This is the IP address and port of the Messaging Agent. By default, the Messaging Agent port is 8300. For example, if you installed to a server with an IP address of 172.16.5.18, the Novell Messenger Download page would be http://172.16.5.18:8300.
Follow the on-screen instructions to download the client.
Change to the directory where you downloaded the file.
Enter the following command:
sh ./nvlmsgr.bin
To start the Linux client after installation, click the Messenger icon on your Linux desktop.
In your Web browser, enter the IP address of the Novell Messenger Download page.
This is the IP address and port of the Messaging Agent. By default, the Messaging Agent port is 8300. For example, if you installed to a server with an IP address of 172.16.5.18, the Novell Messenger Download page would be http://172.16.5.18:8300.
Follow the on-screen instructions to download the client.
To start the Mac client after installation, click the Messenger icon on your Macintosh desktop.
If you use Cerulean Trillian Pro to communicate between instant messaging systems, a Novell Messenger plug-in is available at the Cerulean Studios Web site:
The Pidgin (formerly Gaim) open source instant messaging connector is available at the Pidgin Web site.
The Kopete open source instant messaging plug-in is available at the Kopete Web site.
Section 5.1, ConsoleOne Fails to Start on SLES 12 Because of Missing Dependency
Section 5.2, Extending the eDirectory 8.8.5 Schema When Using LDAP Mode on Linux
Section 5.3, Library Dependency on SUSE Linux Enterprise Server 11
Section 5.4, Case-Sensitive Passwords Do Not Work with eDirectory 8.8
Section 5.5, Encrypted Messenger Attributes in eDirectory 8.8
When running Messenger on SLES 12, ConsoleOne fails to start because the following dependency is missing:
libXtst6
Install the libXtst6 package, then proceed to run Messenger.
When installing Messenger with eDirectory 8.8.5 with LDAP mode on Linux, you must manually extend the eDirectory schema.
How you extend the schema depends on whether eDirectory is installed locally or remotely.
Choose direct mode, as described in Configuring Your Messenger System on Linux
in Installing a Novell Messenger System
in the Novell Messenger 2.2 Installation Guide.
Extend the schema using the Windows installer’s Configuring Your Messenger System on Linux
in Installing a Novell Messenger System
in the Novell Messenger 2.2 Installation Guide.
When running Messenger on SUSE Linux Enterprise Server (SLES) 11, you need to install the libstc++.so.5 or greater library.
If you try to connect to eDirectory 8.8 from Novell Messenger with a case-sensitive password, eDirectory 8.8 might not recognize the case-sensitive password. For information on how to enable case-sensitive passwords in eDirectory 8.8, see “How to Make Your Password Case-Sensitive” in the eDirectory 8.8 What’s New Guide.
If you are storing any encrypted Novell Messenger attributes in eDirectory 8.8, you cannot see these attributes in ConsoleOne until they are unencrypted.
When using some versions of OpenSuse, Messenger does not stay running after it is minimized.
To resolve this issue, install the following packages to OpenSuse:
libjpeg6-32bit-6.2.0-3.1
libjpeg6-6.2.0-3.1
When upgrading your Messenger client from Messenger 2.1 to Messenger 2.2, the auto-update does not initialize. You must manually install the Messenger 2.2 client on each client workstation where the Messenger client is being updated.
For information on how to manually install the Messenger client, see Installing the Messenger Client
in the Novell Messenger 2.2 Installation Guide.
Novell Conferencing provides support for the English, French, and German languages only. If you are using Novell Messenger to launch a Novell Conferencing meeting, as described in Using Novell Messenger with Novell Conferencing
in the Novell Messenger 2.2 Client User Guide, the language in which you are viewing Novell Messenger might not carry over to Novell Conferencing.
For example, if you are viewing Novell Messenger in Chinese and want to launch a Novell Conferencing meeting, your Conferencing meeting would be displayed in English.
For a list of the bugs that have been fixed since Novell Messenger 2.1, see the Novell Messenger 2.2 Bug List. You can look up the bug numbers in Bugzilla for more information about each bug.
For information about Novell Messenger 2.2, see the online product documentation: Novell Messenger 2.2 Documentation Web Site.
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2007-2010 Novell, Inc. All rights reserved. Permission is granted to copy, distribute, and/or modify this document under the terms of the GNU Free Documentation License (GFDL), Version 1.2 or any later version, published by the Free Software Foundation with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the GFDL can be found at http://www.fsf.org/licenses/fdl.html.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.