Documentation Center

Fast Fetch Adapter

Very similar in overall functionality to PcmGetDocCat but significantly faster, this adapter’s custom modules define many of the callbacks developed for PcmGetDocCat plus new callbacks required to help accelerate the export process.

No objects are locked by this adapter.

The adapter is faster because the tree-walking of the SDL Contenta object hierarchy, and the assembly of the export data, is completed by PcmPortal first then the data is streamed in large chunks (~2mb) over the socket to the client program (i.e. the adapter).

With this adapter you can, in some cases, further increase efficiency using callbacks to specify export criteria before tree-walk starts to export the object data. These callbacks are exclusive to FastFetch and include:
  • pcm_content_object_export_criteria
  • pcm_content_slice_export_criteria
  • pcm_property_data_export_criteria

The criteria you most likely will want to control are object and property data criteria.

To learn more about the callbacks, read the comments (and code) in the Perl modules CustomGetDocFetchDefault.pm and CustomGetDocFetch.pm.

Object (meta) data such as OBJECT_ID, NAME, CONFIGURATION_ID, REV, etc. is accessible using $NodeDataO the same way that $CompoundO is used in the callbacks described below.

To read the object name for the current node’s content you pass 0 (a reserved parameter) and the label NAME:
$ObjName = $NodeDataO->GetValueByLabel(0,"NAME");
Available Property data is accessed the same way except you enter the field name—for example:
$DocType = $NodeDataO->GetValueByLabel(0,"Document Type");