System management for Legacy Content Delivery
System management and administration for the Legacy Content Delivery server.
- Legacy Content Delivery scalability
You can spread the distribution of your content across multiple servers. - How to safely shut down Apache Tomcat
Safely shutting down the Tomcat web application server is critical to maintaining the integrity of the Legacy Content Delivery database. - User, Permission, and Group Management
Legacy Content Delivery provides two methods of user authentication. To administer and authenticate users when they log on, you can use Legacy Content Delivery itself or you can use Active Directory (known as single sign-on). - Application URL
Configuring the Legacy Content Delivery URL may be important to help the application fit into an existing web architecture or to allow it to be indexed by search engines. - Uninstalling Legacy Content Delivery
This procedure uses the example of Tomcat Apache as web server application. - Uninstalling Legacy Content Delivery
When you uninstall Legacy Content Delivery , the program files are removed, but application data (content, customized styles, skins, and delivery packages) remains in the application data path. If you intend to reinstall to the same path after uninstalling, move the application data to a different location (or delete it) before reinstalling.