14 |
14 |
15 |
15 |
16 Local registry utilities |
16 Local registry utilities |
17 '''''''''''''''''''''''' |
17 '''''''''''''''''''''''' |
18 |
18 |
19 |
|
20 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, |
21 it's configuration and a set of local utilities. |
20 it's configuration and a set of local utilities. |
22 |
21 |
23 Some important utilities include: |
22 Some important utilities include: |
24 |
23 |
27 and efficient searches. Catalog indexes are automatically created on database upgrade; management interface |
26 and efficient searches. Catalog indexes are automatically created on database upgrade; management interface |
28 allows administrator to get indexes properties, to get the number of indexed objects and values for a given index, and |
27 allows administrator to get indexes properties, to get the number of indexed objects and values for a given index, and |
29 to delete an index before recreating it by running the database upgrade script another time (see :ref:`scripts`). |
28 to delete an index before recreating it by running the database upgrade script another time (see :ref:`scripts`). |
30 |
29 |
31 **Internal IDs** utility: |
30 **Internal IDs** utility: |
32 List of unique identifier used to localise and access easily to a resource or object declared in zo database. |
31 The catalog object doesn't store direct references to objects, but their internal IDs which are generated by this |
|
32 utility. |
33 |
33 |
34 **Language negotiator**: |
34 **Language negotiator**: |
35 Allows the management of several languages for different contents |
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). |
|
38 |
|
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. |
36 |
42 |
37 **Portal templates** container: |
43 **Portal templates** container: |
38 Allows you to define and save, one or more reuse template. |
44 Portal templates are used to define *presentation templates* based on *portlets* (see :ref:`pyams_portal`). You can |
39 These templates can be shared with the entire application for build new site. |
45 create *local* templates, or create *shared templates* into this utility which can then be reused into several |
|
46 places in your web site. |
40 |
47 |
41 **Security manager**: |
48 **Security manager**: |
42 Manage role and permission grant to a user |
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. |
43 |
52 |
44 **Sequential IDs** utility: |
53 **Sequential IDs** utility: |
45 |
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. |
46 |
57 |
47 **Server timezone** utility: |
58 **Server timezone** utility: |
48 Setup the timezone server |
59 Define the timezone server to display date and time accordingly. |
49 |
60 |
50 **User profiles** container: |
61 **User profiles** container: |
51 |
62 This utility is used to store information associated to principals through their user profile. |
52 |
|
53 |
63 |
54 |
64 |
55 Optional utilities can also include: |
65 Optional utilities can also include: |
56 |
66 |
57 **Elasticearch content indexer**: |
67 **Elasticearch content indexer**: |