> 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.md).

# Configuring an External System Server

### Introduction

The normal setup procedure of an External System Server is to:

1. Install FTCAPI Middleware Framework to create keys. See [Installing the FTCAPI Middleware Framework (FMF)](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) for detailed instructions.
2. Import the **GallagherFTCAPI.pem** certificate into Command Centre via the External System Server’s **Setup** tab.
3. Export the **GallagherFTCAPI.ini** configuration file from Command Centre via the External System Server’s **Setup** tab.
4. Copy the configuration file to FTCAPI install folder.

**Note:** The External/DVR System is assigned to the External System Server item via the **API Setup** property page on the External System or DVR System items.

* It is possible to configure multiple External Systems and/or DVR Systems on each External System Server.
* The External System Server must be configured for all pre-7.80 Controller 6000s.
* Each External System and DVR System must have a External System Server configured in the **API Setup** property page from v7.80 onwards, or the external interface will not function.

### Procedure

1. Click **Configure** from the menu bar, then **External Systems**.

   The **External Systems** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. **Right click** and select **New\...External System Server**.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the **Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-aca248952b1505594bc2eea65c6cf1b507d8fe27%2Fcontrollerapihost_setuptab.png?alt=media)
5. Enter the Middleware PCs name or IP Address in the **Host Name** field. This field is limited to 255 alpha-numeric characters.
6. Enter the FTCAPI listening Port that the External System (or DVR System) is configured on in the **Port** field.
7. The **Import Certificate** button allows you to import the FTCAPI certificate ( **GallagherFTCAPI.pem** ) from the PC containing the FTCAPI.

   This is so the FTCAPI will be allowed to send messages through to Command Centre via the Controller.

   **Notes:**

   * Once you import the FTCAPI certificate, the **Export Configuration...** button is enabled.
   * If you select an invalid certificate, the **Clear Certificate** button becomes enabled. Clicking it allows you to click on **OK** or **Apply** without the invalid certificate being imported.
   * If you are using a pre-v7.80 version of FTCAPI, then you copy the server's licence file onto the FTCAPI machine instead of importing keys and exporting configuration.

     You only do Steps 7 and 8 for a 7.80 FTCAPI (or later).
8. You can export the **GallagherFTCAPI.ini** configuration file that can then be copied into the `GallagherFTCAPI` folder of your FTCAPI machine.

   This allows the FTCAPI to be used and you can then send events to Command Centre. Without this **.ini** file, the API will not work.

   **Note:** The private key ( **GallagherFTCAPI.key** ) and configuration file ( **GallagherFTCAPI.ini** ) can be placed in the middleware application folder instead of the FTCAPI folder if you want to have more than one middleware application installed on the same machine.
9. Click the **Custom Fields** tab if you want to add and assign a custom field value to this External System Server.

   For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
10. Click the **Notes** tab if you want to add a note(s) about this External System Server.

    For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
11. Click **OK** to exit and save your changes.

    Click **Cancel** to exit without saving your changes.

    Click **Apply** to save your changes and stay in this window.

### Result

A new External System Server has been created and displays at the root level of the External Systems window.

### In This Section

* [Installing the FTCAPI Middleware Framework (FMF)](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)


---

# 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.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.
