Skip to content
No description, website, or topics provided.
JavaScript Dockerfile
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
assets extend readme Aug 27, 2019
lib remove old line Sep 11, 2019
test
.eslintrc.js linting Jun 12, 2019
.gitignore initial Jun 11, 2019
Dockerfile
Logo.png
README.md
component.json add actiont to component.json Aug 16, 2019
jest.config.js
logo.png
package-lock.json addTests [#551](openintegrationhub/openintegrationhub#551) Jul 25, 2019
package.json

README.md

The Smart Data Framework Adapter (SDF-Adapter) allows flows to communicate with the smart data framework. It is responsible for forwarding the incoming events to the smart data framework. Furthermore, it is responsbile for increasing the ease of use for connector developers as it masks service endpoints.

Entrypoint

The SDF-Adpater is triggered by incoming events received from either the preceding adapter or the transformer (depending on oih operator configuration).

Message Processing

Send Message to Open Integration Hub

If a message arrives from the preceding component it is forwared to the correct service(s)/queue(s). One possible recipient of the forwarded message is the dispatcher component.

sdfAdapter

If scenario 1 is realized it is necessary that the sdf adapter provides meta information in order to clearly identify the data set after it has been pushed onto the queue.

The following snippet shows an example of a dataset that has been processed by the sdf adapter:

{
    "meta":{
        "domainId":"123",
        "schemaUri":"/collaboration/task.json",
        "recordUid":"456",
        "applicationUid":"ab1",
        "iamToken":"ddfdsfsdf5-sdfsdfsdfsdf6",
    },
    "data":{
        "oihUid": "567",
        "oihApplicationRecords": [
        {
          "applicationUid": "123",
          "recordUid": "201306",
        },
        ],
        "substasks": [
        {
            "task": "Analyze system 1",
            "details": {
                "subject": "analysis",
                "startdate": "2018-01-01T10:10:10Z",
                "enddate": "2018-03-01T10:10:10Z",
                "reminderdate": "2018-02-01T10:10:10Z",
                "content": "To create a datamodel we have to analyze system 1...",
                "status": "in progress",
            },
        },
        {
            "task": "Analyze system 2",
            "details": {
                "subject": "analysis",
                "startdate": "2018-01-01T10:10:10Z",
                "enddate": "2018-03-01T10:10:10Z",
                "reminderdate": "2018-02-01T10:10:10Z",
                "content": "To create a datamodel we have to analyze system 2...",
                "status": "in progress",
            },
        },
      ],
        "details": {
            "task": "Analyze systems",
            "details": {
                "subject": "analysis",
                "startdate": "2018-01-01T10:10:10Z",
                "enddate": "2018-03-01T10:10:10Z",
                "reminderdate": "2018-02-01T10:10:10Z",
                "content": "To create a datamodel we have to analyze system 1...",
                "status": "in progress",
            },
        },
    },
}

Send recordUid to Open Integration Hub

The SDF Adapter also takes care of sending the recordUid generated by the preceding to the SDF for ID Linking. In order to properly link the recordUid generated by the target application to the correct oih data record SDF Adapter also send the encrypted oihuid as well as the applicationId to the SDF.

The figure below illustrates an end to end process:

e2e

The following snippet shows the structure of the object that is emitted by this function:

{
    "meta": {
      "oihUid": "abc",
      "applicationUid": "Its easy as",
      "recordUid": "123",
    },
    "data":{
        "emptyPayload"
    }
}
You can’t perform that action at this time.