> 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/defining-the-source-data-location.md).

# Defining the source data location

### Introduction

This procedure describes how to define the source data location.

If the source file (containing the source data) is located on the Command Centre server PC, all folders must be located on the Command Centre server PC and not a network drive.

If the source file (containing the source data) is located on a network drive, you will need to specify the Windows logon used to access the drive. It is recommended that the Windows logon specified is an account created specifically for the purpose of automated data transfers, and is not a standard user account where the password may get changed, or may have more privileges on the network than required.

If the source data is located in a database, you will need to specify the IP address of the database PC and the logon used to access the database.

### Procedure

1. Click the **Data Location** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8f631beec27382c801eb78114d8a008f487897fb%2Fdatalocationtab.png?alt=media)
2. Where is the source data located?

   <table><thead><tr><th width="210">If...</th><th>then...</th></tr></thead><tbody><tr><td>locally on the Gallagher Command Centre server PC,</td><td><ol><li>Ensure <strong>Local file</strong> is selected in the <strong>Location type</strong> drop-down list.</li><li>Enter the source folder path into the <strong>Source folder</strong> field.</li><li><p>Enter the source file name into the <strong>File name</strong> field.</p><p><strong>Note:</strong> If you don't know the source file name, or you want to import more than one source file, you can use wildcard characters, refer to <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/defining-the-source-data-location/wildcard-characters.md">Wildcard characters</a>.</p></li><li>Enter the completed folder path into the <strong>Completed folder</strong> field.</li><li>Enter the failed folder path into the <strong>Failed folder</strong> field, if required.</li><li>If you are importing cardholder images, enter the image folder path into the <strong>Image folder</strong> field.<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5feb63075f219cdc82fe79b514846aec6f3f3df6%2Fdatalocationtab_localfile.png?alt=media" alt=""></li></ol></td></tr><tr><td>on other network location(s),</td><td><ol><li><p>Select <strong>Network Share</strong> from the <strong>Location type</strong> drop-down list.</p><p>The "Details" section of this screen allows you to specify either a single network logon or different network logons for each of the folders if required.</p><p>Windows networking only allows for one username at a time to connect to a Windows file server from within a Windows session. Subsequent connections to the same server with different usernames are refused with Windows system error 1219: The credentials supplied conflict with an existing set of credentials. For this reason, EDI will refuse to connect to the same share with different usernames.</p><p><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-afbd9878cbe845bda2afa616e03e373741457874%2Fdatalocationtab_networkshare.png?alt=media" alt=""></p></li><li><p>Complete the fields as appropriate, (e.g. you may have a single user, multiple users, one network location or multiple network locations).</p><p>The following <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/defining-the-source-data-location/examples.md">Examples</a> help explain how to setup this screen depending on your situation.</p><p><strong>Notes:</strong></p><ul><li>A common logon can be used for some or all of the folders, (e.g. if one logon is used for all network locations, only the <strong>Username</strong> and <strong>Password</strong> fields at the top of the screen need completing).</li><li>If the same <strong>Username</strong> is used for two folder locations, and the second folder location has an incorrect <strong>Password</strong>, the job may still complete if EDI only needs one network connection to reach both locations. If the first location is later changed, the incorrect password may be exposed when EDI uses the credentials of the second folder location to connect to the second location.</li></ul></li></ol></td></tr><tr><td>in a database,</td><td><ol><li>Select <strong>Database</strong> from the <strong>Location type</strong> drop-down list.</li><li>Select the database type from the <strong>Database Type</strong> drop-down list.</li><li>Enter the database server name or IP address into the <strong>Server</strong> field (maximum 64 characters).</li><li>Enter the user name, used to connect to the database into the <strong>Username</strong> field (maximum 64 characters). This field is case sensitive.</li><li>Enter the user password into the <strong>Password</strong> field (maximum 64 characters). This field is case sensitive.</li><li>If required, select the <strong>Test Connection</strong> button. This can be used to validate the connection details entered.</li><li>If you have selected Microsoft SQL Server as the database type, select the database from the <strong>Database Name</strong> drop-down list.</li><li><p>Select a table/view from the database that will be used as the main source for data importing, from the <strong>Data Source Name</strong> drop-down list.</p><p><strong>Note:</strong> This drop-down lists the tables followed by the views that the user can view.</p></li><li>If you are importing cardholder images, enter the image folder path (local pathway) into the <strong>Image Folder</strong> field.</li><li>Enter the log folder path (local pathway) into the <strong>Log Folder</strong> field, if required.</li><li>Optionally, you can execute a stored procedure before the processing of records begins or at the end of processing records. The drop-down lists will display all selectable stored procedures that the logging user has privileges for.<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a56a8aea4499c2f1f5199205995c7ff01181b32b%2Fdatabaseinfo.png?alt=media" alt=""></li></ol></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/defining-the-source-data-location.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.
