Mercurial > hg > orthanc
comparison Resources/Configuration.json @ 2988:9cc3d40e389b
Orthanc 1.4.3 is now known as 1.5.0
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Mon, 10 Dec 2018 11:15:31 +0100 |
parents | 9c0b0a6d8b54 |
children | abe49ca61cd5 |
comparison
equal
deleted
inserted
replaced
2987:96089d1aba4d | 2988:9cc3d40e389b |
---|---|
181 // "clearcanvas" : [ "CLEARCANVAS", "192.168.1.1", 104, "ClearCanvas" ] | 181 // "clearcanvas" : [ "CLEARCANVAS", "192.168.1.1", 104, "ClearCanvas" ] |
182 | 182 |
183 /** | 183 /** |
184 * By default, the Orthanc SCP accepts all DICOM commands (C-GET, | 184 * By default, the Orthanc SCP accepts all DICOM commands (C-GET, |
185 * C-STORE, C-FIND, C-MOVE) issued by the remote SCU | 185 * C-STORE, C-FIND, C-MOVE) issued by the remote SCU |
186 * modalities. Starting with Orthanc 1.4.3, it is possible to | 186 * modalities. Starting with Orthanc 1.5.0, it is possible to |
187 * specify which DICOM commands are allowed, separately for each | 187 * specify which DICOM commands are allowed, separately for each |
188 * remote modality, using the syntax below. | 188 * remote modality, using the syntax below. |
189 **/ | 189 **/ |
190 //"untrusted" : { | 190 //"untrusted" : { |
191 // "AET" : "ORTHANC", | 191 // "AET" : "ORTHANC", |
197 // "AllowStore" : true | 197 // "AllowStore" : true |
198 //} | 198 //} |
199 }, | 199 }, |
200 | 200 |
201 // Whether to store the DICOM modalities in the Orthanc database | 201 // Whether to store the DICOM modalities in the Orthanc database |
202 // instead of in this configuration file (new in Orthanc 1.4.3) | 202 // instead of in this configuration file (new in Orthanc 1.5.0) |
203 "DicomModalitiesInDatabase" : false, | 203 "DicomModalitiesInDatabase" : false, |
204 | 204 |
205 // Whether the Orthanc SCP allows incoming C-Echo requests, even | 205 // Whether the Orthanc SCP allows incoming C-Echo requests, even |
206 // from SCU modalities it does not know about (i.e. that are not | 206 // from SCU modalities it does not know about (i.e. that are not |
207 // listed in the "DicomModalities" option above). Orthanc 1.3.0 | 207 // listed in the "DicomModalities" option above). Orthanc 1.3.0 |
251 // "Pkcs11" : false | 251 // "Pkcs11" : false |
252 // } | 252 // } |
253 }, | 253 }, |
254 | 254 |
255 // Whether to store the Orthanc peers in the Orthanc database | 255 // Whether to store the Orthanc peers in the Orthanc database |
256 // instead of in this configuration file (new in Orthanc 1.4.3) | 256 // instead of in this configuration file (new in Orthanc 1.5.0) |
257 "OrthancPeersInDatabase" : false, | 257 "OrthancPeersInDatabase" : false, |
258 | 258 |
259 // Parameters of the HTTP proxy to be used by Orthanc. If set to the | 259 // Parameters of the HTTP proxy to be used by Orthanc. If set to the |
260 // empty string, no HTTP proxy is used. For instance: | 260 // empty string, no HTTP proxy is used. For instance: |
261 // "HttpProxy" : "192.168.0.1:3128" | 261 // "HttpProxy" : "192.168.0.1:3128" |
422 // Whether to run DICOM C-Move operations synchronously. If set to | 422 // Whether to run DICOM C-Move operations synchronously. If set to |
423 // "false" (the default), each incoming C-Move request results in | 423 // "false" (the default), each incoming C-Move request results in |
424 // creating a new background job. Up to Orthanc 1.3.2, the implicit | 424 // creating a new background job. Up to Orthanc 1.3.2, the implicit |
425 // behavior was to use synchronous C-Move. Between Orthanc 1.4.0 and | 425 // behavior was to use synchronous C-Move. Between Orthanc 1.4.0 and |
426 // 1.4.2, the default behavior was set to asynchronous C-Move. Since | 426 // 1.4.2, the default behavior was set to asynchronous C-Move. Since |
427 // Orthanc 1.4.3, the default behavior is synchronous C-Move | 427 // Orthanc 1.5.0, the default behavior is synchronous C-Move |
428 // (backward compatibility with Orthanc <= 1.3.2). | 428 // (backward compatibility with Orthanc <= 1.3.2). |
429 "SynchronousCMove" : true, | 429 "SynchronousCMove" : true, |
430 | 430 |
431 // Maximum number of completed jobs that are kept in memory. A | 431 // Maximum number of completed jobs that are kept in memory. A |
432 // processing job is considered as complete once it is tagged as | 432 // processing job is considered as complete once it is tagged as |
433 // "Success" or "Failure". Since Orthanc 1.4.3, a value of "0" | 433 // "Success" or "Failure". Since Orthanc 1.5.0, a value of "0" |
434 // indicates to keep no job in memory (i.e. jobs are removed from | 434 // indicates to keep no job in memory (i.e. jobs are removed from |
435 // the history as soon as they are completed). | 435 // the history as soon as they are completed). |
436 "JobsHistorySize" : 10, | 436 "JobsHistorySize" : 10, |
437 | 437 |
438 // Specifies how Orthanc reacts when it receives a DICOM instance | 438 // Specifies how Orthanc reacts when it receives a DICOM instance |
443 "OverwriteInstances" : false, | 443 "OverwriteInstances" : false, |
444 | 444 |
445 // Maximum number of ZIP/media archives that are maintained by | 445 // Maximum number of ZIP/media archives that are maintained by |
446 // Orthanc, as a response to the asynchronous creation of archives. | 446 // Orthanc, as a response to the asynchronous creation of archives. |
447 // The least recently used archives get deleted as new archives are | 447 // The least recently used archives get deleted as new archives are |
448 // generated. This option was introduced in Orthanc 1.4.3, and has | 448 // generated. This option was introduced in Orthanc 1.5.0, and has |
449 // no effect on the synchronous generation of archives. | 449 // no effect on the synchronous generation of archives. |
450 "MediaArchiveSize" : 1 | 450 "MediaArchiveSize" : 1 |
451 } | 451 } |