How to configure remote Application Entities

vrindanayak edited this page Oct 11, 2016 · 10 revisions
Clone this wiki locally

Add a new Device providing one Application Entity available on one Network connection by adjusting following LDIF file:

version: 1
# LDIF for adding a Device providing one Application Entity available on one Network connection
# Adjust Base DN (dc=dcm4che,dc=org), Device name (SAMPLE_DEVICE), AE Title (SAMPLE_AET),
# Hostname (sample.host.name) and Port number before import it into the LDAP server

# Unique AE Title
# (will fail if there is already an object for the same AE Title)
dn: dicomAETitle=SAMPLE_AET,cn=Unique AE Titles Registry,cn=DICOM Configuration,dc=dcm4che,dc=org
objectClass: dicomUniqueAETitle
dicomAETitle: SAMPLE_AET

# Device
dn: dicomDeviceName=SAMPLE_DEVICE,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
objectClass: dicomDevice
dicomDeviceName: SAMPLE_DEVICE
dicomInstalled: TRUE

# Network Connection
dn: cn=dicom,dicomDeviceName=SAMPLE_DEVICE,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
objectClass: dicomNetworkConnection
cn: dicom
dicomHostname: sample.host.name
dicomPort: 12345

# Network Connection (secure)
# dn: cn=dicom-tls,dicomDeviceName=SAMPLE_DEVICE,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
# cn: dicom-tls
# objectClass: dicomNetworkConnection
# dicomHostname: sample.host.name
# dicomPort: 23456
# dicomTLSCipherSuite: TLS_RSA_WITH_AES_128_CBC_SHA
# dicomTLSCipherSuite: SSL_RSA_WITH_3DES_EDE_CBC_SHA

# Network Application Entity
dn: dicomAETitle=SAMPLE_AET,dicomDeviceName=SAMPLE_DEVICE,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
objectClass: dicomNetworkAE
dicomAETitle: SAMPLE_AET
dicomNetworkConnectionReference: cn=dicom,dicomDeviceName=SAMPLE_DEVICE,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
# dicomNetworkConnectionReference: cn=dicom-tls,dicomDeviceName=SAMPLE_DEVICE,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
dicomAssociationInitiator: TRUE
dicomAssociationAcceptor: TRUE

and importing it to the LDAP Server by using the ldapadd command line utility, e.g.:

> ldapadd -xWD "cn=admin,dc=dcm4che,dc=org" -f sample-device.ldif 
Enter LDAP Password: 
adding new entry "dicomAETitle=SAMPLE_AET,cn=Unique AE Titles Registry,cn=DICOM Configuration,dc=dcm4che,dc=org"

adding new entry "dicomDeviceName=SAMPLE_DEVICE,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org"

adding new entry "cn=dicom,dicomDeviceName=SAMPLE_DEVICE,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org"

adding new entry "dicomAETitle=SAMPLE_AET,dicomDeviceName=SAMPLE_DEVICE,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org"

or the LDIF Import... function of Apache Directory Studio.

One may refer to Network Connection and Network AE to understand the description of attributes

Another option is to create a JSON file specifying the Device (e.g.):

{
  "dicomDeviceName": "SAMPLE_DEVICE",
  "dicomInstalled": true,
  "dicomNetworkConnection": [
    {
      "cn": "dicom",
      "dicomHostname": "sample.host.name",
      "dicomPort": 12345
    }
  ],
  "dicomNetworkAE": [
    {
      "dicomAETitle": "SAMPLE_AET",
      "dicomAssociationInitiator": true,
      "dicomAssociationAcceptor": true,
      "dicomNetworkConnectionReference": [
        "/dicomNetworkConnection/0"
      ]
    }
  ]
}

and import it using a RESTfull service of the archive:

$ curl -H "Content-Type:application/json" http://localhost:8080/dcm4chee-arc/devices/SAMPLE_DEVICE --data-binary @path/to/json/file

See also DICOM Part 15: Data Model Component Objects