Content Rendition Services (CRS), formerly known as AutoRender Pro, is a Documentum tool that generates renditions or alternative formats of the original document in a Docbase.
CRS deals with requests from client applications (say Web Publisher) for rendition (for example PDF, Text, HTML) of original documents. CRS, however, does not produce renditions for documents that are in the checked-out state in the Docbase.
CRS should be run on a separate dedicated networked work station and should be the only software executed on the particular work station.
Figure 4.4 indicates some source formats in Documentum Docbase and whether their PDF and HTML renditions are possible via CRS.
|
Source Formats |
HTML rendition possible? |
PDF rendition possible? |
|---|---|---|
|
Microsoft Word |
Yes |
Yes |
|
Microsoft Excel |
Yes |
Yes |
|
Microsoft PowerPoint |
Yes |
Yes |
|
WordPerfect |
No |
Yes |
|
Lotus WordPro |
No |
Yes |
|
PostScript |
No |
Yes |
|
|
No |
Yes |
Figure 4.5 shows how the content rendition services serve rendition requests from Docbases.
Figure 4.5: Generating renditions via CRS
The process of generating renditions via CRS is as follows:
- The client sends a rendition request to the Content Server.
- The Content Server stores the rendition request from the client in a
dm_queue. - CRS polls the
dm_queueat pre-configured intervals to find out if there are any pending rendition requests to be served. - CRS creates renditions as per the rendition requests in
dm_queue, and sends them across to Content Server, which saves the renditions in the Docbase.
We can configure the frequency with which CRS polls the Docbases for rendition requests. Also, note that one CRS workstation can serve the rendition requests for a maximum of eight Docbases.