CoreIntegrator A/P One Enterprise General Management and Maintenance

Applicable to the following:

For customer deployments including on premises, hosted or cloud-based solutions where the customer has responsibility of the “server” infrastructure and/or environment.  This document does not apply to CoreIntegrator SaaS solutions such as A/P One Growth or Enterprise SaaS models.

The information within this document may not apply to all installations as each implementation may be customized to meet specific customer requirements.  It is important to specify (where noted) of any unique requirements or configurations that may impact the proper maintenance of the CoreIntegrator Environment.

General Business Practices and Data Protection:

Although this document will provide reference to backup and general maintenance, it is up to the customer to apply best practices that is suitable for your environment.  CoreIntegrator is not responsible for lost or corrupted data, security breaches, hacks or other data loss due to negligence or other reasons.  It is up to the customer to provide all appropriate levels of protection for your environment.


CoreIntegrator and related solutions rely on a number of system services to keep the application running and operating at expected levels. The following services require an active status, in most environments, to be running at all times.  Note:  it is the customer’s responsibility to actively monitor the status of these services or set up alerts.


  • Batch Notification Service
  • Communication Service
  • Document Cache Service
  • FileWatcher Service (if applicable)
  • Search Index Service
  • Workflow Client Service
  • Workflow Communication Service (not required per note below)
  • Workflow Task Scheduler Service
  • Workflow Engine Service

Note:  The Workflow Communication Service does not apply to any release version of 3.6.5 or later.

Note:  these services can be managed through a services admin console or from within the CoreIntegrator Administrator’s section under the heading of “Diagnostics”.

Other Services:

For customers using the AncoraDocs OCR engine, the following services must be running (some depend on the services deployed) – these are managed from the services screen directly on the server.  Ancora may have multiple servers and these services may be split between each server.

  • ancoraDocs Automated Client Manager
  • ancoraDocs Input Service
  • ancoraDocs Email Input Service
  • ancoraDocs Licensing Service
  • ancoraDocs Server
  • ancoraDocs Web SDK Service
  • RabbitMQ

Additional Services:

If there are other services that apply to your implementation, they should be documented and managed by the customer.

Database Management, Back-up, System Requirements:

Each server environment is configured initially to support the number of users, the number of transactions, integration requirements and other needs to perform at optimal levels.  

  • These needs change over time and should be reviewed on a regular basis including but not limited to the following:
    • Most installations include a Primary Application Server (IIS Web Server), a SQL server and disk allocation.
      • CPU demand and resources available for each server
      • Memory usage for each server
      • Disk availability for each server

Maintenance Plan:

Checking Log Files:

If the database uses a full recovery model, then the appropriate transactional backups and log database maintenance must be performed regularly.  Log files will grow and must be managed and log files must be truncated during back up procedures.

If the database uses a simple recovery model, then perform backups according to existing corporate backup strategy plans.  Log files will not grow using this method (but note that “data” will continue to grow independently).

Back up:

The following databases must be backed up per the customer defined recovery strategy.  Note:  these apply to production servers only.  Development and test environments may apply.

Ci_repositoryname (generally customer name)




For ancoraDocs:

  • Ancoradocsserverdb

There is a Local File System where all your document images are stored.  This location must be backed up as well. 

Custom Scripts also need to be backed up.  They are stored in another location called the CoreIntegrator application folder:

Example:   c:\Program Files\CoreIntegrator\Web\Custom

Custom databases and scripts may exist but are generally part of a custom deployment.  Check with CoreIntegrator for additional databases and scripts that were uniquely included in the initial deployment.

Note: if you are using Sharepoint, be sure to back up the Sharepoint content database – by default it is called:  wss_content (but can be named anything).

Index maintenance:

All tables in the databases listed above should be re-indexed on a regular basis, recommendations are at minimum weekly.  This is set up in SQL server under scheduled maintenance plan.  Nightly reindexing is a common practice.

Disk Space Monitoring:

  • Application server and SQL Server:  generally, CoreIntegrator is stored on a drive C: or D: of the IIS server and generally will not change but should be monitored.  The SQL server will change and needs to be monitored on a regular basis.
  • The app server includes standard windows temporary file storage as well as various caches/temp files.  CI also caches email files for the communication service on the C:\ drive
  • Document (including cached documents which may be located on another drive) storage location:  customer defined.  Because disk utilization grows at a much faster pace for image files vs. traditional data files, it is important to monitor the available disk space for these documents.
    • CoreIntegrator has a secondary “Document Cache” folder which may be configured to use a different storage location 
  • SQL Server: Both the SQL .mdf files and the .ldf files on the SQL server can grow – refer to the discussion under “Checking Log Files” above.

Windows Updates:

  • Keep current on all Microsoft updates and patches.

Additional references and support:

CI administration guide: (included in the application help section)

Release notes: (also included in the application help section)

Contact support: