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

# Configuration Prerequisites

Configuration prerequisites are necessary for the JUNE5 Batch Connector to operate properly.\
The configuration prerequisites of the JUNE5 Batch Connector are performed in several steps, which build on each other.

## Step 1 (Check Source):

Background: The source is a JUNE5 web server that provides batch data to JUNE5.DataTrans.

For the source, ensure the following points and check them in sequence.

#### Prerequisites on the Source:

* URL address, IP address, or server hostname including the port number of the source must be known
* Access credentials for the source (username and password)
* Batch data. These must be visible when directly calling the address with the access credentials.

Log in to the source and create a batch object to ensure that batch data exists.

## Step 2 (Check Target):

Background: The target is a SQL Server. The target can thus also be the SQL Server instance of a JUNE5 server.

For the target, ensure the following points and check them in sequence.

Prerequisites on the Target:

* The server hostname for SQL Server access must be known
* Access credentials for SQL Server (username and password or Windows authentication)

## Step 3 (JUNE5.DataTrans):

Create, configure, and test the source and target in JUNE5.DataTrans.

### Step 3.1 (JUNE5.DataTrans Installation)

* Installation of JUNE5.DataTrans
* Calling up the JUNE5.DataTrans Configurator
* Setting up an administrator account (username and password)
* Setting up a username (username and password)

The installation and basic setup of JUNE5.DataTrans is not described in detail here as it is part of JUNE5.DataTrans. Installation is typically not performed on the source or target system but, as described in the use case, between source and target.

### Step 3.1 (Define Source)

**Example configuration for the Berlin source:**

* Name: BER
* Server hostname: <https://portal.videc.info>
* Username and password

Perform a connection test to ensure a connection can be established.

|   |   |
| - | - |

| <img src="/files/v0v048cqZ1m9Ad1ENrfq" alt="" data-size="original"> |
| ------------------------------------------------------------------- |

### Step 3.2 (Define Target)

**Example configuration for the Customer A target:**

* Name: Customer A
* Server: ServerCA\JUNE5Portal
* Database: BatchHeaderCA
* Provider name: SQLOLEDB

|   |   |
| - | - |

| <img src="/files/X19OEBWYlxUTE7tBmcgA" alt="" data-size="original"> |
| ------------------------------------------------------------------- |

{% hint style="info" %}
The database name was changed from BatchHeader to BatchHeaderCA so that with multiple targets, the database is not named the same everywhere. With data backup across multiple databases, each customer has their own database name.
{% endhint %}

### Step 3.3 (Define Variable Filter)

**Example configuration for all variables**

* Name: VarFilterAll
* Apply to: All
* Filter expression: \*

|   |   |
| - | - |

| <img src="/files/NU2OfOsz0NMEaukNBf3Q" alt="" data-size="original"> |
| ------------------------------------------------------------------- |

### Step 3.4 (Define Time Interval)

**Example configuration for all time intervals**

* Name: TriggerBatch
* Interval: 1 minute
* Time period: 1 minute

|   |   |
| - | - |

| <img src="/files/WTN33zKFhIiCMGIEQDJd" alt="" data-size="original"> |
| ------------------------------------------------------------------- |

{% hint style="info" %}
The setting in minutes is suitable for testing and commissioning. In ongoing operation, a trigger in hours or days is more practical since the transmission of batch headers from the source to JUNE5.DataTrans is not time-critical.
{% endhint %}

### Step 3.5 (Define Users)

**Example configuration for two users**

* Name: User1 and User2
* Email: <user1@email.de> and <user2@email.de>

|   |   |
| - | - |

| <img src="/files/olIw79MRfdqVpLMduYOO" alt="" data-size="original"> |
| ------------------------------------------------------------------- |

### Step 3.6 (Define Group)

**Example configuration for a group**

* Group name: GroupBatch
* User1 and User2 are added to the group

|   |   |
| - | - |

| <img src="/files/5kUD1cYpDw9YaPrFxCWu" alt="" data-size="original"> |
| ------------------------------------------------------------------- |

### Step 3.7 (Define Job Template)

**Example configuration for a job template**

* Name: OrderBER
* Output format: Batch Portal
* Variable filter: VarFilterAll
* Condensation level: Process (default)
* Priority: Normal (default)
* Time interval: TriggerBatch
* Location: Berlin (This name is used for security and appears in the database for Customer A)

|   |   |
| - | - |

| <img src="/files/xbggdSIRi7exdVNBIOvY" alt="" data-size="original"> |
| ------------------------------------------------------------------- |

|   |   |
| - | - |

| <img src="/files/Sg03uDWLtsIcL9ljEssD" alt="" data-size="original"> |
| ------------------------------------------------------------------- |

## Step 4 (JUNE5.DataTrans Jobs):

All jobs that have not yet been transferred are displayed in JUNE5.DataTrans. The transfer is done manually since it is typically not known which batch belongs to which customer.

|   |   |
| - | - |

| <img src="/files/4tDXG9K2j3FQQVxtmVii" alt="" data-size="original"> |
| ------------------------------------------------------------------- |

Transferring a batch with JUNE5.DataTrans from source to target is done by selecting (double-clicking) a job from the list.

### Step 4.1 (JUNE5.DataTrans Transfer Job)

* Select a job
* Choose the target (Exporter / Target)
* Verify the target once more and click apply

A play button is displayed. This can be pressed in this dialog or in the job overview.

|   |   |
| - | - |

| <img src="/files/N2i4TKNPkvzYPsCCnaB4" alt="" data-size="original"> |
| ------------------------------------------------------------------- |

|   |   |
| - | - |

| <img src="/files/CgrDvGJiNPtfbQmilaq4" alt="" data-size="original"> |
| ------------------------------------------------------------------- |

When the job is being processed, the job is displayed in orange. The export delay is now running. If an error occurs, this row is displayed in red. A green row is only displayed briefly.

|   |   |
| - | - |

| <img src="/files/BjMIzY8h9ZvuozXtYY2V" alt="" data-size="original"> |
| ------------------------------------------------------------------- |

The job has now been transferred and is stored as batch header information in the target.

Computer = "ServerCA"

Database = "BatchHeaderCA"

### Step 4.2 (JUNE5.DataTrans Check Job)

To check if the job has arrived on the target, you can check this with the Management Console of the SQL Server or with PowerShell.

* Check on the target system (ServerCA)

|   |   |
| - | - |

| <img src="/files/R6eCTQ3rbQ3F3L9luCJM" alt="" data-size="original"> |
| ------------------------------------------------------------------- |

Only when it is ensured that this transfer with JUNE5.DataTrans works can the JUNE5 Batch Connector operate.


---

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