VERIFIED SOLUTION i
X

Converting to the Enhanced Vault Resource Deduplication Model

UPDATED: September 7, 2017


Converting to the Enhanced Vault Resource Deduplication Model

 

This article will try and covert the basics of moving to the new resource deduplication model that was introduced in Vault release 7.1.1. It covers automatic resource extraction in AFP from both RMFUTIL as well as automatic extraction of inline resources in AFP. You can use one, or the other, not both. Note that a simpler resource deduplication model was introduced in Vault release 7.1.0 but the model in release 7.1.1 is more sophisticated and will yield better results.

For existing RMFUtil users:

Add ResourcePackDeduplication=2 in your profiles.ini for each section

Moving forward, resources will use the newer resource merge logic, and the names of the directories will change.

New resource directories take the form of:

_A87D8327EDA730 , but are otherwise similar to the old format.

Merged resources are stored in subdirectories under distrib and start with underscore, followed by 14 uppercase hexadecimal characters.

Each resource directory contains a listing of the profiles that reference it by way of a file created with the profile name in the file name. There can be many resource directories per profile. These files can be used in your custom scripts to manage multiple directories attached to each profile. The profile filename format is

.profile_<profilename>

A new directory named resource.map is added to your distrib directory, and contains the manifests of all the resources used by each resource group.

The manifest file is named

.<resourcegroupname>.manifest

And it contains all resources mapped for each of the resource group, including a merge history.

These are for internal use, but can be of value since they contain a history of the resource merges. Do not keep them open as they are used (and locked) by production loading of documents and this could cause document loading to fail.

The system will try to merge as many resources as possible into each resource pack. If a new resource is added, but no existing ones change, the new resource will simply be added to an existing resource directory. If there is a conflict, a new resource directory will be automatically created.

 

By default, all the resources will be bundled together as much as possible, regardless of originating job. If this is not desirable, resource group merge is a new feature to help you manage this.

 

Resource group merging allows job resources to be merged with existing resources that share some or all of their resources. Missing resources will be added to the existing resource sets.

 

There are three possible modes that can be used to configure this.

1. (default)

All resources are automatically merged, regardless of source job/profile. This is the most space efficient, but may make it difficult to later customize jobs with separate backgrounds/fonts, etc.

2. resourcegroupasprofile=1

The profile name becomes the resource group. Jobs belonging to the same profile will be merged as possible, but never mixed with other profiles. This is the preferred setting if you wish to keep things like backgroup images separate later (but not at ingestion time).

3. resourcegroup=<resource group name>

This allows multiple related jobs from different profiles to be assigned to the same resource group allowing sharing between members of that group, but no others.

 

Enabling resource merging for downloaded resources:

It is now possible to use resource deduplication with automatic AFP resource extraction, and without using RMFUtil.

This is a scenario that wasn't easy to use automatically before. You'll have to test it out for your particular needs.

1. for AFP extraction, use ....

extractdeduplication=2

mergeresources=2

ignoreresourcepacks=1

Those 2 settings turn off RMFUtil extraction, and enable automatic resource extraction merging.

You will also need to setup a template directory containing backgrounds,fonts.ini, etc.

The procedure is identical to what you would do with the RMFUtil version.

ExtractTemplateResource=<resourcename>

sets up the name of the template directory containing your base template.

Files in the template are copied over AFTER the resources are extracted, but NEVER overwrite extracted resources.

There is no way to change that behavior at this time.


Downloads

  • No Downloads