310 IBM Content Manager OnDemand Guide
From a performance perspective, the use of the transaction data field for transaction-style line 
data optimizes indexing performance by reducing the number of index values to be inserted 
into the database. Therefore, the process of loading and retrieving these large reports is 
faster and the Content Manager OnDemand database is many times smaller. 
13.4.3  AFP data
AFP data is a multi-part data type. In addition to the variable data, external resources, such 
as images, fonts, and logos, are also referenced by the AFP data stream. When Content 
Manager OnDemand stores AFP data, the resources are also archived. When the data is 
viewed, the referenced resources are displayed. 
It is a common misconception that if fonts are collected when the data is loaded, they are 
available for viewing in the Windows client. However, Windows does not recognize AFP fonts. 
It is not possible to use these fonts even if they are sent to the client as part of the resource. 
Windows clients require a mapping from AFP fonts to Adobe Type Manager (ATM) fonts or 
TrueType (TT) fonts. Content Manager OnDemand provides this mapping for most standard 
fonts. For more information about mapping custom fonts, see IBM Content Manager - 
Windows Client Customization Guide and Reference, SC27-0837. 
One possibly useful implementation of storing fonts with the resource group is when server 
reprint is necessary. If the fonts are stored with the resource group, they can be retrieved from 
Content Manager OnDemand and used by AFP printers. However, if fonts are collected, they 
are also sent to the client as part of the resources group and then discarded. Storing the fonts 
with the resource group serves only to increase network traffic when transferring the resource 
to the workstation. A more practical option for server printing is to store the font in a fontlib 
and to keep only the reference (path) to the fontlib. Although the font is accessible on the 
server, Print Services Facility (PSF) or InfoPrint does not need the font to be inline (stored in 
the resource group). The use of this approach also allows all AFP data that references the 
font to use the single instance of the font without redundant inline storage.
Figure 13-5 on page 311 shows the indexer information in the application where you can 
select the resources to collect with the Restype= parameter. Unless reprints to AFP printers 
with 100% fidelity is a requirement, do not collect the fonts.