Wiki Markup |
---|
{style} .panel {-moz-border-radius: 7px; border-radius: 7px;} .panelMacro table {-moz-border-radius: 15px; border-radius: 15px;} {style} |
...
- Open the management console in http://localhost:9990/
- Select the “Deployments” tab
- Add the .war files using the “Add” button (Choose Upload a new deployment or select Replace when the file already exists)
- Configure Weasis weasis-pacs-connector (Required to change the default WADO configuration)
The default configuration of Weasis is stored in two files inside weasisinside weasis-pacs-connector.war.
To override the default configuration:Go here.
Requires weasis-pacs-connector 6.x and superior: Download the current weasis-connector-default.properties and rename it weasis-pacs-connector.properties, and download dicom-dcm4chee.properties (configuration of the dcm4chee archive)
Note title Download issue From github interface, click on "raw" button for downloading the file with the "save as..." menu of the browser.
- Copy the files into wildfly/standalone/configuration (the application uses "jboss.server.config.dir" to locate files)configuration.
- Edit the configuration as needed.
As the current default configuration of dicom-dcm4chee.properties is defined for dcm4chee-web3, it is necessary to modify at least the WADO property by: arc.wado.url=${server.base.url}/dcm4chee-arc/aets/DCM4CHEE/wado
For example, dcm4chee may be running on a different computer than Weasis, or the AE Title of dcm4chee may have been changed. If so, edit weasis-pacs-connector.properties or dicom-dcm4chee.properties (Change pacs.host, pacs.port, and pacs.aet). - To add new properties or arguments in the JNLP file, see configuration of weasis-pacs-connector
...
- To activate Weasis in dcm4chee-arc-light user interface, you need need to import 2 attributes in the LDAP configuration
From a LDAP manager (like Apache Directory Studio)
- Connect with the dcm4chee configuration
Import weasis.ldif
Note title weasis-pacs-connector configuration The weasis.ldif configuration is suitable for the default relative path (when weasis-pacs-connector is installed in the same JBoss as dcm4chee)
Otherwise edit weasis.ldif file and change the relative URL by an absolute value, ex: http://YOUR-host:8080/weasis-pacs-connectorThe new way of launching Java Westart file (jnlp) will require an absolute URL: //myserver.com:8087
jnlp://YOUR-host:8080/weasis-pacs-connector
jnlps://YOUR-host:8443/weasis-pacs-connector (SSL connection)
- Restart all the components (ex. docker restart postgres slapd dcm4chee-arc)
Refresh the web page and the view button should appears as in the screenshot above
...
- Install dcm4chee, if not already done. For security see also how to limit the server access.
- dcm4chee-web3 is not compatible with versions of dcm4chee before 2.16.0
- dcm4chee 2.16.0 to 2.17.0 are compatible with dcm4chee-web3, but the older dcm4chee-web is installed by default.
For dcm4chee 2.17.1+, dcm4chee-web3 is already installed.
Tip To check if it is the latest version, start dcm4chee-web3 (http://localhost:8080/dcm4chee-web3/), log in, and mouse over the dcm4chee.org icon in the upper right corner.
- Go here and download these Weasis files.
- From the folder with the latest version number:
- weasis.war
- weasis-i18n.war - Optional for internationalization (translation)
- From weasis-pacs-connector folder:
- dcm4chee-web-weasis.jar
weasis-pacs-connector.war
Note title Download issue Some browsers (Internet Explorer) may rename war files to zip. If so, use the Save As option when downloading. Change the name back to war.
- From the folder with the latest version number:
...
- To activate Weasis, go to the JMX console (at http://localhost:8080/jmx-console)
In dcm4chee.web select service=WebConfig and set these two values:
Code Block WebviewerNames = weasis WebviewerBaseUrl = NONE
From weasis-pacs-connector 5.0 WebviewerBaseUrl can have different values:
- Launch Weasis as an external application (default value when NONE): WebviewerBaseUrl = weasis:/weasis-pacs-connector/viewer
Launch Weasis as an Applet in the web browser (not recommended as several browsers block Java plugin) : WebviewerBaseUrl = weasis:/weasis-pacs-connector/viewer-applet
Note title weasis-pacs-connector configuration The new way of launching Java Westart file (jnlp) will require an absolute URL:
- weasis:jnlp://YOUR-host:8080/weasis-pacs-connector/viewer
- weasis:jnlps://YOUR-host:8443/weasis-pacs-connector/viewer (SSL connection)
From dcm4chee 2.18.3, it possible to reuse the host name of dcm4chee:
- weasis:jnlp://${server.host}:8080/weasis-pacs-connector/viewer
- weasis:jnlps://${server.host}:8443/weasis-pacs-connector/viewer
- Click the Apply Changes button
- Configure Weasis (This step is optional if you just want to keep the default configuration. It is required when the AE Title AETitle DCM4CHEE has been changed)
The default configuration of Weasis is stored in two files inside weasis-pacs-connector.war.
To override the default configuration:Go here.
weasis-pacs-connector 4.x and 5.x: Download weasis-connector-default.properties and rename it weasis-pacs-connector.propertiesweasis-pacs-connector 6.x and superior: Download the current weasis-connector-default.properties and rename it weasis-pacs-connector.properties, and download dicom-dcm4chee.properties (configuration of the dcm4chee archive)
Note title Download issue From github interface, click on "raw" button for downloading the file with the "save as..." menu of the browser.
- Copy the files into a folder in the classpath of the servlet container. In JBoss (inferior to version 7), the best location would typically be server/default/conf.
- Edit the configuration as needed.
For example, dcm4chee may be running on a different computer than Weasis, or the AE Title of dcm4chee may have been changed.
If so, edit weasis-pacs-connector.properties or dicom-dcm4chee.properties for weasis-pacs-connector 6.x. Change pacs.host, pacs.port, and pacs.aet. - To add new properties or arguments in the JNLP file, see configuration of weasis-pacs-connector
...