Retain Connection Alive for Dabacon Data Sources

Starting version 2.3.2, AVEVA™ Integration Service (Service) provides an option to retain the connection alive for Dabacon data sources. When the Service reads data from a Dabacon data source, the corresponding product is launched in the background in TTY/headless mode. As a result, the performance of the Service is impacted because launching the product takes time. With the Keep Connection Alive feature, the Service retains the process running in the background. By retaining the connection alive, the performance of the Service is improved significantly.

The list of products where the Keep Connection Alive feature is available are:

• AVEVA™ E3D Design 2.1 and later

• AVEVA™ E3D Design 3.1 and later

• AVEVA™ E3D Design 4.0

• AVEVA™ Marine 12.1.SP5 and later

• AVEVA™ Plate & Bar Nesting 15.2 later

• AVEVA™ Engineering 15.5 and later

• AVEVA™ Diagrams 14.1.4 and later

• AVEVA™ Unified Engineering 3.0 and later.

To improve the performance of the Service for a Dabacon data source:

1. Configure the data source for your Dabacon data source.

2. After the data source has been configured, on Integration Settings Editor, select Yes for the KeepConnectionAlive column.

   Note: By default, the value is set to No.

   

3. Click Save to save the configuration.

   Important: When you keep the connection alive, you must remember that if any changes are made in the data source while the connection is alive are not retrieved. The connection must be refreshed so that the latest changes are available for the client products.

To refresh the connection:

4. For the required data source, select No for the KeepConnectionAlive column.

5. Click Save.

6. Change the value back to Yes for the KeepConnectionAlive column.

7. Click Save again. The connection is refreshed.

License Consumption

Normally, when the Service reads data from a data source, it consumes one license of the product. When the Keep Connection Alive functionality is used, one license is consumed for up to five active sessions per product. For example, if a user is trying to retrieve data from five data sources of AVEVA™ E3D Design 3.1, only one license is consumed. If the user initiates another connection with a sixth data source, then another license is consumed. Please note that if the sessions are not closed, then the corresponding licenses are not released.

Points to Note on Keep Connection Alive

• If two users are connecting to the same data source with different usernames, only one session is considered.

• If two users are connecting to the same data source, the first request is served first. The second request needs to wait till the first request is completed.

• A session is alive forever. It is closed when user stops the Service or sets the KeepConnectionAlive column value to No and saves the data source.

• If an Admin user edits data source such as the name of the data source or UID, the respective connection is closed on saving the data source. On receiving first request after the edit, the Service opens a new connection to read the data. This connection would be alive, will not be closed until explicitly done so.

• The memory consumption for the Keep Connection Alive functionality depends on the product and project. For example- AVEVA Engineering 15.6 for Project APS and ALL MDB , an alive connection consumes 14500 K RAM memory on Windows 10. Memory consumption increases when processing a request and comes down after request is processed.

• There is no limit on how many alive connections can be opened simultaneously. However, this also depends on the capacity of the server on which the Service is installed.

• If any change is done to the data source such as a new DB has been added to the MDB or a new mapping has been defined, the connection must be refreshed or the Service must be restarted.