Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(uml):[#xxx] optimize concept reducing unnesessary information a… #1365

Merged
merged 2 commits into from
Aug 30, 2024
Merged

chore(uml):[#xxx] optimize concept reducing unnesessary information a… #1365

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
854bc8a
chore(uml):[#xxx] optimize concept reducing unnesessary information a…
mkanal Aug 30, 2024
881e19e
chore(docs): add missing description
ds-jhartmann Aug 30, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 11 additions & 9 deletions docs/src/uml-diagrams/arc42/runtime-view/data-consumption-process_part1_tracex_scaling.puml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,18 +5,21 @@ participant TraceXFE
participant TraceX
participant "DiscoveryService" as DS
participant "Eclipse Dataspace Connector" as EDC
participant "Digital Twin Registry" as DTR
participant "decentral Digital Twin Registry" as DTR

participant IRS
rnote right TraceX
Blackbox view on EDC
end rnote
TraceX -> DS: Get EDCS for BPN
DS -> TraceX: Provide EDC Urls
TraceX -> EDC: Query for catalog offer of DTR
EDC -> TraceX: Return catalog offer
TraceX -> EDC: Negotiation of contract
EDC -> TraceX: Complete negotiation
ref over TraceX, DS
EDC discovery
end ref

ref over TraceX, EDC, DTR
Get catalog offer of DTR and negotiate it
end ref


TraceX -> DTR: Query for aasIDs by bpn
DTR -> TraceX: Retrieve aasIDs by bpn
rnote right TraceX
Expand All @@ -25,8 +28,7 @@ Because we need to know the BOMLifecycle Type (asBuilt/asPlanned) before request
Then for each BOMLifecycle Type we do two requests (upward/downward) to the IRS job API
end rnote
rnote right TraceX
Optimization: Since IRS can autodetect the BOMLifecycle Type. TraceX could simply use the aasID to reduce a huge amount of load to the EDC / DTR
Afterwards we switching from the IRS Job API to the IRS Order APi which lets us define batch strategies and call IRS only two times (upward/downward) for all aasIDs
Optimization: Trace-X uses digitaltwinregistry.externalSubjectIdWildcardAllowedTypes = digitalTwinType in dtr query to detect bom lifecycle.
end rnote
TraceX -> IRS: Register order for parts to get semantic models and traversal aspects for all aasIds (e.g. 200.000)
rnote right TraceX
Expand Down
Loading