GGP Installations - Installing GGP – GGP Systems Help Center

This guide outlines the steps for installing and configuring GGP software.

💽 Installing GGP

Please read the entire section before beginning installation.

GGP can be installed:

As a standalone application (typically on laptops or single-user workstations)
On a network for multiple users

You can use the GGP installation CD to either:

Install GGP on a machine for the first time
Upgrade an existing GGP installation

If 'Autorun' is enabled on your CD drive, the GGP installation will launch automatically.

If the installation does not start automatically:
Navigate to the CD directory and run **SETUP.EXE**.

Running SETUP.EXE initiates the installation process.

⚠️ Important Setup Behaviour

💡 Tip

When opening SETUP.EXE later, it will also display the version information of the currently installed program.

This version info is only shown when SETUP.EXE is run from the root of the distribution image. If launched from another directory, the version details will not be visible.

🖥️ Setup Location Recommendations

Note: In most cases, do not run Setup directly on the server where GGP is locally installed.

SETUP.EXE is designed for use on client machines, connecting to the GGP installation on the server.
Exception: It is acceptable to run Setup on a standalone laptop installation, where using local drive letters isn’t problematic.
Another exception exists for peer-to-peer networks, where GGP is accessed remotely from a laptop acting as a server.

🌐 Shared Operation and Path Format

When Setup is run on the server, it displays the install path using a drive letter (e.g., D:\GGPWIN).

For shared, multi-user environments, it’s recommended to use:

An Environment Variable path (preferred), or
A UNC path (e.g., \\ServerName\GGPWIN)

These formats ensure consistent access across all users and machines.

⚙️ Global Settings

This section describes the core settings you must configure during the GGP installation process.

📁 GGP Program Path

Specify the directory where GGP files will be installed.

You can type the name of a new folder or browse to an existing one.
Recommendation: Use the default folder name GGPWIN to assist technical support and ensure consistency.

🔐 Licence Folder

Set the directory where GGP licence files will be stored.

This folder must have full read-write access, especially in a network setup.

How licensing works:

GGP verifies that the license path at runtime matches the one used during installation.
On fixed or network drives, this path is usually stable.
On removable drives (e.g., USB sticks), drive letters may vary across machines or sessions.

To support removable devices:

GGP ignores the drive letter and validates the folder path only.
You can map a stable drive letter using:
- Environment Variables (e.g., Q:)
- The SUBST command
  Example:
  SUBST Q: X:\
  (where X: is the current letter for the removable drive)

📝 OS SLA Licence

To comply with the Ordnance Survey licence agreement:

Enter your OS licence number during installation.
If you don’t have it yet, leave it blank and edit it later in the GGP.INI file.

See the GGP Configuration File documentation for more details.

🔄 Clone 2009 DB as New 2014 DB

This feature helps users migrating from GGP 2009 to GGP 2014.

It clones your 2009 database and creates a new 2014 version, retaining all existing data.
You may continue using your 2009 DB while beginning work with the 2014 DB.
You can choose a custom name for the new database.
The new database will be created on the same server as the 2009 one, using similar connection parameters.

🗃️ System Database Setup

Required for GGP 2014 and above

From version 2014 onward, GGP requires a system database to store essential installation metadata.

💾 Supported Database Types

You can use one of the following database systems:

SQL Server
Oracle
PostGIS
SQLite (default for local installations)

⚠️ Pre-Setup Requirements

Before clicking the System Database Setup button for the first time, ensure that:

✅ The Program Path and Licence Folder have been defined
✅ If using SQL Server, Oracle, or PostGIS, the database must already be created in your DBMS

⚙️ Default Behaviour

For local machines, GGP will default to using SQLite and automatically create a file called:
GGP_SYS.DB3
in the Licence Folder you specified earlier.
For network or remote installations, the default expectation is a SQL Server system database.

🧩 Launching the Setup Dialog

Click the System Database Setup button in the installer to open the Database Connections Dialog, where you can:

Specify connection settings
Test connectivity
Complete the setup process for your selected database engine

🧷 Completing System Database Setup

After configuring your connection:

Click OK to save and proceed.

📝 Notes on the System Database Dialog

The primary purpose of the System Database Setup dialog is to:

Generate a ConnectionString
Save it into the LOCK.INI file, under the [Database] section with the key:
ConnectionString=...

⚠️ If this field is empty and you press Next, you will receive a warning dialog, and the installer will not proceed.

🔄 Clearing the `ConnectionString`

Depending on your DBMS, here’s how to clear the connection:

SQL Server / Oracle: Clear the Database Name field.
PostGIS: On the [Edit] > Connection tab, clear the Data Source Name (without running Test Connection).
SQLite: Simply clear the Database field.

🔐 PostGIS Security Caution

Avoid entering username and password directly in the connection string:

These values are stored in plain text if entered in the dialog.
Instead, configure credentials via:
Data Sources (ODBC) > System DSN > Configure
(This method keeps them hidden and secure.)

This also applies when configuring MasterMap connections and user layer connections.

🛠 Create/Repair `GGP.INI`

During installation, the system will:

Copy a GGP.INI file to %APPDATA%\GGPWIN
If a copy already exists, it will be updated

📌 When to Use "Create/Repair"

Use this function to:

Repair a user's local GGP.INI file
Ensure the [Directories] GGPDir key reflects the current setup

GGPDir serves two roles:

Allows external applications to locate the GGP PROGRAMS folder
Helps GGP executables (run outside of PROGRAMS) find the system LOCK.INI file

This option is also accessible from the GMAIN32 interface for convenience.

🛠 Modify Settings and Exit

Use this option when:

You want to change configuration paths or DB connection settings
But do not need to run an installation

Important: Before choosing this, always run System Database Setup first to ensure the ConnectionString is set.

What this option does:

Repairs LOCK.INI by ensuring it contains:
- [Directories] LockDir
- [General] OSLicense
Then runs Create/Repair GGP.INI
Finally, exits Setup

🔄 Update and Transfer Gemini Metadata

This tool migrates existing metadata from older GGP versions to the latest supported format.

🌐 Enable FDO (Feature Data Objects)

This checkbox becomes available after FDO is installed
When checked, it enables global FDO import/export functionality

See the FDO Setup article for details.

✅ Continuing the Installation

Once all Global Settings are completed, click Next to continue to the next stage of the installation process.

For existing installations, the Backup option lets you protect your data before continuing.

New Installation

Click Next to proceed to the next step of the new installation.

After choosing the options you want to install with GGP, click Install to proceed. This will transfer the program and its supporting files from the source location (e.g., CD) to the designated program folder.

📁 Files to Include in the Installation

📖 Help Files
Choose whether to install GGP’s help system. It’s recommended to leave this option selected unless you have a specific reason not to.

🌐 FDO
FDO Data Access Technology is an API designed for manipulating, defining, and analyzing geospatial information, regardless of its storage location. It uses a provider-based model to support various geospatial data sources, with each provider typically handling a specific data format or data store.

Selecting Install FDO will create an fdobin folder within your GGP installation, containing the necessary files to use FDO. However, this does not enable FDO functionality by default. To activate it, you must check the Enable FDO option. You can enable or disable FDO anytime later from the Global Settings page after installation.

🗂️ ArcSDE DLLs
If you want to use the ArcSDE FDO provider, you need to specify the path to your licensed ArcSDE DLLs. Click the Browse to location of your ArcSDEDlls button, navigate to the folder containing the DLL files, and select it. The chosen path will appear on the Install Page. After confirming it is correct, check the Install ArcSDE DLLs box to include them in the installation.

🔄 Upgrade an Existing Installation
Click Next to proceed to the page where you can select what needs to be installed and where.

🔍 Installation Process and Options

As part of the installation, GGP checks if an existing version is installed and identifies its version. If an older installation is found, GGP will prompt you to either:

Overwrite existing Programs folder: Install over the current installation.
Install to a separate sub-directory: Create a new installation in a different folder.

This feature allows you to create a parallel Test or Training environment if needed.

After completing a new installation or returning to this page with a valid NLPG admin user, checkboxes for additional programs will be enabled.

📄 Installation Report

Once all installation steps are complete, GGP will display an Installation Report.

Click Save if you want to keep a record of the files copied during installation.
Then select OK and Exit to close the installation program.

You are now ready to configure your GGP installation.

⚙️ Configuring Your GGP Installation

Navigate to the GGPWIN\PROGRAMS directory.
Create a shortcut to GMAIN32.EXE (the GGP Applications Launcher) on your Start menu or desktop.

Important:
The first time you open the application, use the Run command and add /CREATEINSTALL to the command line to initialize the installation.

Remove this switch after the initial run; otherwise, the application will not start.
Upon first launch, you will see an option to set up security.

For upgrades from GGP 2009 to GGP 2014, use the Run command with /MIGRATE2014 added to the command line.

▶️ Next Steps

After installation, create a desktop icon pointing to GMAIN32.EXE (the GGP Application Launcher).
If desired, set up icons pointing directly to GGP32.EXE to allow users to run GGP without the launcher, though this is optional.

Recommendation:
Use the GGP Application Launcher as it provides a user-friendly interface to access all main GGP components.

Note:
Avoid running GMAIN32.EXE or other GGP client applications directly on the GIS server. If this is unavoidable (e.g., in small peer-to-peer networks):

In the Shared Folders group:
1. Clear the Save shared folders with UNC/Environment Variable aliases if they exist checkbox.
2. For shared folders pointing to remote locations mapped locally, toggle the folder path to UNC format or Environment Variable format where applicable.
3. Click OK to save DEPARTMENT.INI settings.
4. Restart GMAIN32 and verify shared folders are set correctly.

This also applies to Personal.INI shared folder override settings.

🚀 Commissioning Your Installation

You have now loaded GGP and can proceed with commissioning by following these help topics:

User Control Overview
Setting up Departments
Commissioning Users
Installing Ordnance Survey Data

🗂️ GGP Program Components and Executables

File Name	Program Element
ATFED_32.EXE	Setup Application
DATAVW32.EXE	Data Viewer
FRMDES32.EXE	Form Designer
IMLOAD32.EXE	Raster Loader
MAPADM32.EXE	Map Administration
MMLoader.exe	MasterMap Loader
SYMED32.EXE	Symbol Editor
GGP32.EXE	GGP for Windows
GGP.CHM	GGP Help

🛠️ Other Prerequisites

To perform backup or restore operations of spatial database overlays stored in MS SQL Server, you need to install the full Microsoft SQL Server 2008 R2 Command Line Utilities (or equivalent). This installs the BCP.EXE tool, required locally to back up overlays in addition to global security settings.

GGP searches for BCP.EXE in these default locations:

C:\Program Files\Microsoft SQL Server\100\Tools\Binn (SQL Server 2008)
C:\Program Files\Microsoft SQL Server\110\Tools\Binn (SQL Server 2012, on Windows 7 PCs only)