Server Install  -  eFile  -  Admin  -  Client  -  Troubleshooting

Back to Scalix Download page

For Archived versions of this Userguide - Click Here

Enterprise Server Installation Guide
for Scalix


Note: Please read through this entire guide before attempting to install or upgrade the Enterprise Server software. It contains important installation and configuration information that must be in place for the Enterprise Server to function properly after installation.

Note: If upgrading your NLES system from the generic IMAP4 to one that supports Contacts, Calendar and Tasks (PIM), you must uninstall Messaging Component and Web Component using Add/Remove Programs before running the NLES-Scalix installer.


Part 1 - What is the Enterprise Server?

For wireless device users, the NotifyLink Enterprise Server provides support for a variety of wireless networks including cellular networks such as CDMA/1XRTT, GSM/GPRS, iDEN, and all fixed wireless networks using 802.11x technology. For “wired” device users, the network-based NotifyLink solution allows the mobile user to synchronize their device independent of their Mail and PIM (calendar/contact/task data) Servers’ location. Notify has designed the NotifyLink solution for IT organizations that desire centralized management and support for their mobile user needs. With the NotifyLink solution, organizations can easily support their growing mobile workforce while providing a migration path from wired to wireless device usage. Notify also offers the NotifyLink solution “on-demand” for organizations that prefer not to allocate IT resources for mobile user management. Notify is committed to providing answers for organizations seeking a single solution for enterprise mobile device synchronization of email, calendar, contact and task information.

E-mail Using NotifyLink, emails are synchronized to the user’s mobile device. Email, replies, and forwarded email sent from the mobile device are synchronized with the user’s Mail Server “Sent” folder. If the user deletes an email on the mobile device, NotifyLink automatically places that email in the “Trash” folder on the user's Mail Server. If the user reads an email on the device that email is marked as Read on the server. NotifyLink provides email users with a platform specific smart client, which is loaded on the mobile device. The NotifyLink smart client provides the user with the same email folders that exist on the Mail Server: Inbox, Sent Folder, Draft Folder, Outbox, Trash folder. Emails are sent from the user’s account to the mobile device. Once on the mobile device, the user is able to open the email, read it and then perform any number of operations including replying, forwarding, and even deleting the email.

  • Message Filtering Filtering is a critical capability in a mobile messaging environment. NotifyLink supports a robust set of filters that can be controlled by the administrator or mobile end-user. The filter engine supports a powerful set of rules and conditions to control the flow of messages sent to the mobile device. NotifyLink supports the use of multiple filters.
  • Attachment Support Notify supports attachment download and upload for mobile devices. In addition, NotifyLink provides user configurable attachment support regarding information about the number of attachments, names of the attachments, and sizes of the attachments. This information is made available as part of the email displayed on the mobile device. NotifyLink also supports the ability to forward an attachment to any other email user.
Mobile Calendar, Contacts, and Tasks NotifyLink provides synchronization of a user's Calendar, Contacts* and Tasks both to and from their mobile device. Regardless of whether the information is initiated from the mobile device or at the user’s Mail or PIM Server, the information is transmitted, keeping personal calendars continually up to date at both the server level and the mobile device level. The user performing an initial sync on the mobile device activates NotifyLink’s synchronization functionality. Meeting invitations are also supported to and from the mobile device. Users can accept or decline meeting invitations from the mobile device. Users may also initiate a meeting request from the mobile device. NotifyLink uses the native calendar, contact, and tasks applications on the various supported mobile devices.
* Note: With NotifyLink Enterprise Server version 4.0 and later, we send contact changes from the server. In older versions (less than 4.0), users set (from the device) an auto contact sync on a cycle, as the server does not send contact changes to the device automatically.

Encryption and Key Management NotifyLink supports both Triple DES and the latest Advanced Encryption Standard (AES). AES is a Federal Information Processing Standard (FIPS), specifically, FIPS Publication 197, that specifies a cryptographic algorithm for use by U.S. Government organizations to protect sensitive, unclassified information. The AES key size: 192 and 256 bits. In decimal terms, this means that there are approximately: 6.2 x 1057 possible 192-bit keys. Many security systems will almost certainly use both Triple DES and AES.

Top

Part 2 - System Architecture

This guide explains the setup procedures for the Enterprise Server.

The Enterprise Server 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 arrives it is sent to the wireless network (email must meet filter and permissions criteria first), where it will be delivered to the user’s wireless device. The notification is received at the device and read by the user. The path from the wireless device to the recipient follows the same steps, only in reverse.

The Enterprise Server involves the installation of three components - the Database SQL component, the Web component and the Messaging component. All three components may be installed to the same server or each component can be installed to a separate server, depending on the system architecture you choose.

Below are the two possible scenarios for configuring the Enterprise Server. The scenario you choose will determine which server each component of the Enterprise Server will need to be installed to.

  • Single Server Installation - Typical deployment 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

Database SQL Component, Web Component and Messaging Components all on same server - This architecture is typically used within organizations that wish to have one server dedicated to all components of the Enterprise Server. In most cases the organization has allocated a "new" server to house the components.

Advantages: Simplicity
Disadvantages: A single server must meet all the pre-installation and configuration requirements; System resource use

The most simple installation scenario is to install all three components of the Enterprise Server onto a single server. 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. 

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 demand that it places on the server's system resources and the pre-installation and configuration needed. To use this model, it is required that the server to be used have both Microsoft SQL Server and IIS installed. Further the server must have a resolvable external Server address  (if you are using High Speed devices) and have port 80 open.  

Multiple Server Installation

Advantages: Easier to implement security policies; easier to use existing server configurations
Disadvantages: System maintenance on multiple servers. 

The Multiple Server Installation configuration makes for 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 needed, 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. 

The possible system architectures in the Multiple Server Installation scenario are described below. 

  • Database SQL Component, Web Component and Messaging Components all on same server - This architecture is typically used within organizations that wish to have one server dedicated to all components of the Enterprise Server. In most cases the organization has allocated a "new" server to house the components.

  • Database SQL Component and Messaging Component on same server, Web Component on separate server - This architecture is typically used when the server containing Microsoft SQL Server does not have a resolvable external Server address for use with High Speed devices. As a result a separate server with a resolvable external Server address is needed for the Web component to be installed to, while the Database SQL and Messaging components can be installed to the Microsoft SQL Server. machine. 

  • Messaging Component and Web Component on same server, Database SQL Component on separate server - This architecture is typically used when an organization already has Microsoft SQL Server installed to a server and wish to use the pre-existing instance of Microsoft SQL Server with the Enterprise Server, but do not wish to install the Web and Messaging components to that same Microsoft SQL Server machine.     

  • Database SQL Component, Web Component and Messaging Components all on separate servers - This architecture is typically used within organizations that wish to have a separate server dedicated to each component of the Enterprise Server. In some cases the organization may already have in place a separate Microsoft SQL Server machine and Web Server where the Database SQL component and Web components will be installed to, and the Messaging component will be installed to a third server dedicated solely to the Enterprise Server's messaging services.

See System Requirements for needed software versions.

Section 1 - Server Configurations


Single Server Configuration
          All components on one server                      

 

Two Server Configuration-
Web component on one server, Messaging and Database SQL component on another server

 

Two Server Configuration-
Web and Messaging components on one server, Database SQL component on another server

 

Three Server Configuration-
All components on separate servers

Top

Part 3 - System Requirements

Section 1 - Scalix System Requirements


PRE-NLES INSTALLATION STEPS

Scalix Server version 9.2.1.13, 10 or 11 is required.

A Scalix super-user account must be created from the command line on the Scalix Server. Use the following steps and replace <nladmin> and <password> with your chosen values. Note that <nladmin> must not contain spaces. <mailnode> has to be an existing mail node on the same Scalix mail server where wireless users will reside.

  1. omaddu -n <nladmin>/<mailnode> -p <password>
  2. ommodu -o <nladmin> -c+mboxadmin

On the server that will be running the NotifyLink Messaging component, you must have an English version of Outlook 2000 (in Corporate/Workgroup mode), Outlook XP/2002 (SP1 or higher), or Outlook 2003 installed as the default Mail program. Outlook must be installed with "Collaboration Data Objects" component (this is not installed by default during the standard installation). To install Collaboration Data Objects Component:

  • Run installation disk of Microsoft Office
  • Choose "Custom Install" option
  • Under the "Outlook" menu, select "Collaboration Data Objects"
  • Run the installer and follow instructions on the screen

On the server that will be running the NotifyLink Messaging Component, you must install the Scalix Connect for Wireless.

NotifyLink System Requirements

Note: NotifyLink does not currently support Virtual Server Installations.

The Enterprise Server for Scalix requires three components to be installed - the Database SQL, Web Server and Messaging Server components. Requirements vary depending on the component being installed. These components and their respective requirements are as follows:

Section 2 - SQL Database Component Requirements


  • Windows 2000 Server or Windows 2003 Server - English version
  • 32-bit Intel Pentium IV processor or better
  • 512 MB RAM NOTE: Minimum 1 GB RAM if all components are on the same server
  • 2GB free hard drive space  
  • Microsoft SQL Server 2000 with Service Pack 3, English version
    • Note: If you are using SQL Server 2005 or SQL Server 2005 Express, please refer to the special instructions and requirements section listed under Using SQL Server 2005 on the NotifyLink portal page.
    • Note: When installing SQL make sure that you select SQL server authentication.
    • Note: Microsoft SQL Server is an Enterprise Application. Therefore, if you are planning to install the Web and/or Messaging Components on the same server as the SQL Component, it is recommended that you restrict the amount of system resources that Microsoft SQL Server will be allowed to use.  This is accomplished in the following way:
      1. Using the Microsoft SQL Server Enterprise Manager, right click on the SQL Server corresponding to the name of the SQL Server where you will be installing the SQL Component. The list of SQL Servers is located within SQL Server Groups in the SQL Server Enterprise Manger hierarchy.
      2. Right Click on the SQL Server name and select Properties.
      3. Select the Memory Tab and change the settings from "Dynamically Configure SQL Server memory" to "Use a fixed Memory Size". Move the slide bar to the fixed size desired. It is recommended that you leave at least 100MB of RAM free for use by the Messaging and Web Components.

    • Note: During the installation of Microsoft SQL Server a default user is created with the username of sa and a blank password. It is recommended that this password be changed for security. You can use the Enterprise Manager to change this within Microsoft SQL Server:

      In Enterprise Manager:

      • Log on with 'sa' and blank password
      • Expand 'Security'
      • Click the 'Logins' icon
      • Right click the 'sa' account and choose 'Properties'
      • Fill in the 'Password' field and click 'OK'
      • Confirm the password in the prompt and click 'OK'
      • Close the dialog

Section 3 - Web Component Requirements


  • Windows 2000 Server or Windows 2003 Server - English version
  • 32-bit Intel Pentium IV processor or better
  • 512 MB RAM NOTE: Minimum 1 GB RAM if all components are on the same server
  • 50MB free hard drive space  
  • Microsoft Internet Explorer 5.01 or later
  • Microsoft IIS OR Apache
    • Supported Microsoft IIS versions - English version 5 or version 6.
    • Supported Apache versions - 2.0.x.
  • PHP version 5.0.4 is distributed with the NotifyLink Web Component. This will result in an existing installation of PHP being overwritten.
  • Port 80 inbound/outbound open.
    • Note: The Web 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 Blackberry, Treo, and Windows Mobile 5 devices are listed on the Device Client pages.
      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. You can test this after installation by entering http://<YourExternalServerAddress>/hwp/get.asp into a web browser located outside of your Intranet. If the page is not found then the external server address is not accessible.
  • Using SSL with your web component - The following 2 secure certificates have been tested and confirmed to work with all supported NotifyLink devices:
  • Acquiring SSL Certificates:

Section 4 - Messaging Component Requirements


  • Windows 2000 Server or Windows 2003 Server - English version
  • 32-bit Intel Pentium IV processor or better
  • 512 MB RAM Minimum 1 GB RAM if all components are on the same server
  • 50MB free hard drive space  
  • Microsoft Internet Explorer 5.01 or later

Important: Backup of data is extremely important. We suggest that, minimally, you should be using at least RAID level 1 (mirroring of drives). Additionally, you should be following a backup schedule where the backup media (Tape, CD, etc.) is taken off premises, in case of catastrophic failure. Additional software agents may be required, depending upon your backup software. 

Part 4 - Server Installation

Section 1 - Enterprise Server Installation/Upgrade


NOTE: If this is an upgrade stop all of the NotifyLink services before proceeding.

Installation is quite simple and is completed through the installation of three components from the installation medium - the Database SQL, Web Server and Messaging Server components. The installation medium is available on CD or via download.

The sequence for installation of the Enterprise Server is as follows:

  1. Installation of the Database SQL Component (from the Installation Medium)
  2. Installation of the Web Server Component (from the Installation Medium)
  3. Installation of the Messaging Server Component (from the Installation Medium)

Note: During the installation of the Enterprise Server components you will be prompted for the password of the Windows user you are logged in with. This username and password will be used to create the Windows services needed to run the application.

Installation from the Installation Medium:

To begin the installation process from the installation medium, either insert the CD into the server's CD-ROM drive or download the CD to the server's local drive and select launch.exe from the CD's root directory.

Note: If you are not installing each of the three components to the same server, you will need to run through the installation of each component one at a time on each server.

Select the Install Products button from the installation medium to begin the installation process.

The following screen will be displayed.

In the bottom left, you may select "Install All 3 Components". This will install the SQL Database, followed by the Web Server, followed by the Messaging server. When choosing this method, the steps below still apply, but the choosing of each product followed by clicking "Install" do not. Alternatively, you may choose to install each product individually, this method is described in detail below.

Important Note: If you are upgrading NotifyLink Enterprise server, DO NOT use the "Install All 3 Components" button.

Step 1 - Database SQL Component Installation

Select the SQL Database button from the installation medium and select the install button. 

Important Note: If you are upgrading NotifyLink Enterprise server, you must first STOP all of the NLES Services. You may then select the SQL Database button and select "Yes" when prompted to upgrade the existing database.

Read the License Agreement carefully and select 'I accept the License Agreement' if you accept the agreement and wish to continue. Click Next to display the Readme Information dialog. Read this information carefully. Click Next to view the Destination Folder dialog.

Choose your Destination Folder for the Enterprise Server software. After choosing a folder, click Next > .

Select the location of the database to be installed:

  • Local - SQL Database component will be installed on the local computer.
  • Remote - SQL Database component will be installed on a remote computer.
If installing the database to an instance other than the default, enter this then click Next > .

You will be prompted for what SQL Server you want to install to. This allows you to install to a server other than local and will add the required Enterprise Server database to the server's SQL Server Database.

Database Credentials Change- A user can now change the database password to something other than NLSQLServerDSN. The Messaging and Web Installers should prompt for the Username and Password to access the database. On upgrades, the default values should be used NLSQLServerDSN and NLSQLServerDSN. Once installed, you may change the database password. To change it, it must be changed in two places. First change it on the actual database. In Enterprise Manager, go toSecurity->Logins. Then double-click NLSQLServerDSN. This will allow you to change the database login password. You then must also change this value in the registry. The key to change is under our registry root and the value to change is in the ConnectString. Once both changes are made, restart all services so that they pick up the new changes.

Continue on and when the Database SQL installer is finished, you will see a screen that reads "The database has been installed/upgraded successfully!."

Step 2 - Web Server Component Installation

Select the Web Server button from the installation medium and select install . This will set up the Enterprise Server Web Server on the server. When the installation begins you will see the Welcome screen. After reading through the Welcome Screen, click Next > . This takes you to the License Agreement screen.

Read the License Agreement carefully and select 'I accept the License Agreement' if you accept the agreement and wish to continue. Click Next to display the Readme Information dialog. Read this information carefully. Click Next to view the Destination Folder dialog.

Choose your Destination Folder for the Enterprise Server software. After choosing a folder, click Next > . If you have both IIS and Apache running on this server, NotifyLink will prompt you to chose which web server you would like to install NotifyLink to. After selecting, click Next >.

You will now be prompted for the Internal and External Server addresses associated with the server where you are installing the Enterprise Server Web Component. The maximum length of these Server address fields is 50 characters. The Web 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 Blackberry, Treo, and Windows Mobile 5 devices are listed on the Device Client pages.
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. You can test this after installation by entering http://<YourExternalServerAddress>/hwp/get.asp into a web browser located outside of your Intranet. If the page is found, you will see the text Error: Invalid Parameters. This means the external server address is accessible. However, if the page is not found then the external server address is not accessible.

NOTE: If you are going to use SSL or an all Wi-Fi network then you will NOT be able to use an IP address for the external server address, you will have to use a DNS name.

After confirming the Server addresses are correct, click Next > .  

The SQL Server Login Information screen is displayed, as shown above. Enter the username and password that was selected during the Database SQL installation. Click Next >.

First, select from the drop-down the name of the SQL Server containing the Enterprise Server SQL Database (which was installed in Step 1). Next, enter the correct password for the domain administrator account that is shown. Then, select from the drop-down box the web site to which you wish to install. The Enterprise Server Web Component will be installed to the "Default Web Site" by default. 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).

This screen of the installer also offers the option to set a default authentication password or a randomly generated password for each user. This feature was added to allow for an easy transition to the new device authentication capabilities. Some administrators find it easier to give out the default password ('password') to each user rather than having the computer randomly generate a different password for each user. If you choose for the authentication password to be randomly generated, the password for each individual user will be different. This authentication password for each user will be found under Edit User Device in the Notify administrative console.

Click Next > to finish the Web Component installation. When the Web Component installer is finished, you will see a screen that reads "Web Server has been successfully installed."

IMPORTANT UPGRADE NOTE: When upgrading to the latest version of the NotifyLink Enterprise Server, you should be aware of the security settings for IIS that the Notify Installer puts down.  If you have changed the default security settings in IIS for the Notify Web Site, you will need to go back into IIS and change the security settings back to how they were prior to the upgrade.  By default the Notify Web Installer sets the admin and client virtual directories under the Notify Web Site to Integrated Windows Authentication.  The HWP virtual directory will use the security setting from the root website.  We do not support Integrated Windows Authentication for the devices, so the HWP virtual directory does NOT support this type of security.  So, if the HWP virtual directory has inherited Integrated Windows Authentication from the root folder, the devices will not work.  In this case, you should go into IIS and make sure that Integrated Authentication is NOT selected, basic authentication may be selected.  Log into IIS, expand the Notify Web Site, right-click on the HWP virtual directory and go to Properties.  From Properties, select the the Edit button at the top, the next screen will be the location where you need to make the authentication changes.  At the top, Anonymous Access MUST be selected.  At the bottom, Integrated Windows Authentication CANNOT be selected, but Basic Authentication CAN be selected.

Step 3 - Messaging Component Installation

Messaging registry settings saved when upgrading- 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.

Select the Messaging Server button from the installation medium and select install . This will set up the Enterprise Server Messaging Services on the server. When the installation begins you will see the Welcome screen. After reading through the Welcome Screen, click Next > . This takes you to the License Agreement screen.

Read the License Agreement carefully and select 'I accept the License Agreement' if you accept the agreement and wish to continue. Click Next to display the Readme Information dialog. Read this information carefully. Click Next to view the Destination Folder dialog.

Choose your Destination Folder for the Enterprise Server software. After choosing a folder, click Next > . The PIM Service Login Information screen is displayed, as shown below. Enter the password for the Windows account that you are currently logged in as and click Next >.

NOTE: The PIM service and Attachment service need an Administrator account in order to function properly.

The SQL Server Login Information screen is displayed, as shown above. If the username and password are not pre-populated, enter the values that were selected during the SQL Database installation. Click Next >.

At this screen you will be prompted for the following information:

Server Configuration

  • SMTP Server - Enter the domain name for the SMTP server to be used for the Enterprise Server. The SMTP Server is the server that will be used to send outbound SMTP notifications from the Enterprise Server. This selected SMTP Server must be reachable from the server where the Enterprise Server Messaging Component is installed. The selected SMTP Server must also allow for relaying of SMTP email to Internet email accounts from the server where the Enterprise Server Messaging Component is installed.
  • SMTP Port - The port used to access the SMTP Server.
  • 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 NotifyLink Enterprise Server administrator.

NOTE: NotifyLink will attempt to make the connection to the specified SMTP Server via the specified SMTP Port. If this connection fails, you will will be prompted that there was an error connecting.

NOTE: Users who have BlackBerry 85x/95x data only devices must change the "NLES ResponseMailClient" service to have "Startup Type: Automatic" and start the service.

Once this information is entered, click Next > to complete the installation of the Messaging installer. This will take several seconds as features are updated and installed, and product information is registered. Once complete, click OK and you will see a screen that reads "Messaging Server has been successfully installed." Click Finish to complete the installation.

Step 4 - Device Client Installation

Refer to the user guide for each individual device for instructions on how to install each device client.   The device client installers can be downloaded from here: http://notifylink.notify.net/ota.asp 

Top

Section 2 - UPGRADE USERS ONLY


UPGRADE USERS - Download detailed Instructions (file type .doc)

Top

Section 3 - Password Default


After installing or upgrading is complete, start the Administrative Utility to administer the Enterprise Server application. To log into the Administrative console you will type the following in a web browser http://<Server Address>/admin. Where the <Server Address> is the IP or DNS of the machine where the NotifyLink Enterprise Server Web component was installed. When starting the Administrative Utility, you will be prompted for a username and password. By default, the username is 'admin' and the password is 'admin'. These are case-sensitive and must be lower-case. Windows 2003 users - PLEASE READ HERE FIRST.

After you have logged into the Administrative Utility, you can add, remove or edit Administrative logins and perform other administrative tasks. This is detailed in the Enterprise Server Administrator Guide .

Top