Configuring Documaker

Note:

The information in this topic generally explains the required Documaker Server setup. It provides some examples so a knowledgeable Documaker administrator can apply the information to their installation and generate the documents and metadata for use with the Documaker Connector's Documaker source component.
Documaker Connector with the Documaker source reads a database table for rows containing document metadata and an operating system path to each document file. The Documaker source performs these tasks...
  • Queries the database table for rows that have a status field that indicates those records have not been processed (STATUSCD column value of 0)
  • Selects these rows with a maximum row count which equals as many records as it is configured to consider as a maximum sized batch
  • Marks them with a status value (STATUSCD column) of 3 (in progress)
  • Processes each of those records

Documaker Server must be configured to properly generate both the document files and the accompanying database records for the documents to be archived. The configuration of Documaker Server aligns with the configuration of your content management system so Documaker will provide the desired metadata/indexing elements.

Once this list of data elements is determined, you can configure Documaker Server to store the data elements in a database table for Documaker Connector. Documaker Server can store extra data in the table that is not used for indexing, but it must at least provide all the metadata elements which are mapped into the destination content management system.

Documaker Server reads the variable data for each document from a data extract input file or database. This file is supplied in either XML or CSV (comma-separated value) format. To use the data elements in Documaker Server, the data extract values are copied into Documaker global variables, also known as GVM variables or GVMs, using one of these methods:
  • TRN_FIELDS INI option
  • Ext2GVM rule

Once the data are in GVM variables, you use DAL scripting to control a recipient batch’s output print stream name and map the metadata in the GVM variables to database table columns. The Batch Banner and Transaction Banner processing DAL scripts insert the database rows.

Batch and transaction banner processing DAL is used since DAL scripts can be triggered for the different phases of output generation. The output print stream file name and location can be controlled as well as the post transaction processing step to map the GVM variables and any other static data to database table columns (using the DBPreVars DAL function) and finally insert database rows (using the DBAdd DAL function).