
SDL Tridion’s content delivery architecture enables your organization to develop a truly dynamic web environment. It is designed to ensure that your customers interact with a high-performance website regardless of content complexity and dynamic delivery requirements.
Presentation Server enables your organization to publish robust and scalable websites and web applications. Presentation Server provides storage-, link- and cache-management capabilities for high-performance web environments. Dynamic Content Broker enables you to deliver dynamic content based on page context, queries and visitor profiles, ensuring that visitors find relevant information quickly. Content Services enables you to access published content and marketing assets through the SDL Tridion RESTful web service that uses the OData protocol to simplify access and content discovery. In addition, different types of applications (such as eBanking and eCommerce applications) and portals can access integrated content. Secure Content Delivery ensures that sensitive or confidential content is accessible by those with user accounts or permissions. You can control access by providing permission to predefined groups of employees, customers or suppliers. | Benefits
|
| Infrastructure support | Windows and UNIX/Linux infrastructure support |
| Web infrastructure | .NET and J2EE |
| Application servers | IMB WebSphere®, BEA WebLogic® and Microsoft Internet Information Server® |
| APIs | .NET, J2EE and RESTful web service supporting oData |
| Served content | HTML, ASP.NET, ASP, JSP and XML with XSLT (static and dynamic) |
| Storage | Oracle, Microsoft SQL Server, IBM®, DB2®, file system |
| Permission verification | .NET 1.1, 2.0 or higher |
| Transport protocols | FTP, SFTP, HTTP, HTTPS and file copy |
Enterprise readiness. SDL Tridion 2011 brings a number of substantial engineering enhancements to Content Delivery architecture to allow for higher publishing throughput and multi-threaded deployment for high-volume publishing.
Storage model. Define custom storage rules to publish assets to dedicated servers in your environment, content delivery networks (e.g. Akamai) or 3rd party providers (e.g. YouTube). Making use of JPQL, the storage model natively supports transactional deployment.
Content Services module. Offers a robust and uniform way to share information beyond your CMS environment. The RESTful web service takes care of dynamic links, targeting and OAuth support. Content Services follows the latest best practices for serving content to social networks such as Facebook and Twitter.