How can i install the Gentics Content.Node Package?

This page described what steps are needed to install Gentics Content.Node. Additional information can be found in the Admin install guides page.

1 Debian Linux

  • Download the installation package tar.gz file from the Gentics Updatesite using the login gcn and your licensekey.

1.1 Guided Installation


  cd /opt/
  wget https://gcn:1111-2222-3333-4444-5555-6666-7777-8888@updates.gentics.com/maven2/com/gentics/contentnode-package/5.12.0/contentnode-package-5.12.0.tar.gz
  tar xfv gcn5_package-5.12.0.tar.gz
  cd package
  ./install.sh

The installation script will prompt for host names and license keys.

1.2 Unattended Installation


  ./install.sh cms.gcn-testing.office 1111-2222-3333-4444-5555-6666-7777-8888

2 Red Hat Enterprise Linux / SUSE Linux Enterprise Server

Currently the install.sh script only supports Debian Linux. However a manual installation can be achieved on SLES/RHEL.

2.1 User Creation


  groupadd node
  groupadd node_public
  useradd -d /Node -g node -G node_public node
  useradd -d /Node -g node_public node_public

2.2 Move files into place


  cd /opt/
  wget https://gcn:1111-2222-3333-4444-5555-6666-7777-8888@updates.gentics.com/maven2/com/gentics/contentnode-package/5.12.0/contentnode-package-5.12.0.tar.gz
  tar xfv gcn5_package-5.12.0.tar.gz
  cd package
  
  # Main Installation
  cp -ra Node /
  
  # Demo Content Files
  cp -ra dumps/dbfiles/* /Node/node/content/dbfiles/
  chown node: /Node/node/content/dbfiles/*
  

2.3 Correct local file permissions


  cd /Node
  ./dist_setperm.sh

2.4 Setup the Autostart


  ln -s /Node/bin/nodectl  /etc/init.d/nodectl
  # Enable nodectl for runlevels 2,3,4,5 or use the dependency boot system tool __insserv__ or by using __sysv-rc-conf__.

2.5 Setup locales

Make sure that the locale en_US.UTF-8 has been created

2.6 Compatibility libraries

Make sure that the ia32 compatibility libraries have been installed.

2.7 JVM and native libraries

Change the JVM and native libraries (Only applies when a 64 Bit system is used) Use uname -a to check whether you have a 32bit or 64bit system


  # JVM
  unlink /Node/java
  ln -s /Node/jdk1.6.0_14_x64/ /Node/java
  
  # Fileutils
  unlink /Node/lib/libgtx_fileutils.so.1.0
  ln -s /Node/.node/modules/content/files/libgtx_fileutils_64.so.1.0 /Node/lib/libgtx_fileutils.so.1.0

2.8 License Key


  echo "1111-2222-3333-4444-5555-6666-7777-8888" > /Node/etc/tomcat/gentics/license.key
  chown node:node /Node/etc/tomcat/gentics/license.key

2.9 Gentics Content.Node Configuration

Replace the string REPLACESERVERNAME with your desired server name in the /Node/etc/httpd/sites-available/cms.conf file.

2.10 Memory configuration

The default system configuration will utilize around 2-4 GB memory for the MySQL Server, Apache Tomcat Server, Apache and caches. Information about memory configuration can be found in this FAQ (Only available in german language)

2.11 Start the MySQL


  /Node/bin/nodectl start mysql
  # Wait a moment since the mysql could take a moment to startup

2.12 Insert MySQL Dumps


  # Main Gentics Content.Node Database
  echo "CREATE DATABASE node_utf8" | /Node/bin/mysql.sh -u root
  cat /opt/package/dumps/node_utf8.sql | /Node/bin/mysql.sh -u root node_utf8

  # Demo ContentRepository
  echo "CREATE DATABASE contentrepository" | /Node/bin/mysql.sh -u root
  cat /opt/package/dumps/contentrepository.sql | /Node/bin/mysql.sh -u root contentrepository

  # Demo Portal ContentRepository
  echo "CREATE DATABASE contentrepository_portal" | /Node/bin/mysql.sh -u root
  cat /opt/package/dumps/contentrepository_portal.sql | /Node/bin/mysql.sh -u root contentrepository_portal

2.13 Start the backend


  /Node/bin/nodectl start

2.14 Crontab Entry


  echo "# Gentics Content.Node Scheduler Task" >> /etc/crontab
  echo "* * * * *         node    /Node/bin/scheduler.sh >> /Node/node/log/scheduler.log 2>&1" >> /etc/crontab

3 Final steps

You should now be able to access the Gentics Content.Node login page. The /opt/package directory can be deleted.

  • MySQL

We highly recommend that you replace the 32Bit package MySQL with a separate 64Bit MySQL because this will allow you to enhance the memory settings.

  • Memory Setting

Please take some time and adjust the memory settings for your new server. This is very important because it will enhance the performance and improve the usability for your editor. Details are documented in the memory and performance guide.