That's a good question. There is indeed a transitional situation pending the release of the new weasis-manager component in early 2024.
While waiting for the new component, I'd say the simplest solution is to use only the native version (installed on a client workstation) and use either
the DICOMWeb APIs directly or weasis-pacs-connector with
the cdb parameter set to null.
weasis-manager is the successor to weasis-pacs-connector and has the following main functions:
- Itinerant management of user preferences
- Launch context management (plugin configuration, menu and toolbar management) by user, group or host machine
- Management of minor version updates based on this compatibility file and by importing weasis-native.zip (since weasis 3.6.0)
- Management of the translation packages (built every day)
- Several types of connectors for interfacing with a DICOM archive
- Allows you to configure a client in Keycloack and transmit the token to Weasis for DICOMWeb or WADO URI calls (solves the problem of limiting URIs to 2048 characters under Windows, where the token is truncated when passed through the weasis:// uri)
In other words, even if the computer park has heterogeneous Weasis versions, it will be able to update the different versions according to the compatibility file. This is useful when updating progressively the native installer on workstations. And of course, it allows you to instantly update minor versions of all workstations from the server component.