Application configuration CMS

Introduction

From the administration interface, click on the Configuration button to access your application's configuration CMS :

Settings are organized by category. A summary of these categories can be seen on the left-hand side of the screen, allowing direct access to a category's configuration by clicking on it:

 

 

Categories can be folded/unfolded by clicking on the arrow to the left of the category heading. In the illustration below, the category Search and indexing declined, while the Repository has unfolded.

A tooltip is displayed when the user moves the mouse cursor over the  to the right of each form field.

List of configuration parameters

The list of available parameters depends on the features actually deployed in your application. Here we present the configuration as seen in the demo application ofAmetys.

 

In the CMScategory, specify the Internet address of the back-office application (CMS).

This URL is used as a reference for external access (users). This parameter is used, for example, to build the addresses provided in e-mails (links to the application).

Please refer to theAmetys architecture description for an overview ofAmetys components and inter-component communications.

In the category Send mail,

  • Server parameters section: enter the configuration information for the mail server that will be used to send the application's e-mails (url of the SMTP server, port and user name/password if required). The Verify connection to mail server button lets you check that the information you've entered enables you to establish a connection with the e-mail server.

 

  • Mass send heading: When the Send to all box is unchecked, if the users authorized by a context right are all users, none are sent. This is a safety feature to prevent mail from being sent en masse by mistake. You can check this box to have a normal behavior and return all users in this specific case.

 

  • Addresses section: enter the default sender and system administrator e-mail addresses.

 

In the Forms category, specify the data source to be used for managing form data.

You can create the data source on the fly by clicking on the . More information on data sources here.

In the Content management category,

  • Section Content purging Select whether you wish to set up automatic content purging, then enter the following parameters:
    • Automatic purge period: number of days between two purge starts,
    • Time of automatic purge,
    • Version purged after : Number of days after which a content version is deemed too old and is removed the next time it is purged.

    • Keep last validated versions: number of last validated versions not to be deleted during purge.

More information on purging can be found on the dedicated page in the user manual: Purge contents.

 

  • Automatic unlocking section: specify whether you wish to take advantage of the automatic content unlocking feature, and set the length of time before content is unlocked (in hours).

 

  • Section Comments on content : specify whether moderation should be a priori or a posteriori.
    • A priori: comments will only be put online after validation by a contributor with such rights.
    • A posteriori: comments are automatically published but remain editable.

This parameter can be redefined in the site configuration.

 

  • Backup section: If you wish to automate backup, specify the frequency (in minutes) at which information should be saved.

 

  • Section Content reminderspecify :
    • reminder e-mail sending time
    • Automatic reminder times in days. Enter '0' to deactivate the corresponding alert.

 

  • Broken links section: specify whether you wish to set up an automatic check for broken links (with a report sent to mail if such links are detected) and set the time of the check process.

 

  • Copy and paste external content section: specify whether you wish to store linked files, and if so, the list of file extensions to be stored.
    If you enable this feature, when copying text into the rich editor ( copy-and-paste action), links to files with specified extensions will be automatically stored in the content (as content attachments).

 

  • Scheduled archiving item: specify the time at which the automatic scheduled archiving process will start. This process will archive all content scheduled for archiving on this day.
    Also enter the reminder delay before archiving (in days). The contributors concerned will receive a notification by mail reminding them that the scheduled archiving of the content will take place in X days. Set to 0 to disable this feature.

 

  • Resource Explorer section: check the Common resources for all sites box to give access to a directory of common resources shared by all sites. Deactivating this option does not delete the contents of the directory, but makes it invisible to users.

 

As content purging, broken link reporting and reminder e-mail processes are resource-hungry, it is advisable to run them overnight (the same applies to all automatic functions).

In the User registration category, specify the data source to be used to manage user registration data.

You can create the data source on the fly by clicking on the . More information on data sources here.

In the Task Scheduler category, specify the data source to be used to store and manipulate task scheduler data.

You can create the data source on the fly by clicking on the . More information on data sources here.

In the Form protection category, choose the Captcha system you want to use to protect your forms from spamming.

Two human recognition systems are available:

In the case of reCaptcha, you'll need to specify the site key and secret key provided by Google. Log in to your Google account to obtain a reCaptcha key: https: //www.google.com/recaptcha/intro/index.html for your domain name(s).

Then retrieve the site key and the secret key.

In the case of reCaptcha Entreprise, you'll need to specify a project id, aAPI key and the Recaptcha-specific site key supplied by Google. To generate theAPI key, go to https://console.cloud.google.com/apis/credentials and create aAPI key for your project. To generate the site key, go to https://console.cloud.google.com/security/recaptcha and generate a key for your domain name(s).

In the Search and indexing category,

  • Rights cache reload section Solr: Enable automatic cache reload and specify the time at which the rights cache on the Solr server will be reloaded.

 

  • Section Server Solrspecify :
    • theURL server Solr (without the 'collection' part). The Verify connection to Solr server button is used to check that the Solr server'sURL is valid,
    • the prefix used for Solr cores,
    • the internal address of the back-office, used by the Solr server to request Ametys. This address can be left blank to use the address entered in the CMS,
    • the IP address of Solr, for verification when it needs to request Ametys. This address can be left blank to avoid protection.

In the Repository category,

  • Section Display Node sorting: specify the node sorting method to be used by default. Choose from the following options:
    • Alphabetical order
    • Reverse alphabetical order
    • Document order

 

  • Heading Persistence jackrabbit: specify whether you wish to use the default data storage Derby for data storage JCR. If not, specify the data source to be used.

You can create the data source on the fly by clicking on the . More information on data sources here.

 

  • Repository section JCR: specify the size of the JCR cache in bytes, 16777216 by default 16MB.

In the Search Engine Optimization category, enter the time you want the sitemap to be pinged to search engines.

Pinging your sitemap to search engines lets them know that your site map has been updated.

In the Websites category, complete the list:

    • from URL front-office applications (sites) separated by commas. These are the URL used internally, for example, to avoid going through Apache and access localhost directly. In particular, they are used by CMS to invalidate the SITE application(s) cache (i.e., the various site caches).
    • IP addresses of front-office applications, separated by commas. These IP addresses will be the only ones authorized to make page generation requests to CMS. You therefore need to enter all the IP addresses of your front-office applications (SITE).

Please refer to theAmetys architecture description for an overview ofAmetys components and inter-component communications.

In the Cache statistics category, check the Enable box to activate the processing of cache usage statistics.

Please ensure that you have created the SQL tables required for this functionality (scripts/jdbc_cache_mon.sql), and that you have configured access to the monitoring database in the Monitoring database section.

 

In the System category,

  • Development mode section: if you choose Development mode, CSS/JS files will be unminified, which is useful for debugging but will reduce application performance. The cache of page elements will also be deactivated.

 

  • System alerts section: you can enable system alerts. In this case, specify the limit value for free space on the disk where theAmetys data directory is located (indicated in MB). An alert will be sent when the available space falls below this value.

 

  • Upload management section: specify the maximum size (in bytes) of uploaded files, whether to activate antivirus protection and the command to use in this case.

Please refer to the anti-virus installation page for details of the order to be specified.

 

  • Logging section: check the Track long processes checkbox to activate 'warning' severity tracking in application logs for processes taking an abnormally long time.

 

  • Section Data sources Indicate the data sources to be used for :
    • store authentication tickets,
    • store group directory assignments to contexts,
    • store assignments of user populations to contexts,
    • store and manipulate rights,
    • store and manipulate user preferences.

You can create data sources on the fly by clicking on the . More information on data sources here.

 

  • Connection section: check the Public instance box to declare this instance ofAmetys as public. In this case, the drop-down list of populations will no longer be proposed for confidentiality reasons. Users will need to know their population ID.

 

Configuration backup

Click on the Save and Restart ribbon button to save your changes:

We recommend that you check the settings before saving and restarting the application, as a confirmation pop-up will appear to confirm your choice:

The action Save and restart cuts off access to CMS and reloads the new configuration. This operation may take some time, depending on the structure of your installation and the complexity of your application.

 

Back to top

Administration manual