The EAI broker reads the storage account messages and then calls a so-called "worker" that will

do the import/export.

I created the stub for a worker for the archiving-light feature in Sampling, you could create a
similar one for your service and implement it.

Hint: I unified the code and the naming an therefore changed the service keys in admin ui ->
please look up the correct service key there.

Please see

• https://bitbucket.org/materialone/oemportal-
sampling/src/0de4c64d12c8edf012b72399275c9238d9b5c38f/service/src/main/java/de/lo
gsolut/oemportal/sampling/infrastructure/adapter/zeebe/archivinglight/ArchivingLightJob
Worker.java?at=feature%2FMOI-2252_Implement_Zeebe_worker_in_Sampling
• https://bitbucket.org/materialone/oemportal-
sampling/src/0de4c64d12c8edf012b72399275c9238d9b5c38f/service/src/main/java/de/lo
gsolut/oemportal/sampling/infrastructure/adapter/zeebe/archivinglight/ArchivingLightEai
BrokerService.java?at=feature%2FMOI-2252_Implement_Zeebe_worker_in_Sampling

But please complete the interface specification also (so that we at least have a minimum
description of all interfaces) when you implement the worker:

• https://logsolut.atlassian.net/wiki/spaces/lsoem/pages/3966042363/Internal+-
+Document+Exchange+Interfaces
• https://logsolut.atlassian.net/wiki/spaces/lsoem/pages/2707259403/MBAG+-
+Document+Exchange+Interfaces

Please have a look at the documentation of the data interchange with EAI broker first:
https://logsolut.atlassian.net/wiki/spaces/lsoem/pages/3868131406/Partner+Documentation+-
+EAI-Broker

I hope the following BPMN diagrams can help to better understanding how this works internally.
The components that contain "WORKER" in their names are the ones that have to be
implemented in the backend services. The type of worker which has to be implemented depends
on the type of the processing (import or export).
Import

Export
Please note:

• The service of the arichiving-light feature implements the FileTransferExportService -> if

you wanna implement "import-norm" or "import-sqms" you'd rather implement the
FileTransferImportService.
• If you need to implement a worker in a different service (e.g. "import-norm" is probably
in sampling-norm) -> please review the changes of the whole branch, since there are also
some settings in application.yml and dependencies in pom.xml which need to be updated.
• The aforementioned branch with my stub for the worker still misses the required update
of the azure-storage library to a newer version >=4.0.142 (otherwise the down-/upload
will probably fail)