Content Delivery installation overview
A Content Delivery involves a list of mandatory steps. If one is skipped, for example making the Security Token Service recognize Content Delivery, then the capability cannot be functional.
There are two types of installation: bundled and non-bundled. The bundled installation installs both Content Delivery and a web application server (Jetty). The bundled installation is usually limited to demo situations because the bundled server doesn't not allow collaborative use (no Single Sign On), and is considered an exceptional action.
The reference example for separately installed web application servers in Apache Tomcat 8.
- Get a license
- Check the software requirements
- Set up environment variables and paths appropriately
- Enable Secure Socket Layer (SSL) protocol for the web application server
- Enable restricted http protocol for Apache Tomcat
- Install Content Delivery capability using the installer (Windows or Linux)
- Install Content Delivery database using the database setup script (Windows or Linux)
- Establish the trust for Content Delivery in the STS (enabling a Relying Party)
- Configure files for SSO (LiveContentSSO.xml, LiveContentSecurity.xml, lc.properties)
- Map to authorization groups (LiveContentGroups.xml)
- Configure (Java timeouts, path to Linux logs, non-ASCII characters, ...)
- Test/validate