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

# Honeywell HEB

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

### Name

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

### Identification

In this input field, a name must be entered to uniquely identify the newly created endpoint within the <%PRODUCT\_NAME%> system.

### Enabled

If the check box is set, the Honeywell HEB endpoint is enabled. Otherwise the endpoint remains disabled.

### Windows Integrated Security

The check box should be enabled if the username and password do not need to be explicitly entered for authentication. In this case, the Windows credentials of the currently logged-in user are used. This user must have sufficient permissions 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. In other words, there must be a user on both computers with the same username and password.

### UTC Timestamp

The check box should be enabled if the SQL Server evaluates entered times as UTC times and provides 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 database name of the SQL Server instance must be specified, for example "ProcedureAnalyst".

### Provider Name

In this input field, the name of the provider for an MS Server must be specified, for example "SQLOLEDB".

### Username

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

### Password

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

### PHD Data Source Identification

From the dropdown list field located directly below the "PHD Data Source Identification" label, select a PHD data source that contains the process data of the PHD tags of unit batches to be imported.

### OLE DB Data Source Identification

From the dropdown list field located directly below the "OLE DB Data Source Identification" label, select an OLE DB data source through which the events of unit batches to be imported are determined.

{% hint style="info" %}

* When saving or subsequently changing the setting, all required fields must be filled in.
* Required fields are those fields whose left border is marked in red.
  {% endhint %}

## Test Connection

Using the *Test Connection* button in the horizontal toolbar, the connection to the endpoint can be tested.


---

# 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/honeywell-heb.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.