On This Page
Installing Pristy on Alfresco
Preparation
Installing the pristy-core-platform module
- Stop the service
systemctl stop alfresco
- Add the module to your modules installation folder
$TOMCAT_HOME/amps
$TOMCAT_HOME/amps
mv $DOWNLOAD_DIRECTORY/pristy-core-platform-xxx.amp $TOMCAT_HOME/amps/
- Deploy the modules from the
ampsfolder
amps
-jar $TOMCAT_HOME/alfresco-mmt/alfresco-mmt-6.0.jar \
install $TOMCAT_HOME/amps/ $TOMCAT_HOME/webapps/alfresco \
-nobackup -directory \
- Restart
alfrescoto apply the module installation
Setting up Pristy interfaces
If your server does not have a reverse proxy in front of Alfresco, you can install the applications directly
as webapps in Tomcat
pristy-portail
tomcat
mkdir -p $TOMCAT_HOME/webapps/portail
cd $TOMCAT_HOME/webapps/portail
tar xzf $DOWNLOAD_DIRECTORY/pristy-portail-xxx.tgz package/dist --strip-components=2
chown -R alfresco:alfresco $TOMCAT_HOME/webapps/portail
pristy-espaces
tomcat
mkdir -p $TOMCAT_HOME/webapps/espaces
cd $TOMCAT_HOME/webapps/espaces
tar xzf $DOWNLOAD_DIRECTORY/pristy-espaces-xxx.tgz package/dist --strip-components=2
chown -R alfresco:alfresco $TOMCAT_HOME/webapps/espaces
User for chown on pristy-portail and pristy-espaces
Make sure to correctly specify the user that starts the tomcat process.
Configuration
- Modify the
$TOMCAT_HOME/webapps/portail/env-config.jsonfile as follows:
$TOMCAT_HOME/webapps/portail/env-config.json
{
"APP_ROOT": "/portail/",
"ALFRESCO_HOST": "http://localhost:8080",
"ESPACES_HOST": "http://localhost:8080",
"ALFRESCO_AUTH": "BASIC",
"ALFRESCO_ROOT": "alfresco",
}
- Modify the
$TOMCAT_HOME/webapps/espaces/env-config.jsonfile as follows:
$TOMCAT_HOME/webapps/espaces/env-config.json
{
"APP_ROOT": "/espaces/"
"ALFRESCO_HOST": "http://localhost:8080",
"PORTAIL_HOST": "http://localhost:8080",
"ALFRESCO_AUTH": "BASIC",
"ALFRESCO_ROOT": "alfresco",
"BREADCRUMB_ROOT_URL": "/mes-espaces",
"EDIT_WITH_MSOFFICE": true, //"enables or disables editing with MS Office"
"METADATA": [] //"you can define a list of specific metadata to display in addition to standard metadata"
}
URLs ALFRESCO_HOST, PORTAIL_HOST, ESPACES_HOST
All 3 URLs will be identical if they are all installed behind the same application.
In this case, you should specify the FQDN for accessing Tomcat.
Adding metadata
To add specific metadata to display, you should follow this schema:
{
"METADATA": [
{
"id": "am:dateSeance",
"labelId": "am_date_seance",
"display": [
"datatable",
"popup"
],
"input": "date",
"readOnly": true,
"modelAspect": "",
"modelType": "am:documentActe",
"order": 1
},
{
"id": "am:codeActe",
"labelId": "am_code_acte",
"display": [
"datatable",
"popup"
],
"input": "text",
"readOnly": false,
"modelAspect": "",
"modelType": "am:documentActe",
"order": 2
}
]
}
Testing
You can access the following applications:
- pristy-portail : http[s]://
serveur_tomcat:port_tomcat/portail/ - pristy-espaces : http[s]://
serveur_tomcat:port_tomcat/espaces/
Last Update - April 30, 2026