diff --git a/docs/src/uml-diagrams/arc42/runtime-view/data-consumption-process_part1_tracex_scaling.puml b/docs/src/uml-diagrams/arc42/runtime-view/data-consumption-process_part1_tracex_scaling.puml index 8f69f3f2cd..d0e5eb3544 100644 --- a/docs/src/uml-diagrams/arc42/runtime-view/data-consumption-process_part1_tracex_scaling.puml +++ b/docs/src/uml-diagrams/arc42/runtime-view/data-consumption-process_part1_tracex_scaling.puml @@ -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 @@ -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