8 |
8 |
9 PyAMS admin site (called also **ZMI**, in memory of old **\Z**\ope **\M**\anagement **\I**\nterface) is based on the ZODB. |
9 PyAMS admin site (called also **ZMI**, in memory of old **\Z**\ope **\M**\anagement **\I**\nterface) is based on the ZODB. |
10 |
10 |
11 When the PyAMS is initialized, it create and register several utilities into the *local registry* and saved into ZODB. |
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 |
12 These utilities are created with default values which can be modified through **management interface** when |
13 the application is started. |
13 the application is started by default (http://localhost:6543/admin). |
14 |
14 |
15 |
15 |
16 Local registry utilities |
16 Local registry utilities |
17 '''''''''''''''''''''''' |
17 '''''''''''''''''''''''' |
18 |
18 |
19 One of PyAMS pre-requisites is to use the ZODB, at least to store the site root application, |
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. |
20 it's configuration and a set of local utilities. |
21 |
21 |
22 Some important utilities include: |
22 Some important utilities include: |
23 |
23 |
24 - a **catalog**: the catalog has the responsibility to index every content properties which are required to make quick |
24 **Catalog**: |
25 and efficient searches. Catalog indexes are automatically created on database upgrade; management interface |
25 The catalog has the responsibility to index every content properties which are required to make quick |
26 allows administrator to get indexes properties, to get the number of indexed objects and values for a given index, and |
26 and efficient searches. Catalog indexes are automatically created on database upgrade; management interface |
27 to delete an index before recreating it by running the database upgrade script another time (see :ref:`scripts`). |
27 allows administrator to get indexes properties, to get the number of indexed objects and values for a given index, and |
|
28 to delete an index before recreating it by running the database upgrade script another time (see :ref:`scripts`). |
28 |
29 |
29 - an **internal IDs** utility: |
30 **Internal IDs** utility: |
|
31 The catalog object doesn't store direct references to objects, but their internal IDs which are generated by this |
|
32 utility. |
30 |
33 |
31 - a **language negotiator**: |
34 **Language negotiator**: |
|
35 As a web site or application can be localized, this utility allows you to define priorities between language |
|
36 definition options (between *user session*, *browser* end *server*), and to define which languages are available |
|
37 to your users (which is particularly important when managing potentially multi-lingual contents). |
32 |
38 |
33 - a **portal templates** container: |
39 .. tip:: |
|
40 Static texts like those displayed into PyAMS management interface are always translated to the language defined |
|
41 into browser language, if available. |
34 |
42 |
35 - a **security manager**: |
43 **Portal templates** container: |
|
44 Portal templates are used to define *presentation templates* based on *portlets* (see :ref:`pyams_portal`). You can |
|
45 create *local* templates, or create *shared templates* into this utility which can then be reused into several |
|
46 places in your web site. |
36 |
47 |
37 - a **sequential IDs** utility: |
48 **Security manager**: |
|
49 This utility is used to define authentication sources which will be available to authenticate your users. |
|
50 :ref:`pyams_security` package provides several authentication modules (like local users, or via OAuth/OAuth2 |
|
51 providers); :ref:`pyams_ldap` add authentication plug-in via an LDAP directory. |
38 |
52 |
39 - a **server timezone** utility: |
53 **Sequential IDs** utility: |
|
54 This utility is used to assign simple sequential IDs to site contents (like sites, news, topics and more); these |
|
55 IDs are simple to identify a given content; several versions of a given content handle by workflow share the same |
|
56 sequential ID. |
40 |
57 |
41 - a **user profiles** container: |
58 **Server timezone** utility: |
|
59 Define the timezone server to display date and time accordingly. |
|
60 |
|
61 **User profiles** container: |
|
62 This utility is used to store information associated to principals through their user profile. |
42 |
63 |
43 |
64 |
44 Optional utilities can also include: |
65 Optional utilities can also include: |
45 |
66 |
46 - an **Elasticsearch content indexer**: |
67 **Elasticearch content indexer**: |
47 |
68 |
48 - a **maps manager**: |
69 Verifier la connection entre le server ElasticSearch et la l'application PyAMS |
49 |
70 |
50 - a **medias converter**: |
71 **Maps manager**: |
|
72 Systeme de cartografie, avec OpenStreeMaps, WMS, GeoPortable, ESRI ou encore Google Maps |
|
73 permet de créer des zones catographique² |
51 |
74 |
52 - a **tasks scheduler**: |
75 **Medias converter**: |
53 |
76 |
|
77 |
|
78 **Tasks scheduler**: |
|
79 |