Invoking the application:
archive_server [-e] [-f db] [-i] [-l logfile] [-n node] [-o max] [-q] [-r]
[-t] [-v] port
The archive_server application accepts DICOM associations from other
devices/clients. It supports the following functions:
- -e Examine received images and perform
SOP validation. If the image does not pass SOP tests, return a failure
code to sending app.
- -f db Use db as control database rather
than default (CTNControl)
- -i Ignore some tests during association
validation. Effectively turns off the use of the Security Matrix.
- -l logfile Log association requests to
- -n node Use node as the name of the
system rather than using hostname.
- -o max Allow max simultaneous
connections from an organization. (Used in RSNA demonstrations.)
- -q Quiet mode; don-r Reduced
capability. Do not open FIS tables. This is useful for those systems that
do not care about FIS functions, like storage commitment. It is a required
switch in the Windows verson.
- -t Use threads rather than forking a
new process. Required under Windows.
- -v Place DUL and SRV facilities in
verbose mode. port TCP/IP port address. No default.
The archive_server may also initiate DICOM associations to store images to
a third party. The actual movement is handled outside of the
archive_server application. The user only needs to run one copy of
archive_server on a machine. The archive_server uses the CTNControl Database to determine which archive
system is being accessed.
- Storage of composite objects (images, RT objects)
- Query/retrieve of composite objects (images, RT objects)
- Storage commitment requests