> For the complete documentation index, see [llms.txt](https://docs.videc.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videc.de/june5-3.7/en/datenquellenunterstuetzung-und-einbindung/june5-batch-connector/konfiguration.md).
# Configuration
#### Background:
When configuring an endpoint for the [JUNE5 Batch Connector](/june5-3.7/en/webanwendung/datenquellen/endpunkt-anlegen/june5-batch-connector.md), a SQL database must be specified that contains the unit batch headers. You can also define up to four different subordinate JUNE5 servers that provide process data and events to the unit batch headers. The batch header data is obtained with the help of an SQL command. This SQL command is editable and can be edited when configuring the [JUNE5 batch data source](/june5-3.7/en/webanwendung/datenquellen/datenquellen-konfigurieren.md). How this command is defined is described in the subsection [SQL Command Unit Batch Header Data](/june5-3.7/en/datenquellenunterstuetzung-und-einbindung/june5-batch-connector/sql-befehl-unit-batch-headerdaten.md). The structure of the tables with batch header data is described in the subsection [SQL Table Batch Header](/june5-3.7/en/datenquellenunterstuetzung-und-einbindung/june5-batch-connector/sql-tabelle-batch-header.md).
{% hint style="info" %}
This configuration refers to a target server (ServerCA for Customer A).
{% endhint %}
## Step 1 (JUNE5 Batch Connector):
Create, configure, and test a JUNE5 Batch Connector data source.
### Step 1.1 (Data Source Endpoint)
**Example configuration for the data source endpoint on ServerCA for Customer A**
* Identification: JUNE5\_Batch\_CA
* Name: JUNE5 Batch Customer A
* Database instance: localhost\JUNE5Portal
* Database name: BatchHeaderCA
* Provider name: SQLOLEDB
* Username and password or integrated Windows security
Perform a connection test to ensure the connection is working properly.
| | |
| - | - |
| 
|
| ------------------------------------------------------------------- |
### Step 1.2 (Server Batch Data)
**Example configuration for the Berlin source on ServerCA for Customer A**
* Server URL: portal.videc.info
* Location: Berlin
* Username and password
* Authentication
* NA name and NA ID
Up to four locations can be defined. Only define the locations for a customer where batches for that customer are also produced.
| | |
| - | - |
| 
|
| ------------------------------------------------------------------- |
#### Authentication
In authentication, a distinction is made between *Basic* and *NamedAccess*. By default, this setting is *Basic*. Switching to *NamedAccess* can only occur after the endpoint is saved.
### Step 1.3 (Configure Data Source)
Under "Configure data source" perform the following actions:
* Select the data source from the endpoint selection "JUNE5 Batch CA (JUNE5 Batch Customer A)"
* Enable one row and set clear designations:
Identification = MyBatch
Name = MyBatch\
Enabled = true
* Save these settings
| | |
| - | - |
| 
|
| ------------------------------------------------------------------- |
{% hint style="info" %}
* The configuration on ServerCA for Customer A is now complete.
* If necessary, restart the JUNE5 Server and check that all changes have been applied.
{% endhint %}
## Step 2 (Verify Data)
Test the JUNE5 batch data under "Views" by creating a new batch object. If necessary, adjust the time period if no batches are displayed for the current time period.
For the data defined in the use case, the list of transferred batches must now be displayed for Customer A.
| | |
| - | - |
| 
|
| ------------------------------------------------------------------- |
When the batch is analyzed, the JUNE5 Batch Connector establishes the connection to the source and retrieves the data for the measurement values.
| | |
| - | - |
| 
|
| ------------------------------------------------------------------- |
The measurement values (DataSourceKeys) shown in this use case are the same for each batch. This does not have to be the case in every use case. It is entirely possible that certain batches will have more or fewer measurement values displayed. The list of measurement values is dynamic depending on the subordinate batch system.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.videc.de/june5-3.7/en/datenquellenunterstuetzung-und-einbindung/june5-batch-connector/konfiguration.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.