1 Pre Requirements
- System Requirements
- All commands have to be executed using the root user.
- Make sure the locale en_US.UTF-8 is generated
- Make sure your timezone is correctly set (eg. to CET)
1.1 Initial Steps
- Download the contentnode-package archive from maven.gentics.com and extract it. Please extract the package tar.gz file on your server to a location of your choice. This guide will substitute the package directory in that location with PACKAGEDIR.
Please use the username gcn and your license key to authenticate for the downloads.
cd /var/tmp tar xfvz contentnode-package-5.16.0.tar.gz export PACKAGEDIR=/var/tmp/package
1.2 MySQL Server
Please install a compatible MySQL Server on your system. We suggest a installation of MySQL Server 5.6.2+ (64Bit) on the same server that will host Gentics Content.Node.
The following mysql permissions are needed.
mysql> GRANT usage ON *.* to node_cms@HOSTNAME; mysql> GRANT super ON *.* to node_cms@HOSTNAME; mysql> GRANT all ON node_utf8.* to node_cms@HOSTNAME; mysql> GRANT all ON node_utf8_cr.* to node_cms@HOSTNAME; mysql> GRANT all ON node_utf8_todo.* to node_cms@HOSTNAME;
The following mysql custom settings are mandatory.
[mysqld] innodb_flush_log_at_trx_commit = 2 character-set-server = utf8 character_set_client = utf8 sql_mode = "" innodb = FORCE default-storage-engine = InnoDB max_allowed_packet = 256M [client] default-character-set = utf8
1.3 Installation / Migration
The in-depth installation and migration guide can be found for these distributions:
1.4 Final recommendations and suggestions
It is highly recommened to adjust the memory settings for your installation.
1.4.1 Notable utilities and software
- munin – A very versatil monitoring software that helps investigating system perfomance issues.
- nagios / icinga – Another monitoring software that helps you monitoring the overall health status of your installation.
- backup – A backup solution should be installed that created backups of your /Node directory and the used databases. We recommand also the backup of Content.Repositories
- regular updates – Regular distribution updates are mandatory to keep your installation secure
1.4.2 Troubleshooting
There are various logs which yield some information.
- The webserver just stats ‘Forbidden’
Most likely the directory permissions are not correct. Check the apache error log.
- SGB when opening ‘.Node/’
Take a look in /Node/node/log/halt.log. Something might be wrong with the MySQL connection. Check the node.conf and your mysql users. There might be a anonymous user which prevents access for the CMS database user.
- The tree and the start page show SGB’s directly after login.
The apache tomcat server was not able to startup successfully. Try to load the tomcat settings via:
curl http://localhost/.Node/?do=24
You should get a list of properties. When this fails you have an error on the apache, php side. Otherwise something is wrong with your tomcat. Check the tomcat gentics.log and catalina.log in those cases. Keep in mind that the tomcat configuration is loaded during startup. You may just have to restart the tomcat when you just fixed an apache error. The startup of the tomcat may take a few seconds.