Preparing for Installation

wMobile Components

There are four (4) main components to wMobile:

wMobile

The wMobile component is the application itself. This component is the web application you view when you connect to wMobile from a web browser. wMobile is installed on the server running IIS.

Remote GoldMine Service

The Remote GoldMine Service provides communication between wMobile and GoldMine. The Remote GoldMine Service is always installed on the GoldMine server. This service is used for logins.

wMobile Manager Console

The wMobile Manager Console is a tool that provides administrators with the ability to customize wMobile’s menus, security and application settings. This application is always installed on the same server as wMobile.

wMobile E-mail Fetcher

The wMobile E-mail Fetcher is a Windows service used to scan for and download email headers from your POP3 or IMAP server.

PLEASE READ BEFORE STARTING INSTALLATION

1.	Verify IIS is installed.

2.	Verify ASP.NET 2.0 is installed.

Check the GM.INI file in the GoldMine Root directory and ensure that, if present, the ‘SYSDIR’ setting is set to a UNC path or a local path. wMobile will not be able to work if ‘SYSDIR’ contains the path of a network drive. For installations where users are using GISMO, commenting out the SYSDIR may be required in order for wMobile to work properly.

4.	In the case of a mapped drive or GISMO installation, it’s possible to simply remove the ‘SYSDIR’ setting. The setting can also be commented out so GoldMine will ignore its value by putting a ‘;’ at the beginning of the ‘SYSDIR’ line. For example: ;SYSDIR=G:\GoldMine

5.	In the case of a UNC path, you will need to change the service user for the Remote Login Service following the install of the Remote GoldMine Service. The user name must have read/write access to GoldMine’s network share.

6.	If required, the W-Systems Download Manager will install all of the prerequisites first and then install the application components. Save time by downloading and installing the prerequisites before installing wMobile.

7.	Microsoft SharePoint has caused problems with wMobile. Try to avoid installing wMobile on an IIS server with Microsoft SharePoint installed.

8.	Ensure that TCP Port 80 or TCP Port 443 has been redirected in your firewall to your web server.

9.	In Windows 2003 / IIS 6.0 configure the IIS Default Application Pool, Performance tab to NOT idle after 20 minutes. By default an application pool will be configured to idle after 20 minutes. This should be deselected as it will reduce performance on the wMobile application.