ChangeURL in the back office
If you wish to modify theurl backoffice you must :
- Modify DNS entries
- Modify configuration Apache
- Modify configuration Tomcat
- Modify application configuration CMS
- Modify site application configuration
IP address, machine name and DNS
- Add a new DNS entry for new servers
- Set the new IP addresses and host names in /etc/hosts
Apache
ModifyApache configuration to use the new DNS. The location of the files used depends on the OS and the choices made by the system administrator. There is a file for CMS and a file for the Site. These files are usually named :
- /etc/apache2/sites-enabled/httpd-cms.conf for the CMS
- /etc/apache2/sites-enabled/httpd-site.conf for a Site.
- Perform these operations for each new server.
Tomcat
If you've followed the installation documentation and used our tomcat configuration template, then you don't need to modify anything in tomcat, otherwise you need to look at the server.xml file and the webapp declarations.
Configuration of CMS
Go to the CMS administration interface to update the configuration:
- http://cms.xxxxxx.fr/_admin (use administration login, default: admin/admin)
- Click on the configuration tool
- If necessary, modify interconnections with services such as LDAP, Apogée...
- In the left-hand menu, click on CMS and replace the back-office address
- If necessary, change theURL back-office address set for Solr in the Search and Indexing menu. In general, this is not necessary, as it is advisable to set this address to the local address of tomcat (e.g. http://localhost:8080).
- In the Configuration contextual ribbon, click on "Save and restart".
- Wait for registration and restart
Site application configuration
For multiple sites, repeat the operation as many times as necessary.
Go to SITE administration interface to update configuration
- http://www.xxxxxx.fr/_admin (use administration login, default: admin/admin)
- Click on the configuration tool
- If necessary, modify interconnections with services such as LDAP, Apogée...
- In the left-hand menu, click on CMS and replace theURL and, if required, the CMS IP. We advise you to let applications communicate on the Tomcat port (8080 by default).
- In the Configuration contextual ribbon, click on "Save and restart".
- Wait for registration and restart
Modify theURL front office
Please note that we're talking here about modifying theURL of the front-office application, which is not necessarily that of a hosted site.
As with theURL backoffice modification, you need to modify the DNS, apache and tomcat configuration. For further details, please refer to the corresponding paragraphs in the previous chapter, the procedure is the same.
This chapter covers the changes to the CMS configuration for the new URL website.
Configuration of CMS
Go to the CMS administration interface to update the configuration
- http://cms.xxxxxx.fr/_admin (use administration login, default: admin/admin)
- Click on the configuration tool
- In the left-hand menu, click on Websites and replace the front-office application addresses and front-office IP addresses with the new ones. It is advisable to let the applications communicate on the Tomcat port (8081 by default) and the IPs are those through which CMS sees the sites (when a request is made from a site to CMS).from a Site to CMS).
- In the Configuration contextual ribbon, click on "Save and restart".
- Wait for registration and restart
Modification of a site'sURL
Modification of the CMS
Log on to the CMS administration interface:
- http://cms.xxxxxx.fr/_admin (use administration login, default: admin/admin)
- Click on Sites
- For each site, click on the site, then on "Configure".
- Change at leastURL, check the title and description.
Rule changes Apache
Il faut modifier le fichier de règles correspondant au site dont vous voulez modifier l’URL. Ce fichier est situé dans /etc/apache2/sites-enabled/ (cela peut varier en fonction de votre système d’exploitation) et en règle générale est nommé selon la nomenclature <url>.conf
- Rename this file with the new DNS,
- Replace all references to the old DNS in the file with the new DNS,
- Reload the apache configuration by running " service apache2 reload " (this may vary depending on your operating system).
Test your new configuration
- Log on to the new URL . CMS
- Creating pages and content
- Validating content
- Log on to the new URL website, and check that the pages that have been validated are available on the site.
Back to top