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

# acron

acron is a special case among endpoints. The acron endpoint is always available and is the only endpoint that cannot be deleted.

The following input fields (required fields) are described below:

### 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 acron endpoint is enabled. Otherwise the endpoint remains disabled.

### Optional Parameters

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

## acron Installations (Table)

With the *Plus button*, additional acron installations can be added. In general, JUNE5 is operated with only one acron version. In exceptional cases, up to two different acron installation paths can be selected here. A combination of two different acron versions is possible, for example:

* acron Version 8.3 and another 9.3 version
* acron Version 9.2 and another 10.x version

### Display Fields acron Installations

The # is an internal sequential number and can be ignored. If an update of acron is performed with multiple acron installations, the number must remain the same as the previous acron installation.

### Enabled

If the check box is set, the acron installation is enabled. When the JUNE5-ACRON-Service starts, it will attempt to determine all acron systems from this installation path.

### acron API Path

The path for the acron installation. If additional acron installations exist, the respective acron installation path should be clearly identifiable. For example:

C:\Program Files\ACRON84

C:\Program Files\ACRON85

### acron Version (API Version)

The internal acron API version is displayed here. If this field is empty, the acron API version cannot be determined. Check that the acron database server is running for the respective acron installation.

### Registry

Indicates whether the acron installation was taken from the registry or directly from the path specification.

### Test Connection

Using the corresponding *Test Connection* button, the connection to a specific acron installation can be tested.

#### Delete

Using the corresponding *Delete button*, an acron installation can be removed or deleted.

{% hint style="info" %}

* If the acron API version is not displayed, please check that at least one acron database server is running for each acron installation.
* If necessary, restart the JUNE5-ACRON-Service and check the log file for errors.
* The acron system ID must be unique across all acron installations. An acron system ID "DEMOSTD" may only occur in one acron installation.
  {% 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/acron.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.