> 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.md).

# JUNE5 Batch Connector

The JUNE5 Batch Connector provides batch data from subordinate JUNE5 servers to the client. Information is exchanged between subordinate JUNE5 servers and local JUNE5 servers using a client-server model. Within this model, the JUNE5 Batch Connector acts as the client. The subordinate JUNE5 server acts as the server. Additionally, the JUNE5 Batch Connector works with a local SQL Server to obtain the list of batch header data. The data flow is complex and is illustrated using a use case.

The JUNE5 Batch Connector should only be used when the following conditions exist:

* Production data is highly sensitive data, and strict separation of access is required.
* Each customer is provided with a computing unit (RE) or virtual machine (VM). This RE contains access credentials for only one customer.
* Within the RE for a customer, batch header data is stored in the local SQL Server of this RE.
* Only batch data can be retrieved from the RE. All other JUNE5 functions are only available to the customer in a limited way.

The following client functionalities are supported by the JUNE5 Batch Connector.

* Query the list of unit batch headers from a local SQL Server
* Query the measurement values of a selected unit batch header
* Query the events of a selected unit batch header

### JUNE5 Source Server

A JUNE5 source server defines the production location where batches are produced for multiple customers. The source server provides its data only via the WebAPI server interface to an overlying JUNE5 Batch Connector.

### JUNE5 Customer Server

A JUNE5 customer server defines the customer portal where the customer sees only the batches that were produced for them. Only batch header data is stored locally here.

{% hint style="info" %}
The terms "Batch", "Charge", and "Lot" all mean the same thing. Depending on the industry, one or the other term is used.
{% endhint %}

### Definition of Batch Header Data

Batch header data are rows of information that serve to uniquely identify a unit batch within the overall system. A batch header consists of several partial pieces of information.

### Operation

The JUNE5 Batch Connector operates in three stages:

#### Stage 1:

Reading locally stored unit batch header information. This information is displayed from the local SQL database.

#### Stage 2:

Verification of the selected unit batch header with unit batch headers from the subordinate JUNE5 server for the following properties:

* Namespace
* Batch number
* Start time
* End time

#### Stage 3:

Reading process data and, if applicable, events from the subordinate JUNE5 server and display in the user interface.

The JUNE5 Batch Connector can only communicate with a subordinate JUNE5 server when the following conditions are met:

### On the Source (Server)

* The version of the subordinate JUNE5 server is equal to or higher than version 3.1 SP3
* JUNE5 license (Enterprise) with the Web Service Interface option (Order No. JUNE5-OPTN-API).

### On the Client (JUNE5 Batch Connector)

* JUNE5 license (Enterprise) with the Batch option (Order No. JUNE5-OPTN-BAO).

Once connections to the SQL Server and subordinate JUNE5 servers are established, unit batch headers with process data and events can be displayed in a batch object.

Port number of the JUNE5 server

{% hint style="info" %}
The firewall must be configured by IT so that the SQL Server and subordinate JUNE5 server are accessible via remote access on the network.

* By default, data traffic to a standard instance of a SQL Server is handled via port 1433.
* Data traffic to a named instance of a SQL Server occurs via dynamic ports.
  {% endhint %}

## Authentication

In authentication, a distinction is made between *Basic* and *NamedAccess*. By default, this setting is *Basic*. Registration of an endpoint for named access can only occur after the endpoint is saved.


---

# 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.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.