Copy the shared libraries into the classpath of the application
server. For Apache Tomcat, copy the libraries into the folder
${catalina.home}/shared/lib/
. When using
Tomcat 5.0 you have to copy the database driver classes (eg. JDBC Driver) to
common/lib
.
The libraries found in the directory ${catalina.home}/shared/lib/endorsed/
define APIs which possibly also exist in the JVM in other versions. Therefore those libraries need to override the JVM APIs to avoid version conflicts.
This can be achieved in one of the two possible ways:
$JAVA_ENDORSED_DIR
to point to the directory ${catalina.home}/shared/lib/endorsed/
.
Copy the content of the Gentics configuration directory into
${com.gentics.portalnode.confpath}
. See
Section 2, “System properties” for
details on the configuration path.
Modify your application server's configuration:
Make sure the application server does not include the context paths into the generated session cookies.
For Apache Tomcat 6: SetemptySessionPath="true"
for all <Connector>
-nodes in the file
tomcat/conf/server.xml
.
For Apache Tomcat 7+: Configure sessionCookiePath="/"
in the global context.xml tomcat/conf/context.xml
.
For Apache Tomcat create a user account with access to the manager application and add the login data together with the access data for the manager into your portal configuration file. For details see Section 8.8, “administration-section”
Deploy the Portal.Node.war on your application server.
In Tomcat you can use /manager/html to upload and deploy the webapp. Take care you stop and undeploy any already existing instances in before. It’s also suggested to restart Tomcat after redeploying an application, see http://jakarta.apache.org/tomcat/faq/deployment.html for details.
Your application server should be configured to
provide the maximum amount of heap memory possible
(-Xmx
see man
java for details). The minimum is 512MB
(-Xmx512M). The maximum on a 32bit platform is about
1,5GB (-Xmx1536M). On dedicated 64bit platforms you
should provide nearly all you have.
(Optionally) deploy the GenticsImageStore.war on your application server (see above).
Open the url
http://[hostname]/Portal.Node
on your browser (substitute [hostname] with the servers hostname or ip address).
When not already done before, follow the shown
instructions to activate your copy of Portal.Node.
You need a valid License Key (e.g. A234-B678...) to
activate your installation, it can be obtained from
<sales@gentics.com>
.
![]() | Note |
---|---|
This activation process will only work if you access Gentics Portal.Node directly. If a reverse proxy is configured in front of Gentics Portal.Node which might replace the 'Host' header from the request, please use the following manual activation process. |
If you get a HTTP 503 (service unavailable) error
instead of the activation instructions, you do not
have activated the activation dialog. In this case,
you can either turn on the activation dialog (see
Section 8.2.3, “Portal server activation”
for details) or find the activation instructions in
your portal server's log file (for Tomcat typically
${CATALINA_HOME}/logs/catalina.out
).
![]() | Warning |
---|---|
To finish the installation Process you will have to activate the product with your license key. Unless activated properly the portal will keep showing the activation instructions or - when the activation dialog is turned off in the portal configuration - responding with a HTTP 503 (service unavailable) error and write an error message in the logfile. |