> 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/honeywell-experion-batch-heb/konfiguration.md).
# Configuration
The HEB Connector is configured in three steps that build on each other.
## Step 1 (PHD):
Create, configure, and test a [PHD data source](/june5-3.7/en/datenquellenunterstuetzung-und-einbindung/honeywell-uniformance-process-history-database-phd/konfiguration.md).
### Step 1.1 (Data Source Endpoint)
#### Example configuration for the data source endpoint:
* Identification: HEB\_PHD
* Name: HEB Process Data
* Server hostname: ServerPHD (The server name or computer name of the PHD Server)
* Port number: 3100
* User and password
| | |
| - | - |
| 
|
| ------------------------------------------------------------------- |
### Step 1.2 (Configure Data Source)
Under "Configure Data Source" perform the following actions:
* Select the data source from the endpoint selection "HEB Process Data (HEB\_PHD)"
* Modify the identification, name, and enabled flag in this row:
Identification = HEB\_PHD
Name = HEB Process Data\
Enabled = true
* Save these settings
| | |
| - | - |
| 
|
| ------------------------------------------------------------------- |
### Step 1.3 (Browse Data Source)
Under "Browse Data Source" perform the following actions:
* Select the data source from the endpoint selection "HEB Process Data (HEB\_PHD)". The time before PHD variables are displayed depends on the number of variables and the speed of the PHD Server.
* Enable all PHD variables that are relevant to you. If necessary, all variables can also be selected.
* Save these settings
| | |
| - | - |
| 
|
| ------------------------------------------------------------------- |
### Step 1.4 (Test PHD Data):
Test the PHD data under "Views" by creating a new chart object. If necessary, modify the time range if no process data is displayed for the current time range.
## Step 2 (Microsoft OLE DB):
Create, configure, and test an [OLE DB data source](/june5-3.7/en/webanwendung/datenquellen/endpunkt-anlegen/microsoft-ole-db.md) for events. The Microsoft OLE DB data source is a general-purpose interface. For the HEB definition, the "ProcedureAnalyst" database of the Honeywell system is used for events. See Step 2.1.
### Step 2.1 (Data Source Endpoint)
Configure the data source endpoint with the identification "HEB\_Event" for OLE DB access to the Honeywell Server. Fill in all fields of the configuration for "HEB\_Event".
#### Example configuration for the data source endpoint:
* Identification: HEB\_Event
* Name: HEB Events
* Initial Catalog required = enabled
* Database instance name: ServerHWE (The server name or computer name of the HW Server)
* Provider name: SQLOLEDB
* User and password
Subsequently save the settings and perform a connection test.
Optionally, the command for "SQL Command Database List" can be modified to the following if the appropriate rights exist on the source database:
SELECT \* FROM sys.databases WHERE Name = ProcedureAnalyst
| | |
| - | - |
| 
|
| ------------------------------------------------------------------- |
### Step 2.2 (Configure Data Source)
Under "Configure Data Source" perform the following actions:
* Select the data source from the endpoint selection "HEB Events (HEB\_Event)"
* Go to the row with the database "ProcedureAnalyst" and modify the identification, name, and enabled flag in this row:
Identification = HEB\_Event
Name = HEB Events\
Enabled = true
* Save these settings
| | |
| - | - |
| 
|
| ------------------------------------------------------------------- |
Go to the "Event Configuration" button
* Select the event configuration and modify the SQL string. Copy the SQL string from "[SQL Command Events](/june5-3.7/en/datenquellenunterstuetzung-und-einbindung/honeywell-experion-batch-heb/sql-befehl-ereignisse.md)"
* Enable the checkbox "Column names are provided by the user..." and copy the SQL command into the SQL Command Events field.
* After pasting, click the "Determine Column Names" button
* Enable the column configuration for the following alias names:
| **Alias Name** | **Column Name** |
| -------------- | --------------- |
| From | Starttime |
| To | Endtime |
| Namespace | Namespace |
| Item-ID | Lotnumber |
| | |
| - | - |
| 
|
| ------------------------------------------------------------------- |
{% hint style="info" %}
At least these four columns (Starttime, Endtime, Namespace, and Lotnumber) must be defined.
{% endhint %}
* Click the "Apply" button
* Save the settings.
{% hint style="info" %}
**3.2 RC3:**
This intermediate step of logging out and back in is only necessary for 3.2 RC3.
* Log out
* Log back in
{% endhint %}
### Step 2.3 (Test Event Data):
Test the events under "Views" by creating a new event object. If multiple event data sources are defined, you may receive an error message here. Therefore, limit the event display to the "HEB\_Event" event data source.
Go to the "Properties" of the event object and select only the data source with the ID "HEB\_Event" in the "Event Source Selection".
If necessary, modify the time range if no data is available for the current time range.
## Step 3 (HEB)
Create, configure, and test an HEB data source for batches. For the HEB definition, the "ProcedureAnalyst" database of the Honeywell system is used for batches. See Step 3.1.
### Step 3.1 (Data Source Endpoint)
Configure the data source endpoint with the identification "HEB\_Batch" for HEB access. Fill in all fields of the configuration for "HEB\_Batch".
#### Example configuration for the data source endpoint:
* Identification: HEB\_Batch
* Name: HEB Batch
* Database instance name: ServerHWE (The server name or computer name of the HW Server)
* Provider name: SQLOLEDB
* User and password
* PHD Data Source Identification: HEB\_PHD
* OLE DB Data Source Identification: HEB\_Event
| | |
| - | - |
| 
|
| ------------------------------------------------------------------- |
### Step 3.2 (Configure Data Source)
Under "Configure Data Source" perform the following actions:
* Select the data source from the endpoint selection "HEB Batch (HEB\_Batch)"
* Go to the row with the database "ProcedureAnalyst" and modify the identification, name, and enabled flag in this row:
Identification = HEB\_Batch
Name = HEB Batch\
Enabled = true
* Save these settings
| | |
| - | - |
| 
|
| ------------------------------------------------------------------- |
For the "SQL Command Unit-Batch" and "SQL Command PHD Variable List" buttons, no further settings are necessary. The SQL commands stored here generally do not need to be modified.
### Step 3.3 (Test Batch Data):
Test the batch data under "Views" by creating a new batch object. If necessary, modify the time range if no batch information is displayed for the current time range.
Select a batch and then click "Analyze". The measurement data for the batch should be displayed. The "Events" tab displays the events for the batch.
---
# 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/honeywell-experion-batch-heb/konfiguration.md?ask=
```
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.