1.
Check the software
requirements and supported versions for:
• Exchange
• Kerio
• MDaemon
• Oracle
• Oracle Communications Unified Communications Suite (formerly Sun JCS)
• Scalix
• Zimbra
2.
Review the Enterprise Server Installation Guide
3.
Consider Hardware
Configuration
possibilities.
The NLES involves installation of three components:
• Database
• Web/HTTP
• Messaging
The three components may be installed on one, two or three separate servers depending on a variety of factors. Information to help you make these decisions can be found in the Installation Guide under System Architecture.
4.
Consider System
Requirements.
See the Installation Guide under System Requirements.
5.
Consider the use of
SSL with your Web/HTTP
Server.*
If you will be using SSL with your Web/HTTP Server, the following secure certificates have been tested and confirmed to work with all supported NotifyLink devices.
• VeriSign/RSA Secure Server CA: “Secure Site” or “Secure Site Pro”
• Thawte Server CA: “SSL Web Server Certificate”
* NotifyLink currently does not support SSL on Apache.
6.
Software
Prerequisites for NotifyLink Installation. Install English
versions only.
• On any server where a NotifyLink component will be installed, install one of the following:
o Windows Server 2008 R2 SP1,
o Windows Server ‡2008 with SP2,
o Windows Server *2003 R2 x64, or
o
Windows Server 2003
Apply all Windows Server updates as
well.
‡Setup instructions for Windows
2008 x64 ;
More information about Windows
Server 2008
*Setup instructions for Windows
2003 R2 x64
o The
NotifyLink Enterprise Server is also supported on any of the above
operating systems running as a virtual machine.
VMWare 3.0 or VMWare
vSphere 4.0/4.1 (recommended)
• On any server where the NotifyLink Messaging or Web components will be installed:
o Prior to or after the installation of NLES v4.8, users are advised to apply the Microsoft Visual C++ 2005 Redistributable Package. See Knowledge Base article for details.
• On the server where NotifyLink SQL Database will be installed, install one of the following:
o Microsoft SQL Server 2008 R2 SP1 (Standard Edition),
o Microsoft SQL Server 2008 R2 (Standard Edition),
o Microsoft SQL Server 2008 SP3 (Standard Edition),
o Microsoft SQL Server 2008 SP2 (Standard Edition),
o Microsoft SQL Server 2008 SP1 (Standard Edition),
o Microsoft SQL Server 2005 SP3 (Standard Edition) or
o Microsoft SQL 2008 Web Edition
Use Mixed Mode Authentication, as it is required for the NotifyLink SQL Server. Make note of the SA password.
• On the server where NotifyLink Web Component will be installed:
o
Install IIS OR
Apache.
Supported Microsoft
IIS versions 7.5, 7.0, or 6.0
Supported Apache versions – 2.2.x
On the server where NotifyLink Messaging Component will be installed:
-Install the GroupWise Client See step 1 for supported versions.
Note: Login once to activate.
-Install Novell Client only if you are going to register NotifyLink as a trusted application - Supported for GroupWise 6.5 or later.
Note: Login once with administrator credentials to activate.
•
Verify that WebDAV is enabled
PIM information is accessed using the WebDAV protocol. This protocol runs over HTTP and cannot be turned off, thus HTTP must be enabled for WebDAV to work. In addition, to use WebDAV to access Exchange, the HTTP server must have a virtual directory for Exchange, i.e. Exchange has to be exposed through the HTTP server.
Verify that WebDAV is enabled by entering the following address in a web browser:
<ip address of the mail server>:<port that is used for HTTP>/exchange
If you get the NT authentication prompt, WebDAV is enabled and PIM will be able to process.
On a server that best suits your configuration:
Download and install the Meeting Maker Sync Servlet. (See step 1 for supported version.)