Post installation actions (non-bundled)
After you have installed Content Delivery separately from the web application server, follow these tasks to establish the Single Sign On and configure the capability.
- Manually installing a license file
If you did not have a license file when you installed or upgraded Content Delivery, or if you have a new license file to install, follow this procedure. - Configuring Content Delivery to Support Single Sign-On (SSO) User Authentication
To enable Single Sign On (SSO) for Content Delivery, you first must load the secure socket layer (SSL) and security token service (STS) certificates, configure the STS service to recognize the web application, and make some minor configuration file modifications. - Configuring the Content Delivery Web application
Optimize Content Delivery Web application performance by setting Java's initial and maximum heap size and by overriding session timeouts. - Configuring context.xml files
When you proceed to an unbundled installation (using your own Tomcat server with Content Delivery), we recommend that you make specific changes in Tomcatcontext.xmlfile and in Content Deliverycontext.xmlfile. - Setting the path to Linux installation logs
By default, when you run startup.sh, your installation log files are saved in a logs/ subdirectory relative to the directory from which you run startup.sh. For example, in $tomcat, running bin/startup.sh makes logs appear in $tomcat/logs/. To log to the same directory at all times, in Content Delivery's WEB-INF/log4j.xml, specify the full path to your $tomcat/logs directory. - Enabling the use of non-ASCII characters on Content Delivery
Only if you use Apache Tomcat 7 or earlier, addURIEncoding="UTF-8"to every HTTP connector in your server.xml file. (For Apache Tomcat 8 or higher, this attribute is present by default.)