This page is obsolete, please go to the new Weasis website







Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 39 Next »

This page describes how to install Weasis.

Weasis is launched from the dcm4chee administrative web interface, as shown in the pictures below. It may also be copied to a CD with images.


For dcm4chee-web3 (new web interface)

  • Install dcm4chee, if needed. The latest version and installation instructions can be found here.
    • 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. 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.
    • weasis.war
    • weasis-i18n.war - Optional for internationalization (translation)
    • dcm4chee-web3/dcm4chee-web-weasis.jar
    • dcm4chee-web3/weasis-pacs-connector.war
      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.
  • Place these files in the dcm4chee deploy folder (server/default/deploy/).
  • 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:
      WebviewerNames = weasis
      WebviewerBaseUrl = NONE
    • Click the Apply Changes button
  • Configure Weasis
    The default configuration of Weasis is stored in two files inside weasis.war.
    To override the default configuration,
    • Go here.
      Select the latest version and navigate to src/main/resources
      Download weasis-connector-default.properties and rename it weasis-pacs-connector.properties
      Download weasis-jnlp-default.xml and rename it weasis-jnlp.xml
    • Copy the files to the classpath. 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 been changed.
      If so, edit weasis-pacs-connector.properties. Change pacs.host, pacs.port, and pacs.aet.
      Changes to weasis-jnlp.xml are needed less often.

That's all, now restart dcm4chee and launch Weasis from the dcm4chee-web3 portal.

For dcm4chee-web (classic - before 2.17.1)

Be Careful

dcm4chee-web.war has been built only for some dcm4chee versions. For other versions see Rebuild dcm4chee-web from any version)

  • Place these three files into the deploy folder (server/default/deploy/) of dcm4chee.
  • Modify the permission in /dcm4jboss-web/src/etc/conf/dcm4chee-web/folder.permissions or in server/default/conf/dcm4chee-web if dcm4chee is already installed

folder.*=edit,move,delete,view,*export,edit.newStudyUID,mergepat,study_permission,study_permission.free_role_action,query_has_issuer folder.*export=export_tf,export_xds

...

folder=WebUser(send,view);DatacareUser(edit,move,delete,export_xds,view);WebAdmin(*)

That's all, now restart dcm4chee and launch Weasis from the web portal.

Write weasis-portable to DICOM CDs with dcm4chee-cdw

  • Install dcm4chee-cdw (see doc/INSTALL.txt in the archive)
  • Extract weasis-portable.zip into the ../dcm4chee/server/default/data/mergedir directory
  • Go to the dcm4che jmx console (dcm4chee.cdw):
    •  Select the MediaCreationMgtSCP item and set to true the value of DefaultIncludeDisplayApplication
    •  Select the MakeIsoImage item and set to 4 the value of isoLevel
  • Click on the Apply Changes button

Embedding a Java Runtime for Windows

The executable (weasis-win32.exe) allows to embed a JRE in the directory "jre/windows" (weasis-portable/jre/windows/bin/java.exe). The embedded Java Runtime is used only when no runtime is available on the system. When Java is run from CD, it could be a little slow.

  • No labels