GoldMine Install Guide PDF

Transcription

GoldMine
Enterprise Edition
(GMEE)
Installation Guide
REV 65-6-21-10
ii Notices
Copyright  2007 - 2010 FrontRange Solutions USA Inc. All Rights Reserved.
Use of this software and its related user documentation IS subject to the terms and conditions of the applicable End-User License Agreement (EULA), a copy of which is found in
the user documentation FOLDER included in the software. You must agree to the terms
and conditions of the EULA in order to use this software. If you do not agree to the terms
and conditions of the EULA, return the unused software within thirty (30) days of purchase
IN ITS UNOPENED PACKAGE to the place from which you obtained it for a refund (minus
any restocking fee).
WARNING: The software described in this manual and its related user documentation are
protected by copyright law. In no event, shall any part of the related user documentation
be copied, reproduced, distributed, transmitted, stored in a retrieval system, or translated
into any language, without the express written permission of FrontRange Solutions USA
Inc.
This product includes software developed by The Apache Software Foundation http://
www.apache.org/). Please read the LICENSE files present in the root directory of this distribution.
FrontRange Trademark Information
The following are trademarks of FrontRange Solutions USA Inc. and/or its affiliates in the
United States and/or other countries: FrontRange Solutions®, FrontRange™, GoldMine®,
GoldSync®, GoldMine® Answer Wizard™, GoldMine® Management Intelligence™, GoldMine® Manager’s Console™, iGoldMine™, HEAT®, HEAT® Service & Support™, HEAT®
PowerDesk™, iHEAT™, HEAT® Self Service™, HEAT® Manager’s Console™, HEAT®
Answer Wizard™, HEAT® Quick Start Wizard™, InfoCenter®, Automated Processes™,
First Level Support®, enteo®, DeviceWall®, Centennial Discovery®, Discovery Dashboard®, MicroAudit®, SAM™ and other FrontRange products and brands.
Other Trademark Information
Microsoft products, brands and trademarks, including Microsoft, Windows, Windows
Server, Windows Vista, SQL Server, and Internet Explorer, are the property of Microsoft
Corporation in the United States and/or other countries.
Other products and brands are the trademarks of their respective owners or companies.
Contact FrontRange Solutions USA Inc. at our Web site: www.frontrange.com
GoldMine Enterprise Edition (GMEE)
Table of
Contents
Introduction
Welcome to GMEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii
Audience and Expertise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii
Contact Us . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Support Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Installation Prerequisites
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Provided Third-Party Software Components . . . . . . . . . . . . . . . . 1-1
Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Web Application Server* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Client Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Outlook Add-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Lotus Notes Add-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Compatibility Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Key for Compatibility Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Server Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Installation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Administrative Installation Checklist . . . . . . . . . . . . . . . . . . . . . . 1-12
End-User Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Server Installation
iv
Table of Contents
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Importing the Application Server License File . . . . . . . . . . . . . . 2-11
Updating Your Host MAC Information . . . . . . . . . . . . . . . . . . . . 2-12
Adding Additional Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Assigning the MAC address in a Virtual Environment . . . . . . . 2-14
Adding Connections in Windows 2008 . . . . . . . . . . . . . . . . . . . . 2-14
Application Database Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Loading the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Client Installation
Information Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Smart Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Click-Once Deployed Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Configuring Clients Using Three-tier Connections . . . . . . . . . . . 3-9
Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Disconnected Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Desktop Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Outlook Integration Add-In Installation . . . . . . . . . . . . . . . . . . . . . . 3-17
Lotus Notes Integration Add-In Installation . . . . . . . . . . . . . . . . . . . 3-20
Prerequisite Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Upgrading GMEE
Upgrade Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Feature Enablement Utility Overview . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Pre-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Upgrading from v6.0.7 GMEE Foundation . . . . . . . . . . . . . . . . . . . . . 4-4
Upgrade Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Creating an External Database Connection . . . . . . . . . . . . . . . . . . . . . 4-6
Using the Feature Enablement Utility . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Handling Upgrade Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Viewing Upgrade Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Resolving Upgrade Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Viewing Upgrade Wizard Log Files . . . . . . . . . . . . . . . . . . . . . . . 4-15
Table of Contents v
Post-Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Knowledge Management Installation
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Business Process Configuration
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Business Process Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Business Process Service Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Business Object Web Service Tab . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Notification Web Service Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Business Process Engine log and configuration files . . . . . . . . . . . . . 5-5
Schema Files that can be changed by customers . . . . . . . . . . . . . . 5-5
Configuring User Account for the BPService Windows Service . . . 5-7
BPService MSMQ Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
FSMTService Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Messaging Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Running BP Engine on a Separate Machine . . . . . . . . . . . . . . . . . . . . 5-11
Knowledge Management Configuration
Knowledge Management Server Configuration . . . . . . . . . . . . . . . . . 6-1
Configuring GMEE
Auto Deploy (ClickOnce) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Configuring Microsoft Distributed Transaction Coordinator (MS DTC)
7-10
Installation Guide
vi
Table of Contents
Introduction
Welcome to GMEE
GoldMine® Enterprise Edition (GMEE) is the latest Customer Relationship
Management solution from FrontRange Solutions, Inc. and the award winning
GoldMine® product line. It offers a complete, modular approach that helps Sales
and Marketing organizations reduce costs, drive revenue and improve overall
customer interactions.
GMEE is designed with an innovative technology to provide better
configurability and flexibility, including an inclusive dashboard and analytics
platform to provide easy access to customer information. It is built with
interaction management capabilities that pull together all disparate pieces in
order to create a complete, integrated solution. This capability allows
organizations to be more responsive to their customers’ needs, capture more new
customers, and derive increased revenue from existing customers, all while
keeping down the costs.
viii
Introduction
About this Guide
This guide provides the requirements and basic procedures for installing
and configuring GMEE.
IMPORTANT: For detailed instructions on any of the procedures mentioned in
this guide, please refer to online Help by selecting Help>Help Topics.
Audience and Expertise
The information in this guide is intended for System Administrators who
will configure and use the features of GMEE.
This material assumes that users have a fundamental working knowledge
of computers and a basic understanding of databases and the Microsoft
Windows operating system. It also assumes that users have a working
knowledge of FRS Foundation and FRS Administrator.
Document Conventions
Example
Description
File>>Print
Menu bar commands (in this example, select
File on the menu bar, then select Print in the
drop-down menu)
The Select a Data Source
dialog box appears.
Dialog boxes and menu items in bold
OK
Button names
Note
Additional information
CAUTION/WARNING
Critical information to prevent functionality or
data loss

Reference to another topic or resource
Contact Us ix
Contact Us
Support Site
FrontRange Solutions can answer your technical support questions about
GoldMine Enterprise Edition (GMEE) and other applications. Visit:
http://www.frontrange.com/support/
Contact Information
FrontRange Solutions Headquarters:
5675 Gibraltar Drive, Pleasanton, CA 94588
TEL: 800.776.7889 and +1925.398.1800
If calling fro m Canada, dial 1.888.603.3270
Offices are also located in Colorado Springs, Los Angeles, United
Kingdom, Germany, Italy, South Africa, Australia, Singapore, and China.
.
Installation Guide
x
Introduction
1
Overview
Before you install GMEE, it is important to understand the basic installation
requirements and components.
System Requirements
Requirements will vary by implementation. Contact your FrontRange
representative for more information.
For the latest requirements, please contact Technical Support at:
http://support.frontrange.com.
WARNING: Any deviation from the recommended system requirements may
have an adverse impact.
Provided Third-Party Software Components
As part of the installation packages, FrontRange makes a number of required
third-party software components available, including:
• Microsfost .NET Framework
• Crystal Reports 2008 SP2
• Microsoft Visual Studio Tools for Office (VSTO)
1-2
These are installed by the server or client installer program if they are not
detected on the host system. If you are creating your own installation
packages for remote deployment, you must include these software
components as noted in the following system requirements.
Application Server
System
Recommended
CPU
Dual CPU or Dual-Core 1.8GHz+
RAM
4 GB
Hard Disk
10 GB (Minimum Installation)
Operating System
• Microsoft Windows 2003 Server R2 SP2
• Microsoft Windows 2008 Server R2
• Microsoft .NET Framework, version 3.5 SP1
• Microsoft Internet Information Services (IIS) server 6.0 SP1 (Windows
2003)
• Microsoft Internet Information Services (IIS) server 7.0 (Windows 2008)
• Microsoft Message Queuing (MSMQ)
Web Application Server*
System
Recommended
CPU
RAM
4 GB
Hard Disk
10 GB (Minimum Installation)
Operating Systems
* When deployed separately from Application Server
SystemRequirements
1-3
• Microsoft Internet Information Services (IIS) server 6.0 SP1 (Windows
2003)
• Microsoft Internet Information Services (IIS) server 7.0 (Windows 2008)
• Microsoft Message Queuing (MSMQ)
• Compatibility with one or more of the following browsers:
• Microsoft Internet Explorer 7.0
• Microsoft Internet Explorer 8.0 (only use the currently-available
version. Pre-release versions have associated known issues.)
• Firefox 2.0 (Windows or Macintosh)
Note: In Windows 2008, you must enable the 32-bit mode for GMEE web
applications. To do so, open the Server Manager and access the IIS Manager.
In the Advanced Settings dialog box for each application in the Application
Pool, set Enable 32-bit Applications to TRUE.
Database Server
System
Recommended
CPU
RAM
4 GB
Hard Disk
10 GB (Minimum - see below for sizing)
Operating System
• Microsoft SQL Server 2005 SP2
• Microsoft SQL Server 2008
• Oracle 10g: On Release 2 of the Windows 2008 operating system, you
must install the Oracle 11g client.
• Note that disk space requirement above is the minimum. For proper
disk space sizing, please use the guidance below:
Demo Database: 200MB
Installation Guide
1-4
Average disk space requirement per record (Incident, Problem,
Change, Configuration): ~200KB
Average disk space requirement per record (Inventory): ~500KB
Client Machine
System
Recommended
CPU
Pentium IV or equivalent
RAM
1 GB (2GB for Windows Vista)
Operating System
• Microsoft Windows XP Professional SP3
• Microsoft Windows Vista Business Edition SP1
• Microsoft Windows 7 Ultimate 32-bit
• 100 MB of free hard disk space
• Microsoft Office 2003 or Microsoft Office 2007
• One of the following browsers:
• Microsoft Internet Explorer 7.0
• Microsoft Internet Explorer 8.0 ( only use the currently-available
version. Pre-release versions have associated known issues.)
• Firefox 2.0 (Windows or Macintosh)
Outlook Add-In
You must have the following items installed to use the Outlook
integration add-in module (depending on the version of Outlook you are
using):
Outlook 2003
• Microsoft Office 2003 Primary Interop Assemblies (PIA)
• Microsoft VSTO SE
CompatibilityMatrix
1-5
Outlook 2007
• Microsoft Office 2007 Primary Interop Assemblies (PIA)
• Microsoft VSTO 3.0
Note: The Outlook integration add-in installer programs for both Outlook 2003
and Outlook 2007 will search your host system for these components, and
install them if they are not already present.
Lotus Notes Add-In
You must have the following items installed to use the Lotus Notes
integration add-in module:
• Lotus Notes Client 6.5.3 - 8.5
Note: The Lotus Notes integration add-in installer program for Lotus Notes
will search your host for the required version of .NET, and install it if it is not
already present.
Compatibility Matrix
The following is an overview of software compatibility for GMEE.
Compatibility information for unreleased products is subject to change.
Contact FrontRange Solutions Support Services for additional details.
Installation Guide
1-6
Key for Compatibility Matrix
*
Code
Description
C
Has been fully QA tested and is Compatible (supported)
I
Has been fully QA tested and can be Integrated* (supported)
W
Has not been fully QA tested for compatibility/integration, but does
Work (supported)
N
Has been QA tested for compatibility and/or integration, but is NOT
supported due to test results
NT
Has Not been QA Tested; is currently NOT supported due to lack of
testing
-
Not Applicable/Not Available (NOT Supported)
Integration has been tested between products.
CompatibilityMatrix
1-7
Server Compatibility
Operating Systems
6.3
Windows 2000 Server
-
Windows Server 2003 SP1
W
Windows Server 2003 R2 SP1
W
Windows Server 2003 R2 SP2
C
Windows Server 2003 R2 x64
NT
Windows Server 2003 R2 German
C
Windows Server 2003 R2 French
-
Windows Server 2003 R2 Spanish
W
Windows Server 2003 R2 Portuguese
W
Windows Server 2008 (includes all
patch levels) 32-bit
C
W
Windows Server 2008 German
W
Windows Server 2008 French
C
Windows Server 2008 Spanish
W
Windows Server 2008 Portuguese
W
.NET Framework
6.3
.NET 3.0 SP1
-
.NET 3.5 SP1
C
Web Servers
6.3
IIS 5.1
-
Installation Guide
1-8
Web Servers
6.3
IIS 6.0 SP1
C
IIS 7.0
C
Database Management Systems
6.3
SQL Server 2000 SP3
-
SQL Server 2000 SP4
-
SQL Server 2005 RTM
-
SQL Server 2005 SP1
-
SQL Server 2005 SP2
C
SQL Server 2008
C
Oracle 9i
-
Oracle 10g R2
C
Oracle 11g
W
IBM DB2.1
-
Email Servers
6.3
Lotus Domino 6.5
W
Lotus Domino 7.0
W
Lotus Domino 8.0
W
Novell GroupWise 7.0.1
NT
Client Compatibility
Client Operating Systems
6.3
Windows 2000 Professional
-
Windows XP Professional SP1
-
CompatibilityMatrix
Client Operating Systems
6.3
C
C
Windows Vista Business
C
C
Microsoft Windows 7 Ultimate 32-bit
-
N
.NET Framework
6.3
.NET 1.1 SP1
-
.NET 2.0
-
.NET 3.0 SP1
-
.NET 3.5 SP1
C
Browser
6.3
1-9
Microsoft Internet Explorer 6.0 SP1
Microsoft Internet Explorer 7.0
C
Microsoft Internet Explorer 8.0
C
Firefox 2.0 on Windows
C
Firefox 2.0 on MAC OS 10.4 (Tiger)
-
Firefox 2.0 on MAC OS 10.5 (Leopard)
-
Firefox 3.0 on Windows
C
Installation Guide
1-10
Browser
6.3
Firefox 3.5 on Windows (requires
Microsoft .NET Framework Assistant
1.1 be downloaded if using the
ClickOnce client)
W
Firefox 3.0 on MAC OS
-
Firefox 3.5 on MAC OS
W
Crystal Reports
6.3
Crystal Reports 9.2.33
-
Crystal Reports 10.0.33
-
Crystal Reports 11.0.33 (Crystal
reports CR 11 R2 for .NET2, version
11.5.3700.0)
W
Crystal Reports 2008 SP2
C
Microsoft Office
6.3
Microsoft Office 2003 SP2
C
Microsoft Office 2007
C
Email
6.3
MS Outlook 97
-
MS Outlook 98
-
MS Outlook 2000 SP1
-
MS Outlook 2002
-
MS Outlook 2003
C
MS Outlook 2007
C
MS Outlook Express
-
Notes 1-11
Email
6.3
Lotus Notes Client 6.5.3
C
GroupWise Client 7.0.1
W
Other Integrations
6.3
HEAT 8.4.1(Last tested with 5.0.7.3
-
HEAT 8.4.3
-
HEAT 9.0
W
IPCM 5.1
W
IPCM 5.3
C
Citrix
W
Microsoft SMS (Integrations through
SMS adaptor)
-
(Patch 3))
Notes
The following recommendations are presented for the GMEE database
server.
• The Microsoft SQL Server needs to be installed locally on the machine
hosting GMEE.
• IIS needs to installed and configured to run on the machine hosting
GMEE
• On average, GMEE requires 100 MB of hard drive space.
• All system requirements were developed using Microsoft SQL Server
as the GMEE database application.
• It is recommended that a server be dedicated to the GMEE database for
larger implementations. Consult your GMEE Sales Analyst to
determine specific needs.
Installation Guide
1-12
Installation Type
The End User Installation type installs program files to an end user’s
workstation. Users can select the GMEE features they need or select all
features.
You can run this type of installation from either an administrative image
on a shared network drive or from the GMEE Installation CD
Administrative Installation Checklist
 Back up your GMEE database (upgrading customers only). We
recommend backing up your database before beginning any
installation. This prevents the loss of valuable, company-specific
information such as Contacts or Opportunities.
 Exit all programs running on your system. This frees memory and
alleviates potential conflicts between the installer and other software
on your computer. You should also exit the Microsoft Office shortcut
bar and stop all services.
IMPORTANT: You must have Microsoft Windows Installer Service
installed on your server in order to distribute GMEE to workstations by way
of your server.
 License GMEE. Licensing registers GMEE and its numerous modules.
Licensing is conducted through the Administrator module.
 For more information on licensing, see “Setting Security” in the online
Help.
End-User Installation Checklist
 Exit all programs running on your system. This frees memory and
alleviates potential conflicts between the installer and other software
on your computer. You should also exit the Microsoft Office shortcut
bar and stop all services.
2
Server Installation
Prerequisites
Prior to installing GMEE server, you should determine the following:
• The location and name of the database you intend to use with the server.
During the server installation, you will be prompted to input information
regarding this database, including its type, host, and login.
• The type of setting intended for the product:
• Production - a live installation that will be used for production
• Non-production - a test and development setting where no actual
production usage is intended.
Note: When installing a non-production version of the licensed software, you
may not use the licensed software in a production or live environment. Any such
use is a violation of the terms of use for the non-production version of the
licensed software. The non-production version is functionally limited in its
capabilities. The appropriate license agreement appears in the next step based
upon your selection here.
• The type of installation to perform:
• Complete - the standard installation where all features are installed.
• Custom - a user-specified installation where you can select individual
components.
2-2
Server Installation
• Where to install the software on your host (the destination location).
• The type of database you are using with GMEE. Refer to the system
requirements to see a list of supported databases.
The type of database selected determines what kind of reports will be
installed. If SQL is selected, only SQL type reports are installed. The
same is true for Oracle.
When selecting an Oracle Server database, you will be required to
configure the Oracle database manually. Contact your database
administrator for the necessary information, including server location,
login, and password.
• Whether or not to create a default database with your selected database.
If you choose a non-default database, you will be prompted to specify
it.
• The type of database authentication method to use. The recommended
option is “Server authentication using the Login ID and password”.
You will be prompted for the login name and associated password.
• The type of database connection. If installed on a 64-bit Windows
Server 2008 and connected to an Oracle database, you must install both
the 32-bit and 64-bit Oracle clients on the GMEE Server.
Installation
2-3
Installation
The following instructions are for installing a complete release of the
GMEE server. If you are upgrading from a previous release, follow the
instructions for upgrading your product.
The GMEE server can be installed on your database server or another
server.
The installation folder on your product CD contains a separate folder for
each GMEE component.
1. Access the GMEEserver folder on your installation package and run
setup.exe to launch the installer program. The welcoming screen
appears.
2. Click Next to continue. The Select License Type window appears.
Installation Guide
2-4
Server Installation
3. Select whether the installation if intended for use as production or for
evaluation. Click Next to continue. The License Agreement screen
appears.
4. Select the appropriate options to accept the license agreement and
click Next to continue. The Setup Type screen appears.
Installation
2-5
5. Select he type of installation to perform:
• Complete - the standard installation where all features are installed.
• Custom - a user-specified installation where you can select
individual components.
Click Next to continue. If you selected the Complete option, skip to the
next step. If you selected the Custom option, the Custom Setup
window appears.
Select any of the individual server components listed in the screen and
click Change to specify an alternate installation location.
Installation Guide
2-6
Server Installation
You can also click the down arrow on any subcomponent and specify
which option to use:
• This feature will be installed on the hard drive.
• This feature, and all subfeatures, will be installed on the hard drive.
• This feature will be installed when required.
• This feature will not be available.
Make your selections and click Next. The Ready to Install the Program
screen appears.
6. Review the installation information listed in the screen. It it is correct,
click Next to continue the installation. To change anything, click Back
and update your installation information, then return to this screen.
The Select Database screen appears.
Installation
2-7
7. Select the database type from the list. You can also indicate whether to
create a default database for GMEE by checking the associated box.
You can also enter the name of the default database in the Default
Database Name field. Click Next to continue.
Note: The subsequent screens associated with configuring your server
database can vary depending on the type of database you selected. The
following steps provide a general summary of the tasks required.
8. Perform the following tasks in the Database Server screen:
• Enter the name of the database host. Click Browse to navigate your
network to find the host if necessary.
• Select the authentication method to use with the database:
Installation Guide
2-8
Server Installation
• Use the Windows authentication method of the current user.
This option relies on the login credentials you entered to login
to your host.
• Use a user-defined database login (typically “sa” and
password. You must enter this information in the associated
boxes below this option.
• Enter the name of the database catalog. Click Browse to view a list of
the available catalogs to choose.
Click Next to continue. The Ready to Install the Program screen
appears.
After clicking Next, the installation starts. A status screen shows you
the progress of the installation. When the installation is successfully
complete, the following window appears.
Installation
2-9
From this window you can run the following programs:
• GMEE Server Manager
• Business Process (BP) Setting Utility
To end the installation without further activities, click Finish.
Installation Guide
2-10
Server Installation
License Management
Before you can run your application, you must ensure that it is properly
licensed. License management tasks are performed in the License
Manager tool. Select Programs>FrontRange Solutions>License Server to
run this tool.
You must perform the following tasks in the License Manager tool to
properly license your application:
• Import your application server license file.
• Update your application server host MAC information.
LicenseManagement 2-11
Importing the Application Server License File
When you acquire a license for the application, you will be issued a
license file. Place this file on your application server host’s file system or
some other location that your host can access.
To import the license file into your application’s license server:
1. Run the License Manager tool and select Import under License
Management to display the License Management window.
2. Click Import to display the Import File window and navigate to your
license file’s location.
Installation Guide
2-12
Server Installation
3. Select the license file and click Open. The License Management
window reappears containing your imported license.
Updating Your Host MAC Information
You must add your application server host’s MAC address into the
application license server for your application to be completely licensed.
To update the host MAC information in your application’s license server:
1. Open a command prompt window on your application server host
and enter ipconfig /all. This command displays a variety of host and
network information. Note the value for Physical Address under
Ethernet Adapter Local Area Connection. You will need this value
later in this process.
2. Run the License Manager tool and select Update Addresses under
License Management to display the Manage Application Server MAC
Address window.
LicenseManagement 2-13
3. Ensure that _ALL SERVER BASED MODULES_ is selected for the
Module List.
4. Substitute the 12-digit physical address value you noted when you ran
ipconfig /all and enter it for the default 00-00-00-00-00-00 value under
the MAC Addresses table and click Confirm. A confirmation window
is displayed containing your updated MAC address.
5. Close the Manage Application Server MAC Address window to return
to the License Management window
You have now properly licensed your application server, and you can
begin using it.
Adding Additional Licenses
After purchasing GMEE with the original allotment of licenses, you may
have a need to increase the capacity of the original license. For example, if
you have originally purchased 30 licenses for the Incident module, but
will need to increase that capacity by 20 more licenses, to raise the total
number of licenses to 50.
Installation Guide
2-14
Server Installation
To increase the number of licenses, import the license file which contains
the additional licenses. The total number of licenses available for a given
module will be increased based on the number of licenses defined in the
new license file.
Assigning the MAC address in a Virtual
Environment
When running GMEE within a virtual environment, it is important to
realize that the MAC address that must be specified in the License Server
Admin, is the MAC address that is reported inside the virtual
environment itself.
To determine this information, inside a running virtual session (i.e. guest
environment), launch the command prompt, and then run either
“ipconfig /all” or “getmac”, which will display the available MAC
addresses in the virtual environment. The user can then assign these
MAC addresses in the License Server Admin.
Note that if the Virtual Machine is copied to a different location, when
booting the image in the new host environment, the user will be
prompted to create a new UUID, or keep the same UUID. Make sure you
choose the Keep option to ensure that the same MAC address is retained
for the virtual machine.
Adding Connections in Windows 2008
On Windows 2008, a two-tier and three-tier connection must be created.
You will add the name of your two-tier connection to the following file:
C:\Program Files (x86)\FrontRange
Solutions\FRSApplication\ServiceManagement\web.config
You will add the name of your three-tier connection to the following file:
C:\Program Files (x86)\FrontRange
Solutions\FRSApplication\ServiceManagementWeb\web.config
ApplicationDatabaseLoading
2-15
Application Database Loading
After you have installed and licensed your application, you must prepare
its associated database for use. The database must be populated with the
necessary data to run the application. The data is combined into a Fusion
Archive Document (FAD) file.
By default, a new installation of the application includes a demonstration
FAD file and an empty one for production use. You can also select any
existing FAD files to import into your application database.
In a clean GMEE v6.3.1 installation (not an upgrade), the following major
tasks should be performed:
1. Use the Server Manager tool to load the common GMEE demo FAD
file found in the <installation directory>/GMEE/Fad folder as
described in "Loading the Database."
2. Use the Admin tool to create an external database connection. For
more information, see "Creating an External Database Connection" on
page 4-6.
3. Use your SQL database management tool (normally SQL Management
Studio) to run the SQL scripts found in the <installation directory>/
GMEE/Fad/SqlScripts folder. Select the scripts applicable to your
database server, as the scripts differ for MS SQL servers and Oracle
servers.
Note: Review the Readme.txt file in the script directory to obtain the
sequence for running the scripts. For example, Forecast scripts need to be
run before the SalesCapacity scripts.
4. Use the Admin tool to import the GMEE631Step2.fud file found in the
<installation directory>GMEE/Fad folder.
Loading the Database
Loading the application database is performed using the application
Service Manager tool. To import a FAD into your application database:
1. Select Programs>FrontRange Solutions>GMEE>FrontRange Server
Manager to display the FRS Application Server Manager window.
Installation Guide
2-16
Server Installation
2. Select Load FAD File from the icons on the left. The associated
attributes are displayed.
3. Enter the path to the FAD file to import in the FAD File box. Click
Browse and navigate to the FAD file’s location.
If this is a new installation, and you do not want to import an existing
FAD file, navigate to the GMEE\Fad folder and select one of the FADs
present there. A (demo) FAD has sample content for demonstration
purposes. An (empty) FAD is intended for production use.
After you select your FAD, the Server Manager window is updated
with the FAD you selected.
ApplicationDatabaseLoading
2-17
To import the FAD to a database other than the default specified
during installation, uncheck the box and click Browse to display the
application connections window. Select the alternate connection’s
database to import the FAD to and click OK.
4. Click Import to begin the database population. You will be required to
log in before the importation can begin.
Note: If you selected a database that already has a FAD installed, you will
overwrite this data. In such cases, the Service Manager will warn you
before beginning the importation.
Installation Guide
2-18
Server Installation
3
Client Installation
Information Prerequisites
Prior to installing GMEE, you should determine the following:
• The type of installation to perform:
• Typical - the GMEE software and accompanying help files.
• Complete - the GMEE software and accompanying help files, plus all
additional optional modules available.
• Custom - the GMEE software and accompanying help files, and the option of
selecting any particular optional module available.
3-2
Client Installation
For each of these options, the destination folder for the installed
software is indicated.
• Where to install the software on your server (the destination location)
and whether to have a shortcut to the client placed on your desktop.
• Whether to create a connection to an GMEE server during the client
installation. If you choose this option, you are promoted to enter the
URL to the appropriate application server.
Smart Client Installation
The following instructions are for installing a complete release of the
GMEE server. If you are upgrading from a previous release, follow the
instructions for upgrading your product.
1. Access the GMEEclient folder on your installation package and run
setup.exe to launch the installer program. The welcoming screen
appears.
SmartClientInstallation
3-3
appears.
click Next to continue. The Installation Type screen appears.
Installation Guide
3-4
Client Installation
Here you can choose from the following installation options:
• Typical Install - select to install the client and help files to the default
location: C:\Program Files\FrontRange Solutions\FRSAppliction.
• Complete Install - select to install the client, administrative tools, and
help files to the default location.
• Custom Install - select to do one or more of the following:
• Select specific installation component options, but not install
the complete set of options.
• Specify a destination folder for you client software other than
the default location.
• Place a shortcut for the client on your desktop.
Click Next to continue. If you selected the Typical or Complete option,
skip to the next step. If you selected the Custom option, the Choose
Additional Features screen appears.
3-5
Here you can select any of the available components available for
installation. Select an option (or none at all) and click Next. The Select
Destination screen appears.
Here you can specify a different installation destination location. You
can also check the option to place a shortcut on the desktop.
Make your selections and click Next. The ConnectionsGMEE screen
appears.
Installation Guide
3-6
Client Installation
5. Click the checkbox to establish a connection between the client and the
GMEE server during installation. Checking the box displays the
ApplicationServerURL field. Enter the URL to the appropriate
application server for the connection.
Clink Next when done. The Ready to Install the Program screen
appears.
3-7
When the installation is complete, the following screen appears:
7. Click Finish to complete the Smart Client installation.
Installation Guide
3-8
Client Installation
Click-Once Deployed Client
Click-once provides client functionality with the deployment and update
capabilities of a smart client. Click-once works in a network environment
or over the Internet. All setup and run tools are included in the GMEE
server installation.
Note: For Firefox users, only Firefox 2.0 is supported for click-once deployed
clients.
After you complete the GMEE server installation, follow these steps:
1. Open a Web browser window and go to this URL:
http://<your_server_name>/FRSAppServer
The splash screen appears:
2. Click Download Prerequisites to download the prerequisites. The
Save File dialog appears.
3. Save the prerequisites file and unzip the contents to a temporary
folder.
4. Run the prerequisites setup program.
5. Follow the instructions to install the Prerequisites.
Click-OnceDeployedClient
3-9
Note: When using Firefox, first click the Firefox Prerequisites link to
download and install the Firefox plug-in. Then click the Launch GoldMine
Enterprise Edition Application link to start GMEE.
6. Click the Launch GoldMine Enterprise Edition Now link .
This will launch the application using a default 3-tier connection to the
server. You will be prompted to log in. After logging in, you can access
GMEE in the same way you would using the Smart Client.
Configuring Clients Using Three-tier Connections
1. To connect with a three–tier connection to GMEE, from
Programs>FrontRange Solutions> Launch GoldMine Enterprise
Edition application.
2. Click New on the Personal tab (only you will see the connection), or
Common (other’s logged onto the same PC can see these connections).
3. Select Connect to FRS Application under Connection Options.
Installation Guide
3-10
Client Installation
4. Click Next.
3-11
5. Type the URL for your Application Server, or browse to the location
and click Next.
Installation Guide
3-12
Client Installation
6. On the Server Connection Options dialog box, select a Compression
setting from the drop-down list:
• None: Select if you are connecting to an application server within
your Local Area Network.
• Best Compression: Recommended for Wide Area Network
environments and home users. If you are connecting to an
application server remotely, you should select this option.
• Good Compression: Select if the application server you are
connecting to is not within your Local Area Network and you are
concerned about overusing your computer's resources.
• Low Compression: Select if the application server you are
connecting to is not within your Local Area Network and you would
like to utilize the minimum amount of your computer's resources for
compression.
7. Select a Cache Mode from the drop-down list:
• None: Not recommended. No definitions will be cached.
3-13
• User Role Caching: Recommended for users connecting to an
Application server. All definitions for this user's role will be cached.
• Server Caching: Recommended for server applications. All
definitions will be cached locally.
8. Click Next. The Name Connection dialog box appears.
9. Type a Name for your connection to the FRS Application and click
Next.
Installation Guide
3-14
Client Installation
10. Click Test Connection.
11. If the connection is successful, click Finish. (If the connection fails,
click Back and verify the settings or contact your Administrator.)
12. The client connection is now configured to launch your GMEE
instance.
3-15
Web Client
In order to use the Web Client, it must be configured by the
Administrator on a web server and must use a supported browser. IE and
Firefox are supported browsers for both clients.
IMPORTANT: Firefox disables all pop-up windows by default. Make sure you
disable pop-up blocking in Firefox to allow full display of messages in the
GMEE Web Client.
The web files are installed with the server installation and once
configured can be ran by the clients.
To login to GMEE Web, launch your browser and type in the following
address. http://<yourservername>/ServiceManagementWeb/
Login.aspx
In order for GMEE Web to work properly, the web.config file must be
pointing to the correct connection names on the server.
Disconnected Client
The GMEE client can run when it is disconnected from the network
linking it to the GMEE server.
To replace the lost connection to the license server, you must locally
install the GMEE license server by running the GMEE server installation
Installation Guide
3-16
Client Installation
program, which in turn requires the Windows Message Queueing feature
to be enabled.
1. Enable Windows Message Queueing on the disconnected computer
where the GMEE client is installed.
The feature is found in Control Panel>Add/Remove Program on
Windows XP, in Control Panel>Program and Features on Microsoft
Vista and on Windows 7 Ultimate 32-bit..
2. Install the License Server:
a. Copy and launch the GMEE server installer on the disconnected
computer where your GMEE smart client is installed.
b. Run the Setup Wizard. On the Setup Type screen, select Custom.
Click Next to open the Custom Setup screen.
c. Select only LicenseServer to install. Make sure the other features are
unselected and marked with a red X.
d. Complete the Setup Wizard.
e. Import a license, update the MAC address of the local computer and
restart the Licence Server as you would in a regular server
installation.
Note: Since there is no connection with the BP Engine in a disconnected
state, you must uncheck the Send events to BP engine checkbox in the
Administrator before disconnecting.
Desktop Shortcuts
Installing the client does not automatically place a shortcut on your
desktop. Instead, you must run the following tasks, depending on the
type of client installation you are performing:
• Smart Client installation - during the Smart Client installation, the
window that prompts you to specify the installation location contains a
checkbox for placing a shortcut on your desktop. Check this item. See
"Smart Client Installation" on page 3-2 for more information.
• Silent installation - run the following command after the silent
installation:
GMEE<release>Client.msi /qb+ SHORTCUT=1
Outlook Integration Add-In Installation
3-17
Depending on the type of client installation you performed, the Outlook
integration add-in module may require a separate installation. You must
have a supported version of Microsoft Outlook on the client host before
you can install the Outlook integration module.
There are separate installation folders for Outlook 2003 and Outlook
2007. Only run the installation from the folder for the version of Outlook
you have on your host:
• OutLookAddIn2003
• OutLookAddIn2007
To install the Outlook integration module:
1. Access the installation folder on the product CD appropriate for your
version of the Outlook integration and run
FRSOutLookAddIn2003.exe or FRSOutLookAddIn2007 to launch the
installer program.
2. Click Next to continue. The License Agreement screen appears.
Installation Guide
3-18
Client Installation
click Next to continue. The Ready to Install the Program screen
appears.
4. Click Install to begin the installation. When the installation is
complete, the following screen appears.
3-19
5. Click Finish to complete the installation.
Note: On Outlook 2007, you can verify that the Outlook integration add-in
loaded successfully after installation by accessing the Outlook Trust Center
and selecting the Add-ins screen. The entry FrontRange Outlook2007
AddIn should be listed under the Active Application Add-ins heading. If the
Outlook integration add-in entry is listed under Inactive Application Addins, select COM Add-ins from the Manage list and click Go. Check the box
for the Outlook add-in the resulting window and click OK.
Installation Guide
3-20
Client Installation
Lotus Notes Integration Add-In Installation
The Lotus Notes integration add-in module requires a separate
installation. You must have a supported version of Lotus Notes on the
client host before you can install the Lotus Notes integration module.
Notes:For previous users of this feature, a number of changes have been
made with this release:
• The file “Orion.Module.FRSLotus Notes.dll” has been renamed to
“Orion.Module.LotusIntegration.dll”, and now resides in the following
location: C:\Program Files\FrontRange Solutions\FRSApplication.
• The Lotus Notes integration add-in only requires installation on the client.
No server-side installation is required.
Prerequisite Installation Steps
The following sections describe tasks you should perform prior to
installing the Lotus Notes integration add-in.
Configuring Lotus Notes for a Single User
Lotus Notes should be configured for a single user installation rather
than a multiple user installation prior to installing the Lotus Notes
integration add-in. Refer to your Lotus Notes documentation on how to
configure it for use by a single user if it is not already.
Granting Manager Rights to Users
When installing the Lotus Notes client, you must select a user who has
“manager" rights on the Domino server. To grant this permission to a
user:
1. Open the Domino Admin program.
3-21
2. Select the Files tab to make it active.
3. Select the mail folder in the left pane. The contents of this folder are
displayed in the right pane.
4. Right-click the user to assign the permission and select Access
Control>Manage from the pop-up menu to display the Access Control
List window.
Installation Guide
3-22
Client Installation
5. Highlight the user and select Designer from the Access list.
6. Check the Create LotusScript/Java agents and click OK.
Enabling Notifications
To enable the notification feature in the Lotus Notes integration, you
must install it on your application server.
Installation
To install the Lotus Notes integration module:
1. Access the installation folder on the product CD appropriate for your
version of the Lotus Notes integration and run
FRSLotusNotesAddIn.exe to launch the installer program.
2. Click Next to continue. The License Agreement screen appears.
3-23
click Next to continue. The Custom Setup screen appears.
Click Next to accept the default installation C:\Program
Files\FrontRange Solutions\FRSApplication or click Change to
specify an alternate installation location. The Lotus Integration Data
appears.
Installation Guide
3-24
Client Installation
4. Review the Lotus Notes attributes in this screen and make any
required changes. You must also enter the user password associated
with Lotus Notes in the User Password field. Click Next to continue.
The Ready to Install the Program screen appears.
5. Click Back to change any settings. Otherwise, click Install to begin the
installation.
When the installation is complete, the following screen appears:
3-25
6. Click Finish to complete the installation.
Installation Guide
3-26
Client Installation
4
Upgrading GMEE
GMEE can be upgraded to v6.3.1 from the 6.0.7 and 6.3.0 versions, introducing a
Customer Self Service Portal and 13 new dashboards. This chapter describes the
tasks required to successfully upgrade the GMEE server application to version
6.3.1. It includes the following sections:
• "Feature Enablement Utility Overview" on page 4-2
• "Pre-Installation Checklist" on page 4-2
• "Upgrading from v6.0.7 GMEE Foundation" on page 4-4
• "Upgrade Checklist" on page 4-5
• "Creating an External Database Connection" on page 4-6
• "Using the Feature Enablement Utility" on page 4-7
• "Post-Upgrade Steps" on page 4-16
Upgrade Path
You can upgrade to GMEE version 6.3.1 from versions 6.0.7 and 6.3.0.
4-2
Upgrading GMEE
Feature Enablement Utility Overview
The v6.3.1 installation package includes the Feature Enablement Utility,
which upgrades the system schema and performs data cleanup while
preserving system customizations.
The Feature Enablement Utility is a wizard that:
• Lists new features available for installation. You can select which
features to install.
• Checks your current installation for dependencies and conflicts with
the features being installed. For each conflict area detected, you can
choose to overwrite or retain your currently installed configuration.
• Enables your selected features by adding their metadata to your FAD
file.
Pre-Installation Checklist
Prior to running the GMEE Feature Enablement Utility, you should have
performed the following tasks:
Description

Back up the current GMEE database.
FrontRange Solutions highly recommends that customers create an
image of the current Applications Server.
If you experience any unexpected interruptions or unexpected
behavior during the upgrade process, FrontRange Solutions
recommends that you restore the original image on the Application
Server.

Back up the existing installation, including the installation directory
(C:\Program Files\FrontRange Solutions\) and the
database.

Perform a file backup of other separate servers (such as a separate
BPE or Web application server) used for the GMEE application

Install the GMEE v6.3.1 product.
Pre-InstallationChecklist
4-3
Description

When upgrading from a v6.0.7 installation, run the Foundation
Upgrade Wizard on your existing Fusion Archive Document (FAD) file.
For more information, see "Upgrading from v6.0.7 GMEE Foundation"
on page 4-4.
Installation Guide
4-4
Upgrading GMEE
Upgrading from v6.0.7 GMEE Foundation
Before being able to run the Feature Enablement Utility, the GMEE 6.0.7
database must be upgraded version 6.3.0 by running a Foundation
Upgrade Wizard. This section describes how to run that Foundation
upgrade Wizard.
When the Upgrade Wizard detects an older Foundation, a window is
displayed with a message that the Foundation upgrade needs to be
performed.
The upgrade process performs the following tasks:
• Removes records with duplicate RecIDs
• Upgrades the System Table
• Removes any duplicate link records
• Updates link fields with Autofill for backward compatibility
• Checks the application for errors
Validation of the database is also run as part of the System Table
upgrade.
To Run the Wizard
1. Open the Windows Start menu and select All Programs >
FrontRangeSolutions>GMEE>Upgrade Wizard.
You can also access the Application Upgrade Wizard from the
\Program Files\FrontRange Solutions\Service
Management\UpgradeWizard.exe
2. Select the target database to update and click OK.
3. Log in with Admin credentials.
4. After logging in, a validation check runs, checking for any possible
errors or warnings in your current FAD.
Let the validation check complete. Do not cancel at this time.
If you encounter any errors, you must quit the wizard and fix the
errors in the Admin tool. If the errors are validation errors, the wizard
will not let you proceed with the upgrade.
UpgradeChecklist
4-5
5. After the validation completes, the Welcome to the Upgrade Wizard
screen opens.
6. Close all running FrontRange Solutions services.
7. As a safety precaution, back up your database before starting the
upgrade process.
8. After you have created a backup of your database, select I
acknowledge the above warning and then click Next.
DO NOT check the Perform application upgrade option.
The system checks for conflicts between the upgrade package
definitions and the target database definitions. It also checks for errors,
such as missing data files.
Any reported conflicts must be dealt with before you can proceed. For
more information, see “Handling Upgrade Conflicts” on page 27.
9. Click Finish to close the wizard.
10.After completing the upgrade process, restart IIS and test.
Upgrade Checklist
A successful upgrade to GMEE version 6.3.1 involves the following tasks:
Description

Manually create an external database connection. For more
information, see "Creating an External Database Connection" on
page 4-6.

Run the Feature Enablement Utility. For more information, see "Using
the Feature Enablement Utility" on page 4-7.

Run data-migration SQL scripts. For more information, see "PostUpgrade Steps" on page 4-16.

Customize GMEE form layouts to compensate for any new fields. For
more information, see "Post-Upgrade Steps" on page 4-16
Installation Guide
4-6
Upgrading GMEE
Creating an External Database Connection
Before you can run the Feature Enablement Utility, you must first create a
manual database connection to an external source.
1. Open the Administrator tool and click New Definition.
2. Select External Data Sources… from the Definitions menu.
A screen opens displaying existing External Data Sources.
3. Click the New button to start the Connection Wizard:
a. Select Database and click Next.
b. A screen opens for selecting the Database Server. Select a Database
Server and click Next.
c. A screen opens for selecting the Database. Select a Database and click
Next.
d. A screen opens for selecting security options. Select either Integrated
Security or User ID/Password information and click Next.
e. A screen opens for entering the security information corresponding
to your selection. When finished, click Next.
f. A screen opens for entering Connection pooling information. Enter
the connection pooling values and click Next.
g. A screen opens for entering Database Command Timeout values.
Enter the values and click Next.
h. A screen opens for defining your connection. Enter the Connection
Name (LocalGMEE) and Description (Local GMEE - External
Database Connection) and click Next.
i. The Test Connection screen opens. Click the Test Connection button.
• If the test fails, edit your Connection Wizard settings.
• If the test is successful click Finish. A new screen opens listing the
new connection.
4. Click OK and Commit to commit the new definition.
Using the Feature Enablement Utility
4-7
1. Locate and run the Feature Enablement Utility executable
(UpgradeTool.exe) from its installation directory:
C:\Program Files\FrontRange
Solutions\FRSApplication\GMEE\Fad\UpgradeTool.exe
The Feature Enablement Utility
opens.
2. Select the database to upgrade and click OK to continue.
3. Click the checkboxes to select the list of features to add to the
installation from the list in the dialog box. The database will be
updated to reflect these new additions.
Installation Guide
4-8
Upgrading GMEE
Click Next to continue.
4-9
4. The system checks for conflicts and displays the total number of
conflicts for each feature in the dialog box.
• Click the View Conflicts hyperlink to view the complete list of
conflicts detected for each feature.
• Click a checkbox to select an option for resolving these conflicts.
• Keep the current definitions
• Overwrite with new definitions
• Click the Let me decide for each conflict radio button to display the
list of conflicts for this module for individual resolution.
Click Next to continue.
Installation Guide
4-10
Upgrading GMEE
5. The Ready dialog box opens for reviewing your selections.
To make corrections, click the Back button to return to the previous
screens. When finished, click Next to continue.
4-11
The dialog box changes to reflect the progress of the installation for
each component.
Installation Guide
4-12
Upgrading GMEE
6. When the installation is complete, click Next to display a checklist of
post-installation tasks.
4-13
7. Review the post-installation tasks displayed on this screen and click
Finish to exit the utility.
Handling Upgrade Conflicts
Upgrade conflicts occur when the Upgrade Wizard encounters an object
(relationships, panels, grids, etc.) that is either unexpectedly missing or
already existing in the target database. Any conflicts are displayed in the
window.
• Add Object Conflict is any conflict that occurs when the Upgrade
Wizard encounters an object that it doesn’t expect to be in the target
database. An example might be that the user created a new object that
has the same name as an object that the wizard is attempting to add.
This type of conflict can cause a loss of data to the user’s database, if the
Installation Guide
4-14
Upgrading GMEE
user has created a object for a specific purpose, because the upgrade
will overwrite this object with its own information.
• Update Object Conflict is any conflict that occurs when the Upgrade
Wizard encounters a missing object that it was going to update in the
target database. This type of conflict is typically safer to ignore because
it does not replace existing data, but adds data that is missing.
Viewing Upgrade Conflicts
When a conflict is discovered, the results appear in the window with a
link and a description of the conflict. To view the details of the conflict,
click the link under the Upgrade Feature column. A new window opens
with detailed information about the conflict.
Resolving Upgrade Conflicts
After viewing the details of any reported conflict, you can choose to
either proceed without upgrading the areas of conflict or continue
upgrading and ignore the conflict.
To Resolve Conflicts
1. View each conflict’s details to decide if you want to ignore or upgrade
it.
2. Check the Ignore Conflicts box and then check the box next to the
conflict(s) you want to update.
All unchecked conflicts will be upgraded.
Conflicts that are ignored (checked) display a different symbol on the
Selected Upgrade Feature tree after proceeding to the next step.
3. Click Next to resolve the conflicts.
For heavily customized databases (standard fields deleted, custom
fields added, panels altered), the Feature Enablement Utility will
locate a large number of conflicts. If this list proves too difficult to
resolve manually, contact FrontRange Solutions Professional Services
for a to develop a customized implementation of GMEE v6.3.1.
4-15
Viewing Upgrade Wizard Log Files
After the Upgrade Wizard process completes, you can view the log file
created from the Upgrade Wizard. This file contains all the information
displayed on the Log tab, plus other information logged. The log file is
stored in the following directory:
\Program Files\FrontRange Solutions\Service Management
\UpgradeData\Logs\
The log files are named in the following manner:
UpgradeWizard_yyyy-mm-dd_hhmmss.log
yyyy
4-digit Year value
mm
2-digit Month value
dd
2-digit Day value
hh
2-digit hour value
mm
2-digit minutes value
ss
2-digit seconds value
An example of a log file for the Upgrade Wizard that was completed on
December 10th, 2008 at 1:24.36 P.M. would have the following structure:
UpgradeWizard_2008-12-10_132436.log
Installation Guide
4-16
Upgrading GMEE
Post-Upgrade Steps
1. Restart your IIS and GMEE services following best practice guidelines.
2. New Geography, Region and Territory fields have replaced the old
Territory field. The Geography field is mandatory, and when empty
could prevent saving updates on an existing object. You can manually
set the Geography field each time you open an existing object., or run a
set of SQL scripts which will populate the Geography field in existing
objects where the old Territory field was empty.
Using SQL Server Management Studio, Run the SQL migration scripts
provided in your upgrade package to repopulate data. The scripts can
be found at:
<installation directory>\FrontRange
Solutions\FRSApplication\GMEE\Fad\DataMigration\
Run the scripts in the following order:
a. updGRTEmployee.sql
b. updGRTContact.sql
c. updGRTAccount.sql
d. updOpportunity.sql
e. updQuota.sql
f. updForecast.sql
g. updGRTLead.sql
h. updGRTActivity.sql
In existing objects where the old Territory field contains a value, the
value is automatically mapped to the new Region field and the
Geography field is automatically filled with a corresponding value.
For example, if the old Territory field contains Canada, the new
Geography field will be filled with Americas and the new Region field
will be filled with Canada.
In new objects, the Geography field contains the Americas value by
default.
3. The Feature Enablement Utility adds new fields to existing forms.
These new fields are added around the existing fields to avoid
Post-UpgradeSteps 4-17
overwrites. In some cases, the label of a field may be separated from
the actual field.
It is left to the user to manually customize the layout of the form with
the new fields. To do so, use the Administrator tool to edit the
Definition Set on the GMEE server. Refer to the Foundation
Administration documentation for detailed instructions.
4. During an upgrade from v6.0.7 or 6.3.0, the installation program adds
a new_ prefix to each of the files listed below:
• ServiceManagementWeb\Defs-SelfServiceNavigatorDefSelfServiceMain.xml
• ServiceManagementWeb\SelfService.htm
• ServiceManagementWeb\SelfServiceLogin.aspx
• ServiceManagementWeb\welcome.html
• ServiceManagementWeb\Images\bgr.jpg
• ServiceManagementWeb\Images\bg_container_1x300.gif
• ServiceManagementWeb\Images\hdr_bg_black.GIF
• ServiceManagementWeb\Images\support_photo.gif
• ServiceManagementWeb\Presentation\SelfServiceHeader.htm
This is done to preserve any header banner customizations. In the
default demo FAD, those files contain a header banner mentioning
ITSM instead of GMEE. Remove the new_ prefix from the files listed
above and use them to replace the files in the default demo FAD.
5. Verify that your existing application is working correctly in the v6.x
foundation.
Failure Recovery
A failure of the upgrade process results in the following window being
displayed.
Installation Guide
4-18
Upgrading GMEE
If the upgrade fails, copy files that may have changed since the initial
installation to a separate location for comparison purposes. You can find
these files in the following location:
C:\Documents and Settings\<user>\LocalSettings\Temp\Guid.
Because a failure results in the Foundation files being rolled back, you
must re-install your original Foundation software. Following the reinstallation of the original Foundation software, you can place the copied
files into their original location.
It is recommended you delete any existing FrontRange virtual directories
and application pools and then restart IIS before re-installing your
original Foundation software.
5
Knowledge Management
Installation
This chapter describes the installation of the Knowledge Management (KM)
module.
Prerequisites
Prior to installing the KM server, you should determine the following:
• The location and name of the database you intend to use with the server.
During the server installation, you will be prompted to input information
regarding this database, including its type, host, and login.
• Where to install the software on your server (the destination location).
5-2
• The type of database you are using with your application. Refer to the
system requirements to see a list of supported databases.
The type of database selected determines what kind of reports will be
installed. If SQL is selected, only SQL type reports are installed. The
same is true for Oracle.
When selecting an Oracle Server database, you will be required to
configure the Oracle database manually. Contact your database
administrator for the necessary information, including server location,
login, and password.
• The type of database authentication method to use. The recommended
option is “Server authentication using the Login ID and password”.
You will be prompted for the login name and associated password.
• The application roles to grant access to the KM server.
Installation
The Knowledge Management server can be installed on your database
server or another server. It is typically installed on the same host as your
application server.
1. Access the KnowledgeBase Server folder on your installation package
and run setup.exe to launch the installer program. The welcoming
screen appears.
Installation
5-3
appears.
click Next to continue. The Destination Folder screen appears.
Installation Guide
5-4
5. Click Browse and navigate to the destination location for the
installation. Click Next to continue. The Ready to Install Program
screen appears.
6. Click Back if you need to change any of the settings you made for the
installation. Click Install to start the installation. The Knowledge
Management Server Configuration Wizard starts.
Installation
5-5
7. Select the items to configure. Click Next to continue.
Note: For instructive purposes, it is assumed you have checked all the
options.
The Knowledge Management Content Path screen appears.
8. Enter the path to the repository for the Knowledge Documents
collection in the Select New Content Path field. Click Next to continue.
The Select the Database Type screen appears.
Installation Guide
5-6
9. Select the database type from the list. Click Next to continue. The
Configure Database Connection screen appears.
Note: The subsequent screens associated with configuring your server
database can vary depending on the type of database you selected. The
following steps provide a general summary of the tasks required.
10.Perform the following tasks in the Database Server screen:
• Enter the name of the database host. Click Browse to navigate your
network to find the host if necessary.
• Select the authentication method to use with the database:
Installation
5-7
• Use the Windows authentication method of the current user.
This option relies on the login credentials you entered to login
to your host.
• Use a user-defined database login (typically “sa” and
password. You must enter this information in the associated
fields below this option.
Click Next to continue. The Choose Port Number and Protocol screen
appears.
11.Perform the following tasks:
• Select the protocol from the Protocol list.
• Enter the port number in the Port Number field.
Click Next to continue. The Database Connection screen appears.
Installation Guide
5-8
12.Enter the name of the database connection in the Database
Connection field. You must also provide the application user name
and password. Click Next to continue. The Configuration Options
screen appears.
13.Check the associated box to register the Knowledge Manager module
in your application. You must also provide the hostname and
associated password for the host displayed. Click Next to continue.
The Knowledge Management Licenses screen appears.
Installation
5-9
14.Select each role that will be authorized to use the Knowledge
Management module. Click Next to continue. The Configuration
Options screen appears.
15.Review the installation information listed in the screen. It it is correct,
After clicking Next, the installation starts. A status screen shows you
the progress of the installation. When the installation is successfully
complete, the following window appears.
Installation Guide
5-10
16.Click Finish to complete the installation. The Wizard Completed
screen appears.
17.Click Finish to close the wizard.
5
Overview
The BP Engine interprets the BPML generated by the BP Designer and executes
the activities in the BP Process.
Business Process Configuration Utility
The Business Process Configuration Utility (BPMLSettingUtility.exe) is a utility
that modifies the BPService.exe.config file in the BPEngine folder, as well as the
Web.config files for the FusionBOWS and FusionNotification Web Services. The
BP Engine reads configuration setting from the BPService.exe.config. Access the
BP Configuration Utility by double-clicking the BPSettingUtility.exe file, located
in the Program Files\FrontRange Solutions\FRSApplication directory.
5-2
The following sections describe each tab.
Business Process Service Tab
The BPServer and MBServer settings specify the location where the
message queues for inbound and outbound messaging are running. The
default period (.) setting means the queues are running on the local
computer which is the required configuration to support transactions.
The Engine must have read and write privileges on the queues.
The BPServiceAccount and MBServiceAccount settings specify the login
accounts for the inbound and outbound message queues. Do not change
these—they are reserved for future use.
Business Process Configuration Utility
5-3
The default Package Path is Program Files\FrontRange
Solutions\FRSApplication\GMEE\BPPackages.
This is the directory where your package is saved.
If you save your packages in a different location, change the setting for
your Package Path. Do not use a relative path name.
Select the Package Name. In the previous screen capture, notice the
package name is set to GMEE package.bpml. Select the Engine package to
run here.
Leave the false default setting for UseQueueForWebService. This means
the Engine communicates directly with the Web services it uses. This
field is reserved for future expansion.
Connection String can be configured when … button at the end of the text
box is pressed. The Connection wizard is shown where server, database
name, and credential can be entered. After testing for a connection and
clicking OK, the connection string is automatically filled in.
Business Object Web Service Tab
This tab is used to configure the login (fusion connection information)
portion of Fusion BOWS (web.config)
- Fusion Connection – Name of the database connection you use to
connect to. For example ‘GMEE user Name of the user accessing the
system. Example admin password The user’s password manage
Installation Guide
5-4
- PageQueryCleanupInterval – The time (in minutes) to clean up any
paged query jobs. If you are using paged queries, ignore this field.
Default value is 20.
- PageQueryCacheDuration – The time (in minutes) to keep any paged
query jobs in the cache. If you are using paged queries, ignore this field.
Default is 20.
- AppServerConnectionKeepAlive Interval – The interval (in minutes) the
fusion server should tell the license server about its existence.
Notification Web Service Tab
This tab is used to configure the login (fusion connection information)
portion of Fusion Notification Web Service.
SmtpServer - Name of the SMTP server.
The SMTP server is running on the local computer and is therefore set to
localhost.
SmtpUid - Name of the user account connecting to the SMTP server.
SmtpPwd - Password for the user account.
Fusion Connection - Name of the database connection you use to access
the application data.
Example: GMEE
FusionUserType - Type of user connecting to Fusion.
Business Process Engine log and configuration files
5-5
Example: user
FusionUser ID - Name of the user account connecting to the SMTP server.
Example: admin
Fusion Password - User account password.
Example: manage
LogSource - Name of the Fusion log source file.
Example: FusionNotification
LogName - Name of the Fusion Notification log source.
Example: FusionNotificationLog
LogMachineName - Name of the computer to store the logs on.
Set to the local computer, or localhost.
DefaultFromAddress - The default “from” e-mail account that appears in
the “from” field of any e-mails sent by the Notification service.
Example: demo@localhost
Business Process Engine log and
configuration files
All BPEngine configuration, Log files, and executable files are located in:
C:\Program Files\FrontRange Solutions\FRSApplication\BPEngine
BPEngine.log - Logs everything from DEBUG, INFO, WARNING,
ERROR
BPEngineError.log - Logs only errors, but is otherwise the same as the
BPEngine.log file
BPService.exe.config - Configuration file of the BP Configuration Utility.
One key configuration value to modify is the log level for BP engine. Out
of the box, it is set for “INFO”. To log more details information, you can
set it to “DEBUG”. <level value="INFO" />
Schema Files that can be changed by customers
Business process package used in GMEE must be consistent with meta
data defined in GMEE. When meta data is changed, a new schema must
Installation Guide
5-6
be generated so that Business Process engine can be in synch with meta
data.
To create the fusion schema file:
1. Open the GMEE Administrator Client.
2. Select File>Generate Schema
3. Name the file ‘fusion.xsd’ to C:\Program Files\FrontRange
Solutions\FRSApplication\GMEE\BPPackages
Fusion Query – Any query that is used by the Business Process Engine
will need to be exposed through ‘FusionQuery.xsd’ in:
Fusion Quick Action – Any Quick Action that is used by the Business
Process Engine will need to be exposed through ‘FusionQuickAction.xsd’
in:
Configuring User Account for the BPService Windows Service
5-7
Configuring User Account for the BPService
Windows Service
By default the account is ‘Local System account’ but other users can be
configured. User will need to permission rights to read MSMQ and make
Web Service calls.
Installation Guide
5-8
BPService MSMQ Dependency
If the Business Process Engine does not display, check the MSMQ and
make sure it is running. The BPEngine depends on MSMQ.
FSMTService Configuration
Messaging Service
The FSMTService messaging service, controls the processes that use
messages to communicate between the Foundation and an external Web
service.
To start messaging, open the Services dialog box from your Microsoft
Windows Administrative Tools, navigate to FSMTService, right-click,
and select Start. Once started, the service monitors from those items
activated on the Server Settings – Messaging dialog box, Listeners/
Invokers tab.
FSMTServiceConfiguration
5-9
Configuration
Configure messaging from the Server Settings - Messaging dialog box in
FRS Application Administrator’s System Settings.
This dialog box is divided into two tabs:
• General: Information about the messaging Web service and error
logging settings.
• Listeners and Invokers: Settings for listeners that monitor possible
incoming messages, and settings for invokers that process arriving
messages.
General Tab
• Location of the service: The server hosting the messaging service.
• Log Level: The types of messages to log for this service, including
Information (general events), Warning (events of possible disruption),
Error (events disrupting the service), and Verbose (detailed
descriptions of application processing events).
• Log Source: The location where the event is logged (Event Viewer).
• Location: The path to the source where events are logged.
Installation Guide
5-10
• Audit Messages: Includes an audit trail of all messages in the log files.
• Request Queue: The name of the server that sends messages.
• Response Queue: The name of the server that receives messages.
Listeners and Invokers Tab
• Name: The name of the listener or invoker.
• Type: The type of listener or invoker; for example, a file listener and an
e-mail listener.
• Description: A description of the listener’s or invoker’s purpose.
• Invoker to Use: The invoker that processes the message the listener
finds.
• Log Location: The log file path for this listener’s or invoker’s event
logging.
• Audit Messages: Includes an audit trail of all messages going through
the listener or invoker.
• Add Button: Add a new listener or invoker.
• Delete Button: Delete the selected listener or invoker.
Running BP Engine on a Separate Machine
5-11
• Activate Button: Ready the listener or invoker for use.
• Deactivate Button: Disable the listener or invoker for use.
• Set Parameters Button: Specify how the data is monitored by the
selected listener or invoker.
• Set Transformations Button: Specify the XSLT file that translates the
data into proper Foundation XML schema.
• Note: Restart the Messaging service (FSMTService) to apply new
settings or recently activated listeners or invokers.
Listener and Invoker Parameters
Each listener and invoker type has a specialized set of parameters that
determine how the data is monitored.
To set parameters, select a listener or invoker on the Server Settings Messaging dialog box, Listeners/Invokers tab, and click Set Parameters.
• E-mail Listener Parameters: Monitors an e-mail server, looking for new
messages to process. The parameters specify the server to monitor and
the actions after processing the message.
• File Listener Parameters: Monitors a network location, looking for new
XML files to process. The parameters specify the directory to monitor
and the actions after processing the file.
• LDAP Listener Parameters: Monitors applications communicating with
an LDAP protocol (for example, Active Directory). The parameters
specify the directory to monitor and the actions after processing the
object.
Example: Use LDAP to communicate between Active Directory and the
Foundation to update users in the system from Active Directory.
• Fusion Invoker Parameters: Performs transactions for a given request
message in XML format that conforms to the specified XML schema.
Under this configuration the FRS Application Server and the Web
Services will be running in one machine and the BP Engine alone will be
running on another machine as shown below:
Installation Guide
5-12
• Software installation requirements for the machine where the
AppServer/Web Services will be running:
GMEE Server installed and running.
Configure the FusionBOWS and FusionNotification as per the docs.
Make sure the Web Services are up and running in an application pool
different from the App Server as recommended before.
• Software installation requirements for the machine where the BP
Engine will be running:
FRS BP Engine is installed.
RDBMS Client software is installed and can connect with the RDBMS
Server and Database.
MSMQ Service is up and running
Network connection between the above two machines.
• Configure the Event Queue Settings:
Administrator tool >System Settings>Server Settings
Click the Business Process
5-13
In the Event Queue Settings screen type in the name of the machine
where the BP Engine will be running (example: usa.ex.corp-1)
Save the settings.
Please note that the application may not show an error if this machine
name is configured incorrectly.
• Edit the following Web Services files in the machine where the BP
Engine will be running as follows:
Edit the file FusionBOWS.wsdl and FusionNotification.wsdl file under
the folder $INTALLDIR/FRSApplication/BPEngine.
This is to ensure the BP Engine can communicate with the Web Services
(FusionBOWS and FusionNotification) running in some other machine.
Change the “localhost” to the machine where the web services will be
running (example: usa.ex.corp-1) in the element <wsdl:port> under
<wsdl:service>
• BP Engine configuration:
Make sure the persistence database connection string in the
BPService.exe.config file is pointing to the correct BPE RDBMS Server
and database
Make sure the BP Engine package path, package name and the log files
are configured for the local paths.
• Stop and restart the BP Engine.
Installation Guide
5-14
6
Knowledge Management
Configuration
Knowledge Management Server Configuration
To use Knowledge Management, the module requires some additional
configuration after installation.
1. From All Programs>FrontRange Solutions>GMEE, open GMEE Administrator.
2. Go to System Settings>Module Registration.
3. Select Settings for the KnowledgeManagement module.
6-2
Select tcp:// or http://
Enter your server name.
Add Port 2242 as an exemption to your firewall settings unless you
want to change it here.
Connect as user can be left as administrator (this is case-sensitive) with
a password of manage, or you can change the Server Credentials by
clicking the button and entering new information.
Select the Default Interaction Business Object for Knowledge
Management, this is the object GMEE will interact with Knowledge
Management. Incident is usually the default for this setting.
4. Click the Search icon.
6-3
5. Select the default Business Object that will appear in all sections of the
KM configuration areas in the top container. Once that has been done,
select the Search Type that you would like to use by default, and also
the Advanced search option for this Business object. Once this is
complete, you can specify the fields in which the search will take
information from to search the KM base. Do this step for each Business
Object to be included in the Knowledge Base. Click Apply after each
objects field selection.
6. Click the Auto Population icon
Installation Guide
6-4
7. Use this area to create new articles for different Business Objects. You
can define the fields for each category of each tab. Click Apply.
8. Click the Manage Content Collection icon.
6-5
9. Use this section to manage how your content will be organized. You
can add existing Content collections, Collection Folders, Document
Folders, ODBC Folders, and File system folders. Besides being able to
add files, you can also arrange files by moving them up or down or
into different locations. Click Apply.
10. Click the Thesaurus and Stop Words icon.
Installation Guide
6-6
11. Select your Language, Editor Program and enter the path to the
KnowledgeManagement\bin folder. You can also edit your Stop
Words and Thesaurus from this location. Click Apply.
12. Click the Categories icon.
6-7
13. Use this section to manage your categories within the Knowledge
Management database. You can add or remove and also rename
existing categories. Once a category is in use and contains one or more
articles, do not modify an article, as it will lose its placeholder. Click
Apply.
14. Click Workflow States and Usage Weights.
Installation Guide
6-8
15. Use this section to define your workflow states by adding or changing.
Assign numeric values to the usage weights according to what you
view as a weight when an article is viewed, printed, or used as a
problem solved. Click Apply.
16. Click the Survey Responses icon.
6-9
17. You can define the surveys you would like to conduct. These surveys
are accessed through the web client side of KM. Click Apply.
18. Click the Resolution icon.
Installation Guide
6-10
19. Here you can define the field in which the resolution will be posted by
the Business Object. Click Apply.
Select Append to add the resolution text to the contents of the field, or
Overwrite to replace the contents of the field with the resolution text.
20. Click the Plug-In Manager icon.
6-11
21. Your Plug-Ins should all be set to Idle and Automatic. This will ensure
that the system will always be functioning at any given time. The
Document Auto Archive plug-ins is configurable by selecting and
clicking the Configure Plug-In button. This will allow you to change or
modify the schedule for archiving data from Knowledge. Click Apply.
22. Click the Top Solutions icon.
Installation Guide
6-12
23. Use this area to define Top Solutions that will be displayed in
Knowledge Management. Click Apply.
24. Click the E-mail Settings icon.
6-13
25. Use this area to define e-mail settings. You can select either Enable Email capabilities which uses the company email server, or Use
Notification Server Settings, which uses the settings that you have
defined in the Notification settings in Administrator to send email.
26. Click Apply and OK, exit the Knowledge Management Settings and
close Module Registration.
27. Go into the Security Group Manager to associate the Knowledge
Management license with the Administrators group. Select the Roles
tab for Administrators.
Installation Guide
6-14
28. For the Admin role, click the Edit button on the Advanced tab. In the
section Associated Licenses: scroll down until you reach Knowledge.
Check this box to enable.
29.Click Apply, and then Close. This will return you to the main Security
Group Manager dialog.
30.On the Administrators Security Group, go to the KBPermissions tab.
6-15
31.Highlight the Knowledge Base Server (top of tree) and select the
checkboxes for the specific rights you would like to have. (This will
apply all these rights to the entire tree) You can also select different
parts of the tree to assign specific rights to each part. Click Apply when
completed.
32.Exit Administrator.
Using Windows Explorer, find the DefaultACM.ini file on the server at
C:\Program Files\FrontRange Solutions\KnowledgeManagement\bin
folder.
Installation Guide
6-16
1. Right-click the DefaultACM.ini file and select Properties>Security tab.
Add “Everyone” and “Local Service” with Full Control.
2. Click OK and exit.
7
Configuring GMEE
This chapter explains how to configure some GMEE features for your users after
installation.
Auto Deploy (ClickOnce)
The Auto Deployment feature, also known as ClickOnce, lets you and your users
launch GMEE by clicking a Launch GMEE link. As an administrator, you can also
access the GMEE Application Administrator in the same manner.
To set up the Auto Deployment feature, use the following procedure.
Note: Make sure that the GMEE Server is installed before following this procedure.
To set up Auto Deployment for GMEE
1. Access the following URL:
http://localhost/FRSAppServer/ (change the machine name accordingly).
7-2
Configuring GMEE
2. At the FrontRange Application Suite window, click Download
Prerequisites and click setup.
3. At the FrontRange Auto Deployment Pre-requisite install Setup
Wizard, click the Repair FrontRange Auto Deploy Pre-requisite install
radio button.
AutoDeploy(ClickOnce)
7-3
If the install is successful, the Installation Complete window appears.
Click Close.
4. If you are using Outlook integration, at the FrontRange Application
Suite window, click Outlook Integration Install and then click Run.
5. At the Wizard for FrontRangeOutlookIntegration window, click Next.
Installation Guide
7-4
Configuring GMEE
6. At the License Agreement window, accept the license agreement and
click Next.
7. At the Setup Type window, select the type (Complete is
recommended) and click Next.
AutoDeploy(ClickOnce)
7-5
8. At the Ready to Install window, click Install.
9. At the Installation Completed window, click Finish.
10. Type issreset and click Run.
You can now click the Launch GoldMine Enterprise Edition link to
open GMEE.
Setting Up Auto Deployment for the GMEE
Application Administrator
You can also configure Auto Deployment for the GMEE Application
Administrator.
1. Make sure the Prerequisites are downloaded to your machine.
Installation Guide
7-6
Configuring GMEE
2. At the FrontRange Application Suite window, click the launch the
FrontRange Administrator link to open the GMEE Application
Administrator.
3. At the dialog window, select the GMEE database and click OK.
4. To eliminate the dialog window and go directly to the GMEE
application, set up the AutoConnect URL.
• Click the Default.htm file and open in an editor such as Notepad.
• Modify the URL so that AutoConnect=true. Copy all text after the ?
symbol and copy into the Orion.apploader as shown here:
Change
http://localhost/FRSAppServer/AutoDeploy/AppLoader/
Orion.Apploader.application?AutoConnectConnectionName=FRS3
TierConnectonName&ClickOnceDeploy=true&AutoConnect=false
&AutoConnectDescription=FRSApplication&AutoConnectAppServ
erUrl=
to
http://localhost/FRSAppServer/AutoDeploy/AppLoader/
Orion.Apploader.application?AutoConnectConnectionName=FRS3
TierConnectonName&ClickOnceDeploy=true&AutoConnect=true&
AutoConnectDescription=FRSApplication&AutoConnectAppSerer
Url=
5. Type issreset and click Run.
Security
7-7
You can now open the GMEE Application Administrator by clicking
the launch the FrontRange Administrator link.
Security
It is important to set up the appropriate Security rights for your
company’s GMEE users. You set up Security rights in the same manner as
for other FRS applications. For more information and basic procedures to
set up Security rights, see the Foundation Administration Reference Guide.
Briefly, to set up the Security rights, open the FRS Application
Administrator - GMEE. At the Navigator pane on the left side of the
screen, select Common Tasks>Security Group Manager.
Note: The Self Service Security group is not applicable in GMEE v6.3.1. It
has been replaced by the Customer Self Service security group.
The left side of the screen is a list of roles. Select a group or create a new
group, then click the tabs in the following table.
Tab
Description
General
The role and a description are generated in the
Name and Description fields. To change the
description, edit the existing text and click
Apply.
Installation Guide
7-8
Configuring GMEE
Tab
Description
Module Rights
Allows you to select the global rights for the
group, controlling what tasks a person in the
group can perform. For example, you can
select whether the role should have the right to
export a FAD file.
Select a category and at the Rights area,
select all rights you need and then click Apply.
Object Rights
Allows you to select the objects for which the
group has rights to execute QuickAction and/or
Templates actions.
Select the action Type and at the Objects
Rights area, select the objects, the object
actions and then click Apply.
Business Objects
Allows you to select Business Object actions
for which the group has rights to execute
Business Object actions.
At the Available Business Objects box, select
the Business Object, select the actions and
then click Apply.
Users
Allows you to add or remove users to a group.
Select the user and click Move into Group or
Move out of Group and then click Apply.
Roles
Allows you to add roles to a group.
Select a role, click Add and complete the Add
a New Role wizard.
You can also set up a new Security record from
a similar existing record using the Clone
QuickAction.
User Profiles
Set up profiles of all of your company’s GMEE users. You can add new
users and provide internal authentication. For more information and
basic procedures to set up User profiles, see the Foundation Administration
Reference Guide.
UserProfiles
7-9
To set up the Security rights, open the FRS Application Administrator GMEE. At the Navigator pane on the left side of the screen, select
Common Tasks>User Manager.
Select a name or position from the left side of the screen. To create a new
user profile, complete the fields in the following table.
Field
Description
Logon ID
The user logon ID. Enter a login ID for the user.
Security group
The security group of the new user. Select a
group from the drop-down list.
Business group
The business group of the new user. Select a
group from the drop-down list.
Track presence
Tracks the user’s actions. Click the checkbox
to select.
Internal tab
Select fields to authenticate the user internally.
Select a login ID and password.
Windows authentication
tab
Click the Allow Windows Integrated
authentication checkbox to authenticate the
user on Windows. Select a Windows ID.
Installation Guide
7-10
Configuring GMEE
Field
Description
PubCookies tab
Select the Allow PubCookies authentication
(for SelfService only) checkbox to authenticate
the user. Select a PubCookies ID.
Click the Extended tab to complete the Employee detail window. For
more information on completing the Employee form, see the GMEE User
Guide.
Settings
You should configure the general settings for GMEE. These settings
include hours of operations, attachments files, servers for reports and so
on.
For more information and basic procedures to configure settings, see the
Foundation Administration Reference Guide.
Configuring Microsoft Distributed Transaction
Coordinator (MS DTC)
The MSDTC is a transaction manager that coordinates transactions that
span multiple resource managers, such as Message Queuing and
Microsoft SQL Server. MS DTC is automatically installed when Message
Queuing is installed.
You need to configure the MSDTC to ensure that whenever you make a
change to an object in GMEE it is propagated to the Business Processes
Engine (BPE).
Configuring MSDTC
1. At the Microsoft start menu, navigate to Settings>Control
Panel>Administrative Tools>Component Services.
Configuring Microsoft Distributed Transaction Coordinator (MS DTC)
7-11
2. At the Console Root pane, select Component Services.
If a window pops up that blocks you from the window, click Unblock.
3. Right-click My Computer and select Properties.
4. Click the MSDTC tab and then click the Security Configuration button.
5. Click all the checkboxes to activate and then click OK and then click
OK again.
6. Restart your computer.
Installation Guide
7-12
Configuring GMEE

GoldMine Install Guide PDF

Transcription

Similar documents

Atlantis Energy Systems Inc.

Regions CD Check Viewer Installation Guide

KV “ANDENES” - KV “SENJA” - KV “NORDKAPP”

QuadraTec™ - Auralex Acoustics

Products_files/6 (catalogo DECO PROJECTS.EN)

aerocet 6650 installation pricing

Glass instructions

model vp180.b5 - Visiport Spin Window Systems

Brochure - Sonoma Tilemakers

Company Profile