> 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/configuring-an-interface/generating-source-data.md).

# Generating source data

### Introduction

The source data for a Cardholder Interface should contain the cardholder records you wish to add, update or remove in Command Centre. The source data for a Booking Interface should contain the bookings for the bookable resources in Command Centre.

The source data must originate from either a source file, (e.g. CSV file) or a database (Oracle or Microsoft SQL Server).

### Enterprise Data Interface folders

When importing data into Command Centre you will need to create the appropriate folders, as detailed in the following topics. It is recommended that you create one set of folders for the Cardholder Interfaces and another set of folders for the Booking Interfaces.

**Note:** In new installs of the Command Centre service account ("Network Service"), modify access permission must be granted to the Source, Image, Completed and Failed folders. This also applies to updates from versions prior to vEL7.70 where "Network Service" has been selected on install.

#### Importing data from a source file

If the source file is located on the local Command Centre server PC, you will need to create the following folders on the local Command Centre server PC.

If the source file is located on a remote PC, you will need to create the following folders on the remote PC. The remote PC must be setup and made available to the Command Centre server PC.

The interface will "pick-up" and process the source file from the source folder directory.

**Notes:**

* It is recommended you name the folders as shown below.
* It is recommended that your company limits access to these folders, only allowing certain people or services access to the folder locations.
* The image folder is not required for a Booking Interface.

  <table><thead><tr><th width="120">Folder Name</th><th>Description</th></tr></thead><tbody><tr><td>Source</td><td>This is where the interface will retrieve the source file from.</td></tr><tr><td>Completed</td><td>This is where the processed source file will be moved to, regardless of success.</td></tr><tr><td>Failed (optional)</td><td><p>The unsuccessfully imported cardholder records will be copied to a new file and placed in this folder.</p><p>If this folder does not exist, the failed file will be placed in the completed folder.</p></td></tr><tr><td>Image (optional)</td><td><p>This is where the interface will retrieve the cardholder images from. The successfully imported images will be moved to the completed folder.</p><p>Images that have failed to be imported or are not specified in the source file will remain in this folder.</p><p>It is recommended that you supply only the images that require importing to this folder, not images that have already been imported. This will show you what was not processed by Enterprise Data Interface.</p><p>If you are not importing images, this folder is not required.</p></td></tr></tbody></table>

#### Importing from a database

If the source data is located in a database, you will need to create the following folders on the local Command Centre server PC.

**Note:** The image folder is not required for a Booking Interface.

<table><thead><tr><th width="120">Folder Name</th><th>Description</th></tr></thead><tbody><tr><td>Log</td><td>The import log file will be saved to this directory.</td></tr><tr><td>Image (optional)</td><td><p>This is where the interface will retrieve the cardholder images from. The successfully imported images will be moved to the processed folder. The processed folder resides in the image folder directory. If not already present, the processed folder is automatically created when the interface is run.</p><p>Images that have failed to be imported or are not specified in the source data will remain in this folder.</p><p>It is recommended that you supply only the images that require importing to this folder, not images that have already been imported. This will show you what was not processed by Enterprise Data Interface.</p><p>If you are not importing images, this folder is not required.</p></td></tr></tbody></table>


---

# 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/configuring-an-interface/generating-source-data.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.
