Legacy Content Delivery installation overview
A Legacy Content Delivery installation involves a list of steps. This overview lists the mandatory ones with the addition of the Single Sign On (SSO) operations. SSO is optional for Legacy Content Delivery.
The reference web server application example for the installation is Apache Tomcat.
- 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 Legacy Content Delivery capability using the installer (Windows or Linux)
- Install Legacy Content Delivery database using the database setup script (Windows or Linux)
- Establish a trust for Legacy 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