> 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/webanwendung/datenquellen/endpunkt-anlegen/june5-batch-connector.md).

# JUNE5 Batch Connector

For the configuration of this endpoint, two tabs are displayed. On the first tab labeled "Server Batch-Header", you must enter the login credentials of a SQL Server that contains the batch header data to be retrieved. On the second tab labeled "Server Batch-Data", by default only one subordinate tab is displayed, but its number can be increased to four. On each subordinate tab, you must define the login credentials of a JUNE5 Server that is used to retrieve the measurements and events of the batch header data from the SQL database.

### Name

In this input field, a symbolic name of the newly created endpoint is entered.

### Identification

A unique identification is entered here.

### Enabled

If the check box is set, the JUNE5 Batch endpoint is enabled. Otherwise the endpoint remains disabled.

### Optional Parameters

Special parameters can be entered here. In general, this field remains empty.

## Server Batch Header Data

### Test Connection

Using the *Test Connection* button, the connection to the entered SQL Server can be tested.

### Enabled

The setting can be enabled or disabled via the check box.

### Windows Integrated Security

The check box is enabled if the username and password do not need to be explicitly entered for authentication. In this case, the Windows credentials of the user under which the JUNE5 Web server service is running are used. This user must have sufficient rights to read the data from the SQL databases. If access is not local and the SQL Server and JUNE5 Server are not in the same domain, users with identical credentials can be created on both computers to use Windows integrated security for this user.

### UTC Timestamp

The check box is enabled if the SQL Server evaluates input and output times as UTC times.

### Database Instance Name

In this input field, a name must be specified to uniquely identify the SQL Server instance. This name can be a computer name or can consist of a computer name followed by a backslash and the instance name.

For example: ComputerName\SQLExpress, localhost\SQLExpress or ComputerName.

### Database Name

In this input field, the name of the database with the unit batch headers must be specified.

For example: BatchHeader

### Provider Name

The name of the SQL provider is entered here.

For example: MSOLEDBSQL

### Username

In this input field, the name of a user who has sufficient permissions to read the data from the SQL Server databases is entered.

### Password

The password for the user specified in the Username field is entered in this field.

Input fields of subordinate JUNE5 Servers

## Server Batch Data

### Test Connection

Using the *Test Connection* button, the connection to the entered server can be tested.

### Enabled

The setting can be enabled or disabled via the check box.

### Server URL

In this input field, the URL of a subordinate server must be entered.

### Location

In this input field, the name of the location must be entered.

### Username

In this input field, the username of a user from the specified subordinate server is entered.

### Password

In this field, the password corresponding to the selected user must be entered.

### Authentication

From the dropdown list field located directly below the "Authentication" label, select an authentication method that is used when checking the integrity of the user. Two authentication methods are supported:

* **Basic**: The specified username and password are always used during the login process.
* **Named Access**: After successful authentication, a channel is reserved for the user. This gives the user the option to log in via the named access assigned to them at any time.

### NA Name

In this input field, you can enter a symbolic name for the newly registered named access.

### NA ID

In this input field, the identification of the named access is displayed. The contents of this field are automatically generated and cannot be edited.

### Register

This button is used to register a channel for the endpoint. During registration, the credentials stored in the fields for the user and password are used. Registration can only occur after the endpoint has been saved.

### Remove Registration

This button is used to undo a registration.

{% hint style="info" %}

* Please note that a JUNE5 user with appropriate rights is set up on the server to be connected to.
* When saving or subsequently changing the settings, all required fields must be filled in.
* Required fields are those fields whose left border is marked in red.
  {% endhint %}


---

# 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/webanwendung/datenquellen/endpunkt-anlegen/june5-batch-connector.md?ask=<question>
```

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.