Ligero

Accessing Content Is Easier And Faster Than Ever!

Do you want your end users to read documents without logging into WebTop and without you having to replicate all that content to a file system? Are you tired of writing still more custom applications for users to access content? Wondering how to get all of the information sitting in your repositories out to your new intranet or portal? Do you use RightSite and need to upgrade to D6 without time-consuming changes?

Introducing Ligero Content Delivery Server

An advanced caching server, Ligero Content Delivery Server (CDS) provides a simple, flexible, scalable way to access content managed in Documentum. With MicroSoft SharePoint, or other portal environ- ments, you can access the Documentum repository efficiently and easily through simple dynamic pages, URL links, RSS, or custom Flex applications. What’s more, you can upgrade to D6 without changing con- tent or interfaces…that’s because Ligero CDS supports legacy Documentum RightSite tags and anony- mous access. All that, and Ligero can be used with any version of Documentum.

What It Does

Traditionally, web content is pushed from a cache, but Ligero eliminates potentially enormous caches by pulling requested content from a repository. This model increases efficiency by making content deliv- ery faster and easier on the publishing engine and reducing network disk and processing infrastructure requirements. Even better, Ligero takes a best-of-both-worlds approach by caching the most frequently requested content, reducing dependency on the repository server. Access is provided through anonymous sessions or user-supplied credentials for confidential data.

How It Works

Ligero CDS employs dynamic page assembly, which means files are pro- cessed on request — not statically staged. With just a few lines of code, you can pull together content from multiple files and combine that with other query results to create compos- ite pages. Ligero will RSS-enable your entire repository and will ensure that the most current content is viewable as soon as it is ready. Additionally, load balancing, preemptive caching of critical content, and other techniques reduce the dependence on the reposi- tory server to provide added perfor- mance and reliability.

Example implementation scenarios

Ligero is flexible, powerful, and only limited by your creativity. But here are a few examples to get you started:

• Your organization has a requirement to make policy and procedure documents available through all internal portals. The documents are maintained in Documentum but each division maintains its own portal using different software: two versions of Microsoft SharePoint Server (2003 & 2007) and IBM WebSphere. You don’t want to force readers to learn a new product (WebTop); so a dynamic table of contents is created in Ligero that filters the appropriate content from the metadata in Documentum. Because these are infrequently accessed documents, the content only is pulled from the repository when needed. Changes are immediately reflected in the listing, and the owners of the content only have to maintain it in one place. Users don’t have to leave the application they are in to access the content they need to read.
• Your bio-medical company manages its packaging system with a third-party product. The application has a feature that enables users to click on hyperlinks to display text specific graphics or instructions. But the system only supplies a step number to a web address when identifying the content. A simple page in Ligero is created to read the parameters and retrieve the appropriate document to the manu- facturing application.
• HR Managers are required to review changes in benefits when they are published. Since the ben- efits documents are in Documentum, an RSS link can be added to their start page. The RSS reader account is given browse access so that it can see the documents that have changed within the /HR/ Benefits cabinets. When one of the managers clicks on the document link, the system will recognize that the Ligero admin account does not have read permissions and ask for user credentials. Once credentials are provided the content requested is displayed.