More questions about Forward RESTful services to other archive

[Kirill K]

Hi

Realised that i have lot more questions then expected.

My setup is as follows: 2 archives (5.22) on diferent docker hosts.

On first LDAP  container i need to apply  settings descibed in "Forward RESTful services to other archive" howto, right?

On second  LDAP  container i need to create new web app to recieve changes from first archive.

Can i use last part from howto to create one? Like:

dn: dcmWebAppName=archive2WebApp,dicomDeviceName=dcm4chee-arc2,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
  objectClass: dcmWebApp
  dcmWebAppName: archive2WebApp
  dcmWebServiceClass: DCM4CHEE_ARC_AET
  dcmWebServicePath: /dcm4chee-arc/aets/DCM4CHEE/rs
  dicomNetworkConnectionReference: cn=http,dicomDeviceName=dcm4chee-arc2,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
  -

Or i need somethig more?

Do i need to mirror that setup vise-versa to get changes from 2 to 1?

[vrinda...@j4care.com]

If you have 2 separate LDAP containers then you need to also ensure that the 2 LDAPs are synced. For your case, you could use a single LDAP used by both archives.

1) To forward requests from archive 1 to archive 2

- Create a RS Forward Rule on archive 1

- Create a HTTP Connection and Web Application on archive 2

- Reference this Web Application of archive 2 in RS Forward Rule of archive 1

- Set RS Operations as required

2) To forward requests from archive 2 to archive 1

- Create a RS Forward Rule on archive 2

- Create a HTTP Connection and Web Application on archive 1

- Reference this Web Application of archive 1 in RS Forward Rule of archive 2

- Set RS Operations as required

Note : Current (latest) version of archive allows selecting only its own web application in a RS Forward Rule, which is not helpful in this case. This has been fixed and shall be available in the next version. Until then, you can use Apache DS client or update using LDIF file as specified in the wiki.

In case you have same RS Operations configured on RS Forward rules on both archives, you would also need to specify a condition in Request URL Pattern field of RS Forward Rule to avoid ping-pong scenario.

With current version of archive, there is a logical error in this pattern matching check - which has been fixed. In addition to this fix, you will also need to create additional AEs and Web Applications which shall be used only in the case of forwarding the RS requests. Attached sample configuration ldif (Ensure to change the host / ports / device / AE / web app names as required).