synchronize without a primary, and configuring AETs without IP address or port

63 views
Skip to first unread message

rrose...@securerad.com

unread,
Jul 15, 2015, 11:19:22 AM7/15/15
to dcm...@googlegroups.com
Hello,

I have 2 dcm4chee servers not on a LAN or the same network. They need to be synchronized. I have two issues I think I need to deal with. I plan to use the forward service specifying <aeTitleFrom>. In theory, (I think), specifying <aeTitleFrom> in the Forward Service on both dcm4chee1 and dcm4chee2 should allow them to be synchronized and not have an endless loop.

dcm4chee1 has multiple modalities within the same LAN, and when studies are received, it needs to forward them to dcm4chee2. Easy enough, they will all have static IPs, ports etc. I'll configure using the standard forward service specifying AETs to forward to dcm4chee2 so I don't have an endless loop.

The issue is dcm4chee2. dcm4chee2 will receive studies from mobile units from different locations, those locations will change, and once dcm4chee2 receives them, it needs to forward them to dcm4chee1. On dcm4chee2, I cannot only enter an AETitle in "add AETitles" without also adding IP addresses and ports. Will "fictitious" IP addresses/ports suffice in the entry so when the forward service is configured with <aeTitleFrom>, dcm4chee only looks at the AETitle, and not the IP address or port in order for the forward rule to function?

Thanks,

Rich




medmike

unread,
Jul 17, 2015, 4:23:50 AM7/17/15
to dcm...@googlegroups.com
Just give it a try...

But how about using a forwarding rule for dcm4chee2 like this to send to DCM4CHEE1 from all callingAETs except when calling AET is DCM4CHEE1:
[calling != DCM4CHEE1]DCM4CHEE1

Moreover to keep your dcm4chee servers in sync in case of data correction, you may look at AttributesModification Services (dcm4chee.archive and web) and HL7-Services.

Arnold Maderthaner

unread,
Jul 17, 2015, 5:21:29 AM7/17/15
to dcm...@googlegroups.com, rrose...@securerad.com
Hi Rich !

I don't think that you need to setup the AETs of the modalities sending to DCM4CHEE2 instance (you only need this if they need to do C-MOVE or Storage Commitment - so when dcm4chee2 needs to make a connection back to the modality). 
Additionally the rule from medmike looks good to me :)

yours
Arnold

rrose...@securerad.com

unread,
Jul 17, 2015, 1:06:17 PM7/17/15
to dcm...@googlegroups.com
Hold the phone!!!!!  ! as a "not" operator works??? WOW... It would be extraordinarily helpful to know what "library" of items work. I use it in bash all the time, but really had no idea it would work here. Seriously, it would be helpful, and I'd be willing to help, to have a mini library of slick tips like this.....

Thanks SO much (although I have not tested it yet...)

Rich

side note - hi Arnold! hope you are well.
Reply all
Reply to author
Forward
0 new messages