Weasis 4.2.0

[Gaël Renault]

Hello guys, i have an issue.
I have installed Weasis 4.2.0 on a client computer, and try to open it through dcm4chee arclight 5.29.2 ui.
When i do i get a "Failed to launch JVM" error. 
When i check the Weasis logs on the client, it's trying to reach a file called "base.json" file.
I noticed that the version 4.2.0 implements a new type of configuration file (no longer config.properties but a JSON file). How do i make it work with dcm4chee please ?

[Nicolas Roduit]

Please specify which integration configuration as there are several.

See also the boot.log file which shows the launch configuration.

[Gaël Renault]

Hello Nicholas,

The integration type is embedded Weasis for dcm4chee arc light 5.29.2 and weasis-pacs-connector. I followed this procedure :  Embedding in dcm4chee :: Weasis Documentation
When i click on the viewer eye in the dcm4chee arclight ui from another computer though, with an older version of weasis (tried 3.8.7, 4.1.1 and 4.1.2); it works fine. It seems like there a conflict between versions of Weasis when the 4.2.0 has been installed.

[Nicolas Roduit]

Since version 4.2.0, the preferences configuration has changed to be compliant with a new component. You must ensure that preferences are not retrieved on the server side via the "cdb" property (the value must be empty for the preferences to be those of the native client), in boot.log => Application configuration file = file:/opt/weasis/lib/app/conf/base.json

However, we will be proposing a new weasis-manager component by the end of the year. This component is the successor to weasis-pacs-connector and will manage user and launch preferences by user, group or host. It will also manage minor version updates according to this compatibility file and by importing weasis-native.zip (from weasis 3.6.0). 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 with the native version installer on workstations is done progressively.

[Ryan Colburn]

installed 4.2.0 from microsoft store.  When i try to launch, it seems to do so before automatically closing a second later (before any chance to even load files).

Additional detail: weasis launch logo shows, then the plug-ins loader/launch box appears to run, shows "completed 41 of 41 plug-ins", and the program itself launches as well (icon in the taskbar too) , then subsequently closes everything.

System: Windows 11 v22h2

[Nicolas Roduit]

A post can only deal with one subject at a time. Please open a bug if the application doesn't start by providing the launch logs (boot.log).

[Piotr Orzechowski]

If Weasis is not installed on the server side, the parameter cdb with no value must be added to the URL (e.g. http://localhost:8080/weasis-pacs-connector/weasis?patientID=9702672&cdb) or the weasis.base.urlproperty in the weasis-pacs-connector configuration must be commented or set to null.
It is working.