Processing Resource Consumption on the Database Server - Directory Import Processor - English - Foundation 22.1 - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

Directory Import Processor

Platform
OnBase
Product
Directory Import Processor
Release
Foundation 22.1
License
Standard
Essential
Premier

Remember to consider processing resource consumption on your database server. Processing incurs a large drain on the database server's resources.

  • In most cases, you will install an instance of the Client module on the database server, and run the process during non-peak times. Take into account the Client's additional resource requirements, in terms of process capabilities and memory, on the database server.

  • The Directory Import Processor process speed will be directly related to OnBase 's ability to communicate with the database. Anything that improves the communication between the Client Workstation that is processing and the database server will increase the processing speed.

  • Attempting to run a Directory Import Processor process while running another process, such as COLD or another Directory Import Processor process, will result in a dramatic drop in all processing speeds. It is usually best to run a single automated process at a time.

  • During Directory Import Processor processing, the database will receive a large number of queries and updates. If the database is not configured correctly, the overall database performance could potentially be degraded.

The process can be scheduled like all automated OnBase processes.

When a document is processed in, the database is updated with a new record for the document as well as all of the Keyword Value information for it. The record also includes the path to the data file.

The Directory Import Processor configuration format is stored in the database. When the Directory Import Processor process is selected in the Client module, the process format information is loaded. Changes to the process format will only be seen after the Client is re-launched.