|
1 .. _appmanage: |
|
2 |
|
3 .. _site: |
|
4 |
|
5 |
|
6 PyAMS admin site |
|
7 ================ |
|
8 |
|
9 PyAMS admin site (called also **ZMI**, in memory of old **\Z**\ope **\M**\anagement **\I**\nterface) is based on the ZODB. |
|
10 |
|
11 When the PyAMS is initialized, it create and register several utilities into the *local registry* and saved into ZODB. |
|
12 These utilities are created with default values which can be modified through **management interface** when |
|
13 the application is started. |
|
14 |
|
15 |
|
16 Local registry utilities |
|
17 '''''''''''''''''''''''' |
|
18 |
|
19 One of PyAMS pre-requisites is to use the ZODB, at least to store the site root application, |
|
20 it's configuration and a set of local utilities. |
|
21 |
|
22 Some important utilities include: |
|
23 |
|
24 - a **catalog**: the catalog has the responsibility to index every content properties which are required to make quick |
|
25 and efficient searches. Catalog indexes are automatically created on database upgrade; management interface |
|
26 allows administrator to get indexes properties, to get the number of indexed objects and values for a given index, and |
|
27 to delete an index before recreating it by running the database upgrade script another time (see :ref:`scripts`). |
|
28 |
|
29 - an **internal IDs** utility: |
|
30 |
|
31 - a **language negotiator**: |
|
32 |
|
33 - a **portal templates** container: |
|
34 |
|
35 - a **security manager**: |
|
36 |
|
37 - a **sequential IDs** utility: |
|
38 |
|
39 - a **server timezone** utility: |
|
40 |
|
41 - a **user profiles** container: |
|
42 |
|
43 |
|
44 Optional utilities can also include: |
|
45 |
|
46 - an **Elasticsearch content indexer**: |
|
47 |
|
48 - a **maps manager**: |
|
49 |
|
50 - a **medias converter**: |
|
51 |
|
52 - a **tasks scheduler**: |
|
53 |