|
0
|
1 .. _configuration:
|
|
|
2 .. highlight:: bash
|
|
|
3
|
|
|
4 Configuration of Orthanc
|
|
|
5 ========================
|
|
|
6
|
|
|
7 Configuring Orthanc simply consists in copying and adapting the
|
|
|
8 `default configuration file
|
|
72
|
9 <https://bitbucket.org/sjodogne/orthanc/raw/Orthanc-1.2.0/Resources/Configuration.json>`_. This
|
|
0
|
10 file is in the `JSON <https://en.wikipedia.org/wiki/JSON>`_ file
|
|
|
11 format. You can generate a sample configuration file with the
|
|
|
12 following call::
|
|
|
13
|
|
|
14 $ Orthanc --config=Configuration.json
|
|
|
15
|
|
|
16 Then, start Orthanc by giving it the path to the modified
|
|
|
17 Configuration.json path as a command-line argument::
|
|
|
18
|
|
|
19 $ Orthanc ./Configuration.json
|
|
|
20
|
|
|
21 The default configuration file would:
|
|
|
22
|
|
|
23 * Create a DICOM server with the DICOM AET (Application Entity Title)
|
|
|
24 ``ORTHANC`` that listens on the port 4242.
|
|
|
25 * Create a HTTP server for the REST API that listens on the port 8042.
|
|
|
26 * Store the Orthanc database in a folder called ``OrthancStorage``.
|
|
|
27
|
|
73
|
28 *Remark:* When specifying paths under Microsoft Windows, backslashes
|
|
|
29 (i.e. ``\``) should be either escaped by doubling them (as in ``\\``),
|
|
|
30 or replaced by forward slashes (as in ``/``).
|
|
|
31
|
|
0
|
32 To obtain more diagnostic, you can use the ``--verbose`` or the
|
|
|
33 ``--trace`` options::
|
|
|
34
|
|
|
35 $ Orthanc ./Configuration.json --verbose
|
|
|
36 $ Orthanc ./Configuration.json --trace
|
|
|
37
|
|
|
38 Starting with Orthanc 0.9.1, you can also start Orthanc with the path
|
|
|
39 to a directory. In such a case, Orthanc will load all the files with a
|
|
|
40 ``.json`` extension in this directory, and merge them to construct the
|
|
|
41 configuration file. This allows to split the global configuration into
|
|
|
42 several files.
|
