> 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/licensable-features/enterprise-data-interface.md).

# Enterprise Data Interface

### Introduction

Welcome to Enterprise Data Interface.

Enterprise Data Interface provides the ability to import cardholder data or booking data (timetable data) into Command Centre. Data can be imported from either a source file or a database.

A Cardholder Interface can be configured in Enterprise Data Interface to add, update or remove cardholders in Command Centre.

A Booking Interface can be configured in Enterprise Data Interface to update bookable resources configured in Command Centre.

**Note:** The Booking Interface option will only be available if your site has the "Bookable Resources" licensable feature installed also.

In order to configure an interface, source data fields must be mapped to Gallagher Command Centre fields. Once configured, an interface can be run manually (at any time), run according to a schedule or run in sequence.

***

### Licensing

Enterprise Data Interface is a licensed feature of Gallagher Command Centre.

The following table details the licensing structure:

<table><thead><tr><th width="316">License entry</th><th>is required when...</th></tr></thead><tbody><tr><td><code>EnterpriseDataInterface=1</code></td><td>importing cardholders from a file.</td></tr><tr><td><code>ScheduleEnterpriseDataInterface=1</code></td><td>scheduling an interface or adding an interface to an execution sequence.</td></tr><tr><td><code>EDI-CardholderDatabase=1</code></td><td>importing cardholders from a database.</td></tr><tr><td><code>EDI-BookingDatabase=1</code></td><td>importing bookings from a database.</td></tr><tr><td><code>EDI-BookingFile=1</code></td><td>importing bookings from a file.</td></tr></tbody></table>

***

### Supported Databases

Enterprise Data Interface supports importing data from the following databases:

* Oracle Database Express Edition 19c

  **Note:** If you want to use the Oracle Database feature you will need to perform the following procedure, otherwise Command Centre will fail to connect to the Oracle Database using EDI:

  1. Navigate to C:\Program Files (x86)\Gallagher\Command Centre\Bin.
  2. Back up **Oracle.ManagedDataAccess.dll** into another folder in the file system.
  3. Stop Command Centre services.
  4. Copy **Oracle.ManagedDataAccess.dll** (v4.122.19.1) into C:\Program Files (x86)\Gallagher\Command Centre\Bin, overwriting the existing file.
  5. Start Command Centre services.

  Try entering the server name as SERVER/SERVICE.

  If the data point is named DATA and the server is Orastage, in EDI the server would be listed as Orastage/DATA, and if they are using a custom port, (e.g. 4443), then the server would be Orastage:4443/DATA.
* Microsoft SQL Server 2008 R2
* Microsoft SQL Server 2014


---

# 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/licensable-features/enterprise-data-interface.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.
