VERIFIED SOLUTION i
X

How Resource Sets work in EngageOne Vault (formerly E2 Vault)

UPDATED: March 30, 2017


How can the user tell what fonts, images, backgrounds and other resources are being used by any particular set of documents in Vault?  How can the user make adjustments to this if necessary?  Do the files need to be reingested to update\adjust the resources used?

Resource management in EngageOne Vault is something that can be adjusted without re-ingestion of the print stream.
 
1. During ingestion, the file name is checked against the [filemap] section of profiles.ini for a match.  This derives the profile name, which is written to the header of the .DRP file.
2. In XML (and uXML) journal mode, the resource set name is derived from the ResourceGUID in the Journal File (if present).
3. If the ResourceGUID is not present, the resource set name is derived from the profile [section] that matches the profile for the current file being loaded.
4. The parameter that is looked for in profiles.ini is ResourceSet= <something>.  If nothing is defined, the resource set named “default” is used (found in the root of the vault_install_path\render folder).
5. The resource set name is written into the header of the .DRP file.
6. Ingestion (document loading) continues: 
       a. Compression (build .DRP)
       b. Document info building (build .DRD)
       c. Indexing (build/extend .DRI)
 
During search and render time, the process works somewhat in reverse:  
 
1. Index lookup (read .DRI)
2. Document info is read (read .DRD)
3. Pages are read (read .DRP)
4. In addition, the profile and resource set names are read from the .DRP file.
5. At this point, the Client software uses the profile and resource set to initialize the correct rendering components (for example. AFP vs. PostScript vs. Metacode), and loads up the various resources from the relevant resource set folder, and attempts to render the page.
 
The resource set is NOT required for the Indexes of the document.  Resources have nothing to do with the document until it needs to be rendered, therefore, the resource set can be altered without the need to reindex or reload the document.  If the user wishes to change the resource set, the FILEINFO tool enables the user to adjust the resource set folder specified in the .DRP file.  This is done with the -Rnew_name parameter, for example:
 
vault_install_path\server\tools>fileinfo
 
File Information Utility 6.0M1p0071
 
usage:
 
fileinfo <filename>
fileinfo <filename> -r<newresourcename>
fileinfo <filename> -p<newprofilename>
fileinfo <filename> -d

To see what resource set is currently being used:

vault_install_path\server\tools>fileinfo somefile.drp
 
File Information Utility 6.0M1p0071
 
filename: somefile.drp
profile: Default
resource set: HTMLRES
block size: 50000000
codec: 2
deltabitsize: 17
original size: 237995197
compressed size: 15940940
compression ratio: 14.93:1
total number of pages: 75240
average bytes per page: 211

To change the resource set from HTMLRES to another (for example, test)

D:\Vault\server\tools>fileinfo somefile.drp -rtest
 
File Information Utility 6.0M1p0071
 
** changing resource set from [HTMLRES] to [test]
 
filename: somefile.drp
profile: Default
resource set: test
block size: 50000000
codec: 2
deltabitsize: 17
original size: 237995197
compressed size: 15940940
compression ratio: 14.93:1
total number of pages: 75240
average bytes per page: 211

NOTE: Please use caution when changing resource sets because files will not display correctly if they are using the incorrect resource set!  Once the resource set has been changed with this utility the DRP does not contain any reference to the original resource set.

Environment Details

Vault 5.4, 5.5, 6.0, 6.1

Downloads

  • No Downloads