> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/configuring-an-external-system-server/installing-the-ftcapi-middleware-framework-fmf.md).

# Installing the FTCAPI Middleware Framework (FMF)

### Introduction

This topic describes how to install the FTCAPI Middleware Framework.

If your site is licensed for FTCAPI middleware plug-ins, each middleware PC must have the FTCAPI Middleware Framework installed. Perform the following procedure on each middleware PC:

**Note:** Microsoft.NET Framework 4.7.2 is required on the middleware PC.

### Procedure

1. Run the executable **FMFSetup\_8.xx.xx.msi** located in the `Utilities\System Interfaces\Middleware Framework vMF8.xx.xx` folder of the Gallagher Command Centre installation files.

   The FTCAPI Middleware Framework Installer wizard displays.
2. Click the **Next** button on each wizard screen, and then the **Finish** button on the final screen.

   The following are installed on the middleware PC:

   * The Gallagher FTCAPI Middleware Framework.
   * A new service named FTCAPI Router Service. It will need to be manually started first time. This service needs to remain running to enable FTCAPI functionality.
3. The directory `C:\ProgramData\Gallagher\Command Centre` will be created as soon as you start the service. You need to enable "Show hidden files, folders and drives" in **Control Panel** > **Folder Options** to see it.

   Copy your Command Centre license file ( **Command Centre.lic** ) into that folder.
4. Ensure the middleware PC's Firewall is configured to allow the FTCAPI to listen on port 1073.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/configuring-an-external-system-server/installing-the-ftcapi-middleware-framework-fmf.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
