Batch runs to Vault
The steps that follow must be completed prior to ingesting documents into Vault:
Note that this is a basic guideline only. For more detailed instructions refer to the appropriate Vault Guide.
To configure the environment:
- Ensure that the Vault configuration has been modified to ingest the following
files:
- Profiles.ini
- Database.ini (if being used)
For detailed information about modifying these files please refer to the Vault User’s Guide.
- Ensure that the EngageOne output device and delivery channel are configured
correctly.
- You must have a delivery channel configured for Archive.
- Archive must be set to Batch mode.
For detailed information on configuring output devices and delivery channels refer to Archive definitions.
- Ensure that the transfer mechanism (FTP or other script) is configured.
- The files must be routed to the hot folder in Vault
Windows default path:
Vault\Server\download
.To run batch for Vault:
- The files must be routed to the hot folder in Vault
Windows default path:
- Run accumulated batch for the Archive delivery channel. This creates an accumulated print stream file, a resource file and an accumulated index file.
- Transfer the files created in step one from the
accumulated batch process to the Vault hot
folder. You can view documents as they complete ingestion.
AFP resources
Note that when working with AFP files you must follow these steps before the files are transferred to Vault to ensure the availability of resources:
- Open for Edit the
profiles.ini
file for the Vault Application. - Add the line
ExtractResources=distrib\Default
to the profile section used for EngageOne. - Users with potentially conflicting resource sets may
extract to separate directories specifying:
ExtractResources=distrib\resourceset1 ResourceSet=resourceset1 ExtractResources=distrib\resourceset2 ResourceSet=resourceset2 . . . ExtractResources=distrib\resourcesetn ResourceSet=resourcesetn