dcm4chee-arc-light 5.0.1 (finally) released

[gunterze]

Finally, there is dcm4chee-arc-light 5.0.1 out:

Sources: https://github.com/dcm4che/dcm4chee-arc-light5
Binaries: https://sourceforge.net/projects/dcm4che/files/dcm4chee-arc-light
Issue Tracker: https://github.com/dcm4che/dcm4chee-arc-light/issues
Wiki: https://github.com/dcm4che/dcm4chee-arc-light/wiki

There is also a dockerized version with PostgreSQL as DB available for quick installation
(https://github.com/dcm4che/dcm4chee-arc-light/wiki/Running-on-Docker )

Any feedback welcome,
gunter

[gunterze]

Oops, correct links:

Sources: https://github.com/dcm4che/dcm4chee-arc-light
Binaries: https://sourceforge.net/projects/dcm4che/files/dcm4chee-arc-light5

Issue Tracker: https://github.com/dcm4che/dcm4chee-arc-light/issues
Wiki: https://github.com/dcm4che/dcm4chee-arc-light/wiki

[gunterze]

Oops, the displayed links were right, but the effective one still wrong. Hopefully now both are right

Sources: https://github.com/dcm4che/dcm4chee-arc-light
Binaries: https://sourceforge.net/projects/dcm4che/files/dcm4chee-arc-light5
Issue Tracker: https://github.com/dcm4che/dcm4chee-arc-light/issues
Wiki: https://github.com/dcm4che/dcm4chee-arc-light/wiki

[Alvaro G. [Andor]]

Ok, That's awesome! Why doesn't anybody comment on this? :P

So, here goes a battery of questions :)

• So, v4 evolved as an internal company version and we should forget about it, and just think in v5 as a v2, isn't it?
• How does it compare right now to v2 in term of features?
• I see mention of a web interface. Is it as functional as the one on v2 right now?
• Is it production ready?
• How is jpeg2k and jpegls working there, still through jai-io? Or is there any interface for modern libraries, open or not?
• How stateless is it? Does all configuration (or almost everything) reside on the LDAP and or database? We are re-designing our cloud and clustering solutions, and having configuration files on disk makes more difficult to make stateless/disposable nodes, or deploying additional nodes when needed... Also, it makes more difficult updating the running PACS version, as you have to track all (or most) config files changed to avoid overwriting them...
  

Thanks for all the work!
Congrats!

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

[gunterze]

On Monday, January 11, 2016 at 8:07:58 PM UTC+1, andor wrote:

Ok, That's awesome! Why doesn't anybody comment on this? :P

So, here goes a battery of questions :)

• So, v4 evolved as an internal company version and we should forget about it, and just think in v5 as a v2, isn't it?

I left the company half a year ago. I don't know the reason, why the management decided recently, to discontinued open source development on v4. The main reason for me to start with v5 was, that I got the feeling, that v4 becomes to complex, because of the requirements to have to integrate with other (10 time larger) proprietary systems.

• How does it compare right now to v2 in term of features?

Missing:

MWL SCP - should be doable in few days, not yet scheduled, but I guess during next 3 months
No auto-switch of storage file systems (but  you can switch manually) - not scheduled
No archiving to nearline storage (but support of cloud storage as primary storage) - not yet scheduled
No store-and-remember to other DICOM archive (but DICOM forwarding controlled by rules) - not yet scheduled
No DICOM export triggered by Web UI - scheduled for 5.0.2 (~1 month)
No XDS-I export - not scheduled
No Media Creation export - not scheduled
No Teaching File Export - not scheduled
No Data Management support by Web UI - not yet scheduled, but I guess during next 6 months

New Features, not available in v2:
QIDO-RS
IHE IOCM (also used as replacement of Trash Folder)
Queue Management via Web GUI and RESTful Service
Storage abstraction - it's quite easy to plugin your own primary storage provider
Exporter abstraction

Other features planed to implement during next 6 months
WADO-RS
STOW-RS
RESTFul Service to (r/w) access LDAP configuration
...

• I see mention of a web interface. Is it as functional as the one on v2 right now?

Not yet, see above

• Is it production ready?

Yes. We already use it in an installation were we receive > 100.000 objects a day.

• How is jpeg2k and jpegls working there, still through jai-io? Or is there any interface for modern libraries, open or not?

It still use jai-io, with the same possiblity to plugin another codec wrapped in an Image IO Reader/Writer. By the way, running in docker, you can use jai-io also on Win64 or OSX.
 

• How stateless is it? Does all configuration (or almost everything) reside on the LDAP and or database? We are re-designing our cloud and clustering solutions, and having configuration files on disk makes more difficult to make stateless/disposable nodes, or deploying additional nodes when needed... Also, it makes more difficult updating the running PACS version, as you have to track all (or most) config files changed to avoid overwriting them...
  

All configuration is stored in LDAP. Only the primary key needed for dicom-tls and LDAP connection parameters are stored on the node - technically you could also store the primary key on LDAP, but I didn't want to introduce such practice by default.

Have fun,

gunter

[gunterze]

Also Missing: ATNA Audit Log - scheduled for next 3 month

On Sunday, January 10, 2016 at 11:49:37 PM UTC+1, gunterze wrote:

[simonmd]

Congratulations!

[simonmd]

Big thanks to Gunter for moving forward with this open source v5!

For previous users of dcm4chee 2.x, one of the barriers to start playing around with v4/v5 is the LDAP configuration. In the JMX console every option/parameter was visible and at least a small description was available, and you could learn a lot just by exploring all the MBeans.

Thanks to the Docker and Docker Compose containers it's easy to have a 5.0.1 instance up and running, but when you look at the LDAP hierarchy in Apache DS Studio, it's pretty minimalistic, with only some basic options.

Is there a way to see all the possible configurable parameters that the project supports? That could help many in the community get started while the documentation and Wiki progresses.

Great work and congrats to everyone involved.

Simon

[gunterze]

On Wednesday, January 13, 2016 at 4:07:22 PM UTC+1, simonmd wrote:

Big thanks to Gunter for moving forward with this open source v5!

For previous users of dcm4chee 2.x, one of the barriers to start playing around with v4/v5 is the LDAP configuration. In the JMX console every option/parameter was visible and at least a small description was available, and you could learn a lot just by exploring all the MBeans.

Thanks to the Docker and Docker Compose containers it's easy to have a 5.0.1 instance up and running, but when you look at the LDAP hierarchy in Apache DS Studio, it's pretty minimalistic, with only some basic options.

Is there a way to see all the possible configurable parameters that the project supports? That could help many in the community get started while the documentation and Wiki progresses.

There is minimal documentation about all available LDAP objects and attributes in the LDAP schema definitions. Unfortunately Apache Directory Studio shows this information only in its Schema Browser View, but not in the LDAP Browser and the Table Entry Editor View.

I started documented some main configuration scenarios in the Wiki: https://github.com/dcm4che/dcm4chee-arc-light/wiki/HowTos
Any help to add and improve the Wiki is highly welcome.

A RESTful service for accessing the LDAP configuration will be available at v5.0.2 ( https://github.com/dcm4che/dcm4chee-arc-light/issues/5 ). We are already working to extend the Web UI with a configuration editor, using that RESTful service - But it will take some time, until you will be able to configure all parameters via the Web UI.

gunter

 

[Li Bin]

 Hi, gunter, 

    Could you pls take some time to give us some words on the relationship between 4.x and 5.x ?   From your post, it seems a new product line more than a upgraded version of  4.x ?     

     Thanks a lot.

[Ramesh R]

Great to see dcm4chee-arc-light actively coming up with releases almost every month. I have seen it has given many more additional features that are not available in dcm4chee 2.x. I have few questions.

1) Does dcm4chee-arc-light provide all the features that are available in dcm4chee 2.x, as of the current release 5.14?

2) Is there a feature list comparison between dcm4chee 2.x and dcm4chee-arc-light to understand where we stand with dcm4chee-arc-light today? 

3) Is the dcm4chee-arc-light production ready? Are there any specific version that you would recommend to use for production?

[Endi Silveira]

Would be great to know those questions...

I also wanna ask if dcm4chee-arc-light provides a MWL as dcm4chee-2.x... Thanks in advance.

--

You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

--

[Pablo Fonseca]

Hi Endi,

Dcm4chee archive 5 provides MWL, we have deployed it at a radiology imaging center in Peru, and it's working fine! There is also the hl7 OMI O23 option to create the entries (appart from the original ORM O01 in v.2.x). The interface is different though, for seeing the records on the interface you need to select MWL instead of studies.

Best Regards, 

Pablo