Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Integration Service

TABLE OF CONTENTS

Generic Data Source

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedMay 09, 2025
  • 2 minute read

Any application (Data Provider) registers itself by providing a unique identifier (Data Source Name) through the AVEVA Integration Service Config API or AVEVA Integration Service Web Admin UI. This identifier serves as a key for organizing and managing the associated data.

To create new Generic Data Source, open AVEVA Integration Service Web Admin URL in your browser.

  1. Click Add Data Sources button.

  2. Specify Name of your data source.

  3. Select Product as Generic from the drop-down

  4. Specify the Project Name, the value can be null or empty.

  5. Enter Description for your data source, the value can be null or empty.

    Note: Use JSON string to add structured description.

    Note: This feature is only available in AVEVA Integration Service Web Admin not in AVEVA Integration Service Settings Editor

Functionality

Generic Data Source Creation:

  • Any application (Data Provider) registers itself by providing a unique identifier (Data Source Name) through the AVEVA Integration Service Config API or AVEVA Integration Service Web Admin UI.

  • This identifier serves as a key for organizing and managing the associated data.

Data Upload and Publishing:

  • The Data Provider uploads data to the AVEVA Integration Service Data API, specifying the Data Source Name of the Generic Data Source and including a context for the data.

  • Registered Data Providers upload JSON data to the API.

  • Each upload generates a unique ACKID and temporarily stores the data in the database.

  • A contextual comment describing the uploaded data can be added.

Message via SignalR:

  • The Data API validates that the data is in proper JSON and stores the data temporarily in the database. A unique ACKID is generated for each upload.

  • The API uses SignalR to publish a message on the topic named after the Data Source Name. This message notifies subscribers that new data is available, including the context, ACKID or reference to the data.

Data Retrieval:

  • Subscribers can access and download the data using the ACKID provided in the message.

Handling Large Data:

  • The API supports uploading large datasets in paginated chunks using PATCH MEMO requests.

TitleResults for “How to create a CRG?”Also Available in