GO!NotifyLink
Enterprise Server Installation Guide
Installing GO!NotifyLink Enterprise Server
This guide contains important configuration information that must be in place to successfully complete the GO!NotifyLink Enterprise Server installation and for proper functionality after installation. Please read through the entire guide before attempting to install or upgrade the Enterprise Server software. Note: If you are upgrading your GO!NotifyLink Enterprise Server (GO!NLES) system from the generic IMAP4 to one that supports Contacts, Calendar and Tasks (PIM), you must uninstall the Messaging Component and the Web/HTTP Component using Add/Remove Programs before running the GO!NLES installer.
GO!NotifyLink 1 Table of Contents
GO!NotifyLink 1
System Architecture 3 Single Server Installation ...... 3 Single Server Configuration Diagram ...... 4 Multiple Server Installation ...... 5 Multiple Server Configuration Diagram ...... 6 Meeting Maker Servlet Configuration ...... 7 Messaging Component Port Requirements ...... 7
System Requirements 8 Collaboration Suite System Requirements ...... 8 CommuniGate Pro System Requirements ...... 9 Exchange System Requirements ...... 9 FirstClass System Requirements...... 9 GroupWise System Requirements...... 10 Kerio System Requirements ...... 11 MDaemon System Requirements ...... 11 Meeting Maker System Requirements ...... 12 Mirapoint System Requirements ...... 12 Oracle Communications Unified Communications Suite Requirements ...... 13 Oracle System Requirements ...... 13 Scalix System Requirements ...... 13 Sun Java Enterprise System Requirements ...... 14 Zimbra System Requirements ...... 14 Mixing Collaboration Suites ...... 15 GO!NotifyLink System Requirements ...... 16 SQL Database Component Requirements ...... 16 Web/HTTP Component Requirements ...... 17 Messaging Component Requirements ...... 18
Server Installation 19 Download the GO!NotifyLink Enterprise Server Software ...... 19 Step 1 – SQL Database Component Installation ...... 21 Step 2 - Web/HTTP Server Component Installation ...... 23 Step 3 – Messaging Component Installation ...... 28 Step 4 - Apply Software Patches ...... 31 Additional GroupWise Step - Register Trusted Application ...... 32 Post Installation Tasks ...... 34 Disaster Recovery Recommendations ...... 35
System Architecture
GO!NotifyLink Message Flow. The GO!NotifyLink Enterprise Server (GO!NLES) continually checks the mail server for new mail and the PIM server for new calendar, contact, and task data addressed to Enterprise Server users. When new data is found it is stored in the GO!NotifyLink database (email must first meet filter and permissions criteria). From there it is delivered to the user’s device over the wireless network. The path from the wireless device to the recipient follows the same steps, only in reverse. Enterprise Server Components. The Enterprise Server is comprised of three components: - the SQL Database component - the Web/HTTP component - the Messaging component All three components may be installed on the same server or each component can be installed on a separate server. The architecture you choose will depend on system size and complexity. (See the System Requirements section.) It is recommended that the server(s) you install the components on be dedicated to the GO!NotifyLink Enterprise Server (GO!NLES) software. Configuration Models. There are two possible configuration models: Single Server Installation - Typical configuration suitable for general-purpose deployment where a single server meets all the requirements needed for installation. Multiple Server Installation - Deployment options for larger more complex deployments where a single server does not meet all the requirements needed for installation.
Single Server Installation SQL Database Component, Web/HTTP Component, and Messaging Component all on same server This architecture is typically used by organizations that wish to have one server dedicated to all components of the Enterprise Server. In most cases, the organization has allocated a separate server to house the components. This is the simplest installation scenario, however, because the individual components of Enterprise Server have varying resource requirements you must choose a server that meets the resource requirements of all three components. Advantages: Simplicity Disadvantages: A single server must meet all the pre-installation and configuration requirements; system resource use The main advantage of this configuration is its simplicity. Everything is located on the same server for a single point of access for administration and control. The disadvantages of this configuration are the demands it places on the server's system resources and the pre-installation and configuration needed. To use this model, the server housing the components must have both Microsoft SQL Server and IIS/Apache installed. In addition, the server must have a resolvable external server address and have port 80 open.
System Architecture 3 Single Server Configuration Diagram
More: Port Tables for Firewall Rules
Multiple Server Installation The multiple server configuration offers a more flexible deployment, allowing each of the Enterprise Server components to be installed onto servers configured specifically for that component. Each component can be installed to either a pre-existing server without further configuration, or to servers configured for the individual component. This is particularly useful in deployments where a single server cannot meet all the requirements for each of the Enterprise Server components. Advantages: Easier to implement security policies; easier to use existing server configurations Disadvantages: System maintenance on multiple servers.
There are several possible architectural configurations with a multiple server installation: Web/HTTP Component on separate server; Messaging and SQL Database Components on same server - This architecture is typically used when the server containing Microsoft SQL Server does not have a resolvable external server address. As a result a separate server with a resolvable external server address is needed for the Web component, while the SQL Database and Messaging components can be installed on the Microsoft SQL Server machine. SQL Database Component on separate server; Messaging and Web/HTTP Components on same server - This architecture is typically used when an organization already has Microsoft SQL Server installed on a server. They use the pre-existing instance of Microsoft SQL Server with the Enterprise Server database component, but do not wish to install the Web and Messaging components on the Microsoft SQL Server machine. SQL Database, Web/HTTP, and Messaging Components all on separate servers - This architecture is typically used by organizations that wish to have a separate server dedicated to each component of the Enterprise Server. There may already be in place, a separate Microsoft SQL Server machine and Web Server where the SQL Database component and Web/HTTP components can be installed. The Messaging component will be installed on a third server dedicated to the Enterprise Server's messaging services.
System Architecture 5 Multiple Server Configuration Diagram Multiple server configuration has several possibilities. The three GO!NotifyLink Enterprise Server components (SQL Database Component, Web/HTTP Component, and Messaging Component) can each reside on separate servers or two can be coupled on one server, while the third resides on another. See Multiple Server Installation for placement scenarios that may best fit your needs.
More: Port Tables for Firewall Rules
Meeting Maker Servlet Configuration For Meeting Maker users only. Where to put the Meeting Maker Sync Servlet The GO!NotifyLink to Meeting Maker interface requires Meeting Maker Sync Servlet and Apache Tomcat software. (See Meeting Maker System Requirements.) The Servlet and Apache must be installed on a server system OTHER THAN where GO!NotifyLink Enterprise Server components will be running. This may be the server where Meeting Maker is installed or another entirely separate server. Some things to consider. You may already have the required Apache Tomcat in the environment where you will run the Servlet. You do if: o You are running the Meeting Maker Connector for Outlook (MMCO) or o You are using the Meeting Maker HTML Client. If you DO NOT have Apache Tomcat, you must install it before you install the Servlet. See the GO!NotifyLink portal page for links to Sync Servlet installation resources.
Messaging Component Port Requirements
Port Requirements GO!NotifyLink Messaging Component to Email/PIM Servers Email Server Calendar Server Contacts Server Tasks Server CommuniGate Pro 143 or 993 143 or 993 143 or 993 143 or 993 Exchange 143 or 993 80 or 443 80 or 443 80 or 443 FirstClass 143 or 993 80 or 443 80 or 443 80 or 443 GroupWise 143 or 993 1677 1677 1677 Kerio 143 or 993 80 or 443 80 or 443 80 or 443 MDaemon 143 or 993 3000 or https port 3000 or https port 3000 or https port Meeting Maker 143 or 993 8080 or 8443 8080 or 8443 8080 or 8443 Mirapoint 143 or 993 80 or 443 80 or 443 80 or 443 Oracle 143 or 993 7779 or 4445 7779 or 4445 7779 or 4445 Oracle Beehive 143 or 993 7777 or 4443 7777 or 4443 7777 or 4443 Scalix 143 or 993 (CalDAV) 80 or 443 ------Sun 143 or 993 3080 or 4445 80 or 443 3080 or 4445 Sun CalDAV 143 or 993 8080 or 8443 ------Zimbra 143 or 993 80 or 443 80 or 443 80 or 443
System Architecture 7 System Requirements
Collaboration Suite System Requirements
Select the collaboration suite you are using for information on versions supported by GO!NotifyLink: CommuniGate Pro Exchange FirstClass GroupWise Kerio MDaemon Meeting Maker Mirapoint Oracle Communication Unified Communications Suite Oracle Scalix Sun Java Enterprise Zimbra
CommuniGate Pro System Requirements Supported CommuniGate versions (English): CommuniGate Pro (IMAP PIM) 5.4.5 CommuniGate Pro (IMAP PIM) 5.4.2 CommuniGate Pro (IMAP PIM) 5.3.13 CommuniGate Pro (IMAP PIM) 5.3.12 CommuniGate Pro (IMAP PIM) 5.3.8
Exchange System Requirements Supported Exchange versions (English version): Exchange 2007, SP3 Exchange 2007, SP2 Exchange 2003, SP2 Exchange 2000, SP3 Rollup 1
Note: Exchange 2007 is supported by GO!NotifyLink Enterprise Server, however, Super User/Administrator Access is not supported by Exchange 2007.
FirstClass System Requirements Supported FirstClass version (English version): FirstClass 11, SP3 FirstClass 11 FirstClass 10 Note: FirstClass Synchronization Services, which contain SyncML, must be running since GO!NotifyLink PIM synchronization is done via SyncML.
System Requirements 9 GroupWise System Requirements Supported GroupWise Server Versions (English version): GroupWise 2014 GroupWise 2012 GroupWise 8.0.2 HP3 GroupWise 8.0.2 HP2 GroupWise 8.0.2 HP1 GroupWise 8.0.2 GroupWise 8.0.1* *For GroupWise 8.0 and later, the GO!NotifyLink Messaging Component should be installed on machines running Windows Server 2003 or other more recent releases of Windows Server. See Messaging Component Requirements. *See also, GW version 6.5.6/8.0 compatibility issue described in GO!NotifyLink Knowledge Base article. GroupWise 7.0.4 GroupWise 6.5.6up2 The server should point to the POA. Pointing to the GWIA is not recommended.
Internet Addressing must be enabled for GroupWise to function properly with the GO!NotifyLink software. For more information on enabling this feature, please contact your GroupWise administrator.
GroupWise Client. In addition, GroupWise Client (English version) should be installed on the server where the GO!NotifyLink Messaging Component resides. Supported GroupWise Client versions are: 2012 8.0.2 8.0.1 7.0.4 6.5.6up2
Registering GO!NotifyLink as a Trusted Application. Please read Recommendations and Requirements in the section documenting registration of GO!NotifyLink as a trusted application.
Kerio System Requirements Supported Kerio version (English version): Kerio Mail Server (WebDAV) 7.4.1 Kerio Mail Server (WebDAV) 7.4.0 Kerio Mail Server (WebDAV) 7.3.0 Kerio Mail Server (WebDAV) 7.2.3, 7.2.3 P1 Kerio Mail Server (WebDAV) 7.2.2 Kerio Mail Server (WebDAV) 7.2.1 Kerio Mail Server (WebDAV) 7.2 P1 Kerio Mail Server (WebDAV) 7.1.4, 7.1.4 P1 Kerio Mail Server (WebDAV) 7.1.3 Kerio Mail Server (WebDAV) 7.1.2, 7.1.2 P1 Kerio Mail Server (WebDAV) 7.1.1 Kerio Mail Server (WebDAV) 7.0.2 P1
MDaemon System Requirements Supported MDaemon version (English version): MDaemon 12.5.5 MDaemon 12.5.0 MDaemon 12.0.4 MDaemon 12.0.3 MDaemon 12.0.1 MDaemon 11.0.3 MDaemon 11.0.0
System Requirements 11 Meeting Maker System Requirements Supported Meeting Maker versions (English version): Meeting Maker version 8.8.2 / Meeting Maker Sync Servlet 8.8.0 Meeting Maker version 8.8.1 / Meeting Maker Sync Servlet 8.8.0 Meeting Maker version 8.8.0 / Meeting Maker Sync Servlet 8.8.0 For the GO!NotifyLink to Meeting Maker Interface: Meeting Maker Sync Servlet corresponding to the collaboration suite version used (see above). Apache Tomcat 5.5.9 or 6.0* Java Versions o Sun J2SE 5.0 or J2SE 6.0 o Sun J2SDK 1.5 or J2SDK 1.6 Intel Pentium IV processor or better *The Meeting Maker Servlet installation guide states that Meeting Maker Sync Servlet was tested and verified against these versions, but newer versions may work as well. Memory requirements for the servlet will vary based on the amount of data it is handling. It is recommended that you allocate as much memory to the servlet as the server allows (512 MB to 1 GB if possible). An average of 20 MB of hard drive space for each user is also needed. See System Architecture: Meeting Maker Servlet Configuration for recommendations on servlet configuration.
NOTE: As Meeting Maker is a collaboration suite dedicated exclusively to PIM processing (calendar, contact, and task data), any information on email in this guide refers to messages processed through your elected email system.
Mirapoint System Requirements Supported Mirapoint versions (English version): Mirapoint Message Server 4.4.4 (supported with GO!NotifyLink v4.10) Mirapoint Message Server 4.3.3 Mirapoint Message Server 4.3.2 Mirapoint Message Server 4.3.1 Mirapoint Message Server 4.2.3 Mirapoint Message Server 4.2.2 Mirapoint Message Server 4.1.10 Mirapoint Message Server 4.1.9
NOTE: Mirapoint Message Server should be configured to operate in the Server Mode, rather than the Email Mode in order to process meeting invitations to successfully.
Oracle Communications Unified Communications Suite Requirements (Formerly Sun Java Systems Communication Suite or Sun JCS)
Supported Oracle Communications Unified Communications versions (English version): Oracle Communications Unified Communications Suite 7 Update 5 (supported with GO!NotifyLink Enterprise Server v4.9.0 Patch 1 or greater) Oracle Communications Unified Communications Suite 7 Update 2) Oracle Communications Unified Communications Suite 7 Update 1
Oracle System Requirements Supported Oracle versions (English version): Oracle Beehive (SyncML) Release 2.0.1.7.0 Oracle Beehive (SyncML) Release 2.0.1.6.0 Oracle Beehive (SyncML) Release 2.0.1.5.0 Oracle Beehive (SyncML) Release 2.0.1.4.0 Oracle Beehive (SyncML) Release 2.0.1.3.0 Oracle Beehive (SyncML) Release 1.5.1.5.3 Oracle Collaboration Suite 10g Release and corresponding OCAS versions: 10.1.2.4.7
Scalix System Requirements Supported Scalix version (English version): Scalix Server (CalDAV) 11.4.6 Note: Scalix versions 11.4 offer the use of the CalDAV protocol for Scalix calendar servers. Future versions may employ the CalDAV protocol for tasks and contacts as well.
System Requirements 13 Sun Java Enterprise System Requirements See also Oracle Communications Unified Communications Suite Requirements.
Supported Sun Java Versions (English version): Sun Java Communications Suite 7 (JCS 7) (Also known as Oracle Communications Unified Communications Suite 7) o Messaging Server 7.3 o Calendar Server 6.3 (WCAP) or 7.0 (CalDAV) o Convergence 1u3 1.0
Sun Java Communications Suite 6 (JCS 6) o Messaging Server 7.0 o Calendar Server 6.3 o Communications Express 6.3
Sun Java Communications Suite 5 (JCS 5) o Messaging Server 6.3 o Calendar Server 6.3 o Communications Express 6.3
Zimbra System Requirements Supported Zimbra versions (English version):
Zimbra Collaboration Suite (SOAP) 7.2.0 (Network Edition) Zimbra Collaboration Suite (SOAP) 7.1.3 (Network Edition) Zimbra Collaboration Suite (SOAP) 7.1.2 (Network Edition) Zimbra Collaboration Suite (SOAP) 7.1.1 (Network Edition) Zimbra Collaboration Suite (SOAP) 7.1.0 (Network Edition) Zimbra Collaboration Suite (SOAP) 7.0.1 (Network Edition) Zimbra Collaboration Suite (SOAP) 7.0.0 (Network Edition) Zimbra Collaboration Suite (SOAP) 6.0.16 (Network Edition) Zimbra Collaboration Suite (SOAP) 6.0.14 (Network Edition) Zimbra Collaboration Suite (SOAP) 6.0.13 (Network Edition) Zimbra Collaboration Suite (SOAP) 6.0.12 (Network Edition) Zimbra Collaboration Suite (SOAP) 6.0.10 (Network Edition) Zimbra Collaboration Suite (SOAP) 6.0.9 (Network Edition) Zimbra Collaboration Suite (SOAP) 6.0.8 (Network Edition) Zimbra Collaboration Suite (SOAP) 6.0.6 (Network Edition) Mixing Collaboration Suites Installing GO!NotifyLink for use with more than one collaboration suite
GO!NotifyLink Enterprise Server (GO!NLES) accommodates the use of multiple mail and PIM server platforms. It is possible, therefore, to use one platform for Email processing and another for PIM processing. You might even choose to have more than one PIM platform. (Example: Scalix for calendar, Exchange for contacts and tasks, etc.) Here are some things you will want to do prior to setting up such a system: Read the sections in Pre-installation Guide documenting each collaboration suite. Check the version(s) of each collaboration suite supported by GO!NotifyLink. Versions supported Check for any special system requirements the products may have. System requirements Make sure corresponding ports to each PIM / Email server are open. Port Chart Be aware that you need only install the GO!NotifyLink Enterprise Server software once. The product contains one process that can serve different mail/pim systems.
System Requirements 15 GO!NotifyLink System Requirements The GO!NotifyLink Enterprise Server consists of three components: SQL Database Component Web/HTTP Server Component Messaging Server Component The following sections outline the installation requirements for each component. Note: Minimum requirements may vary depending on the factors that make up your environment. See the Pre-Installation Guide: System Hardware Recommendations
SQL Database Component Requirements ‡Windows Server 2012 R2 ‡Windows Server 2008 with SP2 ‡Windows Server 2012 *±Windows Server 2003 R2 x64 or ‡Windows Server 2008 R2 SP1 ±Windows Server 2003 Use English versions. Apply all Windows Server updates as well. ‡Setup instructions for Windows 2008 x64 or 2012 ; More Windows Server 2008 information *Setup instructions for Windows 2003 R2 x64; ±Microsoft Redistributable for Windows Server 2003 The GO!NotifyLink Enterprise Server is also supported on any of the above operating systems running as a virtual machine. Recommended: VMWare 3.0 or VMWare vSphere 4.0-5.1 or Hyper-V on Windows 20008/2012 servers
32-bit Intel Xeon processor or better
Multiple-Server Setup (components on separate servers) Single-Server Setup (all components on a single server) 1 GB RAM (minimum) 2 GB RAM (minimum)
Multiple-Server Setup (components on separate servers) Single-Server Setup (all components on a single server) 10 GB± free hard drive space (minimum) 10 GB± free hard drive space (minimum) ± More space may be required depending on number of ± More space may be required depending on number of users and amount of email and PIM data. users and amount of email and PIM data. Microsoft SQL Server 2014 (Standard Edition) Microsoft SQL Server 2012 up to SP1 (Standard Edition) Microsoft SQL Server 2008 R2 SP1 (Standard Edition) Microsoft SQL Server 2008 R2 (Standard Edition) Microsoft SQL Server 2008 SP3 (Standard Edition) Microsoft SQL Server 2008 SP2 (Standard Edition) Microsoft SQL Server 2008 SP1 (Standard Edition) Microsoft SQL Server 2005 SP4 (Standard Edition) Microsoft SQL Server 2005 SP3 (Standard Edition) or Microsoft SQL 2008 Web Edition Use English versions
Use Mixed Mode Authentication, as it is required for the GO!NotifyLink SQL server. Make note of the SA password. If you are installing the Web/HTTP and/or the Messaging Component(s) on the same server as the SQL Database Component, we recommended you restrict the amount of system resources that Microsoft SQL Server uses. You can accomplish this by adjusting the min server memory and max server memory options in SQL Server 2005, 2008, or 2012.
Web/HTTP Component Requirements ‡Windows Server 2012 R2 ‡Windows Server 2012 ‡Windows Server 2008 R2 SP1 ‡Windows Server 2008 with SP2 *Windows Server 2003 R2 x64 or Windows Server 2003 Use English versions. Apply all Windows Server updates as well. ‡Setup instructions for Windows 2008 x64 or 2012 ; More information about Windows Server 2008 *Setup instructions for Windows 2003 R2 x64 The GO!NotifyLink Enterprise Server is also supported on any of the above operating systems running as a virtual machine. Recommended: VMWare 3.0, VMWare vSphere 4.0-5.1, or Hyper-V on Windows 20008/2012 servers
32-bit Intel Xeon processor or better
Multiple-Server Setup (components on separate servers) Single-Server Setup (all components on a single server) 1 GB RAM (minimum) 2 GB RAM (minimum)
Multiple-Server Setup (components on separate servers) Single-Server Setup (all components on a single server) 50 MB free hard drive space 3 GB free hard drive space
Microsoft IIS OR Apache Supported Microsoft IIS versions: English versions 8, 7.5, 7.0 or 6.0 Supported Apache versions: 2.2.x PHP, Version 5.3.17 is distributed with the GO!NotifyLink Web/HTTP Component. Note: This will overwrite any existing installation of PHP. Therefore, it is recommended that you do NOT install the Web/HTTP Component on a server with other PHP websites.
Port 80/443 (http/https) inbound and outbound must be open The Web/HTTP Component contains a high-speed messaging gateway that is accessed by devices supported on high-speed cellular networks or fixed wireless networks. During installation of the Web Component you will be prompted for the internal and external server addresses associated with the server where you are installing. The external server address must be accessible from the Internet in order for high-speed devices to use the messaging gateway. Test this after installation by entering http://
Using SSL with your web component* The following secure certificates have been tested and confirmed to work with all supported GO!NotifyLink devices: Verisign/RSA Secure Server CA: We are using their "Secure Site" certificate Thawte Server CA: We are using their "SSL Web Server Certificate"
* GO!NotifyLink now supports SSL on Apache. See Knowledge Base article for Apache configuration requirements.
System Requirements 17
Messaging Component Requirements ‡Windows Server 2012 R2 ‡Windows Server 2012 ‡Windows Server 2008 R2 SP1 ‡Windows Server 2008 with SP2 *Windows Server 2003 R2 x64 or Windows Server 2003 Use English versions. Apply all Windows Server updates as well. ‡Setup instructions for Windows 2008 x64 or 2012 ; More information about Windows Server 2008 *Setup instructions for Windows 2003 R2 x64 The GO!NotifyLink Enterprise Server is also supported on any of the above operating systems running as a virtual machine. Recommended: VMWare 3.0 or VMWare vSphere 4.0-5.1 or Hyper-V on Windows 20008/2012 servers
32-bit Intel Xeon processor or better
Multiple-Server Setup (components on separate servers) Single-Server Setup (all components on a single server) 1 GB RAM (minimum) 2 GB RAM (minimum)
Multiple-Server Setup (components on separate servers) Single-Server Setup (all components on a single server) 50 MB free hard drive space 3 GB free hard drive space
Server Installation
Enterprise Server Installations Installation of the GO!NotifyLink Enterprise Server consists of the download and installation of three components. The sequence for installing all three components on a single server is as follows: 1st Install the SQL Database Component 2nd Install the Web/HTTP Server Component 3rd Install the Messaging Server Component If you are installing the components on multiple servers, you will need to run through the installation of each component one at a time on their respective servers. See System Architecture for more on single vs. multiple server installation. Upgrades Stop all of the GO!NotifyLink services before proceeding if you are upgrading. Please read the GO!NotifyLink Upgrade Instructions before you proceed with an upgrade installation. Note: If upgrading your GO!NotifyLink Enterprise Server (GO!NLES) system from the generic IMAP4 to one that supports Contacts, Calendar and Tasks (PIM); you must uninstall the Messaging Component and the Web/HTTP Component using Add/Remove Programs before running the GO!NLES installer.
Follow the steps below in the order they appear.
Download the GO!NotifyLink Enterprise Server Software Before you Begin Have the password of the Windows user account you are logged in with ready to enter during the installation. The username and password will be used to create the Windows services needed to run the application.
1. From a web browser enter http://notifylink.notify.net . 2. Under Downloads select New Server Installation. Review the Installation Instructions on the screen. 3. Enter your name, company and email address, then select Download.
Server Installation 19 4. To begin the installation, select the Install Products button.
Launch page Start by installing the SQL Database component
You are now ready to install the GO!NotifyLink Enterprise Server components.
Step 1 – SQL Database Component Installation Before you Begin Supported versions of Microsoft SQL Server are: 2005 with SP 3; 2008 with SP1, SP2, SP3, R2, R2 SP1; or 2012 up to SP1 Note: Microsoft SQL Server 2000 with SP4 is supported only for those upgrading to GO!NotifyLink Enterprise Server version 4.7.x from an older version. All new installations, as well as upgrades to versions 4.8.x or later, will require one of the SQL Server versions listed above. Upgrades: Before you begin an upgrade of the existing database, STOP all of the GO!NLES Services and web services (IIS or Apache). If you are using SQL Server 2005, you should enable TCP before you begin. In SQL Server Configuration Manager, select SQL Server 2005 Network Configuration > Protocols for MSSQLServer, and enable TCP/IP
1. Select the SQL Database button, and then click Install. (Not necessary if you chose “Install All 3 Components.”) 2. Answer Yes at the popup dialog to begin running the GO!NotifyLink SQL Installer. 3. Read through the Welcome screen and click Next. 4. Read the License Agreement carefully and select 'I accept the License Agreement' to continue. Click Next to display the Readme Information. Read this information carefully. 5. Click Next to view the Destination Folder dialog. Choose your Destination Folder for the Enterprise Server software, and then click Next. You can change the drive, but leave the ProgramFiles/NLES path. This is required so that, in the future, you can run the GO!NotifyLink Patch Installer to apply software updates.
Server Installation 21 6. At the SQL Server Information screen, enter the following: From the drop-down list select the SQL Server to which you will install the database. This allows you to install to the local server or a remote server. It will add the required Enterprise Server database to the server's SQL Server Database. Enter the sa password defined at the installation of SQL Server. Create a username and password for the SQL Server login. Jot it down, as the Messaging and Web installers will prompt for this username/password. This will be used by the GO!NotifyLink components to access the database. Upgrades: Database login credentials will default to the current username and password when upgrading.
Click Next > to finish the SQL Database Component installation. When it is completed, you will see a screen that reads "The SQL Database Component has been installed/upgraded successfully!" Note: Several warning messages appear near the completion of the Database Component installation. This is expected behavior and the messages can be ignored. EX: Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'CheckForPolicyDiffsByClass'. The stored procedure will still be created.
Administrator’s Tip: Changing Database Login Password The password is encrypted for security purposes. Should you wish to change the database password after installation, you must contact Globo Mobile Technologies Technical Support. A technical support representative must decrypt, change the value of, and re-encrypt the password, then change in the registry.
Proceed with Step 2 – Web/HTTP Server Component Installation Step 2 - Web/HTTP Server Component Installation Before you Begin PHP, Version 5.2.17 is distributed with the GO!NotifyLink Web/HTTP Component. This will overwrite any existing installation of PHP. Therefore, it is recommended that you do NOT install the Web/HTTP Component on a server with other PHP websites.
1. Select the Web/HTTP Component button, and then click Install. (Not necessary if you chose “Install All 3 Components.”) 2. Read through the Welcome screen and click Next. 3. Read the License Agreement carefully and select 'I accept the License Agreement' to continue. Click Next to display the Readme Information. Read this information carefully. 4. Click Next to view the Destination Folder dialog. Choose your Destination Folder for the Enterprise Server software, and then click Next. You can change the drive, but leave the ProgramFiles/NLES path. This is required so that, in the future, you can run the GO!NotifyLink Patch Installer to apply software updates. 5. If you have both IIS and Apache running on this server, GO!NotifyLink will prompt you to choose the web server on which you would like to install GO!NotifyLink. After selecting, click Next. Note: GO!NotifyLink Enterprise Server (GO!NLES) must be run on port 80. If another website is on the server, you must either change the port of the other web site, or install GO!NLES elsewhere.
Server Installation 23 6. At the Internal Gateway Information screen, enter the Internal and External Server addresses associated with the server where you are installing the Enterprise Server Web/HTTP Component. The maximum length of these Server address fields is 50 characters. It is recommended that you use a DNS name as opposed to an IP address for the external server address. The Web/HTTP Component contains a high-speed messaging gateway that is accessed by devices supported on high speed cellular networks or fixed wireless networks. Examples of supported mobile device models are listed on the Device Client Applications pages.
Check the Proxy Server checkbox if your system requires a proxy server to connect to the Internet. Then click Next > to proceed to the Proxy Information screen to enter the server information.
Proxy Server Information Screen
Click Next > to continue.
After the installation: The external server address must be accessible from the Internet in order for high-speed devices to use the messaging gateway. Test this after installation by entering http://
7. At the SQL Server Login Information screen, enter the username and password that was defined during the SQL Database installation. This will be filled in by default if you are installing the Web/HTTP component on the same server as the SQL Database Component. Click Next >.
8. At the last Web/HTTP Component Setup screen, enter the following: From the drop-down, select the name of the SQL Server running the Enterprise Server SQL Database (which was installed in Step 1). Enter the correct password for the Windows administrator account that is shown. If you are using Microsoft IIS, select the web site to which you are installing. By default, the Enterprise Server Web/HTTP Component will be installed to the "Default Web Site." Note: Install to a web site that is not currently in use or create a new web site with IIS/Apache before installation (so that it appears in the drop-down list).
Server Installation 25 You also have the option to set a default authentication password. If you do not check the box and make an entry, a password is randomly generated for each user.
The Authentication Password must be 8 characters in length, and can only contain the characters A-Z, a-z, 0-9, and the following: # * ( ) - + / ' " @ ? ! , .
This feature allows for an easy transition to the device authentication capabilities, but is a less secure option than randomly generating authentication passwords. Some administrators find it easier to give out a default password to all users rather than having the computer generate a different password for each user (which would then have to be communicated to each user). You can then instruct users to change their own passwords from the GO!NotifyLink Client Web (General > Security) before they register their devices. This authentication password for each user can be found under Edit User Device in the GO!NotifyLink Administrative Web console.
Click Next > to finish the Web Component installation. When it is completed, you will see a screen that reads "GO!NotifyLink Enterprise Web/HTTP Component has been successfully installed." 9. At the prompt to restart the system, answer Yes to reboot the server if you will be installing the final component on a different machine. If you will be installing the Messaging component on this machine, you can wait and reboot at the end.
A Note About Integrated Windows Authentication During installation or upgrade of the web component, GO!NotifyLink virtual directories inherit security settings from their parent level in the IIS directory tree. If the root level security settings were ever altered to enable Integrated Windows Authentication, that setting is passed down to GO!NotifyLink’s HWP virtual directory at installation/upgrade. This type of security, however, should not be used for the HWP virtual directory, since devices accessing the directory do not support Integrated Windows Authentication. It is, therefore, necessary for you to verify that Integrated Authentication is NOT enabled for the HWP virtual directory. Also, should you create a website for GO!NotifyLink instead of using the Default Web Site, do NOT enable Integrated Windows Authentication. Verify that Integrated Windows Authentication is Disabled: 1. Open the IIS manager and expand the Default Web Site or the GO!NotifyLink website you created. 2. Right click on the HWP virtual directory and select Properties. 3. You will see a window with multiple tabs. Select the Directory Security tab. 4. Select the Edit button in the “Anonymous access and authentication control” section. On the Authentication Methods screen: Anonymous Access MUST be selected. In the Authenticated access section, Integrated Windows authentication must NOT be selected. (Basic Authentication can be selected.) Note: Unless Integrated Authentication is required for another web site, you can make these changes at the parent level so that security settings will be as needed for future GO!NotifyLink upgrades.
Proceed with Step 3 – Messaging Component Installation
Server Installation 27 Step 3 – Messaging Component Installation Before you Begin Upgrades: When upgrading the Messaging Component, the registry settings will be saved. This is done in the SaveSettings program. The settings are restored in the messaging installer.
1. Select the Messaging Component button, and then click Install. (Not necessary if you chose “Install All 3 Components.”) 2. Read through the Welcome screen and click Next. 3. Read the License Agreement carefully and select 'I accept the License Agreement' to continue. Click Next to display the Readme Information. Read this information carefully. 4. Click Next to view the Destination Folder dialog. Choose your Destination Folder for the Enterprise Server software, and then click Next. You can change the drive, but leave the ProgramFiles/NLES path. This is required so that, in the future, you can run the GO!NotifyLink Patch Installer to apply software updates.
5. The PIM Service Login Information screen is displayed as shown below. Enter the password for the Windows administrator account that you are currently logged in under and click Next. NOTE: The following services need an Administrator account in order to function properly. AttachmentService Monitor Service AvailableUsers PimService GleanerController
6. The SQL Server Login Information screen is displayed as shown below. The username and password are pre-populated if you are installing on the same machine as the previous components. If you are installing the Messaging component on a different server, enter the values that were selected during the SQL Database installation. Click Next >.
Server Installation 29 7. This Database Permissions screen is displayed as shown below. If you would like to run the SQL Report monitoring job, select it and enter the sa password. The permissions displayed will be granted for the job if selected. If it is not selected, the sa password is not needed. Click Next >.
8. At the last screen you will be prompted for the following server configuration information: Default SMTP Server - Enter the IP or DNS of the SMTP Server to be used by default for the Enterprise Server. The Default SMTP Server is the server that will be used to send outbound SMTP notifications from the Enterprise Server, unless another SMTP server has been specified for a user. This default SMTP Server must be accessible from the server where the Enterprise Server Messaging Component is installed. It must also allow for relaying of SMTP email to Internet email accounts from the server where the Enterprise Server Messaging Component is installed. Default SMTP Port - The port used to access the Default SMTP Server. NOTE: GO!NotifyLink will attempt to make the connection to the specified SMTP Server via the specified SMTP Port. If this connection fails, you will be prompted that there was an error connecting.
SQL Server - Select from the drop-down the name of the SQL Server containing the Enterprise Server SQL Database (which was installed in Step 1). Administrator Email Address - Enter the email address of the GO!NotifyLink Enterprise Server administrator. The administrator will receive email regarding system monitoring errors, warnings, and notices of software updates and new releases.
Click Next > to finish the Messaging Component installation. This will take several seconds as features are updated and installed, and product information is registered. When it is completed, click OK and you will see a screen that "Messaging Component has been successfully installed." 9. Click Finish to complete the Messaging Component installation. 10. If you are prompted to restart the system, answer Yes to reboot the server.
You are now ready to apply software patches.
Step 4 - Apply Software Patches If patches are available, proceed with the following: Open Internet Explorer and enter http://notifylink.notify.net/ Click on Software Patches. New installations and upgrades of On Premise systems should apply only the latest patch (at the top of the list). Bundling partners upgrading an On Demand system must apply all patches (oldest to newest).
GroupWise users who wish to register GO!NotifyLink as a Trusted Application, proceed to Additional GroupWise Step.
Server Installation 31 Additional GroupWise Step - Register Trusted Application Complete this step only if you are using a GroupWise server, and you wish to register GO!NotifyLink as a Trusted Application. If you are upgrading and you previously registered GO!NotifyLink as a trusted application, you DO NOT have to register again.
Recommendations and Requirements Make sure you have updated the GO!NotifyLink SQL Database, Web/HTTP, and Messaging components before you register. The machine that the registration application is run on must have Novell Client installed on it. Once GO!NotifyLink is registered as a trusted application, you can remove Novell Client. Note: There is no 64 bit version of the Novell Client for Windows Server 2003. If you have installed GO!NotifyLink on Windows Server 2003, a workaround solution is to install Trusted Application from another server that has the Novell Client already installed. Please reference Knowledge Base article for instructions. It is recommended that you register GO!NotifyLink as a Trusted Application on the machine where you have installed the GO!NotifyLink Messaging component. You must enable multi-PIM processing by increasing the number of MaxThreads to 3 in the registry’s GO!NLES PIMService. See Enable Multi-PIM Processing in the GO!NotifyLink Administrative Web Guide for instructions.
Registration Instructions 1. Log into Novell so that you have administrative rights to the primary GroupWise domain. 2. Run the installer on the machine where you have installed the GO!NotifyLink Messaging component. 3. Select Register Trusted Application and then click Register.
Troubleshooting Tips Errors. If you press the Register button and get an error that the registration application could not be run, open up a Windows explorer window and browse to the GO!NotifyLink application directory, C:\Program Files\Notifylink Enterprise Server (by default). Ensure that the file, RegisterTrustedApp.exe exists. Double-click this file. If it still does not launch, you should be given a more specific error as to why the application could not be run. The registration application will prompt you for a path to the primary domain. Provide this path and press the “Register Trusted App” button.
If the application registers successfully, an application key will be encrypted and stored in the GO!NotifyLink database. A trusted app with the name “GO!NotifyLink” will be registered with your primary GroupWise domain. It should be viewable via ConsoleOne under Tools > GroupWise System Operations > Trusted Applications.
Authorization Failures. Since the trusted application must be registered with the primary domain, it may take some time for the trusted application to be recognized by secondary domains. If your GWIA is on a secondary domain and you are experiencing authorization failures from our services after registering as a trusted application, you may want to disable GO!NotifyLink from using the trusted app functionality for a short period of time. (See "Toggle Trusted App ON / OFF" below.)
Server Installation 33 Toggle Trusted App ON / OFF When you register as a trusted application, GO!NotifyLink will automatically switch the trusted app flag to “ON”. If you would like to make a change to this value, log into the GO!NotifyLink Administrative Web console. If Trusted App has been registered and a GroupWise mail server has been added, you can toggle between ON and OFF in Server Administration.
To Remove the Trusted Application Registration Uninstalling the GO!NotifyLink software will not automatically unregister GO!NotifyLink as a trusted application. To remove GO!NotifyLink as a trusted application you must go to ConsoleOne under Tools > GroupWise System Operations > Trusted Applications. Select GO!NotifyLink and press Delete.
Post Installation Tasks Once the three GO!NotifyLink Enterprise Server components are installed and the patches have been applied, you are ready to access the Administrative Web console and begin configuring the GO!NotifyLink environment.
Post installation tasks include: mail, PIM, LDAP, and SMTP server configuration entering end user licenses setting IT Policy rules installing GO!NotifyLink Device Application software on user devices See Configuring a New GO!NotifyLink Server in the Enterprise Server Administrative Web Guide for a checklist. Device Application software can be found at http://notifylink.notify.net/deviceclients.asp
Accessing the Administrative Web Console To access the Administrative Web console type the following in a web browser: http://
Disaster Recovery Recommendations
Daily Backup Backup of the NLES_IMAP4_POP3* database is extremely important. A daily backup is recommended. Backups should minimally be done on a weekly basis. In addition, you should be following a backup schedule where backup media (Tape, CD, etc.) is taken off premises. Refer to Microsoft documentation for information on how to set up automated backups.
* POP3 is part of the NLES database name only as legacy. It is a protocol that is no longer supported.
High Availability Setup
High Availability refers to the ability of a system or component to limit or avoid disruption when a component fails.
Setting the GO!NotifyLink Enterprise Server up with High Availability provides a customer with redundancy should the GO!NotifyLink Enterprise Server experience failure due to factors that might include, hardware failure, Operating System failure, or an unexpected stoppage of a service.
Method of Providing High Availability
GO!NotifyLink Enterprise Server (GO!NLES) itself is not configurable for High Availability. Therefore, a secondary, or Stand-by, server must be utilized. This server will only be used in the event of the primary server malfunctioning, and should be installed with the exact same hardware specifications as the primary server.
Configuring a Second GO!NotifyLink Enterprise Server
Active Server
Server Configuration o Web / Messaging Components - These two components should be installed on one server. o Database Component - This should be installed separately, and in a cluster.
Stand-by Server
Server Configuration o Database / Web / Messaging Component -Install all 3 components on this one server -Stop all NotifyLink Services, and set them to “manual” startup Items from the Active Server to have copied on to the stand-by Server o Exported copy of the SSL Certificate installed o Copy of the exported registry settings for GO!NLES -My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Notify Technology Corporation o Copy of the NotifyLink Enterprise Server directory -As GO!NLES Patches are released and applied to the Active Server, an updated copy of the GO!NLES Directory should be placed on the stand-by
Server Installation 35 Failing over to the Stand-by Server
In the event of a failure on the Web / Messaging component when the Stand-by Server must be activated, the following is a list of steps that should be completed in order to get the GO!NLES Server functioning:
Take the Active Node offline (unplug the NIC) Change the IP Address of the Stand-by Server to the IP Address of the failed component Change the Server Name to the name of the failed component Import the SSL Certificate Import the registry settings Copy the GO!NLES directory to the appropriate directory on the new server o By default, located at C:\Program Files\NotifyLink Enterprise Server Change the ODBC Connection to point to the database cluster o Start > Administrative Tools > Data Sources > System DSN Tab > NLSQLServerDSN o Server = IP of the Database Cluster > Next o Login ID / Password = the Database User created when setting up GO!NLES > Next o Next > Finish o Test the Data Source o Click OK all the way out Start all NotifyLink Services, set to “automatic” startup Verify that the GO!NLES Admin Console can be accessed by the External IP Address, and that logs are updating as expected
Licensing
GO!NotifyLink Licensing o GO!NotifyLink Licensing is not affected by this configuration Microsoft Licensing o Please contact a Microsoft Server Specialist for information