Table of Contents

Antivirus and Endpoint Detection & Response (EDR) software can have a significant performance impact on the Ometa Framework. Security scanners intercept file I/O operations through filter drivers. If not properly configured, these drivers can block worker threads while scanning, leading to high CPU usage, application latency, and "thread-locking."

To balance security and performance, Ometa recommends a tiered approach to exclusions.

Level 1: Directory Exclusions (Recommended for all)

Start by excluding the following folders (including all subdirectories and files). For many modern AV solutions (like Bitdefender), this provides sufficient performance gains.

  • Installation Root: %OMETA_INSTALL_ROOT%\Ometa Software Suite\*
  • Work Directory: %OMETA_INSTALL_ROOT%\WorkDir\* (Specifically important if located on a separate drive).
  • Logs: %OMETA_INSTALL_ROOT%\Log (Prevents CPU spikes during high-frequency logging of BAM, Authority, and Core services).

Level 2: Process Exclusions (Advanced / High CPU)

If you still observe high CPU usage from your security software after applying Level 1, you should exclude the following processes. This allows these trusted applications to bypass the filter driver entirely:

  • IIS Worker Process: w3wp.exe
  • Ometa Service Processes:
    • BCA.exe
    • BCJS.exe
    • BCM.exe
    • BCSL.exe
    • BCSP.exe
    • BCS_[Interface].exe, replace the [Interface] with the used interfaces, for example: BCS_SAP.exe for the SAP Interface.
    • Ometa.Framework.Services.Audit.exe
    • Ometa.Framework.Services.Bam.exe
    • Ometa.Framework.Services.OpcUa.exe

Performance Validation (The CPU Rule):

A well-configured server should show minimal interference from security software. You can validate your configuration by monitoring the system during heavy I/O actions, such as loading the Ometa Business Connector or restarting an Application Pool.

You can easily verify if the Antivirus is impacting your Ometa environment by monitoring the CPU usage during specific actions:

How to verify:

  1. Open Task Manager or Resource Monitor.
  2. Identify the process name of your security software (e.g., MsMpEng.exe for Windows Defender, SentinelAgent.exe, CylanceSvc.exe, EPSecuritySerivce.exe etc.).
  3. Perform a heavy request in Ometa, such as loading the Ometa Business Connector and running the Ometa Portals.
  4. The result: If the security process spikes in CPU usage (e.g., taking up a significant portion of a CPU core) while Ometa is working, the exclusions are not active or are being ignored.

Note: In a correctly tuned environment, the security software's CPU impact should remain near 0% during Ometa operations.